[go: up one dir, main page]

WO2025171593A1 - Gestion prédictive de faisceau selon des types de quasi-colocalisation - Google Patents

Gestion prédictive de faisceau selon des types de quasi-colocalisation

Info

Publication number
WO2025171593A1
WO2025171593A1 PCT/CN2024/077282 CN2024077282W WO2025171593A1 WO 2025171593 A1 WO2025171593 A1 WO 2025171593A1 CN 2024077282 W CN2024077282 W CN 2024077282W WO 2025171593 A1 WO2025171593 A1 WO 2025171593A1
Authority
WO
WIPO (PCT)
Prior art keywords
beams
resources
quasi
qcl
channel characteristics
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/077282
Other languages
English (en)
Inventor
Hamed Pezeshki
Tao Luo
Qiaoyu Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2024/077282 priority Critical patent/WO2025171593A1/fr
Priority to PCT/CN2025/076767 priority patent/WO2025171783A1/fr
Publication of WO2025171593A1 publication Critical patent/WO2025171593A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/20—Monitoring; Testing of receivers
    • H04B17/24—Monitoring; Testing of receivers with feedback of measurements to the transmitter
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/30—Monitoring; Testing of propagation channels
    • H04B17/373—Predicting channel quality or other radio frequency [RF] parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B17/00—Monitoring; Testing
    • H04B17/30—Monitoring; Testing of propagation channels
    • H04B17/391—Modelling the propagation channel
    • H04B17/3913—Predictive models, e.g. based on neural network models
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/0632—Channel quality parameters, e.g. channel quality indicator [CQI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection

Definitions

  • the following relates to wireless communications, including predictive beam management according to quasi-collocation (QCL) types.
  • QCL quasi-collocation
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
  • UE user equipment
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support predictive beam management according to quasi-collocation (QCL) types.
  • QCL quasi-collocation
  • techniques described herein support improved beam consistency in beam prediction training and beam inference.
  • a user equipment (UE) may predict beams for one set of resources based on measurements taken via another set of beams and resources.
  • the network entity may indicate a QCL relationship that indicates both temporal parameters, and spatial parameters. Such a QCL relationship may increase the consistency between predicted beams reported by the UE (e.g., based on the AI/ML model and the previous measurements) , and the actual transmit beam utilized by the network entity for subsequent downlink transmissions.
  • Such QCL relationships may combine temporal and spatial parameters indicated by other QCL relationships.
  • the QCL relationship may also apply to the measurement beams and the predicted beams (e.g., such that a predicted beam corresponds to a measurement beam according to the QCL relationship) , or may apply across beam inference and beam prediction training (e.g., such that a first measurement beam of beam prediction training corresponds to a first measurement beam for beam inference, and a first predicted beam of the beam prediction training corresponds to a first predicted beam for beam inference, according to the QCL relationship indicting both temporal and spatial parameters) .
  • Such a QCL relationships may be configured at the UE.
  • the network entity may indicate such a QCL relationship to the UE for downlink signaling based on whether the source resources of the QCL relationship (e.g., the resources corresponding to the predicted beam) are virtual resources or physical resources.
  • the CSI report may be configured to indicate channel characteristics corresponding to the virtual resources (e.g., or physical resources) associated with the predicted beam.
  • the QCL relationship may be based on a level of consistency of a particular type of beam prediction or a particular use case (e.g., for more or less stringent beam consistency) .
  • a method for wireless communications by a user equipment may include receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, receiving a control message including an indication of a quasi colocation relationship between a downlink receive beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and receiving downlink signaling using the downlink receive beam according to the control message and the quasi colocation relationship.
  • the UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the UE to receive a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, transmit an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, receive a control message including an indication of a quasi colocation relationship between a downlink receive beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and receive downlink signaling using the downlink receive beam according to the control
  • the UE may include means for receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, means for transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, means for receiving a control message including an indication of a quasi colocation relationship between a downlink receive beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and means for receiving downlink signaling using the downlink receive beam according to the control message and the quasi colocation relationship.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by one or more processors to receive a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, transmit an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, receive a control message including an indication of a quasi colocation relationship between a downlink receive beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and receive downlink signaling using the downlink receive beam according to the control message and the quasi colocation relationship.
  • the quasi colocation relationship may be based on a use case of a beam prediction procedure.
  • a first candidate quasi colocation relationship of a set of multiple candidate quasi colocation relationships corresponds to a first level of beam shape consistency between the first set of beams and the second set of beams
  • a second candidate quasi colocation relationship of the set of multiple candidate quasi colocation relationships corresponds to a second level of beam shape consistency between the first set of beams ad the second set of beams and the quasi colocation relationship includes the first candidate quasi colocation relationship based on the use case of the beam prediction procedure relying on the first level of beam shape consistency.
  • the set of one or more spatial beam parameters includes a set of spatial receive beam parameters at the UE, and the set of one or more temporal beam parameters include a Doppler shift, a Doppler spread, an average delay, a delay spread, or any combination thereof.
  • the predicted channel characteristics associated with the second set of beams may be based on a second quasi colocation relationship between the first set of beams, and the second set of beams, the second quasi colocation relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • the predicted channel characteristics associated with the second set of beams may be based on a machine learning model trained according to at least a third set of beams corresponding to a third set of resources including measurement resources, and a fourth set of beams corresponding to a fourth set of resources including prediction target resources, a second quasi colocation relationship exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof, and the second quasi colocation relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • a method for wireless communications by a network entity may include outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, outputting a control message including an indication of a quasi colocation relationship between a downlink beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and outputting downlink signaling using the downlink beam according to the control message and the quasi colocation relationship.
  • the network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the network entity to output a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, obtain an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, output a control message including an indication of a quasi colocation relationship between a downlink beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and output downlink signaling using the downlink beam according to the control message and
  • the network entity may include means for outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, means for obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, means for outputting a control message including an indication of a quasi colocation relationship between a downlink beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and means for outputting downlink signaling using the downlink beam according to the control message and the quasi colocation relationship.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by one or more processors to output a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources, obtain an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, output a control message including an indication of a quasi colocation relationship between a downlink beam and the set of one or more preferred beams, where the quasi colocation relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters, and output downlink signaling using the downlink beam according to the control message and the quasi colocation relationship.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting control signaling indicating the second set resources, where the second set of resources includes virtual prediction target resources, where the set of predicted channel characteristics associated with the second set of resources may be based on outputting the set of multiple reference signals via the first set of resources without outputting any reference signals via the second set of resources based on the control signaling, the set of predicted channel characteristics may be associated with the second set of resources according to the quasi colocation relationship.
  • control message includes a transmission configuration indicator state including the indication of the quasi colocation relationship.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting control signaling scheduling one or more channel state information reports, the control signaling indicating the first set of resources for the one or more measurements and indicating a set of one or more report quantities including the set of predicted channel characteristics associated with the second set of resources and obtaining the one or more channel state information reports based on the one or more measurements and the set of predicted channel characteristics, where the set of predicted channel characteristics may be associated with the second set of resources based on the quasi colocation relationship.
  • the quasi colocation relationship may be based on a use case of a beam prediction procedure.
  • a first candidate quasi colocation relationship of a set of multiple candidate quasi colocation relationships corresponds to a first level of beam shape consistency between the first set of beams and the second set of beams
  • a second candidate quasi colocation relationship of the set of multiple candidate quasi colocation relationships corresponds to a second level of beam shape consistency between the first set of beams and the second set of beams
  • the quasi colocation relationship includes the first candidate quasi colocation relationship based on the use case of the beam prediction procedure relying on the first level of beam shape consistency.
  • the set of one or more spatial beam parameters includes a beam direction, beam size, beam shape, beam power, or any combination thereof
  • the set of one or more temporal beam parameters include a Doppler shift, a Doppler spread, an average delay, a delay spread, or any combination thereof.
  • the predicted channel characteristics associated with the second set of beams may be based on a second quasi colocation relationship between the first set of beams, and the second set of beams, the second quasi colocation relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • the predicted channel characteristics associated with the second set of beams may be based on a machine learning model trained according to at least a third set of beams corresponding to a third set of resources including measurement resources, and a fourth set of beams corresponding to a fourth set of resources including prediction target resources, a second quasi colocation relationship exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof, and the second quasi colocation relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • FIG. 1 shows an example of a wireless communications system that supports predictive beam management according to quasi-collocation (QCL) types in accordance with one or more aspects of the present disclosure.
  • QCL quasi-collocation
  • FIG. 2 shows an example of a wireless communications system that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIG. 3 shows an example of a wireless communications system that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIG. 4 shows an example of a process flow that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIGs. 5 and 6 show block diagrams of devices that support predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIG. 7 shows a block diagram of a communications manager that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIG. 8 shows a diagram of a system including a device that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIGs. 9 and 10 show block diagrams of devices that support predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIG. 11 shows a block diagram of a communications manager that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIG. 12 shows a diagram of a system including a device that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • FIGs. 13 through 16 show flowcharts illustrating methods that support predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • a user equipment (UE) and a network entity may perform beam prediction based on an artificial intelligence (AI) or machine learning (ML) model (e.g., which may be referred to herein as an AI/ML model) .
  • the UE may measure one or more reference signals received via a first set of resources and a first set of beams, and may generate predicted channel characteristics for a second set of resources and a second set of beams.
  • the UE may report a preferred set of one or more predicted beams (e.g., of the second set of beams) .
  • the network entity may schedule downlink signaling and indicate (e.g., via a transmission configuration indicator (TCI) state) a relationship (e.g., a quasi-collocation (QCL) relationship) between the reference signals and resources corresponding to the one or more predicted beams (e.g., which may be actual resources via which additional reference signals are transmitted, or virtual resources via which no reference signals have been transmitted) , and resources and beam on which the scheduled downlink signaling is to be received by the UE.
  • TCI transmission configuration indicator
  • QCL quasi-collocation
  • some QCL relationships may indicate spatial receive parameters (e.g., which may define aspects of a receive beam at the UE, but may not define any aspects of a transmit beam used by the network entity) .
  • the QCL relationship indicated by the network entity may define temporal parameters, but not spatial parameters.
  • the network entity may transmit the downlink signaling using a beam of a different size and shape than the transmit beam indicated by the UE based on the beam prediction. Because the relationship between the indicated predicted beam or beams, and the selected downlink transmit beam used by the network entity for downlink signaling does not constrain the network entity to select a beam of similar size and shape, downlink transmissions based on the beam prediction performed by the UE may be performed via different downlink beams.
  • an actually used beam may not be a best available beam (e.g., downlink communications may not experience best available channel quality) .
  • Such wireless communications may result in failed downlink transmissions, lower channel quality, inefficient use of available system resources, increased system latency, and decreased user experience.
  • the AI/ML model may fail, or beam inference based on the beam model may fail.
  • the network entity may indicate (e.g., in a TCI state) a QCL relationship that indicates both temporal parameters, and spatial parameters.
  • a QCL relationship may increase the consistency between predicted beams indicated by the UE (e.g., based on the AI/ML model and the previous measurements) , and the actual transmit beam utilized by the network entity for subsequent downlink transmissions.
  • Such QCL relationships e.g., types of QCL
  • the QCL relationship may also apply to the measurement beams and the predicted beams (e.g., such that a predicted beam corresponds to a measurement beam according to the QCL relationship) , or may apply across beam inference and beam prediction training (e.g., such that a first measurement beam of beam prediction training corresponds to a first measurement beam for beam inference, and a first predicted beam of the beam prediction training corresponds to a first predicted beam for beam inference, according to the QCL relationship indicting both temporal and spatial parameters) .
  • Such a QCL relationships may be configured at the UE.
  • the network entity may indicate such a QCL relationship to the UE for downlink signaling based on whether the source resources of the QCL relationship (e.g., the resources corresponding to the predicted beam) are virtual resources or physical resources.
  • the CSI report may be configured to indicate channel characteristics corresponding to the virtual resources (e.g., or physical resources) associated with the predicted beam.
  • the QCL relationship may be based on a level of consistency of a particular type of beam prediction or a particular use case (e.g., for more or less stringent beam consistency) .
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to wireless communications systems and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to predictive beam management according to QCL types.
  • FIG. 1 shows an example of a wireless communications system 100 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs radio access technologies
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
  • a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with a core network 130, or with one another, or both.
  • network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
  • network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) .
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • a disaggregated architecture e.g., a disaggregated base station architecture, a disaggregated RAN architecture
  • a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by
  • a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof.
  • a central unit such as a CU 160
  • DU distributed unit
  • RU such as an RU 170
  • a RAN Intelligent Controller (RIC) such as an RIC 175
  • a Near-Real Time RIC Near-RT RIC
  • Non-RT RIC Non-Real Time RIC
  • SMO Service Management and Orchestration
  • An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU 160 may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • RLC radio link control
  • MAC medium access control
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) .
  • a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
  • a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • CU-CP CU control plane
  • CU-UP CU user plane
  • a CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network architecture e.g., to a core network 130
  • one or more of the network entities 105 may be partially controlled by each other.
  • the IAB node (s) 104 may be referred to as a donor entity or an IAB donor.
  • a DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) .
  • the one or more donor entities may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) .
  • IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
  • an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB node (s) 104, and one or more UEs 115.
  • the IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130.
  • the IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
  • the IAB donor and IAB node (s) 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) .
  • the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.
  • IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
  • a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) .
  • IAB node (s) 104 may also be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN.
  • the IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node (s) 104) to receive signaling from a parent IAB node (e.g., the IAB node (s) 104) , and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.
  • a DU interface e.g., a DU 165
  • IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both.
  • An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104.
  • the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both.
  • the CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (e.g., other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.
  • DUs e.g., DUs 165
  • one or more components of the disaggregated RAN architecture may be configured to support test as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125.
  • a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • a given RAT e.g., LTE, LTE-A, LTE-A Pro, NR
  • Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
  • the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • another device e.g., directly or via one or more other network entities, such as one or more of the network entities 105
  • a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
  • the communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., a quantity of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
  • a network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) .
  • a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110.
  • coverage areas 110 e.g., different coverage areas
  • coverage areas 110 may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) .
  • overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) .
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • network entities 105 e.g., base stations 140
  • network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) .
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data.
  • Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
  • vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
  • vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
  • roadside infrastructure such as roadside units
  • network nodes e.g., network entities 105, base stations 140, RUs 170
  • V2N vehicle-to-network
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas.
  • mmW millimeter wave
  • such techniques may facilitate using antenna arrays within a device.
  • EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115) .
  • a transmitting device e.g., a network entity 105 or a UE 115
  • a single beam direction e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a transmitting device e.g., a network entity 105
  • a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or PDCP layer may be IP-based.
  • An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
  • a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
  • an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
  • a PHY layer may map transport channels to physical channels.
  • the UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) .
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • the network entity 105 may indicate (e.g., in a TCI state) a QCL relationship that indicates both temporal parameters, and spatial parameters.
  • a QCL relationship may increase the consistency between predicted beams indicated by the UE 115 (e.g., based on the AI/ML model and the previous measurements) , and the actual transmit beam utilized by the network entity for subsequent downlink transmissions.
  • Such QCL relationships e.g., types of QCL
  • the QCL relationship may also apply to the measurement beams and the predicted beams (e.g., such that a predicted beam corresponds to a measurement beam according to the QCL relationship) , or may apply across beam inference and beam prediction training (e.g., such that a first measurement beam of beam prediction training corresponds to a first measurement beam for beam inference, and a first predicted beam of the beam prediction training corresponds to a first predicted beam for beam inference, according to the QCL relationship indicting both temporal and spatial parameters) .
  • Such a QCL relationships may be configured at the UE 115.
  • the network entity may indicate such a QCL relationship to the UE 115 for downlink signaling based on whether the source resources of the QCL relationship (e.g., the resources corresponding to the predicted beam) are virtual resources or physical resources.
  • the CSI report may be configured to indicate channel characteristics corresponding to the virtual resources (e.g., or physical resources) associated with the predicted beam.
  • the QCL relationship may be based on a level of consistency of a particular type of beam prediction or a particular use case (e.g., for more or less stringent beam consistency) .
  • FIG. 2 shows an example of a wireless communications system 200 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 200 may implement, or be implemented, by aspects of the wireless communications system 100.
  • the wireless communications system 200 may include a network entity 105-a, and a UE 115-a, which may be examples of corresponding devices described with reference to FIG. 1.
  • a user may support techniques for beam prediction using an AI/ML model.
  • the UE 115-a may receive one or more reference signals via a first set of beams and a first set of resources (e.g., set B beams and set B resources) , and may utilize the AI/ML model to predict channel characteristics for signaling (e.g., downlink signaling) via a second set of resources and a second set of beams (e.g., set B resources and set B beams) .
  • the AI/ML model may be trained, and may then be utilized for beam inference (e.g., beam prediction) .
  • the AI/ML model may be defined such that one or more inputs (e.g., measurements of the first set of beams, such as channel characteristic measurements) provided to the AI/ML model may generate outputs (e.g., predictive channel characteristics or preferred beams) for the second set of resources and the second set of beams.
  • inputs e.g., measurements of the first set of beams, such as channel characteristic measurements
  • outputs e.g., predictive channel characteristics or preferred beams
  • the first set of beams may be referred to as a set of measurement beams
  • the second set of beams may be referred to as predicted beams.
  • the UE 115-a may use the AI/ML model to obtain or identify predicted beams or channel characteristics associated with the predicted beams.
  • the UE 115-a may input the measurements into the AI/ML model, and the AI/ML model may output predicted channel characteristics for one or more downlink beams.
  • the UE 115-a may identify, or the AI/ML model may output, information associated with receive beams that correspond to the predicted channel characteristics for the downlink beams.
  • the UE 115-a may predict which downlink transmit beams will be strongest in a future time slot, in a different frequency domain, or in different directions, and the UE 115-a may also identify corresponding receive beams for the downlink transmit beams.
  • the predicted beams may correspond to a beam supported by the UE 115-a, a predicted downlink AoA, or the like.
  • the UE 115-a may perform predictions for beams in one or more domains.
  • the UE 115-a may perform spatial domain prediction.
  • predicted channel characteristics may include downlink AoAs and an associated RSRP or an associated SINR for the preferred candidate resources.
  • predicted channel characteristics may include one or more preferred candidate resources from a set of candidate resources indicated by the network entity 105-a.
  • the UE 115-a may additionally or alternatively predict an associated RSRP or an associated SINR.
  • the UE 115-a may perform temporal domain predictions.
  • the UE 115-a may predict (e.g., as an output of the AI/ML model) one or more preferred beams, or one or more channel characteristics associated with one or more preferred beams, at a future point in time.
  • the UE 115-a may perform temporal downlink transmit beam prediction for the second set of beams based on historic measurement results of the first set of beams (e.g., which may be referred to as beam management case 2) .
  • the UE 115-a e.g., or the network entity 105-a
  • the UE 115-a e.g., or the network entity 105-a
  • LCM life cycle management
  • the UE 115-a, the network entity 105-a, or both may perform beam prediction training 225, beam inference 230, or both.
  • Beam prediction training 225 may include data collection, model inference, performance monitoring, etc., for the AI/ML model.
  • the AI/ML model may be UE-sided, network entity-sided, or both.
  • measurements taken via the first set of measurement resources and the measurement beams 205 may be used for predicting predicted beams 210 (e.g., the predicted beam 210-a, the predicted beam 210-c, the predicted beam 210-d, the predicted beam 210-e, the predicted beam 210-f, the predicted beam 210-g, the predicted beam 210-h, the predicted beam 210-i, the predicted beam 210-j) , or generating predicted channel characteristics associated with a set of resources corresponding to the predicted beams 210.
  • predicted beams 210 e.g., the predicted beam 210-a, the predicted beam 210-c, the predicted beam 210-d, the predicted beam 210-e, the predicted beam 210-f, the predicted beam 210-g, the predicted beam 210-h, the predicted beam 210-i, the predicted beam 210-j
  • the beam prediction training 225 may be performed at another device (e.g., the same network entity 105-a via one or more additional UEs 115, or a different network entity 105-a and one or more UEs 115) .
  • the trained AI/ML model may be provided to the UE 115 (e.g., via control signaling) such that the UE 115-a may utilize the trained model for beam inference 230.
  • the AI/ML model may not accurately predict preferred beams 220.
  • measurements taken via the first set of measurement resources and the measurement beams 215 may be applied to the trained AI/ML model for inferring predicted beams 220 (e.g., the predicted beam 220-a, the predicted beam 220-b, the predicted beam 220-d, the predicted beam 220-e, the predicted beam 220-f, the predicted beam 220-g, the predicted beam 220-h, the predicted beam 220-i, the predicted beam 220-j) , or generating predicted channel characteristics associated with a set of resources corresponding to the predicted beams 220.
  • predicted beams 220 e.g., the predicted beam 220-a, the predicted beam 220-b, the predicted beam 220-d, the predicted beam 220-e, the predicted beam 220-f, the predicted beam 220-g, the predicted beam 220-h, the predicted beam 220-i, the predicted beam 220-j
  • a lack of consistency between beams may result in decreased effectiveness of the beam prediction training 225 and beam inference 230.
  • Consistency across beam prediction training 225 and beam inference 230 may be impacted by various parameters or parameter values.
  • one or more additional conditions at the network entity 105-a may change over time, and may impact consistency between beams.
  • Such additional conditions may include down-tilt angles of antenna arrays, antenna array height, time of day of data collection (e.g., for beam prediction training 225) , or the like.
  • some such additional conditions e.g., aspect related to physical characteristics of the network entity 105-a, timing of data collection, etc.
  • ) may not be essential to ensuring consistency, and in some examples may be considered to be meta-data associated with UE-side data collection that can assist the UE 115-a in identifying the applicability of an AI/ML model during beam inference 230 (e.g., based on consistency of the AI/ML model across beam prediction training 225 and beam inference 230) .
  • Such additional information may be indicated to the UE 115-a via control signaling (e.g., which may enable consistent use or accurate selection of a relevant AI/ML model) .
  • a lack of other parameters may result in failure of consistency between beams, or across beam prediction training 225 and beam inference 230.
  • the beam prediction training 225 may fail or be reduced in effectiveness and accuracy (e.g., the AI/ML model based on the beam prediction training 225 may not be reliable for beam inference 230) .
  • beam size, shape, and direction, for the predicted beams 210 may be different from the beam size, shape, and direction, for predicted beams 220.
  • the AI/ML model may be flawed or incomplete.
  • a relative beam direction, beamwidth difference, beam size or shape difference, etc., between the measurement beams 215 and the predicted beams 220, or between the predicted beams 210 and the predicted beams 220, may result in beam inference failure.
  • beam inconsistency between a preferred predicted beam 220 and a subsequently selected beam for downlink communication may lead to failed or decreased quality in downlink communications.
  • the UE 115-a may receive reference signals via the measurement beam 215-a.
  • the UE 115-a may perform one or more measurements, and may determine one or more channel characteristics for a first set of resources based on the measurements.
  • the UE 115-a may input such measurements into the AI/ML model, which may generate (e.g., as an output) , an indication of one or more channel characteristics corresponding to the predicted beams 220, one or more predicted beams 220, or any combination thereof.
  • the UE 115-a may determine a single preferred beam (e.g., the predicted beam 220-b) , or a set of preferred beams (e.g., the predicted beam 220-a, the predicted beam 220-b, and the predicted beam 220-c) based on the output of the AI/ML model.
  • the UE 115-a may indicate (e.g., via a CSI report) the one or more preferred predicted beams 220.
  • the network entity 105-a may schedule downlink communications, and may indicate a TCI state that the UE 115-a is to use for receiving the downlink communications.
  • the indicated downlink beam may not actually be a best beam for subsequent communications.
  • the network entity 105-a may indicate, to the UE 115-a based on the indicated preferred beams, a TCI state.
  • the TCI state may include an indication of a QCL relationship between a source beam (e.g., an actual or virtual source resource associated with the predicted beam 220-b, or an actual or virtual source signal such as an actual or virtual reference signal corresponding to the predicted beam 220-b) and the indicated beam for receiving the scheduled downlink communication (e.g., the indicated beam or resource associated with the indicated beam) .
  • a source beam e.g., an actual or virtual source resource associated with the predicted beam 220-b
  • an actual or virtual source signal such as an actual or virtual reference signal corresponding to the predicted beam 220-b
  • some QCL relationships may not sufficiently indicate beam consistency. In such examples, subsequent downlink communication via an indicated preferred beam (e.g., according to an indicated QCL relationship) may fail.
  • the lack of consistency between the predicted beam 220 and the downlink beam for subsequently transmitted downlink signaling may result in downlink transmissions sent via a downlink beam that is not preferred by the UE 115-a, failed or unreliable downlink transmissions, decreased reliability of wireless communications, more retransmissions, less efficient use of available system resources, increased system latency, and decreased user experience.
  • one or more additional conditions at the network entity 105-a may change over time.
  • the network entity 105-a may adjust one or more beam parameters (e.g., such as beam size or beam shape) without a mechanism to ensure beam consistency, resulting in a different beam selected by the network entity than the preferred predicted beam indicated by the UE 115-a.
  • Techniques described herein may support consistency across the beam prediction training 225, and the beam inference 230. Techniques described herein may further support increased consistency during beam inference 230. That is, techniques described herein may support consistency between network side additional conditions with regards to inputs (e.g., measurements from the first set of beams) and outputs (e.g., predictions for the second set of beams) of AI/ML models across both beam prediction training 225 and beam inference 230. Beam shape consistency may be improved, according to techniques described herein.
  • Beam shape consistency achieved according to techniques described herein may include consistency of beam shape for measurement beams 205 and measurement beams 215 and between predicted beams 210 and predicted beams 215, consistency measurement beams 215 and predicted beams 220 during beam inference 230, consistency between predicted beams and subsequently scheduled beams, etc.
  • Such beam consistency may be defined by a QCL type that indicates both spatial and temporal beam parameters.
  • a QCL type defined as described herein may include a spatial receive parameter, and one or more temporal parameters.
  • such a QCL type may be a combination or hybrid QCL type including parameters of two other QCL types.
  • a QCL relationship may refer to a relationship between parameters or antenna ports across multiple transmissions.
  • a device receiver (e.g., the UE 115-a) can assume that the radio channels corresponding to two different antenna ports have the same properties (e.g., the same large-scale properties) in terms of specific parameters such as average delay spread, doppler spread, Doppler shift, average delay, average gain, and spatial receive parameters if the antenna ports are specified as being quasi collocated.
  • properties e.g., the same large-scale properties
  • specific parameters such as average delay spread, doppler spread, Doppler shift, average delay, average gain, and spatial receive parameters if the antenna ports are specified as being quasi collocated.
  • the network entity 105-a may indicate a QCL relationship to the UE 115-a.
  • the QCL relationship may indicate a relationship between parameters of a source beam (e.g., a predicted beam 220) and a target beam (e.g., a downlink beam for a subsequent downlink communication) .
  • some QCL types e.g., a QCL typeA, QCL typeB, and QCL type C
  • QCL types indicate consistency between beam temporal parameters (e.g., but not beam spatial parameters) , as described in greater detail with reference to FIG. 3.
  • Other QCL types e.g., a QCL type D
  • spatial parameters e.g., a spatial receive parameter
  • the UE 115-a may indicate a preferred predicted beam 220-b based on measurements performed via the measurement beam 215-a.
  • the network entity 105-a may schedule downlink traditions, and may indicate a TCI state to the UE 115-a.
  • the TCI state may indicate a QCL relationship between the source beam (e.g., the predicted beam 220-b) and a target beam (e.g., the beam to use for downlink signaling) .
  • the QCL typeD indicated by a TCI state merely indicates a spatial receive parameter
  • the QCL typeD relationship may not indicate a consistent beam shape or size (e.g., such that a downlink receive beam used for the scheduled downlink communication may not be the same size and shape as the preferred predicted beam 220-b) .
  • the network entity 105-a may determine an associated transmit parameter, and may use a beam that is narrower than the QCL source (e.g., the measurement beam 215-a, or the indicated predicted beam 220-b) to improve throughput.
  • the beam inference 230 may be ineffective because the beam utilized by the network entity 105-a may not be the same beam (e.g., may not have the same size or shape) as the predicted beam 220-b indicated by the UE 115-a (e.g., because the QCL typeD does not indicate consistent beam size or shape) .
  • Such differences may occur because the network entity 105-a may be free to adjust a beam size and shape autonomously without a QCL type that relies on beam consistency over time, or because one or more parameters may change over time such that different parameters are applied for downlink beams at a point in time subsequent to the indication of a preferred predicted beam 220.
  • the network entity 105-a may transmit an indication of a beam (e.g., an enhanced TCI state) indicating a QCL relationship that includes both temporal parameters, and spatial parameters.
  • a beam e.g., an enhanced TCI state
  • the beam shape consistency e.g., between the QCL source beam, such as a such as a predicted beam 220, and the QCL target beam, such as a downlink beam for downlink signaling
  • a TCI state indicating such a QCL relationship may ensure some level of beam shape consistency across beam prediction training 225 and beam inference 230.
  • the QCL type may include one or more temporal parameters (e.g., corresponding to QCL typeA, QCL typeB, and QCL typeC) , and one or more spatial parameters (e.g., corresponding to QCL typeD) .
  • the indicated beam for downlink signaling may similar in size and shape to the predicted beam 220 (e.g., because the target beam and the source beam share both spatial parameters and temporal parameters, resulting in increased beam consistency over time) .
  • the UE 115-a may perform CSI reporting based on such a QCL type.
  • the QCL type may be based on a use case (e.g., more stringent or less stringent indications of consistency of beam shape and size between QCL source and QCL target beams) .
  • Such enhanced QCL types may also apply to both beam prediction training 225, and beam inference 230.
  • beam consistency for set A beams and set B beams may be defined by a QCL relationship (e.g., QCL typeF, QCL typeG, or QCL typeF) across training and inference.
  • Beam consistency may be referred to as QCL consistency.
  • RI resource index
  • Such consistency may be particularly applicable to wide-to-narrow beam prediction. For instance, as described with reference to FIG. 2, if predicted beam predicted 210-a, predicted beam 210-b, and predicted beam 210-c correspond to measurement beam 205-a according to a QCL relationship, then predicted beam 220-a, predicted beam 220-b, and predicted beam 220-c correspond to measure beam 215-a according to the QCL relationship, then the QCL consistency relationship holds for the QCL type.
  • the QCL relationship may define a QCL relationship between measurement beams 205 in beam prediction training 225 and measurement beams 215 in beam inference 230, and between predicted beams 210 during beam prediction training and predicted beams 220 during beam inference 230.
  • the relationship may be defined between each measurement beam 205 of beam prediction training 225 and each respective measurement beam 215 of beam inference 230, and between each predicted beam 210 of beam prediction training 225 and each respective predicted beams 220 of beam inference 230.
  • QCL types such as QCL typeF, QCL typeG, and QCL typeH may leverage both temporal and spatial parameters of other QCL types (e.g., QCL typeA, QCL typeB, QCL typeC, and QCL typeD) .
  • QCL typeF as described with reference to FIG. 3 may be defined such that both QCL-TypeD and QCL-TypeA are enabled, rather than QCL typeD alone.
  • a QCL type such as the QCL types described herein may ensure that both QCL-TypeD and QCL-TypeA are enabled, and may put more constraints on the downlink transmit beam shape (compared to QCL-TypeD alone) , and therefore may ensure some level of beam shape consistency.
  • FIG. 3 shows an example of a wireless communications system 300 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 300 may implement, or be implemented by, aspects of the wireless communications system 100 and the wireless communications system 200.
  • the wireless communications system may include a network entity 105-b, and a UE 115-b, which may be examples of corresponding devices described with reference to FIGs. 1-2.
  • the UE 115-a and the network entity 105-a may perform beam inference according to an AI/ML model (e.g., based on beam selection training) .
  • the network entity 105-b may transmit control signaling 325.
  • the control signaling 325 may indicate a first set of measurement resources (e.g., set B resources) a first set of measurement beams (e.g., set B beams) , or both, and a second set of prediction resources (e.g., set A resources) a second set of predicted beams (e.g., set A beams) , or both.
  • the control signaling 325 may indicate the AI/ML model to the UE 115-b.
  • the network entity 105-b may transmit one or more reference signals 305 via the measurement beams and the measurement resources.
  • the UE 115-b may receive the reference signals, and perform one or more measurements.
  • the measurements may be input into the AI/ML model, and the UE 115-b may determine one or more preferred predicted beams based on an output of the AI/ML model (e.g., based on predicted channel characteristics for the prediction resources or the predicted beams) .
  • the UE 115-b may transmit a report 310 (e.g., a CSI report) , which may indicate one or more predicted beams (e.g., such as a predicted beam 220 as described with reference to FIG. 2) .
  • the network entity 105-b may transmit a control message 315, which may include an indication of a beam for subsequent downlink signaling 320.
  • the control message 315 may include an indication of a TCI state for the downlink signaling 320.
  • the TCI state may be an enhanced TCI state, which may indicate a QCL type 330.
  • Different sets 335 of QCL types may correspond to different parameters.
  • set 335-a may include QCL types corresponding to temporal parameters.
  • QCL typeA may indicate a QCL relationship sharing the same parameters, including Doppler shift, Doppler Spread, average delay, and delay spread.
  • QCL typeB may indicate a QCL relationship sharing the same parameters, including Doppler shift and Doppler spread.
  • QCL typeC may indicate a QCL relationship sharing the same parameters, including Doppler shift and average delay.
  • QCL typeF may include temporal parameters defined by QCL typeA and spatial parameters defined by QCL typeD.
  • QCL typeF may indicate a QCL relationship sharing the parameters including Doppler shift, Doppler spread, average delay, delay spread, and spatial receive parameters.
  • QCL typeG may include temporal parameters defined by QCL typeB and spatial parameters defined by QCL typeD.
  • QCL typeG may indicate a QCL relationship sharing the parameters including Doppler shift and Doppler spread, and the spatial receive parameter.
  • QCL typeH may include temporal parameters defined by QCL typeC and spatial parameters defined by QCL typeD.
  • QCL typeG may indicate a QCL relationship sharing parameters including Doppler shift and average delay, and spatial parameters.
  • QCL typeD may support only loose consistency between beams, and may therefore not ensure downlink transmit beam consistency (e.g., because the QCL typeD is associated with a spatial receive parameter) .
  • QCL typeF, QCL typeG, and QCL typeH may add additional conditions to the QCL relationship to tighten a relationship (e.g., improve consistency based on the QCL relationship) between the predicted downlink spatial parameters of the predicted beam and the beam scheduled for downlink signaling.
  • QCL typeF may indicate more beam consistency in terms of both temporal parameters and spatial parameters, than QCL typeH (e.g., because QCL typeF defines more shared temporal parameters than QCL typeH) .
  • the control message 315 may indicate a QCL type that includes both temporal and spatial parameters (e.g., QCL typeF, QCL typeG, or QCL typeH) .
  • the QCL relationship indicated a QCL relationship between a source resource (e.g., the prediction resource or the predicted beam indicated by the UE 115-b in the report 310) and a scheduled resource (e.g., a scheduled beam for the downlink signaling 320) . Because the indicated QCL relationship defines both shared temporal parameters, and shared spatial parameters, the QCL relationship may ensure at least a threshold level of consistency between the preferred predicted beam indicated by the UE 115-b and the actual beam scheduled for downlink signaling 320.
  • Such consistency may be ensured by both the spatial receive parameters indicated by the QCL relationship, and the temporal parameters indicated by the QCL relationship such that the beam is consistent over time (e.g., has not been changed despite the time that has passed between reception of the report 310 and the downlink signaling 320) .
  • the TCI state indicating the QCL type may be based on virtual source resources, or actual source resources.
  • the UE 115-b may actually receive the reference signals 305 via the measurement resources, and may predict channel characteristics or the prediction resources based thereon without actually receiving any reference signals from the network entity 105-b via the prediction resources.
  • the prediction resources e.g., via which no reference signals are actually transmitted or received
  • virtual resources may be referred to as virtual resources.
  • Such virtual resources may be the source resources of the QCL relationship indicated by the TCI state in the control message 315.
  • the UE 115-b may indicate (e.g., in the report 310) one or more predicted beams of a larger set of candidate predicted beams based on the AI/ML model (e.g., predicted beam 220-a, predicted beam 220-b, and predicted beam 220-c, as described with reference to FIG. 2) .
  • the network entity 105-b may transmit actual reference signals (e.g., additional reference signals 305, or different reference signals, such as channel state information reference signals (CSI-RSs) via the indicated predicted beams.
  • the UE 115-b may actually receive reference signals via the one or more predicted beams indicated in the report 310, and may perform additional measurements.
  • the UE 115-b may then transmit an indication (e.g., via a second report 310) of one or more selected or preferred predicted beams.
  • Such resources e.g., the resources via which the second reference signals are actually transmitted
  • the QCL relationship indicated in the control message 315 may indicate a QCL relationship between one or more actual resources (e.g., via which the second set of reference signals was transmitted) and the resources corresponding to the beam to be used for the downlink signaling 320.
  • use of the QCL types corresponding to both spatial and temporal parameters may be conditioned on the QCL source resources (e.g., the source of the TCI state) being virtual resources (e.g., on which no reference signals 305 are actually transmitted) .
  • Such virtual resources may be reported by the UE 115-b with predicted channel characteristics.
  • the UE 115-b may transmit (e.g., via the report 310) one or more predicted channel characteristics, such as a predicted L1-RSRP, L1-SINR, RI, CQI, PMI, top set of K resources (e.g., top-K resources) , or any combination thereof, for the set of virtual resources.
  • the UE 115-b may also report (e.g., in the report 310) that the predicted channel characteristics correspond to virtual resources.
  • the report 310 may include an indication of whether the reported predicted channel characteristics correspond to virtual resources, or actual resources.
  • the network entity 105-b may determine that the reported channel characteristics correspond to virtual resources (e.g., based on configuring such resources at 325, or based on a lack of transmission of corresponding reference signals, or the like) .
  • the QCL relationship from set 335-c may be conditioned on the source of the TCI state being virtual resources configured by the network entity 105-b to be considered as prediction target resources.
  • the UE 115-b may therefore be expected to at least identify predicted channel characteristics associated with the configured virtual resources.
  • the UE 115-b may also be configured to report the predicted channel characteristics (e.g., via control signaling 325) .
  • the network entity 105-b may select a QCL type from the set 335-c (e.g., including both spatial and temporal parameters) for the TCI state indicated in the control message 315.
  • the QCL type (e.g., including the set 335-c) may be RRC configured (e.g., via one or more control messages 315, or via the control signaling 325) .
  • a QCL type (e.g., QCL typeF, QCL typeG, or QCL typeH) may be indicated for use by the UE 115-b by RRC configuration.
  • RRCI signaling (e.g., control signaling 325) may define multiple candidate TCI states, one or more of which may indicate QCL types of set 335-c.
  • a QCL type (e.g., QCL typeF, QCL typeG, or QCL typeH) may be RRC configured and activated by a media access control (MAC) control element (CE) message.
  • MAC media access control
  • a list or set of candidate TCI states indicating QCL types (e.g., the set 335-c of QCL types) may be configured via RRC signaling (e.g., control signaling 325) , and a MAC-CE may activate one or more of the TCI states indicating the enhanced QCL types (e.g., the MAC-CE may activate a TCI state indicating a QCL type from the set 335-c) .
  • the TCI state indicating the QCL type may be indicated in a DCI message (e.g., a control message 315) .
  • the TCI state in the DCI message may define the QCL typeH, QCL type H, or QCL typeF.
  • RRC signaling may configure multiple candidate TCI states or multiple set of candidate TCI states (e.g., some of which indicate the QCL types of set 335-c)
  • the MAC-CE may activate a subset of the TCI states (e.g., one or more of which may indicate a QCL type of the set 335-c)
  • the DCI message scheduling the downlink signaling 320 may include an activated TCI state indicating one of the QCL types of the set 335-c (e.g., QCL typeF, QCL typeG, or QCL typeH) .
  • the UE 115-b may transmit the report 310, which may be a CSI report.
  • CSI reporting maybe associated with virtual (e.g., or physical) QCL typeF, QCL typeG, or QCL typeH source resources.
  • the network entity 105-b may configure the UE 115-b (e.g., via the control signaling 325) to transmit periodic CSI reports, semi-persistent CSI reports, or aperiodic CSI reports.
  • the channel measurement resources (CMR) associated with the CSI report may be based on actual downlink reference signal resources (e.g., SSB or CSI-RS resources, which may be related to other downlink reference signals associated with virtual resources) .
  • the report quantities associated with the QCL source resources may be further associated with the CSI report.
  • the CSI report may indicate virtual resources or physical resources corresponding to the predicted beams.
  • the type of QCL may be based on (e.g., a function of) a use case in terms of level of beam shape consistency.
  • the network entity 105-b may indicate more stringent consistency between beams (e.g., QCL typeF) , compared to temporal beam prediction (e.g., in which case the network entity 105-b may indicate a less stringent consistency between beams, such as QCL typeH) .
  • the beam consistency defined by the set 335-c of QCL types may be utilized in beam prediction training of the AI/ML model, and then applied to the beam inference procedure, as described herein.
  • the UE 15-b may receive downlink signaling 320 using a receive beam indicated by the QCL type indicated by the TCI state in the control message 315.
  • the network entity 105-b may transmit the downlink signaling 320 via a transmit beam that is similar in size and shape (e.g., is within a threshold difference) with reference to the transmit beam indicated by the predicted beam reported by the UE 115-b.
  • FIG. 4 shows an example of a process flow 400 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the process flow 400 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, or the wireless communications system 300.
  • the process flow 400 may include a network entity 105-c and a UE 115-c, which may be examples of corresponding devices described with reference to FIGs. 1-3.
  • the UE 115-c may receive (e.g., from the network entity 105-c) control signaling.
  • the control signaling may indicate a first set of resources (e.g., beam measurement resources) and a second set of resources (e.g., beam prediction resources) .
  • the second set of resources may be virtual prediction target resources.
  • the control signaling may schedule one or more CSI reports (e.g., including the CSI report at 420) .
  • the control signaling may indicate the first set of resources for one or more measurements, and may indicate a set of one or more report quantities associated with the second set of resources (e.g., according to the QCL relationship) .
  • the UE 115-c may receive (e.g., from the network entity 105-c) one or more reference signals (e.g., SSBs, CSI-RSs, among other examples) via a first set of beams (e.g., set B beams or measurement beams, such as the beams 215 described with reference to FIG. 2) corresponding to a first set of resources (e.g., set B resources or measurement resources) .
  • a first set of beams e.g., set B beams or measurement beams, such as the beams 215 described with reference to FIG. 2
  • a first set of resources e.g., set B resources or measurement resources
  • the UE 115-c may perform one or more measurements on the reference signals.
  • the UE 115-c may generate the set of predicted channel characteristics associated with the second set of resources based on receiving the reference signals via the first set of resources without receiving any reference signals via the second set of resources based at least in part on the control signaling.
  • the set of predicted channel characteristics may be associated with the second set of resources according to the QCL relationship.
  • the UE 115-c may transmit a report (e.g., a CSI report) .
  • the report may include an indication of a set of one or more preferred beams of a second set of beams (e.g., predicted beams, such as the beams 220 described with reference to FIG. 2) based at least in part on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources (e.g., prediction resources) .
  • the set of predicted channel characteristics associated with the second set of beams may be based at least in part on one or more measurements performed on the plurality of reference signals.
  • the UE 115-c may receive a control message (e.g., a DCI, a MAC-CE, an RRC message, or any combination thereof) .
  • the control message may include a TCI state indicate a QCL relationship.
  • the QCL relationship may be between a downlink receive beam and the set of one or more preferred beams indicated in the report.
  • the QCL relationship may include one or more spatial parameters (e.g., a spatial receive parameter) , and one or more temporal beam parameters.
  • the QCL may be a QCL typeF, a QCL typeG, or a QCL type H (e.g., may be a QCL type that combines elements of QCL typeA, QCL typeB, and QCL typeC, with QCL typeD) .
  • the QCL relationship may be based on a use case of a beam prediction procedure.
  • a first candidate QCL relationship may correspond to a first level of beam shape consistency between the first set of beams and the second set of beams (e.g., QCL typeF)
  • a second candidate QCL relationship may correspond to a second level of beam shape consistency between the first set of beams and the second set of beams (e.g., QCL typeG or QCL typeH) .
  • the predicted channel characteristics associated with the second set of beams is based at least in part on a second QCL relationship between the first set of beams, and the second set of beams, the second QCL relationship including a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters. For example, as described in greater detail with reference to FIG.
  • the first set of beams or the first set of resources may be related to the second set of beams or the second set of resources (e.g., each beam of set A beams or each resource of set B resources) according to a QCL relationship including both spatial and temporal parameters (e.g., such that beam size and shape of set A beams and set B beams satisfies a threshold level of consistency) .
  • the predicted channel characteristics associated with the second set of beams is based at least in part on the AI/ML model trained according to at least a third set of beams corresponding to a third set of resources (e.g., beams 205, as described with reference to FIG. 2) and a fourth set of beams corresponding to a fourth set of resources (e.g., beams 210, as described with reference to FIG. 2) , wherein a second QCL relationship (e.g., a QCL typeF, QCL typeG, or QCL typeH) exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof.
  • a second QCL relationship e.g., a QCL typeF, QCL typeG, or QCL typeH
  • the predicted channel characteristics may be generated according to the AI/ML model, and the AI/ML model may be based on a QCL relationship (e.g., QCL typeF, QCL typeG, or QCL typeH) , such that each beam of set A beam used in beam training (e.g., each beam 210) corresponds to a respective set A beam used in beam inference (e.g., to a respective beam 220) according to the QCL relationship, and each beam of set B used in beam training (e.g., each beam 205) corresponds to a respective set B beam used in beam inference (e.g., to a respective beam 215) according to the QCL relationship.
  • QCL relationship e.g., QCL typeF, QCL typeG, or QCL typeH
  • the UE 115-c may receive downlink signaling from the network entity 105-c according to the QCL relationship.
  • the network entity 105-c may utilize a transmit beam according to the QCL relationship, such that the beam used for transmitting the downlink signaling at 430 is similar (e.g., in size and shape) to a predicted beam indicated by the UE 115-c at 420.
  • FIG. 5 shows a block diagram 500 of a device 505 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the device 505 may be an example of aspects of a UE 115 as described herein.
  • the device 505 may include a receiver 510, a transmitter 515, and a communications manager 520.
  • the device 505, or one or more components of the device 505 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to predictive beam management according to QCL types) . Information may be passed on to other components of the device 505.
  • the receiver 510 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 515 may provide a means for transmitting signals generated by other components of the device 505.
  • the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to predictive beam management according to QCL types) .
  • the transmitter 515 may be co-located with a receiver 510 in a transceiver module.
  • the transmitter 515 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for performing various aspects of predictive beam management according to QCL types as described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • microcontroller discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • At least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both.
  • the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 520 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 520 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the communications manager 520 is capable of, configured to, or operable to support a means for transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the communications manager 520 is capable of, configured to, or operable to support a means for receiving a control message including an indication of a QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the communications manager 520 is capable of, configured to, or operable to support a means for receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • the device 505 e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof
  • the device 505 may support techniques for improving beam consistency resulting in more reliable wireless communications, decreased latency, and improved user experience.
  • FIG. 6 shows a block diagram 600 of a device 605 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the device 605 may be an example of aspects of a device 505 or a UE 115 as described herein.
  • the device 605 may include a receiver 610, a transmitter 615, and a communications manager 620.
  • the device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, the communications manager 620) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to predictive beam management according to QCL types) . Information may be passed on to other components of the device 605.
  • the receiver 610 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 615 may provide a means for transmitting signals generated by other components of the device 605.
  • the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to predictive beam management according to QCL types) .
  • the transmitter 615 may be co-located with a receiver 610 in a transceiver module.
  • the transmitter 615 may utilize a single antenna or a set of multiple antennas.
  • the device 605, or various components thereof, may be an example of means for performing various aspects of predictive beam management according to QCL types as described herein.
  • the communications manager 620 may include a measurement resource manager 625, a predicted beam manager 630, a QCL manager 635, a downlink signaling manager 640, or any combination thereof.
  • the communications manager 620 may be an example of aspects of a communications manager 520 as described herein.
  • the communications manager 620, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both.
  • the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 620 may support wireless communications in accordance with examples as disclosed herein.
  • the measurement resource manager 625 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the predicted beam manager 630 is capable of, configured to, or operable to support a means for transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the QCL manager 635 is capable of, configured to, or operable to support a means for receiving a control message including an indication of a QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the downlink signaling manager 640 is capable of, configured to, or operable to support a means for receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • FIG. 7 shows a block diagram 700 of a communications manager 720 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein.
  • the communications manager 720, or various components thereof, may be an example of means for performing various aspects of predictive beam management according to QCL types as described herein.
  • the communications manager 720 may include a measurement resource manager 725, a predicted beam manager 730, a QCL manager 735, a downlink signaling manager 740, a virtual resource manager 745, a CSI report manager 750, a beam shape consistency manager 755, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the communications manager 720 may support wireless communications in accordance with examples as disclosed herein.
  • the measurement resource manager 725 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the predicted beam manager 730 is capable of, configured to, or operable to support a means for transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the QCL manager 735 is capable of, configured to, or operable to support a means for receiving a control message including an indication of a QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the downlink signaling manager 740 is capable of, configured to, or operable to support a means for receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • the virtual resource manager 745 is capable of, configured to, or operable to support a means for receiving control signaling indicating the second set resources, where the second set of resources includes virtual prediction target resources. In some examples, the virtual resource manager 745 is capable of, configured to, or operable to support a means for generating the set of predicted channel characteristics associated with the second set of resources based on receiving the set of multiple reference signals via the first set of resources without receiving any reference signals via the second set of resources based on the control signaling, the set of predicted channel characteristics is associated with the second set of resources according to the QCL relationship.
  • control message includes a transmission configuration indicator state including the indication of the QCL relationship.
  • the CSI report manager 750 is capable of, configured to, or operable to support a means for receiving control signaling scheduling one or more channel state information reports, the control signaling indicating the first set of resources for the one or more measurements and indicating a set of one or more report quantities including the set of predicted channel characteristics associated with the second set of resources.
  • the CSI report manager 750 is capable of, configured to, or operable to support a means for transmitting the one or more channel state information reports based on the one or more measurements and the set of predicted channel characteristics, where the set of predicted channel characteristics is associated with the second set of resources based on the QCL relationship.
  • the QCL relationship is based on a use case of a beam prediction procedure.
  • a first candidate QCL relationship of a set of multiple candidate QCL relationships corresponds to a first level of beam shape consistency between the first set of beams and the second set of beams
  • a second candidate QCL relationship of the set of multiple candidate QCL relationships corresponds to a second level of beam shape consistency between the first set of beams and the second set of beams.
  • the QCL relationship includes the first candidate QCL relationship based on the use case of the beam prediction procedure relying on the first level of beam shape consistency.
  • the set of one or more spatial beam parameters includes a set of spatial receive beam parameters at the UE, and the set of one or more temporal beam parameters include a Doppler shift, a Doppler spread, an average delay, a delay spread, or any combination thereof.
  • the predicted channel characteristics associated with the second set of beams is based on a second QCL relationship between the first set of beams, and the second set of beams, the second QCL relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • the predicted channel characteristics associated with the second set of beams is based on a machine learning model trained according to at least a third set of beams corresponding to a third set of resources including measurement resources, and a fourth set of beams corresponding to a fourth set of resources including prediction target resources.
  • a second QCL relationship exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof.
  • the second QCL relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • FIG. 8 shows a diagram of a system 800 including a device 805 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the device 805 may be an example of or include components of a device 505, a device 605, or a UE 115 as described herein.
  • the device 805 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) .
  • the device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller, such as an I/O controller 810, a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845) .
  • a bus 845 e.g., a bus 845
  • the I/O controller 810 may manage input and output signals for the device 805.
  • the I/O controller 810 may also manage peripherals not integrated into the device 805.
  • the I/O controller 810 may represent a physical connection or port to an external peripheral.
  • the I/O controller 810 may utilize an operating system such as or another known operating system.
  • the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 810 may be implemented as part of one or more processors, such as the at least one processor 840.
  • a user may interact with the device 805 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.
  • the device 805 may include a single antenna. However, in some other cases, the device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 815 may communicate bi-directionally via the one or more antennas 825 using wired or wireless links as described herein.
  • the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825.
  • the transceiver 815 may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.
  • the at least one memory 830 may include random access memory (RAM) and read-only memory (ROM) .
  • the at least one memory 830 may store computer-readable, computer-executable, or processor-executable code, such as the code 835.
  • the code 835 may include instructions that, when executed by the at least one processor 840, cause the device 805 to perform various functions described herein.
  • the code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 835 may not be directly executable by the at least one processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 830 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the at least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 840 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the at least one processor 840.
  • the at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting predictive beam management according to QCL types) .
  • the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein.
  • the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories.
  • the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 835 (e.g., processor-executable code) stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.
  • code 835 e.g., processor-executable code
  • the communications manager 820 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 820 is capable of, configured to, or operable to support a means for receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the communications manager 820 is capable of, configured to, or operable to support a means for transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the communications manager 820 is capable of, configured to, or operable to support a means for receiving a control message including an indication of a QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the communications manager 820 is capable of, configured to, or operable to support a means for receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • the device 805 may support techniques for improving beam consistency resulting in more reliable wireless communications, more efficiency use of available system resources, decreased system latency, and improved user experience.
  • the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof.
  • the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof.
  • the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of predictive beam management according to QCL types as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the device 905 may be an example of aspects of a network entity 105 as described herein.
  • the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
  • the device 905, or one or more components of the device 905 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 905.
  • the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905.
  • the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of predictive beam management according to QCL types as described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
  • the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 920 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 920 is capable of, configured to, or operable to support a means for outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the communications manager 920 is capable of, configured to, or operable to support a means for obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the communications manager 920 is capable of, configured to, or operable to support a means for outputting a control message including an indication of a QCL relationship between a downlink beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the communications manager 920 is capable of, configured to, or operable to support a means for outputting downlink signaling using the downlink beam according to the control message and the QCL relationship.
  • the device 905 e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof
  • the device 905 may support techniques for improving beam consistency resulting in more reliable wireless communications, decreased latency, and improved user experience.
  • FIG. 10 shows a block diagram 1000 of a device 1005 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein.
  • the device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020.
  • the device 1005, or one of more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1005.
  • the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005.
  • the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the device 1005, or various components thereof, may be an example of means for performing various aspects of predictive beam management according to QCL types as described herein.
  • the communications manager 1020 may include a measurement resource manager 1025, a predicted beam manager 1030, a QCL manager 1035, a downlink signaling manager 1040, or any combination thereof.
  • the communications manager 1020 may be an example of aspects of a communications manager 920 as described herein.
  • the communications manager 1020, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both.
  • the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1020 may support wireless communications in accordance with examples as disclosed herein.
  • the measurement resource manager 1025 is capable of, configured to, or operable to support a means for outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the predicted beam manager 1030 is capable of, configured to, or operable to support a means for obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the QCL manager 1035 is capable of, configured to, or operable to support a means for outputting a control message including an indication of a QCL relationship between a downlink beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the downlink signaling manager 1040 is capable of, configured to, or operable to support a means for outputting downlink signaling using the downlink beam according to the control message and the QCL relationship.
  • FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein.
  • the communications manager 1120, or various components thereof, may be an example of means for performing various aspects of predictive beam management according to QCL types as described herein.
  • the communications manager 1120 may include a measurement resource manager 1125, a predicted beam manager 1130, a QCL manager 1135, a downlink signaling manager 1140, a virtual resource manager 1145, a CSI report manager 1150, or any combination thereof.
  • Each of these components, or components or subcomponents thereof may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
  • the communications manager 1120 may support wireless communications in accordance with examples as disclosed herein.
  • the measurement resource manager 1125 is capable of, configured to, or operable to support a means for outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the predicted beam manager 1130 is capable of, configured to, or operable to support a means for obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the QCL manager 1135 is capable of, configured to, or operable to support a means for outputting a control message including an indication of a QCL relationship between a downlink beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the downlink signaling manager 1140 is capable of, configured to, or operable to support a means for outputting downlink signaling using the downlink beam according to the control message and the QCL relationship.
  • the virtual resource manager 1145 is capable of, configured to, or operable to support a means for outputting control signaling indicating the second set resources, where the second set of resources includes virtual prediction target resources, where the set of predicted channel characteristics associated with the second set of resources is based on outputting the set of multiple reference signals via the first set of resources without outputting any reference signals via the second set of resources based on the control signaling, the set of predicted channel characteristics is associated with the second set of resources according to the QCL relationship.
  • control message includes a transmission configuration indicator state including the indication of the QCL relationship.
  • the CSI report manager 1150 is capable of, configured to, or operable to support a means for outputting control signaling scheduling one or more channel state information reports, the control signaling indicating the first set of resources for the one or more measurements and indicating a set of one or more report quantities including the set of predicted channel characteristics associated with the second set of resources.
  • the CSI report manager 1150 is capable of, configured to, or operable to support a means for obtaining the one or more channel state information reports based on the one or more measurements and the set of predicted channel characteristics, where the set of predicted channel characteristics is associated with the second set of resources based on the QCL relationship.
  • the QCL relationship is based on a use case of a beam prediction procedure.
  • a first candidate QCL relationship of a set of multiple candidate QCL relationships corresponds to a first level of beam shape consistency between the first set of beams and the second set of beams
  • a second candidate QCL relationship of the set of multiple candidate QCL relationships corresponds to a second level of beam shape consistency between the first set of beams and the second set of beams
  • the QCL relationship includes the first candidate QCL relationship based on the use case of the beam prediction procedure relying on the first level of beam shape consistency.
  • the set of one or more spatial beam parameters includes a beam direction, beam size, beam shape, beam power, or any combination thereof
  • the set of one or more temporal beam parameters include a Doppler shift, a Doppler spread, an average delay, a delay spread, or any combination thereof.
  • the predicted channel characteristics associated with the second set of beams is based on a second QCL relationship between the first set of beams, and the second set of beams, the second QCL relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • the predicted channel characteristics associated with the second set of beams is based on a machine learning model trained according to at least a third set of beams corresponding to a third set of resources including measurement resources, and a fourth set of beams corresponding to a fourth set of resources including prediction target resources.
  • a second QCL relationship exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof.
  • the second QCL relationship includes a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the device 1205 may be an example of or include components of a device 905, a device 1005, or a network entity 105 as described herein.
  • the device 1205 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof.
  • the communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, one or more antennas 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240) .
  • a communications manager 1220 e.g., operatively, communicatively, functionally, electronically, electrically
  • buses e.g., a bus 1240
  • the transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein.
  • the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
  • the transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver) , and to demodulate signals.
  • the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1210 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
  • the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or one or more memory components may be included in a chip or chip assembly that is installed in the device 1205.
  • the at least one memory 1225 may include RAM, ROM, or any combination thereof.
  • the at least one memory 1225 may store computer-readable, computer-executable, or processor-executable code, such as the code 1230.
  • the code 1230 may include instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform various functions described herein.
  • the code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by a processor of the at least one processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1225 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories.
  • One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .
  • the at least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1235 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into one or more of the at least one processor 1235.
  • the at least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting predictive beam management according to QCL types) .
  • the device 1205 or a component of the device 1205 may include at least one processor 1235 and at least one memory 1225 coupled with one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 configured to perform various functions described herein.
  • the at least one processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205.
  • the at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within one or more of the at least one memory 1225) .
  • the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories.
  • the at least one processor 1235 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1235) and memory circuitry (which may include the at least one memory 1225) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1235 or a processing system including the at least one processor 1235 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1225 or otherwise, to perform one or more of the functions described herein.
  • a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack.
  • a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the device 1205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the at least one memory 1225, the code 1230, and the at least one processor 1235 may be located in one of the different components or divided between different components) .
  • the communications manager 1220 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1220 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1220 may manage communications with one or more other network devices (e.g., network entities 105) , and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices) .
  • the communications manager 1220 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the communications manager 1220 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for outputting a control message including an indication of a QCL relationship between a downlink beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for outputting downlink signaling using the downlink beam according to the control message and the QCL relationship.
  • the device 1205 may support techniques for improving beam consistency resulting in more reliable wireless communications, more efficiency use of available system resources, decreased system latency, and improved user experience.
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable) , or any combination thereof.
  • the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, one or more of the at least one processor 1235, one or more of the at least one memory 1225, the code 1230, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1235, the at least one memory 1225, the code 1230, or any combination thereof) .
  • the code 1230 may include instructions executable by one or more of the at least one processor 1235 to cause the device 1205 to perform various aspects of predictive beam management according to QCL types as described herein, or the at least one processor 1235 and the at least one memory 1225 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 13 shows a flowchart illustrating a method 1300 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1300 may be implemented by a UE or its components as described herein.
  • the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a measurement resource manager 725 as described with reference to FIG. 7.
  • the method may include transmitting an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a predicted beam manager 730 as described with reference to FIG. 7.
  • the method may include receiving a control message including an indication of a QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by a QCL manager 735 as described with reference to FIG. 7.
  • the method may include receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • the operations of 1320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by a downlink signaling manager 740 as described with reference to FIG. 7.
  • FIG. 14 shows a flowchart illustrating a method 1400 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1400 may be implemented by a UE or its components as described herein.
  • the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a measurement resource manager 725 as described with reference to FIG. 7.
  • the method may include receiving control signaling indicating a second set resources, where the second set of resources includes virtual prediction target resources.
  • the operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a virtual resource manager 745 as described with reference to FIG. 7.
  • the method may include generating the set of predicted channel characteristics associated with the second set of resources based on receiving the set of multiple reference signals via the first set of resources without receiving any reference signals via the second set of resources based on the control signaling, the set of predicted channel characteristics is associated with the second set of resources according to the QCL relationship.
  • the operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a virtual resource manager 745 as described with reference to FIG. 7.
  • the method may include transmitting an indication of a set of one or more preferred beams of the second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, where the set of predicted channel characteristics is associated with the second set of resources according to the QCL relationship.
  • the operations of 1420 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by a predicted beam manager 730 as described with reference to FIG. 7.
  • the method may include receiving a control message including an indication of a QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the operations of 1425 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1425 may be performed by a QCL manager 735 as described with reference to FIG. 7.
  • the method may include receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • the operations of 1430 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1430 may be performed by a downlink signaling manager 740 as described with reference to FIG. 7.
  • FIG. 15 shows a flowchart illustrating a method 1500 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a UE or its components as described herein.
  • the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a measurement resource manager 725 as described with reference to FIG. 7.
  • the method may include receiving control signaling scheduling one or more channel state information reports, the control signaling indicating the first set of resources for the one or more measurements and indicating a set of one or more report quantities including a set of predicted channel characteristics associated with a second set of resources.
  • the operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a CSI report manager 750 as described with reference to FIG. 7.
  • the method may include transmitting the one or more channel state information reports based on the one or more measurements and the set of predicted channel characteristics, where the one or more channel state information reports comprises an indication of the set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals, and where the set of predicted channel characteristics is associated with the second set of resources based on a QCL relationship.
  • the operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a CSI report manager 750 as described with reference to FIG. 7.
  • the method may include receiving a control message including an indication of the QCL relationship between a downlink receive beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a QCL manager 735 as described with reference to FIG. 7.
  • the method may include receiving downlink signaling using the downlink receive beam according to the control message and the QCL relationship.
  • the operations of 1525 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed by a downlink signaling manager 740 as described with reference to FIG. 7.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports predictive beam management according to QCL types in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1600 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include outputting a set of multiple reference signals via a first set of beams corresponding to a first set of resources including measurement resources.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a measurement resource manager 1125 as described with reference to FIG. 11.
  • the method may include obtaining an indication of a set of one or more preferred beams of a second set of beams based on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources including prediction target resources, the set of predicted channel characteristics associated with the second set of beams based on one or more measurements performed on the set of multiple reference signals.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a predicted beam manager 1130 as described with reference to FIG. 11.
  • the method may include outputting a control message including an indication of a QCL relationship between a downlink beam and the set of one or more preferred beams, where the QCL relationship includes a set of one or more spatial beam parameters and a set of one or more temporal beam parameters.
  • the operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a QCL manager 1135 as described with reference to FIG. 11.
  • the method may include outputting downlink signaling using the downlink beam according to the control message and the QCL relationship.
  • the operations of 1620 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed by a downlink signaling manager 1140 as described with reference to FIG. 11.
  • a method for wireless communications at a UE comprising: receiving a plurality of reference signals via a first set of beams corresponding to a first set of resources comprising measurement resources; transmitting an indication of a set of one or more preferred beams of a second set of beams based at least in part on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources comprising prediction target resources, the set of predicted channel characteristics associated with the second set of beams based at least in part on one or more measurements performed on the plurality of reference signals; receiving a control message comprising an indication of a quasi colocation relationship between a downlink receive beam and the set of one or more preferred beams, wherein the quasi colocation relationship comprises a set of one or more spatial beam parameters and a set of one or more temporal beam parameters; and receiving downlink signaling using the downlink receive beam according to the control message and the quasi colocation relationship.
  • Aspect 2 The method of aspect 1, further comprising: receiving control signaling indicating the second set resources, wherein the second set of resources comprises virtual prediction target resources; and generating the set of predicted channel characteristics associated with the second set of resources based on receiving the plurality of reference signals via the first set of resources without receiving any reference signals via the second set of resources based at least in part on the control signaling, the set of predicted channel characteristics is associated with the second set of resources according to the quasi colocation relationship.
  • Aspect 3 The method of any of aspects 1 through 2, wherein the control message comprises a transmission configuration indicator state comprising the indication of the quasi colocation relationship.
  • Aspect 4 The method of any of aspects 1 through 3, further comprising: receiving control signaling scheduling one or more channel state information reports, the control signaling indicating the first set of resources for the one or more measurements and indicating a set of one or more report quantities comprising the set of predicted channel characteristics associated with the second set of resources; and transmitting the one or more channel state information reports based at least in part on the one or more measurements and the set of predicted channel characteristics, wherein the set of predicted channel characteristics is associated with the second set of resources based at least in part on the quasi colocation relationship.
  • Aspect 5 The method of any of aspects 1 through 4, wherein the quasi colocation relationship is based at least in part on a use case of a beam prediction procedure.
  • Aspect 6 The method of aspect 5, wherein a first candidate quasi colocation relationship of a plurality of candidate quasi colocation relationships corresponds to a first level of beam shape consistency between the first set of beams and the second set of beams, and a second candidate quasi colocation relationship of the plurality of candidate quasi colocation relationships corresponds to a second level of beam shape consistency between the first set of beams ad the second set of beams, and the quasi colocation relationship comprises the first candidate quasi colocation relationship based at least in part on the use case of the beam prediction procedure relying on the first level of beam shape consistency.
  • Aspect 7 The method of any of aspects 1 through 6, wherein the set of one or more spatial beam parameters comprises a set of spatial receive beam parameters at the UE, and the set of one or more temporal beam parameters comprise a Doppler shift, a Doppler spread, an average delay, a delay spread, or any combination thereof.
  • Aspect 8 The method of any of aspects 1 through 7, wherein the predicted channel characteristics associated with the second set of beams is based at least in part on a second quasi colocation relationship between the first set of beams, and the second set of beams, the second quasi colocation relationship comprises a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • Aspect 9 The method of any of aspects 1 through 8, wherein the predicted channel characteristics associated with the second set of beams is based at least in part on a machine learning model trained according to at least a third set of beams corresponding to a third set of resources comprising measurement resources, and a fourth set of beams corresponding to a fourth set of resources comprising prediction target resources, a second quasi colocation relationship exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof, and the second quasi colocation relationship comprises a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • a method for wireless communications at a network entity comprising: outputting a plurality of reference signals via a first set of beams corresponding to a first set of resources comprising measurement resources; obtaining an indication of a set of one or more preferred beams of a second set of beams based at least in part on a set of predicted channel characteristics associated with the second set of beams corresponding to a second set of resources comprising prediction target resources, the set of predicted channel characteristics associated with the second set of beams based at least in part on one or more measurements performed on the plurality of reference signals; outputting a control message comprising an indication of a quasi colocation relationship between a downlink beam and the set of one or more preferred beams, wherein the quasi colocation relationship comprises a set of one or more spatial beam parameters and a set of one or more temporal beam parameters; and outputting downlink signaling using the downlink beam according to the control message and the quasi colocation relationship.
  • Aspect 11 The method of aspect 10, further comprising: outputting control signaling indicating the second set resources, wherein the second set of resources comprises virtual prediction target resources, wherein the set of predicted channel characteristics associated with the second set of resources is based on outputting the plurality of reference signals via the first set of resources without outputting any reference signals via the second set of resources based at least in part on the control signaling, the set of predicted channel characteristics is associated with the second set of resources according to the quasi colocation relationship.
  • Aspect 12 The method of any of aspects 10 through 11, wherein the control message comprises a transmission configuration indicator state comprising the indication of the quasi colocation relationship.
  • Aspect 13 The method of any of aspects 10 through 12, further comprising: outputting control signaling scheduling one or more channel state information reports, the control signaling indicating the first set of resources for the one or more measurements and indicating a set of one or more report quantities comprising the set of predicted channel characteristics associated with the second set of resources; and obtaining the one or more channel state information reports based at least in part on the one or more measurements and the set of predicted channel characteristics, wherein the set of predicted channel characteristics is associated with the second set of resources based at least in part on the quasi colocation relationship.
  • Aspect 14 The method of any of aspects 10 through 13, wherein the quasi colocation relationship is based at least in part on a use case of a beam prediction procedure.
  • Aspect 15 The method of any of aspects 10 through 14, wherein a first candidate quasi colocation relationship of a plurality of candidate quasi colocation relationships corresponds to a first level of beam shape consistency between the first set of beams and the second set of beams, and a second candidate quasi colocation relationship of the plurality of candidate quasi colocation relationships corresponds to a second level of beam shape consistency between the first set of beams and the second set of beams, and the quasi colocation relationship comprises the first candidate quasi colocation relationship based at least in part on the use case of the beam prediction procedure relying on the first level of beam shape consistency.
  • Aspect 16 The method of any of aspects 10 through 15, wherein the set of one or more spatial beam parameters comprises a beam direction, beam size, beam shape, beam power, or any combination thereof, and the set of one or more temporal beam parameters comprise a Doppler shift, a Doppler spread, an average delay, a delay spread, or any combination thereof.
  • Aspect 17 The method of any of aspects 10 through 16, wherein the predicted channel characteristics associated with the second set of beams is based at least in part on a second quasi colocation relationship between the first set of beams, and the second set of beams, the second quasi colocation relationship comprises a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • Aspect 18 The method of any of aspects 10 through 17, wherein the predicted channel characteristics associated with the second set of beams is based at least in part on a machine learning model trained according to at least a third set of beams corresponding to a third set of resources comprising measurement resources, and a fourth set of beams corresponding to a fourth set of resources comprising prediction target resources, a second quasi colocation relationship exists between the first set of beams and the third set of beams, between the second set of beams and the third set of beams, or a combination thereof, and the second quasi colocation relationship comprises a second set of one or more spatial beam parameters and a second set of one or more temporal beam parameters.
  • a UE for wireless communications comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 9.
  • a UE for wireless communications comprising at least one means for performing a method of any of aspects 1 through 9.
  • Aspect 21 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 9.
  • a network entity for wireless communications comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 10 through 18.
  • a network entity for wireless communications comprising at least one means for performing a method of any of aspects 10 through 18.
  • Aspect 24 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 10 through 18.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a 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 in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
  • the functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
  • the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components.
  • the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function.
  • a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components.
  • a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.
  • subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components.
  • referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Artificial Intelligence (AREA)
  • Evolutionary Computation (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs destinés aux communications sans fil. Un équipement utilisateur (UE) peut prédire des faisceaux pour un ensemble de ressources sur la base de mesures prises par l'intermédiaire d'un autre ensemble de faisceaux et de ressources. Comme décrit ici, l'entité de réseau peut indiquer une relation de quasi-colocalisation (QCL) qui indique à la fois des paramètres temporels et des paramètres spatiaux. Une telle relation QCL peut augmenter la cohérence entre des faisceaux prédits rapportés par l'UE, et le faisceau de transmission réel utilisé par l'entité de réseau pour des transmissions en liaison descendante ultérieures. De telles relations QCL peuvent combiner des paramètres temporels et spatiaux indiqués par d'autres relations QCL. La relation QCL peut également s'appliquer aux faisceaux de mesure et aux faisceaux prédits, ou peut s'appliquer à travers une inférence de faisceau et un apprentissage de prédiction de faisceau à l'aide d'un modèle d'apprentissage automatique.
PCT/CN2024/077282 2024-02-16 2024-02-16 Gestion prédictive de faisceau selon des types de quasi-colocalisation Pending WO2025171593A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2024/077282 WO2025171593A1 (fr) 2024-02-16 2024-02-16 Gestion prédictive de faisceau selon des types de quasi-colocalisation
PCT/CN2025/076767 WO2025171783A1 (fr) 2024-02-16 2025-02-11 Nouveaux types de qcl pour la gestion prédictive de faisceaux

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077282 WO2025171593A1 (fr) 2024-02-16 2024-02-16 Gestion prédictive de faisceau selon des types de quasi-colocalisation

Publications (1)

Publication Number Publication Date
WO2025171593A1 true WO2025171593A1 (fr) 2025-08-21

Family

ID=96772298

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2024/077282 Pending WO2025171593A1 (fr) 2024-02-16 2024-02-16 Gestion prédictive de faisceau selon des types de quasi-colocalisation
PCT/CN2025/076767 Pending WO2025171783A1 (fr) 2024-02-16 2025-02-11 Nouveaux types de qcl pour la gestion prédictive de faisceaux

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/076767 Pending WO2025171783A1 (fr) 2024-02-16 2025-02-11 Nouveaux types de qcl pour la gestion prédictive de faisceaux

Country Status (1)

Country Link
WO (2) WO2025171593A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117014047A (zh) * 2022-04-29 2023-11-07 中兴通讯股份有限公司 通信方法、设备和存储介质
CN117035018A (zh) * 2022-04-29 2023-11-10 中兴通讯股份有限公司 波束度量参数反馈方法和接收方法及装置
WO2024035325A1 (fr) * 2022-08-12 2024-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Procédés pour prédictions de faisceau spatial côté dispositif sans fil

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12335757B2 (en) * 2021-03-08 2025-06-17 Qualcomm Incorporated Techniques for beam selection using channel state information reference signal acquisition resources
CN117859386A (zh) * 2021-08-24 2024-04-09 高通股份有限公司 在小区间波束管理中跟踪传输配置指示状态
WO2024030604A1 (fr) * 2022-08-05 2024-02-08 Interdigital Patent Holdings, Inc. Validation d'intelligence artificielle (ia)/apprentissage automatique (ml) dans une gestion de faisceau et une prédiction de faisceau hiérarchique

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117014047A (zh) * 2022-04-29 2023-11-07 中兴通讯股份有限公司 通信方法、设备和存储介质
CN117035018A (zh) * 2022-04-29 2023-11-10 中兴通讯股份有限公司 波束度量参数反馈方法和接收方法及装置
WO2024035325A1 (fr) * 2022-08-12 2024-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Procédés pour prédictions de faisceau spatial côté dispositif sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Remaining issues on beam measurement and reporting", 3GPP DRAFT; R1-1801520_REMAINING ISSUES ON BEAM MEASUREMENT AND REPORTING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, Greece; 20180226 - 20180302, 15 February 2018 (2018-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051396772 *

Also Published As

Publication number Publication date
WO2025171783A1 (fr) 2025-08-21

Similar Documents

Publication Publication Date Title
WO2023184062A1 (fr) Configurations de ressources d'informations d'état de canal pour prédiction de faisceau
WO2024065372A1 (fr) Procédés et appareils de rapport de prédiction csi pour un ensemble de faisceaux
WO2024036465A1 (fr) Prédiction et indication de paire de faisceaux
US20240022311A1 (en) Slot aggregation triggered by beam prediction
EP4548670A1 (fr) Sélection d'état d'indicateur de configuration de transmission pour des signaux de référence dans une opération à multiples points de transmission et de réception
WO2024164106A1 (fr) Planification pour bandes de fréquences associées à une capacité de changement de première bande après un commutateur de chaîne de transmission
US20240305504A1 (en) Channel precoder selection for uplink wireless communications
WO2023212890A1 (fr) Techniques de prédiction de caractéristiques de faisceau à l'aide de processus d'apprentissage fédérés
WO2025171783A1 (fr) Nouveaux types de qcl pour la gestion prédictive de faisceaux
WO2025208403A1 (fr) Mappage de signaux de référence à des indicateurs de configuration de transmission pour une gestion et un rapport de faisceau
WO2025179414A1 (fr) Gestion de faisceau déclenchée par un événement lié à la liaison montante
WO2024059960A1 (fr) Rapport de faisceau de liaison montante et de liaison descendante
WO2024207406A1 (fr) Journalisation et signalisation d'opérations pour une gestion de cycle de vie d'apprentissage automatique
WO2024197782A1 (fr) États d'indicateur de configuration de transmission pour prédiction de faisceau spatial
WO2025179416A1 (fr) Configurations d'états de réglage de commande de puissance distincts pour signaux de référence de sondage
WO2024192612A1 (fr) Conditions de correspondance de faisceau avec une prédiction de paire de faisceaux conjoints
US20240349280A1 (en) Methods for symbol aggregation to enable adaptive beam weight communications
US20250192914A1 (en) Model updates with user equipment latent query
US20250260531A1 (en) Sounding reference signal antenna switch with three transmit chains
WO2025107223A1 (fr) Indication de déclenchement de canal d'accès aléatoire pour cellules candidates avec de multiples points de transmission-réception
WO2024234121A1 (fr) Techniques pour un signalement d'identifiants de paramètres en vue de la collecte de données dans une prédiction de faisceau
WO2025102336A1 (fr) Adaptations entre le rapport d'un rapport de prédiction d'affinement de faisceau réel initié par un ue et un rapport de prédiction d'affinement de faisceau virtuel initié par un ue
US20250260971A1 (en) Techniques for resolving uplink and downlink collisions in non-terrestrial networks
WO2024168789A1 (fr) Prédiction de paire de faisceaux au niveau d'une entité de réseau à l'aide d'un rapport de matrice basé sur des coordonnées
WO2024108366A1 (fr) Réglage de modèle pour apprentissage automatique inter-nœuds

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24924367

Country of ref document: EP

Kind code of ref document: A1