Downlink control information (DCI) format and capability reporting for beam indication without scheduling data

Abstract

To provide a system, a method, and a device for a base station (BS) to transmit downlink control information (DCI) without downlink data for indicating a transmission configuration indicator (TCI).SOLUTION: In a wireless communication system, user equipment (UE) transmits a capability indication associated with whether the UE can receive DCI with a TCI and no data allocation, receives DCI with one or more configured fields and no downlink data, and interprets the DCI based on the one or more configured fields for identifying the TCI.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to commonly assigned PCT patent application No. PCT / CN2021 / 080375, entitled "DOWNLINK CONTROL INFORMATION (DCI) FORMAT FOR BEAM INDICATION WITHOUT SCHEDULING DATA," filed March 12, 2021. The disclosure of the prior application is considered part of, and incorporated by reference into, this patent application.

[0002]

[0002] Aspects of the present disclosure relate generally to wireless communication and to techniques for downlink control information (DCI) formats and capability reporting for beam indication without scheduling data. [Background technology]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access 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 extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0004] A wireless network may include several base stations (BSs) that can support communication for several user equipments (UEs). The UEs may communicate with the BSs via a downlink (DL) and an uplink (UP). The "DL" (or "forward link") refers to the communication link from the BSs to the UEs, and the "UL" (or "reverse link") refers to the communication link from the UEs to the BSs. As described in more detail herein, a BS may be referred to as a Node B, an LTE evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a new radio (NR) BS, or a 5G Node B.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide common protocols that enable different UEs to communicate on a city, national, regional, or even global scale. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to improve spectral efficiency, lower costs, improve service, utilize new spectrum, and better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the DL and CP-OFDM or SC-FDM (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the UL (or a combination thereof), better integrating with other open standards, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Summary of the Invention

[0006]

[0006] The systems, methods, and devices disclosed herein each have several inventive aspects, no single aspect of which may be solely responsible for the desirable attributes disclosed herein.

[0007]

[0007] One inventive aspect of the subject matter described in this disclosure may be implemented in a wireless communication method performed by a user equipment (UE) device, comprising receiving downlink control information (DCI) having a DCI format, wherein the DCI includes one or more configured fields, and communicating in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0008] In some aspects, the DCI format is DCI format 1_1 or DCI format 1_2. In some aspects, the DCI format is DCI format 1_0 or an uplink DCI format. In some aspects, the DCI includes a first indication of a TCI and a second indication of another configuration. In some aspects, the second indication includes at least one of a secondary cell (SCell) dormancy indication, a semi-persistent scheduling (SPS) release indication, an SPS activation indication, or a hybrid automatic repeat request (HARQ) indication. In some aspects, the DCI indicates multiple TCIs. In some aspects, the TCI includes a downlink TCI and an uplink TCI.

[0009]

[0009] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a method of wireless communication performed by a base station (BS), comprising transmitting a DCI having a DCI format, wherein the DCI includes one or more configured fields, and communicating in accordance with a TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0010]

[0010] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus for wireless communication in a UE including a memory and one or more processors coupled to the memory, configured to receive DCI having a DCI format, wherein the DCI includes one or more configured fields, and to communicate in accordance with TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0011]

[0011] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus for wireless communication in a BS including a memory and one or more processors coupled to the memory, configured to: transmit a DCI having a DCI format, wherein the DCI includes one or more configured fields, and communicate in accordance with a TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0012]

[0012] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a UE apparatus for wireless communication including a first interface configured to acquire DCI having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data, and the first interface or the second interface is configured to acquire or output information according to a TCI associated with the one or more configured fields.

[0013]

[0013] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus of a BS for wireless communication including a first interface configured to output a DCI having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data, and the first interface or the second interface is configured to output or retrieve information according to a TCI associated with the one or more configured fields.

[0014]

[0014] Another inventive aspect of the subject matter described in this disclosure may be implemented in a non-transitory computer-readable medium storing a set of instructions for wireless communication including one or more instructions, which when executed by one or more processors of a UE cause the user equipment to receive a DCI having a DCI format, wherein the DCI includes one or more configured fields, and communicate in accordance with a TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0015]

[0015] Another inventive aspect of the subject matter described in this disclosure may be implemented in a non-transitory computer-readable medium storing a set of instructions for wireless communications, the one or more instructions including, when executed by one or more processors of a BS, causing the BS to transmit a DCI having a DCI format, where the DCI includes one or more configured fields, and to communicate in accordance with a TCI associated with the one or more configured fields, where the DCI does not include scheduling data.

[0016]

[0016] Another inventive aspect of the subject matter described in this disclosure may be implemented in an apparatus for wireless communication, the apparatus including means for receiving a DCI having a DCI format, wherein the DCI includes one or more configured fields, and means for communicating in accordance with a TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0017]

[0017] Another inventive aspect of the subject matter described in this disclosure may be implemented in an apparatus for wireless communication, the apparatus including means for transmitting a DCI having a DCI format, wherein the DCI includes one or more configured fields, and means for communicating in accordance with a TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0018]

[0018] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a method of wireless communication performed by a UE device, and includes transmitting a capability indicator, where the capability indicator is associated with whether the UE supports DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and communicating in accordance with the capability indicator.

[0019]

[0019] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a method of wireless communication performed by a BS, comprising receiving a capability indicator, wherein the capability indicator is associated with whether the UE supports DCI having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data, and communicating in accordance with the capability indicator.

[0020] In some aspects, wherein the one or more configured fields are associated with a TCI. In some aspects, a method includes receiving a DCI having a DCI format and communicating in accordance with the TCI associated with the one or more configured fields.

[0021]

[0021] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus for wireless communication in a UE including a memory and one or more processors coupled to the memory, configured to: transmit a capability indicator; and communicate in accordance with the capability indicator, wherein the capability indicator is associated with whether the UE supports DCI having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data.

[0022] In some aspects, wherein the one or more configured fields are associated with a TCI. In some aspects, a method includes transmitting a DCI having a DCI format and communicating in accordance with the TCI associated with the one or more configured fields.

[0023]

[0023] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a BS including a memory and one or more processors coupled to the memory, and configured to receive a capability indicator, where the capability indicator is associated with whether the UE supports DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and to communicate in accordance with the capability indicator.

[0024]

[0024] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a UE apparatus for wireless communication including a first interface configured to output a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and the first interface or the second interface is configured to communicate according to the capability indicator.

[0025]

[0025] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus of a BS for wireless communication including a first interface configured to receive a capability indicator, where the capability indicator is associated with whether a UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and where the second interface or the first interface is configured to communicate according to the capability indicator.

[0026]

[0026] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a non-transitory computer-readable medium storing a set of instructions for wireless communication including one or more instructions, which when executed by one or more processors of the UE, cause the UE to transmit a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and to communicate in accordance with the capability indicator.

[0027]

[0027] Another inventive aspect of the subject matter described in the present disclosure may be implemented in a non-transitory computer-readable medium storing a set of instructions for wireless communication, the one or more instructions including, when executed by one or more processors of a BS, causing the BS to receive a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and to communicate in accordance with the capability indicator.

[0028]

[0028] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus for wireless communications, the apparatus including means for transmitting a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and means for communicating in accordance with the capability indicator.

[0029]

[0029] Another inventive aspect of the subject matter described in the present disclosure may be implemented in an apparatus for wireless communication, the apparatus including means for receiving a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and means for communicating in accordance with the capability indicator.

[0030]

[0030] In some aspects, a device of the UE, such as a processing system of the device or one or more interfaces of the device, among other examples, may be configured to perform one or more operations of a wireless communication method implemented by the device.

[0031]

[0031] In some aspects, a device of the BS, such as a processing system of the device or one or more interfaces of the device, among other examples, may be configured to perform one or more operations of a wireless communication method implemented by the device.

[0032]

[0032] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, or processing system substantially as described in this specification with reference to and as illustrated by the accompanying drawings.

[0033]

[0033] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Please note that the relative dimensions of the following figures may not be drawn to scale. [Brief explanation of the drawings]

[0034] [Figure 1]

[0034] FIG. 1 illustrates an example of a wireless network. [Figure 2]

[0035] FIG. 1 illustrates an example of a base station (BS) in communication with user equipment (UE) in a wireless network. [Figure 3]

[0036] FIG. 1 illustrates an example of using beams for communication between a BS and a UE. [Figure 4]

[0037] 1 illustrates an exemplary process, for example, performed by a UE. [Figure 5] 1 illustrates an exemplary process, for example, performed by a BS. [Figure 6]

[0038] 1 is a block diagram of an exemplary apparatus for wireless communication. [Figure 7] 1 is a block diagram of an exemplary apparatus for wireless communication. [Figure 8]

[0039] 1A and 1B are diagrams relating to exemplary aspects of the present disclosure. [Figure 9] 1A and 1B are diagrams relating to exemplary aspects of the present disclosure. [Figure 10] 1A and 1B are diagrams relating to exemplary aspects of the present disclosure. [Figure 11]

[0040] 1 illustrates an exemplary process, for example, performed by a UE. [Figure 12] 1 illustrates an exemplary process, for example, performed by a BS. [Figure 13]

[0041] 1A and 1B are diagrams relating to exemplary aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0035]

[0042] Like reference numbers and designations in the various drawings indicate like elements.

[0036]

[0043] The following description is directed to several implementations for the purposes of illustrating the inventive aspects of the present disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in many different ways. Some of the examples in this disclosure are based on wireless and wired local area network (LAN) communications according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 Power Line Communications (PLC) standard. However, the described implementations may be used to communicate within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, or 5G, or further implementations thereof, technologies such as the IEEE 802.11 standard, Bluetooth® standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Based Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1xEV-DO, EV-DO RevA, EV-DO 1xEV-DO ... It may be implemented in any device, system, or network capable of transmitting and receiving radio frequency signals in accordance with any of the wireless communications standards, including RevB, High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), AMPS, or any other known signal.

[0037]

[0044] In some situations, a base station (BS) may transmit downlink control information (DCI) to provide configuration information to a user equipment (UE). For example, a BS may transmit DCI to indicate semi-persistent scheduling (SPS) release, SPS activation, hybrid automatic repeat request (HARQ) configuration, or secondary cell dormancy configuration, among other examples. The BS may also transmit DCI to update the beam configuration for the UE. For example, a BS may transmit a DCI configured in DCI format 1_1 or DCI format 1_2 with downlink resource allocation for scheduling downlink data transmission to indicate a transmission configuration indicator (TCI), such as a TCI state defined in the 3GPP specifications, or another similar data structure. The TCI may indicate one or more quasi-co-location (QCL) rules, where the rules associate a reference signal (e.g., a synchronization signal such as a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a positioning reference signal (PRS), or other reference signal) with an associated channel property (e.g., one or more spatial parameters such as Doppler shift, Doppler spread, mean delay, delay spread, spatial filter, or other property). Such a QCL rule may include a QCL Type A, QCL Type B, QCL Type C, or QCL Type D data structure defined by the 3GPP specifications.

[0038]

[0045] One type of TCI is a joint downlink and uplink TCI (Type 1 beam indication), which indicates a common beam for at least one downlink channel or reference signal and at least one uplink channel or reference signal. Other types of TCI may include a separate downlink common TCI (Type 2 beam indication), which indicates a common beam for multiple downlink channels or reference signals; a separate uplink common TCI (Type 3 beam indication), which indicates a common beam for multiple uplink channels or reference signals; a separate downlink single-channel TCI (Type 4 beam indication), which may indicate a beam for a single downlink channel or reference signal; a separate uplink single-channel TCI (Type 5 beam indication), which may indicate a beam for a single uplink channel or reference signal; or uplink spatial relationship information (SRI) (Type 6 beam indication), which may indicate a beam for a single uplink channel or reference signal. Other types of TCI are possible and may be defined in standards (such as the 3GPP specifications).

[0039]

[0046] When a BS transmits a DCI scheduling a downlink data transmission to indicate a TCI, the DCI may be, for example, DCI format 1_1 or DCI format 1_2 to indicate a Type 1 beam indication (joint downlink and uplink TCI). Some aspects described herein may define one or more interpretation rules so that a BS may transmit a DCI without downlink data to indicate a TCI. For example, a UE may receive a DCI with one or more configured fields and without downlink data and may interpret the DCI based on the one or more configured fields to identify the TCI. In such an example, the TCI may be a Type 1 beam indication or another type of beam indication. Further, in such examples, the DCI may be DCI format 1_1 or DCI format 1_2, or another DCI format such as DCI format 1_0 or a DCI scheduling uplink configuration, among other examples, and may indicate another configuration with the TCI, such as SPS release, SPS activation, HARQ configuration, or secondary cell dormancy configuration, among other examples. Some aspects described herein may enable a UE to provide a capability report regarding whether the UE supports receiving DCI without downlink data to indicate the TCI. For example, the UE may indicate support for DCI format 1_1 or DCI format 1_2 by transmitting a capability indicator.

[0040]

[0047] Particular implementations of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: As described herein, a UE may receive a DCI that does not schedule data transmission and may communicate according to a TCI associated with one or more configured fields of the DCI. The use of a DCI to identify a TCI that does not schedule data transmission may allow for reduced signaling overhead relative to having information scheduling data transmission included in the DCI that identifies the TCI. Enabling the use of different types of beam indications in the TCI in a DCI may allow for a unified TCI framework that may simplify beam management procedures not only for downlink and uplink channels in 3GPP (NR) systems, but also for data and control channels. Including an explicit beam indication, such as a TCI, in a DCI may increase signaling flexibility, such as when a DCI is being transmitted to indicate another configuration, such as SPS release, SPS activation, HARQ configuration, or secondary cell dormancy configuration, among other examples. By providing a capability indicator for indicating whether a UE supports DCI without downlink data to indicate the TCI, a scenario in which a BS transmits DCI without downlink data to indicate the TCI and the UE is unable to interpret such DCI is avoided. Avoiding the above scenario reduces the likelihood of communication errors from UEs that are unable to interpret such DCI and may enable a BS to operate in a communication system that includes UEs with different capabilities.

[0041]

[0048] FIG. 1 illustrates an example of a wireless network 100. The wireless network 100 may be or include an element of a 5G (NR) network, an LTE network, or another type of network. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, or transmit / receive point (TRP). Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS, the coverage area of ​​a BS subsystem serving this coverage area, or a combination thereof, depending on the context in which the term is used.

[0042]

[0049] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs that have an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB," "base station," "NR BS," "gNB," "TRP," "AP," "Node B," "5G NB," and "cell" may be used interchangeably herein.

[0043]

[0050] In some examples, the cells may not necessarily be fixed, and the geographic area of ​​the cells may move according to the location of the mobile BS. In some examples, the BSs may be interconnected to each other and to one or more other BSs or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, or combinations thereof, using any suitable transport network.

[0044]

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

[0045]

[0052] Wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, or relay BSs, among other examples. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5-40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1-2 watts).

[0046]

[0053] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via wireless or wireline backhaul.

[0047]

[0054] Multiple UEs 120 (e.g., UE 120a, UE 120b, UE 120c, etc.) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), 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 watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium.

[0048]

[0055] Some UEs may be considered machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). The UE 120 may be included in a housing that stores components of the UE 120, such as a processor component, a memory component, or other components. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled, among other examples.

[0049]

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

[0050]

[0057] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a base station 110 as an intermediary for communicating with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a similar protocol), or a mesh network. In such examples, the UEs 120 may perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by the base station 110.

[0051]

[0058] The devices of wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various classes, bands, or channels based on frequency or wavelength. For example, the devices of wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may range from 410 MHz to 7.125 GHz. As another example, the devices of wireless network 100 may communicate using an operating band having a second frequency range (FR2), which may range from 24.25 GHz to 52.6 GHz. 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 the "sub-6 GHz" band. Similarly, FR2 is often referred to as the "millimeter wave" band, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU). Thus, unless otherwise specified, it should be understood that the term "sub-6 GHz" can broadly refer to frequencies below 6 GHz, frequencies within FR1, mid-band frequencies (e.g., greater than 7.125 GHz), or a combination thereof. Similarly, unless otherwise specified, it should be understood that the term "millimeter wave" can broadly refer to frequencies within the EHF band, frequencies within FR2, mid-band frequencies (e.g., less than 24.25 GHz), or a combination thereof. The frequencies included in FR1 and FR2 may vary, and it is contemplated that the techniques described herein are applicable to those varied frequency ranges.

[0052]

[0059] 2 is a diagram illustrating an example base station (BS) 110 200 in communication with a UE 120 in wireless network 100. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general, T≧1 and R≧1.

[0053]

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

[0054]

[0061] At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may 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 processor 258 may process (e.g., demodulate and decode) the detected symbols and provide decoded data for UE 120 to a data sink 260 and may provide decoded control and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other examples. In some aspects, one or more components of the UE 120 may be included in a housing.

[0055]

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

[0056]

[0063] An antenna (such as antennas 234a-234t or antennas 252a-252r) may include or be contained within one or more antenna panels, antenna groups, sets of antenna elements, or antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, or antenna array may include a set of coplanar antenna elements or a set of non-coplanar antenna elements. An antenna panel, antenna group, set of antenna elements, or antenna array may include antenna elements within a single housing or antenna elements within multiple housings. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements coupled to one or more transmitting or receiving components, such as one or more components of FIG. 2.

[0057]

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

[0058]

[0065] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 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 the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication, uplink communication, or a combination thereof. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modulator 232, demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein.

[0059]

[0066] In some implementations, the controller / processor 280 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receive inputs and process the inputs to generate a set of outputs (e.g., that may be passed to other systems or components of the UE 120). For example, the "processing system of the UE 120" may refer to a system that includes various other components or subcomponents of the UE 120.

[0060]

[0067] The processing system of the UE 120 may interface with other components of the UE 120, process information (such as input or signals) received from other components, output information to other components, etc. For example, a chip or modem of the UE 120 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some cases, the "first interface" may refer to the interface between the processing system of the chip or modem and a receiver, such that the UE 120 may receive information or signal input and the information may be passed to the processing system. In some cases, the "second interface" may refer to the interface between the processing system of the chip or modem and a transmitter, such that the UE 120 may transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input and the first interface may also output, transmit, or provide information.

[0061]

[0068] In some implementations, the controller / processor 240 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receive and process inputs to generate a set of outputs (e.g., that may be passed to other systems or components of the base station 110). For example, the "processing system of the base station 110" may refer to a system that includes various other components or subcomponents of the base station 110.

[0062]

[0069] The processing system of the base station 110 may interface with other components of the base station 110, process information (e.g., input or signal) received from other components, output information to other components, etc. For example, a chip or modem of the base station 110 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some cases, the "first interface" may refer to the interface between the processing system and the receiver of the chip or modem, such that the base station 110 may receive information or signal input, and the information may be passed to the processing system. In some cases, the "second interface" may refer to the interface between the processing system and the transmitter of the chip or modem, such that the base station 110 may transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0063]

[0070] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, or any other component of FIG. 2 may implement one or more techniques related to using DCI for beam indication without scheduling data and one or more techniques related to capability reporting, as described in more detail elsewhere herein. Controller / processor 240 of base station 110, controller / processor 280 of UE 120, or any other component (or combination of components) of FIG. 2 may perform or direct the operation of, for example, process 400 of FIG. 4, process 500 of FIG. 5, process 1100 of FIG. 11, process 1200 of FIG. 12, or other processes described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and memory 282 may comprise a non-transitory computer-readable medium that stores one or more instructions (e.g., code or program code) for wireless communication. The one or more instructions, when executed by one or more processors of the base station 110 or UE 120 (e.g., directly or after being compiled, translated, or interpreted), may cause the one or more processors, UE 120, or base station 110 to perform or direct operations of, for example, process 400 of FIG. 4, process 500 of FIG. 5, process 1100 of FIG. 11, process 1200 of FIG. 12, or other processes described herein.

[0064]

[0071] In some aspects, the UE 120 may include, among other examples, means for transmitting a DCI having a DCI format, the DCI including one or more configured fields, and means for communicating in accordance with a TCI associated with the one or more configured fields, where the DCI does not include scheduling data, means for transmitting a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, or means for communicating in accordance with the capability indicator. In some aspects, such means may include one or more components of the UE 120 described with respect to FIG. 2, such as the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antennas 252, the DEMOD 254, the MIMO detector 256, or the receive processor 258.

[0065]

[0072] In some aspects, the base station 110 may include, among other examples, means for transmitting a DCI having a DCI format, the DCI including one or more configured fields, and the DCI not including scheduling data, means for communicating in accordance with a TCI associated with the one or more configured fields, means for receiving a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, or means for communicating in accordance with the capability indicator. In some aspects, such means may include one or more components of the base station 110 described with respect to FIG. 2, such as the antennas 234, the DEMOD 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the transmit processor 220, the TX MIMO processor 230, the MOD 232, or the antennas 234.

[0066]

[0073] 2 are shown as separate components, the functionality described above with respect to those blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, TX MIMO processor 266, or another processor may be performed by or under the control of controller / processor 280.

[0067]

[0074] 3 is a diagram illustrating an example 300 of using beams for communication between a base station (BS) and a UE. As shown in FIG. 3, a base station 110 and a UE 120 may communicate with each other.

[0068]

[0075] The base station 110 may transmit to a UE 120 located within the coverage area of ​​the base station 110. The base station 110 and the UE 120 may be configured for beamformed communications, where the base station 110 may transmit in the direction of the UE 120 using a directional BS transmit beam, and the UE 120 may receive the transmission using a directional UE receive beam. Each BS transmit beam may have an associated beam ID, beam direction, or beam symbol, among other examples. The base station 110 may transmit downlink communications via one or more BS transmit beams 305.

[0069]

[0076] The UE 120 may attempt to receive downlink transmissions via one or more UE receive beams 310, which may be configured using different beamforming parameters in the receive circuitry of the UE 120. The UE 120 may identify a particular BS transmit beam 305, denoted as BS transmit beam 305-A, and a particular UE receive beam 310, denoted as UE receive beam 310-A, that provides relatively advantageous performance (e.g., has the best channel quality of different measured combinations of BS transmit beams 305 and UE receive beams 310). In some examples, the UE 120 may transmit an indication of which BS transmit beam 305 is identified by the UE 120 as the BS transmit beam that the base station 110 may select for transmission to the UE 120. In this manner, the UE 120 may achieve and maintain a beam pair link (BPL) (e.g., a combination of the BS transmitting beam 305-A and the UE receiving beam 310-A) with the base station 110 for downlink communications, and this BPL may be further refined and maintained in accordance with one or more established beam refinement procedures.

[0070]

[0077] A downlink beam, such as a BS transmit beam 305 or a UE receive beam 310, may be associated with a TCI state. The TCI state may indicate the directionality or characteristics of the downlink beam, such as one or more QCL properties of the downlink beam. The QCL properties may include, for example, Doppler shift, Doppler spread, mean delay, delay spread, or spatial reception parameters, among other examples. In some examples, each BS transmit beam 305 may be associated with an SSB, and the UE 120 may indicate the BS transmit beam 305 by sending an uplink transmission in resources of the SSB associated with the BS transmit beam 305. A particular SSB may have an associated TCI state (e.g., for antenna port or beamforming). The base station 110 may indicate the downlink BS transmit beam 305 based on antenna port QCL properties, which may be indicated by the TCI state, in some examples. A TCI state may be associated with one downlink reference signal set (e.g., SSB and aperiodic, periodic, or semi-persistent CSI-RS) for different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, mean delay, delay spread, or spatial reception parameters, among other examples). If the QCL type indicates spatial reception parameters, the QCL type may correspond to analog receive beamforming parameters of the UE receive beam 310 at the UE 120. Thus, the UE 120 may select a corresponding UE receive beam 310 from the set of BPLs based on the base station 110 indicating the BS transmit beam 305 via the TCI indication.

[0071]

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

[0072]

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

[0073]

[0080] The base station 110 may receive uplink transmissions via one or more BS receive beams 320. The base station 110 may identify a particular UE transmit beam 315, denoted as UE transmit beam 315-A, and a particular BS receive beam 320, denoted as BS receive beam 320-A, that provides relatively advantageous performance (e.g., has the best channel quality of different measured combinations of UE transmit beam 315 and BS receive beam 320). In some examples, the base station 110 may transmit an indication of which UE transmit beam 315 the base station 110 has identified as a UE transmit beam that the base station 110 may select for transmissions from the UE 120. The UE 120 and the base station 110 may thus achieve and maintain a BPL (e.g., a combination of the UE transmit beam 315-A and the BS receive beam 320-A) for uplink communications, which may be further refined and maintained according to one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam 315 or a BS receive beam 320, may be associated with a spatial relationship, which may indicate the directionality or characteristics of the uplink beam, as well as one or more QCL properties, as described herein.

[0074]

[0081] 4 illustrates an example process 400, performed, for example, by a UE. Process 400 is an example of a UE (e.g., UE 120) performing operations related to using DCI for beam indication without scheduling data.

[0075]

[0082] 4, in some aspects, process 400 may include receiving a DCI having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data (block 410). For example, a UE may receive a DCI having a DCI format as described herein (such as by using the receiving component 602 shown in FIG. 6), where the DCI includes one or more configured fields, and where the DCI does not include scheduling data. In some aspects, the UE may include a first interface configured to obtain the DCI having the DCI format.

[0076]

[0083] 4, in some aspects, process 400 may include communicating according to a TCI associated with the one or more configured fields (block 420). For example, the UE may communicate according to a TCI associated with the one or more configured fields as described herein (such as by using the receiving component 602 or the transmitting component 604 shown in FIG. 6). In some aspects, the UE may include a first interface or a second interface configured to obtain or output information according to the TCI.

[0077]

[0084] Process 400 may include additional aspects, such as any single aspect or any combination of aspects, related to one or more other processes described below or elsewhere herein.

[0078]

[0085] In a first additional aspect, the DCI format is DCI format 1_1 or DCI format 1_2.

[0079]

[0086] In a second additional aspect, the DCI includes an indication of the TCI and does not include an indication of another type.

[0080]

[0087] In a third additional aspect, the DCI format is DCI format 1_0 or an uplink DCI format.

[0081]

[0088] In a fourth additional aspect, the DCI includes a first indication of the TCI and a second indication of another setting.

[0082]

[0089] In a fifth additional aspect, the second indication includes at least one of a secondary cell dormant indication, a semi-persistent scheduling release indication, a semi-persistent scheduling activation indication, or a hybrid automatic repeat request indication.

[0083]

[0090] In a sixth additional aspect, the TCI is based on a value of a TCI field parameter of the DCI.

[0084]

[0091] In a seventh additional aspect, the TCI is based on values ​​of non-TCI field parameters of the DCI.

[0085]

[0092] In an eighth additional aspect, the TCI is based on one or more CORESET beams of the DCI.

[0086]

[0093] In a ninth additional aspect, the DCI indicates a single TCI, the TCI being associated with a TCI pool, and the process 400 further includes configuring multiple TCIs associated with the TCI pool based on the TCI.

[0087]

[0094] In a tenth additional aspect, the DCI indicates a plurality of TCIs.

[0088]

[0095] In an eleventh additional aspect, the DCI includes a TCI field indicating an identifier of a set of TCIs.

[0089]

[0096] In a twelfth additional aspect, the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from multiple configured groupings of TCIs having a common attribute.

[0090]

[0097] In a thirteenth additional aspect, the TCI includes a downlink TCI and an uplink TCI.

[0091]

[0098] In a fourteenth additional aspect, the TCI is based on a radio network temporary identifier (RNTI) associated with the DCI.

[0092]

[0099] In a fifteenth additional aspect, the TCI is based on a mandatory field of the DCI.

[0093]

[0100] In a sixteenth additional aspect, the TCI is based on a validation sequence configured for the beam indication.

[0094]

[0101] In a seventeenth additional aspect, the TCI is based on a value of a validation sequence associated with a non-TCI configuration.

[0095]

[0102] In an eighteenth additional aspect, the process 400 further includes transmitting a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and communicating according to the capability indicator.

[0096]

[0103] In a nineteenth additional aspect, a configured field associated with the TCI is not present in one or more configured fields of the DCI, and the UE is configured to determine the TCI based on at least one of another DCI, another indicator that is not a DCI, another configured field that is present in one or more configured fields of the DCI, or a default configuration.

[0097]

[0104] 4 illustrates example blocks of process 400, in some aspects process 400 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIGURE 4. Additionally or alternatively, two or more of the blocks of process 400 may be performed in parallel.

[0098]

[0105] 5 illustrates an example process 500, performed, for example, by a base station (BS). Process 500 is an example of a base station (e.g., base station 110) performing operations related to using DCI for beam indication without scheduling data.

[0099]

[0106] 5, in some aspects, process 500 may include transmitting a DCI having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data (block 510). For example, a base station may transmit a DCI having a DCI format as described herein (such as by using the transmitting component 704 shown in FIG. 7), where the DCI includes one or more configured fields, and where the DCI does not include scheduling data. In some aspects, the base station may include a first interface configured to output the DCI having the DCI format.

[0100]

[0107] 5, in some aspects, process 500 may include communicating according to a transmission control indicator (TCI) associated with the one or more configured fields (block 520). For example, a base station may communicate according to a TCI associated with the one or more configured fields (such as by using the receiving component 702 or the transmitting component 704 shown in FIG. 7) as described herein. In some aspects, the base station may include a first interface or a second interface configured to output or obtain information according to the TCI.

[0101]

[0108] Process 500 may include additional aspects, such as any single aspect or any combination of aspects, related to one or more other processes described below or elsewhere herein.

[0102]

[0109] In a first additional aspect, the DCI format is DCI format 1_1 or DCI format 1_2.

[0103]

[0110] In a second additional aspect, the DCI includes an indication of the TCI and does not include an indication of another type.

[0104]

[0111] In a third additional aspect, the DCI format is DCI format 1_0 or an uplink DCI format.

[0105]

[0112] In a fourth additional aspect, the DCI includes a first indication of the TCI and a second indication of another setting.

[0106]

[0113] In a fifth additional aspect, the second indication includes at least one of a secondary cell dormant indication, a semi-persistent scheduling release indication, a semi-persistent scheduling activation indication, or a hybrid automatic repeat request indication.

[0107]

[0114] In a sixth additional aspect, the TCI is based on a value of a TCI field parameter of the DCI.

[0108]

[0115] In a seventh additional aspect, the TCI is based on values ​​of non-TCI field parameters of the DCI.

[0109]

[0116] In an eighth additional aspect, the TCI is based on one or more CORESET beams of the DCI.

[0110]

[0117] In a ninth additional aspect, the DCI indicates a single TCI, the TCI being associated with a TCI pool, and the process 500 further includes communicating according to multiple TCIs associated with the TCI pool based on the TCI.

[0111]

[0118] In a tenth additional aspect, the DCI indicates a plurality of TCIs.

[0112]

[0119] In an eleventh additional aspect, the DCI includes a TCI field indicating an identifier of a set of TCIs.

[0113]

[0120] In a twelfth additional aspect, the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from multiple configured groupings of TCIs that have a common attribute.

[0114]

[0121] In a thirteenth additional aspect, the TCI includes a downlink TCI and an uplink TCI.

[0115]

[0122] In a fourteenth additional aspect, the TCI is based on an RNTI associated with the DCI.

[0116]

[0123] In a fifteenth additional aspect, the TCI is based on a required field of the DCI.

[0117]

[0124] In a sixteenth additional aspect, the TCI is based on a verification sequence configured for beam indication.

[0118]

[0125] In a seventeenth additional aspect, the TCI is based on a value of a validation sequence associated with a non-TCI configuration.

[0119]

[0126] In an eighteenth additional aspect, process 500 includes receiving a capability indicator, where the capability indicator is associated with whether the UE supports DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data, and communicating according to the capability indicator.

[0120]

[0127] 5 illustrates example blocks of process 500, in some aspects process 500 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIGURE 5. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0121]

[0128] 6 is a block diagram of an example apparatus 600 for wireless communication. The apparatus 600 may be a UE, or the UE may include the apparatus 600. In some aspects, the apparatus 600 includes a receiving component 602 and a transmitting component 604, which may be in communication with each other (e.g., via one or more buses or one or more other components). As shown, the apparatus 600 may communicate with another apparatus 606 (such as a UE, a base station, or another wireless communication device) using the receiving component 602 and the transmitting component 604. As shown, the apparatus 600 may include one or more of the determining components 608, among other examples.

[0122]

[0129] In some aspects, apparatus 600 may be configured to perform one or more operations described herein. Additionally or alternatively, apparatus 600 may be configured to perform one or more processes described herein, such as process 400 of FIG. 4 or process 1100 of FIG. 11, among other examples. In some aspects, apparatus 600 or one or more components shown in FIG. 6 may include one or more components of the UE described above with respect to FIG. 2. Additionally or alternatively, one or more components shown in FIG. 6 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored on a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0123]

[0130] The receiving component 602 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 606. The receiving component 602 may provide the received communications to one or more other components of the device 600. In some aspects, the receiving component 602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 606. In some aspects, the receiving component 602 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of a UE described above with respect to FIG. 2. In some aspects, the receiving component 602 may be a component of a processing system. For example, a “processing system of the device 600” may refer to a system that includes various other components or sub-components of the device 600.

[0124]

[0131] The transmitting component 604 may transmit a communication to the device 606, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 606 may generate a communication and provide the generated communication to the transmitting component 604 for transmission to the device 606. In some aspects, the transmitting component 604 may perform signal processing on the generated communication (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signal to the device 606. In some aspects, the transmitting component 604 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE described above with respect to FIG. 2. In some aspects, the transmitting component 604 may be co-located with the receiving component 602 in a transceiver. In some aspects, the transmitting component 604 may be a component of a processing system.

[0125]

[0132] The processing system of device 600 may interface with other components of device 600, process information (e.g., input or signal) received from other components, output information to other components, etc. For example, a chip or modem of device 600 may include a processing system, a receiving component 602 for receiving or acquiring information, and a transmitting component 604 for outputting, transmitting, or providing information. In some cases, the receiving component 602 may refer to an interface between the processing system and a receiver of the chip or modem, such that device 600 may receive information or signal input, and the information may be passed to the processing system. In some cases, the transmitting component 604 may refer to an interface between the processing system and a transmitter of the chip or modem, such that device 600 may transmit information output from the chip or modem. One skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0126]

[0133] The receiving component 602 may receive a downlink control information (DCI) having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data. The receiving component 602 or the transmitting component 604 may communicate according to a transmission control indicator (TCI) associated with the one or more configured fields. The determining component 608 may determine the TCI based on the one or more configured fields of the DCI. The transmitting component 604 may transmit a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data. The receiving component 602 or the transmitting component 604 may communicate according to the capability indicator.

[0127]

[0134] 7 is a block diagram of an example apparatus 700 for wireless communication. The apparatus 700 may be a base station, or a base station may include the apparatus 700. In some aspects, the apparatus 700 includes a receiving component 702 and a transmitting component 704, which may be in communication with each other (e.g., via one or more buses or one or more other components). As shown, the apparatus 700 may communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device) using the receiving component 702 and the transmitting component 704. As shown, the apparatus 700 may include one or more of the configuring components 708, among other examples.

[0128]

[0135] In some aspects, apparatus 700 may be configured to perform one or more operations described herein. Additionally or alternatively, apparatus 700 may be configured to perform one or more processes described herein, such as process 500 of FIG. 5 or process 1200 of FIG. 12, among other examples. In some aspects, apparatus 700 or one or more components shown in FIG. 7 may include one or more components of the base station described above with respect to FIG. 2. Additionally or alternatively, one or more components shown in FIG. 7 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored on a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0129]

[0136] The receiving component 702 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 706. The receiving component 702 may provide the received communications to one or more other components of the apparatus 700. In some aspects, the receiving component 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the apparatus 706. In some aspects, the receiving component 702 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of a base station described above with respect to FIG. 2. In some aspects, the receiving component 702 may be a component of a processing system. For example, the processing system of the apparatus 700 may refer to a system that includes various other components or sub-components of the apparatus 700.

[0130]

[0137] The transmitting component 704 may transmit a communication to the device 706, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 706 may generate a communication and provide the generated communication to the transmitting component 704 for transmission to the device 706. In some aspects, the transmitting component 704 may perform signal processing on the generated communication (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signal to the device 706. In some aspects, the transmitting component 704 may 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 base station described above with respect to FIG. 2. In some aspects, the transmitting component 704 may be co-located with the receiving component 702 in a transceiver. In some aspects, the transmitting component 704 may be a component of a processing system. For example, the processing system of the device 700 may refer to a system that includes various other components or sub-components of the device 700.

[0131]

[0138] The processing system of device 700 may interface with other components of device 700, process information (e.g., input or signal) received from other components, output information to other components, etc. For example, a chip or modem of device 700 may include a processing system, a receiving component 702 for receiving or acquiring information, and a transmitting component 704 for outputting, transmitting, or providing information. In some cases, the receiving component 702 may refer to an interface between the processing system and a receiver of the chip or modem, such that device 700 may receive information or signal input, and the information may be passed to the processing system. In some cases, the transmitting component 704 may refer to an interface between the processing system and a transmitter of the chip or modem, such that device 700 may transmit information output from the chip or modem. One skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0132]

[0139] The transmitting component 704 may transmit a downlink control information (DCI) having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data. The receiving component 702 or the transmitting component 704 may communicate according to a transmission control indicator (TCI) associated with the one or more configured fields. The configuring component 708 may configure one or more configured fields of the DCI. The receiving component 702 may receive a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data. The receiving component 702 or the transmitting component 704 may communicate according to the capability indicator.

[0133]

[0140] 8 to 10 are diagrams relating to an exemplary embodiment of the present disclosure.

[0134]

[0141] We note how DCI should be used to update beam indication in a unified TCI framework. The unified TCI framework includes common beam indication types. A device can use DCI format 1_1 or 1_2 with a DL allocation to indicate a joint downlink (DL) / uplink (UL) TCI status. We note whether or how DCI should be used to indicate a TCI status without scheduling DL data. For DCI-based beam indication, regarding support for DCI formats for beam indication, in addition to DCI format 1_1 / 1_2 with a DL allocation, selecting at least one of the following alternatives is considered: Alternative 0 - No additional DCI format is supported. DCI formats 1_1 and 1_2 without a DL allocation are applicable for joint TCI as well as separate DL / UL TCI. In such cases, support for DCI acknowledgment mechanisms (based on SPS PDSCH release, triggered SRS, or DCI indicating SCell dormancy, among other examples) can be configured. The problem of how to identify DCI formats 1_1 / 1_2 used only for beam indication (not for scheduling PDSCH reception, not for indicating SPS PDSCH release, or not for indicating SCell dormancy) can be solved by considering the impact on PDCCH coverage and scheduling mechanisms. Whether the UE can assume that the application time configured at the BS is after an acknowledgment (ACK) transmission can be solved. Some aspects provide dedicated DCI formats other than 1_1 / 1_2 without DL allocation that are applicable for joint TCI as well as separate DL / UL TCI. Support for DCI acknowledgment mechanisms (based on SPS PDSCH release, based on triggered SRS, based on DCI indicating SCell dormancy, among other examples) can be configured. If the format is based on an existing DCI format, how to identify a DCI format used only for beam indication can be solved.It can be resolved whether the UE can / shall assume that the application time configured in the gNB is after the ACK transmission. Alternative-3 UL-related DCI format 0_1 / 0_2 with UL grant, applicable only for UL-only TCI of separate DL / UL TCI.

[0135]

[0142] On the beam indication signaling medium to support joint or separate DL / UL beam indication in a unified TCI framework, devices may support Layer 1 (L1)-based beam indication using at least a UE-specific (unicast) DCI to indicate joint or separate DL / UL beam indication from an active TCI state. DCI formats 1_1 and 1_2 may be reused for joint beam indication. It may be possible to support additional DCI formats (existing DCI formats 0_0, 0_1, 0_2, 1_0, as well as new DCI formats dedicated to beam indication).

[0136]

[0143] The following three types of TCI states are considered: a joint DL / UL common TCI state for indicating a common beam for at least one DL channel / RS plus at least one UL channel / RS; a separate DL common TCI state for indicating a common beam for two or more DL channels / RS; and a separate UL common TCI state for indicating a common beam for two or more UL channels / RS. In NR Further enhanced MIMO (FeMIMO), on the unified TCI framework, a device may support joint TCI for DL ​​and UL based on and similar to the DL TCI framework. The term "TCI" may include at least a TCI state including at least one source RS to provide a reference (UE assumption) for determining a QCL or spatial filter. In the unified TCI framework, to accommodate the case of separate beam indications for UL and DL, a device may utilize two separate TCI states, one for DL ​​and one for UL. For separate DL TCIs, the source reference signals in M ​​TCIs provide QCL information for at least UE-dedicated reception on the PDSCH and for UE-dedicated reception on all or a subset of the CORESET in a component carrier (CC). For separate UL TCIs, the source reference signals in N TCIs provide a basis for determining a common UL transmit (TX) spatial filter for at least the dynamic grant / configured grant-based physical uplink shared channel (PUSCH) and for all or a subset of the dedicated PUCCH resources in a CC. In some cases, this UL TX spatial filter may also be applied to all SRS resources in the resource set configured for antenna-switched / codebook-based / non-codebook-based UL transmission.

[0137]

[0144] Beam indication types: Type 1 - Joint DL / UL common TCI state to indicate a common beam for at least one DL channel / RS + at least one UL channel / RS, Type 2 - Separate DL common TCI state to indicate a common beam for two or more DL channels / RS, Type 3 - Separate UL common TCI state to indicate a common beam for two or more UL channels / RS, Type 4 - Separate DL single channel / RS TCI state to indicate a beam for a single DL channel / RS, Type 5 - Separate UL single channel / RS TCI state to indicate a beam for a single UL channel / RS, Type 6 - UL Spatial Relationship Information (SRI) to indicate a beam for a single UL channel / RS.

[0138]

[0145] Some aspects described herein may describe methods for using a DCI to indicate TCI status without scheduling data and for capability reporting. A BS may indicate to a UE that the DCI does not schedule data transmission. The UE may distinguish from DCIs intended for other purposes (which also do not schedule data). The DCI may enable SPS release / activation, request Type 3 HARQ, or provide secondary cell idle indication, among other examples. The BS and UE may use DCI formats 1_1 and 1_2. The DCI may indicate only one purpose at a time. The BS and UE may use other DCI formats (DCI format 1_0 and UL format). The DCI can indicate more than one purpose (TCI indication and secondary cell idle indication, among other examples).

[0139]

[0146] FIG. 8 is an example of the association between DCI formats and the indicated configurations.

[0140]

[0147] The verification sequence may depend on the resource allocation type: resourceAllocation=resourceAllocationType0 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or resourceAllocation=resourceAllocationType1 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1, or resourceAllocation=dynamicSwitch and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0 or 1.

[0141]

[0148] For DCI formats 1_1 and 1_2, which may include a TCI field in the DCI, if tci-PresentInDCI is set as "enabled" (or tci-PresentForDCI-Format1-2-r16 is configured for CORESET), the device may use the TCI field in DCI format 1_1 or (1_2) to indicate the TCI state ID. In other cases, among other examples, the following options may be possible: Option 1: The UE does not expect to receive a DCI that does not include a TCI field to indicate the TCI state (without scheduling data). Option 2: The DCI may include another field to indicate the TCI state ID. Option 3: An implicit method may be used (the indicated beam is determined based on the CORESET beam in the DCI). In a multiple DCI (mDCI) multiple transmission / reception point (mTRP) scenario, the indicated beam is the CORESET beam and may be used for channels / RSs scheduled by the same CORESET pool identifier (ID). In the case of a single DCI (sDCI) mTRP, the indicated TCI state may be determined based on the CORESET beam (if the CORESET beam carrying the DCI corresponds to the TCI codepoints of two TCI states, the CORESET beam is the indicated beam; if the CORESET beam carrying the DCI corresponds to a single TCI state, find the lowest ID TCI codepoint that corresponds to the TCI state pair containing the CORESET TCI state). For DCI format 1_0 or UL DCI format, devices may use options 1-3 because the options do not include a TCI state field. For UL DCI format, devices may use the SRI (or UL TCI state) field, if present, to indicate the TCI state ID.

[0142]

[0149] There may be options regarding whether both DL and UL TCI states can be signaled in one instance of a beam indication DCI. Option 1—One DCI can indicate only one TCI state. In such a case, the UE may be configured in different TCI state pools and use additional bits or other signaling to identify which TCI state pool the DCI refers to, such as the UL TCI state pool or the DL TCI state pool; all TCI states may be configured in the same pool, and the UE may use other fields as well as the TCI state to indicate the TCI state. Option 2—One DCI can indicate two or more TCI states, where the multiple TCI states can include one DL and one UL. Option 2-1—There may be direct indication of multiple TCI states in the DCI. In such a case, the DCI may use the TCI field to indicate one TCI and another unused field (the modulation and coding scheme (MCS) field) to indicate another TCI. A field (TCI field) is used to indicate the ID of the Option 2-2-TCI pair / set. The pairing / grouping of the Option 2-2-1-TCI state is configured by BS signaling, and the DCI indicates the ID of the pairing / grouping. The Option 2-2-2-TCI field indicates an index, and the TCI state corresponding to the index in each pool / group is indicated. In such a case, multiple pools / groups may be pre-configured by the BS. As an example, if the DCI indicates index "1" in the TCI field, both TCI states indexed as "1" (in the DL and UL TCI state pools) are indicated.

[0143]

[0150] In the case of a DCI that can indicate only one purpose at a time, to distinguish with DCIs for indicating other purposes, the beam indication DCI may use at least one of the following options from the indication method for other purposes (among examples: SPS release / activation, Type 3 HARQ request, secondary cell (SCell) dormancy): different RNTI, different DCI format, at least one different field used for verification, different verification sequence in the same verification field.

[0144]

[0151] 9 is an example of an association between an RNTI or DCI format and a configuration indicated in a DCI. With respect to FIG. 9, a new RNTI for beam indication may be defined, a new DCI format for beam indication may be defined, or the BS may use a combination of an RNTI and a DCI format that is not used for other purposes. For example, the BS may use a C-RNTI or MCS-C-RNTI and format 1_0 or 1_2 (or UL) for the indication TCI state. For DCI format 1_0 or 1_2, the verification sequence / fields can be any possible combination. For example, the BS may reuse the SPS / UL Type 2 release format. In such a case, for DCI format 1_0, the BS may use the HARQ process ID field or the time domain resource allocation (TDRA) to indicate the TCI state ID.

[0145]

[0152] Figure 10 is an example of the use of verification information in DCI fields. For example, the BS may use fields that are mandatory (optionally absent) in the DCI format. The new verification field, which is not mandatory, may not be used in favor of information fields for other purposes. In addition to or instead of the DCI fields shown in Figure 10, for DCI1_1, possible fields include, among other examples, a TPC command for scheduled PUCCH (2 bits), a PUCCH resource indicator (2 bits), or an SRS request (3 bits), and for DCI1_2, possible fields include a TPC command for scheduled PUCCH (2 bits).

[0146]

[0153] In some aspects, when a DCI uses different DCI fields for verification than those used for other purposes, a UE such as UE 120 may identify a received DCI used to indicate a TCI configuration without scheduling a downlink assignment. For example, when the received DCI uses DCI format 1_1 or 1_2 in which the CRC is scrambled by the C-RNTI or MCS-C-RNTI, when the one-shot HARQ request is '0' or not available, when bits in the FDRA field are all '1' or '0' (based on the resource allocation type), and when bits in fields not used by other verification purposes (TPC commands for a scheduled PUCCH match a configured sequence, such as when the field is all '1'), the UE may determine that the DCI indicates a TCI state without scheduling data. The TCI state ID may be indicated in the TCI state field (if tci-PresentInDCI is set as "enabled" or if tci-PresentForDCI-Format1-2-r16 is configured for CORESET). Alternatively, the BS may use at least one of the MCS field, the New Data Indicator (NDI) field, or the Redundancy Version (RV) field, among other examples, to indicate the TCI state.

[0147]

[0154] In some aspects, a DCI for a beam indication that does not schedule a downlink assignment may use the same DCI format indicator, the same type of RNTI to scramble the CRC bits of the DCI, or the same field for verification as in other indication purposes such as SPS activation / release, Type 3 HARQ request, or secondary cell dormancy indication. In such cases, a new verification sequence for the beam indication may be defined to distinguish the purpose of the DCI (beam indication) from other indication purposes using the same verification field. For example, a DCI for indicating a TCI status to a UE may use the same DCI format, the same RNTI to scramble the CRC bits, and the same field for verification as a DCI for indicating an SPS release to a UE. In this example, a first verification sequence is defined differently for a DCI for indicating a TCI status relative to a second verification sequence for indicating an SPS release (in at least one of the verification fields). As an example, the RV field verification sequence may be defined as all '1's for beam indication purposes and all '0's for SPS release or activation. In this way, the UE can determine the indication purpose by examining the bits in the RV field of the received DCI.

[0148]

[0155] In another example, the BS may use the CS-RNTI to scramble the CRC and may use DCI format 1_0, 1_1, or 1_2. In such a case, if the NDI is '0' and, among other examples, if at least one of the MCS field, RV field, or FDRA field uses a configured sequence that is different from the configured sequence used for SPS release or activation (defining at least one of the following: RV = all '1', MCS = all '1', or FDRA uses a configured sequence other than all '0' or all '1', and other fields in MCS, RV, or FDRA may use the same sequence as SPS), the UE may determine that the DCI indicates a TCI state. The DCI may use the TCI field, if present, to indicate the TCI state ID. In other cases, the DCI may use another reserved field, such as the FDRA field, HARQ field, or antenna port field, among other examples, to indicate the TCI state ID. In some aspects, rules may be defined such that a validation sequence for beam indication is not included in the same field of DCI intended to indicate other purposes.

[0149]

[0156] In addition to or as an alternative to the fields used for verification purposes and the field for indicating the TCI state ID, a DCI format used for beam indication (without scheduling a data transmission allocation) may include information bits in one or more additional fields. For example, a DCI format may be defined to include information bits for a DCI format indicator, a TDRA, an identifier of the DCI format, a carrier indicator, a bandwidth part (BWP) indicator, a downlink allocation index (if configured), a TPC command for the scheduled PUCCH, a PUCCH resource indicator, or a PDSCH to HARQ feedback timing indicator (if present), among other examples. In some aspects, one or more fields may be used to indicate information for locating the time or frequency resource of an ACK for a DCI or for power control parameters of a PUCCH for carrying an ACK for a DCI. In some aspects, one or more fields may be used to indicate information about the indicated TCI state, such as the power control configuration of an uplink transmission associated with the indicated TCI state.

[0150]

[0157] In some aspects, one or more fields defined for a DCI format and used for verification or information may be omitted from a DCI of a DCI format when the DCI is used for beam indication without scheduling data. For example, one or more evaluation rules may be defined to enable omission of a defined field from a DCI without preventing verification or information transmission for beam indication. In some aspects, when a defined field for verification or for indicating information is not present in the DCI, the UE is not expected to receive a DCI for indicating a TCI status ID. Alternatively, when a defined field is not present in the DCI format, an additional field may be used for verification or for indicating information. In some aspects, the UE may determine a reserved sequence of bits to enable interpretation of the DCI for the absent field. For example, the RV field may be used for verification in a DCI to indicate a TCI status without scheduling data, and the RV field may not be present or configured in a DCI of DCI format 1_2. In this example, the UE may be configured not to receive a DCI in format 1_2 to indicate a TCI status without scheduling data. Alternatively, when the RV field is not present in the RV field, the UE may be configured to assume a predefined sequence, such as "0" in the field. Alternatively, rules may be defined so that the UE can use an alternative field (such as the MCS field) for verification. Similar rules may apply in cases where other fields used to indicate TCI status information or additional information are not present in the DCI. For example, if a configured field is not included in the DCI, the UE may use a configured alternative field for verification. Additionally or alternatively, the UE may use a configured default sequence for verification. Additionally or alternatively, the UE may use another DCI.

[0151]

[0158] Some BSs and UEs may not support indication of more than one purpose at a time (TCI indication and at least one of SPS activation / release, Type 3 HARQ request, and SCell dormancy indication, among other examples). In such cases, the UE does not expect to receive a DCI to indicate the TCI state as well as the other purposes. Some aspects herein enable the use of a single DCI to indicate the TCI state and at least one of SPS activation / release, Type 3 HARQ, and SCell dormancy, among other examples. The BSs and UEs may use different combinations of validation fields and sequences than the single-purpose case in the DCI to indicate that the DCI indicates multiple purposes.

[0152]

[0159] In one aspect, a DCI format may be defined to indicate the TCI state and SPS activation or release. For example, a BS may use the CS-RNTI in association with DCI format 1_0, 1_1, or 1_2. In such a case, if the NDI and RV fields are all "0" and the MCS field is a configured reserved index for initial TX that is different from the index used for TCI indication only (or SPS / UL release / activation only), the UE may determine that the DCI indicates the TCI state and SPS release / activation. In such a case, the DCI may use the TCI field, if present, to indicate the TCI state ID. In other cases, the DCI may use the FDRA field to indicate the TCI state ID. The DCI may use the HARQ process ID field to indicate the configuration of SPS release / activation.

[0153]

[0160] When using DCI format 1_1 in which the CRC is scrambled by the C-RNTI or modulation and coding scheme (MCS)-specific C-RNTI (MCS-C-RNTI), and when the One-Shot HARQ Request field is set to '1', the FDRA field is set to '1' or '0' based on the resource allocation type, and the TPC command for the scheduled PUCCH matches a configured sequence different from the sequence used in the case indicating TCI only, the UE may determine that the DCI indicates a TCI state and request Type 3 HARQ without scheduling data. In such cases, the TCI State ID is indicated in the TCI State field if tci-PresentInDCI is set as 'enabled' (or tci-PresentForDCI-Format1-2-r16 is configured for CORESET). In other cases, the DCI may use at least one of the MCS field, NDI field, or RV field, among other examples, to indicate the TCI state.

[0154]

[0161] When using DCI format 1_1, in which the CRC is scrambled by the C-RNTI or MCS-C-RNTI, when the One-Shot HARQ Request field is absent or set to '0', when the FDRA field is '1' or '0' (based on the resource allocation type), and when the TPC command for the scheduled PUCCH matches a configured sequence different from the sequence used in the case indicating only TCI, the UE may determine that the DCI indicates a TCI state and request Type 3 HARQ without scheduling data. In such cases, the TCI State ID is indicated in the TCI State field if tci-PresentInDCI is set as 'enabled' (or tci-PresentForDCI-Format1-2-r16 is configured for CORESET). In other cases, the DCI may use at least one of the PUCCH resource indicator or SRS request, among other examples, to indicate the TCI state. The DCI may use the same field as shown in Figure 10 to indicate the SCell dormancy bitmap.

[0155]

[0162] 11 illustrates an example process 1100, performed by, for example, an apparatus, in which a UE (e.g., UE 120) performs operations related to a capability indication in a DCI for beam indication without scheduling data.

[0156]

[0163] 11, in some aspects, process 1100 may include transmitting a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format (block 1110). For example, the UE may transmit a capability indicator (such as by using the transmitting component 604 shown in FIG. 6) as described herein, where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data. In some aspects, the UE may include a first interface configured to output the capability indicator.

[0157]

[0164] 11, in some aspects, the process 1100 may include communicating according to the capability indicator (block 1120). For example, the UE may communicate according to the capability indicator (such as by using the receiving component 602 or the transmitting component 604 shown in FIG. 6) as described herein. In some aspects, the UE may include a first interface or a second interface configured to obtain or output a communication according to the capability indicator.

[0158]

[0165] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects, related to one or more other processes described below or elsewhere herein.

[0159]

[0166] In a first additional aspect, the one or more configured fields are associated with the TCI.

[0160]

[0167] In a second additional aspect, the capability indicator identifies UE support for DCI having a DCI format.

[0161]

[0168] In a third additional aspect, the process 1100 includes receiving a DCI having a DCI format, and communicating according to the capability indicator includes communicating according to a TCI associated with one or more configured fields.

[0162]

[0169] In a fourth additional aspect, the capability indicator is included in an optional field of an uplink control information (UCI) message.

[0163]

[0170] In a fifth additional aspect, the capability indicator is a single capability indicator that indicates support for a DCI format that does not include scheduling data and another DCI format that does include scheduling data.

[0164]

[0171] In a sixth additional aspect, the capability indicator is a first capability indicator that indicates support for a DCI format that does not include scheduling data.

[0165]

[0172] In a seventh additional aspect, the process 1100 includes transmitting a second capability indicator indicating support for another DCI format including the scheduling data, and communicating in accordance with the capability indicator includes communicating in accordance with the first capability indicator and the second capability indicator.

[0166]

[0173] 11 illustrates example blocks of process 1100, in some aspects process 1100 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIGURE 11. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0167]

[0174] 12 illustrates an example process 1200, performed by, for example, an apparatus. Process 1200 is an example of a base station (e.g., base station 110) performing operations related to a capability indication in a DCI for beam indication without scheduling data.

[0168]

[0175] 12, in some aspects, process 1200 may include receiving a capability indicator, where the capability indicator is associated with whether the UE supports a DCI having a DCI format (block 1210). For example, a base station may receive a capability indicator as described herein (such as by using receiving component 702 shown in FIG. 7), where the capability indicator is associated with whether the UE supports a DCI having a DCI format, where the DCI format includes one or more configured fields, and where the DCI format does not include scheduling data. In some aspects, the BS may include a first interface configured to obtain the capability indicator.

[0169]

[0176] 12, in some aspects, process 1200 may include communicating in accordance with the capability indicator (block 1220). For example, the base station may communicate in accordance with the capability indicator (such as by using the receiving component 702 or the transmitting component 704 shown in FIG. 7) as described herein. In some aspects, the BS may include a first interface or a second interface configured to output or obtain a communication in accordance with the capability indicator.

[0170]

[0177] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects, with respect to one or more other processes described below or elsewhere herein.

[0171]

[0178] In a first additional aspect, the one or more configured fields are associated with the TCI.

[0172]

[0179] In a second additional aspect, the capability indicator identifies UE support for DCI having a DCI format.

[0173]

[0180] In a third additional aspect, the process 1200 includes transmitting a DCI having a DCI format, and communicating according to the capability indicator includes communicating according to a TCI associated with one or more configured fields.

[0174]

[0181] In a fourth additional aspect, the capability indicator is included in an optional field of the UCI message.

[0175]

[0182] In a fifth additional aspect, the capability indicator is a single capability indicator that indicates support for a DCI format that does not include scheduling data and another DCI format that does include scheduling data.

[0176]

[0183] In a sixth additional aspect, the capability indicator is a first capability indicator that indicates support for a DCI format that does not include scheduling data.

[0177]

[0184] In a seventh additional aspect, the process 1200 includes receiving a second capability indicator indicating support for another DCI format including the scheduling data, and communicating in accordance with the capability indicator includes communicating in accordance with the first capability indicator and the second capability indicator.

[0178]

[0185] 12 illustrates example blocks of process 1200, in some aspects process 1200 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIGURE 12. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0179]

[0186] 13 is a diagram illustrating an example 1300 relating to capability indication for use of a DCI format for beam indication without scheduling data in accordance with the present disclosure. As shown in FIG. 13, a base station 110 and a UE 120 may communicate with each other.

[0180]

[0187] As indicated by reference numeral 1305, the UE 120 may transmit a capability indication to the base station 110. For example, the UE 120 may transmit a UCI indicating whether the UE 120 supports a DCI format for beam indication without scheduling data. In this case, the UCI may include an optional field to indicate support for one or more DCI formats, such as DCI format 1_1 or DCI format 1_2, among other examples. In some aspects, the UE 120 may transmit a single UE capability indication. For example, the UE 120 may transmit a UCI with a single field to indicate whether the UE 120 supports both a beam indication DCI with a downlink assignment or a beam indication DCI without a downlink assignment. Alternatively, the UE 120 may transmit multiple capability indications, such as a first capability indication of whether the UE 120 supports a beam indication DCI with a downlink assignment and a second capability indication of whether the UE 120 supports a beam indication DCI without a downlink assignment.

[0181]

[0188] As indicated by reference numeral 1310, base station 110 may transmit, and UE 120 may receive, a DCI. For example, UE 120 may receive a beam indication DCI that does not schedule downlink data based on UE 120 providing a capability indication to indicate that UE 120 supports a beam indication DCI that does not use a downlink assignment. In this case, the beam indication DCI may be DCI format 1_1, DCI format 1_2, DCI format 1_0, or uplink format DCI, among other examples, that includes one or more configured fields to indicate TCI. Additionally or alternatively, the beam indication DCI may include, in addition to TCI, one or more configured fields for another indication, such as a secondary cell dormant indication.

[0182]

[0189] As indicated by reference numeral 1315, the UE 120 may determine a communication configuration based on the DCI. For example, the UE 120 may determine a TCI to use when communicating with the base station 110. In some aspects, the UE 120 may determine that the DCI includes a TCI field for determining the communication configuration. For example, the UE 120 may parse the DCI to identify a field indicating whether an indication of TCI is included in the DCI. Additionally or alternatively, the UE 120 may determine that the DCI includes a TCI field based on the RNTI, the DCI format, a validation field, or a validation sequence. When the TCI field is not present in the DCI, the UE 120 may determine the TCI based on other information. For example, the UE 120 may determine that the TCI is included in the DCI based on another field in the DCI, the CORESET beam of the DCI, or a default configuration. In another example, when the field is not present, the UE 120 may determine that the DCI does not indicate a TCI status.

[0183]

[0190] In some aspects, the UE 120 may identify multiple TCI states based on the DCI. For example, the UE 120 may receive a DCI that identifies a single TCI within a TCI pool, and the UE 120 may apply the TCI to the TCI pool. In this case, the TCI pool may include an uplink TCI pool or a downlink TCI pool. In another example, the UE 120 may receive a DCI that identifies multiple TCIs, such as an uplink TCI and a downlink TCI. In this case, the DCI may include explicit indicators of the multiple TCIs (e.g., a first indicator of a first TCI in the TCI field and a second indicator of a second TCI in another field, such as the MCS field). Alternatively, the DCI may include an identifier from which the UE 120 may derive multiple TCIs (e.g., an index value on which the UE 120 may perform a table lookup to identify multiple TCIs corresponding to the index value). In this case, the table (or another data structure or pool) from which to perform the table lookup may be configured in signaling received from the base station 110.

[0184]

[0191] As indicated by reference numeral 1320, UE 120 may communicate with base station 110 according to a communication configuration. For example, UE 120 may send signaling to base station 110 (on the uplink) or receive signaling from base station 110 (on the downlink) using the TCI identified from the DCI. In some aspects, UE 120 may communicate on another link according to a communication configuration, such as a sidelink.

[0185]

[0192] The following provides a summary of some aspects of the disclosure.

[0186]

[0193] Aspect 1: A method of wireless communication implemented by a UE device, the method including: receiving DCI having a DCI format, wherein the DCI includes one or more configured fields, and communicating according to a TCI associated with the one or more configured fields, wherein the DCI does not include scheduling data.

[0187]

[0194] Aspect 2: The method of aspect 1, wherein the DCI format is DCI format 1_1 or DCI format 1_2.

[0188]

[0195] Aspect 3: The method of aspect 2, wherein the DCI includes an indication of the TCI and does not include an indication of another type.

[0189]

[0196] Aspect 4: The method of aspect 1, wherein the DCI format is DCI format 1_0 or an uplink DCI format.

[0190]

[0197] Example 5: The method of Examples 1 to 4, wherein the DCI includes a first indication of the TCI and a second indication of another setting.

[0191]

[0198] Aspect 6: The method of aspect 5, wherein the second indication includes at least one of a secondary cell dormant indication, a semi-persistent scheduling release indication, a semi-persistent scheduling activation indication, or a hybrid automatic repeat request indication.

[0192]

[0199] Example 7: The method of any one of Examples 1 to 6, wherein the TCI is based on a value of a TCI field parameter of the DCI.

[0193]

[0200] Example 8: The method of any one of Examples 1 to 7, wherein the TCI is based on a value of a non-TCI field parameter of the DCI.

[0194]

[0201] Embodiment 9: The method of any of embodiments 1 to 8, wherein the TCI is based on one or more CORESET beams of the DCI.

[0195]

[0202] Embodiment 10: The method of any of embodiments 1 to 9, wherein the DCI indicates a single TCI, the TCI being associated with a TCI pool, and further including configuring multiple TCIs associated with the TCI pool based on the TCI.

[0196]

[0203] Embodiment 11: The method of any of embodiments 1 to 9, wherein the DCI represents a plurality of TCIs.

[0197]

[0204] Example 12: The method of any one of examples 1 to 11, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs.

[0198]

[0205] Aspect 13: The method of aspect 12, wherein the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from multiple configured groupings of TCIs having a common attribute.

[0199]

[0206] Embodiment 14: The method of any one of embodiments 1 to 13, wherein the TCI includes a downlink TCI and an uplink TCI.

[0200]

[0207] Example 15: The method of any one of examples 1 to 14, wherein the TCI is based on an RNTI associated with the DCI.

[0201]

[0208] Embodiment 16: The method of any of embodiments 1 to 15, wherein the TCI is based on a required field of the DCI.

[0202]

[0209] Embodiment 17: The method of any of embodiments 1 to 16, wherein the TCI is based on a verification sequence configured for the beam indication.

[0203]

[0210] Embodiment 18: The method of any of embodiments 1-16, wherein the TCI is based on a value of a validation sequence associated with a non-TCI configuration.

[0204]

[0211] Aspect 19: The method of any of aspects 1 to 18, wherein a configured field associated with the TCI is not present in one or more configured fields of the DCI, and the UE is configured to determine the TCI based on at least one of another DCI, another indicator that is not a DCI, another configured field that is present in the one or more configured fields of the DCI, or a default configuration.

[0205]

[0212] Aspect 20: A method of wireless communication implemented by a base station, the method including: transmitting a DCI having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI communicates according to a TCI associated with the one or more configured fields, the TCI not including scheduling data.

[0206]

[0213] Aspect 21: The method of aspect 20, wherein the DCI format is DCI format 1_1 or DCI format 1_2.

[0207]

[0214] Embodiment 22: The method of embodiment 21, wherein the DCI includes an indication of the TCI and does not include an indication of another type.

[0208]

[0215] Aspect 23: The method of aspect 20, wherein the DCI format is DCI format 1_0 or an uplink DCI format.

[0209]

[0216] Example 24: The method of example 23, wherein the DCI includes a first indication of the TCI and a second indication of another setting.

[0210]

[0217] Aspect 25: The method of aspect 24, wherein the second indication includes at least one of a secondary cell dormant indication, a semi-persistent scheduling release indication, a semi-persistent scheduling activation indication, or a hybrid automatic repeat request indication.

[0211]

[0218] Embodiment 26: The method of any one of embodiments 20 to 25, wherein the TCI is based on a value of a TCI field parameter of the DCI.

[0212]

[0219] Embodiment 27: The method of any one of embodiments 20 to 26, wherein the TCI is based on a value of a non-TCI field parameter of the DCI.

[0213]

[0220] Embodiment 28: The method of any of embodiments 20 to 27, wherein the TCI is based on one or more CORESET beams of the DCI.

[0214]

[0221] Embodiment 29: The method of any of embodiments 20 to 28, wherein the DCI indicates a single TCI, the TCI being associated with a TCI pool, and further including communicating according to the multiple TCIs associated with the TCI pool based on the TCI.

[0215]

[0222] Embodiment 30: The method of any of embodiments 20 to 28, wherein the DCI represents a plurality of TCIs.

[0216]

[0223] Embodiment 31: The method of any one of embodiments 20 to 30, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs.

[0217]

[0224] Embodiment 32: The method of embodiment 30, wherein the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from multiple configured groupings of TCIs having a common attribute.

[0218]

[0225] Embodiment 33: The method of any one of embodiments 20 to 32, wherein the TCI includes a downlink TCI and an uplink TCI.

[0219]

[0226] Example 34: The method of any of examples 20 to 33, wherein the TCI is based on a radio network temporary identifier (RNTI) associated with the DCI.

[0220]

[0227] Embodiment 35: The method of any of embodiments 20 to 34, wherein the TCI is based on a required field of the DCI.

[0221]

[0228] Embodiment 36: The method of any of embodiments 20 to 35, wherein the TCI is based on a verification sequence configured for the beam indication.

[0222]

[0229] Embodiment 37: The method of any of embodiments 20 to 36, wherein the TCI is based on a value of a validation sequence associated with a non-TCI configuration.

[0223]

[0230] Aspect 38: A method of wireless communication performed by a UE device, the method including: transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports DCI having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; and communicating in accordance with the capability indicator.

[0224]

[0231] Embodiment 39: The method of embodiment 38, wherein one or more configured fields are associated with the TCI.

[0225]

[0232] Embodiment 40: The method of any of embodiments 38-39, wherein the capability indicator identifies UE support for DCI having a DCI format.

[0226]

[0233] Aspect 41: The method of aspect 40, further comprising receiving a DCI having a DCI format, and wherein communicating according to the capability indicator comprises communicating according to a TCI associated with one or more configured fields.

[0227]

[0234]

[0071] Aspect 42: The method of any of aspects 38-41, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message.

[0228]

[0235] Example 43: The method of any of examples 38 to 42, wherein the capability indicator is a single capability indicator that indicates support for a DCI format that does not include scheduling data and another DCI format that includes scheduling data.

[0229]

[0236] Example 44: The method of any of examples 38 to 43, wherein the capability indicator is a first capability indicator that indicates support for a DCI format that does not include scheduling data.

[0230]

[0237] Aspect 45: The method of aspect 44, further comprising transmitting a second capability indicator indicating support for another DCI format including the scheduling data, and wherein communicating in accordance with the capability indicator comprises communicating in accordance with the first capability indicator and the second capability indicator.

[0231]

[0238] Aspect 46: A method of wireless communication implemented by a device of a BS, the method including: receiving a capability indicator, wherein the capability indicator is associated with whether the UE supports downlink DCI having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; and communicating in accordance with the capability indicator.

[0232]

[0239] Aspect 47: The method of aspect 46, wherein one or more configured fields are associated with the TCI.

[0233]

[0240] Embodiment 48: The method of any of embodiments 46-47, wherein the capability indicator identifies UE support for DCI having a DCI format.

[0234]

[0241] Aspect 49: The method of aspect 48, further comprising transmitting a DCI having a DCI format, wherein communicating in accordance with the capability indicator comprises communicating in accordance with a TCI associated with one or more configured fields.

[0235]

[0242] Embodiment 50: The method of any of embodiments 46 to 49, wherein the capability indicator is included in an optional field of the UCI message.

[0236]

[0243] Aspect 51: The method of any of aspects 46 to 50, wherein the capability indicator is a single capability indicator that indicates support for a DCI format that does not include scheduling data and another DCI format that includes scheduling data.

[0237]

[0244] Embodiment 52: The method of any of embodiments 46 to 51, wherein the capability indicator is a first capability indicator that indicates support for a DCI format that does not include scheduling data.

[0238]

[0245] Aspect 53: The method of aspect 34, further comprising receiving a second capability indicator indicating support for another DCI format including the scheduling data, and wherein communicating in accordance with the capability indicator comprises communicating in accordance with the first capability indicator and the second capability indicator.

[0239]

[0246] Aspect 54: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method of one or more of aspects 1 to 19.

[0240]

[0247] Aspect 55: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 1 to 19.

[0241]

[0248] Aspect 56: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of aspects 1 to 19.

[0242]

[0249] Aspect 57: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method of one or more of aspects 1 to 19.

[0243]

[0250] Aspect 58: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 1 to 19.

[0244]

[0251] Aspect 59: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method of one or more of aspects 20 to 37.

[0245]

[0252] Aspect 60: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 20 to 37.

[0246]

[0253] Aspect 61: An apparatus for wireless communication, the apparatus including at least one means for performing the method of one or more of aspects 20 to 37.

[0247]

[0254] Aspect 62: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to implement a method of one or more of aspects 20 to 37.

[0248]

[0255] Aspect 63: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 20-37.

[0249]

[0256] Aspect 64: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method of one or more of aspects 38 to 45.

[0250]

[0257] Aspect 65: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 38 to 45.

[0251]

[0258] Aspect 66: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of aspects 38 to 45.

[0252]

[0259] Aspect 67: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to implement the method of one or more of aspects 38 to 45.

[0253]

[0260] Aspect 68: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 38 to 45.

[0254]

[0261] Aspect 69: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method of one or more of aspects 46 to 53.

[0255]

[0262] Aspect 70: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 46 to 53.

[0256]

[0263] Aspect 71: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of aspects 46 to 53.

[0257]

[0264] Aspect 72: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to implement the method of one or more of aspects 46 to 53.

[0258]

[0265] Aspect 73: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 46-53.

[0259]

[0266] The above disclosure provides illustration and description, and is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or acquired from practice of the embodiments.

[0260]

[0267] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be broadly interpreted to mean "based at least in part on." As used herein, satisfying a threshold may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples. 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" encompasses a, b, c, ab, ac, bc, and abc.

[0261]

[0268] Also, as used herein, the articles "a" and "an" include one or more items and may be used interchangeably with "one or more." Furthermore, as used herein, the article "the" includes one or more items referenced in connection with the article "the" and may be used interchangeably with "one or more." Furthermore, as used herein, the terms "set" and "group" include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may 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," and similar terms are intended to be open-ended terms. Furthermore, as used herein, the term "or" is inclusive when used consecutively and can be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of").

[0262]

[0269] The various example logic, logic blocks, modules, circuits, and algorithmic processes described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. Interchangeability between hardware and software has been generally described in terms of functionality and illustrated in the various example components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the particular application and design constraints imposed on the overall system.

[0263]

[0270] The hardware and data processing equipment used to implement the various example logic, logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, particular processes and methods may be performed by circuitry that is specific to a given function.

[0264]

[0271] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed herein, and structural equivalents of those structures, or in any combination thereof. Aspects of the subject matter described herein may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage medium for execution by, or to control the operation of, a data processing apparatus.

[0265]

[0272] If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The processes of a method or algorithm disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. Computer-readable media includes both computer storage media and computer communication media, including any medium that may enable transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may be properly referred to as a computer-readable medium. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy discs, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media. Furthermore, the operations of a method or algorithm may reside as one or any combination of code and instructions on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0266]

[0273] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the scope of the claims is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with this disclosure and the principles and novel features disclosed herein.

[0267]

[0274] Furthermore, those skilled in the art will readily appreciate that the terms "upper" and "lower" are sometimes used to simplify illustration of the figures, indicate relative positions corresponding to the orientation of the figure on a suitably oriented page, and may not reflect the proper orientation of any implemented device.

[0268]

[0275] Also, some features described herein in the context of separate aspects may be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may be implemented in multiple aspects separately or in any suitable subcombination. Moreover, although features may be described above as working in some combinations and may even initially be claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0269]

[0276] Similarly, although operations are illustrated in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequence shown, or that all illustrated operations be performed, to achieve desirable results. Furthermore, the figures may generally depict another exemplary process in the form of a flow chart. However, other operations not shown may be incorporated into the generally depicted exemplary process. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the above-described aspects should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged in multiple software products. Furthermore, other aspects are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

Claims

1. 1. A method of wireless communication implemented by a user equipment (UE) device, comprising: receiving a downlink control information (DCI) having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data; and communicating in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields.

2. The method of claim 1 , wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes an indication of the TCI and does not include an indication of another type.

3. 2. The method of claim 1, wherein the DCI format is DCI format 1_0 or an uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of another configuration.

4. The second indication is: Secondary cell (SCell) out-of-service indication, Semi-persistent scheduling (SPS) release indication, SPS activation indication, or 4. The method of claim 3, comprising at least one of a Hybrid Automatic Repeat Request (HARQ) indication.

5. 2. The method of claim 1, wherein the TCI is based on a value of a TCI field parameter of the DCI, a value of a non-TCI field parameter of the DCI, or one or more control resource set (CORESET) beams of the DCI.

6. 2. The method of claim 1, wherein the DCI indicates a single TCI associated with multiple TCIs or a TCI pool from which the multiple TCIs are to be configured.

7. 2. The method of claim 1, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs, the set of TCIs being a single configured grouping of TCIs or a group of TCIs selected from multiple configured groupings of TCIs with common attributes.

8. The method of claim 1 , wherein the TCI includes a downlink TCI and an uplink TCI.

9. The TCI is a Radio Network Temporary Identifier (RNTI) associated with the DCI; Required fields of the DCI; A verification sequence configured for beam indication, or The method of claim 1 , wherein the value is based on at least one of a value of a verification sequence associated with a non-TCI configuration.

10. a configured field associated with the TCI is not present in the one or more configured fields of the DCI, and the UE: Another DCI, Another indicator that is not DCI, another configured field present in the one or more configured fields of the DCI; or The method of claim 1 , configured to determine the TCI based on at least one of a default configuration.

11. 1. A method of wireless communication implemented by a base station (BS) device, comprising: transmitting a downlink control information (DCI) having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data; and communicating in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields.

12. The method of claim 11 , wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes an indication of the TCI and does not include an indication of another type.

13. 12. The method of claim 11, wherein the DCI format is DCI format 1_0 or an uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of another configuration.

14. The second indication is: Secondary cell (SCell) out-of-service indication, Semi-persistent scheduling (SPS) release indication, SPS activation indication, or 14. The method of claim 13, comprising at least one of a Hybrid Automatic Repeat Request (HARQ) indication.

15. 12. The method of claim 11, wherein the TCI is based on a value of a TCI field parameter of the DCI, a value of a non-TCI field parameter of the DCI, or one or more control resource set (CORESET) beams of the DCI.

16. 12. The method of claim 11, wherein the DCI indicates a single TCI associated with multiple TCIs or a TCI pool from which the multiple TCIs are to be configured.

17. 12. The method of claim 11, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs, the set of TCIs being a single configured grouping of TCIs or a group of TCIs selected from multiple configured groupings of TCIs with common attributes.

18. The method of claim 11 , wherein the TCI includes a downlink TCI and an uplink TCI.

19. The TCI is a Radio Network Temporary Identifier (RNTI) associated with the DCI; Required fields of the DCI; A verification sequence configured for beam indication, or The method of claim 11 , based on at least one of the values ​​of a verification sequence associated with a non-TCI configuration.

20. 1. A method of wireless communication implemented by a user equipment (UE) device, comprising: transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports a downlink control information (DCI) having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; and communicating according to the capability indicator.

21. 21. The method of claim 20, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI).

22. 21. The method of claim 20, wherein the capability indicator identifies UE support for the DCI having the DCI format.

23. receiving the DCI having the DCI format, wherein communicating according to the capability indicator further comprises:

23. The method of claim 22, comprising communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields.

24. 21. The method of claim 20, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message.

25. 21. The method of claim 20, wherein the capability indicator is a single capability indicator that indicates support for the DCI format that does not include scheduling data and another DCI format that does include scheduling data.

26. 21. The method of claim 20, wherein the capability indicator is a first capability indicator that indicates support for the DCI format that does not include scheduling data.

27. transmitting a second capability indicator indicating support for another DCI format including scheduling data, wherein communicating according to the capability indicator further comprises:

27. The method of claim 26, comprising communicating according to the first capability indicator and the second capability indicator.

28. 1. A method of wireless communication implemented by a base station (BS) device, comprising: receiving a capability indicator, wherein the capability indicator is associated with whether a user equipment (UE) supports a downlink control information (DCI) having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; and communicating according to the capability indicator.

29. 30. The method of claim 28, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI).

30. 29. The method of claim 28, wherein the capability indicator identifies UE support for the DCI having the DCI format.

31. transmitting the DCI having the DCI format, wherein communicating according to the capability indicator further comprises:

31. The method of claim 30, comprising communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields.

32. 30. The method of claim 28, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message.

33. 29. The method of claim 28, wherein the capability indicator is a single capability indicator that indicates support for the DCI format that does not include scheduling data and another DCI format that does include scheduling data.

34. 29. The method of claim 28, wherein the capability indicator is a first capability indicator that indicates support for the DCI format that does not include scheduling data.

35. receiving a second capability indicator indicating support for another DCI format including scheduling data, wherein communicating in accordance with the capability indicator further comprises:

35. The method of claim 34, comprising communicating according to the first capability indicator and the second capability indicator.

36. 1. An apparatus for wireless communication in a user equipment (UE), comprising: Memory and one or more processors coupled to the memory, the processors comprising: receiving a downlink control information (DCI) having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data; and communicating in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields.

37. 37. The apparatus of claim 36, wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes an indication of the TCI and does not include an indication of another type.

38. 37. The apparatus of claim 36, wherein the DCI format is DCI format 1_0 or an uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of another configuration.

39. 1. An apparatus for wireless communication in a base station (BS), comprising: Memory and one or more processors coupled to the memory, the processors comprising: transmitting a downlink control information (DCI) having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data; and communicating in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields.

40. 40. The apparatus of claim 39, wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes an indication of the TCI and does not include an indication of another type.

41. 40. The apparatus of claim 39, wherein the DCI format is DCI format 1_0 or an uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of another configuration.

42. 1. An apparatus for wireless communication in a user equipment (UE), comprising: Memory and one or more processors coupled to the memory, the processors comprising: transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports a downlink control information (DCI) having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; and communicating in accordance with said capability indicator.

43. 43. The apparatus of claim 42, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI).

44. 43. The apparatus of claim 42, wherein the capability indicator identifies UE support for the DCI having the DCI format.

45. the one or more processors: and further configured to: receive the DCI having the DCI format, wherein the one or more processors communicate according to the capability indicator; 45. The apparatus of claim 44, configured to communicate in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields.

46. 43. The apparatus of claim 42, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message.

47. 1. An apparatus for wireless communication in a base station (BS), comprising: Memory and one or more processors coupled to the memory, the processors comprising: receiving a capability indicator, wherein the capability indicator is associated with whether a user equipment (UE) supports a downlink control information (DCI) having a DCI format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; and communicating in accordance with said capability indicator.

48. 48. The apparatus of claim 47, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI).

49. 48. The apparatus of claim 47, wherein the capability indicator identifies UE support for the DCI having the DCI format.

50. the one or more processors: and wherein the one or more processors are further configured to: transmit the DCI having the DCI format, for communicating according to the capability indicator; 50. The apparatus of claim 49, configured to communicate in accordance with a transmission configuration indicator (TCI) associated with the one or more configured fields.

Images