Downlink Control Information (DCI) format and capability reporting for beam indication without scheduling data

Abstract

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

Description

Technical Field

[0001] Cross - reference to related applications

[0001] This patent application claims 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 a variety of telecommunications services, including telephone, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long-Term Evolution (LTE®). LTE / LTE Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard published by the Third Generation Partnership Project (3GPP®).

[0004]

[0004] A wireless network may include several base stations (BS) that can support communication for several user equipment (UEs). UEs may communicate with BSs via downlink (DL) and 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, BSs may also be called node B, LTE evolved node B (eNB), gNB, access point (AP), radio head, transmit / receive point (TRP), new radio (NR) BS, or 5G node B.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, national, regional, and even global levels. NR, sometimes called 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, lowering costs, improving service, utilizing new spectra, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefixes (CP) (CP-OFDM) on DL (or a combination thereof), using CP-OFDM or SC-FDM (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM), for example) on UL (or a combination thereof), as well as by supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. [Overview of the project]

[0006]

[0006] The systems, methods, and devices of this disclosure each have several inventive embodiments, and not one of these embodiments alone is responsible for any of the desirable attributes disclosed herein.

[0007]

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

[0008]

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

[0009]

[0009] Another inventive aspect of the subject matter described herein may be implemented in a method of wireless communication carried out by a base station (BS), and includes transmitting a DCI having a DCI format, wherein the DCI includes one or more configured fields, and wherein the DCI communicates according to a TCI associated with one or more configured fields, which does not include scheduling data.

[0010]

[0010] Another inventive aspect of the subject matter described herein may be implemented in an apparatus for wireless communication in a UE, comprising a memory and one or more processors coupled to the memory, and configured to receive a DCI having a DCI format, wherein the DCI comprises one or more configured fields, and herein the DCI communicates according to a TCI associated with one or more configured fields, which does not include scheduling data.

[0011]

[0011] Another inventive aspect of the subject matter described herein may be implemented in an apparatus for wireless communication in a BS, comprising a memory and one or more processors coupled to the memory, and configured to transmit a DCI having a DCI format, wherein the DCI comprises one or more configured fields, and wherein the DCI communicates according to a TCI associated with one or more configured fields, which does not include scheduling data.

[0012]

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

[0013]

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

[0014]

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

[0015]

[0015] Another inventive aspect of the subject matter described herein may be implemented in a non-temporary computer-readable medium storing a set of instructions for wireless communication and includes one or more instructions that, when executed by one or more processors of a BS, cause the BS to transmit a DCI having a DCI format, wherein the DCI includes one or more configured fields, and herein the DCI communicates according to a TCI associated with one or more configured fields, which does not include scheduling data.

[0016]

[0016] Another inventive aspect of the subject matter described herein may be implemented in an apparatus for wireless communication, the apparatus comprising means for receiving a DCI having a DCI format, wherein the DCI comprises one or more configured fields, and wherein the DCI communicates according to a TCI associated with one or more configured fields, which does not include scheduling data.

[0017]

[0017] Another inventive aspect of the subject matter described herein may be implemented in an apparatus for wireless communication, the apparatus comprising means for transmitting a DCI having a DCI format, wherein the DCI comprises one or more configured fields, and wherein the DCI communicates according to a TCI associated with one or more configured fields, the DCI not comprising scheduling data.

[0018]

[0018] Another inventive aspect of the subject matter described herein may be implemented in a method of wireless communication carried out by an apparatus of a UE, 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 comprises one or more configured fields, and wherein the DCI format does not comprise scheduling data, and communicates according to the capability indicator.

[0019]

[0019] Another inventive aspect of the subject matter described herein may be implemented in a method of wireless communication carried out by BS, comprising receiving a capability indicator, wherein the capability indicator is associated with whether UE supports DCI having a DCI format, wherein the DCI format comprises one or more configured fields, and wherein the DCI format communicates according to the capability indicator, wherein the DCI format does not comprise scheduling data.

[0020]

[0020] In some embodiments, one or more configured fields are associated with a TCI. In some embodiments, the method includes receiving a 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 herein may be implemented in an apparatus for wireless communication in a UE comprising a memory and one or more processors coupled to the memory, and is configured to transmit a capability indicator, wherein the capability indicator is associated with whether the UE supports DCI having a DCI format, wherein the DCI format comprises one or more configured fields, and wherein the DCI format communicates according to the capability indicator, wherein the DCI format does not include scheduling data.

[0022]

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

[0023]

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

[0024]

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

[0025]

[0025] Another inventive aspect of the subject matter described herein may be implemented in a BS device for wireless communications including a first interface configured to receive capability indicators, wherein the capability indicators are associated with whether a 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 the second or first interface is configured to communicate according to the capability indicators.

[0026]

[0026] Another inventive aspect of the subject matter described herein may be implemented in a non-temporary computer-readable medium storing a set of instructions for wireless communication, the one or more instructions causing the UE to transmit a capability indicator when executed by one or more processors of the UE, 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 communicates 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, causes 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 other examples, the BS device may be configured to perform one or more operations of the wireless communication method performed by the device, such as the device's processing system or one or more interfaces of the device.

[0032]

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

[0033]

[0033] Details of one or more implementations of the subject matter described herein are described in the accompanying drawings and the following description. Other features, embodiments, and advantages will become apparent from the description, drawings, and claims. Note that the relative dimensions in the following figures may not be drawn to a constant scale. [Brief explanation of the drawing]

[0034] [Figure 1]

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

[0035] This diagram shows an example of a base station (BS) communicating with user equipment (UE) in a wireless network. [Figure 3]

[0036] A diagram illustrating an example of using a beam for communication between a BS (Broadcasting Station) and an UE (Union Engine). [Figure 4]

[0037] For example, a diagram illustrating a similar process carried out by UE. [Figure 5] For example, a diagram illustrating a similar process implemented by BS. [Figure 6]

[0038] Block diagram of an exemplary device for wireless communication. [Figure 7] Block diagram of an exemplary device for wireless communication. [Figure 8]

[0039] A diagram relating to an exemplary aspect of this disclosure. [Figure 9] A diagram relating to an exemplary aspect of this disclosure. [Figure 10] A diagram relating to an exemplary aspect of this disclosure. [Figure 11]

[0040] For example, a diagram illustrating a similar process carried out by UE. [Figure 12] For example, a diagram illustrating a similar process implemented by BS. [Figure 13]

[0041] A diagram relating to an exemplary aspect of this disclosure. [Modes for carrying out the invention]

[0035]

[0042] Similar reference numbers and symbols in various drawings indicate the same elements.

[0036]

[0043] The following description covers several implementations for the purpose of illustrating the inventive aspects of the disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in numerous different ways. Some of the examples in this disclosure are based on wireless and wired local area network (LAN) communication using the IEEE 802.11 wireless standard, the IEEE 802.3 Ethernet® standard, and the IEEE 1901 power line communication (PLC) standard. However, the implementations described are used for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, or 5G, or further implementations thereof, and include 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-Purpose Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Infrastructure Radio (TETRA), Wideband CDMA (W-CDMA®), Evolution Data Optimized (EV-DO), 1xEV-DO, EV-DO RevA, and EV-DO. It can be implemented in any device, system, or network capable of transmitting and receiving radio frequency signals in accordance with any wireless communication standards including RevB, High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Advanced High Speed ​​Packet Access (HSPA+), Long-Term Evolution (LTE), AMPS, or any other known signal.

[0037]

[0044] In some situations, a base station (BS) may transmit downlink control information (DCI) to provide configuration information to user equipment (UE). For example, a BS may transmit DCI to indicate, among other things, semi-persistent scheduling (SPS) release, SPS activation, hybrid automatic retransmission request (HARQ) configuration, or secondary cell dormancy configuration. A BS may also transmit DCI to update the beam configuration for the UE. For example, a BS may transmit DCI consisting of DCI format 1_1 or DCI format 1_2, which has a downlink resource allocation for scheduling downlink data transmissions, to indicate a transmission configuration indicator (TCI) state as defined in the 3GPP specification, or another similar data structure. A TCI may represent one or more pseudo-collocation (QCL) rules, where the rule associates 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 another reference signal) with a relevant channel property (e.g., one or more spatial parameters such as Doppler shift, Doppler spread, mean delay, delay spread, spatial filter, or other properties). Such a QCL rule may include QCL type A, QCL type B, QCL type C, or QCL type D data structures as defined by the 3GPP specification.

[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 may 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 standards (such as 3GPP specifications).

[0039]

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

[0040]

[0047] Certain implementations of the subject matter described herein may be implemented to achieve one or more of the following potential benefits: As described herein, a UE may receive DCIs that do not schedule data transmissions and communicate according to TCIs associated with one or more configured fields of the DCI. The use of DCIs to identify TCIs that do not schedule data transmissions may reduce signaling overhead compared to having information that schedules data transmissions to be included in the DCI that identifies the TCI. A unified TCI framework may be possible that simplifies beam management procedures not only for downlink and uplink channels but also for data and control channels in 3GPP(NR) systems by enabling the use of different types of beam indications in TCIs within DCIs. The inclusion of explicit beam indications, such as TCIs, within DCIs may improve signaling flexibility, such as when a DCI is transmitted to indicate a different configuration, such as SPS release, SPS activation, HARQ configuration, or secondary cell quiescing configuration, among other examples. By providing a capability indicator to show whether the UE supports DCI without downlink data to indicate TCI, the scenario in which the BS transmits DCI without downlink data to indicate TCI and the UE is unable to interpret such DCI is avoided. By avoiding the above scenario, the likelihood of communication errors from UEs unable to 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] Figure 1 shows an example of a wireless network 100. The wireless network 100 is or may be an element of a 5G (NR) network, an LTE network, or another type of network. The wireless network 100 may include one or more base stations 110 (shown as 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 called an NR BS, node B, gNB, 5G node B (NB), access point, or transmit / receive point (TRP). Each BS may provide communication coverage to 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 that services this coverage area, or a combination thereof, depending on the context in which the term is used.

[0042]

[0049] A BS can provide communication coverage to macrocells, picocells, femtocells, other types of cells, or combinations thereof. A macrocell can cover a relatively large geographical area (e.g., a radius of several kilometers) and can enable unlimited access by UEs subscribing to the service. A picocell can cover a relatively small geographical area and can enable unlimited access by UEs subscribing to the service. A femtocell can cover a relatively small geographical area (e.g., a home) and can enable limited access by UEs associated with a femtocell (e.g., UEs in a Limited Subscriber Group (CSG)). A BS for a macrocell is sometimes called a macroBS. A BS for a picocell is sometimes called a picoBS. A BS for a femtocell is sometimes called a femtoBS or homeBS. In the example shown in Figure 1, BS110a could be a macroBS for macrocell 102a, BS110b could be a picoBS for picocell 102b, and BS110c could be a femtoBS for femtocell 102c. A BS may support one or more (for example, three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “Node B”, “5G NB”, and “cell” may be used interchangeably in this specification.

[0043]

[0050] In some examples, cells may not necessarily be fixed, and the geographical area of ​​a cell may move according to the location of the mobile BS. In some examples, 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 a combination thereof, using any suitable transport network.

[0044]

[0051] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from upstream stations (e.g., BS or UE) and send those data transmissions to downstream stations (e.g., UE or BS). A relay station may also be a UE that can relay transmissions to other UEs. In the example shown in Figure 1, relay BS110d may communicate with macro BS110a and UE120d to facilitate communication between macro BS110a and UE120d. Relay BS may also be called relay stations, relay base stations, or relays.

[0045]

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

[0046]

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

[0047]

[0054] Multiple UE120s (e.g., UE120a, UE120b, UE120c, etc.) may be distributed across the entire wireless network 100, and each UE may be stationary or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. UEs may be cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, netbooks, smartbooks, ultrabooks, medical devices or medical equipment, biosensors / biometric devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radios), vehicle components or vehicle sensors, smart meters / smart sensors, industrial manufacturing equipment, global positioning system devices, or any other suitable devices configured to communicate via wireless or wired media.

[0048]

[0055] Some UEs may be considered machine-type communications (MTC) UEs or advanced or enhanced machine-type communications (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags that can communicate with base stations, other devices (e.g., remote devices), or any other entities. Wireless nodes may provide connectivity to or for a network (e.g., a wide area network such as the Internet or a cellular network) via wired or wireless communication links. Some UEs may be considered Internet of Things (IoT) devices or implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE120 may be contained within a housing that houses the components of UE120, such as processor components, memory components, or other components. In some examples, processor components and memory components may be combined together. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) can be operationally coupled, communicatively coupled, electronically coupled, or electrically coupled, among other examples.

[0049]

[0056] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network may support a specific RAT and may operate on one or more frequencies. RATs are sometimes called wireless technologies or air interfaces. Frequencies are sometimes called carriers or frequency channels. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0050]

[0057] In some embodiments, two or more UE120s (for example, shown as UE120a and UE120e) may communicate directly using one or more sidelink channels (for example, without using base station 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-anything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), or mesh networks. In such examples, UE120s may perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by base station 110.

[0051]

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

[0052]

[0059] Figure 2 shows an example of a base station (BS) 110 communicating with a UE 120 in a wireless network 100. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, where generally T ≥ 1 and R ≥ 1.

[0053]

[0060] At base station 110, the transmit processor 220 may receive data from data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on channel quality indicators (CQI) received from the UEs, process (e.g., encode and modulate) the data for each UE based on the MCS selected for that UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information) and control information (e.g., CQI requests, authorizations, or upper-layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulated reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may, where applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, and may provide T output symbol streams to T modulators (MODs) 232a-232t. Each modulator 232 may process its respective output symbol stream (e.g., for OFDM) to acquire an output sample stream. Each modulator 232 may further process its output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to acquire 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-252r may receive downlink signals from base station 110 or other base stations and provide the received signals to demodulators (DEMOD) 254a-254r, respectively. Each demodulator 254 may adjust the received signal (e.g., filter, amplify, downconvert, and digitize) to acquire an input sample. Each demodulator 254 may further process the input sample (e.g., for OFDM) to acquire a received symbol. A MIMO detector 256 may acquire received symbols from all R demodulators 254a-254r and, where applicable, perform MIMO detection on the received symbols and provide the detected symbols. A receiving processor 258 may process the detected symbols (e.g., demodulate and decode) and provide the decoded data for UE120 to the data sink 260 and the decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may, in some examples, determine 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 embodiments, one or more components of the UE120 may be contained within a housing.

[0055]

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

[0056]

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

[0057]

[0064] On the uplink, in UE120, the transmit processor 264 may receive and process data from data source 262 and control information from controller / processor 280 (for example, for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may, where applicable, be precoded by the TX MIMO processor 266, further processed by modulators 254a-254r (for example, for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some embodiments, the modulators and demodulators of UE120 (e.g., MOD / DEMOD 254) may be included in the modem of UE120. In some embodiments, UE120 includes transceivers. The transceiver may include any combination of an antenna 252, a modulator 254, a demodulator 254, a MIMO detector 256, a receiving processor 258, a transmitting processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and memory 282 to carry out 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 where applicable, and may be further processed by receiving processor 238 to obtain decoded data and control information sent by UE 120. The receiving 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, which may communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling one or more UE 120 for downlink communication, uplink communication, or a combination thereof. In some embodiments, the modulator and demodulator of base station 110 (e.g., MOD / DEMOD 232) may be included in the modem of base station 110. In some embodiments, base station 110 includes transceivers. The transceiver may include any combination of (one or more) antennas 234, modulator 232, demodulator 232, MIMO detector 236, receiving processor 238, transmitting processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to carry out any aspect of the processes described herein.

[0059]

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

[0060]

[0067] The processing system of UE120 may interface with other components of UE120, process information (such as inputs or signals) received from other components, and output information to other components. 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 a receiver, and thus UE120 may receive information or signal inputs, and information may be passed to the processing system. In some cases, the “second interface” may refer to the interface between the processing system of the chip or modem and a transmitter, and thus UE120 may transmit information output from the chip or modem. It will be readily apparent to those skilled in the art that the second interface may also acquire or receive information or signal inputs, and the first interface may also output, transmit, or provide information.

[0061]

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

[0062]

[0069] The processing system of the base station 110 may interface with other components of the base station 110 and may 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 the base station 110 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some cases, the “first interface” may refer to the interface between the processing system of the chip or modem and a receiver, and thus the base station 110 may receive information or signal inputs, and the information may be passed to the processing system. In some cases, the “second interface” may refer to the interface between the processing system of the chip or modem and a transmitter, and thus the base station 110 may transmit information output from the chip or modem. It will be readily apparent to those skilled in the art that the second interface may also acquire or receive information or signal inputs, and the first interface may also output, transmit, or provide information.

[0063]

[0070] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, or any other component in Figure 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 will be described in more detail elsewhere in this specification. The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, or any other component (or combination of components) in Figure 2 may implement or direct the operation of, for example, process 400 in Figure 4, process 500 in Figure 5, process 1100 in Figure 11, process 1200 in Figure 12, or other processes described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some embodiments, memory 242 and memory 282 may include non-temporary computer-readable media for storing one or more instructions (e.g., code or program code) for wireless communication. When one or more instructions are executed by one or more processors of the base station 110 or UE 120 (for example, directly or after compilation, translation, or interpretation), one or more processors, UE 120, or base station 110 may be caused to perform or instruct the operation of, for example, process 400 in Figure 4, process 500 in Figure 5, process 1100 in Figure 11, process 1200 in Figure 12, or other processes described herein.

[0064]

[0071] In some embodiments, the UE120 may include, among other examples, means for transmitting a DCI having a DCI format, means for communicating according to a TCI associated with one or more configured fields, wherein the DCI includes one or more configured fields and the DCI does not include scheduling data, and means for transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports a 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, or means for communicating according to the capability indicator. In some embodiments, such means may include one or more components of the UE120 described with respect to Figure 2, such as a controller / processor 280, a transmit processor 264, a TX MIMO processor 266, a MOD 254, an antenna 252, a DEMOD 254, a MIMO detector 256, or a receive processor 258.

[0065]

[0072] In some embodiments, the base station 110 may include, among other examples, means for transmitting a DCI having a DCI format, means for communicating according to a TCI associated with one or more configured fields, wherein the DCI includes one or more configured fields and the DCI does not include scheduling data, and means for receiving a capability indicator, wherein the capability indicator is associated with whether the UE supports a 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, or means for communicating according to the capability indicator. In some embodiments, such means may include one or more components of the base station 110 described with respect to Figure 2, such as an antenna 234, a DEMOD 232, a MIMO detector 236, a receiving processor 238, a controller / processor 240, a transmitting processor 220, a TX MIMO processor 230, a MOD 232, or an antenna 234.

[0066]

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

[0067]

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

[0068]

[0075] Base station 110 may transmit to UE 120 located within the coverage area of ​​base station 110. Base station 110 and UE 120 may be configured for beamformed communication, where base station 110 may transmit in the direction of UE 120 using a directional BS transmit beam, and UE 120 may receive the transmission using a directional UE receive beam. Each BS transmit beam may have an associated beam ID, beam direction, or beam symbol, among other things. Base station 110 may 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 UE120's receiving circuit. UE120 may identify a particular BS transmit beam 305, designated as BS transmit beam 305-A, and a particular UE receive beam 310, designated as UE receive beam 310-A, that offers relatively favorable performance (e.g., having the best channel quality of different measured combinations of BS transmit beam 305 and 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 base station 110 may select for transmission to UE120. In this way, UE120 can achieve and maintain a beam pair link (BPL) with base station 110 for downlink communication (for example, a combination of BS transmit beam 305-A and UE receive beam 310-A), which BPL can be further improved and maintained according to one or more established beam shaping procedures.

[0070]

[0077] Downlink beams, such as the BS transmit beam 305 or the UE receive 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. QCL properties may include, for example, Doppler shift, Doppler spread, mean delay, delay spread, or spatial receive parameters. In some examples, each BS transmit beam 305 may be associated with an SSB, and the UE 120 may indicate the BS transmit beam 305 by transmitting an uplink transmit on the SSB resource associated with the BS transmit beam 305. A particular SSB may have associated TCI states (for example, with respect to an antenna port or beamforming). In some examples, the base station 110 may indicate the downlink BS transmit beam 305 based on antenna port QCL properties that may be indicated by the TCI state. The TCI state can be associated with a single downlink reference signal set (e.g., SSB and aperiodic, periodic, or semi-persistent CSI-RS) for different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, mean delay, delay spread, or spatial receive parameters). If the QCL type indicates spatial receive parameters, the QCL type may correspond to the analog receive beamforming parameters of the UE receive beam 310 at UE 120. Thus, UE 120 can select the corresponding UE receive beam 310 from the set of BPLs based on the base station 110 indicating the BS transmit beam 305 via TCI indication.

[0071]

[0078] 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 beam that base station 110 uses 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 beam that base station 110 can use for downlink transmission on the physical downlink control channel (PDCCH) or in a control resource set (CORESET). UE 120 may also maintain a set of activated TCI states for receiving downlink shared channel transmission and CORESET transmission. When TCI states are activated for UE 120, UE 120 may have one or more antenna configurations based on the TCI states, and UE 120 may not need to reconfigure the antenna or antenna weighting configuration. In some examples, a set of activated TCI states for the UE120 (e.g., an activated PDSCH TCI state and an activated CORESET TCI state) may be configured by configuration messages such as Radio Resource Control (RRC) messages.

[0072]

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

[0073]

[0080] Base station 110 may receive uplink transmissions via one or more BS receive beams 320. Base station 110 may identify a particular UE transmit beam 315, designated as UE transmit beam 315-A, and a particular BS receive beam 320, designated as BS receive beam 320-A, that offer relatively favorable performance (e.g., having the best channel quality of different measured combinations of UE transmit beam 315 and BS receive beam 320). In some examples, base station 110 may transmit an indication of which UE transmit beam 315 is identified by base station 110 as a UE transmit beam that base station 110 may select for transmission from UE 120. In this way, UE 120 and base station 110 may achieve and maintain a BPL (e.g., a combination of UE transmit beam 315-A and BS receive beam 320-A) for uplink communication, which BPL may be further improved and maintained according to one or more established beam improvement procedures. Uplink beams, such as the UE transmit beam 315 or the BS receive beam 320, may be associated with spatial relationships. These spatial relationships may indicate the directivity or characteristics of the uplink beams, as well as one or more QCL properties, as described herein.

[0074]

[0081] Figure 4 shows an exemplary process 400, which is performed by a UE, for example. Process 400 is an example of an operation performed by a UE (e.g., UE120) that involves using DCI for beam indication without scheduling data.

[0075]

[0082] As shown in Figure 4, in some embodiments, process 400 may include receiving a 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 a DCI having a DCI format, as described herein (for example, by using the receiving component 602 shown in Figure 6), where the DCI includes one or more configured fields and the DCI does not include scheduling data. In some embodiments, the UE may include a first interface configured to acquire a DCI having a DCI format.

[0076]

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

[0077]

[0084] Process 400 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below or elsewhere in this specification.

[0078]

[0085] In the first additional embodiment, 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 but does not include another type of indication.

[0080]

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

[0081]

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

[0082]

[0089] In a fifth additional aspect, the second indication includes at least one of a secondary cell pause indication, a semi-persistent scheduling release indication, a semi-persistent scheduling activation indication, or a hybrid auto-retransmission 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 the non-TCI field parameter of the DCI.

[0085]

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

[0086]

[0093] In a ninth additional aspect, DCI refers to a single TCI, the TCI is associated with a TCI pool, and process 400 further comprises configuring multiple TCIs associated with the TCI pool based on the TCI.

[0087]

[0094] In a tenth additional aspect, DCI refers to multiple TCIs.

[0088]

[0095] In the eleventh additional aspect, the DCI includes a TCI field that identifies the set of TCIs.

[0089]

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

[0090]

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

[0091]

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

[0092]

[0099] In the 15th additional aspect, the TCI is based on the mandatory fields of the DCI.

[0093]

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

[0094]

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

[0095]

[0102] In an 18th additional aspect, the process 400 further includes 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 communicates according to the capability indicator, wherein the DCI format does not include scheduling data.

[0096]

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

[0097]

[0104] Figure 4 shows an exemplary block of process 400, but in some embodiments, process 400 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those illustrated in Figure 4. Additionally or alternatively, two or more blocks of process 400 may be executed in parallel.

[0098]

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

[0099]

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

[0100]

[0107] As shown in Figure 5, in some embodiments, process 500 may include communicating according to a transmit 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 (for example, by using a receive component 702 or a transmit component 704 shown in Figure 7), as described herein. In some embodiments, the base station may include a first or second interface configured to output or receive information according to a TCI.

[0101]

[0108] Process 500 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below or elsewhere in this specification.

[0102]

[0109] In the first additional embodiment, 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 but does not include another type of indication.

[0104]

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

[0105]

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

[0106]

[0113] In a fifth additional aspect, the second indication includes at least one of a secondary cell pause indication, a semi-persistent scheduling release indication, a semi-persistent scheduling activation indication, or a hybrid auto-retransmission 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 embodiment, the TCI is based on one or more CORESET beams of the DCI.

[0110]

[0117] In a ninth additional aspect, the DCI represents 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, DCI refers to multiple TCIs.

[0112]

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

[0113]

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

[0114]

[0121] In the 13th 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 the 15th additional aspect, the TCI is based on the required fields of the DCI.

[0117]

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

[0118]

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

[0119]

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

[0120]

[0127] Figure 5 shows an exemplary block of process 500, but in some embodiments, process 500 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those illustrated in Figure 5. Additionally or alternatively, two or more blocks of process 500 may be executed in parallel.

[0121]

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

[0122]

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

[0123]

[0130] The receiving component 602 may receive communications from the device 606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 602 may provide the received communications to one or more other components of the device 600. In some embodiments, the receiving component 602 may perform signal processing on the received communications (among examples being 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 the device 606. In some embodiments, the receiving component 602 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof of the UE described above with respect to Figure 2. In some embodiments, the receiving component 602 may be a component of a processing system. For example, “processing system of device 600” may refer to a system including various other components or sub-components of device 600.

[0124]

[0131] The transmitting component 604 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 606. In some embodiments, one or more other components of the device 606 may generate communications and provide the transmitted component 604 with the generated communications for transmission to the device 606. In some embodiments, the transmitting component 604 may perform signal processing on the generated communications (among examples being filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 606. In some embodiments, the transmitting component 604 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the UE described above with respect to Figure 2. In some embodiments, the transmitting component 604 may be collated with the receiving component 602 in the transceiver. In some embodiments, the transmitting component 604 may be a component of a processing system.

[0125]

[0132] The processing system of device 600 may interface with other components of device 600 and may 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 device 600 may include a processing system, a receiving component 602 for receiving or acquiring information, and a transmitting component 604 for outputting, transmitting, or providing information. In some cases, the receiving component 602 may refer to an interface between the processing system of the chip or modem and a receiver, and thus device 600 may receive information or signal inputs, 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 modem and a transmitter, and thus device 600 may transmit information output from the chip or modem. It will be readily apparent to those skilled in the art that a second interface may also acquire or receive information or signal inputs, and the first interface may also output, transmit, or provide information.

[0126]

[0133] The receiving component 602 may receive 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. The receiving component 602 or the transmitting component 604 may communicate according to a Transmit Control Indicator (TCI) associated with one or more configured fields. The determining component 608 may determine a TCI based on one or more configured fields of the DCI. The transmitting component 604 may transmit a capability indicator, wherein the capability indicator is associated with whether the UE supports a 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. The receiving component 602 or the transmitting component 604 may communicate according to the capability indicator.

[0127]

[0134] Figure 7 is a block diagram of an exemplary device 700 for wireless communication. Device 700 may be a base station, or a base station may include device 700. In some embodiments, device 700 includes a receiving component 702 and a transmitting component 704, which may communicate with each other (for example, via one or more buses or one or more other components). As shown, device 700 may communicate with another device 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, device 700 may include one or more of the component 708, among other examples.

[0128]

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

[0129]

[0136] The receiving component 702 may receive communications from the device 706, such as reference signals, control information, data communications, or a combination thereof. The receiving component 702 may provide the received communications to one or more other components of the device 700. In some embodiments, the receiving component 702 may perform signal processing on the received communications (among examples being 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 the device 706. In some embodiments, the receiving component 702 may include one or more antennas, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the base station described above with respect to Figure 2. In some embodiments, the receiving component 702 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.

[0130]

[0137] The transmitting component 704 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 706. In some embodiments, one or more other components of the device 706 may generate communications and provide the transmitted component 704 with the generated communications for transmission to the device 706. In some embodiments, the transmitting component 704 may perform signal processing on the generated communications (among examples being filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) and transmit the processed signals to the device 706. In some embodiments, the transmitting component 704 may include one or more antennas, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the base station described above with respect to Figure 2. In some embodiments, the transmitting component 704 may be collated with the receiving component 702 in the transceiver. In some embodiments, the transmitting component 704 may be a component of a processing system. For example, the processing system of the device 700 may refer to a system that includes various other components or sub-components of the device 700.

[0131]

[0138] The processing system of device 700 may interface with other components of device 700 and may 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 device 700 may include a processing system, a receiving component 702 for receiving or acquiring information, and a transmitting component 704 for outputting, transmitting, or providing information. In some cases, the receiving component 702 may refer to an interface between the processing system of the chip or modem and a receiver, and thus device 700 may receive information or signal inputs, and the information may be passed to the processing system. In some cases, the transmitting component 704 may refer to an interface between the processing system of the chip or modem and a transmitter, and thus device 700 may transmit information output from the chip or modem. It will be readily apparent to those skilled in the art that a second interface may also acquire or receive information or signal inputs, and the first interface may also output, transmit, or provide information.

[0132]

[0139] The transmitting component 704 may transmit 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. The receiving component 702 or the transmitting component 704 may communicate according to a Transmit Control Indicator (TCI) associated with one or more configured fields. The configuration component 708 may configure one or more configured fields of the DCI. The receiving component 702 may receive a capability indicator, wherein the capability indicator is associated with whether the UE supports a 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. The receiving component 702 or the transmitting component 704 may communicate according to the capability indicator.

[0133]

[0140] Figures 8 to 10 are diagrams relating to exemplary embodiments of the present disclosure.

[0134]

[0141] This section focuses on how DCI should be used to update beam indications within a unified TCI framework. The unified TCI framework includes common beam indication types. Devices can use DCI format 1_1 or 1_2 with DL assignments to indicate joint downlink (DL) / uplink (UL) TCI status. This section focuses on whether or how DCI should be used to indicate TCI status without scheduling DL data. For DCI-based beam indications, in terms of support for DCI formats for beam indications, in addition to DCI formats 1_1 / 1_2 with DL assignments, at least one of the following alternatives should be selected: Alternative 0 - No additional DCI format is supported. DCI formats 1_1 and 1_2 without DL assignments are applicable for joint TCIs as well as separate DL / UL TCIs. In such cases, support for DCI acknowledgment mechanisms may be configured (among other examples, based on SPS PDSCH release, based on triggered SRS, based on DCI indicating SCell pauses). The question of how to identify DCI formats 1_1 / 1_2 used solely for beam indication (not for scheduling PDSCH reception, not for indicating SPS PDSCH release, or not for indicating SCell pause) can be resolved by considering the impact on PDCCH coverage and scheduling mechanisms. The question of whether the UE can assume that the application time configured in the BS is after the acknowledgment (ACK) transmission can be resolved. Several embodiments provide dedicated DCI formats other than 1_1 / 1_2 without DL allocation, applicable for joint TCIs and separate DL / UL TCIs. Support for DCI acknowledgment mechanisms (including those based on SPS PDSCH release, triggered SRS, and DCI indicating SCell pause) can be configured. If the format is based on an existing DCI format, the question of how to identify the DCI format used solely for beam indication can be resolved.The UE may be able to resolve whether it can / should assume that the application time configured in the gNB is after the ACK transmission. Alternative-3 DCI format 0_1 / 0_2 for UL relationships with UL authorization, applicable only for UL-only TCIs of separate DL / UL TCIs.

[0135]

[0142] On a beam indication signaling medium to support joint or separate DL / UL beam indications within a unified TCI framework, the device may support Layer 1 (L1) based beam indications using at least UE-specific (unicast) DCI to indicate joint or separate DL / UL beam indications from an active TCI state. DCI formats 1_1 and 1_2 may be reused for joint beam indications. 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 indications).

[0136]

[0143] Three types of TCI states are considered: a joint DL / UL common TCI state to indicate a common beam for at least one DL channel / RS and at least one UL channel / RS; a separate DL common TCI state to indicate a common beam for two or more DL channels / RS; and a separate UL common TCI state to indicate a common beam for two or more UL channels / RS. 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 include at least a TCI state that includes at least one source RS to provide a criterion (UE assumption) for determining the QCL or spatial filter. In a unified TCI framework, to accommodate the case of separate beam indication for UL and DL, a device may utilize two separate TCI states, one for DL ​​and one for UL. In the case of separate DL TCIs, the source reference signals in the M TCIs provide QCL information for at least UE-only reception on the PDSCH and for UE-only reception on all or a subset of the CORESET in the component carrier (CC). In the case of separate UL TCIs, the source reference signals in the N TCIs provide a criterion for determining a common UL transmit (TX) spatial filter for at least the dynamically authorized / configured authorized-based physical uplink shared channel (PUSCH) and for all or a subset of the dedicated PUSCH resources in the CC. In some cases, this UL TX spatial filter may also apply to all SRS resources in the resource set configured for antenna switching / codebook-based / non-codebook-based UL transmits.

[0137]

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

[0138]

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

[0139]

[0146] Figure 8 shows an example of the relationship between the DCI format and the configuration shown.

[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 include a TCI field within the DCI, if tci-PresentInDCI is set to "enabled" (or tci-PresentForDCI-Format1-2-r16 is configured for 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 other examples, the following options may be possible: Option 1: The UE does not expect to receive a DCI that does not include a TCI field to indicate the TCI state (without scheduling data). Option 2: The DCI may include other fields to indicate the TCI state ID. Option 3: An implicit method may be used (the indicated beam is determined based on the CORESET beam of the DCI). In a multiple DCI (mDCI) multiple transmit / receive point (mTRP) scenario, the indicated beam is the CORESET beam and may be used for channels / RS scheduled by the same CORESET pool identifier (ID). In the case of a single DCI (sDCI)mTRP, the indicated TCI state can be determined based on the CORESET beam (if the CORESET beam sending the DCI corresponds to a TCI code point for two TCI states, the CORESET beam is the indicated beam; if the CORESET beam sending 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). For DCI format 1_0 or UL DCI format, the device can use options 1-3 as the options do not include a TCI state field. For UL DCI format, the device can use the SRI (or UL TCI state) field, if present, to indicate the TCI state ID.

[0142]

[0149] There are options regarding whether both DL TCI states and UL TCI states can be signaled in a single instance of beam-indicating DCI. Option 1 - A single DCI can indicate only one TCI state. In such a case, the UE may be configured in different TCI state pools and may use additional bits or other signaling to identify which TCI state pool the DCI is referring to, such as the UL TCI state pool or the DL TCI state pool, all TCI states may be configured in the same pool, and the UE may use other fields as well as TCI states to indicate a TCI state. Option 2 - A single DCI can indicate two or more TCI states, where multiple TCI states may include one DL and one UL. Option 2-1 - There may be direct indication of multiple TCI states in a DCI. In such a case, the DCI may use a 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 a TCI pair / set. Option 2-2-1 - Pairing / grouping of TCI states is configured by BS signaling, and DCI indicates the ID of the pairing / grouping. 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 cases, multiple pools / groups may be pre-configured by BS. For example, if 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, which can indicate only one purpose at a time, to distinguish it from DCI for indicating other purposes, beam-indicating DCI may use at least one of the following options from the indication method for other purposes (among other examples, SPS release / activation, type 3 HARQ request, secondary cell (SCell) quiesce): different RNTI, different DCI format, at least one different field used for verification, different verification sequences within the same verification field.

[0144]

[0151] Figure 9 shows an example of the association between an RNTI or DCI format and the configuration shown in DCI. With respect to Figure 9, a new RNTI for beam indication may be defined, a new DCI format for beam indication may be defined, or BS may use a combination of RNTI and DCI formats that are not used for other purposes. For example, BS may use C-RNTI or MCS-C-RNTI for an indication TCI state and format 1_0 or 1_2 (or UL). The DCI format can be used. For format 1_0 or 1_2, the verification sequence / fields can be any possible combination. For example, BS may reuse the SPS / UL type 2 release format. In such a case, for DCI format 1_0, 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 shows an example of the use of verification information in DCI fields. For example, BS may use fields that are required (optionally absent) in the DCI format. New verification fields that are not required may not be used for information fields for other purposes. As additions or replacements to the DCI fields shown in Figure 10, for DCI1_1, possible fields include, among other examples, a TPC command for scheduled PUCCH (2 bits), a PUCCH resource indicator (2 bits), or an SRS request (3 bits), and for DCI1_2, possible fields include a TPC command for scheduled PUCCH (2 bits).

[0146]

[0153] In some aspects, when a DCI uses different DCI fields for verification than those used for other purposes, a UE such as UE120 may identify an incoming DCI used to indicate TCI configuration without scheduling downlink allocations. For example, when an incoming DCI uses DCI format 1_1 or 1_2, where the CRC is scrambled by C-RNTI or MCS-C-RNTI, when a one-shot HARQ request is "0" or unavailable, when all bits in the FDRA field are "1" or "0" (based on resource allocation type), and when bits in fields not used for other verification purposes (such as a TPC command for a scheduled PUCCH matching a configured sequence, where all fields are "1"), the UE may determine that the DCI indicates TCI status without scheduling data. The TCI status ID may be shown in the TCI status field (if tci-PresentInDCI is set to "Enabled" or if tci-PresentForDCI-Format1-2-r16 is configured for CORESET). Alternatively, BS may use at least one of the following fields to indicate the TCI status: the MCS field, the New Data Indicator (NDI) field, or the Redundant Version (RV) field, among others.

[0147]

[0154] In some embodiments, a DCI for beam indication that does not schedule 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 / release, type 3 HARQ request, or secondary cell quiescence indication. In such cases, a new verification sequence for beam indication may be defined to distinguish the purpose of the DCI (beam indication) from other indication purposes by using the same verification fields. For example, a DCI for indicating a TCI status to a UE may use the same DCI format, the same RNTI to scramble the CRC bits, and the same fields for verification, as a DCI for indicating an SPS release to a UE. In this example, the first verification sequence is defined differently for the DCI for indicating a TCI status with respect to the second verification sequence for indicating an SPS release (in at least one of the verification fields). For example, the RV field verification sequence may be defined as all "1" for beam indication purposes and all "0" for SPS release or activation. In this way, the UE can determine the indication purpose by examining the bits in the RV field of the received DCI.

[0148]

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

[0149]

[0156] As an addition or replacement for fields used for verification purposes and fields indicating TCI status IDs, 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 information bits for, among other examples, a DCI format indicator, TDRA, DCI format identifier, carrier indicator, bandwidth part (BWP) indicator, downlink allocation index (if configured), TPC command for scheduled PUCCH, PUCCH resource indicator, or PDSCH vs. HARQ feedback timing indicator (if present). In some embodiments, one or more fields may be used to indicate information for power control parameters of a PUCCH for locating time or frequency resources for ACKs to the DCI, or for carrying ACKs to the DCI. In some embodiments, one or more fields may be used to indicate information about the indicated TCI status, such as the power control configuration of the uplink transmission related to the indicated TCI status.

[0150]

[0157] In some embodiments, one or more fields defined for the DCI format and used for verification or information may be omitted from the DCI in 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 the omission of defined fields from the DCI without interfering with verification or information transfer for beam indication. In some embodiments, when no defined fields for verification or information are present in the DCI, the UE is not expected to receive a DCI for indicating a TCI state ID. Alternatively, when no defined fields are present in the DCI format, additional fields may be used for verification or information. In some embodiments, the UE may determine a reserved sequence of bits to enable interpretation of the DCI for missing fields. For example, the RV field may be used for verification in the DCI to indicate a TCI state without scheduling data, and the RV field may not be present or constituted in the DCI in DCI format 1_2. In this example, the UE may be configured not to receive a DCI in format 1_2 to indicate a TCI state without scheduling data. Alternatively, when an RV field is not present in the RV field, the UE may be configured to assume a predefined sequence, such as "0" in the field. Alternatively, rules may be defined to allow the UE to use an alternative field (such as an MCS field) for validation. Similar rules may apply in cases where other fields used to indicate TCI status information or additional information are not present in the DCI. For example, if a configured field is not included in the DCI, the UE may use a configured alternative field for validation. Additional or alternative, the UE may use a configured default sequence for validation. Additional or alternative, the UE may use a different DCI.

[0151]

[0158] Some BSs and UEs may not support indications for two or more purposes at once (for example, TCI indication and at least one of SPS activation / release, type 3HARQ request, or SCell pause indication). In such cases, the UE does not expect to receive a DCI to indicate a TCI state and other purposes. Some aspects of this specification allow the use of a single DCI to indicate a TCI state and at least one of SPS activation / release, type 3HARQ, or SCell pause, for example. In the case of a single purpose in a DCI, the BS and UE may use different combinations of validation fields and sequences to indicate that the DCI indicates multiple purposes.

[0152]

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

[0153]

[0160] When the CRC uses DCI format 1_1 scrambled by C-RNTI or Modulation and Coding Scheme (MCS) specific C-RNTI (MCS-C-RNTI), and when the one-shot HARQ request field is set to "1", 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 of showing only TCI, the UE may determine that the DCI is showing a TCI state and is requesting a type 3 HARQ without scheduling data. In such cases, the TCI state ID is shown in the TCI state field if tci-PresentInDCI is set to "enabled" (or tci-PresentForDCI-Format1-2-r16 is configured for CORESET). Otherwise, the DCI may use at least one of the MCS field, NDI field, or RV field, among others, to show a TCI state.

[0154]

[0161] When the CRC uses DCI format 1_1 scrambled by C-RNTI or MCS-C-RNTI, when the one-shot HARQ request field is absent or set to "0", when the FDRA field is "1" or "0" (based on resource allocation type), and when the TPC command for scheduled PUCCH matches a configured sequence different from the sequence used in cases showing only TCI, the UE may determine that the DCI is showing a TCI state and requesting a type 3 HARQ without scheduling data. In such cases, the TCI state ID is shown in the TCI state field if tci-PresentInDCI is set to "enabled" (or tci-PresentForDCI-Format1-2-r16 is configured for CORESET). Otherwise, the DCI may use at least one of the PUCCH resource indicator or SRS request, among others, to indicate the TCI state. The DCI may use the same fields shown in Figure 10 to indicate the SCell pause bitmap.

[0155]

[0162] Figure 11 shows an exemplary process 1100, which is performed, for example, by the apparatus. Process 1100 is an example in which a UE (e.g., UE120) performs operations related to DCI capability indication for beam indication without scheduling data.

[0156]

[0163] As shown in Figure 11, in some embodiments, 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 as described herein (for example, by using the transmit component 604 shown in Figure 6), 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 embodiments, the UE may include a first interface configured to output the capability indicator.

[0157]

[0164] As further shown in Figure 11, in some embodiments, process 1100 may include communicating according to capability indicators (block 1120). For example, the UE may communicate according to capability indicators (for example, by using the receiving component 602 or transmitting component 604 shown in Figure 6) as described herein. In some embodiments, the UE may include a first or second interface configured to acquire or output communications according to capability indicators.

[0158]

[0165] Process 1100 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below or elsewhere in this specification.

[0159]

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

[0160]

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

[0161]

[0168] In a third additional embodiment, process 1100 includes receiving a DCI having a DCI format, and communicating according to a capability indicator, and 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 the uplink control information (UCI) message.

[0163]

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

[0164]

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

[0165]

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

[0166]

[0173] Figure 11 shows an exemplary block of process 1100, but in some embodiments, process 1100 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those illustrated in Figure 11. Additionally or alternatively, two or more blocks of process 1100 may be executed in parallel.

[0167]

[0174] Figure 12 shows an exemplary process 1200, which is performed, for example, by the device. Process 1200 is an example in which a base station (e.g., base station 110) performs operations related to DCI capability indication for beam indication without scheduling data.

[0168]

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

[0169]

[0176] As further shown in Figure 12, in some embodiments, process 1200 may include communicating according to capability indicators (block 1220). For example, a base station may communicate according to capability indicators (for example, by using the receiving component 702 or the transmitting component 704 shown in Figure 7) as described herein. In some embodiments, the BS may include a first or second interface configured to output or acquire communications according to capability indicators.

[0170]

[0177] Process 1200 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below or elsewhere in this specification.

[0171]

[0178] In the first additional embodiment, 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 a DCI having a DCI format, and communicating according to a capability indicator, and communicating according to a TCI associated with one or more configured fields.

[0174]

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

[0175]

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

[0176]

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

[0177]

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

[0178]

[0185] Figure 12 shows an exemplary block of process 1200, but in some embodiments, process 1200 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those illustrated in Figure 12. Additionally or alternatively, two or more blocks of process 1200 may be executed in parallel.

[0179]

[0186] Figure 13 shows an example related to capability indication for the use of the DCI format for beam indication without scheduling data, as disclosed herein. As shown in Figure 13, base station 110 and UE 120 can communicate with each other.

[0180]

[0187] As shown by reference number 1305, UE120 may transmit capability indications to base station 110. For example, UE120 may transmit a UCI indicating whether UE120 supports the DCI format for beam indication without scheduling data. In this case, the UCI may include optional fields to indicate support for one or more DCI formats, such as DCI format 1_1 or DCI format 1_2, among others. In some embodiments, UE120 may transmit a single UE capability indication. For example, UE120 may transmit a UCI with a single field to indicate whether UE120 supports both beam indication DCI with downlink allocation or beam indication DCI without downlink allocation. Alternatively, UE120 may transmit multiple capability indications, such as a first capability indication indicating whether UE120 supports beam indication DCI with downlink allocation, and a second capability indication indicating whether UE120 supports beam indication DCI without downlink allocation.

[0181]

[0188] As indicated by reference number 1310, base station 110 may transmit a DCI and UE 120 may receive it. For example, UE 120 may receive a beam indication DCI that does not schedule downlink data, based on the fact that UE 120 provides a capability indication to show that UE 120 supports beam indication DCI that does not use downlink allocation. In this case, the beam indication DCI could be DCI format 1_1, DCI format 1_2, DCI format 1_0, or uplink format DCI, among other examples, including one or more configured fields to indicate TCI. Additional or alternative, the beam indication DCI may include one or more configured fields for other indications, such as secondary cell quiescence indications, in addition to TCI.

[0182]

[0189] As indicated by reference number 1315, UE120 may determine the communication configuration based on the DCI. For example, UE120 may determine the TCI to be used when communicating with base station 110. In some embodiments, UE120 may determine that the DCI includes TCI fields for determining the communication configuration. For example, UE120 may parse the DCI to identify fields indicating whether the TCI indication is included in the DCI. Additionally or alternatively, UE120 may determine that the DCI includes TCI fields based on the RNTI, DCI format, verification fields, or verification sequence. When the TCI field is not present in the DCI, UE120 may determine the TCI based on other information. For example, UE120 may determine that the TCI is included in the DCI based on another field in the DCI, the CORESET beam of the DCI, or the default configuration. In another example, when the field is not present, UE120 may determine that the DCI does not indicate a TCI state.

[0183]

[0190] In some embodiments, UE120 may identify multiple TCI states based on the DCI. For example, UE120 may receive a DCI that identifies a single TCI within a TCI pool, and UE120 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, UE120 may receive a DCI that identifies multiple TCIs, such as uplink TCIs and downlink TCIs. In this case, the DCI may include explicit indicators of the multiple TCIs (e.g., a first indicator of a first TCI in a TCI field, and a second indicator of a second TCI in another field, such as an MCS field). Alternatively, the DCI may include an identifier from which UE120 can derive multiple TCIs (e.g., an index value from which UE120 can perform a table lookup to identify multiple TCIs corresponding to an index value). In this case, the table (or another data structure or pool) from which the table lookup should be performed may consist of signaling received from base station 110.

[0184]

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

[0185]

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

[0186]

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

[0187]

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

[0188]

[0195] Embodiment 3: The method of Embodiment 2, wherein DCI includes an indication of TCI but does not include another type of indication.

[0189]

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

[0190]

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

[0191]

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

[0192]

[0199] Embodiment 7: The TCI is determined by any of Embodiments 1 to 6, based on the value of the TCI field parameter of the DCI.

[0193]

[0200] Embodiment 8: The TCI is determined by any of Embodiments 1 to 7, based on the values ​​of the non-TCI field parameters of the DCI.

[0194]

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

[0195]

[0202] Embodiment 10: Any method of Embodiments 1 to 9, further comprising the DCI representing a single TCI, the TCI being associated with a TCI pool, and comprising multiple TCIs associated with the TCI pool based on the TCI.

[0196]

[0203] Embodiment 11: Any method according to Embodiments 1 to 9, wherein the DCI represents multiple TCIs.

[0197]

[0204] Embodiment 12: Any method of Embodiments 1 to 11, wherein the DCI includes a TCI field indicating an identifier for a set of TCIs.

[0198]

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

[0199]

[0206] Embodiment 14: Any method according to Embodiments 1 to 13, wherein the TCI includes a downlink TCI and an uplink TCI.

[0200]

[0207] Embodiment 15: A method of any of Embodiments 1 to 14 in which the TCI is based on the RNTI associated with the DCI.

[0201]

[0208] Embodiment 16: The TCI is based on the required fields of the DCI, using any of the methods described in Embodiments 1 to 15.

[0202]

[0209] Embodiment 17: A method of any of Embodiments 1 to 16 in which TCI is based on a verification sequence configured for beam indication.

[0203]

[0210] Embodiment 18: A method of any of Embodiments 1 to 16 in which TCI is based on the value of a verification sequence associated with a non-TCI configuration.

[0204]

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

[0205]

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

[0206]

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

[0207]

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

[0208]

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

[0209]

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

[0210]

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

[0211]

[0218] Embodiment 26: The TCI is determined by any of the methods in Embodiments 20 to 25, based on the value of the TCI field parameter of the DCI.

[0212]

[0219] Embodiment 27: The TCI is determined by any of the methods in Embodiments 20 to 26, based on the values ​​of the non-TCI field parameters of the DCI.

[0213]

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

[0214]

[0221] Embodiment 29: Any method of Embodiments 20 to 28, further comprising the DCI representing a single TCI, the TCI being associated with a TCI pool, and communicating according to a plurality of TCIs associated with the TCI pool based on the TCI.

[0215]

[0222] Embodiment 30: Any method of Embodiments 20 to 28, wherein DCI represents multiple TCIs.

[0216]

[0223] Embodiment 31: Any method of Embodiments 20 to 30, wherein the DCI includes a TCI field indicating an identifier for a set of TCIs.

[0217]

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

[0218]

[0225] Embodiment 33: Any method according to Embodiments 20 to 32, wherein the TCI includes a downlink TCI and an uplink TCI.

[0219]

[0226] Embodiment 34: The TCI is based on a Radio Network Temporary Identifier (RNTI) associated with the DCI, using any of the methods in Embodiments 20 to 33.

[0220]

[0227] Embodiment 35: The TCI is determined by any of the methods in Embodiments 20 to 34, based on the required fields of the DCI.

[0221]

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

[0222]

[0229] Embodiment 37: The TCI is determined by any of the methods in Embodiments 20 to 36, based on the values ​​of the verification sequence associated with the non-TCI configuration.

[0223]

[0230] Embodiment 38: A method of wireless communication performed by a device of a UE, 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 comprises one or more configured fields, and wherein the DCI format comprises scheduling data, and communicates according to the capability indicator.

[0224]

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

[0225]

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

[0226]

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

[0227]

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

[0228]

[0235] Embodiment 43: Any method of Embodiments 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] Embodiment 44: Any method of Embodiments 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] Embodiment 45: The method of Embodiment 44, further comprising transmitting a second capability indicator indicating support for another DCI format including scheduling data, wherein communication according to the capability indicator includes communicating according to the first capability indicator and the second capability indicator.

[0231]

[0238] Embodiment 46: A method of wireless communication performed by a BS device, 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] Embodiment 47: The method of Embodiment 46, wherein one or more configured fields are associated with the TCI.

[0233]

[0240] Embodiment 48: Any method of Embodiments 46 to 47, wherein the capability indicator identifies UE support for DCI having a DCI format.

[0234]

[0241] Embodiment 49: The method of Embodiment 48, further comprising transmitting a DCI having a DCI format, communicating according to a capability indicator, and communicating according to a TCI associated with one or more configured fields.

[0235]

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

[0236]

[0243] Embodiment 51: Any method of Embodiments 46 to 50, 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.

[0237]

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

[0238]

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

[0239]

[0246] Embodiment 54: 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 apparatus to perform a method of one or more embodiments of Embodiments 1 to 19.

[0240]

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

[0241]

[0248] Embodiment 56: An apparatus for wireless communication, comprising at least one means for carrying out a method of one or more embodiments from Embodiments 1 to 19.

[0242]

[0249] Embodiment 57: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to carry out one or more of the embodiments of Embodiments 1 to 19.

[0243]

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

[0244]

[0251] Embodiment 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 apparatus to perform a method of one or more embodiments of embodiments 20 to 37.

[0245]

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

[0246]

[0253] Embodiment 61: An apparatus for wireless communication, comprising at least one means for carrying out a method of one or more embodiments of embodiments 20 to 37.

[0247]

[0254] Embodiment 62: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to carry out a method of one or more embodiments of Embodiments 20 to 37.

[0248]

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

[0249]

[0256] Apparatus 64: Apparatus for wireless communication in a device, comprising a processor, memory coupled to the processor, and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method of one or more of the apparatuses of Apparatuses 38 to 45.

[0250]

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

[0251]

[0258] Apparatus 66: Apparatus for wireless communication, comprising at least one means for carrying out a method of one or more of the apparatuses 38 to 45.

[0252]

[0259] Embodiment 67: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to implement a method of one or more embodiments of Embodiments 38 to 45.

[0253]

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

[0254]

[0261] Apparatus 69: Apparatus for wireless communication in a device, comprising a processor, memory coupled to the processor, and instructions stored in the memory, wherein the instructions are executable by the processor to cause the apparatus to perform a method of one or more of the apparatuses of Apparatuses 46 to 53.

[0255]

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

[0256]

[0263] Embodiment 71: An apparatus for wireless communication, comprising at least one means for carrying out a method of one or more embodiments of Embodiments 46 to 53.

[0257]

[0264] Embodiment 72: A non-temporary computer-readable medium for storing code for wireless communication, wherein the code includes instructions that can be executed by a processor to implement a method of one or more embodiments of Embodiments 46 to 53.

[0258]

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

[0259]

[0266] The above disclosures are illustrative and explanatory, and are not exhaustive, nor do they limit the embodiments to the exact forms disclosed. Modifications and variations may be made in light of the above disclosures or derived from the practice of the embodiments.

[0260]

[0267] As used herein, the term “components” is broadly interpreted to mean hardware, firmware, or a combination of hardware and software. As used herein, processors are implemented as hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is broadly interpreted to mean “at least partially based on.” As used herein, “meeting a threshold” may, in examples, mean that a value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold. As used herein, the phrase “at least one of” the list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” includes a, b, c, ab, ac, bc, and abc.

[0261]

[0268] Furthermore, the articles “a” and “an” as used herein include one or more items and may be used interchangeably with “one or more.” Additionally, the article “the” as used herein includes one or more items that refer to the article “the” and may be used interchangeably with “one or more.” Furthermore, the terms “set” and “group” as used herein include one or more items (for example, 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. Furthermore, the term “or” as used herein is inclusive when used consecutively and may be used interchangeably with “and / or” unless otherwise specified (for example, when used in combination with “either” or “only one of”).

[0262]

[0269] The various exemplary logics, logic blocks, modules, circuits, and algorithmic processes described in relation to the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. Hardware-software compatibility is generally described in terms of functionality and is shown in the various exemplary components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0263]

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

[0264]

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

[0265]

[0272] When implemented in software, the functionality may be stored on or transmitted via computer-readable media as one or more instructions or codes. The processes of the methods or algorithms disclosed herein may be implemented in processor-executable software modules that reside on computer-readable media. Computer-readable media include both computer storage media and computer communication media, including any media that can enable the transfer of computer programs from one location to another. Storage media can be any available media that can be accessed by a computer. Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM®, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer. Any connection may also be appropriately referred to as computer-readable media. As used herein, the terms "disk" and "disc" include Compact Disc (CD), LaserDisc® (disc), Optical Disc (disc), Digital Multipurpose Disc (disc) (DVD), Floppy Disk (disk), and Blu-ray® Disc (disc), where a disk typically reproduces data magnetically and a disc reproduces data optically using a laser. The aforementioned combinations should also be included within the scope of computer-readable media. Furthermore, the operation of a method or algorithm may exist as one or any combination of codes and instructions on machine-readable and computer-readable media, or a set thereof, which may be incorporated into computer program products.

[0266]

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

[0267]

[0274] Furthermore, it will be readily understood by those skilled in the art that the terms “top” and “bottom” are sometimes used to simplify 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 implemented device.

[0268]

[0275] Furthermore, some features described herein in relation to separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in relation to a single embodiment may be implemented individually in multiple embodiments or in any preferred partial combination. Moreover, features are described above as working in several combinations, and may even be initially claimed as such, but one or more features from a claimed combination may be removed from that combination in some cases, and the claimed combination may be a partial combination or a variation of a partial combination.

[0269]

[0276] Similarly, while operations are illustrated in a specific order in the drawings, this should not be understood as requiring that such operations be performed in a specific order or sequence shown, or that all illustrated operations must be performed, in order to achieve the desired result. Furthermore, drawings may schematically illustrate another exemplary process in the form of a flowchart. However, other operations not illustrated may be incorporated into the schematically illustrated exemplary process. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated with each other in a single software product or packaged in multiple software products. Furthermore, other embodiments fall within the scope of the following claims. In some cases, the actions described in the claims may be performed in a different order and still achieve the desired result. The invention described in the original claims of this application is listed below. [C1] A method of wireless communication performed by a user equipment (UE), Receiving 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. A method comprising communicating according to a Transmit Configuration Indicator (TCI) associated with one or more configured fields. [C2] The method according to C1, wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes the indication of the TCI but does not include any other type of indication. [C3] The method according to C1, wherein the DCI format is DCI format 1_0 or uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of a different setting. [C4] The second indication is, Secondary cell (SCell) hiatus indication, Semi-persistent scheduling (SPS) release indication, SPS activation indication, or The method described in C3, which includes at least one of the Hybrid Automated Resend Request (HARQ) indications. [C5] The method according to C1, 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 set (CORESET) beams of the DCI. [C6] The method according to C1, wherein the DCI represents a plurality of TCIs, or a single TCI associated with a TCI pool from which the plurality of TCIs should be composed. [C7] The method according to C1, wherein the DCI includes a TCI field indicating an identifier for 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 common attributes. [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 required fields of the aforementioned DCI, A verification sequence configured for beam indication, or The method described in C1, based on at least one of the values ​​of the validation sequence associated with a non-TCI configuration. [C10] The configured field associated with the TCI is not present in one or more configured fields of the DCI, and the UE is Another DCI, Another indicator that is not DCI, Another configured field that exists in one or more configured fields of the DCI, or The method of C1, configured to determine the TCI based on at least one of the default configurations. [C11] A method of wireless communication carried out by equipment 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. A method comprising communicating according to a Transmit Configuration Indicator (TCI) associated with one or more configured fields. [C12] The method according to C11, wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes the indication of the TCI but does not include any other type of indication. [C13] The method according to C11, wherein the DCI format is DCI format 1_0 or uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of a different setting. [C14] The second indication is, Secondary cell (SCell) hiatus indication, Semi-persistent scheduling (SPS) release indication, SPS activation indication, or The method described in C13, comprising at least one of the Hybrid Automatic Resend Request (HARQ) indications. [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 set (CORESET) beams of the DCI. [C16] The method according to C11, wherein the DCI represents a plurality of TCIs, or a single TCI associated with a TCI pool from which the plurality of TCIs should be composed. [C17] The method according to C11, wherein the DCI includes a TCI field indicating an identifier for 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 common attributes. [C18] The method according to C11, wherein the TCI includes a downlink TCI and an uplink TCI. [C19] The TCI is The Radio Network Temporary Identifier (RNTI) associated with the DCI, The required fields of the aforementioned DCI, A verification sequence configured for beam indication, or The method described in C11, based on at least one of the values ​​of the validation sequence associated with a non-TCI configuration. [C20] A method of wireless communication performed by a user equipment (UE), Transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports 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. A method comprising communicating according to the aforementioned capability indicator. [C21] The method according to C20, wherein one or more configured fields are associated with a Transmit Configuration Indicator (TCI). [C22] The method of 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, The method of C22, comprising communicating according to a Transmit Configuration Indicator (TCI) associated with one or more configured fields. [C24] The method of C20, wherein the capability indicator is included in an optional field of the uplink control information (UCI) message. [C25] The method according to C20, wherein the capability indicator is a single capability indicator indicating support for the DCI format without scheduling data and for another DCI format that includes scheduling data. [C26] The method according to C20, wherein the capability indicator is a first capability indicator indicating support for the DCI format which does not include scheduling data. [C27] Further comprising transmitting a second capability indicator indicating support for another DCI format including scheduling data, and communicating in accordance with the said capability indicator, The method according to C26, comprising communicating according to the first capability indicator and the second capability indicator. [C28] A method of wireless communication carried out by equipment of a base station (BS), Receiving a capability indicator, wherein the capability indicator is associated with whether the 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. A method comprising communicating according to the aforementioned capability indicator. [C29] The method according to C28, wherein one or more configured fields are associated with a Transmit Configuration Indicator (TCI). [C30] The method according to C28, wherein the capability indicator identifies UE support for the DCI having the DCI format. [C31] Further comprising transmitting the DCI having the DCI format and communicating according to the capability indicator, The method of C30, comprising communicating according to a Transmit Configuration Indicator (TCI) associated with one or more configured fields. [C32] The method according to C28, wherein the capability indicator is included in an optional field of the uplink control information (UCI) message. [C33] The method according to C28, wherein the capability indicator is a single capability indicator indicating support for the DCI format without scheduling data and for another DCI format that includes scheduling data. [C34] The method according to C28, wherein the capability indicator is a first capability indicator indicating support for the DCI format which does not include scheduling data. [C35] Further comprising receiving a second capability indicator indicating support for another DCI format including scheduling data, and communicating in accordance with the capability indicator, The method according to C34, comprising communicating according to the first capability indicator and the second capability indicator. [C36] Device for wireless communication in user equipment (UE), Memory and The system comprises one or more processors coupled to the memory, and the processors are Receiving 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. A device configured to communicate in accordance with a Transmit Configuration Indicator (TCI) associated with one or more of the configured fields. [C37] The apparatus according to C36, wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes the indication of the TCI but does not include any other type of indication. [C38] The apparatus according to C36, wherein the DCI format is DCI format 1_0 or uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of a different setting. [C39] Equipment for wireless communication at a base station (BS), Memory and The system comprises one or more processors coupled to the memory, and the processors are 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. A device configured to communicate in accordance with a Transmit Configuration Indicator (TCI) associated with one or more of the configured fields. [C40] The apparatus according to C39, wherein the DCI format is DCI format 1_1 or DCI format 1_2, and the DCI includes the indication of the TCI but does not include any other type of indication. [C41] The apparatus according to C39, wherein the DCI format is DCI format 1_0 or uplink DCI format, and the DCI includes a first indication of the TCI and a second indication of a different setting. [C42] A device for wireless communication in user equipment (UE), Memory and The system comprises one or more processors coupled to the memory, and the processors are Transmitting a capability indicator, wherein the capability indicator is associated with whether the UE supports 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. A device configured to communicate according to the aforementioned capability indicator. [C43] The apparatus according to C42, wherein one or more configured fields are associated with a Transmit 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 The one or more processors are further configured to receive the DCI having the DCI format, and to communicate according to the capability indicators, The apparatus according to C44, configured to communicate in accordance with a Transmit Configuration Indicator (TCI) associated with one or more of the configured fields. [C46] The apparatus according to C42, wherein the capability indicator is included in an optional field of the uplink control information (UCI) message. [C47] Equipment for wireless communication at a base station (BS), Memory and The system comprises one or more processors coupled to the memory, and the processors are Receiving a capability indicator, wherein the capability indicator is associated with whether the 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. A device configured to communicate according to the aforementioned capability indicator. [C48] The apparatus according to C47, wherein one or more configured fields are associated with a Transmit Configuration Indicator (TCI). [C49] The apparatus according to C47, wherein the capability indicator identifies UE support for the DCI having the DCI format. [C50] The one or more processors The DCI having the DCI format is further configured to transmit the one or more processors to communicate according to the capability indicators. The apparatus according to C49, configured to communicate in accordance with a Transmit Configuration Indicator (TCI) associated with one or more of the configured fields.

Claims

1. A method of wireless communication performed by a user equipment (UE), 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. To communicate according to the aforementioned capability indicator A method that includes [a certain feature].

2. The method according to claim 1, wherein one or more configured fields are associated with a Transmit Configuration Indicator (TCI).

3. The method according to claim 1, wherein the capability indicator identifies UE support for the DCI having the DCI format.

4. Receiving the DCI having the DCI format It further comprises the ability indicator, and communicates according to the ability indicator, Communicating according to the Transmit Configuration Indicator (TCI) associated with one or more of the configured fields. The method according to claim 3, comprising:

5. The method according to claim 1, wherein the capability indicator is included in an optional field of the uplink control information (UCI) message.

6. The method according to claim 1, wherein the capability indicator is a single capability indicator indicating support for the DCI format without scheduling data and for another DCI format that includes scheduling data.

7. The method according to claim 1, wherein the capability indicator is a first capability indicator indicating support for the DCI format which does not include scheduling data.

8. Send a second capability indicator that shows support for another DCI format, including scheduling data. It further comprises the ability indicator, and communicates according to the ability indicator, The method according to claim 7, comprising communicating according to the first capability indicator and the second capability indicator.

9. A method of wireless communication carried out by equipment of a base station (BS), Receiving a capability indicator, wherein the capability indicator is associated with whether a user device (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. To communicate according to the aforementioned capability indicator A method that includes [a certain feature].

10. The method according to claim 9, wherein one or more configured fields are associated with a Transmit Configuration Indicator (TCI).

11. The method according to claim 9, wherein the capability indicator identifies UE support for the DCI having the DCI format.

12. To transmit the DCI having the DCI format. It further comprises the ability indicator, and communicates according to the ability indicator, Communicating according to the Transmit Configuration Indicator (TCI) associated with one or more of the configured fields. The method according to claim 11, comprising:

13. The method according to claim 9, wherein the capability indicator is included in an optional field of the uplink control information (UCI) message.

14. The method according to claim 9, wherein the capability indicator is a single capability indicator indicating support for the DCI format without scheduling data and for another DCI format that includes scheduling data.

15. The method according to claim 9, wherein the capability indicator is a first capability indicator indicating support for the DCI format which does not include scheduling data.

16. Receiving a second capability indicator that shows support for another DCI format, including scheduling data. It further comprises the ability indicator, and communicates according to the ability indicator, The method according to claim 15, further comprising communicating according to the first capability indicator and the second capability indicator.

Images