Reporting channel state information associated with beam prediction results

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can identify, at a channel state information (CSI) reporting occasion, that a UE-side beam prediction result satisfies a criterion. The UE can drop, based at least in part on the UE-side beam prediction result satisfying the criterion, a CSI report that includes the UE-side beam prediction result. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for reporting channel state information (CSI) associated with beam prediction results. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0004] In some specific implementations, an apparatus for wireless communication at a user equipment (UE) includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being capable of operating individually or in any combination to cause the apparatus to: identify when a channel state information (CSI) report is submitted that the UE-side beam prediction result meets a criterion; and to discard a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criterion.

[0005] In some specific implementations, an apparatus for wireless communication at a UE includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being capable of operating individually or in any combination to enable the apparatus to: identify at a CSI reporting time when the UE-side beam prediction result meets the criteria; and transmit a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid based at least in part on the UE-side beam prediction result meeting the criteria.

[0006] In some specific implementations, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being capable of operating individually or in any combination to enable the apparatus to: receive a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid based at least in part on the UE-side beam prediction results meeting a criterion; and to perform scheduling in the absence of UE-side beam prediction results based at least in part on the indication.

[0007] In some specific implementations, a method for wireless communication performed by a UE includes: identifying at the time of CSI reporting that the UE-side beam prediction result meets the criteria; and discarding CSI reports including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criteria.

[0008] In some specific implementations, a method for wireless communication performed by a UE includes: identifying at the CSI reporting time point that the UE-side beam prediction result meets the criteria; and sending a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid based at least in part on the UE-side beam prediction result meeting the criteria.

[0009] In some specific implementations, a method of wireless communication performed by a network node includes: receiving a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on criteria met by the UE-side beam prediction results; and performing scheduling in the absence of UE-side beam prediction results at least in part based on the indication.

[0010] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a UE, cause the UE to: identify at the time of a CSI report that the UE-side beam prediction result meets a criterion; and discard a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criterion.

[0011] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a UE, cause the UE to: identify at a CSI reporting time when the UE-side beam prediction result meets a criterion; and send a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid at least in part based on the UE-side beam prediction result meeting the criterion.

[0012] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a network node, cause the network node to: receive a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on criteria met by the UE-side beam prediction results; and perform scheduling in the absence of UE-side beam prediction results, at least in part based on the indication.

[0013] In some specific implementations, an apparatus for wireless communication includes: a component for identifying, at the time of a CSI report, that the device-side beam prediction result meets a criterion; and a component for discarding a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criterion.

[0014] In some specific implementations, an apparatus for wireless communication includes: components for identifying, at the time of a CSI report, that a device-side beam prediction result meets a criterion; and components for transmitting a CSI report including the device-side beam prediction result, wherein the CSI report includes an indication that the device-side beam prediction result will be ignored or considered invalid based at least in part on the fact that the device-side beam prediction result meets the criterion.

[0015] In some specific implementations, an apparatus for wireless communication includes: a component for receiving a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on criteria met by the UE-side beam prediction results; and a component for performing scheduling in the absence of UE-side beam prediction results based at least in part on the indication.

[0016] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0017] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0018] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

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

[0020] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0022] Figure 4This is a diagram illustrating an example of channel state information (CSI) associated with beam prediction results in accordance with this disclosure.

[0023] Figures 5 to 7 This is a diagram illustrating an example process associated with CSI reports related to beam prediction results according to this disclosure.

[0024] Figures 8 to 9 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0025] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0026] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0027] Network nodes can schedule UEs to report beam prediction results via Channel State Information (CSI) reports. CSI reports may potentially be multiplexed with other CSI reports or Uplink Control Information (UCI) on the same Physical Uplink Channel (PUxCH). Alternatively, CSI reports may not be multiplexed with other CSI reports or UCI on the same PUxCH.

[0028] At a given CSI reporting time (e.g., a periodic / semi-persistent CSI reporting time or an aperiodic triggered CSI reporting time), the UE may determine not to report its current beam prediction result to the network node. For example, the UE may momentarily identify that reporting its current beam prediction result to the network node would be meaningless. The UE may determine not to report its current beam prediction result due to an inapplicable scenario (e.g., the difference between the AI ​​or machine learning (AI / ML) input and normal characteristics meets a threshold). The UE may determine not to report its current beam prediction result due to unreliable prediction. Unreliable prediction may be due to the prediction output being associated with relatively low confidence, causing the network node to use the prediction output for scheduling, resulting in relatively poor throughput performance or causing interruption / confusion issues for network-side link adaptation. Unreliable prediction may be due to significant changes in other UE-side conditions compared to the conditions used to train the model (e.g., sudden UE drop or rotation). Unreliable prediction may be due to the unavailability of the prediction result (e.g., UE processing limitations). Unreliable prediction may be a result of UE-side lifecycle management (LCM) operations.

[0029] Due to inapplicability to the scenario and / or unreliable prediction, the UE may indicate that reporting its current beam prediction result to the network node would be inappropriate. However, the UE may not have a mechanism to not report its current beam prediction result or to notify the network node that the current beam prediction result is not applicable to AI / ML-based beam management. Therefore, the network node may continue to use the UE-side beam prediction result for AI / ML-based beam management (e.g., scheduling), which can lead to decreased throughput and overall network performance.

[0030] Various aspects collectively involve reporting CSI results associated with beam prediction. Some aspects are more specifically related to discarding CSI reports or sending CSI reports with indications to ignore beam prediction results. In some examples, the UE may indicate at the time of CSI reporting that the UE-side beam prediction results meet criteria. Criteria may be related to measurements or priors regarding the prediction. K The threshold for the UE prediction confidence level of each resource is associated with the following: KIt is a positive integer. The UE may discard a CSI report including the UE-side beam prediction result, at least in part, based on criteria met by the UE-side beam prediction result. The criteria for discarding the CSI report may be predefined by a standard, signaled by the network, or determined at the UE. Alternatively, the UE may send a CSI report including the UE-side beam prediction result, wherein the CSI report may include an indication that the UE-side beam prediction result will be ignored or considered invalid, at least in part, based on criteria met by the UE-side beam prediction result. The CSI report may include one or more additional bits to indicate that the UE-side beam prediction result will be ignored or considered invalid. The CSI report may include one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid. Network nodes may perform scheduling without using the UE-side beam prediction result.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used by network nodes to avoid using UE-side beam prediction results when performing scheduling for a UE by configuring the UE to identify whether the UE-side prediction result meets the criteria and then discarding the CSI report or sending a CSI report with an indication that the UE-side prediction result and the UE-side beam prediction result will be ignored or considered invalid. Network nodes can avoid performing scheduling when the UE-side beam prediction result can be associated with unreliable predictions that would otherwise cause poor throughput performance for the UE. By avoiding the use of UE-side beam prediction results for scheduling, poor throughput performance can be avoided, thereby improving overall network performance.

[0032] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables different wireless communication devices to communicate at the city, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution program released by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0033] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or AI / ML, and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0034] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0035] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0036] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency 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.

[0037] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may be referred to as: NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in the radio access network (RAN).

[0038] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete protocol stack. For example, and as shown, network node 110 may be an aggregated network node, meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0039] Alternatively, and also as shown, network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 may use protocol stacks that are physically distributed and / or logically distributed across two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple individually deployable units.

[0040] Network nodes 110 of wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some examples, DUs may also host one or more low-PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or low-PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0041] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0042] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0043] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0044] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0045] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0046] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0047] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0048] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0049] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0050] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0051] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0052] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. Category 1 UEs 120 facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to Category 2 UEs 120. Category 2 UEs 120 may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. Category 3 UEs 120 may possess intermediate-level complexity and / or capabilities (e.g., capabilities between Category 1 and Category 2 UEs 120). Category 3 UEs 120 may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0053] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can send and receive sidelink communication using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0054] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0055] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0056] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may identify when the UE-side beam prediction result meets the criteria at the CSI reporting time; and discard a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criteria. As described in more detail elsewhere herein, the communication manager 140 may identify when the UE-side beam prediction result meets the criteria at the CSI reporting time; and send a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid based at least in part on the UE-side beam prediction result meeting the criteria. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on criteria met by the UE-side beam prediction results; and to perform scheduling at least in part based on the indication in the absence of UE-side beam prediction results. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0058] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0059] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0060] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0061] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0062] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0063] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or CSI reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0064] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0065] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0066] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0067] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0068] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0069] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0070] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0071] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (such as a data pipeline, data queue, and / or application executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0072] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0073] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0074] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0075] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, 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, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0076] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0077] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0078] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0079] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0080] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0081] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360) (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0082] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0083] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each 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 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0084] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0085] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0086] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0087] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with reporting CSI results related to beam prediction, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with reporting CSI results related to beam prediction, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 5 Process 500 Figure 6 Process 600 Figure 7 The operation of process 700 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 5 Process 500 Figure 6 Process 600 Figure 7 The process 700 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0088] In some aspects, the UE (e.g., UE 120) includes components for identifying that the UE-side beam prediction result meets the criteria at the time of CSI reporting; and / or for discarding a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criteria. In some aspects, the UE includes components for identifying that the UE-side beam prediction result meets the criteria at the time of CSI reporting; and / or for transmitting a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid based at least in part on the UE-side beam prediction result meeting the criteria. Components for the UE to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0089] In some aspects, a network node (e.g., the network node) includes: components for receiving a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on criteria met by the UE-side beam prediction results; and / or components for performing scheduling in the absence of UE-side beam prediction results, at least in part based on the indication. Components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 216, 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.

[0090] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0091] In AI / ML-based beam management, the first beam management scenario may involve spatial domain downlink beam prediction, and the second beam management scenario may involve temporal domain downlink beam prediction. The first beam management scenario may involve spatial downlink transmission beam prediction for a first set of beams (set A) based at least in part on measurements of a second set of beams (set B). The second beam management scenario may involve temporal downlink transmission beam prediction for a first set of beams (set A) based at least in part on historical measurements of the second set of beams (set B). A general framework design can support both the first and second beam management scenarios. AI / ML-based beam management may involve downlink transmission beam prediction for both the UE-side model and the network-side model. AI / ML-based beam management may involve defining necessary signaling / mechanisms to facilitate data collection, model inference, and performance monitoring for both the UE-side model and the network-side model. AI / ML-based beam management may involve defining signaling / mechanisms to facilitate necessary LCM operations for the UE-side model. Signaling / mechanisms can be specified to facilitate LCM operation specific to beam management use cases. AI / ML-based beam management may involve ensuring consistency between training and inference regarding network-side additional conditions used for inference at the UE.

[0092] Network nodes can schedule UEs to report beam predictions via CSI reports (e.g., regarding the timing before or after the time slot carrying UE feedback, Layer 1 (L1) RSRP (L1-RSRP) or L1 signal-to-interference-plus-noise ratio (SINR) (L1-SINR) measurements, or information regarding L1-RSRP / L1-SINR prior to or after the time slot). K (Resource). In the first case, a CSI report may potentially be reused on the same PUxCH as other CSI reports or UCI reports. In the second case, a CSI report may not be reused on the same PUxCH as other CSI reports or UCI reports (e.g., a CSI report is not assumed to be reused on the same PUxCH as other CSI reports or UCI reports).

[0093] At a given CSI reporting time (e.g., a periodic / semi-persistent CSI reporting time or an aperiodic triggered CSI reporting time), the UE may determine not to report its current beam prediction result to the network node. For example, the UE may momentarily identify that reporting its current beam prediction result to the network node would be meaningless. The UE may determine not to report its current beam prediction result due to an inapplicable scenario (e.g., the difference between the AI / ML input and normal characteristics meets a threshold). The UE may determine not to report its current beam prediction result due to unreliable prediction. Unreliable prediction may be due to the prediction output being associated with relatively low confidence, causing the network node to use the prediction output for scheduling, resulting in relatively poor throughput performance or causing interruption / confusion issues for network-side link adaptation. Unreliable prediction may be due to significant changes in other UE-side conditions compared to the conditions used to train the model (e.g., sudden UE drop or rotation). Unreliable prediction may be due to the unavailability of the prediction result (e.g., UE processing limitations). Unreliable prediction may be a result of LCM operations on the UE side.

[0094] Due to inapplicability to the scenario and / or unreliable prediction, the UE may indicate that reporting its current beam prediction result to the network node would be inappropriate. However, the UE may not have a mechanism to not report its current beam prediction result or to notify the network node that the current beam prediction result is not applicable to AI / ML-based beam management. Therefore, the network node may continue to use the UE-side beam prediction result for AI / ML-based beam management (e.g., scheduling), which can lead to decreased throughput and overall network performance.

[0095] In various aspects of the technologies and apparatus described herein, the UE can identify UE-side beam prediction results as meeting criteria at the CSI reporting time. Criteria can be related to measurements or prior art regarding the prediction. K The threshold for the UE prediction confidence level of each resource is associated with the following: K It is a positive integer. The UE may discard a CSI report including the UE-side beam prediction result, at least in part, based on criteria met by the UE-side beam prediction result. The criteria for discarding the CSI report may be predefined by a standard, signaled by the network, or determined at the UE. Alternatively, the UE may send a CSI report including the UE-side beam prediction result, wherein the CSI report may include an indication that the UE-side beam prediction result will be ignored or considered invalid, at least in part, based on criteria met by the UE-side beam prediction result. The CSI report may include one or more additional bits to indicate that the UE-side beam prediction result will be ignored or considered invalid. The CSI report may include one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid. Network nodes may perform scheduling without UE-side beam prediction results.

[0096] In some respects, by configuring the UE to identify whether the UE-side prediction result meets the criteria, and then discarding the CSI report or sending a CSI report indicating that the UE-side prediction result and the UE-side beam prediction result will be ignored or considered invalid, network nodes can avoid using UE-side beam prediction results when performing scheduling for the UE. Network nodes can also avoid performing scheduling when the UE-side beam prediction result can be associated with unreliable predictions that would otherwise cause poor throughput performance for the UE. By avoiding the use of UE-side beam prediction results for scheduling, poor throughput performance can be avoided, thereby improving overall network performance.

[0097] In some aspects, signaling support can be defined that allows informing network nodes that a UE is unwilling to share its current prediction results with the network node because the current prediction results are associated with inapplicable scenarios and / or unreliable predictions. In other aspects, a UE can choose to directly discard a CSI report when it is not multiplexed with other CSI reports or UCIs on the same PUxCH. This can be done, at least in part, based on the network-specific implementation. For example, the network node can reuse a previously used Transmit Configuration Indicator (TCI) state, or the network node can trigger an actual reference signal to fall back to beam management based on conventional measurements for a certain period. The discard criteria / events can be network-controlled or standard-predefined. Discarding a CSI report can cause ambiguity regarding which CSI reports are involved in the PUxCH when it is potentially multiplexed with other CSI reports or UCIs on the same PUxCH.

[0098] In some respects, when a CSI report is not multiplexed on the same PUxCH as other CSI reports or UCIs, or when a CSI report is potentially multiplexed on the same PUxCH as other CSI reports or UCIs, the CSI report payload may include additional bits or use feedback positions reserved relative to the prediction result payload to indicate that the reported prediction result is preferably not used for scheduling by network nodes. The CSI report may include additional bits to indicate that the reported prediction result should not be used because it is associated with an inapplicable scenario and / or an unreliable prediction. Using additional bits in the CSI report payload does not cause ambiguity issues compared to directly discarding the CSI report, but it may incur additional reporting overhead.

[0099] Figure 4 This is an illustration of Example 400, which is related to the CSI (Current Indicator) of the beam prediction results in the report according to this disclosure. Figure 4 As shown, Example 400 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0100] As indicated by reference numeral 402 in the attached figure, the UE can indicate at the CSI reporting time that the UE-side beam prediction result meets the criteria. The criteria can be related to measurements or prior art related to the prediction. K The threshold for the UE prediction confidence level of each resource is associated with the following: K is a positive integer.

[0101] As indicated by reference numeral 404, a UE may discard a CSI report, including the UE-side beam prediction result, based at least in part on criteria met by the UE-side beam prediction result. A CSI report may be discarded at least in part on the basis that it is not multiplexed with other CSI reports or other types of UCIs on the same uplink channel. Criteria for discarding CSI reports may be standard-predefined, signaled by the network, or determined at the UE. In some aspects, the UE may receive an indication of criteria associated with discarding CSI reports from a network node via network signaling, wherein such indication may be received via CSI report settings, CSI-related report configuration information, or a MAC-CE activating CSI reports. The UE may send an indication of criteria associated with discarding CSI reports to a network node via a UE capability report, an RRC message, or a MAC-CE.

[0102] As shown by reference numeral 406 in the accompanying figure, the UE may send a CSI report to the network node including the UE-side beam prediction results. The CSI report may include an indication that the UE-side beam prediction results will be ignored or considered invalid, at least in part, based on criteria met by the UE-side beam prediction results. In some aspects, the CSI report may include one or more additional bits to indicate that the UE-side beam prediction results will be ignored or considered invalid. The one or more additional bits may be a binary indication based on a single bit without indication of the criteria, or the one or more additional bits may include multiple bits with indication of the criteria. In some aspects, the CSI report may include one or more reserved bits for indicating that the UE-side beam prediction results will be ignored or considered invalid. The CSI report may include a measurement payload or resource identifier (ID) payload with one or more reserved bits. The one or more reserved bits may be associated with a Synchronization Block Resource Indicator (SSBRI) report component, a CSI-RS Resource Indicator (CRI) report component, or a Virtual Resource Indicator (VRI) report component. In some respects, the UE may transmit a CSI report including an indication based at least in part on the multiplexing of the CSI report with other CSI reports or UCIs on the same uplink channel, or at least in part on the CSI report not being multiplexed with other CSI reports or UCIs on the same uplink channel.

[0103] In some respects, UEs may be allowed to discard CSI reports. The standard may predefine: allowing UEs to discard CSI reports is at least in part based on the condition that the considered CSI report is not assumed to be multiplexed onto the same PUCCH / PUSCH with other CSI reports or other types of UCI. The criteria for discarding CSI reports can be standard-defined, signaled by the network, or determined by the UE. The criteria may be at least in part based on the UE-side beam prediction results being associated with inapplicable scenarios or unreliable predictions. The criteria may be related to L1-RSRP / L1-SINR or previous predictions. K The threshold for the UE prediction confidence level is associated with each resource. For network signaling, this is determined via CSI report settings and CSI-related report configuration information (…). CSI- AssociatedReportConfigInfo The parameters or MAC-CE RRC signaling activating CSI reporting can be used, or it can be a specially configured serving cell (ServCell) / BWP. For network signaling, the standard can predefine various optional criteria, and the network node can signal the option selected downwards. When the criteria are determined by the UE, the criteria can be predefined by the standard, or the network node can signal various optional criteria, and the UE can select the option downwards via UE capability report, RRC message, or MAC-CE report.

[0104] In some aspects, the UE can transmit data including UE-side beam prediction results (e.g., CSI reports). reportQuantity The time slot of the CSI report directly indicates that one or more components of the UE-side beam prediction result carried by the CSI report should be ignored or considered invalid because the UE-side beam prediction result is associated with an inapplicable scenario or unreliable prediction.

[0105] In some aspects, the CSI payload may allow the UE to indicate to the network node that the UE-side beam prediction result carried by the corresponding CSI reporting timing should be ignored or considered invalid. In some aspects, the UE may indicate that the UE-side beam prediction result should be ignored or considered invalid based at least in part on additional bits including those used for such invalidation indication. For example, a binary indication based on a single bit may be reported via UE capability or via a separate RRC / MAC-CE message. The binary indication based on a single bit may have no indication of a detailed reason (e.g., inapplicable scenario or unreliable prediction) or may have an indication of a detailed reason. As another example, multiple bits may be indicated, where different bits may indicate different reasons, such as inapplicable scenario, unreliable prediction, and / or unavailable prediction (e.g., UE processing limitations).

[0106] In some respects, the UE may indicate, at least in part, that the UE-side beam prediction result should be ignored or considered invalid based on one or more reserved positions for such invalidation, included in one or more components of the CSI payload. The UE may report the predicted L1-RSRP measurement and the corresponding SSBRI, CRI, and / or VRI to the network node. One or more of the L1-RSRP payload and / or resource ID payload may include reserved positions for such invalidation. For example, 5G NR may define some invalid L1-RSRP positions for the 7-bit strongest L1-RSRP report (valid for Layer 3 (L3) RSRP measurement reports). Such values ​​may be used in association with the strongest L1-RSRP predicted and carried in the CSI report. Since there may be more than one invalid L1-RSRP value, different values ​​can be used to interpret different reasons. The bit width of the SSBRI / CRI / VRI report components can be extended to ensure that invalidation indications can be carried. An invalid indication can be applied to the entire CSI report (e.g., via the strongest L1-RSRP value) or individually to the corresponding resource (e.g., via different L1-RSRP components or different resource IDs). Alternatively, when the UE is only assumed to be before reporting... K When a resource ID is used without addressing the corresponding L1-RSRP / L1-SINR, it may be necessary to extend the bit width to allow for reporting before... K At least one additional field for a resource ID will result in an invalid indication.

[0107] In some respects, whether a UE is allowed to discard CSI reports or whether the CSI payload allows the UE to instruct the UE-side beam prediction results to be ignored or considered invalid can be network-controlled. For example, this can be achieved through CSI report settings, CSI- AssociatedReportConfigInfo RRC signaling for the MAC-CE that activates the CSI report can be used, or a specially configured ServCell / BWP. Whether the UE is allowed to discard the CSI report or to indicate that the UE-side beam prediction result should be ignored / invalidated may be subject to the AI / ML functionality / model linked to the CSI report (e.g., not all functionality / models allow the UE to indicate invalidity).

[0108] In some respects, whether a UE is allowed to discard a specific CSI report or whether the UE-side beam prediction result should be ignored / invalidated can be network-controlled or standard-predefined. For example, this can be achieved through CSI report settings... CSI- AssociatedReportConfigInfoRRC signaling for the MAC-CE that activates the CSI report can be used, or a specially configured ServCell / BWP can be used. In some respects, the UE may only be allowed to discard a CSI report if it is not assumed to be multiplexed on the same PUxCH with other CSI reports or other types of UCI. On the other hand, the UE may instruct that UE-side beam prediction results should be ignored / invalidated without such a constraint.

[0109] As shown by reference numeral 408 in the accompanying figure, a network node can perform scheduling without UE-side beam prediction results. The network node can perform scheduling without UE-side beam prediction results based at least in part on the absence of a CSI report received from the UE (e.g., when the CSI report is discarded by the UE). Alternatively, the network node can perform scheduling without UE-side beam prediction results based at least in part on an indication that the UE-side beam prediction results received in the CSI report will be ignored or considered invalid. Therefore, scheduling will not suffer from poor throughput performance due to UE-side beam prediction results being associated with inapplicable scenarios or unreliable predictions.

[0110] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0111] Figure 5 This is a diagram illustrating an example process 500 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 500 is an example in which a device or UE (e.g., UE 120) performs operations associated with reporting CSI results related to beam prediction.

[0112] like Figure 5 As shown, in some aspects, process 500 may include identifying, at the CSI reporting time, that the UE-side beam prediction result meets the criteria (box 510). For example, the UE (e.g., using...) Figure 8 The Communication Manager 806 described above can identify when the UE-side beam prediction results meet the criteria at the CSI report timing.

[0113] like Figure 5 As further shown, in some aspects, process 500 may include discarding CSI reports (box 520) that include UE-side beam prediction results, at least in part, based on criteria met by the UE-side beam prediction results. For example, the UE (e.g., using...) Figure 8 The Communication Manager 806 described above may discard CSI reports that include UE-side beam prediction results, at least in part, based on criteria that the UE-side beam prediction results meet.

[0114] Process 500 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 in this document.

[0115] In the first aspect, the CSI report is discarded at least in part based on the fact that the CSI report is not multiplexed with other CSI reports or other types of UCI on the same uplink channel.

[0116] In the second aspect, either alone or in combination with the first aspect, the criteria for discarding the CSI report are standard-predefined, signaled by the network, or determined at the UE.

[0117] In the third aspect, alone or in combination with one or more of the first and second aspects, this criterion relates to measurements or predictions regarding forecasts. K The threshold for the UE prediction confidence level of each resource is associated with the following: K is a positive integer.

[0118] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 500 includes receiving, via network signaling, an instruction for the criterion associated with discarding the CSI report, wherein the instruction is received via CSI report settings, CSI-associated report configuration information, or a MAC-CE that activates the CSI report.

[0119] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 500 includes sending an instruction for the criterion associated with discarding the CSI report via a UE capability report, an RRC message, or a MAC-CE.

[0120] although Figure 5 An example box of process 500 is shown, but in some respects, process 500 may include... Figure 5 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 500 may be executed in parallel.

[0121] Figure 6 This is a diagram illustrating an example process 600 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 600 is an example in which a device or UE (e.g., UE 120) performs operations associated with reporting CSI results related to beam prediction.

[0122] like Figure 6 As shown, in some aspects, process 600 may include identifying, at the CSI reporting time, that the UE-side beam prediction result meets the criteria (box 610). For example, the UE (e.g., using...) Figure 8The Communication Manager 806 described above can identify when the UE-side beam prediction results meet the criteria at the CSI report timing.

[0123] like Figure 6 Further shown, in some aspects, process 600 may include sending a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid, at least in part, based on criteria met by the UE-side beam prediction results (box 620). For example, the UE (e.g., using...) Figure 8 The transmitting component 804 and / or the communication manager 806 described herein may transmit a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on the criteria that the UE-side beam prediction results meet, as described above.

[0124] Process 600 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 in this document.

[0125] In the first aspect, the CSI report includes one or more additional bits to indicate that the UE-side beam prediction results will be ignored or considered invalid.

[0126] In the second aspect, either alone or in combination with the first aspect, the one or more additional bits are binary indicators based on a single bit without any indication of the criterion, or the one or more additional bits include multiple bits with an indication of the criterion.

[0127] In the third aspect, either alone or in combination with one or more of the first and second aspects, the CSI report includes one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid.

[0128] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the CSI report includes a measurement payload or resource ID payload having the one or more reserved bits.

[0129] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the one or more reserved bits are associated with the SSBRI reporting component, the CRI reporting component, or the VRI reporting component.

[0130] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 600 includes transmitting the CSI report including the indication, either based at least in part on multiplexing the CSI report with other CSI reports or UCIs on the same uplink channel or based at least in part on not multiplexing the CSI report with other CSI reports or UCIs on the same uplink channel.

[0131] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 600 may be executed in parallel.

[0132] Figure 7 This is a diagram illustrating an example process 700 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 700 is an example in which a device or network node (e.g., network node 110) performs operations associated with reporting CSI results related to beam prediction.

[0133] like Figure 7 As shown, in some aspects, process 700 may include receiving a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid, at least in part, based on criteria met by the UE-side beam prediction results (box 710). For example, network nodes (e.g., using...) Figure 9 The receiving component 902 and / or communication manager 906 depicted herein may receive a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on the criteria that the UE-side beam prediction results meet, as described above.

[0134] like Figure 7 As further shown, in some aspects, process 700 may include performing scheduling (box 720) at least in part based on this instruction in the absence of UE-side beam prediction results. For example, network nodes (e.g., using...) Figure 9 The communication manager 906 depicted in the text can perform scheduling, at least in part, based on this instruction, in the absence of UE-side beam prediction results, as described above.

[0135] Process 700 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 in this document.

[0136] In the first aspect, the CSI report includes one or more additional bits to indicate that the UE-side beam prediction results will be ignored or considered invalid.

[0137] In the second aspect, either alone or in combination with the first aspect, the one or more additional bits are binary indicators based on a single bit without any indication of the criterion, or the one or more additional bits include multiple bits with an indication of the criterion.

[0138] In the third aspect, either alone or in combination with one or more of the first and second aspects, the CSI report includes one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid.

[0139] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the CSI report includes a measurement payload or resource ID payload having the one or more reserved bits.

[0140] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the one or more reserved bits are associated with the SSBRI reporting component, the CRI reporting component, or the VRI reporting component.

[0141] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 700 includes receiving a CSI report, including an indication, based at least in part on multiplexing the CSI report with other CSI reports or UCIs on the same uplink channel, or based at least in part on not multiplexing the CSI report with other CSI reports or UCIs on the same uplink channel.

[0142] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0143] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 806 is combined with... Figure 1The described communication manager 140. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0144] In some respects, device 800 can be configured to perform the functions described herein. Figure 4 One or more operations described herein. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 5 Process 500 Figure 6 The process 600 or a combination thereof. In some respects, Figure 8 The illustrated device 800 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 8 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

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

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

[0147] The communication manager 806 may support the operation of the receiving component 802 and / or the transmitting component 804. For example, the communication manager 806 may receive information associated with configuring the reception of communications by the receiving component 802 and / or the transmission of communications by the transmitting component 804. Additionally or alternatively, the communication manager 806 may generate control information and / or provide control information to the receiving component 802 and / or the transmitting component 804 to control the reception and / or transmission of communications.

[0148] The communication manager 806 can identify when the CSI report is submitted that the UE-side beam prediction result meets the criteria. The communication manager 806 can discard a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criteria. The receiving component 802 can receive an indication of the criteria associated with discarding the CSI report via network signaling, wherein the indication is received via CSI report settings, CSI-related report configuration information, or a MAC-CE that activates the CSI report. The transmitting component 804 can transmit the indication of the criteria associated with discarding the CSI report via a UE capability report, an RRC message, or a MAC-CE.

[0149] The communication manager 806 can indicate at the CSI report timing that the UE-side beam prediction result meets the criteria. The transmitting component 804 can transmit a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid, at least in part, based on the UE-side beam prediction result meeting the criteria.

[0150] Figure 8 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 8The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The executable description of the collection of (one or more) components shown is composed of Figure 8 Another set of components shown performs one or more functions.

[0151] Figure 9 This is a diagram illustrating an example device 900 for wireless communication according to the present disclosure. Device 900 may be a network node, or a network node may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 906 is combined with... Figure 1 The described communication manager 150. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0152] In some respects, device 900 can be configured to perform the functions described herein. Figure 4 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein (such as...). Figure 7 The process 700) or a combination thereof. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0153] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 902 and / or transmitter component 904 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 900 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0154] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 904 may co-located with the receive component 902 in one or more transceivers.

[0155] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0156] The receiving component 902 can receive a CSI report including UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid, at least in part, based on criteria met by the UE-side beam prediction results. The communication manager 906 can perform scheduling in the absence of UE-side beam prediction results, at least in part, based on a second indication.

[0157] Figure 9 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The executable description of the collection of (one or more) components shown is composed of Figure 9 Another set of components shown performs one or more functions.

[0158] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: identifying, at a channel state information (CSI) reporting time, that a UE-side beam prediction result meets a criterion; and discarding a CSI report including the UE-side beam prediction result based at least in part on the UE-side beam prediction result meeting the criterion.

[0159] Aspect 2: According to the method of aspect 1, the CSI report is discarded at least in part based on the fact that the CSI report is not multiplexed with other CSI reports or other types of uplink control information (UCI) on the same uplink channel.

[0160] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the criteria for discarding the CSI report are standard predefined, signaled by the network, or determined at the UE.

[0161] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the criterion is related to the measurement or prediction. K The threshold for the UE prediction confidence level of each resource is associated with the following: K is a positive integer.

[0162] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: receiving via network signaling an indication of the criteria associated with discarding the CSI report, wherein the indication is received via CSI report settings, CSI-associated report configuration information, or a Media Access Control (MAC-CE) element activating the CSI report.

[0163] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: sending an indication of the criteria associated with discarding the CSI report via a UE capability report, a radio resource control (RRC) message or a media access control control element (MAC-CE).

[0164] Aspect 7: A method for wireless communication performed by a user equipment (UE), the method comprising: identifying, at a channel state information (CSI) reporting time, that a UE-side beam prediction result meets a criterion; and transmitting a CSI report including the UE-side beam prediction result, wherein the CSI report includes an indication that the UE-side beam prediction result will be ignored or considered invalid at least in part based on the UE-side beam prediction result meeting the criterion.

[0165] Aspect 8: According to the method of aspect 7, the CSI report includes one or more additional bits to indicate that the UE-side beam prediction result will be ignored or considered invalid.

[0166] Aspect 9: According to the method of aspect 8, wherein the one or more additional bits are binary indicators based on a single bit without any indication of the criterion, or the one or more additional bits include multiple bits having an indication of the criterion.

[0167] Aspect 10: The method according to any one of Aspects 7 to 9, wherein the CSI report includes one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid.

[0168] Aspect 11: According to the method of aspect 10, wherein the CSI report includes a measurement payload or resource identifier payload having the one or more reserved bits.

[0169] Aspect 12: According to the method of aspect 10, wherein the one or more reserved bits are associated with a Synchronization Block Resource Indicator (SSBRI) report component, a Channel State Information Reference Signal Resource Indicator (CRI) report component, or a Virtual Resource Indicator (VRI) report component.

[0170] Aspect 13: The method according to any one of Aspects 7 to 12, wherein the CSI report including the indication is transmitted based at least in part on multiplexing the CSI report with other CSI reports or uplink control information (UCI) on the same uplink channel or at least in part on not multiplexing the CSI report with other CSI reports or UCI on the same uplink channel.

[0171] Aspect 14: A method for wireless communication performed by a network node, the method comprising: receiving a channel state information (CSI) report including a user equipment (UE) side beam prediction result, wherein the CSI report includes an indication that the UE side beam prediction result will be ignored or considered invalid at least in part based on a criterion that the UE side beam prediction result satisfies; and performing scheduling in the absence of the UE side beam prediction result at least in part based on the indication.

[0172] Aspect 15: According to the method of aspect 14, the CSI report includes one or more additional bits to indicate that the UE-side beam prediction result will be ignored or considered invalid.

[0173] Aspect 16: According to the method of aspect 15, wherein the one or more additional bits are binary indicators based on a single bit without any indication of the criterion, or the one or more additional bits include a plurality of bits having an indication of the criterion.

[0174] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the CSI report includes one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid.

[0175] Aspect 18: The method according to aspect 17, wherein the CSI report includes a measurement payload or resource identifier payload having the one or more reserved bits.

[0176] Aspect 19: According to the method of aspect 17, wherein the one or more reserved bits are associated with a Synchronization Block Resource Indicator (SSBRI) report component, a Channel State Information Reference Signal Resource Indicator (CRI) report component, or a Virtual Resource Indicator (VRI) report component.

[0177] Aspect 20: The method according to any one of Aspects 14 to 19, wherein the CSI report including the indication is received based at least in part on the multiplexing of the CSI report with other CSI reports or uplink control information (UCI) on the same uplink channel or at least in part on the not multiplexing of the CSI report with other CSI reports or UCI on the same uplink channel.

[0178] Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 13.

[0179] Aspect 22: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 13.

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

[0181] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 13.

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

[0183] Aspect 26: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 13.

[0184] Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 13.

[0185] Aspect 28: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 14 to 20.

[0186] Aspect 29: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 14 to 20.

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

[0188] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the methods described in one or more of aspects 14 to 20.

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

[0190] Aspect 33: A device for wireless communication, the device comprising: a processing system including one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 14 to 20.

[0191] Aspect 34: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 14 to 20.

[0192] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0193] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0194] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0195] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0196] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0197] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors coupled to one or more memories, the one or more processors being capable of operating individually or in any combination to enable the device to: The UE-side beam prediction result meets the criteria at the time of Channel State Information (CSI) reporting. as well as CSI reports including the UE-side beam prediction results are discarded, at least in part, based on the UE-side beam prediction results meeting the criteria.

2. The apparatus of claim 1, wherein the CSI report is discarded at least in part based on the fact that the CSI report is not multiplexed with other CSI reports or other types of uplink control information (UCI) on the same uplink channel.

3. The apparatus of claim 1, wherein the criteria for discarding the CSI report are standard-predefined, network-signaled, or determined at the UE.

4. The apparatus of claim 1, wherein the criterion is related to the measurement or prediction. K The threshold for the UE prediction confidence level of each resource is associated with the following: K is a positive integer.

5. The apparatus of claim 1, wherein the one or more processors are capable of operating individually or in any combination to cause the apparatus to: The instruction for the criteria associated with discarding the CSI report is received via network signaling, wherein the instruction is received via CSI report settings, CSI-associated report configuration information, or a Media Access Control (MAC-CE) element that activates the CSI report.

6. The apparatus of claim 1, wherein the one or more processors are capable of operating individually or in any combination to cause the apparatus to: Instructions for the criteria associated with discarding the CSI report are sent via UE Capability Report, Radio Resource Control (RRC) message, or Media Access Control Control Element (MAC-CE).

7. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors coupled to one or more memories, the one or more processors being capable of operating individually or in any combination to enable the device to: At the time of Channel State Information (CSI) reporting, indicate that the UE-side beam prediction result meets the criteria; and Send a CSI report including the UE-side beam prediction results, wherein the CSI report includes an indication that the UE-side beam prediction results will be ignored or considered invalid at least in part based on the UE-side beam prediction results meeting the criteria.

8. The apparatus of claim 7, wherein the CSI report includes one or more additional bits to indicate that the UE-side beam prediction result will be ignored or considered invalid.

9. The apparatus of claim 8, wherein the one or more additional bits are binary indications based on a single bit without indication of the criterion, or the one or more additional bits comprise a plurality of bits having indication of the criterion.

10. The apparatus of claim 7, wherein the CSI report includes one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid.

11. The apparatus of claim 10, wherein the CSI report includes a measurement payload or resource identifier payload having the one or more reserved bits.

12. The apparatus of claim 10, wherein the one or more reserved bits are associated with a Synchronization Block Resource Indicator (SSBRI) report component, a Channel State Information Reference Signal Resource Indicator (CRI) report component, or a Virtual Resource Indicator (VRI) report component.

13. The apparatus of claim 7, wherein the one or more processors are capable of operating individually or in any combination to cause the apparatus to: The CSI report, including the indication, is transmitted based at least in part on the fact that it is multiplexed with other CSI reports or uplink control information (UCI) on the same uplink channel, or at least in part on the fact that it is not multiplexed with other CSI reports or UCI on the same uplink channel.

14. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors coupled to one or more memories, the one or more processors being capable of operating individually or in any combination to enable the device to: Receive a Channel State Information (CSI) report including user equipment (UE) side beam prediction results, wherein the CSI report includes an indication that the UE side beam prediction results will be ignored or considered invalid at least in part based on the UE side beam prediction results meeting a criterion; as well as Scheduling is performed, at least in part, based on the indication in the absence of the UE-side beam prediction result.

15. The apparatus of claim 14, wherein the CSI report includes one or more additional bits to indicate that the UE-side beam prediction result will be ignored or considered invalid.

16. The apparatus of claim 15, wherein the one or more additional bits are binary indications based on a single bit without indication of the criterion, or the one or more additional bits comprise a plurality of bits having indication of the criterion.

17. The apparatus of claim 14, wherein the CSI report includes one or more reserved bits for indicating that the UE-side beam prediction result will be ignored or considered invalid.

18. The apparatus of claim 17, wherein the CSI report includes a measurement payload or resource identifier payload having the one or more reserved bits.

19. The apparatus of claim 17, wherein the one or more reserved bits are associated with a Synchronization Block Resource Indicator (SSBRI) report component, a Channel State Information Reference Resource Indicator (CRI) report component, or a Virtual Resource Indicator (VRI) report component.

20. The apparatus of claim 14, wherein the one or more processors are capable of operating individually or in any combination to cause the apparatus to: The CSI report, including the indication, is received at least in part based on the fact that it is multiplexed with other CSI reports or uplink control information (UCI) on the same uplink channel, or at least in part based on the fact that it is not multiplexed with other CSI reports or UCI on the same uplink channel.

Images