Downlink Control Information (DCI) Format and Capability Report for Beam Indication Without Scheduling Data

Abstract

The present disclosure provides a system, method, and apparatus that enable a base station (BS) to transmit downlink control information (DCI) without downlink data to indicate a transmission configuration indicator (TCI). In one aspect, a user equipment (UE) may transmit a capability indication associated with whether the UE can receive a DCI with a TCI and without a data assignment. The 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. The TCI may be a type 1 beam indication or another type of beam indication. The DCI may be DCI format 1_1 or 1_2, or another DCI format such as DCI format 1_0 or a DCI that schedules an uplink configuration, among other examples, and may indicate another configuration with the TCI.

Description

Technical Field

[0001] Cross - reference to Related Applications

[0001] This patent application claims the priority of PCT Patent Application No. PCT / CN2021 / 080375, titled "DOWNLINK CONTROL INFORMATION (DCI) FORMAT FOR BEAM INDICATION WITHOUT SCHEDULING DATA", filed on March 12, 2021, which was assigned to the assignee of this application. The disclosure of the prior application is regarded as part of this patent application and is incorporated herein by reference.

[0002]

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

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple access technology that can support 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 (registered trademark)). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard published by the Third Generation Partnership Project (3GPP (registered trademark)).

[0004]

[0004] A wireless network may include several base stations (BSs) that can support communication for several user equipments (UEs). The UE can communicate with the BS via a downlink (DL) and an uplink (UP). "DL" (or "forward link") refers to the communication link from the BS to the UE, and "UL" (or "reverse link") refers to the communication link from the UE to the BS. As will be described in more detail herein, the 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 multi-connectivity technology is adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and even global scales. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectra, and better integrating with other open standards by using cyclic prefix (CP)-orthogonal frequency division multiplexing (OFDM) (CP-OFDM) on the DL and using CP-OFDM or single-carrier frequency division multiplexing (SC-FDM), also known as discrete Fourier transform spread OFDM (DFT-s-OFDM), on the UL (or combinations thereof), as well as by supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

Summary of the Invention

[0006]

[0006] The systems, methods, and devices of the present disclosure each have several inventive aspects, and no single aspect among them necessarily bears the desirable attributes disclosed herein alone.

[0007]

[0007] One inventive aspect of the subject matter described in the present disclosure can be implemented in a method of wireless communication performed by an apparatus of a user equipment (UE), including receiving downlink control information (DCI) having a DCI format, where the DCI includes one or more configured fields, and where the DCI communicates according to a transmission control indicator (TCI) associated with the one or more configured fields and does not include scheduling data.

[0008]

[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 TCI and a second indication of a different 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 this disclosure can be implemented in a method of wireless communication performed by a base station (BS), including transmitting a DCI having a DCI format, where the DCI includes one or more configured fields and where the DCI communicates according to a TCI associated with the one or more configured fields that does not include scheduling data.

[0010] Another inventive aspect of the subject matter described in this 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, the method comprising receiving DCI having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data, and communicating according to a TCI associated with the one or more configured fields.

[0011] Another inventive aspect of the subject matter described in this 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, the method comprising transmitting DCI having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data, and communicating according to a TCI associated with the one or more configured fields.

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

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

[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 that includes one or more instructions, the one or more instructions causing a user equipment to receive DCI having a DCI format when executed by one or more processors of the UE, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data, and to communicate according to a TCI associated with the one or more configured fields.

[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 communication, the set of instructions including one or more instructions that, when executed by one or more processors of a BS, cause the BS to transmit DCI having a DCI format, where the DCI includes one or more configured fields, and where the DCI does not include scheduling data, and to communicate according to a TCI associated with the one or more configured fields.

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

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

[0018] Another inventive aspect of the subject matter described in this disclosure may be implemented in a method of wireless communication performed by a UE device, the method comprising 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 according to the capability indicator.

[0019] Another inventive aspect of the subject matter described in this disclosure may be implemented in a method of wireless communication performed by a BS, the method comprising 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.

[0020]

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

[0021]

[0021] Another inventive aspect of the subject matter described in this disclosure may be implemented in an apparatus for wireless communication in a UE that includes a memory and one or more processors coupled to the memory, 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 according to the capability indicator.

[0022]

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

[0023]

[0023] Another inventive aspect of the subject matter described in this disclosure may be implemented in a BS that includes a memory and one or more processors coupled to the memory, 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.

[0024] Another inventive aspect of the subject matter described in this disclosure may be implemented in a UE apparatus for wireless communication that includes a first interface configured to output 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 where the first interface or the second interface is configured to communicate according to the capability indicator.

[0025] Another inventive aspect of the subject matter described in this disclosure may be implemented in a BS apparatus for wireless communication that includes a first interface 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 where the second interface or the first interface is configured to communicate according to the capability indicator.

[0026] 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 that includes one or more instructions, where the one or more instructions, 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 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 according to the capability indicator.

[0027] Another inventive aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing a set of instructions for wireless communication, which, when executed by one or more processors of a BS, cause the BS to receive a capability indicator, where the capability indicator is associated with whether a 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 according to the capability indicator, including one or more instructions.

[0028] Another inventive aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication, the apparatus including means for transmitting a capability indicator, where the capability indicator is associated with whether a 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 means for communicating according to the capability indicator.

[0029] Another inventive aspect of the subject matter described in this disclosure can 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 a 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 means for communicating according to the capability indicator.

[0030] In some aspects, by way of example, a UE's apparatus, such as the apparatus's processing system or one or more interfaces of the apparatus, can be configured to perform one or more operations of a method of wireless communication performed by the apparatus.

[0031]

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

[0032]

[0032] Embodiments are generally substantially described herein with reference to the accompanying drawings and include, as shown by the accompanying drawings, methods, devices, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, or processing systems.

[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 description below. Other features, aspects, and advantages will be apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.

Brief Description of the Drawings

[0034]

Figure 1

[0034] A diagram showing an example of a wireless network.

Figure 2

[0035] A diagram showing an example of a base station (BS) communicating with a user equipment (UE) in a wireless network.

Figure 3

[0036] A diagram showing an example of using a beam for communication between a BS and a UE.

Figure 4

[0037] For example, a diagram showing an exemplary process implemented by a UE.

Figure 5

Figure 6

[0038] A block diagram of an exemplary device for wireless communication.

Figure 7

Figure 8

[0039] Figures related to exemplary aspects of the present disclosure.

Figure 9

Figure 10

Figure 11

[0040] For example, a diagram showing an exemplary process performed by a UE.

Figure 12

Figure 13

[0041] Figures related to exemplary aspects of the present disclosure.

Best Mode for Carrying Out the Invention

[0035]

[0042] Like reference numerals and symbols in the various drawings indicate like elements.

[0036]

[0043] The following description is directed to several implementations for the purpose of describing the inventive aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings of this specification may be applied in many different ways. Some of the examples in the present 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 communication (PLC) standard. However, the described implementations may be implemented in any device, system, or network capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards including, but not limited to, 3G, 4G, or 5G, or further implementations thereof, such as systems utilizing IEEE 802.11 standards, Bluetooth® standards, 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 Trunked Radio (TETRA), Wideband CDMA (W-CDMA®), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, 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 signals.

[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, the BS may transmit DCI to indicate, among other examples, semi-persistent scheduling (SPS) release, SPS activation, hybrid automatic repeat request (HARQ) configuration, or secondary cell dormancy configuration. The BS may also transmit DCI to update the beam configuration for the UE. For example, the BS may transmit DCI having a downlink resource allocation for scheduling downlink data transmission, configured with DCI format 1_1 or DCI format 1_2, to indicate a transmission configuration indicator (TCI) state defined in the 3GPP specifications, or another similar data structure. The TCI may indicate one or more quasi-collocation (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 related channel properties (e.g., one or more spatial parameters such as Doppler shift, Doppler spread, average delay, delay spread, spatial filter, or other properties). Such QCL rules may include QCL type A, QCL type B, QCL type C, or QCL type D data structures defined by the 3GPP specifications.

[0038]

[0045] One type of TCI is a joint downlink and uplink TCI (type 1 beam indication) that 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 include a separate downlink common TCI (type 2 beam indication) that indicates a common beam for multiple downlink channels or reference signals, or a separate uplink common TCI (type 3 beam indication) that indicates a common beam for multiple uplink channels or reference signals, a separate downlink single-channel TCI (type 4 beam indication) that may indicate a beam for a single downlink channel or reference signal, a separate uplink single-channel TCI (type 5 beam indication) that may indicate a beam for a single uplink channel or reference signal, or uplink spatial relationship information (SRI) (type 6 beam indication) that may indicate a beam for a single uplink channel or reference signal. Other types of TCI are possible and may be defined in a standard (such as a 3GPP specification).

[0039]

[0046] When the BS transmits DCI to schedule downlink data to indicate TCI, the DCI can be, for example, DCI format 1_1 or DCI format 1_2 to indicate type 1 beam indication (joint downlink and uplink TCI). Some aspects described herein may define one or more interpretation rules such that the BS can transmit DCI without downlink data to indicate TCI. For example, the UE may have one or more configured fields, receive DCI without downlink data, and interpret the DCI based on one or more configured fields to identify the TCI. In such an example, the TCI can be type 1 beam indication or another type of beam indication. Further, in such an example, the DCI can be DCI format 1_1 or DCI format 1_2, or, among other examples, another DCI format such as DCI format 1_0 or DCI for scheduling uplink configuration, and among other examples, can indicate another configuration with TCI such as SPS release, SPS activation, HARQ configuration, or secondary cell suspension configuration. Some aspects described herein may enable the UE to provide a capability report regarding whether the UE supports receiving DCI without downlink data to indicate TCI. For example, the UE can 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 realize one or more of the following potential advantages. As described herein, a UE may receive DCI that does not schedule data transmission and may communicate according to a TCI associated with one or more configured fields of the DCI. By using DCI to identify a TCI that does not schedule data transmission, signaling overhead may be reduced compared to having information for scheduling data transmission that should be included in the DCI for identifying the TCI. By enabling the use of different types of beam indication in the TCI in the DCI, a unified TCI framework may be enabled that can simplify beam management procedures not only for downlink and uplink channels in a 3GPP (NR) system but also for data and control channels. By including an explicit beam indication such as a TCI in the DCI, signaling flexibility may be improved when the DCI is transmitted to indicate another configuration, such as, among other examples, SPS release, SPS activation, HARQ configuration, or secondary cell suspension configuration. By providing a capability indicator to indicate whether a UE supports DCI without downlink data to indicate a TCI, a scenario is avoided where a BS transmits DCI without downlink data to indicate a TCI and the UE cannot interpret such DCI. By avoiding the above-described scenario, the likelihood of communication errors from UEs that cannot interpret such DCI is reduced and the BS may be able to operate in a communication system that includes UEs with different capabilities.

[0041]

[0048] FIG. 1 is a diagram showing an example of a wireless network 100. The wireless network 100 may be an element of, or include, 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 BS110a, BS110b, BS110c, and BS110d) 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 transmission and reception point (TRP). Each BS may provide communication coverage for a specific 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 to 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 geographical area (e.g., several kilometers in radius) and may enable unrestricted access by UEs subscribed to the service. A pico cell may cover a relatively small geographical area and may enable unrestricted access by UEs subscribed to the service. A femto cell may cover a relatively small geographical area (e.g., a home) and may enable restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). The BS for a macro cell may sometimes be called a macro BS. The BS for a pico cell may sometimes be called a pico BS. The BS for a femto cell may sometimes be called a femto BS or a home BS. In the example shown in FIG. 1, BS110a may be a macro BS for macro cell 102a, BS110b may be a pico BS for pico cell 102b, and BS110c 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, a cell may not necessarily be fixed and the geographical area of the cell may move according to the location of the mobile BS. In some examples, the BSs may be interconnected with each other and with one or more other BSs or network nodes (not shown) in the 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] Wireless network 100 may also include relay stations. A relay station is an entity that can receive the transmission of data from an upstream station (e.g., a BS or a UE) and send the transmission of that data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions to other UEs. In the example shown in FIG. 1, relay BS 110d can communicate with macro BS 110a and UE 120d to facilitate communication between macro BS 110a and UE 120d. A relay BS may also be referred to as a relay station, relay base station, relay, etc.

[0045]

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

[0046]

[0053] Network controller 130 can be coupled to a set of BSs and can coordinate and control these BSs. Network controller 130 can communicate with the BSs via a backhaul. The BSs can also communicate with each other directly or indirectly, for example, via a wireless or wireline backhaul.

[0047]

[0054] A plurality of UEs 120 (e.g., UE120a, UE120b, UE120c, etc.) can be distributed throughout the wireless network 100, and each UE can be fixed or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. A UE can 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 instrument, a biosensor / biodevice, a wearable device (smartwatch, smart clothing, smart glasses, smart list band, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music device or video device, or satellite radio), a vehicle component or vehicle sensor, a smart meter / smart sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless medium or a wired medium.

[0048]

[0055] Some UEs may be regarded as machine type communication (MTC) UEs or enhanced or extended machine type communication (eMTC) UEs. MTC UEs and eMTC UEs can communicate with, for example, a base station, another device (such as a remote device), or some other entity, including robots, drones, remote devices, sensors, meters, monitors, or location tags. A wireless node can provide connectivity for a network (such as a wide area network like the Internet or a cellular network) or to a network, for example, via a wired or wireless communication link. Some UEs may be regarded as Internet of Things (IoT) devices or may be implemented as narrowband Internet of Things (NB-IoT) devices. Some UEs may be regarded as customer premise equipment (CPE). UE120 may be included within a housing that houses components of UE120, 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, the processor component (such as one or more processors) and the memory component (such as a memory) can be operably coupled, communicatively coupled, electronically coupled, or electrically coupled in the examples.

[0049]

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

[0050]

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

[0051]

[0058] Devices of the wireless network 100 may communicate using the electromagnetic spectrum that can be subdivided into various classes, bands, or channels based on frequency or wavelength. For example, devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1) that can span from 410 MHz to 7.125 GHz. As another example, devices of the wireless network 100 may communicate using an operating band having a second frequency range (FR2) that can span from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 may sometimes be referred to as mid-band frequencies. A portion of FR1 is greater than 6 GHz, but FR1 is often referred to as the "sub-6 GHz" band. Similarly, although FR2 is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band, FR2 is often referred to as the "millimeter wave" band. Thus, it should be understood that unless otherwise specified, the term "sub-6 GHz" may broadly represent frequencies below 6 GHz, frequencies within FR1, mid-band frequencies (e.g., greater than 7.125 GHz), or combinations thereof. Similarly, it should be understood that unless otherwise specified, the term "millimeter wave" may broadly represent frequencies within the EHF band, frequencies within FR2, mid-band frequencies (e.g., less than 24.25 GHz), or combinations thereof. The frequencies included in FR1 and FR2 may be changed, and the techniques described herein are intended to be applicable to those changed frequency ranges.

[0052]

[0059] FIG. 2 is a diagram showing an example 200 of a base station (BS) 110 communicating with a UE 120 in the wireless network 100. The base station 110 may be equipped with T antennas 234a - 234t, and the UE 120 may be equipped with R antennas 252a - 252r, where generally T ≧ 1 and R ≧ 1.

[0053]

[0060] At base station 110, a transmission processor 220 receives data from a data source 212 for one or more UEs, selects one or more modulation and coding schemes (MCSs) for each UE based on channel quality indicators (CQIs) received from the UEs, processes (e.g., encodes and modulates) the data for each UE based on the MCS selected for that UE, and may provide data symbols for all UEs. The transmission processor 220 may also process system information (e.g., for semi-static resource partitioning information) and control information (e.g., CQI requests, grants, or upper layer signaling) and may provide overhead symbols and control symbols. The transmission processor 220 may also generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A 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-232t. Each modulator 232 may process each output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from modulators 232a-232t may be transmitted via T antennas 234a-234t, respectively.

[0054]

[0061] In UE120, antennas 252a to 252r can receive downlink signals from base station 110 or other base stations, and can provide the received signals to demodulators (DEMOD) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. The MIMO detector 256 can obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols when applicable, and provide the detected symbols. The receiving processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE120 to the data sink 260, and provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine, among other things, the reference signal received power (RSRP) parameter, the received signal strength indicator (RSSI) parameter, the reference signal received quality (RSRQ) parameter, or the CQI parameter. In some aspects, one or more components of UE120 can be included in a housing.

[0055]

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

[0056]

[0063] Antennas (such as antennas 234a to 234t or antennas 252a to 252r) may include, or be included within, for example, one or more antenna panels, antenna groups, sets of antenna elements, or antenna arrays. The antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements. The 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. The antenna panel, antenna group, set of antenna elements, or antenna array may include antenna elements within a single housing or antenna elements within a plurality of housings. The antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements coupled to one or more transmit or receive components, such as one or more of the components of FIG. 2.

[0057]

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

[0058]

[0065] At base station 110, uplink signals from UE 120 and other UEs are received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain the decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling 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 base station 110 may be included within the modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of (one or more) antennas 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 implement any aspect of the processes described herein.

[0059]

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

[0060]

[0067] The processing system of UE120 can interface with other components of UE120, process information (such as inputs or signals) received from other components, output information to other components, and so on. For example, the chip or modem of UE120 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 the receiver, and thus, UE120 can receive information or signal inputs, and the information can 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 the transmitter, and thus, UE120 can transmit information outputs from the chip or modem. Those skilled in the art will readily recognize that the second interface can also acquire or receive information or signal inputs, and the first interface can also output, transmit, or provide information.

[0061]

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

[0062]

[0069] The processing system of base station 110 can interface with other components of base station 110, process information (such as inputs or signals) received from other components, and output information to other components. For example, the chip or modem of base station 110 can 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" can refer to the interface between the processing system of the chip or modem and the receiver, and thus, base station 110 can receive information or signal inputs, and the information can be passed to the processing system. In some cases, the "second interface" can refer to the interface between the processing system of the chip or modem and the transmitter, and thus, base station 110 can transmit information outputs from the chip or modem. Those skilled in the art will readily recognize that the second interface can also acquire or receive information or signal inputs, and the first interface can also output, transmit, or provide information.

[0063]

[0070] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component in 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 in this specification. The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or any other component (or combination of components) in FIG. 2 may perform or direct the 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. Memories 242 and 282 may store data and program code for the base station 110 and the UE 120, respectively. In some aspects, memories 242 and 282 may include non-transitory computer-readable media that store one or more instructions (e.g., code or program code) for wireless communication. When the one or more instructions are executed by one or more processors of the base station 110 or the UE 120 (e.g., directly or after being compiled, converted, or interpreted), the one or more processors, the UE 120, or the base station 110 may be caused to perform or direct the 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, UE 120 includes, among other things, means for transmitting DCI having a DCI format, where the DCI includes one or more configured fields and the DCI communicates according to a TCI associated with one or more configured fields that does not include scheduling data; means for 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; or means for communicating according to the capability indicator. In some aspects, such means may include one or more components of UE 120 described with respect to FIG. 2, such as controller / processor 280, transmission processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, or reception processor 258.

[0065]

[0072] In some aspects, base station 110 includes, among other things, means for transmitting DCI having a DCI format, where the DCI includes one or more configured fields and the DCI communicates according to a TCI associated with one or more configured fields that does not include scheduling data; means for 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; or means for communicating according to the capability indicator. In some aspects, such means may include one or more components of base station 110 described with respect to FIG. 2, such as antenna 234, DEMOD 232, MIMO detector 236, reception processor 238, controller / processor 240, transmission processor 220, TX MIMO processor 230, MOD 232, or antenna 234.

[0066]

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

[0067]

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

[0068]

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

[0069]

[0076] UE120 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 UE120. UE120 may identify a particular BS transmit beam 305, shown as BS transmit beam 305-A, and a particular UE receive beam 310, shown as UE receive beam 310-A, that provides relatively favorable performance (e.g., has the best channel quality of different measured combinations of the BS transmit beam 305 and the UE receive beam 310). In some examples, UE120 may transmit an indication of which BS transmit beam 305 is identified by UE120 as a BS transmit beam that the base station 110 may select for transmission to UE120. UE120 may thus achieve and maintain a beam pair link (BPL) (e.g., the combination of BS transmit beam 305-A and UE receive beam 310-A) with the base station 110 for downlink communication, and this BPL may be further improved and maintained according to one or more established beam refinement procedures.

[0070]

[0077] Downlink beams such as the BS transmission beam 305 or the UE reception beam 310 may be associated with a TCI state. The TCI state may indicate the directivity or characteristics of the downlink beam, such as one or more QCL properties of the downlink beam. The QCL properties may include, for example, among others, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters. In some examples, each BS transmission beam 305 may be associated with an SSB, and the UE 120 may indicate the BS transmission beam 305 by transmitting an uplink transmission in the resources of the SSB associated with the BS transmission beam 305. A particular SSB may have an associated TCI state (e.g., for an antenna port or beamforming). The base station 110 may indicate the downlink BS transmission beam 305 based on the antenna port QCL properties that may be indicated by the TCI state in some examples. The 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, average delay, delay spread, or spatial reception parameters). When the QCL type indicates spatial reception parameters, the QCL type may correspond to the analog reception beamforming parameters of the UE reception beam 310 at the UE 120. Thus, the UE 120 may select the corresponding UE reception beam 310 from the set of BPLs based on the base station 110 indicating the BS transmission beam 305 via a TCI indication.

[0071]

[0078] The base station 110 may maintain a set of activated TCI states for downlink shared channel transmission and a set of activated TCI states for downlink control channel transmission. The set of activated TCI states for downlink shared channel transmission may correspond to the beams used by the base station 110 for downlink transmission on the physical downlink shared channel (PDSCH). The set of activated TCI states for downlink control channel communication may correspond to the beams that the base station 110 may use for downlink transmission on the physical downlink control channel (PDCCH) or within a control resource set (CORESET). The UE 120 may also maintain a set of activated TCI states for receiving downlink shared channel transmission and CORESET transmission. When 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 the antenna or antenna weighting configuration. In some examples, the set of activated TCI states of the UE 120 (e.g., the activated PDSCH TCI state and the activated CORESET TCI state) may be configured by a configuration message such as a radio resource control (RRC) message.

[0072]

[0079] Similarly, in uplink communication, the UE 120 may transmit in the direction of the base station 110 using a directional UE transmission beam, and the base station 110 may receive the transmission using a directional BS reception beam. Each UE transmission beam may have, among other things, an associated beam ID, beam direction, or beam symbol. The UE 120 may transmit uplink communication via one or more UE transmission 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, shown as UE transmit beam 315-A, and a particular BS receive beam 320, shown as BS receive beam 320-A, that provide relatively favorable performance (e.g., having the best channel quality for 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 is identified by the base station 110 as a UE transmit beam that the base station 110 may select for transmission from UE 120. In this way, UE 120 and the base station 110 may achieve and maintain a BPL (e.g., the combination of UE transmit beam 315-A and BS receive beam 320-A) for uplink communication, and this BPL may be further improved and maintained according to one or more established beam refinement procedures. Uplink beams, such as UE transmit beam 315 or BS receive beam 320, may be associated with a spatial relationship. The spatial relationship may indicate the directivity or characteristics of the uplink beam, similar to one or more QCL properties, as described herein.

[0074]

[0081] FIG. 4 shows, for example, an exemplary process 400 implemented by a UE. Process 400 is an example of operations associated with a UE (e.g., UE 120) using DCI for beam indication without scheduling data.

[0075]

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

[0076]

[0083] As shown in FIG. 4, in some aspects, process 400 may include communicating according to a TCI associated with one or more configured fields (block 420). For example, a UE may communicate according to a TCI associated with one or more configured fields (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 information according to the TCI.

[0077]

[0084] Process 400 may include additional aspects such as any single aspect, or any combination of aspects, regarding one or more other processes described below or elsewhere in this document.

[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 another type of indication.

[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 configuration.

[0082]

[0089] In a fifth additional aspect, the second indication includes at least one of a secondary cell suspension 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 the value of the TCI field parameter of the DCI.

[0084]

[0091] In a seventh additional aspect, the TCI is based on the value of a non-TCI field parameter 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 is associated with a TCI pool, and the process 400 further includes configuring a plurality of 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 that indicates 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 beam indication.

[0094]

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

[0095]

[0102] In an eighteenth additional aspect, 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 19th additional aspect, the configured fields associated with TCI do not exist in one or more of the configured fields of DCI, and the UE is configured to determine TCI based on at least one of another DCI, another indicator that is not DCI, another configured field that exists in one or more of the configured fields of DCI, or a default configuration.

[0097]

[0104] FIG. 4 shows exemplary blocks of process 400, but in some aspects, process 400 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIG. 4. Additionally or alternatively, two or more of the blocks of process 400 may be executed in parallel.

[0098]

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

[0099]

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

[0100]

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

[0101]

[0108] Process 500 may include additional aspects such as any single aspect or any combination of aspects regarding one or more other processes described below or elsewhere in this specification.

[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 another type of indication.

[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 configuration.

[0106]

[0113] In a fifth additional aspect, the second indication includes at least one of a secondary cell suspension 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 the value of the TCI field parameter of the DCI.

[0108]

[0115] In a seventh additional aspect, the TCI is based on the value of the non-TCI field parameter 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 is associated with a TCI pool, and the process 500 further includes communicating according to a plurality of 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, a group of TCIs, or a plurality of configured groupings of TCIs having a common attribute, selected from the plurality of configured groupings of TCIs.

[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 the RNTI associated with the DCI.

[0116]

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

[0117]

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

[0118]

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

[0119]

[0126] In an 18th 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] FIG. 5 shows exemplary blocks of process 500, but in some aspects, process 500 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIG. 5. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0121]

[0128] FIG. 6 is a block diagram of an exemplary apparatus 600 for wireless communication. Apparatus 600 may be a UE, or the UE may include apparatus 600. In some aspects, apparatus 600 includes a receiving component 602 and a transmitting component 604 that may communicate with each other (e.g., via one or more buses or one or more other components). As shown, apparatus 600 may communicate with another apparatus 606 (such as a UE, a base station, or another wireless communication device) using receiving component 602 and transmitting component 604. As shown, apparatus 600 may include one or more of determination 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, by way of example, process 400 of FIG. 4, process 1100 of FIG. 11, etc. In some aspects, apparatus 600 or one or more components thereof 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 a set of components may be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) may be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0123]

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

[0124]

[0131] The transmitting component 604 may transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 606. 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, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) 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 the UE described above with respect to FIG. 2. In some aspects, the transmitting component 604 may be collocated 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 the device 600 may interface with other components of the device 600 and may perform operations such as processing information (such as an input or a signal) received from the other components and outputting information to the other components. For example, a chip or a modem of the device 600 may include a processing system, a receiving component 602 for receiving or obtaining 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 of the chip or the modem and a receiver, and thus, the device 600 may receive an 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 of the chip or the modem and a transmitter, and thus, the device 600 may transmit an information output from the chip or the modem. Those skilled in the art will readily recognize that a second interface may also obtain or receive an information or signal input and that a first interface may also output, transmit, or provide information.

[0126]

[0133] The receiving component 602 may receive 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 one or more configured fields. The determining component 608 may determine the TCI based on 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 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] FIG. 7 is a block diagram of an exemplary apparatus 700 for wireless communication. The apparatus 700 may be a base station or the base station may include the apparatus 700. In some aspects, the apparatus 700 includes a receiving component 702 and a transmitting component 704 that may communicate 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, among other examples, process 500 of FIG. 5, process 1200 of FIG. 12, etc. In some aspects, apparatus 700 or one or more components thereof 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 a set of components may be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) may be stored on a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0129]

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

[0130]

[0137] The transmitting component 704 may transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 706. 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 (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among others) 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 collocated 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 apparatus 700 can interface with other components of apparatus 700, process information (such as inputs or signals) received from other components, output information to other components, etc. For example, a chip or a modem of apparatus 700 can 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 can refer to an interface between the processing system of the chip or modem and a receiver, and thus, apparatus 700 can receive an information or signal input, and the information can be passed to the processing system. In some cases, the transmitting component 704 can refer to an interface between the processing system of the chip or modem and a transmitter, and thus, apparatus 700 can transmit an information output from the chip or modem. Those skilled in the art will readily recognize that a second interface can also acquire or receive an information or signal input, and a first interface can also output, transmit, or provide information.

[0132]

[0139] The transmitting component 704 can transmit DCI having a downlink control information (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 can communicate according to a transmission control indicator (TCI) associated with one or more configured fields. A configuring component 708 can configure one or more configured fields of the DCI. The receiving component 702 can receive a capability indicator, where the capability indicator is associated with whether a 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. The receiving component 702 or the transmitting component 704 can communicate according to the capability indicator.

[0133]

[0140] FIGS. 8-10 are diagrams related to exemplary aspects of the present disclosure.

[0134]

[0141] Note on how to use DCI to update beam indication in a unified TCI framework. The unified TCI framework includes a common beam indication type. A device can use DCI format 1_1 or 1_2 in a DL allocation to indicate joint downlink (DL) / uplink (UL) TCI states. Note on whether DCI should be used to indicate TCI states without scheduling DL data and how DCI should be used. In 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, at least one of the following alternatives is considered for selection. Alternative 0 - Additional DCI formats are not 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 a DCI acknowledgment mechanism (e.g., based on SPS PDSCH release, based on triggered SRS, based on DCI indicating SCell suspension) 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 suspension) can be solved considering the impact on PDCCH coverage and the scheduling mechanism. It can be solved whether a UE can assume that the application time configured by the BS is after an acknowledgment (ACK) transmission. Some aspects provide dedicated DCI formats other than 1_1 / 1_2 without a DL allocation applicable for joint TCI as well as separate DL / UL TCI. Support for a DCI acknowledgment mechanism (e.g., based on SPS PDSCH release, based on triggered SRS, based on DCI indicating SCell suspension) can be configured. If the format is based on existing DCI formats, the problem of how to identify DCI formats used only for beam indication can be solved.The UE can assume that the application time configured by the gNB is after the ACK transmission, or whether it can be assumed can be solved. Alternative - 3 DCI format 0_1 / 0_2 of the UL - related with UL grant, which is only applicable for the UL - dedicated TCI of the separate DL / UL TCI.

[0135]

[0142] On the beam indication signaling medium for supporting joint or separate DL / UL beam indication in the unified TCI framework, the device can support layer 1 (L1) - based beam indication by using at least UE - specific (unicast) DCI to indicate joint or separate DL / UL beam indication from the active TCI state. DCI formats 1_1 and 1_2 can 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, and 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 + at least one UL channel / RS, a separate DL common TCI state for indicating a common beam for two or more DL channels / RSs, and a separate UL common TCI state for indicating a common beam for two or more UL channels / RSs. In NR's Further enhanced MIMO (FeMIMO), on a 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 at least include a TCI state that includes at least one source RS for providing a criterion (UE assumption) for determining QCL or a spatial filter. In a unified TCI framework, to adapt to 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. In the case of a separate DL TCI, the source reference signals among the M TCIs provide QCL information at least for UE-dedicated reception on the PDSCH and for UE-dedicated reception on all or a subset of the CORESETs in a component carrier (CC). In the case of a separate UL TCI, the source reference signals among the N TCIs provide a criterion for determining a common UL transmission (TX) spatial filter at least for a dynamically permitted / configured-permitted-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 a resource set configured for antenna switching / codebook-based / non-codebook-based UL transmission.

[0137]

[0144] Types of beam indication: Type 1 - Joint DL / UL common TCI state for indicating a common beam for at least one DL channel / RS + at least one UL channel / RS; Type 2 - Separate DL common TCI state for indicating a common beam for two or more DL channels / RS; Type 3 - Separate UL common TCI state for indicating a common beam for two or more UL channels / RS; Type 4 - Separate DL single channel / RS TCI state for indicating a beam for a single DL channel / RS; Type 5 - Separate UL single channel / RS TCI state for indicating a beam for a single UL channel / RS; Type 6 - UL spatial relation information (SRI) for indicating a beam for a single UL channel / RS.

[0138]

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

[0139]

[0146] FIG. 8 is an example of the association between a DCI format and the shown configuration.

[0140]

[0147] The verification sequence may depend on the following resource allocation types: 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] In DCI formats 1_1 and 1_2, which may contain a TCI field in the DCI, when tci-PresentInDCI is set to "valid" (or tci-PresentForDCI-Format1-2-r16 is configured for the CORESET), the device can use the TCI field of DCI format 1_1 or (1_2) to indicate the TCI state ID. In other cases, among others, the following options may be possible. Option 1: The UE does not expect to receive a DCI that does not contain a TCI field to indicate the TCI state (without scheduling data). Option 2: The DCI may contain other fields to indicate the TCI state ID. Option 3: An implicit method may be used (the beam to be indicated is determined based on the CORESET beam of the DCI). In a multiple DCI (mDCI) multiple transmit-receive point (mTRP) scenario, the beam to be indicated is the CORESET beam and can be used for channels / RSs scheduled by the same CORESET pool identifier (ID). In the case of a single DCI (sDCI) mTRP, the TCI state to be indicated can be determined based on the CORESET beam (if the CORESET beam for transmitting the DCI corresponds to the TCI code points of two TCI states, the CORESET beam is the indicated beam; if the CORESET beam for transmitting the DCI corresponds to a single TCI state, find the lowest ID TCI code point corresponding to the TCI state pair containing the CORESET TCI state). In the case of DCI format 1_0 or UL DCI format, since the option does not contain a TCI state field, the device can use Options 1 to 3. In the case of UL DCI format, the device can use the field of the SRI (or UL TCI state), if present, to indicate the TCI state ID.

[0142]

[0149] There may be an option regarding whether both the DL TCI state and the UL TCI state can be signaled in one instance of the beam indication DCI. Option 1 - One DCI can indicate only one TCI state. In such a case, the UE may use an additional bit or other signaling to identify which TCI state pool the DCI is referring to, such as a UL TCI state pool or a DL TCI state pool, and 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 a 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 (modulation and coding scheme (MCS) field) to indicate another TCI. Option 2-2 - Use a field (TCI field) to indicate the ID of the TCI pair / set. Option 2-2-1 - The pairing / grouping of the TCI states is configured by BS signaling, and the DCI indicates the pairing / grouping ID. Option 2-2-2 - The 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 preconfigured by the BS. As an example, if the DCI indicates index "1" in the TCI field, both TCI states indexed "1" (in the DL and UL TCI state pools) are indicated.

[0143]

[0150] In the case of DCI that can indicate only one purpose at a time, to distinguish with DCI 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 others, SPS release / activation, type 3 HARQ request, secondary cell (SCell) suspension): different RNTIs, different DCI formats, at least one different field used for verification, different verification sequences in the same verification field.

[0144]

[0151] Figure 9 is an example of the association between the RNTI or DCI format and the configuration indicated in the DCI. Regarding Figure 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 RNTI and DCI format not used for other purposes. For example, the BS may use C-RNTI or MCS-C-RNTI for the indication TCI state and format 1_0 or 1_2 (or UL DCI) format. For format 1_0 or 1_2, the verification sequence / field may 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 the DCI field. For example, the BS may use fields that are mandatory (optionally absent) in the DCI format. A new verification field that is not mandatory may not be used for information fields for other purposes. As an addition or alternative to the DCI field shown in Figure 10, in the case of DCI1_1, possible fields include, among others, a TPC command (2 bits) for scheduled PUCCH, a PUCCH resource indicator (2 bits), or an SRS request (3 bits), and in the case of DCI1_2, possible fields include a TPC command (2 bits) for scheduled PUCCH.

[0146]

[0153] In some aspects, when the DCI uses a different DCI field for verification than for other purposes, a UE such as UE120 may be able to identify the received DCI used to indicate the TCI configuration without scheduling a downlink assignment. For example, when the received DCI uses DCI format 1_1 or 1_2 where the CRC is scrambled by the C-RNTI or MCS-C-RNTI, when the one-shot HARQ request is "0" or not available, when the bits in the FDRA field are all "1" or "0" (based on the resource allocation type), and when the bits in a field not used for other verification purposes (such as the TPC command for scheduled PUCCH matches a configured sequence when the field is all "1"), the UE may determine that the DCI indicates the TCI state without scheduling data. The TCI state ID may be indicated in the TCI state field (when tci-PresentInDCI is set to "valid" or when tci-PresentForDCI-Format1-2-r16 is configured for the CORESET). Alternatively, the BS may use at least one of, among others, the MCS field, the new data indicator (NDI) field, or the redundancy version (RV) field to indicate the TCI state.

[0147]

[0154] In some aspects, the DCI for beam indication that does not schedule a downlink allocation may use the same DCI format indicator, the same type of RNTI to scramble the CRC bits of the DCI, or the same fields for verification, as in other indication purposes such as SPS activation / deactivation, type 3 HARQ request, or secondary cell suspension indication. In such cases, a new verification sequence for beam indication may be defined using the same verification fields to distinguish the purpose of the DCI (for beam indication) from other indication purposes. For example, the DCI for indicating the TCI state to the UE may use the same DCI format, the same RNTI to scramble the CRC bits, and the same fields for verification as the DCI for indicating SPS release to the UE. In this example, the first verification sequence is defined differently for the DCI for indicating the TCI state with respect to the second verification sequence for indicating 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 inspecting 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, at least one of the MCS field, RV field, or FDRA field is using a configured sequence 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 is using 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, among other examples, the FDRA field, HARQ field, or antenna port field, to indicate the TCI state ID. In some aspects, rules may be defined such that a verification sequence for beam indication is not included in the same field of the DCI for other purposes.

[0149]

[0156] For verification purposes, and as an addition or alternative to fields used to indicate the TCI state ID, the DCI format used for beam indication (without scheduling data transmission allocations) may include information bits in one or more additional fields. For example, the DCI format may be defined to include, among other examples, information bits for a DCI format indicator, TDRA, an identifier for the DCI format, a carrier indicator, a bandwidth part (BWP) indicator, a downlink allocation index (if configured), a TPC command for scheduled PUCCH, a PUCCH resource indicator, or a PDSCH-to-HARQ feedback timing indicator (if present). In some aspects, one or more fields may be used to indicate information for locating a time resource or a frequency resource for ACK with respect to the DCI, or for power control parameters of a PUCCH for carrying ACK with respect to the DCI. In some aspects, one or more fields may be used to indicate information regarding the indicated TCI state, such as a power control configuration for 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 the DCI of the DCI format when the DCI is used for beam indication without scheduling data. For example, one or more evaluation rules may be defined to allow omission of defined fields from the DCI without preventing verification or information transfer for beam indication. In some aspects, when a defined field for verification or for indicating information does not exist in the DCI, the UE is not expected to receive DCI for indicating the TCI state ID. Alternatively, when a defined field does not exist in the DCI format, additional fields 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 a non-existent field. For example, the RV field may be used for verification in the DCI to indicate the TCI state without scheduling data, and the RV field may not be present or may not be configured in the DCI of DCI format 1_2. In this example, the UE may be configured not to receive DCI in format 1_2 to indicate the TCI state without scheduling data. Alternatively, when the RV field does not exist 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 such 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 for indicating TCI state information or additional information do not exist 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 two or more purpose indications (for example, at least one of the TCI indication, and SPS activation / deactivation, type 3 HARQ request, SCell suspension indication) at a time. In such cases, the UE does not expect to receive DCI for the TCI state and other purposes. Some aspects of this specification enable, for example, using a single DCI to indicate a TCI state and at least one of SPS activation / deactivation, type 3 HARQ, and SCell suspension. The BS and UE may use different combinations of verification fields and sequences from the single-purpose case in the DCI to indicate that the DCI indicates multiple purposes.

[0152]

[0159] In one aspect, the DCI format may be defined to indicate a TCI state and SPS activation or deactivation. For example, the BS may use a CS-RNTI in relation to DCI format 1_0, 1_1, or 1_2. In such cases, when the NDI field and the RV field are both "0", and the MCS field is a configured reserved index for initial TX different from the index used only for the TCI indication (or only for SPS / UL release / activation), the UE may determine that the DCI indicates a TCI state and SPS release / activation. In such cases, 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 where the CRC is scrambled by the C-RNTI or the modulation and coding scheme (MCS)-specific C-RNTI (MCS-C-RNTI), and when the one-shot HARQ request field is set to "1", and when the FDRA field is set to "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 requests type 3 HARQ without scheduling data. In such a case, the TCI state ID is indicated in the TCI state field when tci-PresentInDCI is set to "valid" (or tci-PresentForDCI-Format1-2-r16 is configured for the CORESET). In cases where this is not so, the DCI may use at least one of the MCS field, the NDI field, or the RV field to indicate the TCI state, for example, among the examples.

[0154]

[0161] When using DCI format 1_1 where the CRC is scrambled by a C-RNTI or an MCS-C-RNTI, when the one-shot HARQ request field does not exist or is 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 where it indicates only the TCI, the UE may determine that the DCI indicates a TCI state and requests type 3 HARQ without scheduling data. In such a case, the TCI state ID is indicated in the TCI state field when tci-PresentInDCI is set to "valid" (or tci-PresentForDCI-Format1-2-r16 is configured for the CORESET). In cases where that is not so, the DCI may use at least one of a PUCCH resource indicator or an SRS request, for example, to indicate the TCI state. The DCI may use the same field as shown in FIG. 10 to indicate the SCell suspension bitmap.

[0155]

[0162] FIG. 11 is a diagram showing an exemplary process 1100 implemented, for example, by a device. Process 1100 is an example of operations performed by a UE (e.g., UE120) related to the capability indication of DCI for beam indication without scheduling data.

[0156]

[0163] As shown in FIG. 11, in some aspects, process 1100 may include transmitting a capability indicator, where the capability indicator is associated with whether the UE supports DCI having a DCI format (block 1110). For example, the UE may transmit a capability indicator (such as by using the transmission component 604 shown in FIG. 6) as described herein, 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. In some aspects, the UE may include a first interface configured to output a capability indicator.

[0157]

[0164] As further shown in FIG. 11, in some aspects, 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 reception component 602 or the transmission 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 communication according to the capability indicator.

[0158]

[0165] Process 1100 may include additional aspects, such as any single aspect, or any combination of aspects, regarding one or more other processes described below or elsewhere in this document.

[0159]

[0166] In a first additional aspect, one or more configured fields are associated with 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, process 1100 includes receiving 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 indicating support for a DCI format that does not include scheduling data and another DCI format that includes scheduling data.

[0164]

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

[0165]

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

[0166]

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

[0167]

[0174] FIG. 12 is a diagram illustrating an exemplary process 1200, for example, implemented by a device. Process 1200 is an example of operations performed by a base station (e.g., base station 110) related to a capability indication of DCI for beam indication without scheduling data.

[0168]

[0175] As shown in FIG. 12, in some aspects, process 1200 may include receiving a capability indicator, where the capability indicator is associated with whether a UE supports DCI having a DCI format (block 1210). For example, a base station may receive a capability indicator (such as by using the receiving component 702 shown in FIG. 7) as described herein, where the capability indicator is associated with whether a 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. In some aspects, the BS may include a first interface configured to obtain a capability indicator.

[0169]

[0176] As further shown in FIG. 12, in some aspects, process 1200 may include communicating according to the capability indicator (block 1220). For example, a base station may communicate according to 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 communication according to the capability indicator.

[0170]

[0177] Process 1200 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 in this specification.

[0171]

[0178] In a first additional aspect, 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, process 1200 includes transmitting DCI having a DCI format, and communicating according to the capability indicator includes communicating according to the 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 indicating support for a DCI format without scheduling data and another DCI format with scheduling data.

[0176]

[0183] In a sixth additional aspect, the capability indicator is a first capability indicator indicating support for a DCI format without scheduling data.

[0177]

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

[0178]

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

[0179]

[0186] FIG. 13 is a diagram illustrating an example 1300 related to the indication of capabilities for the use of a DCI format for beam indication without scheduling data according to the present disclosure. As shown in FIG. 13, the base station 110 and the 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 for indicating support for one or more DCI formats, such as DCI format 1_1 or DCI format 1_2, among others. In some aspects, the UE 120 may transmit a single UE capability indication. For example, the UE 120 may transmit a UCI having a single field to indicate whether the UE 120 supports both a beam indication DCI using a downlink allocation and a beam indication DCI not using a downlink allocation. Alternatively, the UE 120 may transmit multiple capability indications, such as a first capability indication indicating whether the UE 120 supports a beam indication DCI using a downlink allocation and a second capability indication indicating whether the UE 120 supports a beam indication DCI not using a downlink allocation.

[0181]

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

[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 the TCI to be used 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 the 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, DCI format, verification field, or verification sequence. When the TCI field does not exist 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 no field exists, the UE 120 may determine that the DCI does not indicate the TCI state.

[0183]

[0190] In some aspects, UE 120 may identify multiple TCI states based on DCI. For example, UE 120 may receive DCI that identifies a single TCI within a TCI pool, and 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, UE 120 may receive DCI that identifies multiple TCIs, such as an uplink TCI and a downlink TCI. In this case, the DCI may include explicit indicators for the multiple TCIs (e.g., a first indicator for a first TCI in a TCI field and a second indicator for a second TCI in another field such as an MCS field). Alternatively, the DCI may include an identifier from which UE 120 may derive the multiple TCIs (e.g., an index value for which 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) for which the table lookup should then be performed may be configured by signaling received from 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 use the TCI identified from the DCI to transmit signaling to base station 110 (on the uplink) or receive signaling from base station 110 (on the downlink). In some aspects, UE 120 may communicate on another link according to a communication configuration such as a sidelink.

[0185]

[0192] The following provides an overview of some aspects of the present disclosure.

[0186]

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

[0187]

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

[0188]

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

[0189]

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

[0190]

[0197] Aspect 5: The method of Aspect 1 - 4, where the DCI includes a first indication of the TCI and a second indication of another configuration.

[0191]

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

[0192]

[0199] Aspect 7: The method of any of Aspect 1 - 6, where the TCI is based on a value of a TCI field parameter of the DCI.

[0193]

[0200] Aspect 8: The method of any of Aspect 1 - 7, where the TCI is based on a value of a non - TCI field parameter of the DCI.

[0194]

[0201] Aspect 9: Any of the methods of Aspects 1 to 8, where the TCI is based on one or more CORESET beams of the DCI.

[0195]

[0202] Aspect 10: Any of the methods of Aspects 1 to 9, where the DCI indicates a single TCI, and the TCI is associated with a TCI pool and further includes constituting a plurality of TCIs associated with the TCI pool based on the TCI.

[0196]

[0203] Aspect 11: Any of the methods of Aspects 1 to 9, where the DCI indicates a plurality of TCIs.

[0197]

[0204] Aspect 12: Any of the methods of Aspects 1 to 11, where the DCI includes a TCI field indicating an identifier of a set of TCIs.

[0198]

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

[0199]

[0206] Aspect 14: Any of the methods of Aspects 1 to 13, where the TCI includes a downlink TCI and an uplink TCI.

[0200]

[0207] Aspect 15: Any of the methods of Aspects 1 to 14, where the TCI is based on an RNTI associated with the DCI.

[0201]

[0208] Aspect 16: Any of the methods of Aspects 1 to 15, where the TCI is based on an essential field of the DCI.

[0202]

[0209] Aspect 17: Any of the methods of Aspects 1 to 16, where the TCI is based on a verification sequence configured for beam indication.

[0203]

[0210] Aspect 18: Any of the methods of Aspects 1 to 16, where the TCI is based on a value of a verification sequence associated with a non-TCI configuration.

[0204]

[0211] Aspect 19: A configured field associated with TCI does not exist in one or more configured fields of DCI, and a UE is configured to determine TCI based on at least one of another DCI, another indicator that is not DCI, another configured field that exists in one or more configured fields of DCI, and a default configuration, according to any one of the methods of Aspects 1 to 18.

[0205]

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

[0206]

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

[0207]

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

[0208]

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

[0209]

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

[0210]

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

[0211]

[0218] Aspect 26: Any method of Aspects 20 to 25, where the TCI is based on the value of the TCI field parameter of the DCI.

[0212]

[0219] Aspect 27: Any method of Aspects 20 to 26, where the TCI is based on the value of the non-TCI field parameter of the DCI.

[0213]

[0220] Aspect 28: Any method of Aspects 20 to 27, where the TCI is based on one or more CORESET beams of the DCI.

[0214]

[0221] Aspect 29: Any method of Aspects 20 to 28, where the DCI indicates a single TCI, the TCI is associated with a TCI pool, and further includes communicating according to a plurality of TCIs associated with the TCI pool based on the TCI.

[0215]

[0222] Aspect 30: Any method of Aspects 20 to 28, where the DCI indicates a plurality of TCIs.

[0216]

[0223] Aspect 31: Any method of Aspects 20 to 30, where the DCI includes a TCI field indicating an identifier of a set of TCIs.

[0217]

[0224] Aspect 32: The method of Aspect 30, where the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from a plurality of configured groupings of TCIs having a common attribute.

[0218]

[0225] Aspect 33: Any method of Aspects 20 to 32, where the TCI includes a downlink TCI and an uplink TCI.

[0219]

[0226] Aspect 34: Any method of Aspects 20 to 33, where the TCI is based on a radio network temporary identifier (RNTI) associated with the DCI.

[0220]

[0227] Aspect 35: Any method of Aspects 20 to 34, wherein the TCI is based on an essential field of the DCI.

[0221]

[0228] Aspect 36: Any method of Aspects 20 to 35, wherein the TCI is based on a verification sequence configured for beam indication.

[0222]

[0229] Aspect 37: Any method of Aspects 20 to 36, wherein the TCI is based on a value of a verification sequence associated with a non-TCI configuration.

[0223]

[0230] Aspect 38: A method of wireless communication performed by a UE device, comprising 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 according to the capability indicator.

[0224]

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

[0225]

[0232] Aspect 40: Any method of Aspects 38 to 39, wherein the capability indicator identifies UE support for DCI having a DCI format.

[0226]

[0233] Aspect 41: Further comprising receiving 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.

[0227]

[0234] Aspect 42: Any method of Aspects 38 to 41, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message.

[0228]

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

[0229]

[0236] Aspect 44: The method according to any of Aspects 38 to 43, wherein the capability indicator is a first capability indicator indicating 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 that includes scheduling data, and communicating according to the capability indicator includes communicating according to the first capability indicator and the second capability indicator.

[0231]

[0238] Aspect 46: A method of wireless communication performed by an apparatus of a BS, comprising receiving a capability indicator, wherein the capability indicator is associated with whether a 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 according to the capability indicator.

[0232]

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

[0233]

[0240] Aspect 48: The method according to any of Aspects 46 to 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 DCI having a DCI format, and communicating according to an ability indicator includes communicating according to a TCI associated with one or more configured fields.

[0235]

[0242] Aspect 50: The method according to any one of Aspects 46 to 49, wherein the ability indicator is included in an optional field of the UCI message.

[0236]

[0243] Aspect 51: The method according to any one of Aspects 46 to 50, wherein the ability indicator is a single ability indicator indicating support for a DCI format without scheduling data and another DCI format including scheduling data.

[0237]

[0244] Aspect 52: The method according to any one of Aspects 46 to 51, wherein the ability indicator is a first ability indicator indicating support for a DCI format without scheduling data.

[0238]

[0245] Aspect 53: The method of Aspect 34, further comprising receiving a second ability indicator indicating support for another DCI format including scheduling data, and communicating according to the ability indicator includes communicating according to the first ability indicator and the second ability indicator.

[0239]

[0246] Aspect 54: An apparatus for wireless communication in a device, comprising 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 implement the 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 the method of one or more of Aspects 1 to 19.

[0241]

[0248] Aspect 56: An apparatus for wireless communication, comprising at least one means for implementing 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, wherein the code includes instructions executable by a processor to implement the 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, wherein the set of instructions includes one or more instructions that, when executed by one or more processors of a device, cause the device to implement the method of one or more of Aspects 1 to 19.

[0244]

[0251] Aspect 59: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, wherein the instructions are executable by the processor to cause the device to implement the 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 the method of one or more of Aspects 20 to 37.

[0246]

[0253] Aspect 61: An apparatus for wireless communication, comprising at least one means for implementing 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 the 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 implement the method of one or more of Aspects 20 to 37.

[0249]

[0256] Aspect 64: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the device to implement the 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, the memory and the one or more processors being configured to implement the method of one or more of Aspects 38 to 45.

[0251]

[0258] Aspect 66: An apparatus for wireless communication, comprising at least one means for implementing 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-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 implement the method of one or more of Aspects 38-45.

[0254]

[0261] Aspect 69: An apparatus for wireless communication in a device, 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 implement the method of one or more of Aspects 46-53.

[0255]

[0262] Aspect 70: A device for wireless communication, including a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to implement the method of one or more of Aspects 46-53.

[0256]

[0263] Aspect 71: An apparatus for wireless communication, including at least one means for implementing the method of one or more of Aspects 46-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-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 the method of one or more of Aspects 46-53.

[0259]

[0266] The foregoing disclosure provides illustration and description, and is neither comprehensive nor intended to limit the aspects to the exact forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or obtained from practice of the aspects.

[0260]

[0267] As used herein, the term "component" is broadly construed as hardware, firmware, or a combination of hardware and software. A processor as used herein is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is broadly construed to mean "based at least in part on." Meeting a threshold as used herein may, among other things, refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold. The phrase referring to "at least one of" a list of items herein refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" encompasses a, b, c, a-b, a-c, b-c, and a-b-c.

[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." Further, as used herein, the article "the" includes one or more items referenced with respect to the article "the" and may be used interchangeably with "one or more." Further, the terms "set" and "group" as used herein 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." When only one item is intended, the phrase "only one" or similar words are used. Also, the terms "has," "have," "having," and similar terms as used herein are open-ended terms. Further, the term "or" as used herein is inclusive when used in series and may 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 illustrative logical, logical 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. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends upon the particular application and the design constraints imposed on the overall system.

[0263]

[0270] The hardware and data processing apparatus used to implement the various exemplary logics, logical blocks, modules, and circuits described in connection with the aspects disclosed in this specification can be implemented or carried out using a general-purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration. In some aspects, certain processes and methods can be implemented by circuitry that is specific to a given function.

[0264]

[0271] In one or more aspects, the functions described can be implemented in hardware, digital electronic circuitry, computer software, firmware, and structural equivalents of the above structures disclosed in this specification, or in any combination thereof. Aspects of the subject matter described in this specification can 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] When implemented in software, the functions can be stored on a computer-readable medium as one or more instructions or codes, or can be transmitted via a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in processor-executable software modules that may exist on a computer-readable medium. A computer-readable medium includes both a computer storage medium and a computer communication medium, including any medium that can enable the transfer of a computer program from one location to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM (registered trademark), 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 the desired program code in the form of instructions or data structures and can be accessed by a computer. Also, any connection can be properly termed a computer-readable medium. As used herein, disk and disc include compact disc (CD), laser disc (registered trademark), optical disc, digital versatile disc (DVD), floppy (registered trademark) disk and Blu-ray (registered trademark) disc, where disk typically magnetically reproduces data and disc optically reproduces data with a laser. Combinations of the above should also be included within the scope of computer-readable media. Further, the operations of a method or algorithm can exist as one or any combination of codes and instructions on a machine-readable medium and a computer-readable medium that can be incorporated into a computer program product, or as a set thereof.

[0266]

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

[0267]

[0274] Further, the terms "upper" and "lower" are sometimes used for simplicity in the description of the figures and indicate relative positions corresponding to the orientation of the figures on a properly oriented page and may not reflect the proper orientation of any device implemented. Those skilled in the art will readily appreciate that this may be the case.

[0268]

[0275] Also, some of the features described herein with respect to separate aspects may be implemented in combination in a single aspect. Conversely, various features described with respect to a single aspect may be implemented separately, or in any suitable sub-combination, in a plurality of aspects. Moreover, features are described above as acting in some combinations and may even be claimed as such initially, but one or more features from the claimed combination may in some cases be deleted from the combination, and the claimed combination may be directed to a sub-combination, or a variant of a sub-combination.

[0269]

[0276] Similarly, the operations are illustrated in the drawings in a particular order, but this should not be understood as requiring that such operations be performed in the particular order or sequence shown, or that all illustrated operations be performed, in order to achieve the desired result. Additionally, the drawings may schematically illustrate another exemplary process in the form of a flowchart. However, other operations not illustrated may be incorporated into the exemplary process schematically shown. 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 aspects described above 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 with each other in a single software product or packaged into multiple software products. Further, other aspects fall within the scope of the following claims. In some cases, the acts recited in the claims may be performed in a different order and still achieve the desired result. The invention described in the claims of the present application at the time of filing is appended below. [C1] A method of wireless communication implemented by a device of a user equipment (UE), receiving 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, communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields A method comprising: [C2] The method according to C1, 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 another type of indication. [C3] The method according to C1, 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 setting. [C4] The second indication is a secondary cell (SCell) suspension indication, a semi-persistent scheduling (SPS) release indication, an SPS activation indication, or a hybrid automatic repeat request (HARQ) indication The method according to C3, including at least one of: [C5] The method according to C1, 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 sets (CORESET) beams of the DCI. [C6] The method according to C1, wherein the DCI indicates a plurality of TCIs or a single TCI associated with a TCI pool from which the plurality of TCIs are to be constructed. [C7] The method according to C1, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs, and the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from a plurality of configured groupings of TCIs having a common attribute. [C8] The method according to C1, wherein the TCI includes a downlink TCI and an uplink TCI. [C9] The TCI is The radio network temporary identifier (RNTI) associated with the DCI, The mandatory fields of the DCI, A verification sequence configured for beam indication, or The value of the verification sequence associated with the non-TCI configuration The method according to C1, based on at least one of the above. [C10] The configured field associated with the TCI does not exist in the one or more configured fields of the DCI, and the UE Another DCI, Another indicator other than DCI, Another configured field existing in the one or more configured fields of the DCI, or The default configuration The method according to C1, configured to determine the TCI based on at least one of the above. [C11] A method of wireless communication performed by a device of a base station (BS), Transmitting a DCI having a downlink control information (DCI) format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data, Communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields A method comprising the above. [C12] The method according to C11, 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 another type of indication. [C13] The method according to C11, 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 setting. [C14] The second indication is Secondary cell (SCell) suspension indication, Semi-persistent scheduling (SPS) release indication, SPS activation indication, or Hybrid automatic repeat request (HARQ) indication The method according to C13, including at least one of the above. [C15] The method according to C11, wherein the TCI is based on the value of the TCI field parameter of the DCI, the value of the non-TCI field parameter of the DCI, or one or more control resource sets (CORESET) beams of the DCI. [C16] The method according to C11, wherein the DCI indicates a plurality of TCIs or a single TCI associated with a TCI pool to be composed of the plurality of TCIs. [C17] The method according to C11, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs, and the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from a plurality of configured groupings of TCIs having a common attribute. [C18] The method according to C11, wherein the TCI includes a downlink TCI and an uplink TCI. [C19] The TCI is a radio network temporary identifier (RNTI) associated with the DCI, an essential field of the DCI, a verification sequence configured for beam indication, or a value of a verification sequence associated with a non-TCI configuration The method according to C11, based on at least one of the above. [C20] A method of wireless communication performed by a device of a user equipment (UE), comprising: transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports a DCI having a downlink control information (DCI) format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data; communicating according to the capability indicator The method comprising. [C21] The method according to C20, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI). [C22] The method according to C20, wherein the capability indicator identifies UE support for the DCI having the DCI format. [C23] Further comprising receiving the DCI having the DCI format, and communicating according to the capability indicator is communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields The method according to C22, comprising. The method according to C20, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message. [C24] The method according to C20, wherein the capability indicator is a single capability indicator indicating support for the DCI format without scheduling data and another DCI format with scheduling data. [C25] ​ [C26] The method according to C20, wherein the ability indicator is a first ability indicator indicating support for the DCI format that does not include scheduling data. [C27] Transmitting a second ability indicator indicating support for another DCI format including scheduling data further comprising communicating according to the ability indicator, communicating according to the first ability indicator and the second ability indicator The method according to C26, comprising: [C28] A method of wireless communication performed by an apparatus of a base station (BS), receiving an ability indicator, wherein the ability indicator is associated with whether a user equipment (UE) supports a DCI having a downlink control information (DCI) format, wherein the DCI format includes one or more configured fields, and wherein the DCI format does not include scheduling data, communicating according to the ability indicator A method comprising: [C29] The method according to C28, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI). [C30] The method according to C28, wherein the ability indicator identifies UE support for the DCI having the DCI format. [C31] Transmitting the DCI having the DCI format further comprising communicating according to the ability indicator, communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields The method according to C30, comprising: [C32] The method according to C28, wherein the ability indicator is included in an optional field of an uplink control information (UCI) message. [C33] The method according to C28, wherein the ability indicator is a single ability indicator indicating support for the DCI format that does not include scheduling data and another DCI format that includes scheduling data. [C34] The method according to C28, wherein the ability indicator is a first ability indicator indicating support for the DCI format that does not include scheduling data. [C35] Receiving a second ability indicator indicating support for another DCI format including scheduling data further comprising, and communicating according to the capability indicator, communicating according to the first capability indicator and the second capability indicator The method according to C34, comprising: [C36] An apparatus for wireless communication in a user equipment (UE), a memory, one or more processors coupled to the memory and the processor is configured to receive 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, communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields An apparatus configured to perform [C37] The apparatus according to C36, 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 another type of indication. [C38] The apparatus according to C36, 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 setting. [C39] An apparatus for wireless communication in a base station (BS), a memory, one or more processors coupled to the memory and the processor is configured to transmit 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, communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields An apparatus configured to perform [C40] The apparatus according to C39, 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 another type of indication. [C41] The apparatus according to C39, 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 setting. [C42] An apparatus for wireless communication in a user equipment (UE), comprising: a memory; one or more processors coupled to the memory; wherein the processors are configured to: transmit a capability indicator, wherein the capability indicator is associated with whether the UE supports 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; communicate according to the capability indicator; An apparatus configured as such. [C43] The apparatus according to C42, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI). [C44] The apparatus according to C42, wherein the capability indicator identifies UE support for the DCI having the DCI format. [C45] The one or more processors are further configured to: receive the DCI having the DCI format; wherein the one or more processors are configured to communicate according to the transmission configuration indicator (TCI) associated with the one or more configured fields in order to communicate according to the capability indicator. The apparatus according to C44, configured as such. The apparatus according to C42, wherein the capability indicator is included in an optional field of an uplink control information (UCI) message. [C46] An apparatus for wireless communication in a base station (BS), comprising: [C47] a memory; one or more processors coupled to the memory; wherein the processors are configured to: receive a capability indicator, wherein the capability indicator is associated with whether a user equipment (UE) supports 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; communicate according to the capability indicator; An apparatus configured as such. The apparatus according to C47, wherein the one or more configured fields are associated with a transmission configuration indicator (TCI). [C48] ​ [C49] The apparatus according to C47, wherein the ability indicator identifies UE support for the DCI having the DCI format. [C50] The one or more processors are further configured to transmit the DCI having the DCI format and the one or more processors are further configured to communicate according to the ability indicator and communicate according to a transmission configuration indicator (TCI) associated with the one or more configured fields. The apparatus according to C49, configured as such.

Claims

1. A method of wireless communication performed by an apparatus of a user equipment (UE), comprising: receiving downlink control information (DCI) having a DCI format, wherein the DCI includes one or more configured fields and does not include scheduling data; communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields; wherein the TCI is based on at least one of: a radio network temporary identifier (RNTI) associated with the DCI, an essential field of the DCI, a verification sequence configured for beam indication, or a value of a verification sequence associated with a non-TCI configuration. The method according to 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 another type of indication.

2. The method according to 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 setting.

3.

4. wherein the second indication includes at least one of: a secondary cell (SCell) suspension indication, a semi-persistent scheduling (SPS) release indication, an SPS activation indication, or a hybrid automatic repeat request (HARQ) indication. The method according to claim 3.

5. The method according to 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 sets (CORESET) beams of the DCI.

6.

7. The method according to claim 1, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs, and the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from a plurality of configured groupings of TCIs having a common attribute.

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

9. The configured field associated with the TCI does not exist in the one or more configured fields of the DCI, and the UE is another DCI, another indicator that is not a DCI, another configured field existing in the one or more configured fields of the DCI, or a default configuration The method according to claim 1, wherein the method is configured to determine the TCI based on at least one of them.

10. A method of wireless communication implemented by an apparatus of a base station (BS), comprising: transmitting a DCI having a downlink control information (DCI) format, wherein the DCI includes one or more configured fields, and wherein the DCI does not include scheduling data; communicating according to a transmission configuration indicator (TCI) associated with the one or more configured fields and wherein the TCI is a radio network temporary identifier (RNTI) associated with the DCI, an essential field of the DCI, a verification sequence configured for beam indication, or a value of a verification sequence associated with a non-TCI configuration The method is based on at least one of them.

11. The method according to claim 10, 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 another type of indication.

12. The method according to claim 10, 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 setting.

13. The second indication is a secondary cell (SCell) suspension indication, a semi-persistent scheduling (SPS) release indication, SPS activation indication, or hybrid automatic repeat request (HARQ) indication The method according to claim 12, comprising at least one of them.

14. The method according to claim 10, 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 sets (CORESET) beams of the DCI.

15. The method according to claim 10, wherein the DCI indicates a plurality of TCIs, or a single TCI associated with a TCI pool for constituting the plurality of TCIs.

16. The method according to claim 10, wherein the DCI includes a TCI field indicating an identifier of a set of TCIs, and the set of TCIs is a single configured grouping of TCIs or a group of TCIs selected from a plurality of configured groupings of TCIs having a common attribute.

17. The method according to claim 10, wherein the TCI includes a downlink TCI and an uplink TCI.

Images