Default downlink or uplink beam for downlink control channel with repetition configuration

Abstract

In wireless networks, a physical downlink control channel (PDCCH) can be transmitted with multiple repetitions, which can lead to ambiguity in scenarios where a user equipment (UE) has to determine a default downlink or uplink beam for receiving or transmitting a data channel. Accordingly, in scenarios where a UE receives a PDCCH associated with a repetition configuration and the PDCCH does not include a beam indication, the UE can determine a default beam for receiving or transmitting a data channel scheduled by the PDCCH based on the repetition configuration of the PDCCH. For example, the PDCCH can be associated with multiple control resource sets (CORESETs) and / or associated with a CORESET that is associated with multiple transmission configuration indication (TCI) states. Accordingly, the UE can determine the default beam based on one or more parameters associated with the multiple CORESETs and / or associated with the multiple TCI states associated with a CORESET.

Description

[0001] Field of the disclosure

[0002] Aspects of the present disclosure relate generally to wireless communication, and to techniques and apparatuses for determining a default downlink or uplink beam for a downlink control channel with repetition configuration. BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can 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 technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0004] A wireless network can include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A UE can communicate with a BS via the downlink and uplink. The downlink (or forward link) refers to the communication from the BS to the UE, and the uplink (or reverse link) refers to the communication from the UE to the BS. As will be described in more detail herein, a BS can be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a 5G BS, a 5G Node B, and / or the like.

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, and even global level. 5G, which can also be referred to as New Radio (NR), is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). 5G is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDM with cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread ODFM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and 5G technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies.

[0006] SUMMARY

[0007] In a wireless network, a base station can transmit a physical downlink control channel (PDCCH) multiple times repeatedly to improve reliability and / or robustness. For example, one PDCCH repetition technique can be to transmit one downlink control information (DCI) message in two search spaces associated with two control resource sets (CORESETs). In another PDCCH repetition technique, one DCI message can be transmitted in one CORESET associated with two transmission configuration indication (TCI) states (e.g., using two beams pointing in different directions). However, PDCCH repetition can create ambiguity in a case where a UE has to determine a default downlink or uplink beam for receiving or transmitting a data channel (e.g., a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH)) scheduled by the DCI message (e.g., because the DCI message does not have a TCI field).

[0008] For example, when a UE receives a DCI without a TCI field in a wireless network that does not support PDCCH repetition, the UE typically determines a default beam for receiving a PDSCH or transmitting a PUSCH scheduled by the DCI based on a TCI state, a quasi co-location (QCL) assumption, a search space, and / or other suitable parameters associated with a CORESET used to transmit the PDCCH. Accordingly, when a PDCCH is associated with multiple CORESETs and / or with one or more CORESETs associated with multiple TCI states, the UE can not be able to determine a beam to use for receiving a PDSCH or transmitting a PUSCH scheduled by the DCI in cases where the PDCCH does not indicate a downlink or uplink beam.

[0009] Some aspects described herein relate to techniques and apparatuses for determining a default downlink beam or a default uplink beam in cases where a PDCCH is associated with a repetition configuration that includes multiple CORESETs and / or a CORESET associated with multiple TCI states. For example, in some aspects, a PDCCH can be associated with multiple CORESETs and can non-repetitively schedule a PDSCH, in which case a UE can determine a default beam for the PDSCH based on a TCI state or a QCL assumption applied to one of the multiple CORESETs. In some aspects, in cases where the PDCCH includes a CORESET associated with multiple TCI states, a UE can determine a default beam for receiving a non-repetitive PDSCH based on one of the TCI states associated with the CORESET. Alternatively, in cases where the PDCCH repetitively schedules a PDSCH, a UE can map TCI states associated with different CORESETs and / or different TCI states associated with a CORESET to different sets of PDSCH reception occasions. Further, when a PDCCH schedules a PUSCH and includes a CORESET associated with multiple TCI states, a UE can determine a default beam based on one of the TCI states associated with the CORESET in cases where the PUSCH is not configured with repetition or based on a mapping of the TCI states associated with the CORESET to different sets of PUSCH transmission occasions in cases where the PUSCH is configured with repetition.

[0010] In some aspects, a method of wireless communication, performed by a UE, includes receiving, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; determining a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; and receiving the downlink data channel using the default beam.

[0011] In some aspects, a method of wireless communication, performed by a UE, includes receiving, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; determining a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; and receiving the downlink data channel using the default beam.

[0012] In some aspects, a UE includes one or more memories and one or more processors communicatively coupled to the one or more memories, the one or more processors configured to: receive, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; and receive the downlink data channel using the default beam.

[0013] In some aspects, a UE includes one or more memories and one or more processors communicatively coupled to the one or more memories, the one or more processors configured to: receive, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; and receive the downlink data channel using the default beam.

[0014] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to receive, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; and receive the downlink data channel using the default beam.

[0015] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to receive, from a base station, DCI scheduling an uplink data channel, wherein the DCI is associated with a repetition configuration including a CORESET associated with a plurality of TCI states; determine a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET; and transmit the uplink data channel using the default beam.

[0016] In some aspects, an apparatus for wireless communication includes means for receiving, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; means for determining a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; and means for receiving the downlink data channel using the default beam.

[0017] In some aspects, a method for wireless communication includes receiving, from a base station, a DCI scheduling an uplink data channel, wherein the DCI is associated with a repetition configuration including a CORESET associated with a plurality of TCI states; determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET; and transmitting the uplink data channel using the default beam.

[0018] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as substantially described in connection with the drawings and as illustrated in the figures and described in the specification.

[0019] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed conception and specific examples can be readily utilized as bases for modifying or designing other structures for carrying out the same purposes of the disclosure. Such equivalent constructions are not to be regarded as a departure from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and their method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 is a diagram illustrating an example of a wireless network.

[0022] Figure 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network.

[0023] Figure 3 is a diagram illustrating an example of physical channels and reference signals in a wireless network.

[0024] Figure 4 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network.

[0025] Figure 5 is a diagram illustrating an example resource structure for wireless communication.

[0026] Figures 6A-6B is a diagram illustrating an example of downlink and uplink communications configured with multiple repetitions.

[0027] Figures 7A-7Dis a diagram illustrating an example associated with determining a default downlink beam for a downlink control channel with repetition configuration.

[0028] Figures 8A-8B is a diagram illustrating an example associated with determining a default uplink beam for a downlink control channel with repetition configuration.

[0029] Figures 9-10 is a flowchart of an example wireless communication method.

[0030] Figure 11 is a diagram of an example device for wireless communication.

[0031] Figure 12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0032] Figure 13 is a diagram of an example device for wireless communication.

[0033] Figure 14 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0034] DETAILED DESCRIPTION

[0035] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without

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

[0037] By way of example, an element, or any portion of an element, or any combination of elements can be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

[0039] It should be noted that while aspects can be described herein using terminology commonly associated with a 5G or NR radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0040] Figure 1is a diagram illustrating a wireless network 100, in which aspects of the disclosure can be practiced. The wireless network 100 can be or can include elements of a 5G (NR) network and / or a LTE network, among other examples. The wireless network 100 can include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and can also be referred to as an eNodeB, gNB, 5G NB, access point, transmit receive point (TRP), etc. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0041] BSs can be macro BSs, pico BSs, femto BSs, and / or other types of BSs. A macro BS can cover a relatively large geographic area (e.g., 100s of feet to 10s of kilometers in radius) and can allow unrestricted access to users with service subscriptions. A pico BS can cover a relatively small geographic area (e.g., a home) and can allow restricted access to users with service subscriptions. A femto BS can cover a relatively small geographic area (e.g., a home) and can allow restricted access to users with service subscriptions. Figure 1 In the example shown in FIG. 1, the BSs 110a can be macro BSs for the macro cells 102a, the BS 110b can be a pico BS for the pico cell 102b, and the BS 110c can be a femto BS for the femto cell 102c. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “5G BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0042] In some examples, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile BS. In some examples, the BSs can be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as a direct physical connection or a virtual network, using any suitable transmission medium) using any suitable transmission network.

[0043] Wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in FIG. 1, relay BS 1 lOd can communicate with macro BS 110a and UE 120d in furtherance of communication between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, a relay base station, a relay, or the like.

[0044] Wireless network 100 can be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference. For example, macro BSs can have a high transmit power level (e.g., 5 to 40 Watts), whereas pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 Watts).

[0045] A network controller 130 can couple to a set of BSs and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via a backhaul. The BSs can also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

[0046] UEs 120 (e.g., 120a, 120b, 120c) can be dispersed throughout wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE can be a cellular phone (e.g., 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0047] Some UEs can be considered Machine-Type Communication (MTC) devices, or evolved or enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network) via wired or wireless communication links, for example. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components, memory components, etc.

[0048] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, 5G RAT networks can be deployed.

[0049] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary). For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this scenario, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as performed by base station 110.

[0050] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided based on frequency or wavelength into various classes, bands, channels, and so on. For example, devices of wireless network 100 can communicate using an operating band having a first frequency range (FR1), which can span from 410 MHz to 7.125 GHz, and / or can communicate using an operating band having a second frequency range (FR2), which can span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 is often referred to as a “millimeter wave” band despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. Thus, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or like references, if used herein, can broadly represent frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or like references, if used herein, can broadly represent frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 can be modified, and techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, the base station 110 can transmit, to the UE 120, a physical downlink control channel (PDCCH) carrying downlink control information (DCI) for dynamically scheduling a downlink data channel (e.g., a physical downlink shared channel (PDSCH)) or an uplink data channel (e.g., a physical uplink shared channel (PUSCH)). Further, in some cases, the base station 110 can repeatedly transmit the PDCCH to improve reliability and / or robustness. For example, one PDCCH repetition technique can be to transmit the DCI in two search spaces associated with two control resource sets (CORESETs). In another PDCCH repetition technique, the DCI can be transmitted in one CORESET associated with two transmission configuration indication (TCI) states (e.g., using a single frequency network (SFN) scheme in which two beams are associated with a same time-frequency resource, or using a non-SFN scheme in which two beams are associated with different time-frequency resources in a same CORESET). In some aspects, the UE 120 can be configured to follow one or more rules to determine a default beam for receiving a PDSCH in cases in which a scheduling DCI lacks a beam indication and / or to determine a default beam for transmitting a PUSCH in cases in which the PUSCH is not associated with an uplink TCI state or any spatial relation.

[0052] For example, in some aspects, the PDCCH can be associated with multiple CORESETs and can not repeatedly schedule a PDSCH, in which case the UE 120 can determine a default beam for the PDSCH based on a TCI state or quasi co-location (QCL) assumption applied to one of the multiple CORESETs. Additionally or alternatively, in cases in which the PDCCH includes one CORESET associated with multiple TCI states, the UE 120 can determine a default beam for receiving the non-repeated PDSCH based on one of the TCI states associated with the CORESET. Alternatively, in cases in which the PDCCH repeatedly schedules the PDSCH, the UE 120 can map TCI states associated with different CORESETs and / or different TCI states associated with one CORESET to different sets of PDSCH reception occasions. Further, when the PDCCH schedules the PUSCH and includes one CORESET associated with multiple TCI states, the UE 120 can determine a default beam based on one of the TCI states associated with the CORESET when the PUSCH is not configured with repetition or based on a mapping of the TCI states associated with the CORESET to different sets of PUSCH transmission occasions when the PUSCH is configured with repetition.

[0053] As indicated above, Figure 1are provided as examples. Other examples can differ from what is described with respect to at least one of the described examples. Figure 1

[0054] Figure 2 is a diagram illustrating an example 200 in which a base station 110 is in communication with UEs 120 in a wireless network 100. A base station 110 can be equipped with T antennas 234a through 234t, and a UE 120 can be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.

[0055] At the base station 110, a transmit processor 220 can receive data from a data source 212 for one or more UEs, can select one or more modulation and coding schemes (MCSs) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. The transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 can also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS), a phase-tracking reference signal (PTRS), and / or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t can be transmitted via T antennas 234a through 234t, respectively.

[0056] ​At the UE 120, the antennas 252a through 252r can receive the downlink signals from the base station 110 and / or other base stations and can provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive (RX) processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some aspects, one or more components of UE 120 can be included in a housing 284.

[0057] The network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the base station 110 via the communication unit 294.

[0058] Antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included in one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays, among other examples. An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements. An antenna panel, antenna group, antenna element set, and / or antenna array can include a set of co-planar antenna elements and / or a set of non-co-planar antenna elements. An antenna panel, antenna group, antenna element set, and / or antenna array can include antenna elements within a single housing and / or antenna elements within multiple housings. An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of a transceiver 270). Figure 2 An antenna panel, antenna group, antenna element set, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of a transceiver 270).

[0059] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 254) of the UE 120 can be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver can include any combination of antenna(s) 252, modulators and / or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform any of the methods described herein.

[0060] At base station 110, the uplink signals from UE 120 and other UEs can be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and to controller / processor 240 for control information. Base station 110 can include communication unit 244 and communicate to network controller 130 via communication unit 244. Base station 110 can include a scheduler 246 to schedule UEs 120 for downlink and / or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 232) of the base station 110 can be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver can include any combination of antenna(s) 234, modulators and / or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform any of the methods described herein. The scheduler 246 can schedule UEs for data transmissions on the downlink and / or uplink.

[0061] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or Figure 2Any other component may perform one or more techniques associated with determining the default downlink or uplink beam for a downlink control channel with a duplicated configuration, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 9 Method 900 Figure 10 The operation of method 1000 and / or other methods as described herein. Memory 242 and 282 may store data and program code for use by BS 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include: a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed by one or more processors of base station 110 and / or UE 120 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation), the one or more processors, UE 120, and / or base station 110 may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 9 Method 900 Figure 10 Method 1000, and / or other methods described herein. In some aspects, the execution instructions may include run instructions, translate instructions, compile instructions, and / or interpret instructions, etc.

[0062] In some aspects, UE 120 includes: means for receiving a DCI (Distributed Control Interface) for scheduling a downlink data channel from a base station, wherein the DCI is associated with a repetition configuration, the repetition configuration including one or more of the following: a plurality of CORESETs or a plurality of TCI states associated with a CORESET; means for determining a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined at least in part based on the plurality of CORESETs or the plurality of TCI states associated with the CORESET; or means for receiving the downlink data channel using the default beam. Means for UE 120 to perform the operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0063] Additionally or alternatively, in some aspects, UE 120 includes means for receiving, from a base station, DCI scheduling an uplink data channel, wherein the DCI is associated with a repetition configuration including a CORESET associated with a plurality of TCI states, means for determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET, or means for transmitting the uplink data channel using the default beam. The means for UE 120 to perform operations described herein can include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0064] As indicated above, Figure 2 are provided by way of example. Other examples can differ from those described Figure 2 without departing from the spirit of the disclosure.

[0065] Figure 3 is a diagram illustrating an example 300 of physical channels and reference signals in a wireless network. As shown in Figure 3 the downlink channels and the downlink reference signals can carry information from a base station 110 to a UE 120, and the uplink channels and the uplink reference signals can carry information from a UE 120 to a base station 110.

[0066] As shown, the downlink channels can include a PDCCH carrying DCI, a PDSCH carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, among other examples. In some aspects, a PDSCH communication can be scheduled by a PDCCH communication. As further shown, the uplink channels can include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a PUSCH carrying uplink data, or a physical random access channel (PRACH) used for initial network access, among other examples. In some aspects, UE 120 can transmit acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in UCI on a PUCCH and / or a PUSCH.

[0067] As further shown, downlink reference signals can include synchronization signal blocks (SSBs), channel state information (CSI) reference signals (CSI-RSs), DMRSs, or PTRSs, among other examples. As also shown, uplink reference signals can include sounding reference signals (SRSs), DMRSs, or PTRSs, among other examples.

[0068] An SSB can carry information used for initial network acquisition and synchronization, such as a PSS, an SSS, a PBCH, and / or a PBCH DMRS. An SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, a base station 110 can transmit multiple SSBs on multiple corresponding beams, and the SSBs can be used for beam selection.

[0069] A CSI-RS can carry information used for downlink channel estimation (e.g., downlink CSI acquisition), which can be used for scheduling, link adaptation, or beam management, among other examples. A base station 110 can configure a set of CSI-RSs for a UE 120, and the UE 120 can measure the configured set of CSI-RSs. Based at least in part on these measurements, the UE 120 can perform channel estimation and can report channel estimation parameters (e.g., in a CSI report) to the base station 110, such as a CQI, a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or an RSRP, among other examples. The base station 110 can use the CSI report to select transmission parameters for downlink communications to the UE 120, such as a number of transmission layers (e.g., a rank), a precoding matrix (e.g., a precoder), an MCS, or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

[0070] A DMRS can carry information used to estimate a radio channel for demodulating an associated physical channel (e.g., a PDCCH, a PDSCH, a PBCH, a PUCCH, or a PUSCH). The design and mapping of a DMRS can be specific to the physical channel for which the DMRS is used for estimation. A DMRS is UE-specific, can be beamformed, can be confined in scheduled resources (e.g., rather than being transmitted over a wideband), and can be transmitted only when necessary. As shown, DMRSs are used for both downlink communications and uplink communications.

[0071] PTRS can carry information used to compensate for oscillator phase noise. Generally, phase noise increases as the oscillator carrier frequency increases. Thus, PTRS can be utilized at high carrier frequencies, such as millimeter wave frequencies, to mitigate phase noise. PTRS can be used to track the phase of a local oscillator and enable suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0072] SRS can carry information used for uplink channel estimation, which can be used for scheduling, link adaptation, precoder selection or beam management, among other examples. A base station 110 can configure a UE 120 with one or more SRS resource sets, and the UE 120 can transmit SRS on the configured SRS resource sets. An SRS resource set can have a configured usage, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operations, uplink beam management, among other examples. The base station 110 can measure the SRS, can perform channel estimation based at least in part on the measurements, and can use the SRS measurements to configure communications with the UE 120.

[0073] As indicated above, Figure 3 are provided as examples. Other examples can differ from what is described with respect to at least one of the Figure 3 described examples.

[0074] Figure 4 is a diagram illustrating an example 400 of a base station communicating with a UE using beams. As shown in Figure 4 the base station 110 and the UE 120 can communicate with each other in a wireless network (e.g., the wireless network 100) using beams. The base station 110 can transmit to UEs 120 that are within a coverage area of the base station 110. The base station 110 and the UE 120 can be configured for beamformed communications, where the base station 110 can transmit in the direction of the UE 120 using a directional BS transmit beam and the UE 120 can receive the transmission using a directional UE receive beam. Each BS transmit beam can have an associated beam ID, beam direction, or beam symbol, among other examples. The base station 110 can transmit downlink communications via one or more BS transmit beams 405.

[0075] The UE 120 can attempt to receive downlink transmissions via one or more UE receive beams 410, which can be configured at the receive circuitry of the UE 120 using different beamforming parameters. The UE 120 can identify a particular BS transmit beam 405 (shown as BS transmit beam 405-A) and a particular UE receive beam 410 (shown as UE receive beam 410-A) that provide relatively good performance (e.g., that have the best channel quality of different measured combinations of BS transmit beams 405 and UE receive beams 410). In some examples, the UE 120 can transmit an indication of which BS transmit beam 405 the UE 120 identifies as a preferred BS transmit beam, which the base station 110 can select for transmissions to the UE 120. Thus, the UE 120 can obtain and maintain a beam pair link (BPL) with the base station 110 for downlink communications (e.g., the combination of BS transmit beam 405-A and UE receive beam 410-A), which can be further refined and maintained according to one or more established beam refinement procedures.

[0076] A downlink beam, such as a BS transmit beam 405 or a UE receive beam 410, can be associated with a TCI state. The TCI state can indicate a directionality or characteristics of the downlink beam, such as one or more QCL properties of the downlink beam. The QCL properties can include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial receive parameter, among other examples. In some examples, each BS transmit beam 405 can be associated with an SSB, and the UE 120 can indicate a preferred BS transmit beam 405 by transmitting an uplink transmission in resources of an SSB associated with the preferred BS transmit beam 405. A particular SSB can have an associated TCI state (e.g., for antenna port or for beamforming). In some examples, the base station 110 can indicate a downlink BS transmit beam 405 based at least in part on an antenna port QCL property that can be indicated by the TCI state. For different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial receive parameter, among other examples), a TCI state can be associated with a set of downlink reference signals (e.g., SSBs, and aperiodic, periodic, or semi-persistent CSI-RS). In cases where a QCL type indicates a spatial receive parameter, the QCL type can correspond to an analog receive beamforming parameter of a UE receive beam 410 at the UE 120. Thus, the UE 120 can select a corresponding UE receive beam 410 from a set of BPLs based at least in part on the BS transmit beam 405 indicated by the base station 110 via TCI indication.

[0077] The base station 110 can maintain a set of activated TCI states for downlink data channel transmissions and a set of activated TCI states for downlink control channel transmissions. The set of activated TCI states for downlink data channel transmissions can correspond to beams that the base station 110 uses for downlink transmissions on PDSCH. The set of activated TCI states for downlink control channel communications can correspond to beams that the base station 110 can use for downlink transmissions on PDCCH or in CORESET. The UE 120 can also maintain a set of activated TCI states for receiving downlink data channel transmissions and CORESET transmissions. If a TCI state is activated for the UE 120, the UE 120 can have one or more antenna configurations based at least in part on the TCI state, and the UE 120 can not have to reconfigure the antenna or antenna weighting configurations. In some examples, the set of activated TCI states (e.g., activated PDSCH TCI states and activated CORESET TCI states) for the UE 120 can be configured by a configuration message, such as a radio resource control (RRC) message.

[0078] Similarly, for uplink communications, a UE 120 can transmit in the direction of a base station 110 using a directional UE transmit beam, and the base station 110 can receive the transmission using a directional BS receive beam. Each UE transmit beam can have an associated beam ID, beam direction, or beam symbol, among other examples. A UE 120 can transmit uplink communications via one or more UE transmit beams 415.

[0079] The base stations 110 can receive uplink communications via one or more BS receive beams 420. The base stations 110 can identify a particular UE transmit beam 415 (shown as UE transmit beam 415-A) and a particular BS receive beam 420 (shown as BS receive beam 420-A) that provide relatively good performance (e.g., that have the best channel quality of different measured combinations of UE transmit beams 415 and BS receive beams 420). In some examples, the base stations 110 can transmit an indication of which UE transmit beam 415 the base stations 110 identify as a preferred UE transmit beam for the base stations 110 to use for transmissions from the UE 120. Thus, the UE 120 and the base stations 110 can obtain and maintain a BPL for uplink communications (e.g., the combination of UE transmit beam 415-A and BS receive beam 420-A), which can be further refined and maintained according to one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam 415 or a BS receive beam 420, can be associated with a spatial relation. The spatial relation can indicate a directionality or characteristic of the uplink beam, similar to one or more QCL properties as described above. Additionally or alternatively, in a wireless network that supports unified downlink and uplink TCI framework, an uplink beam can be associated with an uplink TCI state or a joint downlink and uplink TCI state (e.g., where a BPL for downlink communications and a BPL for uplink communications are associated with a same SSB).

[0080] As indicated above, Figure 4 are provided by way of example. Other examples can differ from Figure 4 the examples described.

[0081] Figure 5 is a diagram illustrating an example resource structure 500 for wireless communication, in accordance with various aspects of the present disclosure. The resource structure 500 shows examples of various resource groups described herein. As shown, the resource structure 500 can include a subframe 505. The subframe 505 can include a number of slots 510. While the resource structure 500 is shown including two (2) slots per subframe, a different number of slots (e.g., 4 slots, 8 slots, 16 slots, 32 slots, etc.) can be included in a subframe. In some aspects, different types of transmission time intervals (TTIs) can be used in addition to or instead of subframes and / or slots. The slots 510 can include a number of symbols 515, such as fourteen (14) symbols per slot.

[0082] The potential control region of the slot 510 can be referred to as a CORESET 520 and can be structured to support efficient use of resources, such as by flexibly configuring or reconfiguring resources of the CORESET 520 for one or more PDCCHs, one or more PDSCHs, and / or the like. In some aspects, the CORESET 520 can occupy the first symbol 515 of the slot 510, the first two symbols 515 of the slot 510, or the first three symbols 515 of the slot 510. As such, the CORESET 520 can include a number of resource blocks (RBs) in the frequency domain and one, two, or three symbols 515 in the time domain. In 5G, the number of resources included in the CORESET 520 can be flexibly configured, such as by using RRC signaling to indicate a frequency domain region (e.g., number of resource blocks) and / or a time domain region (e.g., number of symbols) of the CORESET 520.

[0083] As illustrated, the symbol 515 including the CORESET 520 can include one or more control channel elements (CCEs) 525, shown as two CCEs 525 spanning a portion of the system bandwidth as an example. The CCEs 525 can include DCI that is used to provide control information for wireless communications (e.g., to schedule PDSCH transmissions from a base station to a UE or PUSCH transmissions from a UE to a base station). The base station can transmit the DCI during multiple CCEs 525 (as shown), where the number of CCEs 525 used for the transmission of the DCI represents an aggregation level (AL) used by the base station for the transmission of the DCI. In Figure 5 As an example, an aggregation level of two is shown, which corresponds to two CCEs 325 in the slot 510. In some aspects, different aggregation levels can be used, such as 1, 2, 4, 8, 16, and / or the like.

[0084] Each CCE 525 can include a fixed number of resource element groups (REGs) 530, shown as 6 REGs 530, or can include a variable number of REGs 530. In some aspects, the number of REGs 530 included in the CCE 525 can be specified by a REG bundling size. The REG 530 can include one resource block, which can include 12 resource elements (REs) 535 within a symbol 515. The resource element 535 can occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0085] A search space can include all possible locations (e.g., in time and / or frequency) where a PDCCH can be located. A CORESET 520 can include one or more search spaces, such as a UE-specific search space, a group-common search space, and / or a common search space. A search space can indicate a set of CCE locations where a UE can find a PDCCH that can be potentially used to transmit control information to the UE. The possible locations of a PDCCH can depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group-common PDCCH (e.g., for multiple UEs), an aggregation level being used, etc. A possible location of a PDCCH (e.g., in time and / or frequency) can be referred to as a PDCCH candidate, and a set of all possible PDCCH locations at an aggregation level can be referred to as a search space. For example, a set of all possible PDCCH locations for a particular UE can be referred to as a UE-specific search space. Similarly, a set of all possible PDCCH locations across all UEs can be referred to as a common search space. A set of all possible PDCCH locations for a particular group of UEs can be referred to as a group-common search space. One or more search spaces across aggregation levels can be referred to as a search space (SS) set.

[0086] A CORESET 520 can be interleaved or non-interleaved. An interleaved CORESET 520 can have a CCE-to-REG mapping such that adjacent CCEs are mapped to dispersed REG bundles (e.g., adjacent CCEs are not mapped to consecutive REG bundles of the CORESET 520) in the frequency domain. A non-interleaved CORESET 520 can have a CCE-to-REG mapping such that all CCEs of the CORESET 520 are mapped to consecutive REG bundles (e.g., in the frequency domain).

[0087] As indicated above, Figure 5 is provided by way of example. Other examples can differ from what is described with respect to at least one of the Figure 5 described examples.

[0088] Figures 6A-6B is a diagram illustrating an example 600 of configuring downlink and uplink communications with multiple repetitions. For example, as shown in Figures 6A-6B one or more communications can be configured to be transmitted with multiple repetitions (e.g., a same transport block transmitted multiple times) to improve reliability and / or robustness of the one or more communications.

[0089] For example, as shown in Figure 6A, at 610, the base station can transmit and the UE can receive multiple repetitions of a PDCCH carrying a DCI used to schedule the PDSCH and indicate the PUCCH resources to be used for transmission, including Hybrid Automatic Repeat Request (HARQ) feedback on the PDSCH, which includes ACK or NACK for the PDSCH. In the illustrated example, there may be up to two (2) linked PDCCH candidates, whereby the PDCCH can be associated with a repetition configuration in which one DCI message is transmitted in two search spaces associated with two CORESETs. For example, as Figure 6A As shown, the base station transmits the first CORESET (CORESET1) in the first search space (SS1) and the second CORESET (CORESET2) in the second search space (SS2).

[0090] In alternative, such as Figure 6B As shown in Figure 620, the base station can transmit multiple PDCCH repetitions according to the SFN configuration. For example, when the PDCCH is associated with an SFN repetition configuration, the base station transmits DCI messages in a single CORESET using multiple TCI states (e.g., using different downlink beams associated with different antenna panels and / or different TRPs, etc.). Furthermore, in Figures 6A-6B In this process, the PDSCH scheduled by the PDCCH and the PUCCH including HARQ feedback for the PDSCH are repeatedly transmitted to improve the reliability and / or robustness of the PDSCH and PUCCH. Furthermore, it will be appreciated that the same or similar PDCCH repetition techniques can be applied in cases where multiple PDCCHs repeatedly carry DCI for scheduling PUSCHs that can be associated with a single transmission timing or multiple repetitions.

[0091] Accordingly, as described herein, a base station can transmit multiple repetitions of the PDCCH to improve the reliability and / or robustness of the DCI carried in the PDCCH. For example, transmitting a DCI message multiple times using multiple CORESETs associated with different search spaces (e.g., in a non-SFN configuration) and / or multiple TCI states associated with a CORESET (e.g., in an SFN configuration) reduces the likelihood of communication loss due to PDCCH transmission interruptions on a particular link (e.g., due to objects or other obstacles physically blocking the transmission path of a particular link and / or due to interference with a particular link caused by other communications). Furthermore, in some cases, the base station can change one or more transmission parameters when transmitting different repetitions of the PDCCH. For example, in Figure 6AIn the non-SFN repetition configuration shown, the base station can use different CORESETs associated with different search spaces and / or different CORESETs at different frequencies within the search space to transmit different PDCCH repetitions to avoid potential interference and / or obstruction that may affect different PDCCH repetitions at specific frequencies. Additionally or alternatively, in Figure 6B In the SFN repetition configuration shown, the base station can simultaneously transmit different PDCCH repetitions in a CORESET using different TCI states associated with different beam directions (e.g., using the same time and frequency resources) to avoid potential interference and / or obstruction that might affect different PDCCH repetitions in a specific beam direction. However, in situations where the UE has to determine the default downlink or uplink beam for receiving or transmitting data channels (e.g., PDSCH or PUSCH scheduled by PDCCH) and / or control channels (e.g., PUCCH including UCI, such as HARQ feedback for PDSCH scheduled by PDCCH), transmitting PDCCH repetitions may cause ambiguity.

[0092] For example, when a UE is connected to a wireless network, the UE can be configured with a default TCI state that indicates a default beam. In some cases, an RRC setting (e.g., a TCIPresentInDCI (TCI present in DCI) parameter) can be established after the UE has connected to the wireless network to enable or disable DCI-based beam selection or beam indication (e.g., the RRC setting can indicate whether a subsequent DCI message will include a TCI field to indicate a TCI state for PDSCH, PUSCH, and / or PUCCH). Accordingly, in cases where the RRC setting indicates that DCI-based beam selection or beam indication is disabled (e.g., the TCIPresentinDCI parameter is set to disable), the UE uses the default beam for any DCI that schedules future data transmissions. However, existing techniques for determining a default PDSCH, PUSCH, and / or PUCCH beam are generally limited to cases where a PDCCH is transmitted without repetition. For example, in cases where a DCI that schedules a PDSCH is associated with a DCI format that does not have a TCI field to indicate a TCI state for the PDSCH, the default TCI state for the PDSCH is the TCI state associated with a CORESET for the DCI that schedules the PDSCH. Similarly, in cases where a DCI schedules a PUSCH transmission by a UE and the UE is not configured with a PUCCH resource on an active uplink bandwidth part, the default uplink beam is determined based at least in part on a QCL assumption associated with a CORESET having a lowest identifier on an active downlink bandwidth part. Accordingly, in cases where a PDCCH is associated with a repetition configuration (e.g., one DCI is transmitted in multiple CORESETs associated with respective search spaces and / or in one or more CORESETs associated with multiple TCI states), the UE can not be able to determine a default beam for receiving a PDSCH scheduled by the DCI and / or transmitting a PUSCH scheduled by the DCI because there can be multiple CORESETs and / or TCI states associated with the scheduling DCI.

[0093] Some aspects described herein relate to techniques and apparatus for determining a default downlink beam or default uplink beam when a PDCCH is associated with a duplicate configuration (which includes multiple CORESETs and / or a CORESET associated with multiple TCI states). For example, in some aspects, a PDCCH may be associated with multiple CORESETs and PDSCHs may be scheduled non-repeatingly. In this case, the UE may determine the default beam for the PDSCH based on a TCI state or QCL assumption applied to one of the multiple CORESETs. In some aspects, where the PDCCH includes a CORESET associated with multiple TCI states, the UE may determine the default beam for receiving non-repeating PDSCHs based on one of the TCI states associated with that CORESET. Alternatively, in cases where the PDCCH is scheduled non-repeatingly, the UE may map TCI states associated with different CORESETs and / or different TCI states associated with a CORESET to different sets of PDSCH reception opportunities. Furthermore, when the PDCCH schedules the PUSCH and includes a CORESET associated with multiple TCI states, the UE can determine the default beam based on one of the TCI states associated with the CORESET in the case where the PUSCH is not reconfigured, or based on a mapping from the TCI states associated with the CORESET to different sets of PUSCH transmission opportunities in the case where the PUSCH is reconfigured.

[0094] As indicated above, Figures 6A-6B This is provided as an example. Other examples may differ from the one provided. Figures 6A-6B The example described.

[0095] Figures 7A-7D This is a diagram illustrating the association of example 700 with determining the default downlink beam for a downlink control channel with a duplicated configuration. For example, as referenced herein... Figures 7A-7D As described, the downlink control channel can be a PDCCH transmitted by a base station (e.g., base station 110) to a UE (e.g., UE 120) to schedule a downlink data channel (e.g., PDSCH). Furthermore, as described herein, the PDSCH can be scheduled by a DCI format in which a TCI field is absent (e.g., the PDCCH does not include a downlink beam indication), and the time offset between the reception of the scheduler DCI and the PDSCH scheduled by the DCI can satisfy (e.g., be equal to or exceed) a threshold that defines the minimum number of symbols required for the UE to perform PDCCH reception and apply the spatial QCL information received in the scheduler DCI to correctly receive and process the PDSCH.

[0096] Accordingly, as described in further detail herein, Figures 7A-7D The example 700 shown in FIG. 7 is applicable to one or more scenarios in which a PDCCH scheduling a PDSCH is transmitted according to a repetition configuration, the PDSCH is scheduled by a DCI format that is absent a TCI field, and the UE has sufficient time to decode the scheduling DCI and determine and apply spatial QCL information to correctly receive and process the PDSCH (e.g., a time offset between reception of the scheduling DCI and the PDSCH scheduled by the DCI is equal to or exceeds a threshold, which can be defined in a timeDurationForQCL (time duration for QCL) parameter based on a reported UE capability).

[0097] For example, as Figure 7A shown in FIG. 7, at 710, the base station can transmit and the UE can receive a PDCCH carrying a DCI for scheduling a PDSCH associated with one or more reception occasions (e.g., the PDSCH can be un-repetition configured, as Figures 7A-7B shown in FIG. 6, or the PDSCH can be repetition configured, as Figures 7C-7D shown in FIG. 7). Further, as described herein, the PDCCH is associated with a repetition configuration to boost reliability and / or robustness of the PDCCH. For example, as described herein with reference to Figure 7A and 7C , the PDCCH can be transmitted according to a non-SFN repetition configuration, in which one DCI is transmitted in multiple CORESETs associated with multiple respective search spaces. Alternatively, as described herein with reference to Figure 7B and 7D , the PDCCH can be transmitted according to an SFN repetition configuration, in which one DCI is transmitted in one CORESET associated with multiple TCI states (e.g., using different beams and same time-frequency resources).

[0098] As Figure 7AAs further shown in 712, the UE can determine a default downlink beam (e.g., a default PDSCH reception beam) according to the repetition configuration of the PDCCH based at least in part on determining that one or more conditions are satisfied. For example, the UE can determine the default downlink beam according to the repetition configuration of the PDCCH based at least in part on the DCI scheduling the PDSCH not having a TCI field or otherwise lacking a beam indication for the PDSCH and a time offset between reception of the scheduling DCI and the corresponding PDSCH satisfying a threshold defining a minimum number of symbols needed for the UE to perform PDCCH reception and apply spatial QCL information received in the scheduling DCI to correctly receive and process the PDSCH (e.g., the time offset being equal to or exceeding a timeDurationForQCL parameter). In some aspects, based at least in part on determining that one or more conditions are satisfied, the UE can apply one or more rules to determine the default downlink reception beam depending on whether the PDSCH is configured with repetition and / or depending on whether the PDCCH is associated with multiple CORESETs associated with different search spaces or a CORESET associated with a different TCI state. As shown in 714, the UE can then receive the PDSCH using the default downlink reception beam.

[0099] For example, as Figure 7AAs shown in 720, the UE can determine a default downlink receive beam in a context in which the PDCCH repetition configuration includes multiple CORESETs associated with different search spaces and the PDSCH is configured with a single reception occasion (e.g., the PDCCH is associated with a non-SFN configuration and the PDSCH is not configured with repetition). In this case, the UE can determine the default downlink receive beam is associated with a TCI state or QCL assumption associated with one of the multiple CORESETs in the PDCCH repetition configuration in the case that the base station transmits a DCI scheduling the PDSCH in a different CORESET associated with a different search space and the scheduling DCI does not have a TCI field. For example, in some aspects, the default downlink receive beam can be associated with a TCI state or QCL assumption that is equivalent to a TCI state or QCL assumption of one of the multiple CORESETs with a lowest or highest CORESET identifier (ID), one of the multiple CORESETs with a lowest or highest CORESET pool identifier (ID), one of the multiple CORESETs associated with a search space with a lowest search space ID or a highest search space ID, one of the multiple CORESETs associated with a most recently monitored search space or an earliest monitored search space. In the case that the PDSCH is associated with an SFN configuration, the UE can determine multiple default downlink receive beams are associated with respective TCI states of the multiple CORESETs.

[0100] Accordingly, as Figure 7AAs shown in 720, if no duplicate PDSCH is configured to be scheduled by a DCI format without a TCI field, and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL, and if more than one CORESET is associated with the PDCCH transmission of the downlink DCI within the active bandwidth portion of the serving cell, then the UE assumes that the TCI state or QCL assumption for the PDSCH is equivalent to the lowest (or highest) CORESET ID among the CORESETs associated with the PDCCH transmission of the scheduled PDSCH, the lowest (or highest) search space ID of the CORESET ID associated with the PDCCH transmission of the scheduled PDSCH, and the latest (or earliest) monitored search space CORESET ID associated with the PDCCH transmission of the scheduled PDSCH. In the case where PDSCH is associated with SFN configuration, the UE can determine that multiple default downlink receive beams are associated with the corresponding TCI states of multiple CORESETs associated with the PDCCH transmission that schedules PDSCH.

[0101] In another example, such as Figure 7B As shown in 730 and 732, the UE can determine the default downlink receive beam in a context where the PDCCH is repeatedly configured to include a CORESET associated with multiple TCI states and the PDSCH is configured with a single receive timing (e.g., the PDCCH is associated with an SFN configuration and the PDSCH is not repeatedly configured). In this scenario, if the base station uses different beams associated with different TCI states to transmit the DCI of the scheduled PDSCH in a CORESET and the scheduled DCI does not have a TCI field, the UE can determine that the default downlink receive beam is associated with the TCI state associated with one or more of the multiple TCI states. For example, when the PDCCH repetition configuration includes a CORESET associated with multiple TCI states and the PDSCH is not configured to repetition, the TCI state applied by the UE to the default downlink receive beam can correspond to: the first (or second) TCI state among the multiple TCI states associated with the CORESET, the TCI state with the lowest (or highest) TCI ID among the multiple TCI states associated with the CORESET, and the TCI state in quasi-co-location (QCL) with the SSB having the lowest (or highest) index among the multiple TCI states associated with the CORESET. In the case where the PDSCH is associated with the SFN configuration, the UE can determine that multiple default downlink receive beams are associated with the corresponding TCI states of the CORESET that schedule the PDSCH.

[0102] Accordingly, as shown in Figure 7B At 730 and 732, if no PDSCH configured with any repetition is scheduled by a DCI format without a TCI field, and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or larger than the threshold timeDurationForQCL, the UE assumes the TCI state or QCL assumption for the PDSCH is equal to the one applied to the CORESET for PDCCH transmission within the active bandwidth part of the serving cell. If there are two TCI states associated with the CORESET, the TCI state to be applied is the first (or second) TCI ID among the two TCI states associated with the CORESET for PDCCH transmission, the lowest (or highest) TCI ID among the two TCI states associated with the CORESET for PDCCH transmission, the TCI ID among the two TCI states associated with the CORESET for PDCCH transmission that has the lowest (or highest) SSB index in QCL. In the case that the PDSCH is associated with SFN configuration, the UE can determine multiple default downlink receive beams are associated with the respective TCI states of the CORESET that schedules the PDSCH.

[0103] In another example, as shown in Figure 7C At 740 and 742, the UE can determine the default downlink receive beam in the context where the PDCCH repetition configuration includes multiple CORESETs associated with different search spaces and the PDSCH is configured with multiple reception occasions (e.g., the PDCCH is associated with non-SFN configuration and the PDSCH is configured with repetition). In this case, the UE can determine the default downlink receive beams for the first set of PDSCH reception occasions and the second set of PDSCH reception occasions in the case that the base station transmits the DCI scheduling the PDSCH multiple times in different CORESETs associated with different search spaces and the scheduling DCI is not present with a TCI field. In other words, in the case that there are multiple PDSCH reception occasions, the UE can apply different default downlink receive beams in different sets of PDSCH reception occasions. For example, in the case that one of the DCIs is transmitted in two CORESETs associated with two search spaces, the UE can determine two default downlink receive beams to be applied in the two respective sets of PDSCH occasions.

[0104] For example, as shown at 740, the multiple PDSCH occasions can be associated with a cyclic mapping, where a first default downlink receive beam is used in a first PDSCH reception occasion, a second default downlink receive beam is used in a second PDSCH reception occasion, and this cyclic pattern continues in the presence of additional PDSCH reception opportunities. Alternatively, as shown at 742, the multiple PDSCH occasions can be associated with a sequential mapping, where a first default downlink receive beam is used in a first half of the PDSCH reception occasions, and a second default downlink receive beam is used in a second half of the PDSCH reception occasions. However, it will be appreciated that other suitable mappings can be used to determine the first set of PDSCH reception occasions and the second set of PDSCH reception occasions. For example, the first set of PDSCH reception occasions and the second set of PDSCH reception occasions can be determined according to a cyclic mapping (e.g., as shown at 740), a sequential mapping (e.g., as shown at 742), a DMRS code division multiplexing (CDM) group index, a time allocation portion, a frequency allocation portion, and / or other suitable information.

[0105] Accordingly, in cases where the DCI scheduling the PDSCH multiple times lacks beam indication and is associated with a non-SFN repetition configuration (e.g., multiple CORESETs associated with different search spaces), the UE can determine that the DMRS ports associated with the first set of PDSCH reception occasions are QCLed with one or more reference signals with respect to QCL parameters used for PDCCH QCL indication of one CORESET associated with the lowest CORESET ID among the CORESETs where the PDCCH transmissions schedule the PDSCH reception occasions, and the UE can further determine that the DMRS ports associated with the second set of PDSCH reception occasions are QCLed with one or more reference signals with respect to QCL parameters used for PDCCH QCL indication of one CORESET associated with the highest CORESET ID among the CORESETs where the PDCCH transmissions schedule the PDSCH reception occasions. Additionally or alternatively, the UE can determine that the DMRS ports for the first set of PDSCH reception occasions and the second set of PDSCH reception occasions are QCLed with one or more reference signals associated with a first CORESET associated with a first search space having a lowest search space identifier and a second CORESET associated with a second search space having a highest search space identifier among the CORESETs where the PDCCH transmissions schedule the PDSCH reception occasions, respectively. Additionally or alternatively, the UE can determine that the DMRS ports for the first set of PDSCH reception occasions and the second set of PDSCH reception occasions are QCLed with one or more reference signals associated with a first CORESET associated with a latest in time monitored search space and a second CORESET associated with an earliest in time monitored search space among the CORESETs where the PDCCH transmissions schedule the PDSCH reception occasions, respectively.

[0106] Accordingly, as Figure 7CAs shown in 740 and 742, if any of the PDSCHs configured with repetition are scheduled by a DCI format that does not have a TCI field and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL, and if more than one CORESET is associated with the PDCCH transmission of the downlink DCI within the active bandwidth part of the serving cell, the UE can assume that the DMRS ports of the first and second PDSCH occasion sets are QCLed with the reference signal with respect to the QCL parameter(s) used for the PDCCH QCL indication of the CORESET(s) associated with the PDCCH transmission: the lowest and highest search space CORESET ID in the CORESETs associated with the PDCCH transmission, the lowest and highest search space CORESET ID of the CORESETs associated with the PDCCH transmission, or the latest and earliest monitored search space CORESET ID of the CORESETs associated with the PDCCH transmission, where the first and second PDSCH occasion sets can be determined by the transmission time occasion, the DMRS CDM group index, the time allocation part, or the frequency allocation part in the cyclic or sequential mapping.

[0107] In another example, as Figure 7D As shown in 750 and 752, the UE can determine the default downlink receive beam in a context in which the PDCCH repetition configuration includes a CORESET associated with multiple TCI states and the PDSCH is configured with multiple reception occasions (e.g., the PDCCH is associated with SFN repetition configuration and the PDSCH is configured with repetition). In this case, the base station can transmit the DCI scheduling the PDSCH in a CORESET associated with one search space, as shown in 750, or the base station can transmit the DCI scheduling the PDSCH in a CORESET associated with multiple search spaces, as shown in 752. In either case, in the case that the scheduling DCI does not have a TCI field and the time offset between the reception of the scheduling DCI and the scheduled PDSCH satisfies the threshold, the UE can determine the default downlink receive beam for the first and second PDSCH reception occasion sets based on the SFN repetition configuration of the PDCCH. In other words, in the case that there are multiple PDSCH reception occasions, the UE can apply different default downlink receive beams in different PDSCH reception occasion sets, which can be determined based on the cyclic mapping, the sequential mapping, the DMRS CDM group index, the frequency allocation part, and / or other suitable information.

[0108] Accordingly, in cases where the DCI for repeatedly scheduling PDSCH lacks beam indication and the PDCCH associated with one CORESET is repeatedly configured with multiple TCI states, the UE can determine that the DMRS port associated with the first PDSCH reception timing set is in QCL with respect to the QCL parameters used for the PDCCH QCL indication for the first TCI state associated with the CORESET, and the UE can further determine that the DMRS port associated with the second PDSCH reception timing set is in QCL with respect to the QCL parameters used for the PDCCH QCL indication for the second TCI state associated with the CORESET, and the UE can also determine that the DMRS port for the first PDSCH reception timing set and the second PDSCH reception timing set is in QCL with respect to one or more reference signals respectively associated with the first TCI state associated with the lowest TCI identifier and the second TCI state associated with the highest TCI identifier. Additionally or alternatively, the UE can determine that the DMRS ports for the first and second PDSCH reception timing sets are in QCL with one or more reference signals respectively associated with the following: the first TCI state associated with the lowest TCI identifier and the second TCI state associated with the highest TCI identifier. Additionally or alternatively, the UE may determine that the DMRS port for the first PDSCH reception timing set and the second PDSCH reception timing set is in QCL with one or more reference signals respectively associated with the following: a first TCI state in QCL with the SSB having the lowest index and a second TCI state in QCL with the SSB having the highest index.

[0109] Accordingly, such as Figure 7D As shown in 750 and 752, if any duplicate PDSCHs are configured to be scheduled by a DCI format without a TCI field and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL, and if more than one CORESET is associated with the PDCCH transmission of the downlink DCI within the active bandwidth portion of the serving cell, then the UE may assume that the DMRS ports of the first PDSCH timing set and the second PDSCH timing set are in QCL with respect to the QCI parameters used for the PDCCH QCL indication of the CORESETs respectively associated with: the first and second TCI IDs of the two TCI states associated with the CORESET for PDCCH transmission, the lowest and highest TCI IDs of the two TCI states associated with the CORESET for PDCCH transmission, or the TCI ID of the two TCI states associated with the CORESET for PDCCH transmission that is in QCL with the lowest and highest SSB indices.

[0110] As indicated above, Figures 7A-7DProvided by way of example. Other examples can differ from what is described Figures 7A-7D without limitation.

[0111] Figures 8A-8B is a diagram illustrating an example 800 associated with determining a default uplink beam for a downlink control channel with repetition configuration. For example, as described herein with reference to Figures 8A-8B , a downlink control channel can be a PDCCH transmitted by a base station (e.g., base station 110) to a UE (e.g., UE 120) to schedule an uplink data channel (e.g., PUSCH). Further, as described herein, a PUSCH is scheduled by a DCI carried in a PDCCH, and the PUSCH is not associated with any uplink TCI state or spatial relation (e.g., the PUSCH is not associated with an uplink beam selection or beam indication). Accordingly, as described in further detail herein, Figures 8A-8B the example 800 shown in FIG. 8 is applicable to one or more scenarios in which a PDCCH schedules a PUSCH that is transmitted according to a repetition configuration, the PUSCH is not associated with an uplink TCI state or any spatial relation, and an upper layer parameter (e.g., enableDefaultBeamPL-ForPUSCH0-r16) for determining a default uplink transmit beam is enabled.

[0112] For example, as Figure 8A shown in FIG. 8, at 810, the base station can transmit and the UE can receive a PDCCH carrying a DCI for scheduling a PUSCH associated with one or more reception occasions (e.g., the PUSCH can be configured without repetition, as shown in Figure 8A , or the PUSCH can be configured with repetition, as shown in Figure 8B ). Further, as described herein, the PDCCH is associated with a repetition configuration to boost the reliability and / or robustness of the PDCCH. For example, as described herein with reference to Figure 8A and 8B , the PDCCH can be transmitted according to an SFN repetition configuration, where one DCI is transmitted in one CORESET associated with multiple TCI states (e.g., using different beams and same time-frequency resources).

[0113] As Figure 8AAs further shown in section 812, the UE can determine the default uplink beam (e.g., the default PUSCH transmit beam) based at least in part on the redundancy configuration of the PDCCH, based on the determination that one or more conditions are met. For example, in cases where the PUSCH is not associated with any uplink TCI state or spatial relationship, the UE can determine the default uplink beam based at least in part on the base station enabling upper-layer parameters for determining the default uplink beam based on the redundancy configuration of the PDCCH. In some aspects, based at least in part on the determination that one or more conditions are met, the UE can apply one or more rules to determine the default uplink transmit beam based on the redundancy configuration of the PDCCH, depending on whether the PUSCH is redundant or not. For example, one or more rules may generally be applicable in cases where the PDCCH is associated with a redundancy configuration that includes a CORESET associated with multiple TCI states. Accordingly, in some aspects, the UE can determine the default uplink beam based on one or more parameters associated with multiple TCI states. As shown at section 814, the UE can then use the default uplink transmit beam to transmit the PUSCH.

[0114] For example, such as Figure 8A As shown in Figure 820, the UE can determine the default uplink transmit beam in a context where the PDCCH is repeatedly configured to include a CORESET associated with multiple TCI states and the PDSCH is configured with a single receive timing (e.g., the PDCCH is associated with an SFN configuration and the PDSCH is not repeatedly configured). In this scenario, where the base station uses different beams associated with different TCI states to transmit the DCI of the scheduled PDSCH in a CORESET, the UE can determine that the default uplink transmit beam is associated with one or more of the multiple TCI states. For example, when the PDCCH is repeatedly configured to include a CORESET associated with multiple TCI states and the PUSCH is not repeatedly configured, the TCI state applied by the UE to the default uplink transmit beam can correspond to: the first TCI state among the multiple TCI states associated with the CORESET, the TCI state with the lowest TCI ID among the multiple TCI states associated with the CORESET, and the TCI state in the QCL with the SSB having the lowest index among the multiple TCI states associated with the CORESET.

[0115] Accordingly, such as Figure 8AAs shown in 820, for a PUSCH scheduled in DCI format on a cell, and with the upper-layer parameter for the default beam (e.g., enableDefaultBeamPL-ForPUSCH0-r16) set to "enabled", if it does not apply to any uplink TCI state or any spatial relationship (e.g., uplink resources, such as PUCCH or SRS resources), the UE can transmit the PUSCH with reference to a reference signal having a "QCL-Type D" corresponding to the QCL assumption of the CORESET with the lowest ID on the active downlink bandwidth portion of the cell. If a CORESET is configured with two TCI states, the applicable TCI state is the TCI state with the following TCI IDs: the first (or second) TCI ID of the two TCI states associated with the CORESET for PDCCH transmission, the lowest (or highest) TCI ID of the two TCI states associated with the CORESET for PDCCH transmission, or the TCI ID of the two TCI states associated with the CORESET for PDCCH transmission that is in the QCL with the lowest (or highest) SSB index.

[0116] In another example, such as Figure 8B As shown in 830 and 832, the UE can determine the default uplink transmit beam in a context where the PDCCH reconfiguration includes a CORESET associated with multiple TCI states and the PUSCH is configured with multiple receive opportunities (e.g., the PDCCH is associated with SFN reconfiguration and the PUSCH is reconfigured). In this scenario, the base station can transmit the DCI scheduling PDSCH in a CORESET associated with one search space, as shown in 830, or the base station can transmit the DCI scheduling PDSCH in CORESETs associated with multiple search spaces, as shown in 832. In either case, if the PUSCH is not associated with an uplink TCI state or spatial relationship, the UE can determine the default uplink transmit beam for a first PUSCH transmission opportunity set and a second PUSCH transmission opportunity set based on the SFN reconfiguration of the PDCCH. In other words, in the presence of multiple PDSCH transmission opportunities, the UE can apply different default uplink transmit beams in different PUSCH transmission opportunity sets. For example, in a scenario where one of the DCIs uses two beams for transmission (e.g., using different TCI states associated with a CORESET), the UE can determine the two default uplink transmit beams to be applied in the two corresponding PUSCH timing sets.

[0117] For example, as shown at 830, the multiple PUSCH occasions can be associated with a cyclic mapping, where a first default uplink transmit beam is used in a first PUSCH transmission occasion, a second default uplink transmit beam is used in a second PUSCH transmission occasion, and this cyclic pattern continues in the presence of additional PUSCH transmission opportunities. Alternatively, as shown at 832, the multiple PUSCH occasions can be associated with a sequential mapping, where a first default uplink transmit beam is used in a first half of the PUSCH transmission occasions, and a second default uplink transmit beam is used in a second half of the PUSCH transmission occasions. However, it will be appreciated that other suitable mappings can be used to determine the first set of PUSCH transmission occasions and the second set of PUSCH transmission occasions. For example, the first set of PUSCH transmission occasions and the second set of PUSCH transmission occasions can be determined according to a cyclic mapping (e.g., as shown at 830), a sequential mapping (e.g., as shown at 832), a DMRS CDM group index, a frequency allocation portion, and / or other suitable information.

[0118] Accordingly, in a case in which a PUSCH that is scheduled multiple times lacks a beam indication and a PDCCH that schedules the PUSCH is associated with a SFN repetition configuration (e.g., one CORESET is associated with multiple TCI states), a UE can determine that DMRS ports associated with a first set of PDSCH reception occasions are QCLed with one or more reference signals with respect to a QCL parameter used for PDCCH QCL indication of a first TCI state associated with the CORESET, and the UE can further determine that a first TCI state to be applied in a first set of PUSCH transmission occasions and a second TCI state to be applied in a second set of PUSCH transmission occasions correspond to the first TCI state and a second TCI state associated with the CORESET, respectively. Additionally or alternatively, the first TCI state to be applied in the first set of PUSCH transmission occasions and the second TCI state to be applied in the second set of PUSCH transmission occasions can correspond to a first TCI state associated with a lowest TCI identifier and a second TCI state associated with a highest TCI identifier, respectively.

[0119] Accordingly, as Figure 8BAs shown in 830 and 832, for PUSCH scheduled by DCI format on a cell and in case a higher layer parameter (e.g., enableDefaultBeamPL-ForPUSCH0-r16) for default beam is set to “enabled”, the UE can transmit the PUSCH with reference to a corresponding “QCL-TypeD” reference signal with QCL assumption of a CORESET with lowest ID on an active downlink bandwidth part of the cell if not applicable to any uplink TCI state or any spatial relation (e.g., uplink resource such as PUCCH or SRS resource). If the CORESET is configured with two TCI states, and the PUSCH transmission has a first and second set of transmission occasions (e.g., cyclic mapping or sequential mapping), the applicable TCI states associated with the first and second transmission occasions are the first and second TCI IDs associated with the CORESET and / or the lower and higher TCI IDs associated with the CORESET, respectively. The first set of PUSCH occasions and the second set of PUSCH occasions can be determined by cyclic mapping, sequential mapping, DMRS CDM group index, or transmission time occasion in a frequency allocation part.

[0120] As indicated above, Figures 8A-8B are provided by way of example. Other examples can differ from those described. Figures 8A-8B

[0121] Figure 9 is a flow diagram of an example wireless communication method 900. The method 900 can be performed, for example, by a UE (e.g., the UE 120).

[0122] At 910, the UE can receive, from a base station, DCI scheduling a downlink data channel, where the DCI is associated with a repetition configuration including one or more of: multiple CORESETs or multiple TCI states associated with a CORESET. For example, the UE (e.g., using reception component 1102 depicted in FIG. 11) can receive, from a base station, DCI scheduling a downlink data channel, where the DCI is associated with a repetition configuration including one or more of: multiple CORESETs or multiple TCI states associated with a CORESET, as described above in connection with, e.g., 710, 720, 730, 732, 740, 742, 750, and 752. Figure 11 At 910, the UE can receive, from a base station, DCI scheduling a downlink data channel, where the DCI is associated with a repetition configuration including one or more of: multiple CORESETs or multiple TCI states associated with a CORESET. For example, the UE (e.g., using reception component 1102 depicted in FIG. 11) can receive, from a base station, DCI scheduling a downlink data channel, where the DCI is associated with a repetition configuration including one or more of: multiple CORESETs or multiple TCI states associated with a CORESET, as described above in connection with, e.g., 710, 720, 730, 732, 740, 742, 750, and 752. Figures 7A-7D At 710, 720, 730, 732, 740, 742, 750, and 752, as described above. In some aspects, the downlink data channel is associated with a single reception occasion and the repetition configuration associated with the DCI includes the multiple CORESETs, as described above in connection with, e.g., 710, 720, 730, 732, 740, 742, 750, and 752. Figure 7A ​described. In some aspects, the downlink data channel is associated with a single reception occasion, and the repetition configuration associated with the DCI includes the CORESET associated with the multiple TCI states, as described above in connection with, for example Figure 7B described. In some aspects, the downlink data channel is configured with multiple reception occasions, and the repetition configuration associated with the DCI includes the multiple CORESETs, as described above in connection with, for example Figure 7C described. In some aspects, the downlink data channel is configured with multiple reception occasions, and the repetition configuration associated with the DCI includes the CORESET associated with the multiple TCI states, as described above in connection with, for example Figure 7D described.

[0123] At 920, the UE can determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple CORESETs or the multiple TCI states associated with the CORESET. For example, the UE (e.g., using determination component 1108, depicted in FIG. 11) can determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple CORESETs or the multiple TCI states associated with the CORESET, as described above in connection with, for example Figure 11 At 920, the UE can determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple CORESETs or the multiple TCI states associated with the CORESET. For example, the UE (e.g., using determination component 1108, depicted in FIG. 11) can determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple CORESETs or the multiple TCI states associated with the CORESET, as described above in connection with, for example Figures 7A-7D described in connection with, for example

[0124] In some aspects, as described above in connection with, for example Figure 7AAs described, the default beam is associated with: a TCI state or QCL assumption applied to a CORESET of the plurality of CORESETs having a lowest CORESET identifier. In some aspects, the default beam is associated with: a TCI state or QCL assumption applied to a CORESET of the plurality of CORESETs associated with a search space having a lowest search space identifier, or a TCI state or QCL assumption applied to a CORESET of the plurality of CORESETs associated with a search space having a highest search space identifier. In some aspects, the default beam is associated with: a TCI state or QCL assumption applied to a CORESET of the plurality of CORESETs associated with a latest monitored search space in time, or a TCI state or QCL assumption applied to a CORESET of the plurality of CORESETs associated with an earliest monitored search space in time. In some aspects, the default beam is associated with: a first TCI state and a second TCI state associated with a first CORESET and a second CORESET of the plurality of CORESETs, respectively, based at least in part on the downlink data channel having an SFN configuration.

[0125] In some aspects, as described above in connection with, for example Figure 7B As described, the default beam is associated with: a first TCI state of the plurality of TCI states associated with the CORESET. In some aspects, the default beam is associated with: a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the CORESET. In some aspects, the default beam is associated with: a TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the CORESET that is QCLed with a SSB having a lowest index. In some aspects, the default beam is associated with: a first TCI state and a second TCI state of the plurality of TCI states associated with the CORESET, based at least in part on the downlink data channel having an SFN configuration.

[0126] In some aspects, as described above in connection with, for example Figure 7CAs described, the multiple reception occasions include: a first set of reception occasions in which the default beam is associated with: a CORESET of the multiple CORESETs having a lowest CORESET identifier; and a second set of reception occasions in which the default beam is associated with: a CORESET of the multiple CORESETs having a highest CORESET identifier. In some aspects, the multiple reception occasions include: a first set of reception occasions in which the default beam is associated with: a CORESET of the multiple CORESETs associated with a search space having a lowest search space identifier; and a second set of reception occasions in which the default beam is associated with: a CORESET of the multiple CORESETs associated with a search space having a highest search space identifier. In some aspects, the multiple reception occasions include: a first set of reception occasions in which the default beam is associated with: a CORESET of the multiple CORESETs associated with a latest monitored search space in time; and a second set of reception occasions in which the default beam is associated with: a CORESET of the multiple CORESETs associated with an earliest monitored search space in time. In some aspects, the multiple reception occasions include at least a first set of reception occasions and a second set of reception occasions associated with a cyclic mapping, a sequential mapping, a DMRS CDM group index, or a frequency allocation portion.

[0127] In some aspects, as described above in connection with, e.g., FIG. 2, the default beam is associated with a CORESET of the multiple CORESETs based at least in part on a CORESET identifier of the CORESET, a search space identifier of a search space associated with the CORESET, a monitored search space in time, or a frequency allocation portion. Figure 7DAs described, the multiple reception occasions include: a first set of reception occasions in which the default beam is associated with: a first TCI state of the multiple TCI states associated with the CORESET, and a second set of reception occasions in which the default beam is associated with: a second TCI state of the multiple TCI states associated with the CORESET. In some aspects, the multiple reception occasions include: a first set of reception occasions in which the default beam is associated with: a lowest TCI identifier of TCI identifiers associated with the multiple TCI states associated with the CORESET; and a second set of reception occasions in which the default beam is associated with: a highest TCI identifier of the TCI identifiers associated with the multiple TCI states associated with the CORESET. In some aspects, the multiple reception occasions include: a first set of reception occasions in which the default beam is associated with: a first TCI identifier of the TCI identifiers associated with the multiple TCI states associated with the CORESET that is QCLed with a SSB having a lowest index; and a second set of reception occasions in which the default beam is associated with: a second TCI identifier of the TCI identifiers associated with the multiple TCI states associated with the CORESET that is QCLed with a SSB having a highest index.

[0128] At 930, the UE can receive the downlink data channel using the default beam. For example, the UE (e.g., using reception component 1102, depicted in FIG. 11) can receive the downlink data channel using the default beam, as described above in connection with, for example, 920. Figure 11 At 930, the UE can receive the downlink data channel using the default beam. For example, the UE (e.g., using reception component 1102, depicted in FIG. 11) can receive the downlink data channel using the default beam, as described above in connection with, for example, 920. Figures 7A-7D At 714, 720, 730, 732, 740, 742, 750, and 752.

[0129] Although Figure 9 An example of the method 900 is illustrated, but in some aspects, the method 900 can include more, fewer, or different blocks than those depicted in FIG. 9. Additionally, or alternatively, two or more blocks of the method 900 can be performed in parallel. Figure 9 An example of the method 900 is illustrated, but in some aspects, the method 900 can include more, fewer, or different blocks than those depicted in FIG. 9. Additionally, or alternatively, two or more blocks of the method 900 can be performed in parallel.

[0130] Figure 10 FIG. 10 is a flow diagram of an example wireless communication method 1000. The method 1000 can be performed by, for example, a UE (e.g., the UE 120).

[0131] At 1010, the UE can receive, from a base station, DCI scheduling an uplink data channel, where the DCI is associated with a repetition configuration including a CORESET associated with multiple TCI states. For example, the UE (e.g., using reception component 1102, depicted in FIG. 11) can receive, from a base station, DCI scheduling an uplink data channel, where the DCI is associated with a repetition configuration including a CORESET associated with multiple TCI states, as described above in connection with, for example, 910. Figure 13The reception component 1302 depicted in FIG. 13B can receive, from a base station, DCI scheduling an uplink data channel, where the DCI is associated with a repetition configuration including a CORESET associated with multiple TCI states, as described above in connection with, e.g., FIG. 10. Figures 8A-8B In some aspects, the uplink data channel is associated with a single transmission occasion, as described above in connection with, e.g., FIG. 10. Figure 8A In some aspects, the uplink data channel is configured with multiple transmission occasions, as described above in connection with, e.g., FIG. 10. Figure 8B

[0132] At 1020, the UE can determine a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple TCI states associated with the CORESET. For example, the UE (e.g., using determination component 1308 depicted in FIG. 13B) can determine a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple TCI states associated with the CORESET, as described above in connection with, e.g., FIG. 10. Figure 13 The determination component 1308 depicted in FIG. 13B can determine a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the multiple TCI states associated with the CORESET, as described above in connection with, e.g., FIG. 10. Figures 8A-8B In some aspects, the default beam is associated with: a first TCI state of the multiple TCI states associated with the CORESET, as described above in connection with, e.g., FIG. 10.

[0133] In some aspects, the default beam is associated with: a first TCI state of the multiple TCI states associated with the CORESET, as described above in connection with, e.g., FIG. 10. Figure 8A In some aspects, the default beam is associated with: a first TCI state of the multiple TCI states associated with the CORESET, as described above in connection with, e.g., FIG. 10.

[0134] In some aspects, the default beam is associated with: a first TCI state of the multiple TCI states associated with the CORESET, as described above in connection with, e.g., FIG. 10. Figure 8B ​The described plurality of transmission opportunities includes: a first set of transmission opportunities, in which the default beam is associated with a first TCI state among the plurality of TCI states associated with the CORESET; and a second set of transmission opportunities, in which the default beam is associated with a second TCI state among the plurality of TCI states associated with the CORESET. In some aspects, the plurality of transmission opportunities includes: a first set of transmission opportunities, in which the default beam is associated with the lowest TCI identifier among the TCI identifiers associated with the plurality of TCI states associated with the CORESET; and a second set of transmission opportunities, in which the default beam is associated with the highest TCI identifier among the TCI identifiers associated with the plurality of TCI states associated with the CORESET. In some aspects, the plurality of transmission opportunities includes at least a first set of transmission opportunities and a second set of transmission opportunities associated with cyclic mapping, sequential mapping, DMRS CDM group index, or frequency allocation portions.

[0135] At 1030, the UE can use the default beam to transmit the uplink data channel. For example, the UE (e.g., using...) Figure 13 The transmission component 1304 described herein can use the default beam to transmit the uplink data channel, as illustrated above in conjunction with, for example... Figures 8A-8B As described in 814, 820, 830 and 832.

[0136] although Figure 10 An example box of method 1000 is shown, but in some aspects, method 1000 may include... Figure 10 The boxes depicted in the diagram may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes of method 1000 may be executed in parallel.

[0137] Figure 11 This is a diagram of an example device 1100 for wireless communication. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a transmitting component 1104, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 may use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, device 1100 may include a determining component 1108 and other examples.

[0138] In some respects, device 1100 can be configured to perform the functions described herein. Figures 7A-7D and / or Figures 8A-8Bone or more operations described herein. Additionally or alternatively, the device 1100 can be configured to perform one or more methods described herein, such as Figure 9 the method 900 of FIG. 13, Figure 10 the method 1000 of FIG. 14, or combinations thereof. In some aspects, one or more components shown in Figure 11 may include one or more components of a UE described above in connection with Figure 2 may be implemented within one or more components shown in Figure 11 above in connection with Figure 2 may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0139] The reception component 1102 can receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1106. The reception component 1102 can provide received communications to one or more other components of the device 1100. In some aspects, the reception component 1102 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 1106. In some aspects, the reception component 1102 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or combinations thereof, of the UE described above in connection with Figure 2 .

[0140] The transmission component 1104 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1106 can generate communications and can provide the generated communications to the transmission component 1104 for transmission to the device 1106. In some aspects, the transmission component 1104 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1106. In some aspects, the transmission component 1104 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof, of the UE described above in connection with Figure 2 .

[0141] The reception component 1102 can receive, from a base station, DCI scheduling a downlink data channel, where the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET. The determination component 1108 can determine a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET. The reception component 1102 can receive the downlink data channel using the default beam.

[0142] Figure 11 The number and arrangement of components shown in FIG. 12 are provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 12. Additionally or alternatively, Figure 11 For example, an element can comprise one or more components of a component shown in FIG. 12. Figure 11 Components shown in FIG. 12 can be implemented in a single component or multiple components, some or all of which can be distributed across one or more computing devices. Figure 11 For example, a component can comprise one or more components of a component shown in FIG. 12. Figure 11 For example, a component can comprise one or more components of a component shown in FIG. 12. Figure 11 For example, a component can comprise one or more components of a component shown in FIG. 12.

[0143] Figure 12 FIG. 12 is a diagram illustrating an example 1200 of a hardware implementation for a device 1205 employing a processing system 1210. The device 1205 can be a UE.

[0144] The processing system 1210 can be implemented with a bus architecture, as represented by the bus 1215, which links the various circuits of the processing system 1210, including one or more processors and / or hardware components (represented by the processor 1220, the illustrated components, and the computer-readable medium / memory 1225). The bus 1215 can include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1210 and the overall design constraints. The bus 1215 links various circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like.

[0145] The processing system 1210 can be coupled to a transceiver 1230. The transceiver 1230 is coupled to one or more antennas 1235. The transceiver 1230 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1230 receives a signal from the one or more antennas 1235, extracts information from the received signal, and provides the extracted information to the processing system 1210, specifically the reception component 1102. In addition, the transceiver 1230 receives information from the processing system 1210, specifically the transmission component 1104, and

[0146] The processing system 1210 includes a processor 1220 coupled to a computer- readable medium / memory 1225. The processor 1220 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1225. The software, when executed by the processor 1220, causes the processing system 1210 to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory 1225 can also be used for storing data that is manipulated by the processor 1220 when executing software. The processing system further includes at least one of the illustrated components. The components can be software modules running in the processor 1220, resident / stored in the computer-readable medium / memory 1225, one or more hardware modules coupled to the processor 1220, or some combination thereof.

[0147] In some aspects, the processing system 1210 can be a component of the UE 120 and can include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the device 1205 for wireless communication includes means for receiving, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: a plurality of CORESETs or a plurality of TCI states associated with a CORESET, means for determining a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of CORESETs or the plurality of TCI states associated with the CORESET, and means for receiving the downlink data channel using the default beam. The aforementioned means can be one or more of the aforementioned components and / or the processing system 1210 of the device 1100 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1210 can include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means can be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0148] Figure 12 are provided as examples. Other examples can differ from what is described Figure 12 in connection with the examples described.

[0149] Figure 13 is a diagram of an example device 1300 for wireless communication. The device 1300 can be a UE, or a UE can include the device 1300. In some aspects, the device 1300 includes reception component 1302 and transmission component 1304, which can be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the device 1300 can communicate with another device 1306 (such as a UE, a base station, or another wireless communication device) using the reception component 1302 and the transmission component 1304. As further shown, the device 1300 can include determination component 1308, among other examples.

[0150] In some aspects, the device 1300 can be configured to perform one or more operations described herein in connection with Figures 7A-7D and / or Figures 8A-8B the methods described herein. Additionally, or alternatively, the device 1300 can be configured to perform one or more methods described herein, such as the method 900 of Figure 9 the device 1300 can include a processor. The processor can include one or more physical processors, each including one or more processing cores. The processor can be configured to execute instructions stored in a memory. The memory can include one or more types of memory, such as internal memory, external memory, or a combination thereof. The memory can include one or more types of volatile memory, such as dynamic random access memory (DRAM) or static RAM (SRAM). The memory can also include one or more types of non-volatile memory, such as read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), flash memory, or a combination thereof. The memory can include one or more types of removable storage media, such as a secure digital (SD) card, a memory stick, or the like. The memory can include one or more types of non-removable storage media, such as internal hard disk drives, solid state drives, or the like. The memory can include one or more types of storage media that can be internal or external, removable or non-removable, volatile or non-volatile, or a combination thereof.Figure 10 Method 1000 of FIG. 13, or a combination thereof). In some aspects, the device 1300 and / or Figure 13 one or more components shown in FIG. 13 can include one or more components of the UE described above in connection with FIGs. 1-12. Additionally, or alternatively, one or more components shown in FIG. 13 can be implemented within one or more components of the UE described above in connection with FIGs. 1-12. Additionally, or alternatively, one or more components of the set of components can be implemented at least in part as software stored in a memory. Figure 2 one or more components shown in FIG. 13 can be implemented within one or more components of the UE described above in connection with FIGs. 1-12. Additionally, or alternatively, one or more components of the set of components can be implemented at least in part as software stored in a memory. Figure 13 one or more components shown in FIG. 13 can be implemented within one or more components of the UE described above in connection with FIGs. 1-12. Additionally, or alternatively, one or more components of the set of components can be implemented at least in part as software stored in a memory. Figure 2 The reception component 1302 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1306. The reception component 1302 can provide received communications to one or more other components of the apparatus 1300. In some aspects, the reception component 1302 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the device 1306. In some aspects, the reception component 1302 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIGs. 1-12.

[0151] The reception component 1302 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1306. The reception component 1302 can provide received communications to one or more other components of the apparatus 1300. In some aspects, the reception component 1302 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the device 1306. In some aspects, the reception component 1302 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIGs. 1-12. Figure 2 The transmission component 1304 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1306. In some aspects, one or more other components of the device 1306 can generate communications and can provide the generated communications to the transmission component 1304 for transmission to the device 1306. In some aspects, the transmission component 1304 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1306. In some aspects, the transmission component 1304 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIGs. 1-12. In some aspects, the transmission component 1304 can be co-located with the reception component 1302 in a transceiver. The transmission component 1304 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1306. In some aspects, one or more other components of the device 1306 can generate communications and can provide the generated communications to the transmission component 1304 for transmission to the device 1306. In some aspects, the transmission component 1304 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1306. In some aspects, the transmission component 1304 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIGs. 1-12. In some aspects, the transmission component 1304 can be co-located with the reception component 1302 in a transceiver.

[0152] The transmission component 1304 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1306. In some aspects, one or more other components of the device 1306 can generate communications and can provide the generated communications to the transmission component 1304 for transmission to the device 1306. In some aspects, the transmission component 1304 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1306. In some aspects, the transmission component 1304 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIGs. 1-12. In some aspects, the transmission component 1304 can be co-located with the reception component 1302 in a transceiver. Figure 2 The transmission component 1304 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1306. In some aspects, one or more other components of the device 1306 can generate communications and can provide the generated communications to the transmission component 1304 for transmission to the device 1306. In some aspects, the transmission component 1304 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the device 1306. In some aspects, the transmission component 1304 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIGs. 1-12. In some aspects, the transmission component 1304 can be co-located with the reception component 1302 in a transceiver.

[0153] The reception component 1302 can receive, from a base station, DCI scheduling an uplink data channel, where the DCI is associated with a repetition configuration including a CORESET associated with a plurality of TCI states. The determination component 1308 can determine a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, where the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET. The transmission component 1304 can transmit the uplink data channel using the default beam.

[0154] Figure 13 The number and arrangement of components shown in FIG. 13 are provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 13. Additionally or alternatively, Figure 13 For example, two or more components shown in FIG. 13 can be implemented within a single component, or Figure 13 For example, two or more components shown in FIG. 13 can be implemented within a single component, or Figure 13 For example, two or more components shown in FIG. 13 can be implemented within a single component, or Figure 13 For example, a set of two or more components shown in FIG. 13 can be implemented by a single component. Figure 13 For example, a set of two or more components shown in FIG. 13 can be implemented by a single component.

[0155] Figure 14 FIG. 14 is a diagram illustrating an example 1400 of a hardware implementation for a device 1405 employing a processing system 1410. The device 1405 can be a UE.

[0156] The processing system 1410 can be implemented with a bus architecture, as represented by the bus 1415, which links the various circuits of the processing system 1410, including one or more processors and / or hardware components (represented by the processor 1420, the illustrated components, and the computer-readable medium / memory 1425). The bus 1415 can include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1410 and the overall design constraints. The bus 1415 links various circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and the like.

[0157] The processing system 1410 can be coupled to a transceiver 1430. The transceiver 1430 is coupled to one or more antennas 1435. The transceiver 1430 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1430 receives a signal from the one or more antennas 1435, extracts information from the received signal, and provides the extracted information to the processing system 1410, specifically the reception component 1302. In addition, the transceiver 1430 receives information from the processing system 1410, specifically the transmission component 1304, and

[0158] The processing system 1410 includes a processor 1425 coupled to a computer- readable medium / memory 1420. The processor 1420 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1425. The software, when executed by the processor 1420, causes the processing system 1410 to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory 1425 can also be used for storing data that is manipulated by the processor 1420 when executing software. The processing system further includes at least one of the illustrated components. The components can be software modules running in the processor 1420, resident / stored in the computer-readable medium / memory 1425, one or more hardware modules coupled to the processor 1420, or some combination thereof.

[0159] In some aspects, the processing system 1410 can be a component of the UE 120 and can include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the device 1405 for wireless communication includes means for receiving, from a base station, DCI scheduling an uplink data channel, wherein the DCI is associated with a repetition configuration including a CORESET associated with multiple TCI states, means for determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the multiple TCI states associated with the CORESET, and means for transmitting the uplink data channel using the default beam. The aforementioned means can be one or more of the aforementioned components and / or the processing system 1410 of the device 1405 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1410 can include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means can be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0160] Figure 14 are provided as examples. Other examples can differ from what is described Figure 14 in connection with

[0161] The following provides an overview of aspects of the disclosure:

[0162] Aspect 1 : A method of wireless communication performed by a UE, comprising: receiving, from a base station, DCI scheduling a downlink data channel, wherein the DCI is associated with a repetition configuration including one or more of: multiple CORESETs or multiple TCI states associated with a CORESET; determining a default beam for the downlink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the multiple CORESETs or the multiple TCI states associated with the CORESET; and receiving the downlink data channel using the default beam.

[0163] Aspect 2: The method of Aspect 1, wherein the downlink data channel is associated with a single reception occasion, and wherein the repetition configuration associated with the DCI includes the multiple CORESETs.

[0164] Aspect 3: The method of aspect 2, wherein the default beam is associated with: a TCI state or a QCL assumption applied to one of the plurality of CORESETs having a lowest CORESET identifier.

[0165] Aspect 4: The method of aspect 2, wherein the default beam is associated with: a TCI state or a QCL assumption applied to one of the plurality of CORESETs associated with a search space having a lowest search space identifier, or a TCI state or a QCL assumption applied to one of the plurality of CORESETs associated with a search space having a highest search space identifier.

[0166] Aspect 5: The method of aspect 2, wherein the default beam is associated with: a TCI state or a QCL assumption applied to one of the plurality of CORESETs associated with a latest monitored search space in time, or a TCI state or a QCL assumption applied to one of the plurality of CORESETs associated with an earliest monitored search space in time.

[0167] Aspect 6: The method of any one of aspects 2-5, wherein the default beam is associated with: a first TCI state and a second TCI state associated with a first CORESET and a second CORESET, respectively, of the plurality of CORESETs based at least in part on the downlink data channel having a SFN configuration.

[0168] Aspect 7: The method of aspect 1, wherein the downlink data channel is associated with a single reception occasion, and wherein the repetition configuration associated with the DCI includes the CORESET associated with the plurality of TCI states.

[0169] Aspect 8: The method of aspect 7, wherein the default beam is associated with: a first TCI state of the plurality of TCI states associated with the CORESET.

[0170] Aspect 9: The method of aspect 7, wherein the default beam is associated with: a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the CORESET.

[0171] Aspect 10: The method of aspect 7, wherein the default beam is associated with: a TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the CORESET that is QCLed with a SSB having a lowest index.

[0172] Aspect 11: The method of any of aspects 7 through 10, wherein the default beam is associated, based at least in part on the downlink data channel having an SFN configuration, with: a first TCI state and a second TCI state of the plurality of TCI states associated with the CORESET.

[0173] Aspect 12: The method of aspect 1, wherein the downlink data channel is configured with a plurality of reception occasions, and wherein the repetition configuration associated with the DCI comprises the plurality of CORESETs.

[0174] Aspect 13: The method of aspect 12, wherein the plurality of reception occasions comprises: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs having a lowest CORESET identifier, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs having a highest CORESET identifier.

[0175] Aspect 14: The method of aspect 12, wherein the plurality of reception occasions comprises: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a search space having a lowest search space identifier, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a search space having a highest search space identifier.

[0176] Aspect 15: The method of aspect 12, wherein the plurality of reception occasions comprises: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a latest monitored search space in time, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with an earliest monitored search space in time.

[0177] Aspect 16: The method of any of aspects 12 through 15, wherein the plurality of reception occasions comprises at least a first set of reception occasions and a second set of reception occasions associated with a cyclic mapping, a sequential mapping, a DMRS CDM group index, or a frequency allocation portion.

[0178] Aspect 17: The method of aspect 1, wherein the downlink data channel is configured with a plurality of reception occasions, and wherein the repetition configuration associated with the DCI comprises the CORESET associated with the plurality of TCI states.

[0179] Aspect 18: The method of aspect 17, wherein the plurality of reception occasions comprises: a first set of reception occasions in which the default beam is associated with: a first TCI state of the plurality of TCI states associated with the CORESET, and a second set of reception occasions in which the default beam is associated with: a second TCI state of the plurality of TCI states associated with the CORESET.

[0180] Aspect 19: The method of aspect 17, wherein the plurality of reception occasions comprises: a first set of reception occasions in which the default beam is associated with: a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the CORESET, and a second set of reception occasions in which the default beam is associated with: a highest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the CORESET.

[0181] Aspect 20: The method of aspect 17, wherein the plurality of reception occasions comprises: a first set of reception occasions in which the default beam is associated with: a first TCI identifier of the TCI identifiers associated with the plurality of TCI states associated with the CORESET that is QCLed with a SSB having a lowest index, and a second set of reception occasions in which the default beam is associated with: a second TCI identifier of the TCI identifiers associated with the plurality of TCI states associated with the CORESET that is QCLed with a SSB having a highest index.

[0182] Aspect 21: A method of wireless communication performed by a UE, comprising: receiving, from a base station, DCI scheduling an uplink data channel, wherein the DCI is associated with a repetition configuration comprising a CORESET associated with a plurality of TCI states; determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET; and transmitting the uplink data channel using the default beam.

[0183] Aspect 22: The method of aspect 21, wherein the uplink data channel is associated with a single transmission occasion.

[0184] Aspect 23: The method of aspect 22, wherein the default beam is associated with: a first TCI state of the plurality of TCI states associated with the CORESET.

[0185] Aspect 24: The method of aspect 22, wherein the default beam is associated with: a lowest TCI identifier among TCI identifiers associated with the plurality of TCI states associated with the CORESET.

[0186] Aspect 25: The method of aspect 22, wherein the default beam is associated with: a TCI identifier that is QCLed with a lowest indexed SSB among TCI identifiers associated with the plurality of TCI states associated with the CORESET.

[0187] Aspect 26: The method of aspect 21, wherein the uplink data channel is configured with a plurality of transmission occasions.

[0188] Aspect 27: The method of aspect 26, wherein the plurality of transmission occasions comprises: a first set of transmission occasions in which the default beam is associated with a first TCI state of the plurality of TCI states associated with the CORESET, and a second set of transmission occasions in which the default beam is associated with a second TCI state of the plurality of TCI states associated with the CORESET.

[0189] Aspect 28: The method of aspect 26, wherein the plurality of transmission occasions comprises: a first set of transmission occasions in which the default beam is associated with a lowest TCI identifier among TCI identifiers associated with the plurality of TCI states associated with the CORESET, and a second set of transmission occasions in which the default beam is associated with a highest TCI identifier among TCI identifiers associated with the plurality of TCI states associated with the CORESET.

[0190] Aspect 29: The method of aspect 26, wherein the plurality of transmission occasions comprises at least a first set of transmission occasions and a second set of transmission occasions associated with a cyclic mapping, a sequential mapping, a DMRS CDM group index, or a frequency allocation portion.

[0191] Aspect 30: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 1 through 20.

[0192] Aspect 31: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of any of aspects 1 through 20.

[0193] Aspect 32: A device for wireless communication, comprising at least one means for performing a method of any of aspects 1 through 20.

[0194] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of any of aspects 1 through 20.

[0195] Aspect 34: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of any of aspects 1 through 20.

[0196] Aspect 30: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any of aspects 21 through 29.

[0197] Aspect 31: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of any of aspects 21 through 29.

[0198] Aspect 32: A device for wireless communication, comprising at least one means for performing a method of any of aspects 21 through 29.

[0199] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of any of aspects 21 through 29.

[0200] Aspect 34: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of any of aspects 21 through 29.

[0201] The foregoing disclosure provides explanation and description to enable a person skilled in the art to make or use the aspects, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made in light of the above disclosure or can be acquired from practice of the aspects.

[0202] As used herein, the term “component” is intended to be broadly interpreted to encompass hardware, firmware, and / or software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it is understood that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0203] As used herein, depending on the context, satisfying a threshold can refer to being greater than the threshold, being greater than or equal to the threshold, being less than the threshold, being less than or equal to the threshold, being equal to the threshold, not being equal to the threshold, and the like.

[0204] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below can directly depend on only one claim, the disclosure of each aspect includes each dependent claim in combination with every other claim in the set. As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination of multiples of the same element (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).

[0205] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items, and can be used interchangeably with “the one or more.” Also, as used herein, the terms “set” and “group” are intended to include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and can be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., in an exhaustive list of options).

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a base station, downlink control information (DCI) scheduling a downlink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration indicating whether the PDCCH is associated with: a plurality of control resource sets (CORESETs), or a plurality of TCI states associated with a CORESET; determining a default beam for the downlink data channel based at least in part on the repetition configuration, wherein the default beam is determined based at least in part on one of the plurality of CORESETs, or based at least in part on one or more of the plurality of TCI states associated with a CORESET, wherein whether one or more of the plurality of TCI states is used to determine the default beam is based at least in part on whether the downlink data channel is associated with a single frequency network (SFN) repetition configuration; and receiving the downlink data channel using the default beam.

2. The method of claim 1, wherein, the downlink data channel is associated with a single reception occasion, and wherein the repetition configuration indicates that the PDCCH is associated with a plurality of CORESETs.

3. The method of claim 2, wherein, the default beam is associated with a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs having a lowest CORESET identifier.

4. The method of claim 3, wherein, a time offset between the reception of the DCI and the downlink data channel scheduled by the DCI is equal to or greater than a configured threshold defining a minimum number of symbols required for the UE to perform PDCCH reception and apply spatial QCL information received in a scheduling DCI.

5. The method of claim 4, wherein, the threshold is defined based on a UE capability.

6. The method of claim 2, wherein, the default beam is associated with: a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with a search space having a lowest search space identifier, or a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with a search space having a highest search space identifier.

7. The method of claim 2, wherein, the default beam is associated with: a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with a latest in time monitored search space, or a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with an earliest in time monitored search space.

8. The method of claim 2, wherein the default beam is associated with a first TCI state and a second TCI state associated with a first CORESET and a second CORESET, respectively, of the plurality of CORESETs based at least in part on the downlink data channel having a single frequency network (SFN) configuration.

9. The method of claim 1, wherein, the downlink data channel is associated with a single reception occasion, and wherein the repetition configuration indicates that the PDCCH is associated with the plurality of TCI states.

10. The method of claim 9, wherein, the default beam is associated with: a first TCI state of the plurality of TCI states associated with the one CORESET.

11. The method of claim 9, wherein, the CORESET is a CORESET associated with a most recently monitored search space.

12. The method of claim 9, wherein, the default beam is associated with: a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET.

13. The method of claim 9, wherein, the default beam is associated with an identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET that is quasi co-located with a synchronization signal block having a lowest index.

14. The method of claim 9, wherein the default beam is associated with based at least in part on the downlink data channel having a single frequency network configuration: a first TCI state and a second TCI state of the plurality of TCI states associated with the one CORESET.

15. The method of claim 1, wherein, the downlink data channel is configured with a plurality of reception occasions, and wherein the repetition configuration indicates that the PDCCH is associated with the plurality of CORESETs.

16. The method of claim 15, wherein, the plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs having a lowest CORESET identifier, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs having a highest CORESET identifier.

17. The method of claim 15, wherein, the plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a search space having a lowest search space identifier, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a search space having a highest search space identifier.

18. The method of claim 15, wherein, the plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a latest in time monitored search space, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with an earliest in time monitored search space.

19. The method of claim 15, wherein, the plurality of reception occasions includes at least a first set of reception occasions and a second set of reception occasions associated with a cyclic mapping, a sequential mapping, a demodulation reference signal (DMRS) code division multiplexing group index, or a frequency allocation portion.

20. The method of claim 1, wherein, The downlink data channel is associated with a single frequency network (SFN) repetition configuration, and wherein the repetition configuration indicates that the PDCCH is associated with the plurality of TCI states.

21. The method of claim 19, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET, and a second set of reception occasions in which the default beam is associated with a highest TCI identifier of the TCI identifiers associated with the plurality of TCI states associated with the one CORESET.

22. The method of claim 19, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET, and a second set of reception occasions in which the default beam is associated with a highest TCI identifier of the TCI identifiers associated with the plurality of TCI states associated with the one CORESET.

23. The method of claim 19, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET, and a second set of reception occasions in which the default beam is associated with a highest TCI identifier of the TCI identifiers associated with the plurality of TCI states associated with the one CORESET.

24. The method of claim 20, wherein determining a default beam for the downlink data channel comprises determining a plurality of default beams for the downlink data channel, the plurality of default beams being associated with respective ones of the plurality of TCI states.

25. The method of claim 24, wherein, A time offset between reception of the DCI and a downlink data channel scheduled by the DCI is equal to or greater than a configured threshold defining a minimum number of symbols required for the UE to perform PDCCH reception and apply spatial QCL information received in scheduling DCI.

26. A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a base station, downlink control information (DCI) scheduling an uplink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration, the repetition configuration indicating whether the PDCCH is associated with a control resource set (CORESET) that is associated with a plurality of TCI states; and determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on a first TCI state of the plurality of TCI states associated with the one CORESET; and transmitting the uplink data channel using the default beam.

27. The method of claim 26, wherein, The uplink data channel is associated with a single transmission occasion.

28. The method of claim 27, wherein, The default beam is associated with a first TCI state of the plurality of TCI states associated with the one CORESET.

29. The method of claim 27, wherein, The default beam is associated with a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET.

30. The method of claim 27, wherein, The default beam is associated with a TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET, the CORESET being quasi co-located with a synchronization signal block having a lowest index.

31. The method of claim 26, wherein, The uplink data channel is configured with a plurality of transmission occasions.

32. The method of claim 31, wherein, The plurality of transmission occasions includes: a first set of transmission occasions in which the default beam is associated with a first TCI state of the plurality of TCI states associated with the one CORESET, and a second set of transmission occasions in which the default beam is associated with a second TCI state of the plurality of TCI states associated with the one CORESET.

33. The method of claim 31, wherein, The plurality of transmission occasions includes: a first set of transmission occasions in which the default beam is associated with a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET, and a second set of transmission occasions in which the default beam is associated with a highest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with the one CORESET.

34. The method of claim 31, wherein, The plurality of transmission occasions includes at least a first set of transmission occasions and a second set of transmission occasions associated with a cyclic mapping, a sequential mapping, a demodulation reference signal (DMRS) code division multiplexing group index, or a frequency allocation portion.

35. A user equipment (UE), comprising: one or more memories; and one or more processors coupled with the one or more memories, the one or more processors configured to: receive, from a base station, downlink control information (DCI) scheduling a downlink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration, the repetition configuration indicating whether the PDCCH is associated with: a plurality of control resource sets (CORESETs), or a plurality of TCI states associated with one CORESET; determining a default beam for the downlink data channel based at least in part on the repetition configuration, wherein the default beam is determined based at least in part on one of the plurality of CORESETs, or one or multiple of the plurality of TCI states associated with a CORESET, wherein whether one or multiple of the plurality of TCI states is used to determine the default beam is based at least in part on whether the downlink data channel is associated with a single frequency network (SFN) repetition configuration; and receiving the downlink data channel using the default beam.

36. The UE of claim 35, wherein, The downlink data channel is associated with a single reception occasion, and wherein the repetition configuration indicates that the PDCCH is associated with multiple CORESETs.

37. The UE of claim 36, wherein, The default beam is associated with a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs having a lowest CORESET identifier.

38. The UE of claim 37, wherein, A time offset between reception of the DCI and a downlink data channel scheduled by the DCI is equal to or greater than a configured threshold defining a minimum number of symbols required for the UE to perform PDCCH reception and apply spatial QCL information received in a scheduling DCI.

39. The UE of claim 38, wherein, The threshold is defined based on a UE capability.

40. The UE of claim 36, wherein, The default beam is associated with: a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with a search space having a lowest search space identifier, or a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with a search space having a highest search space identifier.

41. The UE of claim 36, wherein, The default beam is associated with: a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with a latest monitored search space in time, or a TCI state or quasi co-location assumption applied to one of the plurality of CORESETs associated with an earliest monitored search space in time.

42. The UE of claim 36, wherein, The default beam is associated with first and second TCI states associated with first and second CORESETs of the plurality of CORESETs, respectively, based at least in part on the downlink data channel having a single frequency network (SFN) configuration.

43. The UE of claim 35, wherein, The downlink data channel is associated with a single reception occasion, and wherein the repetition configuration indicates that the PDCCH is associated with the plurality of TCI states.

44. The UE of claim 43, wherein, The default beam is associated with a first TCI state of the plurality of TCI states associated with a CORESET.

45. The UE of claim 43, wherein, The CORESET is a CORESET associated with a most recently monitored search space.

46. The UE of claim 43, wherein, The default beam is associated with a lowest TCI identifier of TCI identifiers associated with the plurality of TCI states associated with a CORESET. The default beam is associated with a first TCI state of the plurality of TCI states associated with a CORESET.

47. The UE of claim 43, wherein, The default beam is associated with one of a plurality of TCI identifiers associated with a plurality of TCI states associated with a CORESET that is quasi co-located with a synchronization signal block having a lowest index.

48. The UE of claim 43, wherein, The default beam is associated with the plurality of TCI states based at least in part on the downlink data channel having a single frequency network configuration. The plurality of TCI states associated with the CORESET.

49. The UE of claim 35, wherein, The downlink data channel is configured with a plurality of reception occasions, and wherein the repetition configuration indicates that the PDCCH is associated with the plurality of CORESETs.

50. The UE of claim 49, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs having a lowest CORESET identifier, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs having a highest CORESET identifier.

51. The UE of claim 49, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a search space having a lowest search space identifier, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a search space having a highest search space identifier.

52. The UE of claim 49, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with a latest in time monitored search space, and a second set of reception occasions in which the default beam is associated with one of the plurality of CORESETs associated with an earliest in time monitored search space.

53. The UE of claim 49, wherein, The plurality of reception occasions includes a first set of reception occasions and a second set of reception occasions associated with a cyclic mapping, a sequential mapping, a demodulation reference signal (DMRS) code division multiplexing group index, or a frequency allocation portion.

54. The UE of claim 35, wherein, The downlink data channel is associated with a single frequency network (SFN) repetition configuration, and wherein the repetition configuration indicates that the PDCCH is associated with the plurality of TCI states.

55. The UE of claim 53, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with a first one of the plurality of TCI states associated with a CORESET, and a second set of reception occasions in which the default beam is associated with a second one of the plurality of TCI states associated with a CORESET.

56. The UE of claim 53, wherein, The plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with a lowest TCI identifier of TCI identifiers associated with a plurality of TCI states associated with a CORESET, and a second set of reception occasions in which the default beam is associated with a highest TCI identifier of TCI identifiers associated with a plurality of TCI states associated with a CORESET.

57. The UE of claim 53, wherein, the plurality of reception occasions includes: a first set of reception occasions in which the default beam is associated with a first TCI identifier of TCI identifiers associated with a plurality of TCI states associated with a CORESET that is quasi co-located (QCLed) with a synchronization signal block (SSB) having a lowest index, and a second set of reception occasions in which the default beam is associated with a second TCI identifier of TCI identifiers associated with a plurality of TCI states associated with a CORESET that is quasi co-located (QCLed) with a SSB having a highest index.

58. The UE of claim 54, wherein, to determine the default beam of the downlink data channel, the one or more processors are configured to determine a plurality of default beams of the downlink data channel, the plurality of default beams being associated with respective ones of the plurality of TCI states.

59. The UE of claim 58, wherein, a time offset between the reception of the DCI and the downlink data channel scheduled by the DCI is equal to or greater than a configured threshold defining a minimum number of symbols required for the UE to perform PDCCH reception and apply spatial QCL information received in scheduling DCI.

60. A user equipment (UE), comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to: receive, from a base station, downlink control information (DCI) scheduling an uplink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration indicating whether the PDCCH is associated with a control resource set (CORESET) associated with a plurality of TCI states; determine a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET; and transmit the uplink data channel using the default beam.

61. The UE of claim 60, wherein, the uplink data channel is associated with a single transmission occasion.

62. The UE of claim 61, wherein, the default beam is associated with a first TCI state of a plurality of TCI states associated with the CORESET.

63. The UE of claim 61, wherein, the default beam is associated with: a lowest TCI identifier of TCI identifiers associated with a plurality of TCI states associated with the CORESET.

64. The UE of claim 61, wherein, The default beam is associated with a TCI identifier of TCI identifiers associated with a plurality of TCI states associated with the CORESET that is quasi co-located with a synchronization signal block having a lowest index.

65. The UE of claim 60, wherein, The uplink data channel is configured with a plurality of transmission occasions.

66. The UE of claim 65, wherein, The plurality of transmission occasions includes: a first set of transmission occasions in which the default beam is associated with a first TCI state of a plurality of TCI states associated with the CORESET, and a second set of transmission occasions in which the default beam is associated with a second TCI state of the plurality of TCI states associated with the CORESET.

67. The UE of claim 65, wherein, The plurality of transmission occasions includes: a first set of transmission occasions in which the default beam is associated with a lowest TCI identifier of TCI identifiers associated with a plurality of TCI states associated with the CORESET, and a second set of transmission occasions in which the default beam is associated with a highest TCI identifier of the TCI identifiers associated with the plurality of TCI states associated with the CORESET.

68. The UE of claim 65, wherein, The plurality of transmission occasions includes at least a first set of transmission occasions and a second set of transmission occasions associated with a cyclic mapping, a sequential mapping, a demodulation reference signal (DMRS) code division multiplexing group index, or a frequency allocation portion.

69. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: receive, from a base station, downlink control information (DCI) scheduling a downlink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration, the repetition configuration indicating whether the PDCCH is associated with: a plurality of control resource sets (CORESETs), or a plurality of TCI states associated with a CORESET; whether to use one or more of the plurality of TCI states to determine the default beam is based at least in part on whether the downlink data channel is associated with a single frequency network (SFN) repetition configuration; and determining a default beam for the downlink data channel based at least in part on the repetition configuration, wherein the default beam is determined based at least in part on one of a plurality of CORESETs, or is determined based at least in part on one of the plurality of TCI states or a plurality of TCI states associated with a CORESET, wherein receive the downlink data channel using the default beam.

70. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: ​ receiving, from a base station, downlink control information (DCI) scheduling an uplink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration, the repetition configuration indicating whether the PDCCH is associated with: a control resource set (CORESET) associated with a plurality of TCI states; determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET; and transmitting the uplink data channel using the default beam.

71. An apparatus for wireless communication, comprising: means for receiving, from a base station, downlink control information (DCI) scheduling a downlink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration, the repetition configuration indicating whether the PDCCH is associated with: a plurality of control resource sets (CORESETs), or a plurality of TCI states associated with a CORESET; means for determining a default beam for the downlink data channel based at least in part on the repetition configuration, wherein the default beam is determined based at least in part on one of a plurality of CORESETs, or based at least in part on one or a plurality of TCI states associated with a CORESET, wherein whether one or a plurality of the TCI states are used to determine the default beam is based at least in part on whether the downlink data channel is associated with a single frequency network (SFN) repetition configuration; and means for receiving the downlink data channel using the default beam.

72. An apparatus for wireless communication, comprising: means for receiving, from a base station, downlink control information (DCI) scheduling an uplink data channel, the DCI not having a transmission configuration indication (TCI) field, wherein the DCI is associated with a physical downlink control channel (PDCCH) repetition configuration, the repetition configuration indicating whether the PDCCH is associated with a control resource set (CORESET) associated with a plurality of TCI states; means for determining a default beam for the uplink data channel based at least in part on the repetition configuration associated with the DCI, wherein the default beam is determined based at least in part on the plurality of TCI states associated with the CORESET; and means for transmitting the uplink data channel using the default beam.

Images