Semi-known transmission configuration indicator state

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can identify a transmit configuration indicator (TCI) state. The UE can determine that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The UE can apply a TCI state switching delay timeline associated with a semi-known TCI state. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for using a semi-known transmit configuration indicator state. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a base station to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include identifying a transmit configuration indicator (TCI) state. The method may include determining that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The method may include applying a TCI state switching delay timeline associated with the semi-known TCI state.

[0006] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include identifying a TCI state. The method may include determining that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied. The method may include applying a TCI state switch delay timeline associated with a known TCI state.

[0007] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a preference indication indicating a preference associated with determining whether a TCI state is semi-known. The method may include sending a configuration including a capability for determining whether a TCI state is a semi-known TCI state.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to identify a TCI state. The one or more processors may be configured to determine that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The one or more processors may be configured to apply a TCI state switching delay timeline associated with a semi-known TCI state.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to identify a TCI state. The one or more processors may be configured to determine that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied. The one or more processors may be configured to apply a TCI state switching delay timeline associated with a known TCI state.

[0010] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a preference indication indicating a preference associated with determining whether a TCI state is semi-known. The one or more processors may be configured to send a configuration including a capability for determining whether a TCI state is a semi-known TCI state.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, can cause the UE to identify a TCI state. The instruction set, when executed by one or more processors of the UE, can cause the UE to determine that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The instruction set, when executed by one or more processors of the UE, can cause the UE to apply a TCI state switching delay timeline associated with a semi-known TCI state.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, can cause the UE to identify a TCI state. The instruction set, when executed by one or more processors of the UE, can cause the UE to determine that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied. The instruction set, when executed by one or more processors of the UE, can cause the UE to apply a TCI state switching delay timeline associated with a known TCI state.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, can cause the network entity to receive a preference indication indicating a preference associated with determining whether a TCI state is semi-known. The instruction set, when executed by one or more processors of the network entity, can cause the network entity to send a configuration including a capability for determining whether a TCI state is a semi-known TCI state.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for identifying a TCI state. The apparatus may include components for determining that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The apparatus may include components for applying a TCI state switching delay timeline associated with the semi-known TCI state.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for identifying a TCI state. The apparatus may include components for determining that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied. The apparatus may include components for applying a TCI state switch delay timeline associated with a known TCI state.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a preference indication indicating a preference associated with determining whether a TCI state is semi-known. The apparatus may include means for sending a configuration including a capability for determining whether a TCI state is a semi-known TCI state.

[0017] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0018] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0019] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0021] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0022] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0023] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0024] Figure 4 is a diagram illustrating an example of using a beam for communication between a network entity and a UE according to the present disclosure.

[0025] Figure 5 is a diagram illustrating an example of beam prediction according to the present disclosure.

[0026] Figure 6 is a diagram illustrating an example of a known transmission configuration indicator (TCI) state according to the present disclosure.

[0027] Figure 7 is a diagram illustrating an example of a TCI state switching timeline according to the present disclosure.

[0028] Figure 8 is a diagram illustrating an example of predicting channel characteristics according to the present disclosure.

[0029] Fig. 9 is a diagram illustrating an example of using a semi-known TCI state according to the present disclosure.

[0030] Fig.10 is a diagram illustrating an example of a TCI state switching timeline for a semi-known TCI state according to the present disclosure.

[0031] Fig.11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0032] Fig.12 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0033] Fig.13is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0034] Figure 14 to Figure 15 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0035] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

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

[0037] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0038] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS 110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0039] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0040] In some examples, the cell may not necessarily be fixed, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0041] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0042] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in FIG. 1 , BS 110 d (eg, a relay base station) can communicate with BS 110 a (eg, a macro base station) and UE 120 d to facilitate communication between BS 110 a and UE 120 d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0043] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0044] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for these network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

[0045] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be fixed or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0046] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network entity, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0048] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0049] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0050] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0051] Considering the above examples, unless otherwise expressly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can broadly refer to frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise expressly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0052] In some aspects, the UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may identify a transmit configuration indicator (TCI) state and determine that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The communications manager 140 may apply a TCI state switching delay timeline associated with the semi-known TCI state.

[0053] In some aspects, the communication manager 140 may identify a TCI state and determine that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied. The communication manager 140 may apply a TCI state switching delay timeline associated with a known TCI state. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0054] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a preference indication indicating a preference associated with determining whether a TCI state is semi-known. The communication manager 150 may send a configuration including an ability to determine whether a TCI state is a semi-known TCI state. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0055] As indicated above, Figure 1 Other examples can be found in the Figure 1 Different than described.

[0056] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0057] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0058] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and a set of received signals (e.g., R received signals) may be provided to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information 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 determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0060] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0061] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 15 ) or any aspect of any of the methods described herein.

[0062] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 15 ) or any aspect of any of the methods described herein.

[0063] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the base station 110 may perform one or more techniques associated with using a semi-known TCI state. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 1300 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of a network entity and / or UE 120, may cause the one or more processors, UE 120, and / or network entity to perform or direct, for example, Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The process 1300 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0064] In some aspects, the UE 120 includes means for identifying a TCI state; means for determining that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition; and / or means for applying a TCI state switching delay timeline associated with a semi-known TCI state. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0065] In some aspects, the UE 120 includes means for identifying a TCI state; means for determining that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied; and / or means for applying a TCI state switching delay timeline associated with a known TCI state.

[0066] In some aspects, a network entity (e.g., base station 110) includes means for receiving a preference indication indicating a preference associated with determining whether a TCI state is semi-known; and / or means for sending a configuration including an ability to determine whether a TCI state is a semi-known TCI state. In some aspects, means for a network entity to perform operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0067] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0068] As indicated above, Figure 2 Other examples can be found in the Figure 2 Different than described.

[0069] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0070] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) performing base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.

[0071] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0072] Base station type operations or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0073] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served by multiple RUs 340 simultaneously. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU") and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0074] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units via a wireless transmission medium.

[0075] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0076] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0077] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0078] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0079] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0080] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0081] As indicated above, Figure 3 Other examples can be found in the Figure 3 Different than described.

[0082] Figure 4 4 is a diagram illustrating an example 400 of using beams for communication between a network entity and a UE according to the present disclosure. Figure 4 As shown, network entities (eg, base station 110) and UE 120 may communicate with each other.

[0083] 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 communications, 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, etc. Base station 110 may transmit downlink communications via one or more BS transmit beams 405.

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

[0085] A downlink beam (such as a BS transmit beam 405 or a UE receive beam 410) may be associated with a TCI state. The TCI state may indicate a directionality or characteristic of the downlink beam, such as one or more quasi-co-location (QCL) attributes of the downlink beam. The QCL attributes may include, for example, Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc. In some examples, each BS transmit beam 405 may be associated with a synchronization signal block (SSB), and the UE 120 may indicate a preferred BS transmit beam 405 by transmitting an uplink transmission in the resources of the SSB associated with the preferred BS transmit beam 405. A specific SSB may have an associated TCI state (e.g., for an antenna port or for beamforming). In some examples, the base station 110 may indicate a downlink BS transmit beam 405 based at least in part on an antenna port QCL attribute that may be indicated by a TCI state. For different QCL types (e.g., QCL types for different combinations of Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters, etc.), the TCI state can be associated with a set of downlink reference signals (e.g., SSB, and aperiodic, periodic, or semi-persistent channel state information reference signals (CSI-RS)). In the case where the QCL type indicates spatial reception parameters, the QCL type can correspond to simulated receive beamforming parameters of the UE receive beam 410 at the UE 120. Therefore, the UE 120 can select the corresponding UE receive beam 410 from the BPL set based at least in part on the base station 110 indicating the BS to transmit the beam 405 via the TCI indication.

[0086] The base station 110 may maintain an activated TCI state set for downlink shared channel transmission and an activated TCI state set for downlink control channel transmission. The activated TCI state set for downlink shared channel transmission may correspond to a beam used by the base station 110 for downlink transmission on a physical downlink shared channel (PDSCH). The activated TCI state set for downlink control channel communication may correspond to a beam that the base station 110 may use for downlink transmission on a physical downlink control channel (PDCCH) or in a control resource set (CORESET). The UE 120 may also maintain an activated TCI state set for receiving downlink shared channel transmissions and CORESET transmissions. In the case where the TCI state is activated for the UE 120, the UE 120 may have one or more antenna configurations based at least in part on the TCI state, and the UE 120 may not need to reconfigure the antenna or antenna weighting configuration. In some examples, a set of activated TCI states (e.g., activated PDSCH TCI states and activated CORESET TCI states) for UE 120 may be configured by a configuration message, such as an RRC message.

[0087] Similarly, for uplink communications, UE 120 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, etc. UE 120 may transmit uplink communications via one or more UE transmit beams 415.

[0088] Base station 110 may receive uplink transmissions via one or more BS receive beams 420. Base station 110 may identify specific UE transmit beams 415 (shown as UE transmit beam 415-A) and specific BS receive beams 420 (shown as BS receive beam 420-A) that provide relatively good performance (e.g., having the best channel quality of different measured combinations of UE transmit beams 415 and BS receive beams 420). In some examples, base station 110 may send an indication of which UE transmit beam 415 base station 110 identifies as a preferred UE transmit beam that base station 110 may select to transmit from UE 120. Thus, UE 120 and base station 110 may obtain and maintain a BPL for uplink communications (e.g., a combination of UE transmit beam 415-A and BS receive beam 420-A), which may be further refined and maintained according to one or more established beam refinement procedures. An uplink beam, such as a UE transmit beam 415 or a BS receive beam 420, may be associated with a spatial relationship. The spatial relationship may indicate a directionality or characteristic (similar to one or more QCL properties) of the uplink beam, as described above.

[0089] As indicated above, Figure 4 Other examples can be found in the Figure 4 Different than described.

[0090] Figure 5 is a diagram illustrating an example 500 of beam prediction according to the present disclosure.

[0091] Current beam management procedures require more power or overhead to achieve better performance, but the limitation on power or overhead limits the beam accuracy. Predictive beam management in the time, frequency, and spatial domains can reduce power and overhead while increasing accuracy, latency, and throughput. However, the prediction of future transmit beams may depend on the speed or trajectory of the UE, and the prediction of future receive beams may not successfully resolve interference. It is difficult to predict future beams via conventional statistical methods.

[0092] Predictive beam management may involve AI / ML to improve beam selection accuracy and address overhead, complexity, and latency issues. This may include using ML models to predict channel characteristics for beam prediction in the time and spatial domains. Predictive beam management may also use ML models to predict unmeasured beam quality (for lower power / overhead or better accuracy) and / or predict future beam blocking or failure (for less latency and higher throughput). Example 500 illustrates the use of layer 1 (L1) RSRP measurements as input to an ML model for predicting L1-RSRP, candidate beams, beam failures, or beam blocking. AI / ML helps with predictive beam management because beam prediction is a highly nonlinear problem.

[0093] Beam prediction can be a trade-off between performance and UE power. The UE has more observations (via measurements) than the network entity (via UE feedback) to predict future downlink transmit beam quality. The UE can also outperform the prediction at the network entity. However, this consumes more UE power. Training of the ML model can facilitate data collection and computation at the UE. Data can be collected at the air interface and higher layers. Model training may require UE computation, UE storage, and UE buffering.

[0094] As indicated above, Figure 5 Other examples can be found in the Figure 5 Different than described.

[0095] Figure 6 is a diagram illustrating an example 600 of known TCI states according to the present disclosure.

[0096] TCI state switching may involve known TCI states and unknown TCI states. The TCI state switching timeline may specify a delay between receiving a reference signal (RS) resource (e.g., CSI-RS, SSB) for an L1-RSRP measurement report for a target TCI state (activated TCI state) and completing an active TCI state switch. The RS resource is an RS in an activated TCI state or in a QCL with an activated TCI state. Example 600 shows that CSI-RS #5 is an RS and the activated TCI state to be applied to the TCI state switch is TCI state #3.

[0097] The TCI state switching timeline for the TCI state switching period may depend on whether the activated TCI state is known or unknown. The TCI state is known if multiple conditions are met. This may include: (Condition #1) whether a TCI state switching command is received within 1280 milliseconds (ms) at the last transmission of RS resources for beam reporting or measurement; (Condition #2) whether the UE has sent at least 1 L1-RSRP report for the target TCI state before the TCI state switching command; (Condition #3) whether the TCI state remains detectable during the TCI state switching period (e.g., from the timeslot carrying the TCI state activation MAC CE to the completion of the TCI switch); and (Condition #4) whether the SSB associated with the TCI state remains detectable during the TCI switching period. The RS may be detectable by the UE if the signal-to-noise ratio (SNR) of the RS is greater than or equal to 3 decibels (dB). This does not necessarily mean that such an RS must be sent. This can be verified by the UE via other RSs (e.g., DMRS). If these conditions are not met, the TCI state is unknown.

[0098] As indicated above, Figure 6 Other examples can be found in the Figure 6 Different than described.

[0099] Figure 7 is a diagram illustrating an example of a TCI state switching timeline according to the present disclosure.

[0100] In the case where the target TCI state (activate TCI state) is known (example 700), when a PDSCH communication carrying a MAC CE activation command is received in time slot n, the UE may be able to activate the MAC CE in time slot n+T HARQ +(3ms+TO k *(T first-SSB +T SSB-proc ))) / NR time slot length occurs at the first time slot after the TCI state switch occurs at the target TCI state of the serving cell. The UE may be able to receive PDCCH communications with the old TCI state until time slot n+T HARQ +3ms. T first-SSB It can be the time from when the MAC CE activation command is decoded by the UE to when the first SSB is sent. The SSB can be QCL type A or QCL type C with the target TCI state. SSB-proc The SSB processing time may be 2 ms. In the case where the target TCI state is not in the active TCI state list for PDSCH, TO k Can be 1, otherwise can be 0.

[0101] In the case where the target TCI state is unknown (examples 702 and 704), when a PDSCH communication carrying a MACCE activation command is received in time slot n, the UE may be able to HARQ +(3ms+T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ))) / NR time slot length occurs at the first time slot after the TCI state switch occurs at the target TCI state of the serving cell. The UE may be able to receive PDCCH communications with the old TCI state until time slot n+T HARQ +(3ms+T L1-RSRP +TO uk *T first-SSB ) / NR time slot length. T L1-RSRP It can be the time of L1-RSRP measurement for receive beam refinement in FR2, which is defined as the periodicity of SSB / CSI-RS relative to TCI state. T for SSB can be specified. L1-RSPR_Measurement_Period_SSB and T for CSI-RS L1-RSRP_Measurement_Period_CSI-RS When TCI state switching involves QCL type D, TO uk For CSI-RS based L1-RSRP measurement, it can be 1, and for SSB based L1-RSRP measurement, it can be 0. When TCI state switching involves other QCL types, TO uk Can be 1.

[0102] For FR2 T L1-RSRP , for SSB as specified in different configurations, T L1-RSRP =T L1-RSPR_Measurement_Period_SSB , where the factor M = 1, the beam scanning factor N = 8 and T Report = 0. For non-discontinuous reception (non-DRX) configuration, T L1-RSPR_Measurement_Period_SSB It can be T Report The maximum value (max) and (M×P×N)×T SSB For non-DRX configurations, it is assumed that the UE needs 8 SSB cycles to refine its transmit beam. For configurations with a DRX cycle ≤ 320 ms, T L1-RSPR_Measurement_Period_SSB It can be T Report The maximum value of ((1.5×M×P×N)×max(T DRX ,T SSB )). For configurations with a DRX cycle > 320ms, T L1-RSPR_Measurement_Period_SSB It can be ((1.5×M×P×N)×T DRX ) is the upper limit value. T SSB=ssb-periodicityServingCell may be the periodicity of the SSB-Index configured for L1-RSRP measurement. DRX It can be the DRX cycle length. Report Can be a configured periodicity for reporting.

[0103] For FR2 T L1-RSRP , for CSI-RS as specified in different configurations, T L1-RSRP =T L1-RSPR_Measurement_Period_CSI-RS , where it is assumed that M = 1 and T Report = 0. Higher layer parameter repetition may be set to on. For aperiodic CSI-RS, the number of resources in a resource set may be at least equal to MaxNumberRxBeam, which may be RRC configured for each band and may vary from 2 to 8. N res_per_set It can be the number of CSI-RS resources in the considered CSI-RS resource set. For non-DRX configuration, T L1-RSPR_Measurement_Period_CSI-RS It can be T Report The maximum value (max) and (M×P×N)×T CSI-RS For maxNumberRxBeam=N res_per_set , it can be assumed that the UE requires a periodic or semi-periodic (P / SP) CSI-RS cycle to refine its receive beam. For P / SP-CSI-RS with repetition set to on, N can be ceil(maxNumberRxBeam / N res_per_set ). For the assumption that maxNumberRxBeam≤N res_per_set For AP CSI-RS, N can be 1. For P / SP CSI-RS, M can be 1. For configurations with a DRX cycle ≤ 320 ms, T L1-RSPR_Measurement_Period_CSI-RS It can be T Report The maximum value of ((1.5×M×P×N)×max(T DRX ,T CSI-RS )). For configurations with a DRX cycle > 320ms, T L1-RSPR_Measurement_Period_CSI-RS It can be ((M×P×N)×T DRX ) is the upper limit value. T CSI-RS It may be the periodicity of the CSI-RS configured for L1-RSRP measurement. Assuming that the CSI-RS resources configured for L1-RSRP measurement are transmitted at density 3, these requirements may be applicable.

[0104] As indicated above, Figure 7 Other examples can be found in the Figure 7 Different than described.

[0105] Figure 8 is a diagram illustrating an example 800 of predicting channel characteristics according to the present disclosure.

[0106] As shown in example 800, the UE may have predicted channel characteristics regarding a certain SSB or CSI-RS and the appropriate receive spatial filter associated with such SSB or CSI-RS (relative to QCL type A / C / D) without actually measuring the SSB or CSI-RS. For example, for time domain beam prediction, the UE can predict future L1-RSRP regarding the SSB and optionally report the predicted L1-RSRP without actually measuring them (compared to known TCI state condition #2). The UE can predict whether the strongest SSB will switch to another SSB in the future duration instead of the most recent L1 measurement report. In the event of no change, the UE can simply do nothing. In the event that a change is predicted, the UE can request an AP / SP L1 measurement report in an on-demand manner (compared to known TCI state condition #2). For spatial domain prediction, the UE can predict the L1-RSRP associated with a CSI-RS (e.g., with a periodicity = 2000 ms) based on the SSB (e.g., with a periodicity = 20ms) without frequently measuring the CSI-RS (compared to known TCI state condition #1). Such cases are considered unknown TCI states, but some delays are not necessary for such predictive beam management. For example, for SSB / CSI-RS, the UE can simply apply the predicted receive spatial filter without measuring SSB / CSI-RS. For CSI-RS, the UE may only need to measure SSB again to verify QCL type A / C, but does not need to actually measure CSI-RS.

[0107] In other words, although the channel characteristics can be predicted, the TCI state can still be considered unknown under the current known TCI state condition. This can introduce a longer delay than necessary.

[0108] As indicated above, Figure 8 Other examples can be found in the Figure 8 Different than described.

[0109] Fig. 9 is a diagram illustrating an example 900 of using a semi-known TCI state according to the present disclosure. Fig. 9 As shown, a network entity 910 (eg, base station 110) and a UE 920 (eg, UE 120) may communicate with each other.

[0110] According to various aspects described herein, a UE may use a semi-known TCI state condition predicted with respect to CSI-RS / SSB channel characteristics. When the channel characteristics do not satisfy a known TCI state condition but satisfy a predicted condition, the TCI state may be semi-known. Because all known TCI state conditions must be satisfied for a TCI state that is considered a known TCI state, not satisfying one of the TCI state conditions means that the TCI state is unknown. In the case where the channel characteristics are predicted within the prediction duration, the predicted condition may be satisfied. In the case where the activated TCI state is semi-known, the UE may use a TCI state switching timeline specific to the semi-known condition. In this way, the predicted channel characteristics may be used to reduce latency rather than causing failures to a longer TCI state switching timeline for an unknown TCI state. For example, the TCI state switching timeline for a semi-known TCI state may remove L1. Alternatively, in the case where a known TCI state condition is not satisfied but a predicted condition is satisfied, the UE may fall back to a known TCI state condition.

[0111] Example 900 illustrates the use of a semi-known TCI state (e.g., TCI state #3). As shown in reference numeral 925, the network entity 910 may send a reference signal (e.g., CSI-RS, SSB). As shown in reference numeral 930, the network entity 910 may send a TCI state activation command (e.g., MAC CE). As shown in reference numeral 935, the UE 920 may identify the TCI state. The UE 920 may identify the TCI state based at least in part on a TCI state activation command MAC CE that activates or updates the TCI state. The UE 920 may identify the TCI state from an earlier MAC CE. The UE 920 may identify the TCI state from a TCI state in an activated TCI state list. The UE 920 may identify the TCI state from a TCI state outside the activated TCI state list. As shown in reference numeral 940, the network entity 910 may send a TCI state switch command (e.g., downlink control information (DCI)).

[0112] As indicated by reference numeral 945, UE 920 may determine that the TCI state is semi-known. That is, UE 920 may determine that the known condition is not satisfied for TCI state #3. For example, a TCI state switching command may be received more than 1280 ms after receiving a reference signal (e.g., CSI-RS #5), and UE 920 has not yet sent a (conventional) L1-RSRP report for the target TCI state before the TCI state switching command. However, the prediction condition is satisfied. UE 920 has predicted the channel characteristics associated with the reference signal in the TCI state (or with the RS QCL) for the prediction duration.

[0113] The prediction duration may be configured as Xms before a TCI state switch command associated with the TCI state is received. The value of the prediction duration may be configured for a specific prediction scenario, and different values ​​of the prediction duration may be used for different prediction scenarios. For example, one scenario (e.g., beam change prediction / reporting) may be more suitable for a semi-static environment, such that the prediction duration for that scenario is longer than the prediction duration for other scenarios. Different values ​​may be specified in the standard, configured by the network entity 910, or indicated by the network entity 910 via an RRC message, MAC CE, or DCI. The UE 920 may also send a preferred value for the prediction duration.

[0114] In some aspects, the channel characteristics may include a predicted L1-RSRP reported without actually receiving RS or measuring RS. For example, the UE 920 may measure only the SSB (e.g., periodicity = 20ms) to identify or report the L1-RSRP of the CSI-RS (e.g., periodicity of 2000ms). The channel characteristics may be based at least in part on sending a preference for using RS resources as a type D QCL source without sending an L1-RSRP report. For example, the UE 920 may report only the SSB resource indicator (SSBRI) as a preferred type D QCL source without reporting its L1-RSRP. The channel characteristics may be based at least in part on a preference for using a reference signal as a type D QCL source (without sending the preference). For example, the UE 920 may send an L1-RSRP report for SSB#3 including the strongest L1-RSRP at time slot n, and if the UE 920 determines that the strongest SSB will change to another SSB, the UE 920 may only request an actual L1-RSRP report. The UE 920 may indicate a preference to use SSB #3 as a Type D QCL source without actually reporting its L1-RSRP (which is agreed upon between the UE 920 and the network entity 910).

[0115] As shown by reference numeral 950, the UE 920 may apply a TCI state switching timeline for a semi-known TCI state. The TCI state switching timeline may affect the delay or time between the time slot in which the TCI state activation command (MAC-CE) is received and the first TCI state switching command (DCI) associated with the TCI state. Priority rules may exist between semi-known and unknown. In the case where a TCI state may be considered semi-known at a certain time, the TCI state may not be considered unknown until the semi-known condition is no longer met.

[0116] The UE 920 and the network entity may apply TCI state switching according to the TCI state switching timeline for the semi-known TCI state. As shown by reference numeral 955, the network entity 910 may send a communication (e.g., on the PDSCH) using the activated TCI state. The UE 920 may receive the communication using the activated TCI state. By using the TVCI state switching timeline for the semi-known state, latency may be reduced.

[0117] In some aspects, the UE 920 may indicate (applicability indication) whether the semi-known TCI state is applicable to the UE 920. For example, in the case where the UE 920 identifies that the reference signal in the TCI state is applicable to the semi-known condition, the UE 920 may assume that the TCI state is applicable to the semi-known state. That is, the UE 920 may determine that the TCI state can be a semi-known TCI state without signaling from the network entity 910.

[0118] In some aspects, the UE 920 may determine that the TCI state can be a semi-known TCI state based at least in part on signaling from the network entity 910. The network entity 910 may control the use of the semi-known TCI state. The network entity 910 may indicate to the UE 920 that the TCI state is applicable to the semi-known state. For example, the network entity 910 may configure whether the semi-known state can be assumed or used by the UE 920 via an RRC configuration for the TCI state or the TCI state activation command (other RRC configurations for the TCI state state may be overwritten). The network entity 910 may also use a MAC CE to configure the UE 920 to specifically activate a TCI state applicable to the semi-known state. The network entity 910 may indicate the TCI state activated by such a MAC CE in a DCI (with a corresponding dedicated radio network temporary identifier (RNTI) or DCI format). For example, the DCI may further indicate the indicated TCI state identifier (ID) associated with the type of the TCI state activation command.

[0119] In some aspects, the UE 920 may report whether the TCI state is applicable to a semi-known state. The UE 920 may report a preference (preference indication) that the TCI state configured by the RRC may be assumed to be a semi-known state. The UE 920 may report, together with an acknowledgment (ACK) about the TCI state activation MAC CE, a UE report for one or more TCI states in the TCI state activated by the MAC CE and whether a semi-known state may be assumed. This may be further based on overwriting the MAC CE indication by such a UE report. The UE 920 may report its preference regarding the value of X (e.g., different values ​​of X for different scenarios).

[0120] As indicated above, Fig. 9 Other examples can be found in the Fig. 9 Different than described.

[0121] Fig.10 is a diagram illustrating an example of a TCI state switching timeline for a semi-known TCI state according to the present disclosure.

[0122] The TCI state switching timeline for a semi-known TCI state may be different from the TCI state switching timeline for an unknown TCI state. Example 1000 illustrates a first option for a timeline applied to both SSB and CSI-RS. No SSB or CSI-RS measurements need to be performed after the time slot in which the TCI state activation command (MAC CE) is received and before the time slot in which the TCI state switching command (DCI) identifying the semi-known TCI state is received. The UE 920 may have previously identified the appropriate QCL type A / C for the TCI state. In the case where the target TCI state included in the active TCI state list for PDSCH communication is semi-known, the UE 920 may be able to select a type D QCL in time slot n+T HARQ +(3ms+TO sk *(T first-SSB +T SSB-proc ))) / NR time slot length occurs at the first time slot after the TCI state switch of the target TCI state of the serving cell. The UE 920 may be able to receive PDCCH communications with the old TCI state until time slot n+T HARQ +3ms / NR slot length. By using semi-known states, the number of SSB cycles for beam refinement (beam scanning) can be reduced from 8 SSB cycles for unknown TCI states to possibly 2 or 3 SSB cycles for semi-known TCI states. This saves overhead and reduces latency.

[0123] Example 1002 applies only to CSI-RS. After receiving a TCI state activation command (MAC CE) in a time slot and before receiving a TCI state switch command (DCI) identifying a semi-known TCI state, the UE 920 does not need to perform measurements of CSI-RS, but still needs to perform measurements of SSB to identify the QCL type A / C for the target TCI state. In the case where the target TCI state included in the active TCI state list for PDSCH communication is semi-known, when the TCI state switch involves a type D QCL, the UE 920 may be able to perform measurements of the CSI-RS in time slot n+T HARQ +(3ms+(T first-SSB +T SSB-proc))) / NR time slot length occurs at the first time slot after the TCI state switch of the target TCI state of the serving cell. The UE 920 may be able to receive PDCCH communications with the old TCI state until time slot n+T HARQ +(3ms+T first-SSB ) / NR time slot length. In case the TCI state is found in the TCI state list, the TO for the semi-known state sk Can be 0. The timeline may not include T L1-RSRP In the event that the TCI state is not in the list, the UE 920 may identify the QCL type A / C.

[0124] In some aspects, the TCI state switching timeline for the semi-known state may include a dedicated time value T L1_RSRP_SemiKnown UE 920 may reuse the TCI state switching timeline for the unknown TCI state, but use the TCI state switching timeline for the semi-known TCI state. L1_RSRP_SemiKnown Replace any T L1-RSRP value. For SSB, the UE 920 receive beam scanning factor N can be reduced based at least in part on a standard definition (e.g., N can be reduced to 2 or 3 compared to 8 for an unknown TCI state), a network entity configuration (e.g., RRC preconfigures an N value for a semi-known TCI state), or a network entity indication (e.g., the network entity 910 indicates an N value for an unknown TCI state via a TCI state activation command (MAC-CE)). The UE 920 may report the N value for an unknown TCI state as its UE capability. For SSB, the UE 920 may apply different receive beams on the PSS, SSS, first DMRS, and / or second DMRS relative to the same SSB for fast receive beam refinement.

[0125] For CSI-RS, the UE 920 receive beam scanning factor N can be reduced to ceil(maxNumberRxBeam / N res_per_set / N SemiKnown ), where N SemiKnown The value may be based at least in part on a standard definition (e.g., N SemiKnown is defined as 2, N res_per_set Defined as 2), network entity configuration (e.g., RRC configuration for N for semi-known TCI state SemiKnown value) and / or a network entity indication (for example, the network entity 910 indicates the N value for the unknown TCI state through a TCI state activation command (MAC-CE) SemiKnown UE 920 may report N for unknown TCI state. SemiKnownvalue as its UE capability. Different signaling can be used for different scenarios. By using semi-known states, the number of CSI-RS cycles for beam refinement (beam scanning) can be increased from 4 CSI-RS cycles for unknown TCI states (within ceil(maxNumberRxBeam / N res_per_set =4) to possible 2 CSI-RS cycles for semi-known TCI states (with ceil(maxNumberRxBeam / N res_per_set / N SemiKnown )=2). This saves overhead and reduces latency.

[0126] As indicated above, Fig.10 Some examples are provided. Other examples can be found in Fig.10 Different than described.

[0127] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a UE according to the present disclosure. Example process 1100 is an example in which a UE (eg, UE 120, UE 920) performs operations associated with using a semi-known TCI state.

[0128] like Fig.11 As shown, in some aspects, process 1100 may include identifying a TCI state (block 1110). For example, a UE (e.g., using Fig.14 The communication manager 1408 and / or identification component 1410 depicted in FIG. 1404 may identify the TCI status as described above.

[0129] like Fig.11 As further shown, in some aspects, process 1100 may include determining that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition (block 1120). Fig.14 The communication manager 1408 and / or determination component 1412 depicted in the figure can determine that the TCI state is a semi-known TCI state based at least in part on not satisfying the known TCI state condition and satisfying the TCI state prediction condition, as described above.

[0130] like Fig.11 As further shown, in some aspects, process 1100 may include applying a TCI state switching delay timeline associated with a semi-known TCI state (block 1130). Fig.14 The communication manager 1408 and / or switching component 1414 depicted in FIG. 14 may apply a TCI state switching delay timeline associated with a semi-known TCI state, as described above.

[0131] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0132] In a first aspect, identifying a TCI state includes identifying a TCI state based at least in part on a MAC CE that activates or updates the TCI state.

[0133] In a second aspect, alone or in combination with the first aspect, identifying the TCI state includes identifying the TCI state from TCI states in an activated TCI state list.

[0134] In a third aspect, alone or in combination with one or more of the first and second aspects, identifying the TCI state includes identifying the TCI state from TCI states outside of an activated TCI state list.

[0135] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a known TCI state condition includes: receiving a TCI state switching command within 1280 milliseconds after the last reference signal for beam reporting or measurement; sending at least one L1-RSRP report for the TCI state before receiving the TCI state switching command; the TCI state remains detectable during the TCI state switching period; and the SSB associated with the TCI state remains detectable during the TCI state switching period, and if the above occurs, the known TCI state condition is satisfied.

[0136] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, when channel characteristics of reference signal resources are predicted within a prediction duration, a TCI state prediction condition is met.

[0137] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the predicted channel characteristics include L1-RSRP reported when the RS is not received or measured.

[0138] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, channel characteristics are predicted based at least in part on sending a preference for using RS resources as a type DQCL source without sending L1-RSRP reports.

[0139] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, channel characteristics are predicted based at least in part on a preference for using RS resources as type D QCL sources without sending L1-RSRP reports, and the preference is not sent.

[0140] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the prediction duration is preconfigured for a specified prediction scenario.

[0141] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1100 comprises determining, without signaling from a network entity, that a TCI state can be a semi-known TCI state.

[0142] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 1100 includes determining, based at least in part on signaling from a network entity, that the TCI state can be a semi-known TCI state.

[0143] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the signaling includes an RRC message indicating that the UE can determine whether the TCI state can be a semi-known TCI state.

[0144] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the signaling includes a TCI state activation command.

[0145] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the signaling includes a MAC CE message dedicated to activating a TCI state and associated with a semi-known TCI state.

[0146] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the process 1100 includes sending a suitability indication indicating that the UE is suitable for using a semi-known TCI state.

[0147] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the applicability indication further indicates a preference for which TCI states are to be associated with the semi-known condition.

[0148] In a seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, process 1100 includes sending a preference indication of a preference for which TCI states are to be associated with the semi-known condition.

[0149] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, process 1100 includes sending an association indication in a confirmation of a TCI state activation command indicating whether the semi-known condition is associated with the TCI state.

[0150] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, process 1100 comprises sending a prediction duration indication of a preference for a prediction duration in which to make a prediction.

[0151] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the TCI state switching delay timeline associated with the semi-known TCI state does not include a first delay for measuring CSI-RS or SSB, and does not include a second delay for reporting L1-RSRP measurements.

[0152] In aspect 21, either alone or in combination with one or more of aspects 1 to 20, a TCI state switching delay timeline associated with a semi-known TCI state does not include a first delay for measuring CSI-RS and does not include a second delay for reporting L1-RSRP measurements.

[0153] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the TCI state switching delay timeline includes a dedicated delay for L1 measurement reporting of a semi-known TCI state.

[0154] In a twenty-third aspect, alone or in combination with one or more of aspects one through twenty-second, process 1100 includes reducing a beam scanning factor in response to the TCI state being a semi-known TCI state.

[0155] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0156] Fig.12 1 is a diagram illustrating an example process 1200 performed, for example, by a UE according to the present disclosure. Example process 1200 is an example in which a UE (eg, UE 120, UE 920) performs operations associated with falling back to a known TCI state.

[0157] like Fig.12 As shown, in some aspects, process 1200 may include identifying a TCI state (block 1210). For example, the UE (e.g., using communication manager 1408 and / or identification component 1410 as depicted in diagram 1410) may identify the TCI state, as described above.

[0158] like Fig.12As further shown, in some aspects, process 1200 may include determining that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied (block 1220). Fig.14 The communication manager 1408 and / or determination component 1412 depicted in FIG. 14 may determine that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied, as described above.

[0159] like Fig.12 As further shown, in some aspects, process 1200 may include applying a TCI state switching delay timeline associated with a known TCI state (block 1230). Fig.14 The communication manager 1408 and / or switching component 1414 depicted in FIG. 14 may apply a TCI state switching delay timeline associated with a known TCI state, as described above.

[0160] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0161] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be performed in parallel.

[0162] Fig.13 13 is a diagram illustrating an example process 1300 performed, for example, by a network entity according to the present disclosure. Example process 1300 is an example in which a network entity (eg, base station 110, network entity 910) performs operations associated with using a semi-known TCI state.

[0163] like Fig.13 As shown, in some aspects, process 1300 may include receiving a preference indication indicating a preference associated with determining whether a TCI state is semi-known (block 1310). For example, a network entity (e.g., using Fig.15 The communication manager 1508 and / or receiving component 1502 depicted in FIG. 14 may receive a preference indication indicating a preference associated with determining whether the TCI state is semi-known, as described above.

[0164] like Fig.13 As further shown, in some aspects, process 1300 may include sending a configuration including a capability for determining whether a TCI state is a semi-known TCI state (block 1320). Fig.15The communication manager 1508 and / or sending component 1504 depicted in can send a configuration including the ability to determine whether the TCI state is a semi-known TCI state, as described above.

[0165] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0166] In a first aspect, receiving the preference indication includes receiving the preference indication in an acknowledgement of a TCI state activation command.

[0167] In a second aspect, either alone or in combination with the first aspect, the preference indication comprises a preference for a prediction duration within which the prediction is to be made.

[0168] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1300 includes applying a TCI state switch delay timeline associated with a semi-known TCI state.

[0169] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the configuration reduces the beam scanning factor for a semi-known TCI state.

[0170] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1300. Additionally or alternatively, two or more blocks of the blocks of process 1300 may be performed in parallel.

[0171] Fig.14 1400 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a UE (e.g., UE 120, UE 920), or a UE may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and transmitting component 1404. As further shown, apparatus 1400 may include a communication manager 1408. Communication manager 1408 may control and / or otherwise manage one or more operations of receiving component 1402 and / or transmitting component 1404. In some aspects, communication manager 1408 may include a communication manager 1408 in conjunction with Figure 2One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 1408 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1408 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1408 can include a receiving component 1402 and / or a sending component 1404. The communication manager 1408 can include an identification component 1410, a determination component 1412, and / or a switching component 1414, among others.

[0172] In some aspects, the apparatus 1400 may be configured to perform Figures 1 to 10 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.11 Process 1100, Fig.12 In some aspects, the apparatus 1400 and / or Fig.14 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.14 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0173] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0174] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0175] The identification component 1410 can identify a TCI state. The determination component 1412 can determine that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition. The switching component 1414 can apply a TCI state switching delay timeline associated with the semi-known TCI state.

[0176] Determining component 1412 can determine that the TCI state can be a semi-known TCI state without signaling from a network entity. Determining component 1412 can determine that the TCI state can be a semi-known TCI state based at least in part on signaling from a network entity. Sending component 1404 can send an applicability indication indicating that the UE is applicable to use a semi-known TCI state.

[0177] The sending component 1404 can send a preference indication of a preference of which TCI states are to be associated with the semi-known condition. The sending component 1404 can send an association indication in an acknowledgement of the TCI state activation command indicating whether the semi-known condition is associated with the TCI state. The sending component 1404 can send a prediction duration indication of a preference of a prediction duration in which prediction is to be made. The switching component 1414 can reduce the beam scanning factor in response to the TCI state being the semi-known TCI state.

[0178] In some aspects, identification component 1410 can identify a TCI state. Determination component 1412 can determine that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied. Switching component 1414 can apply a TCI state switching delay timeline associated with a known TCI state.

[0179] Fig.14 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.14Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.14 Two or more components shown in may be implemented in a single component, or Fig.14 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The assembly of (one or more) components shown in the executable is described as being composed of Fig.14 Another collection of components shown in the figure performs one or more functions.

[0180] Fig.15 is a diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a network entity (e.g., base station 110, network entity 910), or a network entity may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and transmitting component 1504. As further shown, apparatus 1500 may include a communication manager 1508. Communication manager 1508 may control and / or otherwise manage one or more operations of receiving component 1502 and / or transmitting component 1504. In some aspects, communication manager 1508 may include a communication manager 1508 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communications manager 1508 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1508 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1508 can include a receiving component 1502 and / or a sending component 1504. The communication manager 1508 can include a switching component 1510, among others.

[0181] In some aspects, the apparatus 1500 may be configured to perform Figures 1 to 10 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.13 In some aspects, the apparatus 1500 and / or Fig.15 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.15 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0182] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1500. In some aspects, the receiving component 1502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0183] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0184] Receiving component 1502 can receive a preference indication indicating a preference associated with determining whether a TCI state is semi-known. Sending component 1504 can send a configuration including an ability to determine whether a TCI state is a semi-known TCI state. Switching component 1510 can apply a TCI state switching delay timeline associated with a semi-known TCI state.

[0185] Fig.15 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.15Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.15 Two or more components shown in may be implemented in a single component, or Fig.15 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 The assembly of (one or more) components shown in the executable is described as being composed of Fig.15 Another collection of components shown in the figure performs one or more functions.

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

[0187] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: identifying a transmit configuration indicator (TCI) state; determining that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition; and applying a TCI state switching delay timeline associated with the semi-known TCI state.

[0188] Aspect 2: The method according to aspect 1, wherein identifying the TCI state includes identifying the TCI state based at least in part on a medium access control element (MAC CE) that activates or updates the TCI state.

[0189] Aspect 3: The method according to aspect 1 or 2, wherein identifying the TCI state comprises identifying the TCI state from TCI states in an activated TCI state list.

[0190] Aspect 4: The method according to aspect 1 or 2, wherein identifying the TCI state comprises identifying the TCI state from TCI states outside an activated TCI state list.

[0191] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the known TCI state condition includes: receiving a TCI state switching command within 1280 milliseconds after the last reference signal used for beam reporting or measurement; sending at least one layer 1 reference signal received power report for the TCI state before receiving the TCI state switching command; the TCI state remains detectable during the TCI state switching period; and the synchronization signal block associated with the TCI state remains detectable during the TCI state switching period.

[0192] Aspect 6: According to the method according to any one of Aspects 1 to 5, the TCI state prediction condition is met when the channel characteristics of the reference signal (RS) resource are predicted within a prediction duration.

[0193] Aspect 7: The method according to aspect 6, wherein the predicted channel characteristics include layer 1 RS received power reported when the RS is not received or measured.

[0194] Aspect 8: The method of aspect 6, wherein the channel characteristics are predicted based at least in part on sending a preference for using the RS resource as a type D quasi co-site source without sending a layer 1 RS received power report.

[0195] Aspect 9: A method according to aspect 6, wherein the channel characteristics are predicted at least in part based on a preference for using the RS resources as a type D quasi co-located source without sending a layer 1 RS received power report, and wherein the preference is not sent.

[0196] Aspect 10: The method according to aspect 6, wherein the prediction duration is preconfigured for specifying a prediction scenario.

[0197] Aspect 11: The method according to any one of aspects 1 to 10 further comprises determining that the TCI state can be a semi-known TCI state without signaling from a network entity.

[0198] Aspect 12: The method according to any one of aspects 1 to 11 further comprises determining that the TCI state can be a semi-known TCI state based at least in part on signaling from a network entity.

[0199] Aspect 13: The method according to aspect 12, wherein the signaling includes a radio resource configuration message, the radio resource configuration message indicating that the UE can determine whether the TCI state can be a semi-known TCI state.

[0200] Aspect 14: The method according to Aspect 12, wherein the signaling includes a TCI state activation command.

[0201] Aspect 15: The method according to aspect 12, wherein the signaling includes a medium access control control element message, the medium access control control element message is dedicated to activating the TCI state and is associated with the semi-known TCI state.

[0202] Aspect 16: The method according to any one of Aspects 1 to 15 further includes sending a suitability indication indicating that the UE is suitable for using a semi-known TCI state.

[0203] Aspect 17: The method according to aspect 16, wherein the applicability indication further indicates a preference for which TCI states are to be associated with the semi-known condition.

[0204] Aspect 18: The method according to any one of aspects 1 to 17, further comprising sending a preference indication of which TCI states are to be associated with the semi-known condition.

[0205] Aspect 19: The method according to any one of Aspects 1 to 18, further comprising sending an association indication indicating whether a semi-known condition is associated with the TCI state in a confirmation of a TCI state activation command.

[0206] Aspect 20: The method according to any one of aspects 1 to 19, further comprising sending a prediction duration indication of a preference for a prediction duration in which prediction is to be made.

[0207] Aspect 21: A method according to any one of Aspects 1 to 20, wherein the TCI state switching delay timeline associated with the semi-known TCI state does not include a first delay for measuring a channel state information reference signal (RS) or a synchronization signal block, and does not include a second delay for reporting layer 1 RS received power measurement.

[0208] Aspect 22: A method according to any one of Aspects 1 to 21, wherein the TCI state switching delay timeline associated with the semi-known TCI state does not include a first delay for measuring a channel state information reference signal (RS) and does not include a second delay for reporting layer 1 RS received power measurement.

[0209] Aspect 23: The method according to any one of aspects 1 to 22, wherein the TCI state switching delay timeline includes a dedicated delay for layer 1 measurement reporting of semi-known TCI states.

[0210] Aspect 24: The method according to Aspect 23, further comprising reducing a beam scanning factor in response to the TCI state being a semi-known TCI state.

[0211] Aspect 25: A method of wireless communication performed by a user equipment (UE), comprising: identifying a transmit configuration indicator (TCI) state; determining that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied; and applying a TCI state switching delay timeline associated with a known TCI state.

[0212] Aspect 26: A method of wireless communication performed by a network entity, comprising: receiving a preference indication indicating a preference associated with determining whether a transmit configuration indicator (TCI) state is semi-known; and sending a configuration including a capability for determining whether the TCI state is a semi-known TCI state.

[0213] Aspect 27: The method according to aspect 26, wherein receiving the preference indication includes receiving the preference indication in an acknowledgement of a TCI state activation command.

[0214] Aspect 28: The method according to aspect 26 or 27, wherein the preference indication comprises a preference for a prediction duration within which the prediction is to be made.

[0215] Aspect 29: The method according to any one of aspects 26 to 28, further comprising applying a TCI state switching delay timeline associated with a semi-known TCI state.

[0216] Aspect 30: A method according to any one of aspects 26 to 29, wherein the configuration reduces the beam scanning factor for a semi-known TCI state.

[0217] Aspect 31: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 30.

[0218] Aspect 32: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 30.

[0219] Aspect 33: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 30.

[0220] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.

[0221] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 30.

[0222] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0223] Further disclosure is included in the appendix. This appendix is ​​provided as an example only and should be considered a part of this specification. The definitions, illustrations, or other descriptions in the appendix do not replace or cover similar information contained in the specific embodiments or figures. In addition, the definitions, illustrations, or other descriptions in the specific embodiments or figures do not replace or cover similar information contained in the appendix. In addition, this appendix is ​​not intended to limit the disclosure of possible aspects.

[0224] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code to describe the operation and behavior of the system and / or method herein, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0225] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0226] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0227] Any element, action or instruction used herein should not be interpreted as key or necessary, unless otherwise clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: Identifies the status of the Transmit Configuration Indicator (TCI); determining that the TCI state is a semi-known TCI state based at least in part on not satisfying a known TCI state condition and satisfying a TCI state prediction condition; and A TCI state switching delay timeline associated with a semi-known TCI state is applied.

2. The UE of claim 1, wherein to identify the TCI state, the one or more processors are configured to identify the TCI state based at least in part on a medium access control element (MAC CE) that activates or updates the TCI state.

3. The UE of claim 1, wherein to identify the TCI state, the one or more processors are configured to identify the TCI state from TCI states in an activated TCI state list.

4. The UE of claim 1, wherein to identify the TCI state, the one or more processors are configured to identify the TCI state from TCI states outside an activated TCI state list.

5. The UE according to claim 1, wherein the known TCI status condition comprises: A TCI state switch command is received within 1280 milliseconds after the last reference signal used for beam reporting or measurement; before receiving the TCI state switching command, sending at least one layer 1 reference signal received power report for the TCI state; The TCI state remains detectable during a TCI state switching period; and The synchronization signal block associated with the TCI state remains detectable during the TCI state switching period.

6. The UE according to claim 1, wherein the TCI state prediction condition is satisfied when a channel characteristic of a reference signal (RS) resource is predicted within a prediction duration. 7 . The UE according to claim 6 , wherein the predicted channel characteristics include layer 1 RS received power reported when the RS is not received or measured.

8. The UE of claim 6, wherein the channel characteristic is predicted based at least in part on sending a preference for using the RS resource as a Type D quasi co-site source without sending a layer 1 RS received power report.

9. The UE of claim 6, wherein the channel characteristics are predicted based at least in part on a preference for using the RS resources as a Type D quasi co-located source without sending a layer 1 RS received power report, and wherein the preference is not sent. 10 . The UE of claim 6 , wherein the prediction duration is preconfigured for specifying a prediction scenario.

11. The UE of claim 1 , wherein the one or more processors are configured to determine that the TCI state can be a semi-known TCI state without signaling from a network entity.

12. The UE of claim 1, wherein the one or more processors are configured to determine that the TCI state can be a semi-known TCI state based at least in part on signaling from a network entity.

13. The UE of claim 12, wherein the signaling comprises a radio resource configuration message indicating that the UE can determine whether the TCI state can be a semi-known TCI state.

14. The UE according to claim 12, wherein the signaling comprises a TCI state activation command.

15. The UE of claim 12, wherein the signaling comprises a medium access control control element message dedicated to activating a TCI state and associated with a semi-known TCI state.

16. The UE of claim 1, wherein the one or more processors are configured to send a suitability indication indicating that the UE is suitable for using a semi-known TCI state.

17. The UE of claim 16, wherein the applicability indication further indicates a preference for which TCI states are to be associated with semi-known conditions.

18. The UE of claim 1, wherein the one or more processors are configured to send a preference indication of a preference for which TCI states are to be associated with a semi-known condition.

19. The UE of claim 1, wherein the one or more processors are configured to send an association indication in a confirmation of a TCI state activation command indicating whether a semi-known condition is associated with the TCI state.

20. The UE of claim 1, wherein the one or more processors are configured to send a prediction duration indication of a preference for a prediction duration in which to make predictions.

21. The UE of claim 1, wherein the TCI state switching delay timeline associated with a semi-known TCI state does not include a first delay for measuring a channel state information reference signal (RS) or a synchronization signal block, and does not include a second delay for reporting a layer 1 RS received power measurement.

22. The UE of claim 1, wherein the TCI state switching delay timeline associated with a semi-known TCI state does not include a first delay for measuring a channel state information reference signal (RS) and does not include a second delay for reporting a layer 1 RS received power measurement.

23. The UE of claim 1, wherein the TCI state switching delay timeline includes a dedicated delay for layer 1 measurement reporting for semi-known TCI states.

24. The UE of claim 23, wherein the one or more processors are configured to reduce a beam scanning factor in response to the TCI state being a semi-known TCI state.

25. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: Identifies the status of the Transmit Configuration Indicator (TCI); Determining that a known TCI state condition is not satisfied and a TCI state prediction condition is satisfied; and A TCI state switch delay timeline associated with a known TCI state is applied.

26. A network entity for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a preference indication indicating a preference associated with determining whether a transmit configuration indicator (TCI) state is semi-known; and Sending a configuration including the ability to determine whether the TCI state is a semi-known TCI state.

27. The network entity of claim 26, wherein to receive the preference indication, the one or more processors are configured to receive the preference indication in an acknowledgement of a TCI state activation command.

28. The network entity of claim 26, wherein the preference indication comprises a preference for a prediction duration within which prediction is to be made.

29. The network entity of claim 26, wherein the one or more processors are configured to apply a TCI state switching delay timeline associated with a semi-known TCI state.

30. The network entity of claim 26, wherein the configuration reduces a beam scanning factor for a semi-known TCI state.

Images