Specified channel measurement resources in report for network-side beam prediction
By mandating UE to report measurements for both strong and weak CMRs associated with active TCI states and cycling through CMR subsets, the method addresses suboptimal beamforming in wireless systems, improving reliability and performance through AI-enhanced beam prediction.
Patent Information
- Application Number
- PCT/CN2024/077128
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-09
- Publication Date
- 2025-08-14
AI Technical Summary
Wireless communication systems face challenges in maintaining optimal beamforming due to rapidly changing wireless channels, leading to suboptimal performance and reliability issues, particularly in high-mobility environments, where current channel measurement resources (CMRs) may not include measurements for current transmission configuration indicator (TCI) states, limiting the network's ability to ensure beam switch improvements.
The method involves specifying that user equipment (UE) includes measurements for CMRs associated with one or more recently active TCI states and cycles through different subsets of CMRs in different reporting occasions, ensuring comprehensive beam prediction by reporting both stronger and weaker beams.
This approach enhances beam prediction reliability and performance, resulting in improved quality of service and user experience by utilizing AI and ML models to anticipate optimal beam directions based on historical measurements.
Smart Images

Figure CN2024077128_14082025_PF_FP_ABST
Abstract
Description
SPECIFIED CHANNEL MEASUREMENT RESOURCES IN REPORT FOR NETWORK-SIDE BEAM PREDICTION
[0001] Field of the Disclosure
[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for beam prediction.
[0003] Description of Related Art
[0004] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.
[0005] Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists a need for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.SUMMARY
[0006] One aspect provides a method for wireless communication at a user equipment (UE) . The method includes receiving, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) ; receiving, from a network entity, second signaling prompting a channel state information (CSI) report; and transmitting the CSI report, wherein the CSI report includes measurements for one or more CMRs, from the candidate CMRs, associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.
[0007] Another aspect provides a method for wireless communication at a user equipment (UE) . The method includes receiving, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) ; receiving, from a network entity, second signaling prompting channel state information (CSI) reports; and transmitting the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval.
[0008] Another aspect provides a method for wireless communication at a network entity. The method includes transmitting first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) ; transmitting second signaling prompting a channel state information (CSI) report from the UE, based on one or more CMRs from the of the candidate CMRs; and receiving the CSI report, wherein the CSI report includes measurements for one or more CMRs associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.
[0009] Another aspect provides a method for wireless communication at a network entity. The method includes transmitting first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) ; transmitting second signaling prompting channel state information (CSI) reports based on one or more CMRs from the of the candidate CMRs; and receiving the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval.
[0010] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and / or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed (e.g., directly, indirectly, after pre-processing, without pre-processing) by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and / or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.
[0011] The following description and the appended figures set forth certain features for purposes of illustration.BRIEF DESCRIPTION OF DRAWINGS
[0012] The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.
[0013] FIG. 1 depicts an example wireless communications network.
[0014] FIG. 2 depicts an example disaggregated base station architecture.
[0015] FIG. 3 depicts aspects of an example base station and an example user equipment.
[0016] FIGS. 4A, 4B, 4C, and 4D depict various example aspects of data structures for a wireless communications network.
[0017] FIG. 5 illustrates example beam refinement procedures, in accordance with certain aspects of the present disclosure.
[0018] FIG. 6 is a diagram illustrating example operations where beam management may be performed.
[0019] FIG. 7 illustrates a general functional framework applied for AI-enabled RAN intelligence.
[0020] FIG. 8 depicts an example of channel feedback for channel measurement resources (CMRs) .
[0021] FIG. 9 depicts a call flow diagram, in accordance with certain aspects of the present disclosure.
[0022] FIG. 10 depicts an example scenario involving CSI reporting, in accordance with certain aspects of the present disclosure.
[0023] FIG. 11 depicts a call flow diagram, in accordance with certain aspects of the present disclosure.
[0024] FIG. 12 depicts an example of mandated CMRs in certain reporting occasions, in accordance with certain aspects of the present disclosure.
[0025] FIG. 13 depicts a method for wireless communications.
[0026] FIG. 14 depicts a method for wireless communications.
[0027] FIG. 15 depicts a method for wireless communications.
[0028] FIG. 16 depicts a method for wireless communications.
[0029] FIG. 17 depicts aspects of an example communications device.DETAILED DESCRIPTION
[0030] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for feedback of measurements based on channel measurement resources (CMRs) . In some cases, the feedback may include measurements for certain CMRs mandated by a network entity or based on an agreement or rule.
[0031] In advanced wireless systems, mobility procedures are in place to help maintain network connections for a user equipment (UE) as it moves between the coverage areas of different cells. Mobility procedures generally refer to mechanisms that allow a UE to transition from being served by a source cell to being served by a target cell. In some cases, for physical layer (PHY or Layer 1 / L1) and / or medium access control layer (MAC or Layer 2 / L2) , also referred to as L1 / L2 triggered mobility (LTM) , as a UE moves, a new serving cell (e.g. a primary cell (Pcell) ) may be selected (e.g., reselected) among a set of pre-configured candidate cells based on L1 measurement for those cells.
[0032] Temporal beam prediction, also known as time-domain (TD) beam prediction, generally refers to a technique used in wireless communications to anticipate and optimize the direction of transmission and / or reception beams over time. Temporal beam prediction may involve predicting a beam that will be suitable (preferred) for use in the future. The prediction may be based on current measurements of reference signals sent using different beams (which may or may not include the predicted beam) . Temporal beam prediction may be particularly relevant in scenarios where the wireless channel conditions change rapidly, such as in high-mobility environments or in the presence of fading effects.
[0033] In wireless communication systems that employ beamforming, multiple antennas may be used to transmit and receive signals. By dynamically adjusting the direction of the transmit beam, the transmitted energy may be focused towards the intended receiver, which may mitigate interference from other directions. However, due to the dynamic nature of wireless channels, the optimal beam direction can change rapidly, leading to suboptimal performance if the beamforming strategy is not continuously and effectively updated.
[0034] Beam prediction addresses this challenge by utilizing channel state information (CSI) and exploiting spatial and / or temporal correlations in the wireless channel. By analyzing (current and past) channel measurements, such as received signal strength, signal quality, and / or channel characteristics, it is possible to infer the future behavior of the wireless channel and predict the optimal beam direction.
[0035] In some cases, AI and / or ML models may be trained and used (e.g., at a network entity and / or a UE) to improve wireless communications. For example, ML models may be used to perform temporal beam prediction and / or spatial beam prediction (e.g., prediction for a set of beams, Set-A, based on measurements of a different set of beams, Set-B) . For example, such a model may predict channel characteristics of Set-Abeams based on measurement results (e.g., historic measurement results) of Set-B beams (e.g., where Set-Abeams are narrower than Set-B beams) . Such beam prediction may be performed by a model at the network entity and / or a UE.
[0036] In some cases, channel measurement resources (CMR) for measurement reporting may not include CMR for a current transmission configuration indicator (TCI) state, which may present a challenge to the network in making beam switch decisions. For example, a UE may only report measurement for CMRs with strongest measurements. Without measurement for a current TCI, it may be difficult for the network to ensure a new beam would result in an improvement before triggering an actual beam switch, which may result in reliability issues and / or performance degradation. Reporting both stronger and weaker beams may not be possible, for example, in cases where CSI reporting payload is limited.
[0037] Aspects of the present disclosure provide techniques that allow for specifying that measurements for certain CMRs are included (e.g., or are to be included) in a CSI report and any given reporting occasion. For example, in some cases, it may be specified that a UE include measurements for CMRs associated with one or more recently active TCI states. In some cases, a UE may include measurements for different subsets of CMRs in different reporting occasions. In such cases, a UE may cycle through all candidate CMRs over a number of reporting occasions (e.g., in a round-robin manner) .
[0038] In this manner, CMRs with weaker measurements may be included in the reporting. Utilization of the techniques disclosed herein may help improve beam prediction. Improved beam prediction may result in improved reliability and performance, which may lead to better quality of service and user experience.
[0039] Introduction to Wireless Communications Networks
[0040] The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.
[0041] FIG. 1 depicts an example of a wireless communications network 100, in which aspects described herein may be implemented.
[0042] Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes) . A network entity is generally a communications device and / or a communications function performed by a communications device (e.g., a user equipment (UE) , a base station (BS) , a component of a BS, a server, etc. ) . For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102) , and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.
[0043] In the depicted example, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.
[0044] FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA) , satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (IoT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.
[0045] BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.
[0046] BSs 102 may generally include: a NodeB, enhanced NodeB (eNB) , next generation enhanced NodeB (ng-eNB) , next generation NodeB (gNB or gNodeB) , access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and / or others. Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell) . A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area) , a pico cell (covering relatively smaller geographic area, such as a sports stadium) , a femto cell (relatively smaller geographic area (e.g., a home) ) , and / or other types of cells.
[0047] While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a base station may be disaggregated, including a central unit (CU) , one or more distributed units (DUs) , one or more radio units (RUs) , a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a base station includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location. In some aspects, a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated base station architecture.
[0048] Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., an S1 interface) . BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN) ) may interface with 5GC 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface) , which may be wired or wireless.
[0049] Wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz –7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz” . Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz –71,000 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” ( “mmW” or “mmWave” ) . In some cases, FR2 may be further defined in terms of sub-ranges, such as a first sub-range FR2-1 including 24,250 MHz –52,600 MHz and a second sub-range FR2-2 including 52,600 MHz –71,000 MHz. A base station configured to communicate using mmWave / near mmWave radio frequency bands (e.g., a mmWave base station such as BS 180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.
[0050] The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) , and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) .
[0051] Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182’. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182”. UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182”. BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.
[0052] Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.
[0053] Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and / or a physical sidelink feedback channel (PSFCH) .
[0054] EPC 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) Gateway 172, such as in the depicted example. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, MME 162 provides bearer and connection management.
[0055] Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switched (PS) streaming service, and / or other IP services.
[0056] BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and / or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0057] 5GC 190 may include various functional components, including: an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may be in communication with Unified Data Management (UDM) 196.
[0058] AMF 192 is a control node that processes signaling between UEs 104 and 5GC 190. AMF 192 provides, for example, quality of service (QoS) flow and session management.
[0059] Internet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.
[0060] In various aspects, a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.
[0061] FIG. 2 depicts an example disaggregated base station 200 architecture. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a Non-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both) . A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.
[0062] Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0063] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit –User Plane (CU-UP) ) , control plane functionality (e.g., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.
[0064] The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.
[0065] Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, controlled by a DU 230, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 240 can be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU (s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU (s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0066] The SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.
[0067] The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.
[0068] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 225, the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from non-network data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
[0069] FIG. 3 depicts aspects of an example BS 102 and a UE 104.
[0070] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340) , antennas 334a-t (collectively 334) , transceivers 332a-t (collectively 332) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339) . For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which may be configured to implement various functions described herein related to wireless communications.
[0071] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380) , antennas 352a-r (collectively 352) , transceivers 354a-r (collectively 354) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360) . UE 104 includes controller / processor 380, which may be configured to implement various functions described herein related to wireless communications.
[0072] In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller / processor 340. The control information may be for the physical broadcast channel (PBCH) , physical control format indicator channel (PCFICH) , physical HARQ indicator channel (PHICH) , physical downlink control channel (PDCCH) , group common PDCCH (GC PDCCH) , and / or others. The data may be for the physical downlink shared channel (PDSCH) , in some examples.
[0073] Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .
[0074] Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.
[0075] In order to receive the downlink transmission, UE 104 includes antennas 352a-352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.
[0076] MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.
[0077] In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH) ) from the controller / processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) . The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM) , and transmitted to BS 102.
[0078] At BS 102, the uplink signals from UE 104 may be received by antennas 334a-t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller / processor 340.
[0079] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.
[0080] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.
[0081] In various aspects, BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.
[0082] In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.
[0083] In some aspects, one or more processors may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.
[0084] FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.
[0085] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.
[0086] Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD) . OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and / or in the time domain with SC-FDM.
[0087] A wireless communications frame structure may be frequency division duplex (FDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. Wireless communications frame structures may also be time division duplex (TDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.
[0088] In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL / UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) , or semi-statically / statically through radio resource control (RRC) signaling) . In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. Subframes may also include mini-slots, which generally have fewer symbols than an entire slot. Other wireless communications technologies may have a different frame structure and / or different channels.
[0089] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2μ×15 kHz, where μ is the numerology 0 to 6. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=6 has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGS. 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.
[0090] As depicted in FIGS. 4A, 4B, 4C, and 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
[0091] As illustrated in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 104 of FIGS. 1 and 3) . The RS may include demodulation RS (DMRS) and / or channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and / or phase tracking RS (PT-RS) .
[0092] FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including, for example, nine RE groups (REGs) , each REG including, for example, four consecutive REs in an OFDM symbol.
[0093] A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe / symbol timing and a physical layer identity.
[0094] A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
[0095] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and / or paging messages.
[0096] As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS) . The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0097] FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and / or UCI.
[0098] QCL Ports and TCI States
[0099] In many cases, it is important for a UE to know which assumptions it can make on a channel corresponding to different transmissions. For example, the UE may need to know which reference signals (RSs) it can use to estimate the channel in order to decode a transmitted signal (e.g., PDCCH or PDSCH) . It may also be important for the UE to be able to report relevant channel state information (CSI) to the BS (e.g., a gNB) for scheduling, link adaptation, and / or beam management purposes. In NR, the concept of quasi co-location (QCL) and transmission configuration indicator (TCI) states is used to convey information about these assumptions.
[0100] QCL assumptions are generally defined in terms of channel properties. Per 3GPP TS 38.214, “two antenna ports are said to be quasi-co-located if properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. ” Different reference signals may be considered quasi co-located ( “QCL’ d” ) if a receiver (e.g., a UE) can apply channel properties determined by detecting a first reference signal to help detect a second reference signal. TCI states generally include configurations such as QCL-relationships, for example, between the DL RSs in one CSI-RS set and the PDSCH DMRS ports.
[0101] In some cases, a UE may be configured with up to M TCI-States. Configuration of the M TCI-States can come about via higher layer signaling, while a UE may be signaled to decode PDSCH according to a detected PDCCH with DCI indicating one of the TCI states. Each configured TCI state may include one RS set TCI-RS-SetConfig that indicates different QCL assumptions between certain source and target signals.
[0102] For example, TCI-RS-SetConfig may indicate a source RS in the top block and may be associated with a target signal indicated in the bottom block. In this context, a target signal generally refers to a signal for which channel properties may be inferred by measuring those channel properties for an associated source signal. As noted above, a UE may use the source RS to determine various channel parameters, depending on the associated QCL type, and use those various channel properties (determined based on the source RS) to process the target signal. A target RS does not necessarily need to be a PDSCH’s DMRS. In some cases, for example, a target RS may be any other RS (e.g., PUSCH DMRS, CSIRS, TRS, and SRS) .
[0103] Each TCI-RS-SetConfig may contain various parameters. These parameters can, for example, configure quasi co-location relationship (s) between reference signals in the RS set and the DM-RS port group of the PDSCH. The RS set contains a reference to either one or two DL RSs and an associated quasi co-location type (QCL-Type) for each one configured by the higher layer parameter QCL-Type.
[0104] For the case of two DL RSs, the QCL types can take on a variety of arrangements. For example, QCL types may not be the same, regardless of whether the references are to the same DL RS or different DL RSs. In the illustrated example, SSB is associated with Type C QCL for P-TRS, while CSI-RS for beam management (CSIRS–BM) is associated with Type D QCL.
[0105] QCL information and / or types may in some scenarios depend on or be a function of other information. For example, the quasi co-location (QCL) types indicated to the UE can be based on higher layer parameter QCL-Type and may take one or a combination of the following types:
[0106] QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread} ,
[0107] QCL-TypeB: {Doppler shift, Doppler spread} ,
[0108] QCL-TypeC: {average delay, Doppler shift} , and
[0109] QCL-TypeD: {Spatial Rx parameter} ,
[0110] Spatial QCL assumptions (QCL-TypeD) may be used to help a UE to select an analog Rx beam (e.g., during beam management procedures) . For example, an SSB resource indicator may indicate a same beam for a previous reference signal should be used for a subsequent transmission.
[0111] An initial ControlResourceSet CORESET (e.g., CORESET ID 0 or simply CORESET#0) in NR may be identified during initial access by a UE (e.g., via a field in the MIB) . A ControlResourceSet information element (CORESET IE) sent via radio resource control (RRC) signaling may convey information regarding a CORESET configured for a UE. The CORESET IE generally includes a CORESET ID, an indication of frequency domain resources (e.g., a number of RBs) assigned to the CORESET, contiguous time duration of the CORESET in a number of symbols, and Transmission Configuration Indicator (TCI) states.
[0112] As noted above, a subset of the TCI states provide QCL relationships between DL RS (s) in one RS set (e.g., TCI-Set) and PDCCH demodulation RS (DMRS) ports. A particular TCI state for a given UE (e.g., for unicast PDCCH) may be conveyed to the UE by the Medium Access Control (MAC) Control Element (MAC-CE) . The particular TCI state is generally selected from the set of TCI states conveyed by the CORESET IE, with the initial CORESET (CORESET#0) generally configured via MIB.
[0113] Search space information may also be provided via RRC signaling. For example, the SearchSpace IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with one CORESET. The SearchSpace IE identifies a search space configured for a CORESET by a search space ID. In some aspects, the search space ID associated with CORESET #0 is SearchSpace ID #0. The search space is generally configured via PBCH (MIB) .
[0114] Example Beam Refinement Procedures
[0115] In mmWave systems, beamforming may be important to overcome high path-losses. As described herein, beamforming may refer to establishing a link between a BS and UE, wherein both of the devices form a beam corresponding to each other. Both the BS and the UE find at least one adequate beam to form a communication link. BS-beam and UE-beam form what is known as a beam pair link (BPL) . As an example, on the DL, a BS may use a transmit beam and a UE may use a receive beam corresponding to the transmit beam to receive the transmission. The combination of a transmit beam and corresponding receive beam may be a BPL.
[0116] As a part of beam management, beams which are used by BS and UE have to be refined from time to time because of changing channel conditions, for example, due to movement of the UE or other objects. Additionally, the performance of a BPL may be subject to fading due to Doppler spread. Because of changing channel conditions over time, the BPL should be periodically updated or refined. Accordingly, it may be beneficial if the BS and the UE monitor beams and new BPLs.
[0117] At least one BPL has to be established for network access. As described above, new BPLs may need to be discovered later for different purposes. The network may decide to use different BPLs for different channels, or for communicating with different BSs (TRPs) or as fallback BPLs in case an existing BPL fails.
[0118] The UE typically monitors the quality of a BPL, and the network may refine a BPL from time to time.
[0119] FIG. 5 illustrates example 500 for BPL discovery and refinement. In 5G-NR, the P1, P2, and P3 procedures are used for BPL discovery and refinement. The network uses a P1 procedure to enable the discovery of new BPLs. In the P1 procedure, as illustrated in FIG. 5, the BS transmits different symbols of a reference signal, each beam formed in a different spatial direction such that several (e.g., most or all) relevant places of the cell are reached. Stated otherwise, the BS transmits beams using different transmit beams over time in different directions.
[0120] For successful reception of at least a symbol of this “P1-signal” , the UE has to find an appropriate receive beam. It searches using available receive beams and applying a different UE-beam during each occurrence of the periodic P1-signal.
[0121] Once the UE has succeeded in receiving a symbol of the P1-signal, it has discovered a BPL. The UE may not want to wait until it has found the best UE receive beam, since this may delay further actions. The UE may measure the reference signal receive power (RSRP) and report the symbol index together with the RSRP to the BS. Such a report will typically contain the findings of one or more BPLs.
[0122] In an example, the UE may determine a received signal having a high RSRP. The UE may not know which beam the BS used to transmit; however, the UE may report to the BS the time at which it observed the signal having a high RSRP. The BS may receive this report and may determine which BS beam the BS used at the given time.
[0123] The BS may then offer P2 and P3 procedures to refine an individual BPL. The P2 procedure refines the BS-beam of a BPL. For example, the BS may transmit a few symbols of a reference signal with different BS-beams that are spatially close to the BS-beam of the BPL (the BS performs a sweep using neighboring beams around the selected beam) . In P2, the UE keeps its beam constant. Thus, while the UE uses the same beam as in the BPL (as illustrated in P2 procedure in FIG. 5) . The BS-beams used for P2 may be different from those for P1 in that they may be spaced closer together or they may be more focused. The UE may measure the RSRP for the various BS-beams and indicate the best one to the BS.
[0124] The P3 procedure refines the UE-beam of a BPL (see P3 procedure in FIG. 5) . While the BS-beam stays constant, the UE scans using different receive beams (the UE performs a sweep using neighboring beams) . The UE may measure the RSRP of each beam and identify the best UE-beam. Afterwards, the UE may use the best UE-beam for the BPL and report the RSRP to the BS.
[0125] Over time, the BS and UE establish several BPLs. When the BS transmits a certain channel or signal, it lets the UE know which BPL will be involved, such that the UE may tune in the direction of the correct UE receive beam before the signal starts. In this manner, every sample of that signal or channel may be received by the UE using the correct receive beam. In an example, the BS may indicate for a scheduled signal (e.g., SRS, CSI-RS) or channel (e.g., PDSCH, PDCCH, PUSCH, and / or PUCCH) which BPL is involved. In NR, this information may be referred to as a quasi co-location (QCL) indication.
[0126] Two antenna ports are quasi co-located (QCL) if properties of the channel over which a symbol on one antenna port is conveyed may be inferred from the channel over which a symbol on the other antenna port is conveyed. QCL supports, at least, beam management functionality, frequency / timing offset estimation functionality, and radio resource management (RRM) functionality.
[0127] The BS may use a BPL which the UE has received in the past. The transmit beam for the signal to be transmitted and the previously-received signal both point in a same direction or are QCL. The QCL indication may be needed by the UE (in advance of signal to be received) such that the UE may use a correct receive beam for each signal or channel. Some QCL indications may be needed from time to time when the BPL for a signal or channel changes and some QCL indications are needed for each scheduled instance. The QCL indication may be transmitted in the downlink control information (DCI) , which may be part of the PDCCH channel. Because DCI is needed to control the information, it may be desirable that the number of bits needed to indicate the QCL is not too big. The QCL may be transmitted in a medium access control-control element (MAC-CE) or radio resource control (RRC) message.
[0128] According to one example, whenever the UE reports a BS beam that it has received with sufficient RSRP, and the BS decides to use this BPL in the future, the BS assigns it a BPL tag. Accordingly, two BPLs having different BS beams may be associated with different BPL tags. BPLs that are based on the same BS beams may be associated with the same BPL tag. Thus, according to this example, the tag is a function of the BS beam of the BPL.
[0129] As noted above, wireless systems, such as millimeter wave (mmW) systems, bring gigabit speeds to cellular networks, due to availability of large amounts of bandwidth. However, the unique challenges of heavy path-loss faced by such wireless systems necessitate new techniques such as hybrid beamforming (analog and digital) , which are not present in 3G and 4G systems. Hybrid beamforming may enhance link budget / signal to noise ratio (SNR) that may be exploited during the RACH.
[0130] In such systems, the node B (NB) and the user equipment (UE) may communicate over active beam-formed transmission beams. Active beams may be considered paired transmission (Tx) and reception (Rx) beams between the NB and UE that carry data and control channels such as PDSCH, PDCCH, PUSCH, and PUCCH. As noted above, a transmit beam used by a NB and corresponding receive beam used by a UE for downlink transmissions may be referred to as a beam pair link (BPL) . Similarly, a transmit beam used by a UE and corresponding receive beam used by a NB for uplink transmissions may also be referred to as a BPL.
[0131] Since the direction of a reference signal is unknown to the UE, the UE may evaluate several beams to obtain the best Rx beam for a given NB Tx beam. However, if the UE has to “sweep” through all of its Rx beams to perform the measurements (e.g., to determine the best Rx beam for a given NB Tx beam) , the UE may incur significant delay in measurement and battery life impact. Moreover, having to sweep through all Rx beams is highly resource inefficient. Thus, aspects of the present disclosure provide techniques to assist a UE when performing measurements of serving cells and neighbor cells when using Rx beamforming.
[0132] Example Beam Management
[0133] In wireless communications, various procedures may be performed for beam management. FIG. 6 is a diagram illustrating example operations where beam management may be performed. In initial access 602, the network may sweep through several beams, for example, via synchronization signal blocks (SSBs) , as further described herein with respect to FIG. 4B. The network may configure the UE with random access channel (RACH) resources associated with the beamformed SSBs to facilitate the initial access via the RACH resources. In certain aspects, an SSB may have a wider beam shape compared to other reference signals, such as a channel state information reference signal (CSI-RS) . A UE may use SSB detection to identify a RACH occasion (RO) for sending a RACH preamble (e.g., as part of a contention-based Random Access (CBRA) procedure) .
[0134] In connected mode 604, the network and UE may perform hierarchical beam refinement including beam selection (e.g., a process referred to as P1) , beam refinement for the transmitter (e.g., a process referred to as P2) , and beam refinement for the receiver (e.g., a process referred to as P3) . In beam selection (P1) , the network may sweep through beams, and the UE may report the beam with the best channel properties, for example. In beam refinement for the transmitter (P2) , the network may sweep through narrower beams, and the UE may report the beam with the best channel properties among the narrow beams. In beam refinement for the receiver (P3) , the network may transmit using the same beam repeatedly, and the UE may refine spatial reception parameters (e.g., a spatial filter) for receiving signals from the network via the beam. In certain aspects, the network and UE may perform complementary procedures (e.g., U1, U2, and U3) for uplink beam management.
[0135] In certain cases where a beam failure occurs (e.g., due to beam misalignment and / or blockage) , the UE may perform a beam failure recovery (BFR) procedure 606, which may allow a UE to return to connected mode 604 without performing a radio link failure procedure 608. For example, the UE may be configured with candidate beams for beam failure recovery. In response to detecting a beam failure, the UE may request the network to perform beam failure recovery via one of the candidate beams (e.g., one of the candidate beams with a reference signal received power (RSRP) above a certain threshold) . In certain cases where radio link failure (RLF) occurs, the UE may perform an RLF procedure 608 (e.g., a RACH procedure) to recover from the RLF.
[0136] Example Framework for AI / ML in a Radio Access Network
[0137] FIG. 7 depicts an example of AI / ML functional framework 700 for RAN intelligence, in which aspects described herein may be implemented.
[0138] The AI / ML functional framework includes a data collection function 702, a model training function 704, a model inference function 706, and an actor function 708, which interoperate to provide a platform for collaboratively applying AI / ML to various procedures in RAN.
[0139] The data collection function 702 generally provides input data to the model training function 704 and the model inference function 706. AI / ML algorithm specific data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) may not be carried out in the data collection function 702.
[0140] Examples of input data to the data collection function 702 (or other functions) may include measurements from UEs or different network entities, feedback from the actor function, and output from an AI / ML model. In some cases, analysis of data needed at the model training function 704 and the model inference function 706 may be performed at the data collection function 702. As illustrated, the data collection function 702 may deliver training data to the model training function 704 and inference data to the model inference function 706.
[0141] The model training function 704 may perform AI / ML model training, validation, and testing, which may generate model performance metrics as part of the model testing procedure. The model training function 704 may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on the training data delivered by the data collection function 702, if required.
[0142] The model training function 704 may provide model deployment / update data to the Model interface function 706. The model deployment / update data may be used to initially deploy a trained, validated, and tested AI / ML model to the model inference function 706 or to deliver an updated model to the model inference function 706.
[0143] As illustrated, the model inference function 706 may provide AI / ML model inference output (e.g., predictions or decisions) to the actor function 708 and may also provide model performance feedback to the model training function 704, at times. The model inference function 706 may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on inference data delivered by the data collection function 702, at times.
[0144] The inference output of the AI / ML model may be produced by the model inference function 706. Specific details of this output may be specific in terms of use cases. The model performance feedback may be used for monitoring the performance of the AI / ML model, at times. In some cases, the model performance feedback may be delivered to the model training function 704, for example, if certain information derived from the model inference function is suitable for improvement of the AI / ML model trained in the model training function 704.
[0145] The model inference function 706 may signal the outputs of the model to nodes that have requested them (e.g., via subscription) , or nodes that take actions based on the output from the model inference function. An AI / ML model used in a model inference function 706 may need to be initially trained, validated and tested by a model training function before deployment. The model training function 704 and model inference function 706 may be able to request specific information to be used to train or execute the AI / ML algorithm and to avoid reception of unnecessary information. The nature of such information may depend on the use case and on the AI / ML algorithm.
[0146] The actor function 708 may receive the output from the model inference function 706, which may trigger or perform corresponding actions. The actor function 708 may trigger actions directed to other entities or to itself. The feedback generated by the actor function 708 may provide information used to derive training data, inference data or to monitor the performance of the AI / ML Model. As noted above, input data for a data collection function 702 may include this feedback from the actor function 708. The feedback from the actor function 708 or other network entities (e.g., via Data Collection function) may also be used at the model inference function 706.
[0147] The AI / ML functional framework 700 may be deployed in various RAN intelligence-based use cases. Such use cases may include CSI feedback enhancement, enhanced beam management (BM) , positioning and location (Pos-Loc) accuracy enhancement, and various other use cases.
[0148] Overview of Inter-Cell Measurement and Reporting Configuration
[0149] A UE may be configured (e.g., via RRC signaling) for measurement and reporting for inter-cell beam management (BM) . For the measurement, the UE may be configured with at least one CSI-SSB-ResourceSet that includes at least a set of non-Cell SSBs with non-serving PCIs. Additional non-serving SSB information may also be provided by RRC. This information may include position, Tx power, and / or periodicity of non-serving SSB transmissions. In some cases, a maximum number of non-serving PCIs configured for measurement may be based on a UE capability (e.g., with a candidate value at least including 1) . UE measurement behavior for overlapped SSBs may be up to implementation or defined by wireless communications standards.
[0150] For measurement reporting, different parameters may be included. For example, in some cases, a differential L1-RSRP report format may be assumed (e.g., where the UE reports a strongest measured L1-RSRP for one beam / resource and reports differential values for the other measurements) . In some cases, the UE may report up to 4 DL RSs, which can include both Cell RS and non-serving SSB.
[0151] A layer 1 (L1) measurement report (e.g., for L1 / L2 mobility (LTM) ) , may be reported as UCI on PUCCH or PUSCH. For example, periodic reports may be transmitted on PUCCH, semi-persistent reports may be transmitted on PUCCH / PUSCH, and aperiodic reports may be transmitted on PUSCH. In some cases, such reporting may be via medium access control (MAC) control element (CE) . Both gNB scheduled and / or UE initiated reporting may be possible.
[0152] Aspects Related to Specified CMRs in a Report for NW-Side Beam Prediction
[0153] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for feedback of measurements based on channel measurement resources (CMRs) . In some cases, the feedback may include measurements for certain CMRs specified (e.g., mandated) by a network entity or based on an agreement or rule (s) .
[0154] As will be described in greater detail below, in some cases, a network entity may configure a UE to report measurements for select TCI states / CMRs. In some cases, the configuration may also specify one or more of the various options described herein. In this context, specified CMRs may correspond to QCL-source RSs associated with the TCI-states.
[0155] While additional CSI information may be beneficial to make informed decisions (e.g., for data collection in model training or for gNB-side inference) , additional CSI information has a cost in terms of reporting payload. For example, for reporting more than 4 physical (PHY) / layer 1 reference signal received power (L1-RSRPs) and corresponding CMR-IDs, it may be desirable to control (e.g., reduce / limit) overhead of the L1 report.
[0156] Overhead may be controlled, for example, in certain scenarios that provide some form of flexibility on payload size, number of CMRs addressed, and quantization granularity. In such cases, constraints on one or more of the aforementioned parameters, within an associated CSI report, can be network signaled and fixed or, alternatively, UE-determined and reported. As an example, payload size of the CSI report may be network signaled, while the specific number of CMRs in the CSI report may be UE-determined and reported via the same CSI report. In such cases, quantization granularity per L1-RSRP may be based on wireless communication standard predefinitions according to different combinations of parameters (e.g., total payload bits and #of addressed CMRs) .
[0157] In some cases, as illustrated at 802 in diagram 800 of FIG. 8, multiple quantization schemes may be defined depending on the number of CMRs. Depending on the number of CMRs that should be addressed in the CSI report, various L1-RSRP quantization granularity / step-size options are provided. As indicated at 804, the illustrated example assumes a total number of candidates CMRs is 32 and that at least 16 of the 32 should be reported. As shown, if the number of CMRs is 16, 4 bits may be used for a reference (e.g., strongest) CMR while 3 bits may be used for each of the other CMRs (e.g., the next 15 strongest) . On the other hand, if the number of CMRs is 24, 7 bits may be used for a reference CMR while 4 bits may be used for the other CMRs (e.g., the next 23 strongest) .
[0158] As indicated at 806, the corresponding CMR-IDs may be indicated via a bitmap for overhead reduction. For example, a 32 bit bitmap may be used instead of 16 5 bit CMR IDs (in the case the CSI report addresses 16 CMRs) or 24 5 bit CMR IDs (in the case the CSI report addresses 24 CMRs) .
[0159] One potential issue regarding L1 reporting for network-side beam prediction involves a current limitation on which CMRs are reported. For example, in current systems, CMR associated with a current transmission configuration indicator (TCI) state may not be addressed. This limitation may adversely impact the networks ability to make appropriate beam switch decisions.
[0160] Frequent beam switches may introduce problems for a UE’s tracking loop performance. Thus, it may be desirable that the network make sure that an L1-RSRP of a new beam could be significantly / obviously better (e.g., 3dB better) than a beam associated with the UE’s current TCI-state’s RS, before triggering an actual beam switch. Unfortunately, in certain systems (as illustrated in FIG. 8) , when a UE reports CMR-IDs in L1 reports, the UE may flexibly choose from candidate CMRs.
[0161] In some cases, the UE may choose to report CMRs that have the strongest L1-RSRPs / L1-SINRs. Unfortunately, this may result in the CMR associated with a current TCI-state may not be addressed in the L1 report. Considering network-side temporal beam prediction, if the CMRs with respect to the current TCI-state is not addressed in the L1 report, this may cause reliability / accuracy problems for the network when predicting future L1-RSRP / L1-SINR of the same CMR.
[0162] Another potential issue relates to tradeoff between prediction accuracy and the ability to address weak beams (e.g., for CMRs with weak L1-RSRP / L1-SINR) . Although a UE may report L1-RSRPs with respect to weaker CMRs, in order to help with temporal beam prediction, it may be desirable to provide enhanced mechanisms to identify which weak ones should be addressed in a given CSI report. Especially considering temporal beam prediction for a relatively long future period, it may be desirable that all involved CMRs could be addressed in L1 reports (e.g., statistically instead of absolutely every reporting occasion) .
[0163] Aspects of the present disclosure provide various mechanisms for addressing the potential issues described above.
[0164] For example, according to certain aspects, it may be specified that CMR (s) with respect to the most recently active TCI-state (s) may be addressed in an L1 CSI report. In some cases, rules may essentially mandate / specify certain CMRs that are to be addressed in a CSI report. Whether and / or when such rules are to be applied may be determined via wireless communication standard predefinitions and / or (e.g., separate / additional) network signaling. If a UE and the network are on the same page regarding which TCI-states are the most recent active ones, overhead for addressing the corresponding CMRs in the L1 report may be reduced.
[0165] In some cases, to address the potential issue related to the tradeoff between prediction accuracy and the ability to address weak beams CSI, a UE may be configured to address subsets of CMRs in a fixed interval per report occasions. In this manner, the UE may potentially cycle-through all candidate CMRs statistically across report occasions (e.g., in a round-robin manner) . With this subset-based reporting, strongest CMRs may still be addressed. Again, if a UE and network are on the same page properly regarding which CMRs are (e.g., by default) to be addressed at a given report occasion, overhead for addressing such CMRs in the L1 report may be reduced.
[0166] An example mechanism for specifying (e.g., mandating) that a UE is to address CMRs with respect to recent active TCI states in an L1 CSI report may be understood with reference to the call flow diagram 900 of FIG. 9. In some aspects, the UE shown in FIG. 9 (and / or FIG. 11) may be an example of the UE 104 depicted and described with respect to FIG. 1 and 3. In some aspects, the network entity shown in FIG. 9 (and / or FIG. 11) may be an example of the BS 102 (e.g., a gNB) depicted and described with respect to FIG. 1 and 3 or a disaggregated base station depicted and described with respect to FIG. 2.
[0167] As illustrated at 902, the network entity may transmit configuration information (e.g., a CSI reporting configuration) configuring the UE with a plurality of candidate channel measurement resources (CMRs) .
[0168] As illustrated at 904 the network entity may prompt the UE to send CSI feedback based on one or more of the CMRs from the candidate CMRs. As illustrated at 906 the network entity may transmit RS on the candidate CMRs.
[0169] As illustrated at 908, the UE may transmit a CSI report including measurements for one or more CMRs associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.
[0170] As illustrated in diagram 1000 of FIG. 10, the UE may be requested (at 1002) by the network to feedback, via a CSI report, information regarding measured L1-RSRPs / L1-SINRs of selective CMRs among a number of candidate channel measurement resources (CMRs) (e.g., based on SSB / CSI-RS resources) . The UE may further be indicated (e.g., by MAC-CE / DCI at 1004) to apply certain TCI-state (s) on its PDxCH / PUxCH (e.g., PDCCH, PDSCH, PUCCH, or PUSCH) . The QCL-source RSs associated with these TCI-states may be (e.g., partly) overlapping with the candidate CMRs associated with the CSI report.
[0171] At a given CSI reporting occasion, it may be specified (e.g., mandated) that the CSI payload address L1-RSRP (s) / L1-SINR (s) of CMR (s) that have been indicated by the network as QCL-source RS (s) of the TCI-State (s) to be applied for PDxCH / PUxCH during a certain period ahead of the reporting occasion. The UE may also optionally address (e.g., indicate in the CSI report) the corresponding CMR-ID (s) . Mechanisms for identifying the involved TCI-states can be based on wireless communication standard predefinition and / or (e.g., additional / separate) network signaling (e.g., signaling specifying how the UE should indicate the CMR-IDs) .
[0172] There are various options to determine (e.g., by the UE and network) the CMR (s) and / or TCI-state (s) for a given CSI-report.
[0173] According to a first option, a UE may be expected to report CMR associated with a single most recently indicated single TCI-state. For example, the single TCI-state may be the most recent TCI state for PDxCH / PUxCH that the network indicated before the CSI reference resource associated with the CSI report. In some cases, for PDxCH / PUxCH, the TCI state may be further restricted to the TCI-state indicated via the DL-grant DCI or MAC-CE (e.g., at 1004 in FIG. 10) .
[0174] As indicated at 1006, the TCI state may optionally be further conditioned on the CSI reference resources associated with the CSI report (sent at 1008) being at least a threshold duration (e.g., X-ms) after the UE has sent an acknowledgment (ACK 1006) associated with the DL-grant DCI or for a PDSCH carrying the MAC-CE. In such cases, the threshold duration (e.g., the value of X) may be specified in a wireless communication standard or could be network-signaled.
[0175] According to a second option, it may be expected that the UE address CMRs associated with multiple most recently indicated TCI-states, within a period ahead of the reporting occasion. In such cases, the starting and ending points of the period may be identified based on a wireless communication standard predefinition or network signaling. In this manner, all of the TCI-states that have been network indicated for PDxCH / PUxCH may be addressed by the CSI report.
[0176] In some cases, the ending point of the period may be wireless communication standard (pre) defined. For example, the ending point may be X-ms after the UE has sent an ACK associated with the DL-grant DCI or the PDSCH carrying a MAC-CE, wherein the DL-grant DCI or the MAC-CE carries the most recent applicable TCI-state to be applied to PDxCH / PUxCH, before the CSI reference resource associated with the CSI report.
[0177] In some cases, the ending point of the period may be predefined in a wireless communication standard or network-signaled. As one example, the starting point may be indicated to be Y-ms / slots / subframes / frames ahead of the CSI reference resource associated with the CSI report (e.g., or ahead of the ending-point defined above) . As another example, the starting point may be indicated to be the starting symbol of the CSI reference resources associated with the previous reporting occasion (e.g., applicable only for periodic / semi-persistent (P / SP) CSI reports excluding the first reporting occasion) . As another example, the starting point may be indicated to be the first symbol after the RRC / MAC-CE / DCI configuring / activating / triggering P / SP / AP CSI report (for P / SP CSI reports, this may be only applicable for the first reporting occasion) .
[0178] In some cases, the DL-grant DCI or MAC-CE indicating the applicable TCI-state (s) may be mandated to be at least after the Starting-point. In some cases, the UE ACK associated with the DL-grant DCI or PDSCH carrying the MAC-CE may be mandated to be at least after the Starting-point. In some cases, the Starting-point may be mandated to be ahead of the time that is X-ms after the UE sent the ACK with respect to the DL-grant DCI or PDSCH carrying the MAC-CE.
[0179] In some cases, which option or sub-option should be considered may be based on a wireless communication standard predefinition or may be based on network signaling. For example, a wireless communication standard or network signaling may indicate that certain options or sub-options are to be applied to any ServCells or certain ServCells / BWPs. In some cases, which option or sub-option to apply may be RRC / MAC-CE signaled for a particular P / SP / AP CSI report setting or a particular CSI-AssociatedReporfConfigInfo for AP CSI report.
[0180] There are also various options regarding when (e.g., or what type (s) of) a MAC-CE may be considered for TCI-State Indication. According to a first option, only MAC-CEs conveying a beam switch may be considered. In other words, according to this first option, only a MAC-CE indicating TCI-state switch for CORESET (s) may be considered. According to a second option, MAC-CEs activating TCI states may also be considered. In other words, in this case, a MAC-CE activating a subset of TCI-states from a larger set of RRC configured TCI states may also be considered (e.g., in addition to beam switch MAC-CEs) .
[0181] There are also various options proposed herein for how to indicate (address) CMR-IDs in the CSI report (e.g., how to indicate the CMRs corresponding to the reported measurements) .
[0182] According to a first option, the CMR-IDs may not be directly addressed. For example, the CMR-ID (s) defined / specified according to the various options described above may not be explicitly identified in the CSI report. Rather, only the measurements (e.g., L1-RSRP (s) / L1-SINR (s) ) may addressed. In such cases, the measurements (e.g., L1-RSRP (s) / L1-SINR (s) ) may be ordered based on ascending / descending orders of the associated CMR-ID (s) or TCI-state ID (s) . In some cases, other L1-RSRPs / L1-SINRs values, together with their CMRs different from the ones defined by the previous proposals, may be reported (e.g., following conventional methods) in the same CSI report.
[0183] In some cases, measurements (e.g., L1-RSRPs / L1-SINRs) of the CMRs (specified to be included in the CSI report) may be indicated differentially, as difference values relative to a reference measurement. For example, the reference measurement may correspond to a CMR with the strongest L1-RSRP / L1-SINR measurement addressed in the CSI report. In such cases, if one of the CMRs specified to be included happens to be strongest one in the CSI report, the UE may address this CMR measurement two times. In other words, the UE may include this measurement first as the reference / strongest measurement and, again, as being no difference (e.g., 0-dB differentially) relative to its own strongest measurement.
[0184] In some cases, the number of CMRs to be addressed in the CSI report (and specified / mandated) , may be RRC configured or MAC-CE indicated for a particular P / SP / AP CSI report setting, or for a particular CSI-AssociatedReportConfigInfo for AP CSI report.
[0185] In some cases, if the number of TCI-states identified based on the techniques proposed above is more than the number of CMRs controlled by the network for the CSI report, the UE may determine what to address in the CSI report. For example, the UE may report only the CMR (s) associated with the most recent TCI states or the UE may report CMR (s) in ascending / descending ordered according to CMR-ID (s) or TCI-state ID (s) . In such cases, the CMRs that are not included (e.g., cannot be included) in the CSI report may be ignored.
[0186] In some cases, if the number of TCI-states identified based on the techniques proposed herein is less than the number of CMRs controlled by the network for CSI reporting, the UE may report arbitrary L1-RSRPs / L1-SINRs for the ones that have no meaning in the CSI report. One benefit if this approach is that overhead for CMR-IDs can be removed, assuming the gNB and UE has a good common understanding on candidate CMRs. One potential risk, however, is if the UE’s ACK is not received by the network (e.g., which could happen with a not-insignificant 1%chance) , there could be ambiguities between the network and UE regarding the CMRs addressed in the CSI report. For this reason, another option may be preferred in some cases.
[0187] For example, conventional methods to report L1-RSRPs / L1-SINRs together with the CMR-IDs may be used for the CSI payload, with the condition that the CMR (s) specified / mandated as described above are included. In such cases, it may be left up to the UE to determine which CMR (s) defined / mandated should be included, in order to meet CSI payload restrictions. One benefit to this approach is that by indicating the CMR- IDs, there may be no ambiguities regarding the CMR (s) addressed in the CSI report. One potential issue, however, is that this approach increases the reporting payload size (when compared to certain options noted above) .
[0188] According to certain aspects of the present disclosure, CMR-IDs maybe be addressed based on a CMR-ID interval. This may be considered a form of background L1 reporting, since measurements for certain CMR-IDs may be reported essentially in the background.
[0189] Reporting CMRs based on a CMR-ID interval may be understood with reference to the call flow diagram 1100 of FIG. 11.
[0190] As illustrated at 1102, the network entity may transmit configuration information (e.g., a CSI reporting configuration) configuring the UE with a plurality of candidate channel measurement resources (CMRs) .
[0191] As illustrated at 1104 the network entity may prompt the UE to send CSI feedback based on one or more of the CMRs from the candidate CMRs. In this manner, the UE may requested by the network to provide feedback, via a CSI report, regarding measured L1-RSRPs / L1-SINRs of selective CMRs among a number of CMRs (e.g., based on SSB / CSI-RS resources) .
[0192] As illustrated at 1106, the UE may transmit CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs.
[0193] In general, at a given reporting occasion, the UE may be expected to feedback L1-RSRPs / L1-SINRs of a certain number CMRs addressed by the CSI payload.
[0194] In some cases, the reporting may be based on a starting CMR-ID associated with the candidate CMRs (with the starting CMR-ID referred to herein as CS) and a CMR-ID interval (with the CMR interval referred to herein as CI) , such that the CMR IDs {CS, CS+ CI, CS+ 2CI, …} are to be addressed in the given reporting occasion. In such cases, the value CI may be network controlled by signaling associated with the CSI report (e.g., CSI report setting, MAC-CE activating the (SP) CSI report, or CSI-AssociatedReportConfigInfo for the (AP) CSI report) .
[0195] An example of this type of CSI reporting for subsets of CMRs is illustrated in FIG. 12. As illustrated, in each reporting occasion, measurements for a number of specified CMRs 1202 may be reported. As illustrated, according to conventional reporting, only a few CMRs 1204 may be addressed in each reporting occasion. As indicated at 1206, specified CMRs and CMRs per conventional reporting may occasionally overlap. In the example shown in FIG. 12, CI=4.
[0196] In some cases, the value of CS∈ {0, 1, …, CI-1} , assuming CMR-IDs starts from 0, may be determined based on slot / subframe / frame ID associated with the reporting occasion (for P / SP / AP CSI reports) . In the example shown in FIG. 12, in the first reporting occasion, CS = 0, such that (since CI=4) the UE reports for CMR-IDs 0, 4, 8, ...
[0197] In this manner, a UE may be configured to report CMR measurements in a round robin manner, through various reporting occasions (e.g., starting with the 1st candidate value) , or indicated by MAC-CE activating (SP) CSI report or CSI-AssociatedReportConfigInfo for (AP) CSI report.
[0198] In some cases, a CMR-ID may be defined (e.g., or specified) based on the resource entry-ID associated with the candidate CMR set identified for the CSI report (e.g., SSB resource set or CSI-RS resources set) . As illustrated in FIG. 12, a UE may further include additional CMR-IDs 1204 and their L1-RSRPs / L1-SINRs in the CSI payload, following conventional L1 reporting methods.
[0199] Specifying CMRs (e.g., configuring a UE to address subsets of CMRs in a fixed interval) may address the potential issue related to the tradeoff between prediction accuracy and the ability to address weak beams CSI. In some cases, for example, specified CMRs 1202 (e.g., for one or more reporting occasions) may allow the reporting of measurements for CMRs with weaker measurements (e.g., weak L1-RSRP / L1-SINR) . By reporting measurements for only a subset each reporting occasion, payload restrictions may be met. Measurements for all CMRs may still be reported, however, by cycling through all subsets in a round-robin manner. In the example shown in FIG. 12, all subsets are reported in 4 reporting occasions.
[0200] In some cases, there may not be a need to address (e.g., explicitly identify) the CMR-IDs reported in the background. For example, the UE may not need to address CMR-IDs associated with the mandatory CMRs (e.g., that the UE is mandated to include) . Rather, only the corresponding measurements (e.g., L1-RSRPs / L1-SINRs) may need to be addressed.
[0201] As described above, L1-RSRPs / L1-SINRs (e.g., of mandated CMRs) in each reporting occasion may be reported as a difference, relative to a reference CMR (e.g., with the strongest L1-RSRP / L1-SINR) in the CSI report. As also described above, if one of the mandatory CMRs in a reporting occasion happens to be the strongest one in the CSI report, the UE may address this CMR two times (one of them being 0-dB differentially referred to itself with respect to L1-RSRP) .
[0202] In some cases, if the UE is not able to address all CMRs determined as mandatory due to payload restrictions, the UE may ignore the CMRs with certain (e.g., greater / lower CMR-ID (s) ) . In other cases, if the payload size is greater than the addressable CMRs for a given reporting occasion, arbitrary L1-RSRPs / L1-SINRs values may be reported in the CSI report.
[0203] Example Operations
[0204] FIG. 13 shows an example of a method 1300 of wireless communication at a user equipment (UE) , such as a UE 104 of FIGS. 1 and 3.
[0205] Method 1300 begins at step 1305 with receiving, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) . In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 17.
[0206] Method 1300 then proceeds to step 1310 with receiving, from a network entity, second signaling prompting a channel state information (CSI) report. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 17.
[0207] Method 1300 then proceeds to step 1315 with transmitting the CSI report, wherein the CSI report includes measurements for one or more CMRs, from the candidate CMRs, associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 17.
[0208] In some aspects, the one or more TCI states comprise one or more TCI states most recently indicated by the network entity for at least one of a physical downlink control channel (PDCCH) , a physical uplink shared channel (PUSCH) , or a physical uplink control channel (PUCCH) transmissions.
[0209] In some aspects, the one or more TCI states comprise a single TCI state most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0210] In some aspects, the one or more TCI states comprise multiple TCI states most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0211] In some aspects, the multiple TCI states are indicated within a time period defined by a starting point and an ending point.
[0212] In some aspects, the ending point is defined as a time offset after the UE acknowledges signaling carrying a most recent TCI state prior to the CSI reference resource associated with the CSI report.
[0213] In some aspects, the starting point is defined as: a time offset before the CSI reference resource associated with the CSI report; a time offset before the ending point; or a symbol after the first signaling prompting CSI feedback.
[0214] In some aspects, the one or more TCI states are indicated via at least one of: a medium access control (MAC) control element (CE) indicating a TCI state switch for a control resource set (CORESET) ; or a MAC CE activating one or more configured TCI states.
[0215] In some aspects, the CSI report includes CSI metrics ordered based on an order of associated CMR identifiers (CMR IDs) or TCI state IDs.
[0216] In some aspects, the CSI report lacks CMR IDs.
[0217] In some aspects, the CSI metrics are indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0218] In some aspects, the CSI report includes CSI metrics and indicates associated CMR identifiers (CMR IDs) .
[0219] In one aspect, method 1300, or any aspect related to it, may be performed by an apparatus, such as communications device 1700 of FIG. 17, which includes various components operable, configured, or adapted to perform the method 1300. Communications device 1700 is described below in further detail.
[0220] Note that FIG. 13 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0221] FIG. 14 shows an example of a method 1400 of wireless communication at a user equipment (UE) , such as a UE 104 of FIGS. 1 and 3.
[0222] Method 1400 begins at step 1405 with receiving, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) . In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 17.
[0223] Method 1400 then proceeds to step 1410 with receiving, from a network entity, second signaling prompting channel state information (CSI) reports. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 17.
[0224] Method 1400 then proceeds to step 1415 with transmitting the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 17.
[0225] In some aspects, the CMR ID interval is indicated by the network entity.
[0226] In some aspects, the subset of CMRs for each reporting occasion is further determined based on at least one of a slot ID, a subframe ID, or a frame ID associated with the reporting occasion.
[0227] In some aspects, the UE includes measurements for different subsets of CMRs from the candidate CMRs, in a round robin manner, in different reporting occasions.
[0228] In some aspects, the CSI report includes CSI metrics associated with CMR identifiers (CMR IDs) but lacks CMR IDs.
[0229] In some aspects, the CSI report includes CSI metrics indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0230] In some aspects, the UE does not include measurements associated with certain CMR identifiers (CMR IDs) if payload restrictions prevent the inclusion of measurements for all CMRs in a subset for a given reporting occasion.
[0231] In some aspects, the UE includes measurements associated with certain CMR identifiers (CMR IDs) not included in a subset of CMRs for a given reporting occasion, if payload size exceeds a size needed for the subset of CMRs.
[0232] In one aspect, method 1400, or any aspect related to it, may be performed by an apparatus, such as communications device 1700 of FIG. 17, which includes various components operable, configured, or adapted to perform the method 1400. Communications device 1700 is described below in further detail.
[0233] Note that FIG. 14 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0234] FIG. 15 shows an example of a method 1500 of wireless communication at a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0235] Method 1500 begins at step 1505 with transmitting first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) . In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 17.
[0236] Method 1500 then proceeds to step 1510 with transmitting second signaling prompting a channel state information (CSI) report from the UE, based on one or more CMRs from the of the candidate CMRs. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 17.
[0237] Method 1500 then proceeds to step 1515 with receiving the CSI report, wherein the CSI report includes measurements for one or more CMRs associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 17.
[0238] In some aspects, the one or more TCI states comprise one or more TCI states most recently indicated by the network entity for at least one of a physical downlink control channel (PDCCH) , a physical uplink shared channel (PUSCH) , or a physical uplink control channel (PUCCH) transmissions.
[0239] In some aspects, the one or more TCI states comprise a single TCI state most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0240] In some aspects, the one or more TCI states comprise multiple TCI states most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0241] In some aspects, the multiple TCI states are indicated within a time period defined by a starting point and an ending point.
[0242] In some aspects, the ending point is defined as a time offset after the UE acknowledges signaling carrying a most recent TCI state prior to the CSI reference resource associated with the CSI report.
[0243] In some aspects, the starting point is defined as: a time offset before the CSI reference resource associated with the CSI report; a time offset before the ending point; or a symbol after the first signaling prompting CSI feedback.
[0244] In some aspects, the one or more TCI states are indicated via at least one of: a medium access control (MAC) control element (CE) indicating a TCI state switch for a control resource set (CORESET) ; or a MAC CE activating one or more configured TCI states.
[0245] In some aspects, the CSI report includes CSI metrics ordered based on an order of associated CMR identifiers (CMR IDs) or TCI state IDs.
[0246] In some aspects, the CSI report lacks CMR IDs.
[0247] In some aspects, the CSI metrics are indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0248] In some aspects, the CSI report includes CSI metrics and indicates associated CMR identifiers (CMR IDs) .
[0249] In one aspect, method 1500, or any aspect related to it, may be performed by an apparatus, such as communications device 1700 of FIG. 17, which includes various components operable, configured, or adapted to perform the method 1500. Communications device 1700 is described below in further detail.
[0250] Note that FIG. 15 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0251] FIG. 16 shows an example of a method 1600 of wireless communication at a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0252] Method 1600 begins at step 1605 with transmitting first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) . In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 17.
[0253] Method 1600 then proceeds to step 1610 with transmitting second signaling prompting channel state information (CSI) reports based on one or more CMRs from the of the candidate CMRs. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 17.
[0254] Method 1600 then proceeds to step 1615 with receiving the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 17.
[0255] In some aspects, the CMR ID interval is indicated by the network entity.
[0256] In some aspects, the subset of CMRs for each reporting occasion is further determined based on at least one of a slot ID, a subframe ID, or a frame ID associated with the reporting occasion.
[0257] In some aspects, the CSI reports include measurements for different subsets of CMRs from the candidate CMRs, in a round robin manner, in different reporting occasions.
[0258] In some aspects, the CSI report includes CSI metrics associated with CMR identifiers (CMR IDs) but lacks CMR IDs.
[0259] In some aspects, the CSI report includes CSI metrics indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0260] In some aspects, the UE does not include measurements associated with certain CMR identifiers (CMR IDs) if payload restrictions prevent the inclusion of measurements for all CMRs in a subset for a given reporting occasion.
[0261] In some aspects, the CSI reports include measurements associated with certain CMR identifiers (CMR IDs) not included in a subset of CMRs for a given reporting occasion, if payload size exceeds a size needed for the subset of CMRs.
[0262] In one aspect, method 1600, or any aspect related to it, may be performed by an apparatus, such as communications device 1700 of FIG. 17, which includes various components operable, configured, or adapted to perform the method 1600. Communications device 1700 is described below in further detail.
[0263] Note that FIG. 16 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0264] Example Communications Device (s)
[0265] FIG. 17 depicts aspects of an example communications device 1700. In some aspects, communications device 1700 is a user equipment, such as UE 104 described above with respect to FIGS. 1 and 3. In some aspects, communications device 1700 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0266] The communications device 1700 includes a processing system 1705 coupled to the transceiver 1745 (e.g., a transmitter and / or a receiver) . In some aspects (e.g., when communications device 1700 is a network entity) , processing system 1705 may be coupled to a network interface 1755 that is configured to obtain and send signals for the communications device 1700 via communication link (s) , such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The transceiver 1745 is configured to transmit and receive signals for the communications device 1700 via the antenna 1750, such as the various signals as described herein. The processing system 1705 may be configured to perform processing functions for the communications device 1700, including processing signals received and / or to be transmitted by the communications device 1700.
[0267] The processing system 1705 includes one or more processors 1710. In various aspects, the one or more processors 1710 may be representative of one or more of receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to FIG. 3. In various aspects, one or more processors 1710 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors 1710 are coupled to a computer-readable medium / memory 1725 via a bus 1740. In certain aspects, the computer-readable medium / memory 1725 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1710, cause the one or more processors 1710 to perform the method 1300 described with respect to FIG. 13, or any aspect related to it; the method 1400 described with respect to FIG. 14, or any aspect related to it; the method 1500 described with respect to FIG. 15, or any aspect related to it; and the method 1600 described with respect to FIG. 16, or any aspect related to it. Note that reference to a processor performing a function of communications device 1700 may include one or more processors 1710 performing that function of communications device 1700.
[0268] In the depicted example, computer-readable medium / memory 1725 stores code (e.g., executable instructions) , such as code for receiving 1730 and code for transmitting 1735. Processing of the code for receiving 1730 and code for transmitting 1735 may cause the communications device 1700 to perform the method 1300 described with respect to FIG. 13, or any aspect related to it; the method 1400 described with respect to FIG. 14, or any aspect related to it; the method 1500 described with respect to FIG. 15, or any aspect related to it; and the method 1600 described with respect to FIG. 16, or any aspect related to it.
[0269] The one or more processors 1710 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1725, including circuitry for receiving 1715 and circuitry for transmitting 1720. Processing with circuitry for receiving 1715 and circuitry for transmitting 1720 may cause the communications device 1700 to perform the method 1300 described with respect to FIG. 13, or any aspect related to it; the method 1400 described with respect to FIG. 14, or any aspect related to it; the method 1500 described with respect to FIG. 15, or any aspect related to it; and the method 1600 described with respect to FIG. 16, or any aspect related to it.
[0270] Various components of the communications device 1700 may provide means for performing the method 1300 described with respect to FIG. 13, or any aspect related to it; the method 1400 described with respect to FIG. 14, or any aspect related to it; the method 1500 described with respect to FIG. 15, or any aspect related to it; and the method 1600 described with respect to FIG. 16, or any aspect related to it. For example, means for transmitting, sending or outputting for transmission may include transceivers 354 and / or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and / or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and / or the transceiver 1745 and the antenna 1750 of the communications device 1700 in FIG. 17. Means for receiving or obtaining may include transceivers 354 and / or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and / or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and / or the transceiver 1745 and the antenna 1750 of the communications device 1700 in FIG. 17.
[0271] Example Clauses
[0272] Implementation examples are described in the following numbered clauses:
[0273] Clause 1: A method for wireless communication at a user equipment (UE) , comprising: receiving, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) ; receiving, from a network entity, second signaling prompting a channel state information (CSI) report; and transmitting the CSI report, wherein the CSI report includes measurements for one or more CMRs, from the candidate CMRs, associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.
[0274] Clause 2: The method of Clause 1, wherein the one or more TCI states comprise one or more TCI states most recently indicated by the network entity for at least one of a physical downlink control channel (PDCCH) , a physical uplink shared channel (PUSCH) , or a physical uplink control channel (PUCCH) transmissions.
[0275] Clause 3: The method of Clause 2, wherein the one or more TCI states comprise a single TCI state most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0276] Clause 4: The method of Clause 2, wherein the one or more TCI states comprise multiple TCI states most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0277] Clause 5: The method of Clause 4, wherein the multiple TCI states are indicated within a time period defined by a starting point and an ending point.
[0278] Clause 6: The method of Clause 5, wherein the ending point is defined as a time offset after the UE acknowledges signaling carrying a most recent TCI state prior to the CSI reference resource associated with the CSI report.
[0279] Clause 7: The method of Clause 5, wherein the starting point is defined as: a time offset before the CSI reference resource associated with the CSI report; a time offset before the ending point; or a symbol after the first signaling prompting CSI feedback.
[0280] Clause 8: The method of any one of Clauses 1-7, wherein the one or more TCI states are indicated via at least one of: a medium access control (MAC) control element (CE) indicating a TCI state switch for a control resource set (CORESET) ; or a MAC CE activating one or more configured TCI states.
[0281] Clause 9: The method of any one of Clauses 1-8, wherein the CSI report includes CSI metrics ordered based on an order of associated CMR identifiers (CMR IDs) or TCI state IDs.
[0282] Clause 10: The method of Clause 9, wherein the CSI report lacks CMR IDs.
[0283] Clause 11: The method of Clause 9, wherein the CSI metrics are indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0284] Clause 12: The method of any one of Clauses 1-11, wherein the CSI report includes CSI metrics and indicates associated CMR identifiers (CMR IDs) .
[0285] Clause 13: A method for wireless communication at a user equipment (UE) , comprising: receiving, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) ; receiving, from a network entity, second signaling prompting channel state information (CSI) reports; and transmitting the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval.
[0286] Clause 14: The method of Clause 13, wherein the CMR ID interval is indicated by the network entity.
[0287] Clause 15: The method of any one of Clauses 13-14, wherein the subset of CMRs for each reporting occasion is further determined based on at least one of a slot ID, a subframe ID, or a frame ID associated with the reporting occasion.
[0288] Clause 16: The method of any one of Clauses 13-15, wherein the UE includes measurements for different subsets of CMRs from the candidate CMRs, in a round robin manner, in different reporting occasions.
[0289] Clause 17: The method of any one of Clauses 13-16, wherein the CSI report includes CSI metrics associated with CMR identifiers (CMR IDs) but lacks CMR IDs.
[0290] Clause 18: The method of any one of Clauses 13-17, wherein the CSI report includes CSI metrics indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0291] Clause 19: The method of any one of Clauses 13-18, wherein the UE does not include measurements associated with certain CMR identifiers (CMR IDs) if payload restrictions prevent the inclusion of measurements for all CMRs in a subset for a given reporting occasion.
[0292] Clause 20: The method of any one of Clauses 13-19, wherein the UE includes measurements associated with certain CMR identifiers (CMR IDs) not included in a subset of CMRs for a given reporting occasion, if payload size exceeds a size needed for the subset of CMRs.
[0293] Clause 21: A method for wireless communication at a network entity, comprising: transmitting first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) ; transmitting second signaling prompting a channel state information (CSI) report from the UE, based on one or more CMRs from the of the candidate CMRs; and receiving the CSI report, wherein the CSI report includes measurements for one or more CMRs associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.
[0294] Clause 22: The method of Clause 21, wherein the one or more TCI states comprise one or more TCI states most recently indicated by the network entity for at least one of a physical downlink control channel (PDCCH) , a physical uplink shared channel (PUSCH) , or a physical uplink control channel (PUCCH) transmissions.
[0295] Clause 23: The method of Clause 22, wherein the one or more TCI states comprise a single TCI state most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0296] Clause 24: The method of Clause 22, wherein the one or more TCI states comprise multiple TCI states most recently indicated by the network entity, prior to a CSI reference resource associated with the CSI report.
[0297] Clause 25: The method of Clause 24, wherein the multiple TCI states are indicated within a time period defined by a starting point and an ending point.
[0298] Clause 26: The method of Clause 25, wherein the ending point is defined as a time offset after the UE acknowledges signaling carrying a most recent TCI state prior to the CSI reference resource associated with the CSI report.
[0299] Clause 27: The method of Clause 25, wherein the starting point is defined as: a time offset before the CSI reference resource associated with the CSI report; a time offset before the ending point; or a symbol after the first signaling prompting CSI feedback.
[0300] Clause 28: The method of any one of Clauses 21-27, wherein the one or more TCI states are indicated via at least one of: a medium access control (MAC) control element (CE) indicating a TCI state switch for a control resource set (CORESET) ; or a MAC CE activating one or more configured TCI states.
[0301] Clause 29: The method of any one of Clauses 21-28, wherein the CSI report includes CSI metrics ordered based on an order of associated CMR identifiers (CMR IDs) or TCI state IDs.
[0302] Clause 30: The method of Clause 29, wherein the CSI report lacks CMR IDs.
[0303] Clause 31: The method of Clause 29, wherein the CSI metrics are indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0304] Clause 32: The method of any one of Clauses 21-31, wherein the CSI report includes CSI metrics and indicates associated CMR identifiers (CMR IDs) .
[0305] Clause 33: A method for wireless communication at a network entity, comprising: transmitting first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) ; transmitting second signaling prompting channel state information (CSI) reports based on one or more CMRs from the of the candidate CMRs; and receiving the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval.
[0306] Clause 34: The method of Clause 33, wherein the CMR ID interval is indicated by the network entity.
[0307] Clause 35: The method of any one of Clauses 33-34, wherein the subset of CMRs for each reporting occasion is further determined based on at least one of a slot ID, a subframe ID, or a frame ID associated with the reporting occasion.
[0308] Clause 36: The method of any one of Clauses 33-35, wherein the CSI reports include measurements for different subsets of CMRs from the candidate CMRs, in a round robin manner, in different reporting occasions.
[0309] Clause 37: The method of any one of Clauses 33-36, wherein the CSI report includes CSI metrics associated with CMR identifiers (CMR IDs) but lacks CMR IDs.
[0310] Clause 38: The method of any one of Clauses 33-37, wherein the CSI report includes CSI metrics indicated as differential values relative to a strongest CSI metric included in the CSI report.
[0311] Clause 39: The method of any one of Clauses 33-38, wherein the UE does not include measurements associated with certain CMR identifiers (CMR IDs) if payload restrictions prevent the inclusion of measurements for all CMRs in a subset for a given reporting occasion.
[0312] Clause 40: The method of any one of Clauses 33-39, wherein the CSI reports include measurements associated with certain CMR identifiers (CMR IDs) not included in a subset of CMRs for a given reporting occasion, if payload size exceeds a size needed for the subset of CMRs.
[0313] Clause 41: An apparatus, comprising: at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any one of Clauses 1-40.
[0314] Clause 42: An apparatus, comprising means for performing a method in accordance with any one of Clauses 1-40.
[0315] Clause 43: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of an apparatus, cause the apparatus to perform a method in accordance with any one of Clauses 1-40.
[0316] Clause 44: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Clauses 1-40.
[0317] Additional Considerations
[0318] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
[0319] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a graphics processing unit (GPU) , a neural processing unit (NPU) , a digital signal processor (DSP) , an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD) , discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC) , or any other such configuration.
[0320] As used herein, the term wireless node may refer to, for example, a network entity or a user equipment (UE) . In this context, a network entity may be a base station (e.g., a gNB) or a module (e.g., a CU, DU, and / or RU) of a disaggregated base station.
[0321] While the present disclosure may describe certain operations as being performed by one type of wireless node, the same or similar operations may also be performed by another type of wireless node. For example, operations performed by a network entity may also (or instead) be performed by a UE. Similarly, operations performed by a UE may also (or instead) be performed by a network entity.
[0322] Further, while the present disclosure may describe certain types of communications between different types of wireless nodes (e.g., between a network entity and a UE) , the same or similar types of communications may occur between same types of wireless nodes (e.g., between network entities or between UEs, in a peer-to-peer scenario) . Further, communications may occur in reverse direction relative to what is described (e.g., a UE could transmit a request to a network entity and the network entity transmits a response; OR a network entity could transmit the request to a UE and the UE transmits the response) .
[0323] As used herein, “a processor, ” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance of the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory, ” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and / or instructions, multiple memories configured to collectively store data and / or instructions.
[0324] Means for receiving, and means for transmitting may comprise one or more processors, such as one or more of the processors described above with reference to FIG. 17.
[0325] As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
[0326] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
[0327] The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component (s) and / or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0328] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112 (f) unless the element is expressly recited using the phrase “means for” . All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
Claims
1.An apparatus for wireless communication at a user equipment (UE) , comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:receive, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) ;receive, from a network entity, second signaling prompting a channel state information (CSI) report; andtransmit the CSI report, wherein the CSI report includes measurements for one or more CMRs, from the candidate CMRs, associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.2.The apparatus of claim 1, wherein the one or more TCI states comprise one or more TCI states most recently indicated by the network entity for at least one of a physical downlink control channel (PDCCH) , a physical uplink shared channel (PUSCH) , or a physical uplink control channel (PUCCH) transmissions.3.The apparatus of claim 2, wherein the one or more TCI states comprise a single TCI state recently indicated by the network entity.4.The apparatus of claim 2, wherein the one or more TCI states comprise multiple TCI states recently indicated by the network entity.5.The apparatus of claim 4, wherein the multiple TCI states are indicated within a time period defined by a starting point and an ending point.6.The apparatus of claim 5, wherein the ending point is defined as a time offset after the UE acknowledges signaling carrying a recent TCI state.7.The apparatus of claim 5, wherein the starting point is defined as:a time offset before the CSI reference resource associated with the CSI report;a time offset before the ending point; ora symbol after the second signaling.8.The apparatus of claim 1, wherein the one or more TCI states are indicated via at least one of:a medium access control (MAC) control element (CE) indicating a TCI state switch for a control resource set (CORESET) ;or a MAC CE activating one or more configured TCI states.9.The apparatus of claim 1, wherein the CSI report includes CSI metrics ordered based on an order of associated CMR identifiers (CMR IDs) or TCI state IDs.10.The apparatus of claim 9, wherein the CSI report lacks CMR IDs.11.The apparatus of claim 9, wherein the CSI metrics are indicated as differential values relative to a strongest CSI metric included in the CSI report.12.The apparatus of claim 1, wherein the CSI report includes CSI metrics and indicates associated CMR identifiers (CMR IDs) .13.An apparatus for wireless communication at a user equipment (UE) , comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:receive, from a network entity, first signaling configuring the UE with candidate channel measurement resources (CMRs) ;receive, from a network entity, second signaling prompting channel state information (CSI) reports; andtransmit the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval.14.The apparatus of claim 13, wherein the CMR ID interval is indicated by the network entity.15.The apparatus of claim 13, wherein the subset of CMRs for each reporting occasion is further determined based on at least one of a slot ID, a subframe ID, or a frame ID associated with the reporting occasion.16.The apparatus of claim 13, wherein the UE includes measurements for different subsets of CMRs from the candidate CMRs, in a round robin manner, in different reporting occasions.17.The apparatus of claim 13, wherein the CSI report includes CSI metrics associated with CMR identifiers (CMR IDs) but lacks CMR IDs.18.The apparatus of claim 13, wherein the CSI report includes CSI metrics indicated as differential values relative to a strongest CSI metric included in the CSI report.19.The apparatus of claim 13, wherein the UE does not include measurements associated with certain CMR identifiers (CMR IDs) if payload restrictions prevent the inclusion of measurements for all CMRs in a subset for a given reporting occasion.20.The apparatus of claim 13, wherein the UE includes measurements associated with certain CMR identifiers (CMR IDs) not included in a subset of CMRs for a given reporting occasion, if payload size exceeds a size needed for the subset of CMRs.21.An apparatus for wireless communication at a network entity, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:transmit first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) ;transmit second signaling prompting a channel state information (CSI) report from the UE, based on one or more CMRs from the of the candidate CMRs; andreceive the CSI report, wherein the CSI report includes measurements for one or more CMRs associated with one or more transmission configuration indicator (TCI) states previously indicated by the network entity.22.The apparatus of claim 21, wherein the one or more TCI states comprise one or more TCI states most recently indicated by the network entity for at least one of a physical downlink control channel (PDCCH) , a physical uplink shared channel (PUSCH) , or a physical uplink control channel (PUCCH) transmissions.23.The apparatus of claim 22, wherein the one or more TCI states comprise a single TCI state recently indicated by the network entity.24.The apparatus of claim 22, wherein the one or more TCI states comprise multiple TCI states recently indicated by the network entity.25.The apparatus of claim 24, wherein the multiple TCI states are indicated within a time period defined by a starting point and an ending point.26.The apparatus of claim 25, wherein the ending point is defined as a time offset after the UE acknowledges signaling carrying a recent TCI state.27.The apparatus of claim 25, wherein the starting point is defined as:a time offset before the CSI reference resource associated with the CSI report;a time offset before the ending point; ora symbol after the second signaling.28.The apparatus of claim 21, wherein the one or more TCI states are indicated via at least one of:a medium access control (MAC) control element (CE) indicating a TCI state switch for a control resource set (CORESET) ; ora MAC CE activating one or more configured TCI states.29.The apparatus of claim 21, wherein the CSI report includes CSI metrics ordered based on an order of associated CMR identifiers (CMR IDs) or TCI state IDs.30.An apparatus for wireless communication at a network entity, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:transmit first signaling configuring a user equipment (UE) with a plurality of candidate channel measurement resources (CMRs) ;transmit second signaling prompting channel state information (CSI) reports based on one or more CMRs from the of the candidate CMRs; andreceive the CSI reports at different reporting occasions, wherein CSI reports at different reporting occasions include measurements for different subsets of CMRs from the candidate CMRs and the subset of CMRs for each reporting occasion is determined by a CMR ID interval.
Citation Information
Patent Citations
Channel state information determination method, reporting setting determination method, device and related equipment
CN114390554A
Rank indicator and layer indicator signaling in incoherent joint transmission channel state information
CN117121391A
CSI report configuration with multiple CSI reports
WO2021174378A1
UE initiated unified TCI switching
WO2023010507A1
Methods and apparatus for CSI reporting on multi-panel pusch
WO2023201168A1