Method for beam prediction feedback

Abstract

Example methods, systems, and techniques are disclosed for determining and transmitting beam prediction feedback, including methods of wireless communication by a user equipment (UE). An example method includes receiving (304), from a network entity, a reporting configuration to configure a beam prediction report including a beam indicator (BI), the reporting configuration configuring at least one of a set of synchronization signal block (SSB) resources or a set of channel state information reference signal (CSI-RS) resources for channel measurement. The method further includes receiving (306), from the network entity, one or more transmission occasions of the at least one of the set of SSB resources or the set of CSI-RS resources based on the reporting configuration. The method further includes transmitting (310) the beam prediction report including the BI predicted based on the one or more transmission occasions and a validation procedure associated with the beam prediction report.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically to reporting information used for beamforming. Background Technology

[0002] This background description is provided for the purpose of presenting the general context of this disclosure. With respect to the work described in this background section, the work of the currently named inventors, and the descriptions that may not be otherwise considered prior art at the time of filing, are neither expressly nor impliedly acknowledged as prior art to this disclosure.

[0003] Network entities can configure user equipment (UE) reports to report channel state information (CSI). In a CSI report, the UE can send at least one of the following to the network entity: a rank indicator (RI), a precoder matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI). RI and PMI indicate the digital precoder. CQI indicates the signal-to-interference-plus-noise (SINR) state to assist the network entity in determining the modulation and coding scheme (MCS). LI identifies the strongest layer of the reported precoder, as indicated by RI and PMI.

[0004] When reporting CSI via a long Physical Uplink Control Channel (PUCCH) (e.g., a PUCCH with 4 or more symbols) or a Physical Uplink Shared Channel (PUSCH), the UE transmits the RI and CQI of the first codeword in CSI Part 1 and the remaining components of the CSI report in CSI Part 2. The payload size of the CSI component in CSI Part 1 is typically fixed, while the payload size of the CSI component in CSI Part 2 may vary depending on the value of the RI reported in CSI Part 1.

[0005] The network entity can also configure CSI reporting for the UE to report the Layer 1 Reference Signal Received Power (L1-RSRP) or Layer 1 Signal-to-Interference-plus-Noise Ratio (L1-SINR) of one or more Synchronization Block (SSB) resources or Channel State Information Reference Signal (CSI-RS) resources. The UE reports the SSB Resource Index Indicator (SSBRI) or CSI-RS Resource Indicator (CRI) and the corresponding L1-RSRP or L1-SINR in CSI Part 1.

[0006] Currently, UEs report RI, PMI, CQI, and LI based on actual measurements of signals transmitted from network entities (such as SSB or CSI-RS measurements). Therefore, existing CSI reporting configurations may not be able to include beam prediction information or properly allow UEs to send beam prediction feedback. Summary of the Invention

[0007] This disclosure provides methods, systems, and techniques for beam prediction feedback using machine learning (ML) or artificial intelligence (AI) based models to report channel state information (CSI). Beamforming allows for the transmission and reception of signals / channels in specific directions that enhance and / or optimize signal quality and strength. A network entity may transmit multiple synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RS) via multiple beams (e.g., beam scanning). A user equipment (UE) measures the signal quality of the received beams based on the SSBs or CSI-RS and reports the measurement results (e.g., feedback) to the network entity. The network entity may select the optimal beam based on the feedback from the beam measurements. This disclosure provides methods for beam prediction feedback in the spatial or temporal domain, such that the UE measures a subset of all beams from the network entity when predicting the optimal beam to be used between the network entity and the UE.

[0008] According to a general aspect of this disclosure, a method for wireless communication performed by a user equipment (UE) includes: receiving a report configuration from a network entity to configure a beam prediction report including a beam indicator (BI), the report configuration configuring at least one of a synchronization signal block (SSB) resource set or a channel state information reference signal (CSI-RS) resource set for channel measurement. The UE receives one or more transmission opportunities from the network entity based on the report configuration for at least one of the SSB resource set or CSI-RS resource set. The UE selectively transmits a beam prediction report including a BI predicted based on one or more transmission opportunities and a verification process associated with the beam prediction report.

[0009] In all aspects, the UE sends a message to the network entity indicating at least one of the following capabilities of the UE: beam prediction in the spatial domain; beam prediction in the temporal domain and the supported window length for beam prediction in the temporal domain; joint beam prediction in both the spatial and temporal domains; reporting at least one of the following: predicted reference signal received power (P-RSRP), beam probability indicator (BPI), confidence indicator (CI), the maximum number of supported predicted beams for the spatial domain, or the maximum number of supported predicted beams for the temporal domain; the maximum number of SSB or CSI-RS resource sets reported per beam prediction; or the maximum number of beam reporting configurations.

[0010] In all respects, the report configuration is based on at least one of the following to configure SSB resources or CSI-RS resources: the same time-domain behavior; the same serving cell index; the same periodicity; burst periodicity; or the same periodicity in burst transmissions.

[0011] In all respects, the report configures a subset of SSB resources or CSI-RS resources that share at least one of the following quasi-co-located (QCL) parameters: average delay; delay spread; Doppler spread; Doppler shift; spatial reception parameters; average gain; antenna port; or beam identifier.

[0012] In all aspects, the report configuration further configures the time constraints for channel measurements, where one or more transmission opportunities are determined based on time constraints.

[0013] In all respects, the verification process is based on at least one of the following: the number of actual received transmission opportunities for the SSB resource set or CSI-RS resource set; discontinuous reception (DRX) configuration; predicted time slots for beam prediction; time slots for transmitting beam prediction reports; minimum processing delay for beam prediction reports; number of occupied CSI processing units (CPUs); number of occupied extended CPUs (eCPUs); maximum number of CPUs; or maximum number of eCPUs.

[0014] In all aspects, the UE determines the priority of the beam prediction report and the corresponding priority of other types of reports to be sent to network entities; and sends the beam prediction report based on the priority rules between the beam prediction report and other types of reports.

[0015] In some cases, the UE reuses one or more beam prediction reports and other types of reports based on the priority of the beam prediction report and the corresponding priority of other types of reports.

[0016] In all aspects, the UE detects a time-domain conflict between a beam prediction report and a sounding reference signal (SRS) on a Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) transmission; and in response to the detection of a conflict, discards the beam prediction report or SRS based on priority rules.

[0017] In all aspects, the UE receives reference transmission power from network entities and calculates the predicted reference signal received power (P-RSRP) for the predicted beam based on that reference transmission power.

[0018] In all respects, the beam prediction report further includes at least one of the following: the number of predicted beams; one or more predicted time slots; the BI for each of the predicted beams; one or more P-RSRPs for a subset or all of the predicted beams; one or more beam probability indicators (BPIs) for a subset or all of the predicted beams; or one or more confidence indicators (CIs) for a subset or all of the predicted beams.

[0019] In all respects, selectively transmitting a beam prediction report includes at least one of the following: using CSI Part 1 on a PUCCH or PUSCH to carry the beam prediction report; using one or more PUCCH resources to carry the beam prediction report; or using CSI Part 1 on a PUCCH or PUSCH to carry a first portion of the beam prediction report and using CSI Part 2 on a PUCCH or PUSCH to carry a second portion of the beam prediction report.

[0020] According to a general aspect of this disclosure, a method for wireless communication performed by a network entity includes: sending a report configuration to a UE to configure a beam prediction report including a BI, the report configuration configuring at least one of an SSB resource set or a CSI-RS resource set for channel measurement. The network entity then sends one or more transmission opportunities of at least one of the SSB resource set or CSI-RS resource sets to the UE. The network entity receives the beam prediction report, which includes a BI predicted based on the one or more transmission opportunities and a verification process associated with the beam prediction report.

[0021] In all aspects, the report configuration further configures the time constraints for channel measurements, where one or more transmission opportunities are determined based on time constraints.

[0022] In all respects, the beam prediction report includes at least one of the following information: the number of predicted beams; one or more predicted time slots; the BI for each of the predicted beams; one or more P-RSRPs for a subset or all of the predicted beams; one or more beam probability indicators (BPIs) for a subset or all of the predicted beams; or one or more confidence indicators (CIs) for a subset or all of the predicted beams.

[0023] According to a general aspect of this disclosure, an apparatus includes one or more radio frequency (RF) modems; a processor coupled to the one or more RF modems; and at least one memory storing executable instructions. These executable instructions manipulate the processor or at least one of the one or more RF modems to perform the methods discussed in detail herein. Attached Figure Description

[0024] Figure 1 A diagram of a wireless communication system according to various aspects of this disclosure is shown, the system including multiple user equipment (UEs) and network entities communicating through one or more cells.

[0025] Figure 2a An example illustration is shown of performing beam prediction in the spatial domain using a beam prediction model according to various aspects of this disclosure.

[0026] Figure 2b An example illustration is shown of performing beam prediction in the time domain using a beam prediction model according to various aspects of this disclosure.

[0027] Figure 3 Example illustrations of providing beam prediction reports according to various aspects of this disclosure are shown.

[0028] Figure 4 An example illustration of UE behavior in providing a beam prediction report is shown, according to various aspects of this disclosure.

[0029] Figure 5 An example illustration of the network entity behavior in the configuration and received beam prediction report is shown according to various aspects of this disclosure.

[0030] Figure 6a Examples of burst-based synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RS) transmissions according to various aspects of this disclosure are shown.

[0031] Figure 6b Examples of burst-like transmissions based on multiple SSB or CSI-RS resources having the same beam are shown according to various aspects of this disclosure.

[0032] Figure 7 Examples of SSB or CSI-RS measurement behavior with respect to time constraints are shown according to various aspects of this disclosure.

[0033] Figure 8a An example of beam prediction report discarding for measured transmission timing based on SSB or CSI-RS is shown according to various aspects of this disclosure.

[0034] Figure 8b Another example of beam prediction report discarding for measured transmission timing based on SSB or CSI-RS, according to various aspects of this disclosure, is shown.

[0035] Figure 9a An example of a predicted beam report based on a predicted time slot is shown according to various aspects of this disclosure.

[0036] Figure 9b Examples of predicted time slot identification based on SSB or CSI-RS transmission timing according to various aspects of this disclosure are shown.

[0037] Figure 9c An example of predicted time slot identification based on CSI reference resources according to various aspects of this disclosure is shown.

[0038] Figure 9dAnother example of predicted slot identification based on CSI reference resources according to various aspects of this disclosure is shown.

[0039] Figure 10 An example flowchart of a method performed by a UE according to aspects of this disclosure is shown.

[0040] Figure 11 An example flowchart of a method performed by a network entity according to aspects of this disclosure is shown.

[0041] Figure 12 This is a diagram illustrating the hardware implementation of an example UE device.

[0042] Figure 13 It is a diagram illustrating the hardware implementation of one or more example network entities.

[0043] The same number indicates the same component. Detailed Implementation

[0044] This disclosure provides methods, systems, and techniques for beam prediction feedback using machine learning or artificial intelligence to report channel state information (CSI). Beamforming allows for the transmission and reception of signals / channels in specific directions that enhance and / or optimize signal quality and strength. A network entity may transmit multiple synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RS) via multiple beams (e.g., beam scanning). A user equipment (UE) measures the signal quality of the received beams based on the SSBs or CSI-RS and reports the measurement results (e.g., feedback) to the network entity. The network entity may select the optimal beam based on the feedback from the beam measurements. This disclosure provides methods for beam prediction feedback in the spatial or temporal domain, such that the UE measures a subset of all beams from the network entity when predicting the optimal beam to be used between the network entity and the UE.

[0045] Reporting predicted beams can include additional information compared to traditional CSI reports. For example, a UE may calculate or predict beams based on a set of measured beams, thus requiring beam prediction reports to include additional information. For instance, in spatial domain beam prediction, a network entity transmits an SSB or CSI-RS in a first set of beams. The UE then predicts a second set of beams (potentially including the optimal beam) based on the first set. In temporal domain beam prediction, the UE predicts a new set of future beams based on previous sets of beams. When a UE reports a predicted set of beams, it may include additional information such as the predicted beam indicator (BI), predicted reference signal received power (P-RSRP), confidence indicator (CI), and beam probability indicator (BPI). Various examples of reporting such predicted beams are disclosed herein.

[0046] For example, aspects of this disclosure include methods (e.g., verification processes) for verifying that conditions for transmitting beam prediction reports make the information provided in the beam prediction reports valid. Conditions may involve SSB or CSI-RS measurement status, processing delay and scheduling offset status, CSI processing unit (CPU) status, collisions with other uplink signals, and other conditions. Furthermore, this disclosure provides calculations of the P-RSRP when network entities transmit SSB and / or CSI-RS at different power levels. This disclosure also provides methods for determining predicted time slots for time-domain beam prediction. A large number of predicted beams and / or predicted time slots can result in a large payload size for beam prediction reports. Therefore, this disclosure provides methods for transmitting such large beam prediction reports in multiple sections (e.g., CSI section 1 and / or section 2) of the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH).

[0047] The aspects of determining and transmitting beam prediction feedback disclosed herein include wireless communication methods performed by a UE. An example method includes receiving a report configuration from a network entity to configure a beam prediction report including a beam indicator (BI), the report configuration configuring at least one of a Synchronization Signal Block (SSB) resource set or a Channel State Information Reference Signal (CSI-RS) resource set for channel measurements. The method further includes receiving one or more transmission opportunities from the network entity based on the report configuration for at least one of the SSB resource set or CSI-RS resource set. The method further includes transmitting a beam prediction report including a BI predicted based on one or more transmission opportunities and a verification process associated with the beam prediction report.

[0048] A supplementary aspect of this disclosure includes an example method for configuring and receiving a beam prediction report by a network entity. This example method includes: sending a report configuration to a UE to configure a beam prediction report including a BI, the report configuration configuring at least one of an SSB resource set or a CSI-RS resource set for channel measurements. The method further includes sending one or more transmission opportunities to the UE for at least one of the SSB resource set or CSI-RS resource sets for channel measurements. The network entity then receives the beam prediction report, which includes a BI predicted based on the one or more transmission opportunities and a verification process associated with the beam prediction report.

[0049] Figure 1A diagram 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, while others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0050] The operation and / or network design of base station (BS) 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing functionality for at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations (BS) 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RU 106 and / or BS 104 can simultaneously serve UE102, such as through intra-cell and / or inter-cell access links between UE102 and RU 106 / BS 104.

[0051] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission media, such as a fronthaul link 160 between RU 106d and the baseband unit (BBU) 112 of BS 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 to transmit or receive information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) is configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and BS 104e in cell 190e via inter-cell communication beams 136 to 138 of RU 106a and BS 104e.

[0052] RU 106 can be configured to implement low-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or lower-level PHY functions such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0053] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b via a first communication beamset 132 of RU 106b and a second communication beamset 134b of UE 102b of cell 190b. The first and second communication beamsets may correspond to inter-cell communication beams, or in some examples, to inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a via a third communication beamset 134a of UE 102b and a fourth communication beamset 136 of RU 106a of cell 190a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0054] Any combination or individual reference to RU 106, DU 108, and CU 110 may correspond to BS 104. Therefore, BS 104 may include at least one of RU 106, DU 108, or CU 110. BS 104 provides UE 102 with access to the core network. BS 104 may relay communication between UE 102 and the core network (not shown). BS 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0055] Transmissions from UE 102 to BS 104 / RU 106 are called uplink (UL) transmissions, while transmissions from BS 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of BS 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and BS 104d / RU 106d.

[0056] The communication link between UE 102 and BS 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and BS 104 / RU 106 can utilize a per-carrier Y MHz spectral bandwidth (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. Carriers can be adjacent to each other along the spectrum or can be non-adjacent. In the example, uplink and downlink carriers can be allocated asymmetrically, with more or fewer carriers allocated for the uplink or downlink. Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be associated with the primary cell (Pcell), and the secondary component carrier can be associated with the secondary cell (Scell).

[0057] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems, such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0058] UE 102 and BS 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b in one or more transmit directions of RU 106b based on a first communication beam set 132. UE 102b may receive downlink beamforming signals from RU 106b in one or more receive directions of UE 102b based on a second communication beam set 134b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b in one or more transmit directions of UE 102b based on the second communication beam set 134b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b. UE 102b can perform beamforming to determine the optimal reception and transmission directions for beamforming signals. The transmission and reception directions of UE 102 and BS 104 / RU 106 can be the same or different.

[0059] In a further example, the beamforming signal can be transmitted between the first base station / RU 106a and the second BS 104e. For example, BS 104e of cell 190e can transmit the beamforming signal to RU 106a in one or more transmit directions of BS 104e based on communication beam 138. RU 106a can receive the beamforming signal from BS 104e of cell 190e in one or more receive directions of RU 106a based on RU communication beam 136. In a further example, BS 104e transmits a downlink beamforming signal to UE 102e in one or more transmit directions of BS 104e based on communication beam 138. UE 102e receives the downlink beamforming signal from BS 104e in one or more receive directions of UE 102e based on UE communication beam 130. UE 102e can also transmit uplink beamforming signals to BS 104e in one or more transmission directions of UE 102e based on UE communication beam 130, so that BS 104e can receive uplink beamforming signals from UE 102e in one or more reception directions of BS 104e.

[0060] BS 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to BS 104 or at least one element of BS 104, such as RU 106, DU 108, and / or CU 110. BS 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Entities at BS 104 may be implemented as IAB nodes, relay nodes, sidelink nodes, aggregated (monolithic) base stations, or decomposed base stations including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with BS 104e and base station / RU 106a. In such cases, BS 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0061] Uplink / downlink signaling can also be transmitted via a Satellite Positioning System (SPS) 114. In the example, the SPS 114 associated with cell 190c can communicate with one or more UEs 102 (such as UE 102c) and one or more BS 104 / RU 106 (such as RU 106c). The SPS 114 can correspond to one or more of the Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or other satellite positioning / location systems. The SPS114 can be associated with LTE signals, NR signals (e.g., based on round-trip time (RTT) and / or multiple RTT), wireless local area network (WLAN) signals, terrestrial beacon systems (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) technology, downlink angle of departure (DL-AoD), downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL-TDOA), uplink angle of arrival (UL-AoA), and / or other systems, signals, or sensors.

[0062] exist Figure 1 In this configuration, any of UEs 102 may include a beam prediction reporting component 140 configured to receive a report configuration from network entity 104 to configure a beam prediction report including a BI, the report configuration configuring at least one of an SSB resource set or a CSI-RS resource set for channel measurement. The beam prediction reporting component 140 is further configured to receive one or more transmission opportunities from the network entity based on the report configuration for at least one of the SSB resource set or CSI-RS resource sets. The beam prediction reporting component 140 selectively transmits a beam prediction report including a BI predicted based on one or more transmission opportunities and a verification process associated with the beam prediction report. BS 104 includes a report configuration component 150 configured to perform complementary operations to the example methods described herein with the beam prediction reporting component 140.

[0063] therefore, Figure 1 A wireless communication system is described, which can be implemented in conjunction with aspects of one or more other accompanying figures described herein. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0064] Figure 2aAn example illustration 200 is shown illustrating the use of a beam prediction model to perform beam prediction in the spatial domain according to various aspects of this disclosure. As shown, a network entity can use various beams 215 to transmit SSBs or CSI-RS. The UE measures a first set of beams 210. Based on the beam measurements, the UE can use a prediction model 220 (e.g., a trained machine learning model) to predict a second set of beams 230, which may include the optimal beams different from the actually measured beams 210. For example, to identify the optimal network beams, measurements of the first set of network beams 210, such as four beams associated with four SSBs or CSI-RS (e.g., L1-RSRP), are used as input to the prediction model 220.

[0065] Prediction model 220 calculates or predicts a second set of network beams 230 with the highest probability of being the optimal beam (e.g., signal quality and strength between the network entity and the UE). In some cases, the UE may include dedicated hardware (e.g., an ML / AI processing unit) to perform prediction model 220. In other cases, the UE may utilize external resources (e.g., remote hardware connected to the UE) to perform prediction model 220. When predicting the second set of network beams 230, the UE may perform a second-step beam measurement (not shown) based on the predicted second set of network beams 230 to identify the optimal network beam.

[0066] The SSB includes a set of signals used for initial access and may include a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). The SSB allows the UE to synchronize with the network in time and frequency, identify the cell, and obtain essential system information required for network access. In some cases, the network may perform periodic transmissions of the SSB in bursts. The CSI-RS includes a set of reference signals used by the UE to measure channel quality and report the measurements to network entities. Based on the measurement reports, network entities determine the channel conditions to a particular UE and may adjust or select transmission parameters for communicating with that particular UE. In this disclosure, the SSB and CSI-RS (e.g., referred to as SSB / CSI-RS) are used as examples, but other signals may also be used (e.g., in various configuration, measurement, and reporting examples) for synchronization or channel measurements.

[0067] In some embodiments, beam prediction using machine learning (ML) or artificial intelligence (AI) improves network efficiency by proactively adjusting beamforming and predicting optimal beam paths based on the effects of the environment on signal propagation, such as reflections, diffraction, and scattering caused by buildings, terrain, and other obstacles. Prediction model 220 may take into account environmental modeling, CSI, UE mobility prediction, beam manipulation and management, and other variables. Prediction model 220 may include a pre-trained ML / AI model that continuously collects and updates environmental data, CSI, and UE mobility information. In some cases, prediction model 220 may implement feedback mechanisms based on actual measurements to evaluate, validate, refine, improve, or update the prediction information.

[0068] Figure 2b An example illustration of beam prediction in the time domain using a beam prediction model according to various aspects of this disclosure is shown. As shown, a network entity can transmit SSB or CSI-RS from time slot n-sS (or "n-s_S") 240 to time slot n-s1 (or "n-s_1") 245 using various beams 215. For each time slot, the UE measures a first set of beams 210 for time slot 240 and a first set of beams 215 for time slot 245. Based on the beam measurements, the UE can use a prediction model 225 (e.g., a trained ML / AI model) to predict a corresponding second set of beams 250 for time slot n+q1 (or "n+q_1") 260, and a second set of beams 255 for time slot n+qQ (or "n_q_Q") 265, as well as the time slots in between. For example, to identify the optimal network beam in the time domain, measurement results (e.g., L1-RSRP of beams in the first set of past time instances, such as beam reports in time slots n-sS 240, n-sS-1, ..., n-s1 245), and ML models can be used to predict beams in the second set of future time instances, such as the predicted sets of beams 250 and 255 in future time slots n+q1 260, n+q2, ..., n+qQ 265 (as well as other unlabeled beams).

[0069] In some embodiments, using ML or AI for beam prediction in the time domain can leverage historical data and predictive analytics. When compared to non-time-domain beam prediction models (e.g., spatial domain only), the prediction model 225 for time-domain beam prediction can emphasize the availability and quality of historical data. Time-domain beam prediction can adapt to changes in UE behavior, network configuration, physical obstacles, and other dynamic factors that change over time.

[0070] Based on spatial and / or temporal beam prediction, a UE can report predicted beam information for K beams (e.g., K and X are variable integers) across X time slots. The beam information may include at least one of the following: a beam identifier or beam indicator (BI); a predicted RSRP (P-RSRP); a beam probability indicator (BPI) indicating the probability that the beam is the optimal beam; and a confidence indicator (CI) indicating the possible prediction error of the P-RSRP. Existing specifications do not specify how this beam prediction information can be transmitted from the UE to network entities. This disclosure provides methods and solutions for transmitting beam prediction reports or feedback from the UE to network entities to achieve beamforming utilizing ML or AI.

[0071] Figure 3 Example illustration 300 of providing a beam prediction report according to various aspects of this disclosure is shown. As shown, UE 102 may optionally send 302 UE capabilities to network entity 104, indicating supported configurations for the beam prediction report. In some cases, the beam prediction report may be a CSI report (or a variant or derivative thereof) that includes beam prediction information. For example, the UE may send at least one of the following UE capabilities to network entity 104: whether UE 102 supports beam prediction reports based on spatial domain beam prediction; whether UE 102 supports beam prediction reports based on temporal domain beam prediction; whether UE 102 supports beam prediction reports based on joint spatial and temporal domain beam prediction; whether UE 102 supports P-RSRP / BPI / CI reporting; the maximum number of predicted beams supported for spatial and / or temporal domain beam prediction; the supported predicted window length for temporal domain beam prediction; the maximum number of SSB or CSI-RS resources configured for each CSI report for beam prediction; and the maximum number of CSI reports configured for beam prediction.

[0072] Based on UE capabilities, network entity 104 sends 304 control signaling to configure at least one beam prediction report configuration in UE 102. For example, the control signaling may be Radio Resource Control (RRC) signaling (e.g., RRCReconfiguration), which configures a CSI report configuration for the beam prediction report. The RRC signaling may configure at least one SSB / CSI-RS resource set as a Channel Measurement Resource (CMR). Network entity 104 may optionally configure timing measurement constraints between the beam prediction report and another uplink signal, a predicted time slot identification scheme, and / or a collision handling scheme via control signaling.

[0073] Network entity 104 sends 306 SSB / CSI-RS resource to UE 102 for channel measurement. The SSB / CSI-RS resource for channel measurement can be sent at one or more transmission times. For semi-persistent or aperiodic beam prediction reports, network entity 104 can further send 308 Media Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI), which triggers CSI report configuration for beam prediction reporting.

[0074] UE 102 transmits a 310 beam prediction report via the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH) based on one or more transmission timings received from SSB / CSI-RS resources used for channel measurements, CPU occupancy status, and conflict handling with another signal.

[0075] Figure 4 An example illustration 400 of UE behavior in providing beam prediction reports according to various aspects of this disclosure is shown. As shown, the UE may optionally send 402 indicating UE capabilities for supported configurations of beam prediction reporting. The UE receives 404 control signaling configuring at least one beam prediction reporting configuration, which includes at least one set of SSB / CSI-RS resources for channel measurement. The control signaling may optionally configure time measurement constraints, predicted time slot identification schemes, and / or collision handling schemes between the beam prediction report and another uplink signal. The UE receives 406 SSB / CSI-RS for channel measurement. In some cases, the UE may optionally receive 408 triggering MAC CE or DCI for the CSI report configuration configured for beam prediction reporting. Based on one or more transmission timings received for the SSB / CSI-RS resources for channel measurement, CPU occupancy status, and / or collision handling with another signal, the UE sends 410 beam prediction reports to the network entity via PUCCH or PUSCH.

[0076] Figure 5 Example illustration 500 shows the behavior of network entities in configuration and receive beam prediction reports according to various aspects of this disclosure. Network entity behavior and... Figure 4The illustrated UE behavior corresponds to this. As shown, the network entity may optionally receive 502 indicating the UE capability for supported configurations used in beam prediction reporting. The network entity sends 504 control signaling to configure at least one beam prediction reporting configuration, which includes at least one set of SSB / CSI-RS resources for channel measurement. The control signaling may optionally configure time measurement constraints, predicted time slot identification schemes, and / or collision handling schemes between the beam prediction report and another uplink signal. The network entity sends 506 SSB / CSI-RS for channel measurement to the UE. In some cases, the network entity may optionally send 508 to trigger MAC CE or DCI for the CSI report configuration used in the beam prediction report configuration. The network entity receives 510 beam prediction reports from the UE regarding PUCCH or PUSCH. The beam prediction report is generated based on one or more transmission timings of the SSB / CSI-RS resources used for channel measurement, CPU occupancy status, and / or collision handling with another signal.

[0077] In this disclosure, unless otherwise stated, RRC signaling may indicate an RRC reconfiguration message from a network entity to the UE, or a System Information Block (SIB), where the SIB may be an existing SIB (e.g., SIB1) or a new SIB transmitted by the network entity (e.g., SIB J, where J is an integer greater than 21). In some implementations, the network entity receives UE capabilities from the core network (e.g., the Access and Mobility Management Function (AMF)). In still other implementations, the network entity receives UE capabilities from another network entity (e.g., a gNB or eNB).

[0078] Figure 6aAn example 600 of burst-based SSB or CSI-RS transmission according to various aspects of this disclosure is illustrated. As shown, network entity 104 transmits a first SSB / CSI-RS 610 based on a first beam and a second SSB / CSI-RS 620 based on a second beam to a UE. Network entity 104 can configure at least one of the following for burst-based SSB or CSI-RS transmission: burst periodicity 640, periodicity / interval 630, slot offset for each SSB or CSI-RS within a burst, and / or duration of each burst. The network entity can configure an on duration for the SSB or CSI-RS, which configures when network entity 104 transmits the SSB or CSI-RS. Thus, the UE can monitor or receive the SSB or CSI-RS during the on duration. Network entity 104 can configure a off duration for the SSB or CSI-RS, which configures when network entity 104 does not transmit the SSB or CSI-RS. Therefore, the UE does not monitor or receive SSB or CSI-RS during the off duration, and can determine that resource elements or resource blocks used for SSB or CSI-RS during the off duration are available for rate matching of the Physical Downlink Control Channel (PDCCH) and / or Physical Downlink Shared Channel (PDSCH). Network entity 104 can configure such burst-based SSB or CSI-RS resources for time-domain beam prediction.

[0079] exist Figure 6a In Example 600, network entity 104 can configure a set of SSB or CSI-RS resources for channel measurements in the CSI report configuration for beam prediction reporting. Network entity 104 can configure the SSB or CSI-RS resources based on the same temporal behavior and / or periodicity. Network entity 104 can transmit the SSB or CSI-RS resources over Q time slots. Q can be predefined, for example, Q=2. Alternatively, Q can be reported by UE capabilities. Network entity 104 can transmit the SSB or CSI-RS resources on the same serving cell or different serving cells.

[0080] Figure 6b Example 650 of a burst-like transmission based on multiple SSB or CSI-RS resources having the same beam, according to various aspects of this disclosure, is shown. In example 650, compared to example 600, the transmission based on each of the first and second beams includes multiple SSB / CSI-RS resources, such as three SSB / CSI-RS 652, 656, and 660 for transmission based on the first beam, and three SSB / CSI-RS 654, 658, and 662 for transmission based on the second beam.

[0081] In Example 650, network entity 104 configures multiple SSB / CSI-RS resources based on the same antenna port, beam, beam ID, or QCL parameters, including one or more of average delay, delay spread, Doppler spread, Doppler shift, spatial reception parameters, or average gain. The UE can then measure the L1-RSRP of a beam based on the multiple SSB / CSI-RS resources (e.g., 652, 656, and 660). Network entity 104 can then transmit reference signals with different beams in a burst-like structure. Similar to Example 600, network entity 104 can configure burst periodicity 640, periodicity / interval 630, and slot offset for each SSB or CSI-RS within a burst. Network entity 104 can configure such burst-based SSB or CSI-RS resources for time-domain beam prediction.

[0082] Figure 7 Example 700 of time-limited SSB or CSI-RS measurement behavior according to various aspects of this disclosure is shown. In some implementations, network entity 104 may configure a time limit for channel measurements, such as timeRestrictionForChannelMeasurements, in a configuration for beam prediction reporting (e.g., CSI report configuration). If the higher-layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to “notConfigured”, the UE will derive the channel measurements for calculating the beam prediction reported in uplink slot n based solely on the SSB or non-zero power (NZP) CSI-RS associated with the CSI resource settings and no later than the CSI reference resource. If the higher-layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE should derive the channel measurements used to calculate the beam prediction reported in uplink slot n based only on the most recent Y timings of the SSB or NZP CSI-RS associated with the CSI resource settings, no later than the CSI reference resource.

[0083] like Figure 7As shown in Example 700, the network entity configures a time restriction 730 for SSB / CSI-RS regarding measurements used for beam prediction. When Y=2, the UE receives SSB / CSI-RS 710 and 715 for measurements regarding the time restriction. In contrast, without a time restriction, the UE can use a longer time period 740 of SSB / CSI-RS for beam prediction measurements. For example, network entity 104 can avoid configuring the time restriction for channel measurements (e.g., timeRestrictionForChannelMeasurements) as "configured" or "notConfigured" in the CSI report configuration for beam prediction reporting. Therefore, the UE may not expect network entity 104 to configure timeRestrictionForChannelMeasurements as "configured" or "notConfigured" in the CSI report configuration for beam prediction reporting. In some other implementations, the UE can ignore the configuration of the time restriction for channel measurements in the CSI report configuration for beam prediction reporting. Following CSI reference resource 720, the UE sends beam prediction report 725.

[0084] Figure 8a Example 800 of beam prediction report discarding for measured transmission timing based on SSB or CSI-RS is illustrated according to various aspects of this disclosure. As shown, after CSI report (re)configuration, serving cell activation, BWP change, or SP-CSI activation, the UE only reports a beam prediction report (e.g., a CSI report for beam prediction feedback) – for example, having a reportQuantity including at least BI – for example, when DRX is configured, after receiving at least M SSB or CSI-RS transmission timings for each SSB or CSI-RS resource for channel measurement no later than the CSI reference resource and within the discontinuous reception (DRX) activity time 830. Otherwise, the report is discarded. Figure 8a As shown in Example 800, if the number of SSB or CSI-RS transmission opportunities is greater than one (e.g., CSI-RS resources 810 and 815 during DRX active time 830, and excluding CSI-RS resources 812 and 817 during DRX inactive time 840), then beam prediction report 825 is discarded; otherwise, beam prediction report 825 is sent.

[0085] In some embodiments, if the UE receives at least M transmission opportunities for each SSB / CSI-RS resource 810 and 815 before CSI reference resource 820, the UE may send a beam prediction report 825. Otherwise, if the UE does not receive at least M transmission opportunities, the UE may discard the beam prediction report 825 or send an outdated beam prediction report 825.

[0086] In some embodiments, the value of M may be predefined, for example, M=1. In some embodiments, the value of M may be reported by the UE capability or configured by network entity 104. In some embodiments, the UE may determine the value of M based on the type of beam prediction report, such as whether the beam prediction report is for future time slots, or whether the beam prediction report is based on time-domain beam prediction or spatial-domain beam prediction. In this case, if the beam prediction report is for future time slots, the UE may determine a first value of M, and if the beam prediction report is not for future time slots, the UE may determine a second value of M. The first and / or second values ​​may be predefined, reported by the UE capability, or configured by the network entity.

[0087] Figure 8b Example 850 of beam prediction report discarding based on measured transmission timings of SSB or CSI-RS and the offset between the last transmission timing and the beam prediction report is illustrated according to various aspects of this disclosure. As shown, compared to Example 800, an offset 842 between the second CSI-RS resource 815 and the beam prediction report 825 during DRX activity time 830 is shown. In Example 850, if the UE receives at least M transmission timings for each SSB / CSI-RS resource 810 or 815 before CSI reference resource 820, and the offset 842 between the last transmission timing 815 and the beam prediction report 825 does not exceed Y time slots, the UE can determine to send the beam prediction report 825; otherwise, the UE can discard the beam prediction report 825 or send an outdated beam prediction report. The value of Y can indicate the minimum beam prediction length in the time domain used for time-domain beam prediction.

[0088] In the example, after CSI report (re)configuration, serving cell activation, BWP change, or SP-CSI activation, the UE only reports a CSI report for beam prediction reporting if DRX is configured and the offset between the last transmission timing of the first or last SSB or CSI-RS and the first time slot of the PUCCH or PUSCH used for beam prediction reporting does not exceed Y time slots or milliseconds, and after receiving at least M SSB or CSI-RS transmission timings for each SSB or CSI-RS resource for channel measurement no later than the CSI reference resource and during the discontinuous reception (DRX) activity period. Otherwise, the report is discarded. In some embodiments, the value of Y may be predefined, such as 10, or may be reported by the UE capability, or configured by network entity 104, for example, based on individual parameters or periodicity of the SSB / CSI-RS.

[0089] In this embodiment, the CSI reference resource of the beam prediction report is based on the minimum delay of the beam prediction report and the first time slot of the beam prediction report.

[0090] In one example, in the time domain, the CSI reference resource used for beam prediction reporting in uplink slot n' is comprised of a single downlink slot. Definition, where It is a parameter configured by a higher layer (e.g., as specified in Clause 4.2 of the 3GPP Technical Specification (TS) 38.213), and in which yes The subcarrier spacing configuration, where the value for frequency range 1 is 0, where and and These are the subcarrier spacing configurations for DL ​​and UL, respectively. and It is determined by the ca-SlotOffset of the higher-layer configuration of the cell transmitting uplink and downlink (e.g., as defined in Clause 4.5 of 3GPP TS 38.211).

[0091] For periodic and semi-persistent CSI reports, nCSI_ref is the minimum value greater than or equal to a threshold, which can be predefined, for example... Alternatively, the threshold may be reported by the UE capability or configured by network entity 104 to correspond to a valid downlink slot.

[0092] For non-periodic CSI reporting, if the DCI instructs the UE to report the CSI in the same time slot as the CSI request, then nCSI_ref ensures that the reference resource is in the same valid downlink time slot as the corresponding CSI request; otherwise, nCSI_ref is greater than or equal to... The minimum value of is such that time slot n - nCSI_ref corresponds to the effective downlink time slot, where Z' corresponds to the delay requirement of the beam prediction report.

[0093] In some implementations, the value of Z' may be predefined or reported by the UE, or configured by network entity 104, or determined based on at least one of the following: (1) the number of measured SSB / CSI-RS resources, (2) the number of predicted beams, (3) the amount of reporting, such as whether P-RSRP is reported, or (4) the number of predicted time slots.

[0094] In some implementations, the minimum delay between the last symbol of the PDCCH that triggers the aperiodic beam prediction report and the first symbol of the PUSCH that has the triggered aperiodic beam prediction report (Z) can be determined as Z'+q, where q can be predefined or reported by the UE capability.

[0095] In some implementations, if the scheduling offset does not meet the Z or Z' requirements, the UE can report outdated beam predictions or discard beam prediction reports.

[0096] In an embodiment, the network entity and the UE may determine the number of CSI processing units (CPUs) for beam prediction reporting based on at least one of the following: a predefined value (e.g., 1), UE capability, or based on the predicted number of time slots.

[0097] Network entities and UEs can determine the number of extended CPUs (eCPUs) based on predefined values ​​(e.g., 1) or UE capabilities, or based on the predicted number of time slots and / or reported content. In some implementations, the UE can perform beam prediction for each predicted time slot based on an independent AI / ML model. In this case, the number of eCPUs can be the same as the number of predicted time slots. In other implementations, the UE can perform beam prediction for all predicted time slots based on a single AI / ML model. In this case, the number of eCPUs can be 1. In still other implementations, the UE can perform beam prediction for a subset of predicted time slots based on an independent AI / ML model. In this case, the number of eCPUs can be the number of predicted time slots multiplied by a scaling factor.

[0098] If the total number of CPUs across all CSI / L1-RSRP / L1-SINR / beam prediction reports exceeds the maximum number of CPUs, or the total number of eCPUs across all CSI / L1-RSRP / L1-SINR / beam prediction reports exceeds the maximum number of eCPUs, the UE may report outdated CSI / L1-RSRP / L1-SINR / beam predictions in a report with lower priority, or discard a report with that lower priority. In embodiments, network entities and the UE may determine the priority of CSI reports with one or more CSIs based on at least one of the following: (1) the temporal behavior of the CSI report (e.g., aperiodic, semi-persistent, or periodic); (2) the serving cell index of the SSB / CSI-RS used for channel measurements or the serving cell configured with CSI report configuration; (3) the report content, e.g., a CSI / L1-RSRP / L1-SINR / beam prediction report; or (4) the CSI report configuration identifier (ID).

[0099] In some implementations, beam prediction reports have a higher priority than L1-RSRP / L1-SINR reports and CSI reports.

[0100] In the first example, the network entity and the UE determine the priority of CSI reports as follows: if If the value is lower, the first CSI report has a higher priority than the CSI report.

[0101] CSI reports are associated with priority values.

[0102] in: For non-periodic CSI reports to be carried on PUSCH, y = 0; for semi-persistent CSI reports to be carried on PUSCH, y = 1; for semi-persistent CSI reports to be carried on PUCCH, y = 2; and for periodic CSI reports to be carried on PUCCH, y = 3. For CSI reports carrying BI, k=0; for CSI reports carrying L1-RSRP or L1-SINR, k=1; and for CSI reports not carrying L1-RSRP or L1-SINR, k=2. c is the serving cell index, and It is the value of the higher-level parameter maxNrofServingCells; for CSI reports configured with LTM-CSI-ReportConfig, c is the serving cell index value configured in the report configuration. s is the reportConfigID, and MS is the value of the higher-level parameter maxNrofCSI-ReportConfigurations for CSI reports configured with CSI-ReportConfig. For CSI reports configured with LTM-CSI-ReportConfig, s is the LTM-CSI-ReportConfigID, and Ms is the value of the higher-level parameter maxNrofLTM-CSI-ReportConfigurations.

[0103] In some other implementations, beam prediction reports have the same priority as L1-RSRP / L1-SINR reports.

[0104] In the second example, the network entity and the UE determine the priority of CSI reports as follows: if If the value is lower, the first CSI report has a higher priority than the CSI report.

[0105] CSI reports are associated with priority values.

[0106] in

[0107] For non-periodic CSI reports to be carried on PUSCH, y = 0; for semi-persistent CSI reports to be carried on PUSCH, y = 1; for semi-persistent CSI reports to be carried on PUCCH, y = 2; and for periodic CSI reports to be carried on PUCCH, y = 3. For CSI reports carrying L1-RSRP, L1-SINR, or BI, k = 0, and for CSI reports not carrying L1-RSRP or L1-SINR, k = 1; c is the serving cell index, and It is the value of the higher-level parameter maxNrofServingCells; for CSI reports configured with LTM-CSI-ReportConfig, c is the serving cell index value configured in the report configuration. s is the reportConfigID, and MS is the value of the higher-level parameter maxNrofCSI-ReportConfigurations for CSI reports configured with CSI-ReportConfig. For CSI reports configured with LTM-CSI-ReportConfig, s is the LTM-CSI-ReportConfigID, and Ms is the value of the higher-level parameter maxNrofLTM-CSI-ReportConfigurations.

[0108] In some other implementations, beam prediction reports have the same priority as CSI reports.

[0109] In the third example, the network entity and the UE determine the priority of CSI reports as follows: if If the value is lower, the first CSI report has a higher priority than the CSI report.

[0110] CSI reports are associated with priority values.

[0111] in

[0112] For non-periodic CSI reports to be carried on PUSCH, y = 0; for semi-persistent CSI reports to be carried on PUSCH, y = 1; for semi-persistent CSI reports to be carried on PUCCH, y = 2; and for periodic CSI reports to be carried on PUCCH, y = 3. For CSI reports carrying L1-RSRP or L1-SINR, k = 0, and for CSI reports not carrying L1-RSRP or L1-SINR, k = 1; c is the serving cell index, and It is the value of the higher-level parameter maxNrofServingCells; for CSI reports configured with LTM-CSI-ReportConfig, c is the serving cell index value configured in the report configuration. s is the reportConfigID, and MS is the value of the higher-level parameter maxNrofCSI-ReportConfigurations for CSI reports configured with CSI-ReportConfig. For CSI reports configured with LTM-CSI-ReportConfig, s is the LTM-CSI-ReportConfigID, and Ms is the value of the higher-level parameter maxNrofLTM-CSI-ReportConfigurations.

[0113] In some other implementations, beam prediction reports have a lower priority than CSI reports.

[0114] In the fourth example, the network entity and the UE determine the priority of CSI reports as follows: if If the value is lower, the first CSI report has a higher priority than the CSI report.

[0115] CSI reports are associated with priority values.

[0116] in

[0117] For non-periodic CSI reports to be carried on PUSCH, y = 0; for semi-persistent CSI reports to be carried on PUSCH, y = 1; for semi-persistent CSI reports to be carried on PUCCH, y = 2; and for periodic CSI reports to be carried on PUCCH, y = 3. For CSI reports carrying L1-RSRP or L1-SINR, k=0; for CSI reports not carrying L1-RSRP, L1-SINR, or BI, k=1; and for CSI reports carrying BI, k=2. c is the serving cell index, and It is the value of the higher-level parameter maxNrofServingCells; for CSI reports configured with LTM-CSI-ReportConfig, c is the serving cell index value configured in the report configuration. s is the reportConfigID, and MS is the value of the higher-level parameter maxNrofCSI-ReportConfigurations for CSI reports configured with CSI-ReportConfig. For CSI reports configured with LTM-CSI-ReportConfig, s is the LTM-CSI-ReportConfigID, and Ms is the value of the higher-level parameter maxNrofLTM-CSI-ReportConfigurations.

[0118] In some other implementations, beam prediction reports always have a higher or lower priority than other CSI reports. In one example, a network entity can configure beam prediction reports and other CSI reports based on different types of CSI report configurations. A network entity can configure beam prediction reports via AI-ML-CSI-ReportConfig, CSI / L1-RSRP / L1-SINR reports based on CSI-ReportConfig, and reports for lower-layer triggered mobility (LTM) based on LTM-CSI-ReportConfig.

[0119] Different priority orders can correspond to different examples. In one example, a CSI report configured with AI-ML-CSI-ReportConfig, in the event of a conflict with a CSI report configured with LTM-CSI-ReportConfig, will be prioritized regardless of... Regardless of the value, it has higher priority than all CSI reports configured with LTM-CSI-ReportConfig. In another example, CSI reports configured with AI-ML-CSI-ReportConfig, in the event of a conflict with CSI reports configured with CSI-ReportConfig, regardless of... Regardless of the value, it has a lower priority than all CSI reports configured with CSI-ReportConfig. In another example, a CSI report configured with AI-ML-CSI-ReportConfig will have lower priority than a CSI report configured with CSI-ReportConfig in the event of a conflict. Regardless of the value, it has higher priority than all CSI reports configured with CSI-ReportConfig, and in the event of a conflict with a CSI report configured with LTM-CSI-ReportConfig, it will take precedence over all other CSI reports. Regardless of the value, CSI reports configured with LTM-CSI-ReportConfig have a lower priority than all CSI reports configured with CSI-ReportConfig. In the event of a conflict between a CSI report configured with LTM-CSI-ReportConfig and a CSI report configured with CSI-ReportConfig, regardless of the value... The value indicates that the beam prediction report has higher priority than all CSI reports configured using CSI-ReportConfig. In some other implementations, the priority of beam prediction reports, CSI report configurations, and / or LTM report configurations can be configured by the network entity.

[0120] In the fifth example, the network entity and the UE determine the priority of the beam prediction report as follows: If If the value is lower, the priority of the first beam prediction report is higher than that of the beam prediction report.

[0121] CSI reports are associated with priority values.

[0122] in

[0123] For non-periodic CSI reports to be carried on PUSCH, y = 0; for semi-persistent CSI reports to be carried on PUSCH, y = 1; for semi-persistent CSI reports to be carried on PUCCH, y = 2; and for periodic CSI reports to be carried on PUCCH, y = 3. For CSI reports carrying L1-RSRP or L1-SINR, k=0; for CSI reports not carrying L1-RSRP or L1-SINR, k=1. c is the serving cell index, and It is the value of the higher-level parameter maxNrofServingCells; for CSI reports configured with LTM-CSI-ReportConfig, c is the serving cell index value configured in the report; for CSI reports configured with AI-ML-CSI-ReportConfig, c is the serving cell index value configured in the report or the serving cell index that sent the channel measurement resources. `s` is `reportConfigID`, and `MS` is the value of the higher-level parameter `maxNrofCSI-ReportConfigurations` for CSI reports configured with `CSI-ReportConfig`. For CSI reports configured with `LTM-CSI-ReportConfig`, `s` is `LTM-CSI-ReportConfigID`, and `Ms` is the value of the higher-level parameter `maxNrofLTM-CSI-ReportConfigurations`. For CSI reports configured with `AI-ML-CSI-ReportConfig`, `s` is `AI-ML-CSI-ReportConfigID`, and `Ms` is the value of the higher-level parameter `maxNrofAI-ML-CSI-ReportConfigurations`.

[0124] In an embodiment, if a first PUCCH or PUSCH with a beam prediction report conflicts with a second PUCCH or PUSCH for another CSI report in the time domain within the same serving cell, the UE may discard the one with the lower priority and transmit the one with the higher priority. The UE may determine the priority of the beam prediction report and the other CSI report based on the embodiments in the previous section.

[0125] In some implementations, if the PUCCH / PUSCH corresponds to the same UE panel, for example, the same TCI state or control resource set (CORESET) pool index, and the UE supports simultaneous multi-panel transmission, then the UE can discard one of the PUCCH / PUSCH; otherwise, the UE can send both PUCCH / PUSCH.

[0126] In an embodiment, if a first PUCCH or PUSCH with a beam prediction report conflicts with a second PUCCH or PUSCH for another CSI report in the time domain within the same serving cell, the UE can multiplex the beam prediction report and the other CSI report based on their priorities, and transmit the multiplexed report via the first or second PUCCH or PUSCH, or a third PUCCH or PUSCH configured by the network entity. The UE can determine the priority of multiplexing the beam prediction report and the other CSI report based on the embodiments in the previous section.

[0127] In some implementations, if the PUCCH / PUSCH corresponds to the same UE panel, for example, the same TCI state or control resource set (CORESET) pool index, and the UE supports simultaneous multi-panel transmission, the UE can multiplex beam prediction reports and other CSI reports on one of the PUCCH / PUSCH; otherwise, the UE can send both PUCCH / PUSCH.

[0128] In embodiments, network entities can be configured to reuse or discard CSI and beam prediction reports. In one example, the network entity can be configured to reuse CSI and beam prediction reports by configuring a list of PUCCH resources (e.g., multi-CSI-PUCCH-ResourceList). Then, when overlap occurs, the UE reuses all CSI and beam prediction reports from resources provided by multi-CSI-PUCCH-ResourceList. If network entity 104 does not configure a list of PUCCH resources (e.g., multi-CSI-PUCCH-ResourceList) for CSI and beam prediction report reuse, the UE sends the CSI or beam prediction report with the highest priority.

[0129] In an embodiment, if the first PUCCH or PUSCH with a beam prediction report conflicts with an SRS for carrier handover or a protection period (GP) of the SRS (e.g., a GP for RF return) in the time domain within the same serving cell, the UE may discard the PUCCH or SRS. The discard priority may be predefined, configured by a network entity, or determined based on the time-domain behavior of the SRS.

[0130] In one example, for PUCCH and SRS on the same carrier, the UE should not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH carrying only CSI reports, or only L1-RSRP reports, or only L1-SINR reports, or only beam prediction reports. The UE should also not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH carrying HARQ-ACK, (e.g., as defined in Clause 9.2.4 of 3GPP TS38.213) a link recovery request, and / or a scheduling request (SR), or when an aperiodic SRS is triggered to be transmitted in the same symbol as that PUCCH. In cases where an SRS is not transmitted due to overlap with a PUCCH, only the SRS symbol overlapping with the PUCCH symbol is discarded. When an aperiodic SRS is triggered to be transmitted so as to overlap with a PUCCH carrying a semi-persistent / periodic CSI report, or a semi-persistent / periodic L1-RSRP report, or an L1-SINR report, or a beam prediction report in the same symbol, the PUCCH should not be transmitted.

[0131] In another example, for PUCCH and SRS on the same carrier, the UE should not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH carrying only CSI reports, L1-RSRP reports, L1-SINR reports, and / or beam prediction reports. The UE should also not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH carrying HARQ-ACK, (e.g., as defined in Clause 9.2.4 of 3GPP TS 38.213) a link recovery request, and / or SR, or when an aperiodic SRS is triggered to be transmitted in the same symbol as that PUCCH. In cases where an SRS is not transmitted due to overlap with a PUCCH, only the SRS symbol overlapping with the PUCCH symbol is discarded. When an aperiodic SRS is triggered for transmission to overlap with a PUCCH carrying only a semi-persistent / periodic CSI report, a semi-persistent / periodic L1-RSRP report, an L1-SINR report, and / or a beam prediction report in the same symbol, the PUCCH should not be transmitted.

[0132] In another example, for PUCCH and SRS on the same carrier, the UE should not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH that does not carry HARQ-ACK, (e.g., as defined in Clause 9.2.4 of 3GPP TS 38.213) a link recovery request, or an SR. The UE should also not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH that carries HARQ-ACK, (e.g., as defined in Clause 9.2.4 of 3GPP TS 38.213) a link recovery request, and / or an SR, or when an aperiodic SRS is triggered to be transmitted in the same symbol as that PUCCH. In cases where an SRS is not transmitted due to overlap with a PUCCH, only the SRS symbol overlapping with the PUCCH symbol is discarded. When an aperiodic SRS is triggered for transmission to overlap with a PUCCH that does not carry any of the following in the same symbol: a HARQ-ACK, (e.g., as defined in Clause 9.2.4 of 3GPP TS38.213) a link recovery request, or an SR, a PUCCH should not be sent.

[0133] In another example, for PUCCH and SRS on the same carrier, the UE should not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH carrying only CSI reports, only L1-RSRP reports, or only L1-SINR reports. The UE should also not transmit SRS when a semi-persistent or periodic SRS is configured in the same symbol as a PUCCH carrying HARQ-ACK, (e.g., as defined in Clause 9.2.4 of 3GPP TS 38.213) a link recovery request, beam prediction information, and / or SR, or when an aperiodic SRS is triggered to be transmitted in the same symbol as that PUCCH. In cases where SRS is not transmitted due to overlap with a PUCCH, only the SRS symbol overlapping with the PUCCH symbol is discarded. A PUCCH should not be transmitted when an aperiodic SRS is triggered to overlap with a PUCCH carrying a semi-persistent / periodic CSI report, a semi-persistent / periodic L1-RSRP report, or an L1-SINR report in the same symbol.

[0134] In another example, the UE should discard PUCCH / PUSCH transmissions carrying only periodic / semi-persistent CSIs including CQI / PMI / L1-RSRP / L1-SINR / beam prediction information and / or SRS transmissions on carriers of serving cells in the set S(c2) configured for PUSCH / PUCCH transmissions—whenever such transmissions and SRS transmissions on carriers of serving cell c2 (including any interruptions caused by uplink or downlink RF retuning times defined by the higher-layer parameters switchingTimeUL and switchingTimeDL of SRS-SwitchingTimeNR) overlap exactly in the same symbol. The UE should discard PUSCH transmissions on carriers of serving cells in set S(c2) that carry only aperiodic CSI information including CQI / PMI / L1-RSRP / L1-SINR / beam prediction information—whenever such transmission and aperiodic SRS transmissions on carriers of serving cell c2 (including any interruptions caused by uplink or downlink RF retuning times defined by the higher-layer parameters switchingTimeUL and switchingTimeDL of SRS-SwitchingTimeNR) overlap exactly in the same symbol. (For example, as defined in Section 6.2.1.3 of 3GPP TS 38.214) Serving cell S(c2) may indicate the affected serving cell for SRS carrier handover.

[0135] In this embodiment, the UE can transmit beam prediction reports via the MAC CE. The UE can multiplex the beam prediction report MAC CE and other logical channels based on predefined or configured priorities.

[0136] In one example, the MAC CE used for beam prediction reporting has the same priority as a type of logical channel, such as the MAC CE used for buffer status reporting (BSR). Different priority orders correspond to different examples. Logical channels can be prioritized according to the following order (highest priority listed first), where references to abbreviations or acronyms are provided in 3GPP TS 38.321: MAC CE used for Cell Radio Network Temporary Identifier (C-RNTI), or data from the Uplink Common Control Channel (UL-CCCH). MAC CE for (enhanced) beam fault recovery (BFR), or for configured authorized MAC CE, or for multi-entry configuration authorized MAC CE MAC CE for sidechain configuration authorization confirmation MAC CE for Listen-Before-Speak (LBT) faults MAC CE for scheduled advance reporting MACCE for sidechain buffer status reports (SL-BSR) prioritized according to clause 5.22.1.6 MAC CE for (extended) BSRs other than those included for filling, or MAC CE for beam prediction reporting. MAC CE for (enhanced) single-entry Power Headroom Report (PHR), or MAC CE for (enhanced) multi-entry PHR. MAC CE for locating and measuring gap activation / deactivation requests MAC CE for the number of symbols to be protected MAC CE for Case-6 timing requests MAC CE for (extended) preemptive BSR MAC CE for SL-BSRs other than those prioritized according to Clause 5.22.1.6 and those included for filling. MAC CE for recommended beam indication for Integrated Access Backhaul-Multi-Hop Trunk (IAB-MT), or for desired IAB-MT PSD range, or for desired DL Tx power adjustment. Data from any logical channel, except for data from UL-CCCH. MAC CE for recommending bitrate queries MAC CE for inclusion in the BSR used for filling MAC CE for inclusion in SL-BSR for filling In another example, the MAC CE used for beam prediction reporting has a different priority than any type of logical channel. The different priority order corresponds to different examples. Logical channels should be prioritized according to the following order (highest priority listed first), where the abbreviations are defined in 3GPP TS 38.321: MAC CE for C-RNTI, or data from UL-CCCH MAC CE for (enhanced) BFR, or MAC CE for configured authorization verification, or MAC CE for multi-entry configuration authorization verification. MAC CE for sidechain configuration authorization confirmation MAC CE for LBT failure MAC CE for scheduled advance reporting MAC CE for SL-BSR prioritization under Clause 5.22.1.6 MAC CE for (extended) BSRs other than those included for filling. MAC CE for Beam Prediction Reporting MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR. MAC CE for locating and measuring gap activation / deactivation requests MAC CE for the number of symbols to be protected MAC CE for Case-6 timing requests MAC CE for (extended) preemptive BSR MAC CE for SL-BSRs other than those prioritized according to Clause 5.22.1.6 and those included for filling. MAC CE for IAB-MT recommended beam indication, or for desired IAB-MT PSD range, or for desired DL Tx power adjustment. Data from any logical channel, except for data from UL-CCCH. MAC CE for recommending bitrate queries MAC CE for inclusion in the BSR used for filling MAC CE for inclusion in SL-BSR for filling In this embodiment, network entity 104 can transmit SSB / CSI-RS resources for channel measurement based on different transmission powers. The network entity can configure the transmission power for one or more SSBs and configure the power offset between the CSI-RS and the SSB for each CSI-RS resource.

[0137] The UE can calculate P-RSRP based on the reference transmission power and the actual transmission power of the SSB / CSI-RS resources used for channel measurements. In one example, the UE can use the measured RSRP of the SSB / CSI-RS resources plus the power offset between the reference transmission power and the actual transmission power as input to the AI / ML model.

[0138] The reference transmission power can be predefined (e.g., 0 dBm or 40 dBm), or configured by a network entity (e.g., the transmission power of the SSB or one of the SSB / CSI-RS resources used for channel measurements, such as the minimum, maximum, or average transmission power of the SSB / CSI-RS resource used for channel measurements), or reported by the UE in a beam prediction report or UE capability.

[0139] In some other implementations, network entity 104 should transmit SSB / CSI-RS resources for channel measurements based on the same transmission power. Therefore, network entity 104 should configure the same transmission power for SSB / CSI-RS. The UE should then calculate the P-RSRP based on the actual transmission power of the SSB / CSI-RS. Thus, in this case, the reference transmission power is the same as the actual transmission power.

[0140] The UE can quantize and report P-RSRP based on a reference transmit power. In one example, the network entity and the UE can determine the range of P-RSRP based on the reference transmit power. The range and / or step size of P-RSRP can be predefined or configured by the network entity. The UE can report P-RSRP based on linear or non-linear quantization. In one example, the P-RSRP quantization range can be based on {reference transmit power + [-160, -64]} dBm, and the step size can be 1, 2, or 3 dB.

[0141] Figure 9a Example 900 of a beam prediction report based on predicted time slots according to various aspects of this disclosure is illustrated. In example 900, a network entity may configure one or more prediction window sizes. In other cases, one or more prediction window sizes may be predefined or reported by UE capabilities, or provided by the beam prediction report. The network entity and the UE may identify the predicted time slots based on the prediction window, reference start point, CSI reference resource, and / or beam prediction report time slots.

[0142] like Figure 9a As shown in Example 900, after receiving SSB / CSI-RS 910 and 920 and CSI reference resource 930, the UE reports predicted beam information 940 for all predicted time slots 935 and 945. In some other implementations, the UE may optionally report predicted beam information 940 for predicted time slots after CSI reference resource 930 or after the first or last beam prediction reporting time slot 935 or 945, such as... Figure 9a As shown. In some implementations, the UE may discard the report of predicted beam information 940. In some other implementations, the UE may only report the predicted beam information 940 for predicted time slot 945. In some other implementations, the UE may report the predicted beam information 940 for predicted time slots 935 and 945.

[0143] Figure 9b Example 933 of predicted time slot identification based on SSB or CSI-RS transmission timing according to various aspects of this disclosure is illustrated. In example 933, the reference starting point for determining predicted time slot 935 or 945 may be the last transmission timing of one of the SSB / CSI-RS resources 920 preceding CSI reference resource 930 (e.g., the first or last in the time domain). The last transmission timing may indicate a transmission timing in which all SSB / CSI-RS resources precede CSI reference resource 930. When DRX is configured, the last transmission timing may indicate a transmission timing in which all SSB / CSI-RS resources are within the DRX active time.

[0144] As shown in Example 933, the first predicted time slot 935 can be identified based on the last transmission timing of the first predicted window 925 and SSB / CSI-RS 920. Similarly, the second predicted time slot 945 can be identified based on the second predicted window 927 and the last transmission timing of SSB / CSI-RS 920. The UE can optionally report predicted beam information 940 for predicted time slots after CSI reference resource 930 or after the first or last beam prediction reporting time slot 935 or 945. In some implementations, the UE can discard the reporting of predicted beam information 940. In some other implementations, the UE can report only the predicted beam information 940 for predicted time slot 945. In some other implementations, the UE can report the predicted beam information 940 for both predicted time slots 935 and 945.

[0145] Figure 9c Example 960 of predicted timeslot identification based on a CSI reference resource according to various aspects of this disclosure is illustrated. In example 960, the reference starting point for determining predicted timeslot 935 or 945 may be CSI reference resource 930. As shown, instead of identifying the predicted timeslot based on the last transmission timing of the SSB / CSI-RS, as in example 933, predicted timeslots 935 and 945 are identified based on corresponding predicted windows 925 and 927 referenced relative to CSI reference resource 930.

[0146] Figure 9d Example 990 of predicted time slot identification based on CSI reference resources according to various aspects of this disclosure is illustrated. In example 990, the reference starting point for determining predicted time slot 935 or 945 may be one of the beam prediction reporting time slots, for example, the first or last time slot of beam prediction reporting 940. As a result of beam prediction and CSI multiplexing, the UE transmits beam prediction reporting 940 through a second PUCCH or PUSCH resource that is different from the first PUCCH or PUSCH configured for beam prediction reporting before multiplexing. The UE may determine the reference starting point based on the first or second PUCCH or PUSCH. As shown in example 990, predicted time slots 935 and 945 are identified or determined based on corresponding predicted windows 925 and 927 relative to the time slot reference of beam prediction reporting 940.

[0147] In some implementations, network entities can configure a reference starting point for predicted time slot identification. The network entity can transmit the configuration via RRC signaling, MAC CE, or DCI. In one example, the network entity can configure the reference starting point for periodic beam prediction reporting via RRC parameters in the CSI report configuration of beam prediction reporting. In another example, the network entity can configure the reference starting point for semi-persistent beam prediction reporting by activating the CSI report configuration for beam prediction reporting via MAC CE. In yet another example, the network entity can configure the reference starting point for aperiodic beam prediction reporting by triggering the CSI report configuration for beam prediction reporting via DCI; for example, different reference starting points may correspond to different aperiodic CSI trigger states. The UE can report UE capabilities indicating supported reference starting points and / or predicted window sizes. In some other implementations, the UE can report the reference starting point and / or predicted window size in the beam prediction report.

[0148] In an embodiment, if / when the UE is configured to transmit a beam prediction report on a long PUCCH (e.g., a PUCCH with 4 or more symbols) or PUSCH, the UE transmits the beam prediction report in CSI section 1 on the PUCCH or PUSCH. For example, the beam prediction report, including the BI of the predicted beam (and other beam prediction information), may be transmitted along with the CQI, PMI, and RI in the CSI report.

[0149] In some implementations, if the total payload size of CSI Part 1 exceeds the maximum payload size of CSI Part 1, the UE may omit the beam prediction report or another CSI report with lower priority on CSI Part 1 and transmit the remaining portion on CSI Port 1. The UE may determine the priority of omitting CSI Part 1 of the beam prediction report and the CSI report from the other CSI report based on the embodiments in the previous section.

[0150] In some implementations, the UE can report beam prediction using a single PUCCH resource. In other implementations, the UE can report beam prediction using multiple PUCCH resources, where the UE can report the same or different beam prediction information using different PUCCH resources. In one example, the UE can report beam prediction information corresponding to different predicted time slots using different PUCCH resources.

[0151] In an embodiment, if / when the UE is configured to transmit a beam prediction report on a long PUCCH (e.g., a PUCCH with 4 or more symbols) or PUSCH, the UE transmits a first portion of the beam prediction report in CSI section 1 on the PUCCH or PUSCH, and a second portion of the beam prediction report in CSI section 2 on the PUCCH or PUSCH. For example, the second portion of the beam prediction report may be transmitted along with LI, CSI-RS resource indicators, and / or interference and traffic load information.

[0152] In some implementations, the UE may transmit at least one of the following in the first part (reported in CSI Part 1): Number of predicted beams One or more predicted time slots BI of each predicted beam Should P-RSRP be reported for each or all predicted beams? Should BPI be reported for each or all predicted beams? Is CI reported for each or all predicted beams? In some other implementations, the UE may transmit at least one of the following in Part 2 (as reported in CSI Part 2): BI for each predicted beam; P-RSRP can be used for a subset or all of the predicted beams. Used for a subset or all of the predicted beams; CI used for a subset or all of the predicted beam.

[0153] The UE can report the above information for one or more predicted time slots. Although the above example uses CSI Part 1 and CSI Part 2 (e.g., provided in 3GPP TS 38.214 and other relevant technical specifications) as examples for transmitting beam prediction report information, other similar PUCCH or PUSCH uplink transmission mechanisms can be used as alternatives, replacements, or supplements to CSI Part 1 and CSI Part 2 as described.

[0154] In some implementations, if the total payload size of CSI Part 2 exceeds the maximum payload size of CSI Part 2, the UE may omit a subset or all of the lower-priority components in the second part of the beam prediction report and transmit the remaining components in CSI Part 2. The UE may divide the components in the second part into several priority groups and omit the components in the lower-priority groups.

[0155] In one example, the UE may determine that the first priority group includes at least one of the following: a first predicted beam subset or all predicted beams for a first predicted time slot subset or all predicted time slots. The UE may determine that the second priority group includes at least one of the following: a second predicted beam subset or all predicted beams for a second predicted time slot subset; a P-RSRP for a predicted beam subset or all predicted beams for a first predicted time slot subset; a BPI for a predicted beam subset or all predicted beams for a first predicted time slot subset; or a CI for a predicted beam subset or all predicted beams for a first predicted time slot subset.

[0156] The UE may determine that the third priority group includes at least one of the following: P-RSRP for a predicted beam subset or all predicted beams of the second predicted time slot subset; BPI for a predicted beam subset or all predicted beams of the second predicted time slot subset; or CI for a predicted beam subset or all predicted beams of the second predicted time slot subset.

[0157] The UE can determine the CSI omission priority of the priority group in the following order: the first priority group has the highest priority, followed by the second priority group, and then the third priority group.

[0158] Figure 10 A flowchart of a wireless communication method 1000 at the UE is shown. (Reference) Figure 1 , Figures 3 to 5 and Figure 10 The method can be executed by UE 102, UE device 1202, etc., which may include memories 1226', 1206', 1216, and may correspond to the entire UE 102 or the entire UE device 1202, or components of UE 102 or UE device 1202 (e.g., beam prediction reporting component 140) (such as wireless baseband processor 1226 and / or application processor 1206).

[0159] like Figure 10 As shown, the UE can optionally send a 1002 message indicating the UE's capabilities to the network entity (similar to...). Figure 3 and Figure 4 Operations 302 and 402). This capability includes at least one of the following: beam prediction in the spatial domain; beam prediction in the time domain and a supported window length for beam prediction in the time domain; joint beam prediction in both the spatial and time domains; reporting at least one of the following: predicted reference signal received power (P-RSRP), beam probability indicator (BPI), confidence indicator (CI), the maximum number of supported predicted beams for the spatial domain, or the maximum number of supported predicted beams for the time domain; the maximum number of SSB or CSI-RS resource sets reported per beam prediction; or the maximum number of beam reporting configurations.

[0160] The UE receives a 1004 report configuration from the network entity to configure a beam prediction report including a beam indicator (BI). This report configuration configures at least one of the Synchronization Signal Block (SSB) resource sets or Channel State Information Reference Signal (CSI-RS) resource sets used for channel measurements (similar to...). Figure 3 and Figure 4 Operations 304 and 404).

[0161] The UE receives one or more transmission opportunities from the network entity based on the report configuration of at least one of the 1006 SSB resource set or the CSI-RS resource set (similar to...). Figure 3 and Figure 4 Operations 306 and 406).

[0162] The UE selectively transmits a 1010 beam prediction report, which includes a BI (similar to) predicted based on one or more transmission timings and a verification process associated with the beam prediction report. Figure 3 and Figure 4 Operations 310 and 410).

[0163] In all aspects, the UE sends a message to the network entity indicating at least one of the following capabilities of the UE: beam prediction in the spatial domain; beam prediction in the temporal domain and the supported window length for beam prediction in the temporal domain; joint beam prediction in both the spatial and temporal domains; reporting at least one of the following: predicted reference signal received power (P-RSRP), beam probability indicator (BPI), confidence indicator (CI), the maximum number of supported predicted beams for the spatial domain, or the maximum number of supported predicted beams for the temporal domain; the maximum number of SSB or CSI-RS resource sets reported per beam prediction; or the maximum number of beam reporting configurations.

[0164] In all respects, the report configuration is based on at least one of the following to configure SSB resources or CSI-RS resources: the same time-domain behavior; the same serving cell index; the same periodicity; burst periodicity; or the same periodicity in burst transmissions.

[0165] In all respects, the report configures a subset of SSB resources or CSI-RS resources that share at least one of the following quasi-co-located (QCL) parameters: average delay; delay spread; Doppler spread; Doppler shift; spatial reception parameters; average gain; antenna port; or beam identifier.

[0166] In all aspects, the report configuration further configures the time constraints for channel measurements, where one or more transmission opportunities are determined based on time constraints.

[0167] In all respects, the verification process is based on at least one of the following: the number of actual received transmission opportunities for the SSB resource set or CSI-RS resource set; discontinuous reception (DRX) configuration; predicted time slots for beam prediction; time slots for transmitting beam prediction reports; minimum processing delay for beam prediction reports; number of occupied CSI processing units (CPUs); number of occupied extended CPUs (eCPUs); maximum number of CPUs; or maximum number of eCPUs.

[0168] In all aspects, the UE determines the priority of the beam prediction report and the corresponding priority of other types of reports to be sent to network entities; and sends the beam prediction report based on the priority rules between the beam prediction report and other types of reports.

[0169] In some cases, the UE reuses one or more beam prediction reports and other types of reports based on the priority of the beam prediction report and the corresponding priority of other types of reports.

[0170] In all aspects, the UE detects a time-domain conflict between a beam prediction report and a sounding reference signal (SRS) on a Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) transmission; and in response to the detection of a conflict, discards the beam prediction report or SRS based on priority rules.

[0171] In all aspects, the UE receives reference transmission power from network entities and calculates the predicted reference signal received power (P-RSRP) for the predicted beam based on that reference transmission power.

[0172] In all respects, the beam prediction report further includes at least one of the following: the number of predicted beams; one or more predicted time slots; the BI for each of the predicted beams; one or more P-RSRPs for a subset or all of the predicted beams; one or more beam probability indicators (BPIs) for a subset or all of the predicted beams; or one or more confidence indicators (CIs) for a subset or all of the predicted beams.

[0173] In all respects, selectively transmitting a beam prediction report includes at least one of the following: using CSI Part 1 on a PUCCH or PUSCH to carry the beam prediction report; using one or more PUCCH resources to carry the beam prediction report; or using CSI Part 1 on a PUCCH or PUSCH to carry a first portion of the beam prediction report and using CSI Part 2 on a PUCCH or PUSCH to carry a second portion of the beam prediction report.

[0174] Figure 11 This is a flowchart of a wireless communication method 1100 at a network entity. Method 1100 and... Figure 10 Method 1000 is complementary. (Reference) Figure 1 , Figure 3 , Figure 5 and Figure 13 Method 1100 can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station (such as RU 106, DU 108, CU 110, RU processor 1306, DU processor 1326, CU processor 1346, etc.). One or more network entities 104 may include memories 1306' / 1326' / 1346', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104 (such as RU processor 1306, DU processor 1326, or CU processor 1346).

[0175] like Figure 11 As shown, the network entity receives a message from the UE indicating the UE's capabilities (similar to 1102). Figure 3 and Figure 5 Operations 302 and 502).

[0176] The network entity sends a 1104 report configuration to the UE to configure a beam prediction report including BI, which configures at least one of the SSB resource set or CSI-RS resource set used for channel measurements (similar to...). Figure 3 and Figure 5 Operations 304 and 504).

[0177] The network entity sends one or more transmissions of at least one of the 1106 SSB resource set or CSI-RS resource set to the UE at times (similar to...). Figure 3 and Figure 5 Operations 306 and 506).

[0178] The network entity receives an 1110 beam prediction report from the UE. This beam prediction report includes a BI (similar to) predicted based on one or more transmission timings and a verification process associated with the beam prediction report. Figure 3 and Figure 5 Operations 310 and 510).

[0179] In all aspects, the report configuration further configures the time constraints for channel measurements, where one or more transmission opportunities are determined based on time constraints.

[0180] In all respects, the beam prediction report includes at least one of the following information: the number of predicted beams; one or more predicted time slots; the BI for each of the predicted beams; one or more P-RSRPs for a subset or all of the predicted beams; one or more beam probability indicators (BPIs) for a subset or all of the predicted beams; or one or more confidence indicators (CIs) for a subset or all of the predicted beams.

[0181] like Figure 12 The described UE device 1202 can execute method 1000. For example... Figure 13 The one or more network entities (or BSs) 104 described herein may perform method 1100.

[0182] Figure 12 Illustration 1200 illustrates an example of a hardware implementation of UE device 1202. UE device 1202 may be UE 102, a component of UE 102, or may implement UE functions. UE device 1202 may include application processor 1206, which may have on-chip memory 1206'. In the example, application processor 1206 may be coupled to secure digital (SD) card 1208 and / or display 1210. Application processor 1206 may also be coupled to sensor module 1212, power supply 1214, additional memory module 1216, camera 1218, and / or other related components. For example, sensor module 1212 may control barometric pressure sensor / altimeter, motion sensors (such as inertial management unit (IMU), gyroscope, accelerometer), light detection and ranging (LIDAR) device, radio-assisted detection and ranging (RADAR) device, sound navigation and ranging (SONAR) device, magnetometer, audio device, and / or other technologies for positioning.

[0183] The UE device 1202 may further include a wireless baseband processor 1226, which may be referred to as a modem. The wireless baseband processor 1226 may have on-chip memory 1226'. Together with and similarly to the application processor 1206, the wireless baseband processor 1226 may also be coupled to a sensor module 1212, a power supply 1214, an additional memory module 1216, a camera 1218, and / or other related components. The wireless baseband processor 1226 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1220 and / or one or more transceivers 1230 (e.g., wireless RF transceivers).

[0184] Within one or more transceivers 1230, the UE device 1202 may include a Bluetooth module 1232, a WLAN module 1234, an SPS module 1236 (e.g., a GNSS module), and / or a cellular module 1238. The Bluetooth module 1232, WLAN module 1234, SPS module 1236, and cellular module 1238 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1232, WLAN module 1234, SPS module 1236, and cellular module 1238 may each include a dedicated antenna and / or communicate with one or more other nodes using antenna 1240. For example, UE device 1202 can communicate with another UE 102 (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1230 and antenna 1240, wherein network entity 104 may correspond to a base station or a unit of the base station such as RU106, DU 108 or CU 110.

[0185] The wireless baseband processor 1226 and application processor 1206 may each include computer-readable media / memory 1226' and 1206', respectively. An additional memory module 1216 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1226', 1206', and 1216 may be non-transitory. The wireless baseband processor 1226 and application processor 1206 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1226', 1206', and 1216. When executed by the wireless baseband processor 1226 / application processor 1206, this software causes the wireless baseband processor 1226 / application processor 1206 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1226 / application processor 1206 during software execution. The wireless baseband processor 1226 / application processor 1206 may be a component of UE 102. UE device 1202 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1226 and / or the application processor 1206. In other examples, UE device 1202 may be the entire UE 102 and may include additional modules for device 1202.

[0186] like Figure 1 China discusses and about Figure 3 and Figure 4 In implementation, the beam prediction reporting component 130 is configured to receive a first control signaling from a network entity, the first control signaling indicating at least one beam prediction TCI state associated with a first delay and at least one non-beam prediction TCI state associated with a second delay. The beam prediction reporting component 130 then receives a second control signaling that activates one or more of the at least one beam prediction TCI state and the at least one non-beam prediction TCI state. The UE 102 then communicates with the network entity at an action time associated with the first delay or the second delay based on the one or more TCI states.

[0187] The beam prediction reporting component 130 may be located within application processor 1206 (e.g., at 130a), within wireless baseband processor 1226 (e.g., at 130b), or within both application processor 1206 and wireless baseband processor 1226. Beam prediction reporting components 130a-130b may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for use by one or more processors, or a combination thereof.

[0188] Figure 13Illustration 1300 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1346, which may have on-chip memory 1346'. In some aspects, CU 110 may further include an additional memory module 1356 and / or a communication interface 1348, both of which may be coupled to the CU processor 1346. CU 110 may communicate with DU 108 via a midhaul link 162, such as an F1 interface between the communication interface 1348 of CU 110 and the communication interface 1328 of DU 108.

[0189] DU 108 may include a DU processor 1326, which may have on-chip memory 1326'. In some aspects, DU 108 may further include an additional memory module 1336 and / or a communication interface 1328, both of which may be coupled to the DU processor 1326. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1328 and RU 106's communication interface 1308.

[0190] RU 106 may include an RU processor 1306, which may have on-chip memory 1306'. In some aspects, RU 106 may further include an additional memory module 1316, a communication interface 1308, and one or more transceivers 1330, all of which may be coupled to the RU processor 1306. RU 106 may further include an antenna 1340, which may be coupled to one or more transceivers 1330, enabling RU 106 to communicate with UE 102 via the antenna 1340 through one or more transceivers 1330.

[0191] On-chip memories 1306', 1326', 1346' and additional memory modules 1316, 1336, 1356 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1306, 1326, 1346 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1306, 1326, 1346, the software causes the processor 1306, 1326, 1346 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by processors 1306, 1326, 1346 during software execution. In the example, the beam configuration component 150 may be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0192] Based on the examples provided in this article, the beam configuration component 150 can perform various operations and signaling (such as...). Figure 3 , Figure 4 and Figure 5 The beam configuration components 150a-150c may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors 1306, 1326, 1346 configured to perform the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1306, 1326, 1346, or combinations thereof.

[0193] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is for illustrative purposes only. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate exemplary / optional elements in the illustrations. The appended method claims present the elements of each box in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0194] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0195] Various aspects of wireless communication systems (such as telecommunications systems) are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the system as a whole.

[0196] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, ML / AI processing units, central processing units, application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software can be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0197] If the functionality described herein is implemented in software, then such functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage medium can be any available medium that is computer-accessible.

[0198] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0199] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0200] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0201] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, phrases such as "when" do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that may occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0202] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set can be interpreted as a set of elements having a number of one or more elements.

[0203] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate the same or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numbers ending in “06” (e.g., 206, 306, 406, etc.).

[0204] It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X or Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and / or Y". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "B only". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "A+B" or "B+A".

[0205] It should be noted that some or all of the embodiments described above or below may be combined or formed into new or another embodiment.

[0206] It should be noted that the foregoing or following embodiments can be used to solve at least (but not limited to) the problems or scenarios mentioned in this disclosure.

[0207] The following additional considerations may apply to the foregoing and the following discussion.

[0208] It should be noted that any two or more of the foregoing or following paragraphs, (sub)bullets, points, actions or claims described in each method / example / implementation may be logically, reasonably and appropriately combined to form a particular method.

[0209] It should be noted that any sentence, paragraph, (sub)bulb, point, action, or claim described in the foregoing or following embodiments / implementations / concepts can be implemented independently and separately to form a particular method. Dependencies such as "based on," "more specifically," and "wherein" in the embodiments / implementations / concepts mentioned in this disclosure are merely one possible embodiment and do not limit a particular method.

[0210] It should be noted that some or all of the following terms and assumptions may be used below. A BS may include a network central unit or network node in an NR for controlling one or more TRPs associated with one or more cells. Communication between the BS and the TRP is via fronthaul. The BS may be referred to as a Central Unit (CU), eNB, gNB, or NodeB. A TRP may include: a transmit and receive point that provides network coverage and communicates directly with the UE. A TRP may be referred to as a Distributed Unit (DU) or network node. A cell may include one or more associated TRPs; for example, the coverage of a cell consists of the coverage of all associated TRPs. A cell is controlled by a BS or network entity. A cell may be referred to as a TRP group (TRPG). A serving beam may include a beam generated by a network node (e.g., a TRP) and configured to communicate with the UE (e.g., for transmission and / or reception). A candidate beam for the UE is a candidate for the serving beam. The serving beam may or may not be a candidate beam.

[0211] The user device in which the technologies of this disclosure are implemented (e.g., UE 102) can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Furthermore, in some cases, the user device can be embedded in an electronic system (such as the main unit of a vehicle or an advanced driver assistance system (ADAS)). Even further, the user device can operate as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0212] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain way. A hardware module may include a dedicated circuit system or logic that is permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or a circuit system (e.g., included within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0213] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. The software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0214] Structural and functional equivalents of elements of all aspects described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element may be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) may be construed as “at least based on A”.

[0215] Example

[0216] Example 1 is a device including a processor configured to cause a user equipment (UE) to perform: Receive a Channel State Information (CSI) report configuration, the CSI report configuration configuring the UE to report at least a predicted beam indicator (BI) and a synchronization signal block (SSB) and / or a CSI reference signal (CSI-RS) resource set for channel measurements; Receive the SSB / CSI-RS resource set used for channel measurements; The beam prediction report, including the BI, is transmitted based on one or more transmission opportunities received from the SSB / CSI-RS resources used for channel measurements.

[0217] Example 2 is a device according to Example 1, wherein the UE reports UE capabilities, the UE capabilities indicating at least one of the following: Does it support beam prediction reports based on spatial domain beam prediction? Does it support beam prediction reports based on time-domain beam prediction? Does it support beam prediction reports based on joint spatial and temporal beam prediction? Does it support P-RSRP / BPI / CI reporting; the maximum number of predicted beams supported for spatial and / or temporal domain beam prediction; Supported predicted window lengths used for time-domain beam prediction; The maximum number of SSB or CSI-RS resources supported per CSI report for beam prediction; or The maximum number of CSI reports supported for beam prediction configuration.

[0218] Example 3 is a device according to Example 1, wherein the UE receives the configuration of the SSB or CSI-RS resources for channel measurement based on at least one of the following: Same temporal behavior; Same serving cell index; Same periodicity; Sudden periodicity; or The same periodicity in sudden events.

[0219] Example 4 is a device according to Example 1, wherein the UE receives a configuration of a subset of the SSB or CSI-RS resources for channel measurement, the configuration indicating that the SSB or CSI-RS resources share at least one of the following quasi-co-address parameters: Average delay; Delay spread; Doppler extension; Doppler shift; Space reception parameters; Average gain; Same antenna port; or Same beam identifier.

[0220] Example 5 is a device according to Examples 1 to 4, wherein the UE receives a configuration of a time limit for channel measurement.

[0221] Example 6 is a device according to Example 5, wherein the UE determines one or more transmission timings of the SSB / CSI-RS resources for channel measurement based on the received configuration of the time constraints for channel measurement.

[0222] Example 7 is a device according to Example 1, wherein the UE determines whether to send the beam prediction report based on at least one of the following: The number of transmission opportunities received by the SSB / CSI-RS resource for channel measurement; Discontinuous reception (DRX) configuration; Predicted time slots used for beam prediction; The time slot used for the beam prediction report; Minimum processing latency for beam prediction reports; The number of CSI processing units (CPUs) currently in use; The number of extended CPUs currently in use; The maximum number of CPUs; or The maximum number of eCPUs.

[0223] Example 8 is a device according to Example 1, wherein the UE determines whether to send the beam prediction report or another type of report based on priority.

[0224] Example 9 is a device according to Example 1, wherein the UE reuses the beam prediction report and other types of reports based on priority.

[0225] Example 10 is a device according to Example 1, wherein the UE determines the priority based on at least one of the following: The time-domain behavior described in the report; The serving cell index of the SSB / CSI-RS used for channel measurements or the serving cell configured with the report configuration; Report content; or Report configuration identifier (ID).

[0226] Example 11 is a device according to Example 1, wherein if a PUCCH with the beam prediction report conflicts with a sounding reference signal (SRS) in the time domain within the same serving cell, the UE discards the PUCCH or the SRS based on priority.

[0227] Example 12 is a device according to Example 11, wherein the UE determines the priority based on the time-domain behavior of the SRS.

[0228] Example 13 is a device according to Example 1, wherein if the PUCCH or PUSCH with the beam prediction report conflicts with a guard period of the sounding reference signal (SRS) in the time domain in the same serving cell, the UE discards the PUCCH or PUSCH.

[0229] Example 14 is a device according to Example 1, wherein the UE calculates the predicted reference signal received power (P-RSRP) of the predicted beam based on the reference transmitted power.

[0230] Example 15 is a device according to Example 14, wherein the UE receives the configuration of the reference transmission power.

[0231] Example 16 is a device according to Example 1, wherein the UE determines the predicted time slot for beam prediction reporting based on at least one of the following: The transmission timing of the SSB / CSI-RS resources; CSI reference resources; or The time slot used for the beam prediction report.

[0232] Example 17 is a device according to Examples 1 to 16, wherein the UE transmits at least one of the following in the beam prediction report: The predicted number of beams; Predicted time slots; BI for each predicted beam; Whether to report P-RSRP for each or all predicted beams; Whether to report the beam probability indicator (BPI) for each or all predicted beams; Whether to report confidence indicators (CI) for each or all predicted beams; P-RSRP for a subset or all of the predicted beam; For a subset or all of the predicted beams; or CI used for a subset or all of the predicted beam.

[0233] Example 18 is a device according to Example 17, wherein the UE transmits the beam prediction report via CSI section 1 on PUCCH or PUSCH.

[0234] Example 19 is a device according to Example 18, wherein the UE transmits the beam prediction report via one or more PUCCH resources.

[0235] Example 20 is a device according to Example 17, wherein the UE transmits a first portion of the beam prediction report via CSI section 1 on the PUCCH or PUSCH, and transmits the remaining portion of the beam prediction report via CSI section 2 on the PUCCH or PUSCH.

[0236] Example 21 is a device including a processor configured to enable a base station (BS): Send a Channel State Information (CSI) report configuration that configures the UE to report at least a predicted beam indicator (BI) and a synchronization signal block (SSB) and / or a CSI reference signal (CSI-RS) resource set for channel measurements; Transmit the SSB / CSI-RS resource set used for channel measurements; and Receive beam prediction reports including BI.

[0237] Example 22 is a device according to Example 21, wherein the BS receives UE capabilities, the UE capabilities indicating at least one of the following: Does it support beam prediction reports based on spatial domain beam prediction? Does it support beam prediction reports based on time-domain beam prediction? Does it support beam prediction reports based on joint spatial and temporal beam prediction? Does it support P-RSRP / BPI / CI reporting; the maximum number of predicted beams supported for spatial and / or temporal domain beam prediction; Supported predicted window lengths used for time-domain beam prediction; The maximum number of SSB or CSI-RS resources supported per CSI report for beam prediction; or The maximum number of CSI reports supported for beam prediction configuration.

[0238] Example 23 is a device according to Example 21, wherein the BS transmits the configuration of the SSB or CSI-RS resources for channel measurement based on at least one of the following: Same temporal behavior; Same serving cell index; Same periodicity; Sudden periodicity; or The same periodicity in sudden events.

[0239] Example 24 is a device according to Example 21, wherein the BS transmits a configuration for a subset of the SSB or CSI-RS resources for channel measurements, the configuration indicating that the SSB or CSI-RS resources share at least one of the following quasi-co-address parameters: Average delay; Delay spread; Doppler extension; Doppler shift; Space reception parameters; Average gain; Same antenna port; or Same beam identifier.

[0240] Example 25 is a device according to Examples 21 to 24, wherein the BS transmits a configuration of time constraints for channel measurement.

[0241] Example 26 is a device according to Example 21, wherein the BS determines whether to receive the beam prediction report based on at least one of the following: The number of transmission opportunities received by the SSB / CSI-RS resource for channel measurement; Discontinuous reception (DRX) configuration; Predicted time slots used for beam prediction; The time slot used for the beam prediction report; Minimum processing latency for beam prediction reports; The number of CSI processing units (CPUs) currently in use; The number of extended CPUs currently in use; The maximum number of CPUs; or The maximum number of eCPUs.

[0242] Example 27 is the device according to Example 21, wherein the BS determines whether to receive the beam prediction report or other types of reports based on priority.

[0243] Example 28 is the device according to Example 21, wherein the BS receives priority-based multiplexing beam prediction reports and other types of reports.

[0244] Example 29 is a device according to Examples 27 and 28, wherein the BS determines the priority based on at least one of the following: The time-domain behavior described in the report; The serving cell index of the SSB / CSI-RS used for channel measurements or the serving cell configured with the report configuration; Report content; or Report configuration identifier (ID).

[0245] Example 30 is the device according to Example 21, wherein if a PUCCH with the beam prediction report conflicts with a sounding reference signal (SRS) in the time domain within the same serving cell, the BS avoids receiving the PUCCH or SRS based on priority.

[0246] Example 31 is a device according to Example 30, wherein the BS determines the priority based on the time-domain behavior of the SRS.

[0247] Example 32 is the device according to Example 21, wherein if the PUCCH or PUSCH with the beam prediction report conflicts with the guard period of the sounding reference signal (SRS) in the time domain in the same serving cell, the BS avoids receiving the PUCCH or PUSCH.

[0248] Example 33 is the device according to Example 21, wherein the BS transmits the configuration of the reference transmission power.

[0249] Example 34 is a device according to Example 21, wherein the BS determines the predicted time slot for beam prediction reporting based on at least one of the following: The transmission timing of the SSB / CSI-RS resources; CSI reference resources; or The time slot used for the beam prediction report.

[0250] Example 35 is a device according to Examples 21 to 34, wherein the BS receives at least one of the following in the beam prediction report: The predicted number of beams; Predicted time slots; BI for each predicted beam; Whether to report P-RSRP for each or all predicted beams; Whether to report the beam probability indicator (BPI) for each or all predicted beams; Whether to report confidence indicators (CI) for each or all predicted beams; P-RSRP for a subset or all of the predicted beam; For a subset or all of the predicted beams; or CI used for a subset or all of the predicted beam.

[0251] Example 36 is a device according to Example 35, wherein the BS receives the beam prediction report via CSI section 1 on the PUCCH or PUSCH.

[0252] Example 37 is a device according to Example 36, wherein the BS receives the beam prediction report via one or more PUCCH resources.

[0253] Example 38 is a device according to Example 35, wherein the BS receives a first portion of the beam prediction report via CSI section 1 on the PUCCH or PUSCH, and receives the remaining portion of the beam prediction report via CSI section 2 on the PUCCH or PUSCH.

[0254] Example 39 is a method for wireless communication performed by a user equipment (UE), the method comprising: Receive a report configuration from a network entity to configure a beam prediction report including a beam indicator (BI), the report configuration configuring at least one of a synchronization signal block (SSB) resource set or a channel state information reference signal (CSI-RS) resource set for channel measurement; One or more transmission opportunities from the network entity to receive at least one of the SSB resource set or the CSI-RS resource set based on the report configuration; and The beam prediction report is selectively transmitted, and the beam prediction report includes a BI predicted based on the one or more transmission timings and a verification process associated with the beam prediction report.

[0255] Example 40 is the method according to Example 39, further comprising: Send a message to the network entity, the message indicating at least one of the following capabilities of the UE: Beam prediction in the spatial domain; Beam prediction in the time domain and the supporting window length for the beam prediction in the time domain; Joint beam prediction in both the spatial and temporal domains; Report at least one of the following: predicted reference signal received power (P-RSRP), beam probability indicator (BPI), confidence indicator (CI), maximum number of predicted beams supported for the spatial domain, or maximum number of predicted beams supported for the time domain. The maximum number of SSBs or the CSI-RS resource set reported per beam prediction; or Maximum number of beam reports configured.

[0256] Example 41 is a method according to Example 39 or 40, wherein the reporting configuration is based on at least one of the following to configure SSB resources or CSI-RS resources: Same temporal behavior; Same serving cell index; Same periodicity; Sudden periodicity; or The same periodicity in burst transmissions.

[0257] Example 42 is a method according to Example 39 or 40, wherein the reporting configuration configures a subset of the SSB resources or the CSI-RS resources having at least one common QCL parameter among the following quasi-co-location (QCL) parameters: Average delay; Delay spread; Doppler extension; Doppler shift; Space reception parameters; Average gain; Antenna port; or Beam identifier.

[0258] Example 43 is a method according to any one of Examples 39 to 42, wherein the reporting configuration further configures a time limit for channel measurement, wherein the one or more transmission timings are determined based on the time limit.

[0259] Example 44 is a method according to any one of Examples 39 to 43, wherein the verification process is based on at least one of the following: The number of actual transmission opportunities received by the SSB resource set or the CSI-RS resource set; Discontinuous reception (DRX) configuration; Predicted time slots used for beam prediction; The time slot used to send the beam prediction report; The minimum processing delay of the beam prediction report; The number of CSI processing units (CPUs) currently in use; The number of occupied extended CPUs (eCPUs); The maximum number of CPUs; or The maximum number of eCPUs.

[0260] Example 45 is a method according to any one of Examples 39 to 44, further comprising: Determine the priority of the beam prediction report and the corresponding priority of other types of reports to be sent to the network entity; and The beam prediction report is sent based on a priority rule between the beam prediction report and the other types of reports.

[0261] Example 46 is the method according to Example 45, further comprising: One or more of the beam prediction report and the other types of reports may be reused based on the priority of the beam prediction report and the corresponding priority of the other types of reports.

[0262] Example 47 is the method according to Example 45 or 46, wherein determining the priority of the beam prediction report and the corresponding priority of other types of reports to be sent to the network entity is based on at least one of the following: The temporal behavior of the beam prediction report and the other types of reports; The serving cell index of at least one of the SSBs or the CSI-RS resource sets, or the serving cell configured using the report configuration; The corresponding content of the beam prediction report and the other types of reports; or The identifier (ID) configured for the beam prediction report and the other types of reports.

[0263] Example 48 is a method according to any one of Examples 39 to 47, further comprising: Detecting time-domain conflicts between the beam prediction report and the sounding reference signal (SRS) on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) transmissions; and In response to the detection of the conflict, the beam prediction report or the SRS is discarded based on priority rules.

[0264] Example 49 is the method according to Example 48, wherein the conflict in the time domain includes a conflict between the beam prediction report and the SRS during the SRS's guard period, and the method further includes discarding the PUCCH or PUSCH of the beam prediction report.

[0265] Example 50, based on any one of Examples 39 to 49, further includes: Receive reference transmission power from the network entity; and The predicted reference signal received power (P-RSRP) of the predicted beam is calculated based on the reference transmitted power.

[0266] Example 51 is the method according to any one of Examples 39 to 50, wherein the beam prediction report further includes at least one of the following: The predicted number of beams; One or more predicted time slots; BI of each of the predicted beams; One or more P-RSRPs for a subset or all of the predicted beam; One or more beam probability indicators (BPIs) for a subset or all of the predicted beam; or One or more confidence indicators (CIs) are used for a subset or all of the predicted beam.

[0267] Example 52 is a method according to any one of Examples 39 to 51, wherein selectively transmitting the beam prediction report includes at least one of the following: Use CSI Part 1 on PUCCH or PUSCH to carry the beam prediction report; Use one or more PUCCH resources to carry the beam prediction report; or The first part of the beam prediction report is carried on CSI section 1 on the PUCCH or PUSCH, and the second part of the beam prediction report is carried on CSI section 2 on the PUCCH or PUSCH.

[0268] Example 53 is a method for wireless communication performed by a network entity, the method comprising: Send a (304) report configuration to the user equipment (UE) to configure a beam prediction report including a beam indicator (BI), the report configuration configuring at least one of a synchronization signal block (SSB) resource set or a channel state information reference signal (CSI-RS) resource set for channel measurement; Sending (306) one or more transmission opportunities of at least one of the SSB resource set or the CSI-RS resource set to the UE; and Receive (310) the beam prediction report, which includes a BI predicted based on the one or more transmission timings and a verification process associated with the beam prediction report.

[0269] Example 54 is the method according to Example 53, further comprising: The UE receives a (302) message indicating at least one of the following capabilities of the UE: Beam prediction in the spatial domain; Beam prediction in the time domain and the supporting window length for the beam prediction in the time domain; Joint beam prediction in both the spatial and temporal domains; Report at least one of the following: predicted reference signal received power (P-RSRP), beam probability indicator (BPI), confidence indicator (CI), maximum number of predicted beams supported for the spatial domain, or maximum number of predicted beams supported for the time domain. The maximum number of SSBs or the CSI-RS resource set reported per beam prediction; or Maximum number of beam reports configured.

[0270] Example 55 is a method according to Example 53 or 54, wherein the reporting configuration is configured based on at least one of the following: Same temporal behavior; Same serving cell index; Same periodicity; Sudden periodicity; or The same periodicity in sudden operations.

[0271] Example 56 is a method according to Example 53 or 54, wherein the reporting configuration configures a subset of the SSB resources or the CSI-RS resources having at least one common QCL parameter among the following quasi-co-location (QCL) parameters: Average delay; Delay spread; Doppler extension; Doppler shift; Space reception parameters; Average gain; Antenna port; or Beam identifier.

[0272] Example 57 is a method according to any one of Examples 53 to 56, wherein the reporting configuration further configures a time limit for channel measurement, wherein the one or more transmission timings are determined based on the time limit.

[0273] Example 58 is a method according to any one of Examples 53 to 57, further comprising: The reference transmission power of the UE is sent to the UE to calculate the predicted reference signal received power (P-RSRP) of the predicted beam based on the reference transmission power.

[0274] Example 59 is a method according to any one of Examples 53 to 58, wherein the beam prediction report includes at least one of the following information: The predicted number of beams; One or more predicted time slots; BI of each of the predicted beams; One or more P-RSRPs for a subset or all of the predicted beam; One or more beam probability indicators (BPIs) for a subset or all of the predicted beam; or One or more confidence indicators (CIs) are used for a subset or all of the predicted beam.

[0275] Example 60 is the method according to any one of Examples 53 to 59, wherein receiving the beam prediction report includes at least one of the following: Receive the beam prediction report in CSI section 1 on PUCCH or PUSCH; Receive the beam prediction report in one or more PUCCH resources; or The first part of the beam prediction report is received in CSI section 1 on the PUCCH or PUSCH, and the second part of the beam prediction report is received in CSI section 2 on the PUCCH or PUSCH.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive (304) report configuration from network entity to configure a beam prediction report including beam indicator BI, the report configuration being used to configure at least one of the synchronization signal block SSB resource set or channel state information reference signal CSI-RS resource set for channel measurement; One or more transmission opportunities from the network entity based on the report configuration to receive (306) at least one of the SSB resource set or the CSI-RS resource set; as well as Selectively transmit (310) the beam prediction report, which includes a BI predicted based on the one or more transmission timings and a verification process associated with the beam prediction report.

2. The method of claim 1, further comprising: Send a (302) message to the network entity, the message indicating at least one of the following capabilities of the UE: Beam prediction in the spatial domain; Beam prediction in the time domain and the window length supporting the beam prediction in the time domain; Joint beam prediction in both the spatial and temporal domains; Report at least one of the following: predicted reference signal received power P-RSRP, beam probability indicator BPI, confidence indicator CI, the maximum number of predicted beams supported for the spatial domain, or the maximum number of predicted beams supported for the time domain. The maximum number of SSBs or the CSI-RS resource set reported per beam prediction; or Maximum number of beam reports configured.

3. The method of claim 1 or 2, wherein the reporting configuration is used to configure SSB resources or CSI-RS resources based on at least one of the following: Same temporal behavior; Same serving cell index; Same periodicity; Sudden periodicity; or The same periodicity in burst transmissions.

4. The method of claim 1 or 2, wherein the reporting configuration is used to configure a subset of the SSB resources or the CSI-RS resources having at least one common QCL parameter among the following quasi-co-located QCL parameters: Average delay; Delay spread; Doppler extension; Doppler shift; Space reception parameters; Average gain; Antenna port; or Beam identifier.

5. The method of any one of claims 1 to 4, wherein the reporting configuration further configures a time limit for channel measurement, wherein the one or more transmission timings are determined based on the time limit.

6. The method of any one of claims 1 to 5, wherein the verification process is based on at least one of the following: The number of actual transmission opportunities received by the SSB resource set or the CSI-RS resource set; Discontinuous reception DRX configuration; Predicted time slots used for beam prediction; The time slot used to send the beam prediction report; The minimum processing delay of the beam prediction report; The number of CSI processing units (CPUs) currently in use; The number of occupied extended CPUs (eCPUs); The maximum number of CPUs; or The maximum number of eCPUs.

7. The method of any one of claims 1 to 6, further comprising: Determine the priority of the beam prediction report and the corresponding priority of other types of reports to be sent to the network entity; as well as The beam prediction report is sent based on a priority rule between the beam prediction report and the other types of reports.

8. The method of claim 7, further comprising: One or more of the beam prediction report and the other types of reports may be reused based on the priority of the beam prediction report and the corresponding priority of the other types of reports.

9. The method of any one of claims 1 to 8, further comprising: Detect time-domain conflicts between the beam prediction report and the sounding reference signal SRS on the transmission of the physical uplink control channel PUCCH or the physical uplink shared channel PUSCH; as well as In response to the detection of the conflict, the beam prediction report or the SRS is discarded based on priority rules.

10. The method of any one of claims 1 to 9, further comprising: Receive reference transmission power from the network entity; as well as The predicted reference signal received power P-RSRP of the predicted beam is calculated based on the reference transmitted power.

11. The method of any one of claims 1 to 10, wherein the beam prediction report further comprises at least one of the following: The predicted number of beams; One or more predicted time slots; BI of each of the predicted beams; One or more P-RSRPs for a subset or all of the predicted beam; One or more beam probability indicators (BPIs) for a subset or all of the predicted beams; or One or more confidence indicators (CIs) are used for a subset or all of the predicted beam.

12. The method of any one of claims 1 to 11, wherein selectively transmitting the beam prediction report comprises at least one of the following: Use CSI Part 1 on PUCCH or PUSCH to carry the beam prediction report; Use one or more PUCCH resources to carry the beam prediction report; or The first part of the beam prediction report is carried on CSI section 1 on the PUCCH or PUSCH, and the second part of the beam prediction report is carried on CSI section 2 on the PUCCH or PUSCH.

13. A method for wireless communication performed by a network entity, the method comprising: Send (304) report configuration to user equipment (UE) to configure a beam prediction report including beam indicator BI, the report configuration being used to configure at least one of the synchronization signal block SSB resource set or channel state information reference signal CSI-RS resource set for channel measurement; Send (306) one or more transmission opportunities of at least one of the SSB resource set or the CSI-RS resource set to the UE; as well as Receive (310) the beam prediction report, which includes a BI predicted based on the one or more transmission timings and a verification process associated with the beam prediction report.

14. The method of claim 13, wherein the reporting configuration further configures a time limit for channel measurement, wherein the one or more transmission timings are determined based on the time limit.

15. The method of claim 13 or 14, wherein the beam prediction report includes at least one of the following: The predicted number of beams; One or more predicted time slots; BI of each of the predicted beams; One or more P-RSRPs for a subset or all of the predicted beam; One or more beam probability indicators (BPIs) for a subset or all of the predicted beams; or One or more confidence indicators (CIs) are used for a subset or all of the predicted beam.

16. An apparatus comprising: One or more radio frequency (RF) modems; Processor, the processor being coupled to the one or more RF modems; as well as At least one memory storing executable instructions for manipulating at least one of the processor or the one or more RF modems to perform the method as claimed in any one of claims 1 to 15.

Images