Sending predicted beam report based on confidence level of predicted beam

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a beam reporting configuration. The UE may transmit a predicted beam report according to the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. The UE may transmit the predicted beam report based at least in part on the at least one confidence level. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication, and specifically to techniques and apparatus for transmitting predicted beam reports based on a confidence level of the predicted beam. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available wireless communication system resources.

[0003] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Accordingly, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0004] One aspect provides a method for wireless communication by a user equipment (UE). The method includes receiving a beam report configuration. The method further includes transmitting a predicted beam report according to the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein transmitting the predicted beam report includes transmitting the predicted beam report at least in part based on the at least one confidence level.

[0005] On the other hand, a method for wireless communication by a network entity is provided. The method includes: outputting a beam report configuration. The method further includes: obtaining a predicted beam report based on the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein obtaining the predicted beam report includes: obtaining the predicted beam report at least in part based on the at least one confidence level.

[0006] Other aspects provide: an apparatus capable of operating to, configured to, or otherwise adapted to perform any or more of the foregoing methods and / or those methods described herein with reference to the accompanying drawings and description, and illustrated therein; a non-transitory computer-readable medium comprising computer-executable instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and / or those methods described herein with reference to the accompanying drawings and description, and illustrated therein; a computer program product embodied on a computer-readable storage medium including code for performing the foregoing methods and / or those methods described herein with reference to the accompanying drawings and description, and illustrated therein; and / or an apparatus comprising components for performing the foregoing methods and / or those methods described herein with reference to the accompanying drawings and description, and illustrated therein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0007] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to provide a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0008] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers) for analog and digital purposes. The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0009] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as the description acknowledges other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0010] Figure 1 An example of a wireless communication network according to this disclosure is depicted.

[0011] Figure 2 This disclosure describes various aspects of an example base station (BS) and user equipment (UE) according to this disclosure.

[0012] Figure 3 An example decomposed base station architecture is described.

[0013] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various aspects of the data structure of the wireless communication network according to this disclosure are described.

[0014] Figure 5 This is a diagram illustrating an example of a beam management process according to this disclosure.

[0015] Figure 6This is a diagram illustrating an example of beam management according to this disclosure.

[0016] Figure 7 This is a diagram illustrating an example of sending a predicted beam report based on at least one confidence level of at least one predicted beam, in accordance with this disclosure.

[0017] Figure 8 This is a diagram illustrating examples of multiple predicted beams and associated confidence levels according to this disclosure.

[0018] Figure 9 This is an illustration of an example in which the first part of the predicted beam report according to this disclosure includes an indication of the payload size of the second part of the predicted beam report.

[0019] Figure 10 This is a diagram illustrating an example of the payload size of the second part of the beam report predicted according to the beam report configuration configuration of this disclosure.

[0020] Figure 11 This is a diagram illustrating an example of a beam report involving a first prediction and a beam report involving a second prediction according to this disclosure.

[0021] Figure 12 A method for wireless communication by a UE according to this disclosure is shown.

[0022] Figure 13 A method for wireless communication by a network entity according to this disclosure is shown.

[0023] Figure 14 The diagram illustrates an example of a specific implementation of the code and circuitry for a communication device according to this disclosure.

[0024] Figure 15 The diagram illustrates an example of a specific implementation of the code and circuitry for a communication device according to this disclosure. Detailed Implementation

[0025] Various aspects of this disclosure provide apparatus, methods, processing systems, and computer-readable media for transmitting predicted beam reports based on the confidence level of the predicted beam.

[0026] Artificial intelligence (AI) or machine learning (ML) can be used to generate predictions about beam management. For example, AI / ML models can generate predictions about which predicted / potential beams will provide optimal performance for user equipment (UE) and network entities. Based on the predictions generated by AI / ML models, network entities can select the beams to use for transmission (e.g., for downlink and / or uplink transmission).

[0027] AI / ML-based predictive beam management can generate confidence levels (e.g., probabilities) associated with the corresponding predicted beams. Confidence levels can be soft metrics that can be used to assess the quality of the predictions. However, reporting confidence levels (e.g., from the UE to network entities) may involve additional overhead for transmitting and processing indications of the predicted beams and confidence levels. For example, indications of the predicted beams and confidence levels can consume additional time and / or frequency resources. Furthermore, the UE and network entities can use computational and / or power resources to dispose of confidence levels (e.g., to transmit, receive, and / or process indications of confidence levels).

[0028] In some specific implementations provided herein, the UE may send a predicted beam report to a network entity. The predicted beam report may include an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. The UE may send the predicted beam report based on at least one confidence level of the at least one predicted beam. For example, the predicted beam indicated in the predicted beam report may be the predicted beam with the highest confidence level among all predicted beams. For example, the predicted beams indicated in the predicted beam report may have confidence levels whose sum satisfies (e.g., exceeds) a threshold (e.g., a target confidence level threshold). The predicted beam report may be limited to those predicted beams, and any remaining predicted beams with a lower confidence level than the predicted beams indicated in the predicted beam report may be excluded.

[0029] Therefore, the specific implementations described herein enable network entities to obtain indications of predicted beams that may be relevant to beam management (e.g., beam selection) without incurring additional overhead or resources to send indications of less relevant predicted beams. In some examples, the threshold may be configurable, which can provide control over the amount of overhead / resources involved in the transmission and / or processing of predicted beam reports.

[0030] In some examples, a predicted beam report may include a first portion transmitted via a first resource and a second portion transmitted via a second resource. For example, the first portion (which may include an indication of at least one predicted beam and its corresponding confidence level) may indicate the payload size of the second portion (which may or may not include the indication of at least one predicted beam and its corresponding confidence level). Reporting the predicted beam report in multiple portions can inform network entities of the number of predicted beams to be reported, and thus resolve potential ambiguities regarding the payload size. In some examples, the first portion may indicate that the second portion of the predicted beam report should not be sent, which can further reduce the overhead associated with the transmission of the report.

[0031] In some examples, the UE can receive beam report configuration from a network entity that configures the payload sizes of a first portion and a second portion of the predicted beam report. For example, the network entity can configure the payloads of the first and second portions before receiving the first portion of the predicted beam report (e.g., the second portion of the payload can be pre-configured). Besides resolving potential ambiguities, configuring the beam report configuration for the first and second portions can facilitate scheduling and minimize conflicts with other predicted beam reports. In some examples, the first portion can indicate that the second portion of the predicted beam report should not be sent, which can further reduce the overhead associated with report transmission.

[0032] In some examples, the UE may send a first predicted beam report and a second predicted beam report to a network entity based on the confidence levels of the predicted beams indicated in the first and second beam reports, respectively. For example, the predicted beams indicated in the first and second predicted beam reports may have a confidence level whose sum satisfies (e.g., exceeds) a threshold (e.g., a target confidence level threshold). The first predicted beam report may indicate the payload size of the second predicted beam report, and the network entity may configure the payload size of the second predicted beam report based on the first predicted beam report. The network entity may configure the payload size of the second predicted beam report such that overhead is reduced (e.g., such that the payload size of the second predicted beam report is limited based on the information to be indicated in the second predicted beam report (e.g., the number of predicted beams and the confidence level)). In some examples, the first predicted beam report may indicate that the second predicted beam report should not be sent, which may further reduce the overhead associated with sending predicted beam information.

[0033] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the invention.

[0034] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0035] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0036] Figure 1 An example of a wireless communication network 100 according to this disclosure is depicted.

[0037] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., UEs, base stations (BSs), components of BSs, servers, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial and non-terrestrial aspects. The terrestrial aspect includes ground-based network entities (e.g., BS 110), and the non-terrestrial aspect includes satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0038] In the depicted example, the wireless communication network 100 includes a BS 110, a UE 120, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0039] Figure 1 Various example UEs 120 are described, which may include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, Global Positioning System (GPS) devices, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, Always On (AON) devices, edge processing devices, or other similar devices. UE 120 may also be referred to as mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, or mobile phones, etc.

[0040] BS 110 can wirelessly communicate with UE 120 via communication link 170 (e.g., transmit signals to or receive signals from the UE). Communication link 170 between BS 110 and UE 120 can carry uplink (UL) (also known as reverse link) transmission from UE 120 to BS 110 and / or downlink (DL) (also known as forward link) transmission from BS 110 to UE 120. In various aspects, communication link 170 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0041] BS 110 may include, for example, NodeBs, enhanced NodeBs (eNBs), next-generation enhanced NodeBs (ng-eNBs), next-generation NodeBs (gNBs or gNodeBs), access points, transceiver base stations, radio base stations, radio transceivers, transceiver functions, transmit / receive points, etc. BS 110 may provide communication coverage for a corresponding geographic coverage area 112, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell provided by BS 110a may have a coverage area 112' that overlaps with the coverage area 112 of a macro cell). For example, BS 110 may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0042] While the BS 110 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few. In another example, various aspects of the base station can be virtualized. More generally, a BS (e.g., BS 110) can include components located at a single physical location or components located at various physical locations. In the example where the BS includes components located at various physical locations, each component can perform its own function, such that the various components collectively achieve a function similar to that of a BS located at a single physical location. In some aspects, a BS including components located at various physical locations can be referred to as having a decomposed radio access network architecture, such as an open RAN (O-RAN) architecture or a virtualized RAN (VRAN) architecture. Figure 3 An example decomposed BS architecture is depicted and described.

[0043] Different BSs 110 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G, etc.). For example, a BS 110 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 110 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 110 can communicate directly or indirectly with each other (e.g., via EPC 160 or 5GC 190) via a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0044] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some respects, the subdivision is based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 52,600MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). Base stations configured to communicate using mmWave or near-mmWave radio bands (e.g., mmWave base stations such as BS 110b) can utilize beamforming with UEs (e.g., 120) (e.g., as shown by 182) to improve path loss and range.

[0045] The communication link 170 between BS 110 and, for example, UE 120 can be via one or more carriers, which can have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other bandwidths) and can be aggregated in various ways. The carriers may or may not be adjacent to each other. In some examples, carrier allocation can be asymmetric with respect to DL and UL (e.g., more or fewer carriers can be allocated to DL compared to UL).

[0046] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Accordingly, some base stations (e.g., Figure 1Base station 110b can utilize beamforming with UE 120 to improve path loss and range, as shown at 182. For example, BS 110b and UE 120 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 110b can transmit beamformed signals to UE 120 in one or more transmit directions 182'. UE 120 can receive beamformed signals from BS 110b in one or more receive directions 182''. UE 120 can also transmit beamformed signals to BS 110b in one or more transmit directions 182''. BS 110b can also receive beamformed signals from UE 120 in one or more receive directions 182''. BS 110b and UE 120 can then perform beamforming training to determine the optimal receive and transmit directions for each of BS 110b and UE 120. It is worth noting that the transmission and reception directions of BS 110b can be the same or different. Similarly, the transmission and reception directions of UE 120 can be the same or different.

[0047] The wireless communication network 100 also includes a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0048] Some UEs 120 may use device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0049] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 161, other MMEs 162, Serving Gateway 163, Multimedia Broadcast Multicast Service (MBMS) Gateway 164, Broadcast Multicast Service Center (BM-SC) 165, and / or Packet Data Network (PDN) Gateway 166, as in the illustrated example. MME 161 may communicate with Home Subscriber Server (HSS) 167. MME 161 is the control node that handles signaling between UE 120 and EPC 160. Generally, MME 161 provides bearer and connectivity management.

[0050] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 163, which is connected to PDN Gateway 166. PDN Gateway 166 provides UE IP address allocation and other functions. PDN Gateway 166 and BM-SC 165 are connected to IP Service 168, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming media services, and / or other IP services.

[0051] The BM-SC 165 can provide functions for MBMS user service dispatch and delivery. The BM-SC 165 can act as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS bearer services in the Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmission. The MBMS gateway 164 can distribute MBMS services to BS 110 belonging to the Multicast-Broadcast Single Frequency Network (MBSFN) area belonging to the Broadcast-Specific Service, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0052] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 191, other AMFs 192, Session Management Function (SMF) 193, and User Plane Function (UPF) 194. AMF 191 can communicate with Unified Data Management (UDM) 195.

[0053] AMF 191 is the control node that handles signaling between UE 120 and 5GC 190. AMF 191 provides services such as Quality of Service (QoS) flow and session management.

[0054] IP packets are transmitted via UPF 194, which connects to IP service 196 and provides UE IP address allocation and other functions for 5GC 190. IP service 196 may include, for example, the Internet, intranet, IMS, PS streaming services and / or other IP services.

[0055] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, sidelink nodes, transmit and receive points (TRPs), or combinations thereof.

[0056] As indicated above, Figure 1 This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. Figure 1 The examples described are different.

[0057] Figure 2 Various aspects of example BS 110 and UE 120 according to this disclosure are depicted.

[0058] Generally, BS 110 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a to 234t (collectively referred to as 234), transceivers 232a to 232t (collectively referred to as 232) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 212) and the wireless reception of data (e.g., data sink 239). For example, BS 110 can transmit and receive data between BS 110 and UE 120. BS 110 includes a controller / processor 240 that can be configured to implement the various functions described herein related to wireless communication.

[0059] Generally, UE 120 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-252r (collectively referred to as 252), transceivers 254a-254r (collectively referred to as 254) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieval from data source 262) and the wireless reception of data (e.g., provision to data sink 260). UE 120 includes a controller / processor 280 that can be configured to implement the various functions described herein related to wireless communication.

[0060] For example downlink transmission, BS 110 includes a transmission processor 220 that can receive data from data source 212 and control information from controller / processor 240. This control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or other channels. In some examples, this data may be for the Physical Downlink Shared Channel (PDSCH).

[0061] The transmitter processor 220 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 220 can also generate reference symbols such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), or channel state information reference signal (CSI-RS).

[0062] The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 232a-232t. Each modulator in transceivers 232a-232t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 232a-232t can be transmitted via antennas 234a-234t respectively.

[0063] UE 120 includes antennas 252a-252r that receive downlink signals from BS 110 and provide the received signals to demodulators (DEMODs) in transceivers 254a-254r respectively. Each demodulator in transceivers 254a-254r can modulate (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0064] MIMO detector 256 acquires received symbols from all demodulators in transceivers 254a-254r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. Receiver processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information to controller / processor 280.

[0065] For example uplink transmission, UE 120 also includes a transmit processor 264 that receives and processes data from data source 262 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 280 (e.g., for the Physical Uplink Control Channel (PUCCH)). Transmit processor 264 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signals (SRS)). Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266, where applicable, further processed by modulators in transceivers 254a-254r (e.g., for single-carrier frequency division multiplexing (SC-FDM)), and transmitted to BS 110.

[0066] At BS 110, uplink signals from UE 120 can be received by antennas 234a-234t, processed by demodulators in transceivers 232a-232t, detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Memory 242 and memory 282 can store data and program code (e.g., processor-executable instructions, computer-executable instructions) for BS 110 and UE 120, respectively. Scheduler 244 can schedule UE to transmit data on the downlink and / or uplink.

[0067] In various respects, BS 110 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 212, scheduler 244, memory 242, transmit processor 220, controller / processor 240, TX MIMO processor 230, transceivers 232a-232t, antennas 234a-234t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 234a-234t, transceivers 232a-232t, RX MIMO detector 236, controller / processor 240, receive processor 238, scheduler 244, memory 242, network interface, and / or other aspects described herein.

[0068] In various respects, UE 120 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 262, memory 282, transmit processor 264, controller / processor 280, TX MIMO processor 266, transceiver 254a-254t, antenna 252a-252t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antenna 252a-252t, transceiver 254a-254t, RX MIMO detector 256, controller / processor 280, receive processor 258, memory 282, and / or other aspects described herein.

[0069] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

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

[0071] As indicated above, Figure 2 This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. Figure 2 The examples described are different.

[0072] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, AP, TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0073] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0074] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented by two or more units across various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. The various units of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0075] Figure 3 An example decomposed base station architecture 300 is depicted. The decomposed base station architecture 300 may include one or more central units (CUs) 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both. CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links (such as F1 interfaces). DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. RUs 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0076] Each of the units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the unit, or an associated processor or controller providing instructions to the unit's communication interface, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive or transmit signals to one or more other units via wired transmission media. Additionally or alternatively, these units may include wireless interfaces, which may include receivers, transmitters, or transceivers (such as RF transceivers), configured to receive signals or transmit signals to one or more other units, or both, via wireless transmission media.

[0077] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions managed by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU330 for network control and signaling purposes, as needed.

[0078] DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, DU 330 may, at least in part, host one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending on functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0079] Lower-layer functions can be implemented by one or more RU 340s. In some deployments, an RU340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on function splitting (such as lower-layer function splitting). In such architectures, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration enables the implementation of DU 330 and CU 310 in cloud-based RAN architectures such as vRAN architectures.

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

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

[0082] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and execute corrective actions using the AI / ML model via the SMO framework 305 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

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

[0084] Figure 4A , Figure 4B , Figure 4C and Figure 4D The present disclosure describes a method for use in wireless communication networks (such as...) Figure 1 All aspects of the data structure of the wireless communication network 100. Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0085] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and SC-FDM will reduce system bandwidth (e.g., as...) Figure 4B and Figure 4D The data (as depicted in the diagram) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0086] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0087] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and F is flexibly used between DL and UL. The UE can be configured with a time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via RRC signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0088] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Accordingly, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2 per subframe. µ Each time slot. Subcarrier spacing and symbol length / duration are functions of the parameter set. Subcarrier spacing can be equal to 2. μ ×15kHz, where μ is the parameter set index, which can be selected from values ​​0 to 5. Therefore, the subcarrier spacing is 15kHz for parameter set µ=0 and 480kHz for parameter set µ=5. Other parameter sets and subcarrier spacings can be used. Symbol length / duration is negatively correlated with subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D Examples are provided for slot configuration 0 with 14 symbols per slot and parameter set µ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0089] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0090] like Figure 4AAs illustrated, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 120). The RS may include demodulation RS (DMRS) and / or CSI-RS for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).

[0091] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0092] The primary synchronization signal (PSS) is located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE (e.g., UE 120) to determine subframe / symbol timing and physical layer identification.

[0093] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

[0094] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The PBCH carrying the Master Information Block (MIB) can logically group with the PSS and SSS to form a Synchronization Signal (SS) / PBCH Block (SSB). The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0095] like Figure 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE 120 can transmit SRS. SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of these comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0096] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0097] Figure 5 These are illustrations of examples 500, 510, and 520 illustrating beam management procedures according to this disclosure. Figure 5 As shown, Examples 500, 510, and 520 include UE 120 communicating with BS 110 in a wireless network (e.g., wireless communication network 100). However, Figure 5 The devices shown are provided as examples, and the wireless network can support communication and beam management between other devices (e.g., between UE 120 and BS 110 or TRP, between mobile terminal nodes and control nodes, between IAB child nodes and IAB parent nodes, and / or between scheduled nodes and scheduling nodes). In some aspects, UE 120 and BS 110 can be in a connected state (e.g., RRC connected state).

[0098] like Figure 5 As shown, Example 500 may include BS 110 and UE 120 communicating to perform beam management using CSI-RS. Example 500 depicts a first beam management procedure (e.g., P1 CSI-RS beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam scanning procedure, a cell search procedure, and / or a beam search procedure. Figure 5 As shown in Example 500, CSI-RS can be configured to be sent from BS 110 to UE 120. CSI-RS can be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using MAC control element (MAC-CE) signaling), and / or aperiodic (e.g., using DCI).

[0099] The first beam management process may include BS 110 performing beam scanning on multiple transmit (Tx) beams. BS 110 may use each of the multiple Tx beams used for beam management to transmit CSI-RS. To enable UE 120 to perform receive (Rx) beam scanning, BS 110 may use the transmit beams to transmit each CSI-RS multiple times within the same RS resource set (e.g., using repetition), allowing UE 120 to scan through the receive beams in multiple transmit instances. For example, if BS 110 has a set of N transmit beams and UE 120 has a set of M receive beams, CSI-RS may be transmitted M times on each of the N transmit beams, allowing UE 120 to receive M instances of CSI-RS per transmit beam. In other words, for each transmit beam of BS 110, UE 120 may perform beam scanning through UE 120's receive beams. Therefore, the first beam management procedure enables UE 120 to measure CSI-RS on different transmit beams using different receive beams to support the selection of beam pairs for BS 110 transmit beam / UE 120 receive beam. UE 120 can report the measurements to BS 110 so that BS 110 can select one or more beam pairs for communication between BS 110 and UE 120. Although Example 500 has been described in conjunction with CSI-RS, the first beam management procedure can also use SSB for beam management in a similar manner to that described above.

[0100] like Figure 5 As shown, Example 510 may include BS 110 and UE 120 communicating to perform beam management using CSI-RS. Example 510 depicts a second beam management procedure (e.g., P2 CSI-RS beam management). This second beam management procedure may be referred to as a beam refinement procedure, a BS beam refinement procedure, a TRP beam refinement procedure, and / or a transmission beam refinement procedure. Figure 5As shown in Example 510, CSI-RS can be configured to be transmitted from BS 110 to UE 120. The CSI-RS can be configured to be aperiodic (e.g., using DCI). A second beam management procedure may include BS 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with BS 110 (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management procedure). BS 110 may transmit CSI-RS using each of the one or more transmit beams used for beam management. UE 120 may measure each CSI-RS using a single (e.g., the same) receive beam (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable BS 110 to select the optimal transmit beam based at least in part on measurements of the CSI-RS reported by UE 120 (e.g., measured by UE 120 using a single receive beam).

[0101] like Figure 5 As shown, Example 520 depicts a third beam management process (e.g., P3 CSI-RS beam management). This third beam management process may be referred to as a beam refinement process, a UE beam refinement process, and / or a receive beam refinement process. Figure 5 As shown in Example 520, one or more CSI-RS can be configured to be transmitted from BS 110 to UE 120. The CSI-RS can be configured to be aperiodic (e.g., using DCI). The third beam management procedure may include BS 110 transmitting one or more CSI-RS using a single transmit beam (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first and / or second beam management procedures). To enable UE 120 to perform receive beam scanning, BS 110 may use the transmit beam to transmit CSI-RS multiple times within the same RS resource set (e.g., using repetition), allowing UE 120 to scan through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first and / or second beam management procedures). The third beam management process enables BS 110 and / or UE 120 to select the optimal receive beam based at least in part on reported measurements received from UE 120 (e.g., reported measurements of the CSI-RS of the transmit beam using one or more receive beams).

[0102] As indicated above, Figure 5This is provided as an example of a beam management process. Other examples of beam management processes may be provided relative to... Figure 5 The examples described are different. For example, UE 120 and BS 110 may perform a third beam management procedure before performing a second beam management procedure, and / or UE 120 and BS 110 may perform a similar beam management procedure to select the UE transmit beam.

[0103] Figure 6 This is a diagram illustrating example 600 of beam management according to this disclosure. As shown, the UE can initially be in an RRC idle state or an RRC inactive state. The UE can perform initial access and can perform beam management after entering an RRC connected state due to initial access. The UE can perform beam fault detection (BFD), and the UE can perform beam fault recovery (BFR) at least in part based on BFD. When BFR fails, the UE can declare a radio link failure (RLF).

[0104] In some examples, initial access may involve SSB wide-beam scanning. In some examples, initial access may involve contention-based random access (CBRA).

[0105] In some examples, beam management may include P1, P2, and / or P3 beam management procedures as described herein. In some examples, beam management may include U1, U2, and / or U3 beam management procedures, which may be based on SRS. The P1, P2, and / or P3 beam management procedures may be downlink beam management procedures, and the U1, U2, and / or U3 beam management procedures may be uplink beam management procedures. In some examples, beam management may be based on Layer 1 Reference Signal Received Power (L1-RSRP) measurements. L1-RSRP measurements may be reported by the UE, or L1-RSRP measurements may be measured by the UE. L1-RSRP measurements reported by the UE can be used to perform inference at the network node. L1-RSRP measurements measured by the UE can be used to perform inference at the UE. In some examples, beam management may be based on one or more Transmit Configuration Indication (TCI) states of the beam.

[0106] In some examples, beam management may involve one or more of the following: Layer 1 signal-to-interference-plus-noise ratio (L1-SINR) reporting, overhead and latency reduction (e.g., beam updates based on component carrier groups (CC groups) and / or faster uplinks). In some examples, beam management may involve further latency and efficiency enhancements (e.g., unified TCI state, Layer 1 (L1) / Layer 2 (L2) centered mobility, dynamic TCI updates, uplink multi-panel selection, maximum permissible exposure (MPE) mitigation, further beam management latency reductions, etc.), high-speed train (HST) / single-frequency network (SFN) scenarios, beam management for multiple transmit and receive points (mTRP), etc.

[0107] The UE can perform BFD and BFR for the primary cell (Pcell) and / or BFR for both primary and secondary cells (PScells). For example, the UE can perform BFD via the BFD Reference Signal (BFD-RS) and PDCCH Block Error Rate (BLER), perform BFR based on Contention-Free Random Access (CFRA), and so on. Additionally or alternatively, the UE can perform BFD and BFR for the secondary cell (Scell). For example, the UE can perform BFD for the Scell ​​by sending a link recovery request via a Scheduling Request (SR) and / or by receiving and receiving MAC-CE messages.

[0108] As indicated above, Figure 6 This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. Figure 6 The examples described are different.

[0109] One or more AI / ML models can be used to facilitate wireless communication tasks. The lifecycle management of AI / ML models can involve model training, model deployment, model inference, model monitoring, and model updates. Model training can involve AI / ML model training (e.g., offline training), validation and / or testing, etc. AI / ML model training can also involve data preparation based on training data delivered by data collection functions (e.g., data preprocessing, data cleaning, data formatting and / or transformation, etc.). Model deployment can include (e.g., deploying the AI / ML model at the UE or network node).

[0110] Model inference can involve feeding inferred data as input to an AI / ML model and obtaining the model's inference output (e.g., prediction, classification, estimation, and / or decision-making). In some cases, model inference can involve providing model performance feedback to the model training function. Model inference can also involve performing data preparation based on the inferred data (e.g., data preprocessing, data cleaning, data formatting, and / or transformation, etc.).

[0111] Model monitoring can involve monitoring the AI / ML model for performance metrics, such as the frequency and / or extent to which predictions generated by the AI / ML model are correct. For example, poor performance of the AI / ML model (e.g., when the accuracy of the AI / ML model's predictions drops below a threshold) can trigger a fallback to a non-AI / ML model. Model updates can involve retraining the AI / ML model or switching to a different AI / ML model. In some examples, model monitoring can trigger model updates.

[0112] AI / ML-based predictive beam management can involve beam management using AI / ML. One problem with traditional beam management processes is identifying beam quality / faults via measurements, which can require significant power / overhead to achieve good performance. Furthermore, beam accuracy can be limited by constraints regarding power / overhead, and latency / throughput can be affected by beam recovery efforts. AI / ML-based predictive beam management can provide predictive beam management in the spatial (SD), temporal (TD), and / or frequency (FD) domains, and may lead to reduced latency and overhead and / or improved beam selection accuracy.

[0113] For AI / ML-based beam management, both a first case and a second case of beam management can be supported for characterization and baseline performance evaluation. In the first case, SD downlink beam prediction for beam set A can be at least partially based on measurements from beam set B. In the second case, temporal downlink beam prediction for beam set A can be at least partially based on historical measurements from beam set B. Therefore, set A can correspond to the output of an ML model, and set B can correspond to the input of a model. Beams in set A and set B can be within the same frequency range.

[0114] For the first scenario, a first alternative and a second alternative can be defined. In the first alternative, beams in set B may be a subset of beams in set A. The number of beams in set A and the number of beams in set B can be defined. Beams in set B can be determined from beams in set A, at least in part, based on a fixed or random pattern. In the second alternative, beams in set A may differ from beams in set B (e.g., beams in set B may not be a subset of beams in set A). For example, beams in set A may be associated with narrow beams, and beams in set B may be associated with wide beams. The number of beams in set A and the number of beams in set B can be defined. Quasi-colocation (QCL) relationships can be defined between beams in set A and beams in set B. For both the first and second alternatives, set A may be associated with downlink beam prediction, and set B may be associated with downlink beam measurement. Codebook constructions for set A and set B can be defined.

[0115] For UE-side AI / ML models (e.g., AI / ML models deployed on the UE), L1 signaling can be used to report AI / ML model inference information to network nodes. For example, in a first case, L1 signaling can report beams based on the AI / ML model inference output and / or the L1-RSRP corresponding to the beam. In a second case, L1 signaling can be used to report beams for N future time instances based on the AI / ML model inference output, the L1-RSRP corresponding to the beam, and / or explicit or implicit information regarding one or more timestamps corresponding to the reported beam.

[0116] At least three alternative scenarios for monitoring the AI / ML model on the UE side can be defined using potential down-selection. These alternative scenarios can be applied to both the first and second scenarios. The first alternative scenario can involve UE-side model monitoring. For example, the UE can monitor performance metrics of the AI / ML model and determine whether to perform an operation (e.g., model selection, model activation, model deactivation, model switching, rollback, etc.) based on the monitoring. The second alternative scenario can involve network-side model monitoring. For example, the network can monitor performance metrics of the AI / ML model and determine whether to perform an operation (e.g., model selection, model activation, model deactivation, model switching, rollback, etc.) based on the monitoring. The third alternative scenario can involve hybrid model monitoring. For example, the UE can monitor performance metrics of the AI / ML model, and the network can determine whether to perform an operation (e.g., model selection, model activation, model deactivation, model switching, rollback, etc.) based on the monitoring.

[0117] In the first and / or second scenario, for the network-side AI / ML model, the network can perform model monitoring (e.g., "network-side model monitoring"). For example, the network can monitor performance metrics of the AI / ML model and determine whether to perform an action based on the monitoring (e.g., model selection, model activation, model deactivation, model switching, rollback, etc.). In this example, beamforming can occur, and a report for model monitoring can be generated.

[0118] In the first and / or second scenarios, L1 beam reporting can be enhanced for network-side AI / ML model inference. For example, the UE can report measurements of more than four beams in a single reporting instance. Other L1 reporting enhancements can also be implemented.

[0119] AI / ML-based predictive beam management can generate confidence levels (e.g., probabilities) associated with the corresponding predicted beams. However, reporting confidence levels (e.g., from the UE to the network node) may involve additional overhead for transmitting indications of the confidence levels. This additional overhead may consume time and / or frequency resources and may thus cause latency. Furthermore, the UE and network node may use computational and / or power resources to manage the confidence levels (e.g., to transmit, receive, and / or process the confidence levels).

[0120] One approach to mitigate the overhead and resource utilization issues introduced by confidence levels is for the UE to report only one predicted beam and its associated confidence level (e.g., the predicted beam with the highest associated confidence level among all predicted beams). However, reporting only one predicted beam may exclude information that would improve the performance of the predicted beam if included in the report. For example, the report would exclude information about other predicted beams. Therefore, including only one predicted beam may degrade beam prediction performance. One approach to avoid degraded beam prediction performance is for the UE to report all predicted beams and their associated confidence levels. While this approach helps ensure that soft information (e.g., confidence levels) is communicated to the network, reporting will be associated with high overhead, as discussed above.

[0121] Figure 7 This is an illustration of example 700, illustrating the transmission of a predicted beam report based on at least one confidence level of at least one predicted beam, according to this disclosure. Figure 7 As shown, BS 110 and UE 120 can communicate with each other.

[0122] As indicated by reference numeral 710 in the attached figure, BS 110 can output beam report configuration, and UE 120 can receive beam report configuration. The beam report configuration (and / or other configurations discussed herein) can be configured via RRC, semi-statically updated via MAC-CE, or dynamically activated or deactivated via DCI.

[0123] As shown by reference numeral 720 in the attached figure, according to the beam report configuration, UE 120 can transmit a predicted beam report (e.g., a Channel State Information (CSI) report), and BS 110 can obtain the predicted beam report, which includes an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. UE 120 can transmit the predicted beam report at least partially based on at least one confidence level, and BS 110 can obtain the predicted beam report at least partially based on at least one confidence level. For example, UE 120 can include an indication of at least one predicted beam in the predicted beam report based on at least one confidence level. In some examples, UE 120 can exclude indications of other predicted beams from the predicted beam report based on other confidence levels of other predicted beams.

[0124] A confidence level can indicate the probability (e.g., chance, determinism, etc.) of selecting a predicted beam from one or more predicted beams. For example, a confidence level can indicate the predicted signal strength of a predicted beam relative to any other predicted beam. A confidence level can be a soft metric that can be used to evaluate the quality of a prediction. The selection of a beam with a corresponding confidence level may be more reliable (e.g., less noisy) compared to hard-decision beam prediction and selection (e.g., beam selection without an associated confidence level).

[0125] UE 120 can use the AI / ML model deployed at UE 120 as described above to generate predicted beam and confidence levels. UE 120 can generate a predicted beam report based on the output of the AI / ML model (e.g., determine the content of the predicted beam report). For example, the AI / ML model can output predicted beam and confidence levels, and UE 120 can include the predicted beam and confidence levels in the predicted beam report.

[0126] Transmitting and receiving predicted beam reports based on confidence levels allows the predicted beam reports to include indications of predicted beams that are likely to be selected for uplink and / or downlink transmission (e.g., those with higher associated confidence levels) and / or exclude indications of any predicted beams that are unlikely to be selected for uplink and / or downlink transmission (e.g., those with lower associated confidence levels). Therefore, predicted beam reports can save additional overhead and resources by indicating predicted beams that are more relevant to beam selection while excluding indications of less relevant predicted beams.

[0127] As indicated above, Figure 7 This is provided as an example. Other examples may be provided relative to... Figure 7The examples described are different.

[0128] Figure 8 Examples 800 and 810 illustrate multiple predicted beams and associated confidence levels according to this disclosure. The multiple predicted beams and confidence levels can be generated by an AI / ML model deployed at the UE 120 as described above. In examples 800 and 810, the UE 120 can determine which predicted beams to include in the predicted beam report. The number of predicted beams indicated in a given predicted beam report can vary across predicted beam reports depending on the confidence level. For example, the number of predicted beams indicated in the predicted beam report in example 800 can differ from the number of predicted beams indicated in the predicted beam report in example 810.

[0129] In Example 800, the predicted beam 3 has the highest confidence level (26%) among the predicted beams 1-8. However, if UE 120 only wants to report the predicted beam 3 (e.g., to save overhead), the predicted beam report will exclude the predicted beam 4 (25% confidence level) and the predicted beam 5 (25% confidence level). Therefore, although the confidence levels of the predicted beams 4 and 5 are relatively close to the confidence level of the predicted beam 3 (here, 1% away), the indication to exclude the predicted beams 4 and 5 from the predicted beam report may cause BS 110 to ignore the predicted beams 4 and 5 (e.g., not considering selecting the predicted beam 4 or the predicted beam 5), even if the predicted beam 4 or the predicted beam 5 would provide a higher quality beam compared to the predicted beam 3 if it were ultimately selected. Therefore, in Example 800, UE 120 can report three or four predicted beams with the highest corresponding confidence levels of predicted beams 1-8, instead of only reporting predicted beam 3. For example, UE 120 can report predicted beam 3, predicted beam 4, and predicted beam 5—which allows BS 110 to consider selecting the relevant predicted beams—and exclude the remaining predicted beams from the report—which can save overhead.

[0130] In Example 810, predicted beam 2 has the highest confidence level (92%) among predicted beams 1-8, and predicted beams 1 and 3-8 have corresponding confidence levels that sum to the remaining 8%. In this case, given the relatively low confidence levels of predicted beams 1 and 3-8, indicating in the predicted beam report that any predicted beam other than predicted beam 2 might introduce excessive overhead (e.g., to provide beam selection information to BS 110) is problematic. Therefore, in Example 810, UE 120 could report only predicted beam 2 (and the associated 92% confidence level) (which saves overhead) instead of reporting multiple predicted beams.

[0131] In some examples, the number of predicted beams indicated in the predicted beam report may be based at least in part on whether the total number of corresponding confidence levels meets a threshold. For example, the number of predicted beams indicated in the report and the corresponding confidence levels may depend on the total number of confidence levels indicated in the predicted beam report (e.g., total confidence, total probability, etc.) meeting a target confidence level threshold.

[0132] For example, the network (e.g., BS 110) can configure UE 120 to report the identifiers of the predicted beams with the highest confidence levels, the total number of which satisfies a threshold. In some examples, UE 120 may also report the reference signal received power (RSRP) and / or signal-to-interference-plus-noise ratio (SINR) of the predicted beams. The network can configure UE 120 to report the top K predicted beams (e.g., beam indices or RSRPs) whose combination of predicted beams has a confidence level (e.g., sum probability) higher than a threshold (e.g., 90%). For example, if the threshold is set to 90%, in example 800, UE 120 may report predicted beams 3-6 (excluding predicted beams 1, 2, 7, and 8), and in example 810, UE 120 may report only predicted beam 2.

[0133] Including a variable number of beams and corresponding confidence levels in each predicted beam report can reduce reporting overhead while ensuring that sufficient soft beam prediction information is associated with each predicted beam report, and thus ensuring that information about the predicted beams that are more likely to be selected is reported to the network.

[0134] In some examples, the threshold can be configurable (e.g., adjustable). For example, the network can configure the threshold as any suitable percentage (e.g., 85%, 90%, 95%, etc.). The configurability of the threshold provides control over the amount of overhead / resources involved in the transmission and / or processing of predicted beam reports. For example, increasing the threshold can increase the number of predicted beams reported to BS110. Decreasing the threshold can reduce the overhead involved in transmitting predicted beam reports.

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

[0136] In some examples, BS 110 can configure UE 120 via beam reporting configuration to receive a first portion of a beam report predicted via a first resource report and a second portion of a beam report predicted via a second resource report (e.g., the beam prediction report can be divided into at least two portions). Therefore, UE 120 can transmit the first portion of the predicted beam report via the first resource, and BS 110 can receive the first portion of the predicted beam report via the first resource and transmit the second portion of the predicted beam report via the second resource. Reporting the predicted beam report in multiple portions can inform BS 110 of the number of predicted beams to be reported, and thus resolve potential ambiguities regarding the size of the payload.

[0137] In some examples, the first part of the predicted beam report includes an indication of the payload size for the second part of the predicted beam report. For example, the network can configure UE 120 to report the first K predicted beams, the confidence level of which the combination of these predicted beams meets a threshold in a two-part predicted beam report (e.g., a two-part CSI report). The indication of the payload size for the second part can be the proposed payload size.

[0138] The beam report configuration can configure the payload size of the first part of the predicted beam report. For example, the first part of the predicted beam report can have a fixed payload size based on network configuration (e.g., CSI report settings). UE 120 can be configured to report the first N predicted beams (where N is less than K) and their corresponding confidence levels in the predicted beam report. Configuring the payload size of the first part of the predicted beam report in the beam report configuration (e.g., configuring the payload size as a fixed configuration) can facilitate scheduling and minimize conflicts with other transmissions (e.g., other reports).

[0139] The first part of the predicted beam report can indicate whether a second part of the predicted beam report should be sent. For example, if N equals K, all predicted beams in the predicted beams to be sent can be sent in the first part, and UE 120 can avoid sending the second part. The first part can explicitly or implicitly indicate whether UE 120 wants to send the second part (and whether BS 110 wants to receive the second part). Therefore, BS 110 can be notified (e.g., explicitly or implicitly) whether the second part should be sent.

[0140] For example, the first part of the predicted beam report may include an explicit indication (e.g., whether to report the second part) that the UE 120 wants to send the second part of the predicted beam report (and the BS 110 wants to receive the second part of the predicted beam report). For example, the explicit indication may be a 1-bit indicator included in the first part (e.g., where "0" indicates to send the second part and "1" indicates not to send the second part, or where "0" indicates not to send the second part and "1" indicates to send the second part).

[0141] The first part can implicitly instruct the UE to send the second part, at least in part, based on the fact that the total number of any confidence levels indicated in the first part of the predicted beam report does not meet a threshold. For example, the BS 110 can obtain the first part, determine that the sum of the confidence levels indicated in the first part is not equal to the threshold, and determine to send the second part. Alternatively, the BS 110 can obtain the first part, determine that the confidence levels indicated in the first part meet or exceed the threshold, and determine not to send the second part.

[0142] The first part can indicate the configuration details of the second part. For example, as discussed above, the first part can indicate the payload size of the second part. In some examples, the indication of the payload size of the second part may include an indication of the number (and associated confidence level) of one or more predicted beams to be indicated in the second part. Therefore, the indication of the payload size of the second part can be communicated to BS 110.

[0143] In some examples, the two beam prediction reports can be configured and / or multiplexed on one or more PUSCH resources. Configuring beam prediction reports on PUSCH resources allows UE 120 to send beam prediction reports without excessive overhead, as PUSCH allows for variable payloads.

[0144] Figure 9Examples 900 and 910 illustrate, according to this disclosure, that a first portion of a predicted beam report includes an indication of the payload size of a second portion of a predicted beam report. Examples 900 and 910 illustrate how UE 120 can transmit the second portion, at least in part, based on whether the total number of one or more confidence levels indicated in the first portion of the predicted beam report meets a threshold.

[0145] Example 900 relates to Example 800. In Example 900, UE 120 may report the first two predicted beams and their associated confidence levels (e.g., N=2) in the first part of the predicted beam report. As shown, because the total confidence level of the first two predicted beams is 51%, which is less than the 90% threshold, the first part may indicate that a second part of the predicted beam report will be sent. In some examples, UE 120 may also indicate in the first part that the second part will report two additional predicted beams to meet the 90% threshold (because the total confidence level of the first four predicted beams is 91%, which is greater than the 90% threshold).

[0146] Example 910 relates to Example 810. In Example 910, UE 120 may report the first two predicted beams and their associated confidence levels (e.g., N=2) in the first part of the predicted beam report. As shown, because the total confidence level of the first two predicted beams is greater than 90% (e.g., 94%, in the case where the second highest confidence level is 2%), which is greater than the 90% threshold, the first part may indicate that the second part of the predicted beam report will not be sent.

[0147] As indicated above, Figure 9 This is provided as an example. Other examples may be provided relative to... Figure 9 The examples described are different.

[0148] In some examples, the beam reporting configuration can configure the payload size of the second part of the predicted beam report. For example, the network can configure UE 120 to report the first N predicted beams in the first part and the remaining KN predicted beams in the second part. Therefore, the second part can have a pre-configured or fixed payload size. In some examples, UE 120 can also report the L1-RSRP and / or L1-SINR of the predicted beams. Configuring the payload size of the second part in the beam reporting configuration can facilitate scheduling and minimize conflicts with other transmissions (e.g., other reports), because BS 110 can configure the payload size well before the second part is scheduled for transmission (e.g., BS 110 can configure the payload size of the second part before receiving the first part).

[0149] Figure 10 This is an illustration of Example 1000, which illustrates the payload size of a second portion of a predicted beam report configured according to the present disclosure. In Example 1000, UE 120 can be configured to report the first N predicted beams in a first portion of the predicted beam report. UE 120 can transmit the second portion based at least in part on whether the total number of one or more confidence levels indicated in the first portion of the predicted beam report meets a threshold. For example, if the total number of confidence levels does not meet the threshold, UE 120 can transmit the second portion. If the total number of confidence levels meets the threshold, UE 120 can avoid transmitting the second portion.

[0150] As indicated above, Figure 10 This is provided as an example. Other examples may be provided relative to... Figure 10 The examples described are different.

[0151] In some examples, the beam report configuration for the first and second portions of the predicted beam report may include an indication of a first priority associated with the first portion and an indication of a second priority associated with the second portion. UE 120 can transmit the first portion according to the first priority and the second portion according to the second priority.

[0152] By assigning priorities to interference reports, network nodes can help UE 120 resolve conflicts when interference reports clash with other reports (e.g., HARQ-ACK, PUSCH, CSI resources, etc.). In some examples, prioritizing interference reports can help UE 120 decide whether to discard the interference report or reuse it with other uplink communications (e.g., reports).

[0153] In some examples, BS 110 may output instructions for one or more priority rules, and UE 120 may receive instructions for one or more priority rules. Priority rules may indicate how to resolve conflicts between a first portion of a predicted beam report and another report (e.g., channel state or other uplink report) based at least in part on a first priority. Additionally or alternatively, priority rules may indicate how to resolve conflicts between a second portion of a predicted beam report and another report (e.g., channel state or other uplink report) based at least in part on a second priority. Priority rules can help ensure that BS 110 and UE 120 agree on the outcome regarding conflicts.

[0154] In some examples, UE 120 may transmit a first portion of the predicted beam report based at least partially on a first quantization table and a second portion of the predicted beam report based at least partially on a second quantization table, and BS 110 may obtain the first portion of the predicted beam report based at least partially on the first quantization table and the second portion of the predicted beam report based at least partially on the second quantization table. The quantization table may indicate a number of quantization bits to be allocated for a portion of the predicted beam report. For example, the predicted beam report may carry this number of quantization bits to indicate the predicted beam and the associated confidence level. In some examples, the quantization table may be defined in a standard specification. Transmitting and obtaining the first and second portions based on the first and second quantization tables allows BS 110 to control the number of quantization bits allocated for the predicted beam report, which may further reduce the overhead involved in transmitting the predicted beam report.

[0155] For example, a first quantization table can define a first number of quantization bits, and a second quantization table can define a second number of quantization bits. For example, UE 120 can use the first number of quantization bits to transmit a first portion of the predicted beam report and use the second number of quantization bits to transmit a second portion of the predicted beam report, and BS 110 can use the first number of quantization bits to obtain the first portion of the predicted beam report and use the second number of quantization bits to obtain the second portion of the predicted beam report. For example, the first number can be greater than the second number (e.g., the first portion can be transmitted using more quantization bits than the second portion).

[0156] Using a first number of quantization bits and a second number of quantization bits to transmit and receive the first part and the second part respectively allows the first part and the second part to use different numbers of quantization bits. For example, BS 110 can configure UE 120 to transmit the first part using more quantization bits, which can carry an indication of a predicted beam with a higher confidence level than the predicted beam indicated in the second part.

[0157] Figure 11 This is an illustration of example 1100 of a first predicted beam report and a second predicted beam report according to the present disclosure. As shown, in some examples, BS 110 may output a first beam report configuration and a second beam report configuration, and UE 120 may receive the first beam report configuration and the second beam report configuration. UE 120 may transmit a first predicted beam report (e.g., a CSI report) according to the first beam report configuration and transmit a second predicted beam report according to the second beam report configuration, and BS 110 may obtain the first predicted beam report according to the first beam report configuration and obtain the second predicted beam report according to the second beam report configuration. The first predicted beam report may include an indication of at least one first predicted beam and an indication of at least one first confidence level corresponding to the at least one first predicted beam. The second predicted beam report may include an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam.

[0158] Network entities can configure the payload size of the second predicted beam report to reduce overhead. For example, the payload size of the second predicted beam report can be configured (e.g., limited) based on the information to be indicated in the second predicted beam report (e.g., the number of predicted beams and confidence level).

[0159] UE 120 can be configured to report the identifier of the first predicted beam (e.g., the predicted beam with the highest associated confidence level) that meets a threshold across at least two predicted beam reports. In some examples, UE 120 may include one or more of the L1-RSRP or L1-SINR of the first predicted beam in the first predicted beam report and / or the second predicted beam report.

[0160] In some examples, the first beam report configuration can configure the payload size of the first predicted beam report. For example, BS 110 can configure UE 120 to report the first N beams in the first predicted beam report, which can have a fixed payload.

[0161] UE 120 may receive a second beam report configuration based at least in part on whether the total number of one or more confidence levels indicated in the first predicted beam report meets a threshold. For example, if the total number of confidence levels does not meet the threshold, UE 120 may send a second predicted beam report, which may include the remaining top K beams to be reported. If the total number of confidence levels meets the threshold, UE 120 may avoid sending the second predicted beam report, which may further reduce the overhead associated with sending predicted beam information.

[0162] In some examples, the first predicted beam report includes an indication of the payload size and / or structure of the second predicted beam report. For example, the indication of the payload size of the second predicted beam report includes an indication of the number of at least one predicted beam to be indicated in the second predicted beam report. The predicted beams indicated in the second predicted beam report may have an associated confidence level that meets a threshold (e.g., 90%) when added to the confidence level associated with the predicted beams indicated in the first predicted beam report. UE 120 may wait for BS 110 to configure the second predicted beam report before reporting the remaining predicted beams that meet the threshold.

[0163] As indicated above, Figure 11 This is provided as an example. Other examples may be provided relative to... Figure 11 The examples described are different.

[0164] Figure 12 A method 1200 for wireless communication by a UE (such as UE 120) is shown.

[0165] Method 1200 begins at 1210, where the receive beam report configuration is configured.

[0166] Then, method 1200 proceeds to step 1220, wherein a predicted beam report is transmitted according to a beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein transmitting the predicted beam report includes transmitting the predicted beam report at least in part based on at least one confidence level.

[0167] In one respect, the confidence level indicates the probability of selecting the at least one predicted beam from one or more predicted beams.

[0168] In one aspect, the number of one or more predicted beams, including the at least one predicted beam, indicated in the predicted beam report is based at least in part on whether the total number of one or more confidence levels including the at least one confidence level meets a threshold.

[0169] In one respect, the threshold is configurable.

[0170] In one aspect, the beam report configuration configures the UE to report a first portion of the predicted beam report via a first resource and a second portion of the predicted beam report via a second resource, and transmitting the predicted beam report includes: transmitting the first portion of the predicted beam report via the first resource; and transmitting the second portion of the predicted beam report via the second resource.

[0171] In one aspect, the first part of the predicted beam report includes an indication of the payload size of the second part of the predicted beam report.

[0172] In one aspect, the beam report configuration configures the payload size of the first part of the predicted beam report.

[0173] In one aspect, the first part of the predicted beam report includes an explicit indication that the UE will send the second part of the predicted beam report.

[0174] In one aspect, the first portion of the predicted beam report includes an indication that the UE will send the second portion of the predicted beam report based at least in part on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0175] In one aspect, the indication of the payload size in the second part of the predicted beam report includes an indication of the number of one or more predicted beams to be indicated in the second part of the predicted beam report.

[0176] In one aspect, the predicted beam report is configured on one or more PUSCH resources.

[0177] In one aspect, the beam report configuration configures the payload size of the second part of the predicted beam report.

[0178] In one aspect, sending the second portion of the predicted beam report includes sending the second portion of the predicted beam report based at least in part on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0179] In one aspect, the beam report configuration includes an indication of a first priority associated with the first portion of the predicted beam report and an indication of a second priority associated with the second portion of the predicted beam report, and sending the first portion of the predicted beam report includes: sending the first portion of the predicted beam report according to the first priority; and sending the second portion of the predicted beam report includes: sending the second portion of the predicted beam report according to the second priority.

[0180] In one aspect, method 1200 further includes receiving instructions on one or more priority rules, the one or more priority rules indicating how to resolve a conflict between the first portion of the predicted beam report and another report based at least in part on the first priority, or indicating how to resolve a conflict between the second portion of the predicted beam report and another report based at least in part on the second priority.

[0181] In one aspect, transmitting the first portion of the predicted beam report includes transmitting the first portion of the predicted beam report based at least in part on a first quantization table; and transmitting the second portion of the predicted beam report includes transmitting the second portion of the predicted beam report based at least in part on a second quantization table.

[0182] In one aspect, the first quantization table defines a first number of quantization bits, the second quantization table defines a second number of quantization bits, and transmitting the first portion of the predicted beam report includes transmitting the first portion of the predicted beam report using the first number of quantization bits, and transmitting the second portion of the predicted beam report includes transmitting the second portion of the predicted beam report using the second number of quantization bits.

[0183] In one aspect, the beam report configuration is a first beam report configuration, the predicted beam report is a first predicted beam report, the at least one predicted beam is at least one first predicted beam, and the at least one confidence level is at least one first confidence level, and the method 1200 further includes: receiving a second beam report configuration; and transmitting a second predicted beam report according to the second beam report configuration, the second predicted beam report including an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam, wherein transmitting the second predicted beam report includes: transmitting the second predicted beam report at least in part based on the at least one second confidence level.

[0184] In one aspect, receiving the second beam report configuration includes: receiving the second beam report configuration based at least in part on the fact that the total number of one or more first confidence levels indicated in the first predicted beam report does not meet a threshold.

[0185] In one aspect, the first beam report configuration configures the payload size of the first predicted beam report.

[0186] In one aspect, the first predicted beam report includes an indication of the payload size of the second predicted beam report.

[0187] In one aspect, the indication of the payload size reported for the second predicted beam includes an indication of the number of the at least one second predicted beam.

[0188] In one aspect, method 1200 or any aspect thereof may be made by means of a device (such as...) Figure 14 The communication device 1400 is used to perform the method 1200, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1400 is described in more detail below.

[0189] It should be noted that Figure 12 This is merely one example of a method, and other methods with fewer, additional, or alternative steps are possible according to this disclosure.

[0190] Figure 13 The diagram illustrates the use of network entities (such as BS 110 or as relative to...) Figure 3 The method for wireless communication using a decomposed base station (discussed) 1300.

[0191] Method 1300 begins at 1310, where the output beam report configuration is set.

[0192] Then, method 1300 proceeds to step 1320, wherein a predicted beam report is obtained according to a beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein obtaining the predicted beam report includes: obtaining the predicted beam report based at least in part on at least one confidence level.

[0193] In one respect, the confidence level indicates the probability of selecting the at least one predicted beam from one or more predicted beams.

[0194] In one aspect, the number of one or more predicted beams, including the at least one predicted beam, indicated in the predicted beam report is based at least in part on whether the total number of one or more confidence levels including the at least one confidence level meets a threshold.

[0195] In one respect, the threshold is configurable.

[0196] In one aspect, the beam reporting configuration includes an instruction to report a first portion of the predicted beam report via a first resource and a second portion of the predicted beam report via a second resource, wherein obtaining the predicted beam report includes: obtaining the first portion of the predicted beam report via the first resource; and obtaining the second portion of the predicted beam report via the second resource.

[0197] In one aspect, the first part of the predicted beam report includes an indication of the payload size of the second part of the predicted beam report.

[0198] In one aspect, the beam report configuration configures the payload size of the first part of the predicted beam report.

[0199] In one aspect, the first part of the predicted beam report includes an explicit indication that the network entity wants to obtain the second part of the predicted beam report.

[0200] In one aspect, the first portion of the predicted beam report includes an indication that the network entity will obtain the second portion of the predicted beam report based at least in part on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0201] In one aspect, the indication of the payload size in the second part of the predicted beam report includes an indication of the number of one or more predicted beams to be indicated in the second part of the predicted beam report.

[0202] In one aspect, the predicted beam report is configured on one or more PUSCH resources.

[0203] In one aspect, the beam report configuration configures the payload size of the second part of the predicted beam report.

[0204] In one aspect, obtaining the second portion of the predicted beam report includes obtaining the second portion of the predicted beam report based at least in part on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0205] In one aspect, the beam reporting configuration includes an indication of a first priority associated with the first portion of the predicted beam report and an indication of a second priority associated with the second portion of the predicted beam report. Obtaining the first portion of the predicted beam report includes obtaining the first portion of the predicted beam report according to the first priority. Obtaining the second portion of the predicted beam report includes obtaining the second portion of the predicted beam report according to the second priority.

[0206] In one aspect, method 1300 further includes: outputting indications for one or more priority rules, the one or more priority rules indicating how to resolve a conflict between a first portion of the predicted beam report and another report based at least in part on the first priority, or indicating how to resolve a conflict between a second portion of the predicted beam report and another report based at least in part on the second priority.

[0207] In one aspect, obtaining the first portion of the predicted beam report includes obtaining the first portion of the predicted beam report based at least in part on a first quantization table; and obtaining the second portion of the predicted beam report includes obtaining the second portion of the predicted beam report based at least in part on a second quantization table.

[0208] In one aspect, the first quantization table defines a first number of quantization bits, the second quantization table defines a second number of quantization bits, obtaining the first portion of the predicted beam report includes: using the first number of quantization bits to obtain the first portion of the predicted beam report, and obtaining the second portion of the predicted beam report includes: using the second number of quantization bits to obtain the second portion of the predicted beam report.

[0209] In one aspect, the beam report configuration is a first beam report configuration, the predicted beam report is a first predicted beam report, the at least one predicted beam is at least one first predicted beam, and the at least one confidence level is at least one first confidence level. Method 1300 further includes: outputting a second beam report configuration; and obtaining a second predicted beam report based on the second beam report configuration, the second predicted beam report including an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam, wherein obtaining the second predicted beam report includes: obtaining the second predicted beam report at least in part based on the at least one second confidence level.

[0210] In one aspect, outputting the second beam report configuration includes: outputting the second beam report configuration at least in part based on the fact that the total number of one or more first confidence levels indicated in the first predicted beam report does not meet a threshold.

[0211] In one aspect, the first beam report configuration configures the payload size of the first predicted beam report.

[0212] In one aspect, the first predicted beam report includes an indication of the payload size of the second predicted beam report.

[0213] In one aspect, the indication of the payload size reported for the second predicted beam includes an indication of the number of the at least one second predicted beam.

[0214] In one aspect, method 1300 or any aspect thereof may be made by means of a device (such as...) Figure 15 The communication device 1500 performs the execution, and the device includes various components capable of operating, being configured, or adapted to perform the method 1300. The communication device 1500 is described in more detail below.

[0215] It should be noted that Figure 13 This is just one example of a method, and other methods that include fewer, additional, or alternative steps may be consistent with this disclosure.

[0216] Figure 14 This is a diagram illustrating an example of a specific implementation of the code and circuitry for a communication device 1400 according to this disclosure. The communication device 1400 may be a UE, or a UE may include the communication device 1400.

[0217] Communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or receiver). Transceiver 1408 is configured to transmit and receive signals for communication device 1400 via antenna 1410, such as various signals as described herein. Processing system 1402 may be configured to perform processing functions of communication device 1400, including processing signals received by and / or to be transmitted by communication device 1400.

[0218] Processing system 1402 includes one or more processors 1420. In various aspects, the one or more processors 1420 may represent one or more of a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and / or a controller / processor 280, as relative to... Figure 2 As described. One or more processors 1420 are coupled to computer-readable medium / memory 1430 via bus 1406. In various respects, computer-readable medium / memory 1430 may represent memory 282, such as relative to... Figure 2 As described. In some aspects, the computer-readable medium / memory 1430 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1420, cause one or more processors 1420 to perform actions related to... Figure 12 The described method 1200 or any aspect thereof. It should be noted that references to processors performing the functions of communication device 1400 may include one or more processors performing those functions of communication device 1400.

[0219] like Figure 14 As shown, the communication device 1400 may include circuitry (circuit 1435) for receiving beam report configurations.

[0220] like Figure 14 As shown, the communication device 1400 may include code (code 1440) for receiving beam report configuration stored in a computer-readable medium / memory 1430.

[0221] like Figure 14 As shown, the communication device 1400 may include circuitry for configuring the transmission of a predicted beam report based on a beam report configuration. The predicted beam report includes an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. Transmitting the predicted beam report includes: transmitting the predicted beam report (circuit 1445) based at least in part on at least one confidence level.

[0222] like Figure 14 As shown, the communication device 1400 may include code stored in a computer-readable medium / memory 1430 for configuring the transmission of a predicted beam report according to the beam report configuration. The predicted beam report includes an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. The transmission of the predicted beam report includes: transmitting the predicted beam report at least in part based on at least one confidence level (code 1450).

[0223] The various components of the communication device 1400 can provide for performing tasks related to... Figure 12 The described method 1200 or any components related thereto. For example, components for transmitting, conveying, or outputting for transmission may include the transceiver 254 and / or antenna 252 of UE 120, and / or Figure 14 The communication device 1400 includes a transceiver 1408 and an antenna 1410. Components for receiving or acquiring data may include a transceiver 254 and / or an antenna 252 of the UE 120, and / or... Figure 14 The transceiver 1408 and antenna 1410 of the communication device 1400.

[0224] Figure 14 This is provided as an example. Other examples can be combined with it. Figure 14 The examples described are different.

[0225] Figure 15 This is a diagram illustrating an example of a specific implementation of the code and circuitry for a communication device 1500 according to this disclosure. The communication device 1500 may be a network entity (such as BS 110 or as per [other documentation]). Figure 3 The described decomposed base station, or network entity, may include communication equipment 1500.

[0226] Communication device 1500 includes a processing system 1502 coupled to a transceiver 1508 (e.g., a transmitter and / or receiver). Transceiver 1508 is configured to transmit and receive signals for communication device 1500 via antenna 1510, such as various signals as described herein. Network interface 1512 is configured to transmit via a communication link (such as those described herein, such as relative to...). Figure 3 The described backhaul link, midhaul link, and / or fronthaul link receive and transmit signals for communication device 1500. Processing system 1502 can be configured to perform processing functions of communication device 1500, including processing signals received by and / or to be transmitted by communication device 1500.

[0227] Processing system 1502 includes one or more processors 1520. In various aspects, the one or more processors 1520 may represent one or more of the following: receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240, as relative to... Figure 2 As described. One or more processors 1520 are coupled to computer-readable medium / memory 1530 via bus 1506. In various aspects, computer-readable medium / memory 1530 may represent memory 242, such as relative to... Figure 2 As described. In some aspects, the computer-readable medium / memory 1530 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1520, cause one or more processors 1520 to perform relative to Figure 13 The method 1300 described or any aspect thereof. It should be noted that references to processors performing the functions of communication device 1500 may include one or more processors performing those functions of communication device 1500.

[0228] like Figure 15 As shown, the communication device 1500 may include circuitry (circuit 1535) for outputting beam reporting configuration.

[0229] like Figure 15 As shown, the communication device 1500 may include code (code 1540) for output beam report configuration stored in a computer-readable medium / memory 1530.

[0230] like Figure 15As shown, the communication device 1500 may include circuitry for obtaining a predicted beam report according to a configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein obtaining the predicted beam report includes obtaining the predicted beam report (circuit 1545) based at least in part on at least one confidence level.

[0231] like Figure 15 As shown, the communication device 1500 may include code stored in a computer-readable medium / memory 1530 for obtaining a predicted beam report according to a configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein obtaining the predicted beam report includes: obtaining the predicted beam report at least in part based on at least one confidence level (code 1550).

[0232] The various components of the communication device 1500 can provide for performing relative to Figure 13 The described method 1300 or any components related thereto. For example, components for transmitting, conveying, or outputting for transmission may include the transceiver 232 and / or antenna 234 of BS 110, and / or Figure 15 The communication device 1500 includes a transceiver 1508 and an antenna 1510. Components for receiving or acquiring data may include the transceiver 232 and / or antenna 234 of BS 110, and / or... Figure 15 The transceiver 1508 and antenna 1510 of the communication equipment 1500.

[0233] Figure 15 This is provided as an example. Other examples can be combined with it. Figure 15 The examples described are different.

[0234] The following provides an overview of some aspects of this disclosure:

[0235] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving a beam report configuration; and transmitting a predicted beam report according to the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein transmitting the predicted beam report comprises: transmitting the predicted beam report at least in part based on the at least one confidence level.

[0236] Aspect 2: According to the method of aspect 1, wherein the confidence level indicates the probability of selecting the at least one predicted beam from one or more predicted beams.

[0237] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the number of one or more predicted beams including the at least one predicted beam indicated in the predicted beam report is based at least in part on whether the total number of one or more confidence levels including the at least one confidence level meets a threshold.

[0238] Aspect 4: According to the method of aspect 3, the threshold is configurable.

[0239] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the beam report configuration configures the UE to report a first portion of the predicted beam report via a first resource and a second portion of the predicted beam report via a second resource, and wherein sending the predicted beam report includes: sending the first portion of the predicted beam report via the first resource; and sending the second portion of the predicted beam report via the second resource.

[0240] Aspect 6: According to the method of aspect 5, wherein the first portion of the predicted beam report includes an indication of the payload size of the second portion of the predicted beam report.

[0241] Aspect 7: The method according to aspect 6, wherein the beam report configuration configures the payload size of the first portion of the predicted beam report.

[0242] Aspect 8: According to the method of aspect 6, wherein the first portion of the predicted beam report includes an explicit indication that the UE wants to send the second portion of the predicted beam report.

[0243] Aspect 9: According to the method of aspect 6, wherein the first portion of the predicted beam report includes an indication that the UE will send the second portion of the predicted beam report at least in part based on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0244] Aspect 10: The method according to aspect 6, wherein the indication of the payload size of the second portion of the predicted beam report includes an indication of the number of one or more predicted beams to be indicated in the second portion of the predicted beam report.

[0245] Aspect 11: According to the method of aspect 6, wherein the predicted beam report is configured on one or more PUSCH resources.

[0246] Aspect 12: According to the method of aspect 5, wherein the beam report configuration configures the payload size of the second portion of the predicted beam report.

[0247] Aspect 13: According to the method of aspect 5, wherein sending the second portion of the predicted beam report comprises: sending the second portion of the predicted beam report at least in part based on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0248] Aspect 14: The method according to aspect 5, wherein the beam report configuration includes an indication of a first priority associated with a first portion of the predicted beam report and an indication of a second priority associated with a second portion of the predicted beam report, and wherein: sending the first portion of the predicted beam report includes: sending the first portion of the predicted beam report according to the first priority; and sending the second portion of the predicted beam report includes: sending the second portion of the predicted beam report according to the second priority.

[0249] Aspect 15: The method according to aspect 14, the method further comprising: receiving an instruction on one or more priority rules, the one or more priority rules indicating how to resolve a conflict between a first portion of the predicted beam report and another report based at least in part on a first priority, or indicating how to resolve a conflict between a second portion of the predicted beam report and another report based at least in part on a second priority.

[0250] Aspect 16: According to the method of aspect 5, wherein: sending the first portion of the predicted beam report includes: sending the first portion of the predicted beam report at least in part based on a first quantization table; and sending the second portion of the predicted beam report includes: sending the second portion of the predicted beam report at least in part based on a second quantization table.

[0251] Aspect 17: The method according to aspect 16, wherein the first quantization table defines a first number of quantization bits, and the second quantization table defines a second number of quantization bits, and wherein: transmitting the first portion of the predicted beam report comprises: transmitting the first portion of the predicted beam report using the first number of quantization bits; and transmitting the second portion of the predicted beam report comprises: transmitting the second portion of the predicted beam report using the second number of quantization bits.

[0252] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the beam report configuration is a first beam report configuration, the predicted beam report is a first predicted beam report, the at least one predicted beam is at least one first predicted beam, and the at least one confidence level is at least one first confidence level, the method further comprising: receiving a second beam report configuration; and transmitting a second predicted beam report according to the second beam report configuration, the second predicted beam report including an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam, wherein transmitting the second predicted beam report includes: transmitting the second predicted beam report at least in part based on the at least one second confidence level.

[0253] Aspect 19: The method according to aspect 18, wherein receiving the second beam report configuration includes: receiving the second beam report configuration based at least in part on the fact that the total number of one or more first confidence levels indicated in the first predicted beam report does not meet a threshold.

[0254] Aspect 20: The method according to aspect 18, wherein the first beam report configuration configures the payload size of the first predicted beam report.

[0255] Aspect 21: The method according to aspect 18, wherein the first predicted beam report includes an indication of the payload size of the second predicted beam report.

[0256] Aspect 22: According to the method of aspect 21, wherein the indication of the payload size reported for the second predicted beam includes an indication of the number of the at least one second predicted beam.

[0257] Aspect 23: A method for wireless communication performed by a network entity, the method comprising: outputting a beam report configuration; and obtaining a predicted beam report according to the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam, wherein obtaining the predicted beam report comprises: obtaining the predicted beam report at least in part based on the at least one confidence level.

[0258] Aspect 24: According to the method of aspect 23, wherein the confidence level indicates the probability of selecting the at least one predicted beam from one or more predicted beams.

[0259] Aspect 25: The method according to any one of Aspects 23 to 24, wherein the number of one or more predicted beams including the at least one predicted beam indicated in the predicted beam report is based at least in part on whether the total number of one or more confidence levels including the at least one confidence level meets a threshold.

[0260] Aspect 26: The method according to aspect 25, wherein the threshold is configurable.

[0261] Aspect 27: The method according to any one of Aspects 23 to 26, wherein the beam reporting configuration includes an indication to report a first portion of the predicted beam report via a first resource and a second portion of the predicted beam report via a second resource, and wherein obtaining the predicted beam report includes: obtaining the first portion of the predicted beam report via the first resource; and obtaining the second portion of the predicted beam report via the second resource.

[0262] Aspect 28: According to the method of aspect 27, wherein the first portion of the predicted beam report includes an indication of the payload size of the second portion of the predicted beam report.

[0263] Aspect 29: The method according to aspect 28, wherein the beam report configuration configures the payload size of the first portion of the predicted beam report.

[0264] Aspect 30: According to the method of aspect 28, wherein the first portion of the predicted beam report includes an explicit indication that the network entity wants to obtain the second portion of the predicted beam report.

[0265] Aspect 31: According to the method of aspect 28, wherein the first portion of the predicted beam report includes the network entity obtaining an indication of the second portion of the predicted beam report based at least in part on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0266] Aspect 32: The method according to aspect 28, wherein the indication of the payload size of the second portion of the predicted beam report includes an indication of the number of one or more predicted beams to be indicated in the second portion of the predicted beam report.

[0267] Aspect 33: The method according to aspect 28, wherein the predicted beam report is configured on one or more PUSCH resources.

[0268] Aspect 34: The method according to aspect 27, wherein the beam report configuration configures the payload size of the second portion of the predicted beam report.

[0269] Aspect 35: According to the method of aspect 27, wherein obtaining the second portion of the predicted beam report comprises: obtaining the second portion of the predicted beam report based at least in part on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

[0270] Aspect 36: The method according to aspect 27, wherein the beam report configuration includes an indication of a first priority associated with a first portion of the predicted beam report and an indication of a second priority associated with a second portion of the predicted beam report, and wherein: obtaining the first portion of the predicted beam report includes: obtaining the first portion of the predicted beam report according to the first priority; and obtaining the second portion of the predicted beam report includes: obtaining the second portion of the predicted beam report according to the second priority.

[0271] Aspect 37: The method according to aspect 36, the method further comprising: outputting an indication of one or more priority rules, the one or more priority rules indicating how to resolve a conflict between a first portion of the predicted beam report and another report based at least in part on a first priority, or indicating how to resolve a conflict between a second portion of the predicted beam report and another report based at least in part on a second priority.

[0272] Aspect 38: The method according to aspect 27, wherein: obtaining the first portion of the predicted beam report comprises: obtaining the first portion of the predicted beam report at least in part based on a first quantization table; and obtaining the second portion of the predicted beam report comprises: obtaining the second portion of the predicted beam report at least in part based on a second quantization table.

[0273] Aspect 39: The method according to aspect 38, wherein the first quantization table defines a first number of quantization bits, and the second quantization table defines a second number of quantization bits, and wherein: obtaining the first portion of the predicted beam report comprises: using the first number of quantization bits to obtain the first portion of the predicted beam report; and obtaining the second portion of the predicted beam report comprises: using the second number of quantization bits to obtain the second portion of the predicted beam report.

[0274] Aspect 40: The method according to any one of Aspects 23 to 39, wherein the beam report configuration is a first beam report configuration, the predicted beam report is a first predicted beam report, the at least one predicted beam is at least one first predicted beam, and the at least one confidence level is at least one first confidence level, the method further comprising: outputting a second beam report configuration; and obtaining a second predicted beam report according to the second beam report configuration, the second predicted beam report including an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam, wherein obtaining the second predicted beam report includes: obtaining the second predicted beam report at least in part based on the at least one second confidence level.

[0275] Aspect 41: According to the method of aspect 40, outputting the second beam report configuration includes: outputting the second beam report configuration based at least in part on the fact that the total number of one or more first confidence levels indicated in the first predicted beam report does not meet a threshold.

[0276] Aspect 42: The method according to aspect 40, wherein the first beam report configuration configures the payload size of the first predicted beam report.

[0277] Aspect 43: According to the method of aspect 40, wherein the first predicted beam report includes an indication of the payload size of the second predicted beam report.

[0278] Aspect 44: The method according to aspect 43, wherein the indication of the payload size reported for the second predicted beam includes an indication of the number of the at least one second predicted beam.

[0279] Aspect 45: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 44.

[0280] Aspect 46: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 44.

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

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

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

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

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

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

[0287] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase “at least one of” in the list of items refers to any combination of these items (including a single member). As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0288] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

[0289] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited to the scope, applicability, or aspects set forth in the claims. 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. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the invention.

[0290] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration).

[0291] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Additionally, "determine" can include parsing, selecting, picking, building, etc.

[0292] The methods disclosed herein include one or more actions for implementing the methods. These method actions may be interchanged without departing from the scope of the claims. In other words, unless a specified order of actions is given, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. These components may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0293] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person of ordinary skill in the art, or will be known later, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and One or more processors, coupled to the memory, are configured to: Receive beam report configuration; as well as According to the beam report configuration, a predicted beam report is transmitted, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. In order to send the predicted beam report, the one or more processors are configured to send the predicted beam report at least in part based on the at least one confidence level.

2. The UE of claim 1, wherein the confidence level indicates the probability of selecting the at least one predicted beam from one or more predicted beams.

3. The UE of claim 1, wherein the number of one or more predicted beams including the at least one predicted beam indicated in the predicted beam report is based at least in part on whether the total number of one or more confidence levels including the at least one confidence level meets a threshold.

4. The UE according to claim 2, wherein the threshold is configurable.

5. The UE of claim 1, wherein the beam report configuration configures the UE to report a first portion of the predicted beam report via a first resource and a second portion of the predicted beam report via a second resource, and wherein, in order to transmit the predicted beam report, the one or more processors are configured to: The first portion of the predicted beam report is transmitted via the first resource; and The second part of the predicted beam report is sent via the second resource.

6. The UE of claim 5, wherein the first portion of the predicted beam report includes an indication of the payload size of the second portion of the predicted beam report.

7. The UE of claim 6, wherein the beam report configuration configures the payload size of the first portion of the predicted beam report.

8. The UE of claim 6, wherein the first portion of the predicted beam report includes an explicit indication that the UE intends to send the second portion of the predicted beam report.

9. The UE of claim 6, wherein the first portion of the predicted beam report includes an indication that the UE will send the second portion of the predicted beam report at least in part based on the fact that the total number of one or more confidence levels indicated in the first portion of the predicted beam report does not meet a threshold.

10. The UE of claim 6, wherein the indication of the payload size of the second portion of the predicted beam report includes an indication of the number of one or more predicted beams to be indicated in the second portion of the predicted beam report.

11. The UE of claim 6, wherein the predicted beam report is configured on one or more physical uplink shared channel resources.

12. The UE of claim 5, wherein the beam report configuration configures the payload size of the second portion of the predicted beam report.

13. The UE of claim 5, wherein, in order to transmit the second portion of the predicted beam report, the one or more processors are configured to: The second part of the predicted beam report is sent at least in part based on the fact that the total number of one or more confidence levels indicated in the first part of the predicted beam report does not meet a threshold.

14. The UE of claim 5, wherein the beam report configuration includes an indication of a first priority associated with the first portion of the predicted beam report and an indication of a second priority associated with the second portion of the predicted beam report, and wherein, in order to transmit the second portion of the predicted beam report, the one or more processors are configured to: The first portion of the predicted beam report is sent according to the first priority; and The second part of the predicted beam report is sent according to the second priority.

15. The UE of claim 14, wherein the one or more processors are further configured to: Receive instructions on one or more priority rules, which indicate how to resolve a conflict between a first portion of the predicted beam report and another report, at least in part, based on a first priority, or indicate how to resolve a conflict between a second portion of the predicted beam report and another report, at least in part, based on a second priority.

16. The UE of claim 5, wherein, in order to transmit the second portion of the predicted beam report, the one or more processors are configured to: The first portion of the predicted beam report is transmitted, at least in part, based on the first quantization table; and The second part of the predicted beam report is sent at least in part based on the second quantization table.

17. The UE of claim 16, wherein the first quantization table defines a first number of quantization bits, and the second quantization table defines a second number of quantization bits, and wherein, in order to transmit the second portion of the predicted beam report, the one or more processors are configured to: The first portion of the predicted beam report is transmitted using the first number of quantization bits; and The second number of quantization bits is used to send the second part of the predicted beam report.

18. The UE of claim 1, wherein the beam report configuration is a first beam report configuration, the predicted beam report is a first predicted beam report, the at least one predicted beam is at least one first predicted beam, and the at least one confidence level is at least one first confidence level, and wherein the one or more processors are further configured to: Receive second beam report configuration; and A second predicted beam report is transmitted according to the second beam report configuration, the second predicted beam report including an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam. In order to send the second predicted beam report, the one or more processors are configured to send the second predicted beam report at least in part based on the at least one second confidence level.

19. The UE of claim 18, wherein, in order to receive the second beam report configuration, the one or more processors are configured to: The second beam report configuration is received at least in part based on the fact that the total number of one or more first confidence levels indicated in the first predicted beam report does not meet a threshold.

20. The UE of claim 18, wherein the first beam report configuration configures the payload size of the first predicted beam report.

21. The UE of claim 18, wherein the first predicted beam report includes an indication of the payload size of the second predicted beam report.

22. The UE of claim 21, wherein the indication of the payload size reported for the second predicted beam includes an indication of the number of the at least one second predicted beam.

23. A network entity for wireless communication, the network entity comprising: Memory; and One or more processors, coupled to the memory, are configured to: Output beam report configuration; as well as A predicted beam report is obtained according to the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. In order to obtain the predicted beam report, the one or more processors are configured to obtain the predicted beam report based at least in part on the at least one confidence level.

24. The network entity of claim 23, wherein the confidence level indicates the probability of selecting the at least one predicted beam from one or more predicted beams.

25. The network entity of claim 23, wherein the number of one or more predicted beams including the at least one predicted beam, indicated in the predicted beam report, is based at least in part on whether the total number of one or more confidence levels including the at least one confidence level satisfies a threshold.

26. The network entity of claim 25, wherein the threshold is configurable.

27. The network entity of claim 23, wherein the beam reporting configuration includes an indication of reporting a first portion of the predicted beam report via a first resource and a second portion of the predicted beam report via a second resource, and wherein, in order to obtain the predicted beam report, the one or more processors are configured to: The first portion of the predicted beam report is obtained via the first resource; and The second part of the predicted beam report is obtained via the second resource.

28. The network entity of claim 23, wherein the beam report configuration is a first beam report configuration, the predicted beam report is a first predicted beam report, the at least one predicted beam is at least one first predicted beam, and the at least one confidence level is at least one first confidence level, and wherein the one or more processors are further configured to: Output second beam report configuration; and A second predicted beam report is obtained according to the second beam report configuration, the second predicted beam report including an indication of at least one second predicted beam and an indication of at least one second confidence level corresponding to the at least one second predicted beam. In order to obtain the second predicted beam report, the one or more processors are configured to obtain the second predicted beam report at least in part based on the at least one second confidence level.

29. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive beam report configuration; as well as According to the beam report configuration, a predicted beam report is transmitted, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. Sending the predicted beam report includes sending the predicted beam report based at least in part on the at least one confidence level.

30. A method for wireless communication performed by a network entity, the method comprising: Output beam report configuration; as well as A predicted beam report is obtained according to the beam report configuration, the predicted beam report including an indication of at least one predicted beam and an indication of at least one confidence level corresponding to the at least one predicted beam. Obtaining the predicted beam report includes obtaining the predicted beam report based at least in part on the at least one confidence level.

Images