Uplink beamforming

Abstract

Apparatus, methods, and computer program products for wireless communication are provided. An example method can include transmitting, to a second network entity, a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity. The example method can also include transmitting, to the second network entity, a set of beamforming weights based on the indication of diversity and the first number of scheduled layers.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 418,144, entitled “UPLINK BEAMFORMING”, filed January 19, 2024, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0002] This disclosure relates generally to communication systems, and more specifically to wireless communication systems with uplink beamforming. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0005] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In one aspect of this disclosure, methods, computer-readable media, and apparatus are provided at a first network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to send to a second network entity a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to send to the second network entity a beamforming weight set based on the indication of diversity and the first number of scheduled layers.

[0007] In another aspect of this disclosure, methods, computer-readable media, and apparatus are provided at a first network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to transmit a set of probe reference signals (SRS) samples to a second network entity. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive from the second network entity a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive from the second network entity a set of beamforming weights based on the indication of diversity and the first number of scheduled layers, the beamforming weights being based on the SRS sample set.

[0008] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0011] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0012] Figure 2CThis is an illustration of an example of a second frame according to various aspects of this disclosure.

[0013] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network according to various aspects of this disclosure.

[0015] Figure 4 This is an illustration of network nodes and UEs communicating via beamforming according to various aspects of this disclosure.

[0016] Figure 5 This is a diagram illustrating an example of communication between a first network entity and a second network entity.

[0017] Figure 6 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0018] Figure 7 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0019] Figure 8 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0020] Figure 9 These are illustrations of specific hardware implementations of example network entities according to various aspects of this disclosure.

[0021] Figure 10 These are illustrations illustrating specific hardware implementations of various aspects of this disclosure for network entities. Detailed Implementation

[0022] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0023] The aspects presented in this paper can facilitate a reduction in the size of C-plane messages and decrease the likelihood of sending zero beamforming weights by introducing new parameters to C-plane messages carrying beamforming weights. Based on the aspects presented in this paper, C-plane messages carrying beamforming weights may include the parameters diversity and numLayers. The diversity parameter informs the O-RU whether the O-RU diversity variant of uplink beamforming is enabled, and the numLayers parameter indicates the number of scheduled layers.

[0024] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0025] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0026] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible to a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0027] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0028] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0029] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs) (i.e., central or distributed units). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0030] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0031] Figure 1Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0032] Each of these units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals or transmit signals to one or more other units via wireless transmission media.

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

[0034] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0035] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration allows the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

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

[0039] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell) and the secondary component carrier can be referred to as the secondary cell (SCell).

[0040] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0041] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether a channel is available before communication.

[0042] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0043] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0044] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0045] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0046] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0047] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional rate calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0048] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0049] In some aspects, base station 102, such as RU or DU, may include weighting component 199. In some aspects, weighting component 199 may be located at DU and configured to send a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity to the second network entity. In some aspects, weighting component 199 may be configured to send a beamforming weight set based on the indication of diversity and the first number of scheduled layers to the second network entity. In some aspects, weighting component 199 may be located at RU and configured to send a set of sounding reference signals (SRS) samples to the second network entity. In some aspects, weighting component 199 may be configured to receive from the second network entity the first indication of diversity and the second indication of the first number of scheduled layers associated with the first network entity. In some aspects, weighting component 199 may be configured to receive from the second network entity a beamforming weight set based on the indication of diversity and the first number of scheduled layers, the beamforming weight set being based on the SRS sample set.

[0050] While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0051] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may be a component of: a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. Alternatively, a network node may be a base station or a network entity. Furthermore, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In other aspects of this example, the first network node, the second network node, and the third network node may differ from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a wider example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where the UE is configured to receive information from the base station and the first network node is configured to receive information from the second network node, the first network node may refer to the first UE configured to receive information, the first base station, the first device, the first equipment, the first computing system, a first set of one or more components or a first processing entity, etc.; and the second network node may refer to the second UE, the second base station, the second device, the second equipment, the second computing system, a second set of one or more components or a second processing entity, etc.

[0052] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0053] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured using slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured using slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured using any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0054] Figures 2A to 2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0055]

[0056] Table 1: Parameter Set, SCS, and CP

[0057] For a normal CP (14 symbols per slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols per slot and 2 slots per subframe. µ One time slot. The subcarrier spacing can be equal to 2. µ 15kHz, of which The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0058] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0060] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0061] like Figure 2CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0062] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0063] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0064] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. A channel estimate from channel estimator 374 is used to determine the decoding and modulation scheme, as well as for spatial processing. This channel estimate can be derived from a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0065] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0066] The controller / processor 359 may be associated with at least one memory 360 storing program code and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0067] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0068] The TX processor 368 can use the reference signal transmitted from the base station 310 or the channel estimate derived from feedback by the channel estimator 358 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0069] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0070] The controller / processor 375 may be associated with at least one memory 376 storing program code and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0071] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupling. Figure 1 The weighted components of 199 are considered in various aspects.

[0072] Figure 4 This is diagram 400 illustrating communication between network node 402 and UE 404. (See reference...) Figure 4 Network node 402 can transmit beamforming signals to UE 404 in one or more of the following directions: 402a, 402b, 402c, 402d, 402e, 402f, 402g, and 402h. UE 404 can receive beamforming signals from network node 402 in one or more receiving directions: 404a, 404b, 404c, and 404d. UE 404 can also transmit beamforming signals to network node 402 in one or more of the following directions: 404a-404d. Network node 402 can receive beamforming signals from UE 404 in one or more receiving directions: 402a-402h. Network node 402 / UE 404 can perform beamforming training to determine the optimal receiving and transmitting directions for each of network node 402 / UE 404. The transmitting and receiving directions of network node 402 can be the same or different. The transmit and receive directions of UE 404 may be the same or different. The term "beam" may also be referred to as "spatial filter". Beamforming may also be referred to as "spatial filtering". As used herein, the term "beam" may correspond to "spatial filter".

[0073] In response to different conditions, UE 404 may determine, for example, to switch beams between beams 402a-402h. The beam at UE 404 can be used for receiving downlink communications and / or transmitting uplink communications. In some examples, network node 402 may transmit a signal that triggers beam switching for UE 404. The Transmit Configuration Indication (TCI) state may include quasi-co-location (QCL) information, which the UE can use to derive timing / frequency errors and / or transmit / receive spatial filtering for transmitted / received signals. Two antenna ports are said to be quasi-co-located if the properties of a channel transmitting symbols on one antenna port can be inferred from a channel transmitting symbols on another antenna port. The base station may indicate the TCI state to the UE as a transmit configuration indicating the QCL relationship between a signal (e.g., a reference signal) and the signal to be transmitted / received. For example, the TCI state may indicate the QCL relationship between a DL RS in an RS set and a PDSCH / PDCCH DM-RS port. The TCI state provides information about the different beam selections the UE uses to transmit / receive various signals. For example, network node 402 can indicate a change in the TCI state, and in response, UE 404 can switch to a new beam based on the new TCI state indicated by network node 402 (which may also be referred to as performing a beam switch).

[0074] One type of beamforming may include codebook-based beam scanning. The codebook may include information corresponding to the beams used for communication, such as beam index, direction, beam weights across antennas, antenna ordering information, beam steering information (e.g., azimuth and / or zenith angle), and / or other information associated with the beam. For example, the codebook may include a set of beamforming vectors (e.g., fixed or predefined beamforming vectors), and techniques for generating and / or combining vectors (both static and dynamic vectors). Beamforming codebooks may be designed for rank-1 analog beamforming or for higher-rank pre-decoding applications. Examples of codebooks may include a beam weight matrix, where different column vectors correspond to weights across different antennas for a specific data transmission layer.

[0075] Another type of beamforming can be non-codebook based, which can be called "dynamic beamforming". For dynamic beamforming in the uplink, SRS can be transmitted from the UE to the RU, and the RU can send raw SRS samples to the DU, so that the DU can perform spatial processing on these samples and calculate beamforming weights, which can also be called "beam weights".

[0076] O-RAN base stations may include O-RAN Distributed Units (O-DUs) and O-RAN Radio Units (O-RUs), with lower-layer functions split between O-DUs and O-RUs based on lower-layer function splitting. Specifically, an O-DU may refer to a logical node configured to host the RLC layer, MAC layer, and high PHY layer based on lower-layer function splitting. An O-RU may refer to a logical node configured to host the low PHY layer and RF processing based on lower-layer function splitting. O-RAN may include an open fronthaul (FH) interface between O-DUs and O-RUs, and the open FH interface may include a control user synchronization (CUS) plane and a management (M) plane.

[0077] The C-plane is the control plane, which specifically involves real-time control between the O-DU and O-RU. The U-plane is the user plane, which involves IQ sample data transmitted between the O-DU and O-RU. The S-plane is the synchronization plane, which involves services between the O-RU or between the O-DU and the synchronization controller. The M-plane is the management plane, which involves management operations for sharing configuration management between the O-DU and O-RU.

[0078] When the network system starts up, a set of configuration management messages can be exchanged on the M-plane between the O-DU and O-RU. The O-DU and O-RU can configure the M-plane accordingly and use the configuration for CUS-plane communication.

[0079] After the network system starts up, the M-face configuration can be dynamically changed via Remote Procedure Call (RPC) messages. For example, the O-DU and O-RU can dynamically change the M-face configuration with get-config and edit-config RPCs. In some aspects, the O-DU and O-RU can use RPC messages to exchange protocols. RPC messages can dynamically change the M-face configuration between the O-DU and the O-RU.

[0080] As used herein, the term "TRX" may refer to a specific processing chain within an O-RU associated with a digital-to-analog (D / A) converter or an analog-to-digital (A / D) converter. As an example, the processing chain may take a digital signal as input, process the digital signal using a D / A converter, process the output of the D / A converter using a low-pass filter, perform up-conversion based on a local oscillator, amplify the signal using a power amplifier, filter the signal based on a band-pass filter, and process the signal based on a phase shifter. TRX may correspond to forward current.

[0081] As used in this article, the term "fronthaul" may refer to the logical link connecting the O-DU and O-RU.

[0082] As used herein, the term "spatial stream" can refer to the data stream on the DL associated with the pre-decoded data (which may be the same as or different from the layer if there is an extension in the pre-decoding), and the data stream on the UL associated with the number of outputs from digital beamforming. Due to digital beamforming, the number of TRXs may exceed the number of fronthaul streams, and due to analog beamforming, the number of TRXs may be less than the number of antenna elements. "Spatial stream" can correspond to the scheduled layer.

[0083] The specific type of signaling used to transmit beamforming weights can be referred to as a “section extension”. In some wireless communication systems, beamforming weights can be transmitted for all TRXs of every beam present in the system. In a diversity variant of uplink beamforming (where the number of scheduled layers is less than the number of fronthaul flows), non-zero beamforming weights can be transmitted for some TRXs, and zero beamforming weights can be transmitted for both the in-phase (I) and quadrature (Q) components for the remaining TRXs. For example, in an eight-TRX system with eight fronthaul flows, in some wireless communication systems, a C-plane message can be transmitted for the PUSCH of a UE with a layer distributed across the eight fronthaul flows, and this C-plane message can indicate that the beamforming weights for TRX 3 have non-zero values, and the beamforming weights for TRX 0-2 and TRX 4-7 are all zero. The aspects presented herein can facilitate a reduction in the size of the C-plane message by introducing new parameters to the C-plane message carrying the beamforming weights, and reduce the likelihood of zero beamforming weights being transmitted. Based on the aspects provided in this paper, the C-plane message carrying beam weights may include the parameter diversity and the parameter numLayers. The parameter diversity can notify the O-RU whether the O-RU diversity variant of uplink beamforming is enabled, and the parameter numLayers can indicate the number of scheduled layers.

[0084] Based on the aspects provided in this article, Table 2 below provides an example data format for segment extension 11:

[0085]

[0086] Table 2: Example data format used for transmitting beamforming weights

[0087] The parameter ef can represent the extension flag and can be used to indicate whether there is another extension (ef=1) or whether this is the last extension (ef=0).

[0088] The parameter disableBFWs can indicate whether beamforming weights are disabled, and can also be used to indicate whether beamforming weights under segment spread are disabled.

[0089] The parameter RAD indicates the reset following a PRB discontinuity and can be used in conjunction with a segment extension that allows for discontinuous frequency allocation. When the parameter `section` refers to a set of consecutive PRBs, a default value of RAD = 1 can be used. When a segment extension that allows for discontinuous frequency allocation is used with segment extension 11, this parameter indicates whether the PRB bundle boundary is reset (RAD = 1) after a discontinuity occurs in the PRB allocation, or whether the PRB bundle boundary is mapped to the PRB regardless of the discontinuity.

[0090] The parameter `diversity` indicates whether the O-RU diversity variant of uplink beamforming (where the number of scheduled layers is less than the number of fronthaul flows) is enabled. `diversity` can be a binary flag that can be set to "true" or "false". When `diversity` is set to true (which indicates that the O-RU diversity variant of uplink beamforming is enabled), beam weights are transmitted for the applicable number of TRXs, but not for all TRXs in the system. For example, the applicable TRXs may correspond to the TRXs associated with the fronthaul flows. O-RU may assume that the beamforming weights used for other TRXs are zero.

[0091] The parameter `numLayers` helps the O-RU calculate the number of TRXs whose beamforming weights will be set to zero. In some aspects, `numLayers` can represent the total number of scheduled layers. In other aspects, `numLayers` can indicate the number of scheduled layers whose beamforming weights will be set to zero. In some aspects, `numLayers` can be used to indicate the number of layers present in the system, helping the O-RU calculate the number of TRXs whose beamforming weights will be set to 0. In some aspects, `numLayers` can have a defined range of values:

[0092]

[0093] Table 3: Example Value Range

[0094] The parameter extType can represent an extension type, and can provide an extension type that provides additional parameters specific to the data extensions for this topic.

[0095] The parameter extLen can represent the extended length and can provide the length of the data format in 32-bit (or 4-byte) words.

[0096] The parameter numBundPrb can represent the number of bundled PRBs for each beamforming weight, and can also be the number of bundled PRBs for each set of beamforming weights.

[0097] The parameter bfwCompHdr represents the beamforming weight compression header and defines the compression method and IQ bit width for beamforming weights in C-plane messages. For the block compression method, the block size is a vector of beamforming weights for a specific PRB beam.

[0098] The parameter bfwCompParam of PRB beam x can represent the beamforming weight compression parameter and can be applied to the following vector for the beamforming weight of a specific PRB beam (beam x).

[0099] The parameter beamId can represent the beam identifier.

[0100] The parameters bfwI and bfwQ can represent the beamforming weights I and Q, respectively. bfwI can represent the in-phase value of the time-domain beamforming weight, and bfwQ can represent the quadrature phase value of the time-domain beamforming weight.

[0101] In some aspects, the beamforming weights for the k-th forward current (FHS) can be in the structure [precedingTRXsWeights applicableTRXWeights trailingTRXWeights], where the parameter `precedingTRXsWeights` represents the beamforming weights for the TRXs before applying the TRX, the parameter `applicableTRXWeights` can represent the beamforming weights for the applicable TRXs corresponding to the scheduled layer, and `trailingTRXWeights` represents the beamforming weights for the TRXs after applying the TRX. The applicable TRX beamforming weights can be transmitted in the C-plane message, and the beamforming weights for `precedingTRXs` and `trailingTRXweights` can be zero. The O-RU can calculate the number of TRXs before and after applying the TRX based on the following:

[0102]

[0103] The parameter `numFHS` represents the number of forward flows. The parameter `numLayers` represents the number of scheduled layers. The parameter `numTRX` represents the total number of TRXs.

[0104] The parameter numApplicableTRX can be directly calculated from the C-plane and represents the number of TRX that can be transmitted for its beamforming weights. The parameter numFHS can be equal to the number of eaxcids (extended antenna-carrier identifiers) used for an allocation.

[0105] In some aspects, an M-plane capability may be introduced to indicate whether the O-RU supports diversity or whether it supports setting the beamforming weight of TRXs that do not correspond to the forward current to zero. This M-plane capability may be in the form of: +--ro cplane-diversity-indicator-supported Boolean. For example, in some aspects, the O-RU 502 may send a capability indication 505 (e.g., in the form of "cplane-diversity-indicator-supported") to the O-DU 504, indicating whether the O-RU 502 supports diversity or whether it supports setting the beamforming weight of TRXs that do not correspond to the forward current to zero.

[0106] Figure 5 Figure 500 illustrates an example communication between a first network entity (which may be O-RU 502) and a second network entity (which may be O-DU 504).

[0107] At point 506, O-DU 504 may send a configuration message to O-RU 502 comprising multiple M-face configuration sets, each M-face configuration set including a set of M-face configuration parameters. That is, O-DU 504 may notify O-RU 502 of these multiple M-face configuration sets. For example, O-DU 504 may send at least one RPC message to O-RU 502, the at least one RPC message including an M-face configuration ID and one or more parameter pairs for an activation period.

[0108] At 508, O-RU 502 can configure the multiple M-face configuration sets based on the configuration message received at 506. At 510, O-DU 504 can configure the multiple M-face configuration sets based on the configuration message sent at 506.

[0109] At 512, O-RU 502 can send SRS samples to O-DU 504, which can be the original SRS samples. After receiving the SRS samples at 512, at 513, O-DU 504 can calculate the beamforming weight set associated with the applicable TRX (one or more TRXs corresponding to one or more scheduled layers).

[0110] At 514, O-DU 504 may send a C-plane message to O-RU 502 as described in conjunction with Table 2. This C-plane message may include a first indication of diversity (e.g., parameter diversity) and a second indication of the number of scheduled layers (e.g., parameter numLayers), as well as a set of beamforming weights associated with the applicable TRX (one or more TRXs corresponding to one or more scheduled layers). For non-applicable TRXs (one or more TRXs not corresponding to one or more scheduled layers), the C-plane message may not include beamforming weights with I or Q components having a value of zero.

[0111] After receiving the C-plane message at 514, at 516, O-RU 502 can calculate the number of TRX before and after applying TRX based on the following:

[0112]

[0113] Figure 6 This is a flowchart 600 of a wireless communication method. This method can be performed by network entities (e.g., base station 102, network entity 902, network entity 1060). The aspects provided herein reduce the size of the C-plane message by introducing new parameters to the C-plane message carrying beamforming weights, and reduce the likelihood of transmitting zero beamforming weights.

[0114] At 602, the network entity may send a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity to the second network entity. For example, the network entity (e.g., O-DU 504) may send the first indication of diversity and the second indication of the number of scheduled layers associated with the first network entity to the second network entity (e.g., O-RU 502) (e.g., at 514). In some aspects, 602 may be performed by the weighting component 199.

[0115] At 608, the network entity may send a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity. For example, the network entity may send a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity (e.g., at 514). In some aspects, 606 may be performed by the weighting component 199.

[0116] Figure 7 This is a flowchart 700 of a wireless communication method. This method can be performed by network entities (e.g., base station 102, network entity 902, network entity 1060). The aspects provided herein reduce the size of the C-plane message by introducing new parameters to the C-plane message carrying beamforming weights, and reduce the likelihood of transmitting zero beamforming weights.

[0117] At 701, the network entity may receive an indication from the second network entity of capabilities associated with diversity. For example, the network entity may receive an indication from the second network entity of capabilities associated with diversity (e.g., 505). At 702, the network entity may receive a set of SRS samples from the second network entity. For example, the network entity may receive a set of SRS samples from the second network entity (e.g., at 512). In some aspects, 701 and 702 may be performed by weighting component 199.

[0118] At 704, the network entity can compute a beamforming weight set based on the SRS sample set. For example, the network entity can compute the beamforming weight set based on the SRS sample set (e.g., at 513). In some aspects, 704 can be performed by the weight component 199.

[0119] At 706, the network entity may send a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity to the second network entity. For example, the network entity (e.g., O-DU 504) may send the first indication of diversity and the second indication of the number of scheduled layers associated with the first network entity to the second network entity (e.g., O-RU 502) (e.g., at 514). In some aspects, 706 may be performed by the weighting component 199.

[0120] At 708, the network entity may send a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity. For example, the network entity may send a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity (e.g., at 514). In some aspects, 706 may be performed by the weighting component 199.

[0121] In some aspects, the first indication for diversity indicates whether the number of scheduled layers is less than the number of forward flows (e.g., a first number of scheduled layers is less than a second number of forward flows). In some aspects, the first indication for diversity indicates whether a diversity variant is enabled to allow the number of scheduled layers to be less than the number of forward flows. In some aspects, the first indication is a binary flag indicating whether a diversity variant is enabled or disabled. In some aspects, the second indication indicates the number of scheduled layers based on a specific value from a set of configuration values. In some aspects, the beamforming weight set includes a certain number of beamforming weights, and the number of transceivers associated with the second network entity and associated with that number of beamforming weights is based on diversity and equal to the total number of forward flows divided by the number of scheduled layers. In some aspects, the second beamforming weight set associated with the remaining transceiver set, which is different from that number of transceivers, is equal to zero. For example, the number of transceivers may be calculated by the second network entity as the total number of forward flows divided by the number of layers, and the second network entity may assume the beamforming weights of the remaining transceivers to be zero. In some respects, the number of beamforming weights can be referred to as the second number of beamforming weights, and the number of transceivers can be referred to as the third number of transceivers.

[0122] Figure 8 This is a flowchart 800 of a wireless communication method. This method can be performed by network entities (e.g., base station 102, network entity 902, network entity 1060). The aspects provided herein reduce the size of the C-plane message by introducing new parameters to the C-plane message carrying beamforming weights, and reduce the likelihood of transmitting zero beamforming weights.

[0123] At 802, a network entity may send an SRS sample set to a second network entity. For example, a network entity (e.g., O-RU 502) may send an SRS sample set (e.g., 512) to a second network entity (e.g., O-DU 504). In some aspects, 802 may be performed by the weighting component 199.

[0124] At 804, the network entity may receive from the second network entity a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity. For example, the network entity (e.g., O-RU 502) may receive from the second network entity (e.g., at 514) the first indication of diversity and the second indication of the number of scheduled layers associated with the first network entity. In some aspects, 804 may be performed by the weighting component 199.

[0125] At 806, a network entity may receive from a second network entity (e.g., at 514) a beamforming weight set based on an indication of diversity and the number of scheduled layers, the beamforming weight set being based on an SRS sample set. For example, a network entity (e.g., O-RU 502) may receive from a second network entity a beamforming weight set based on an indication of diversity and the number of scheduled layers, the beamforming weight set being based on an SRS sample set. In some aspects, 806 may be performed by a weighting component 199. In some aspects, the first indication of diversity indicates whether the number of scheduled layers is less than the number of forward flows (e.g., a first number of scheduled layers is less than a second number of forward flows). In some aspects, the first indication of diversity indicates whether a diversity variant is enabled to allow the number of scheduled layers to be less than the number of forward flows. In some aspects, the first indication is a binary flag indicating whether a diversity variant is enabled or disabled. In some aspects, the second indication indicates the number of scheduled layers based on a specific value from a set of configuration values. In some aspects, the beamforming weight set includes a certain number of beamforming weights, and the number of transceivers associated with the second network entity and with that number of beamforming weights is based on diversity and equal to the total number of forward flows divided by the number of scheduled layers. In some aspects, the number of beamforming weights may be referred to as a second number of beamforming weights, and the number of transceivers may be referred to as a third number of transceivers. In some aspects, the second beamforming weight set associated with the remaining set of transceivers, which is different from that number of transceivers, is equal to zero.

[0126] Figure 9Figure 900 illustrates an example of a hardware implementation for network entity 902. Network entity 902 may be a BS, a component of a BS, or implement BS functionality. Network entity 902 may include at least one of CU 910, DU 930, or RU 940. For example, depending on the layer functionality handled by component 199, network entity 902 may include: CU 910; both CU 910 and DU 930; each of CU 910, DU 930, and RU 940; DU 930; both DU 930 and RU 940; or RU 940. CU 910 may include at least one CU processor 912. CU processor 912 may include on-chip memory 912'. In some aspects, CU 910 may also include an additional memory module 914 and a communication interface 918. CU 910 communicates with DU 930 via a midhaul link (such as an F1 interface). DU 930 may include at least one DU processor 932. The DU processor 932 may include on-chip memory 932'. In some aspects, the DU 930 may also include an additional memory module 934 and a communication interface 938. The DU 930 communicates with the RU 940 via a fronthaul link. The RU 940 may include at least one RU processor 942. The RU processor 942 may include on-chip memory 942'. In some aspects, the RU 940 may also include an additional memory module 944, one or more transceivers 946, an antenna 980, and a communication interface 948. The RU 940 communicates with the UE 104. The on-chip memories 912', 932', 942' and the additional memory modules 914, 934, 944 may each be considered as computer-readable media / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 912, 932, 942 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. Computer-readable media / storage can also be used to store data manipulated by the processor while executing software.

[0127] As discussed above, the weighting component 199 may be located at the DU and configured to send a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity to the second network entity. In some aspects, the weighting component 199 may be configured to send a beamforming weight set to the second network entity based on the indication of diversity and the number of scheduled layers. In some aspects, the weighting component 199 may be located at the RU and configured to send a set of sounding reference signals (SRS) samples to the second network entity. In some aspects, the weighting component 199 may be configured to receive from the second network entity the first indication of diversity and the second indication of the number of scheduled layers associated with the first network entity. In some aspects, the weighting component 199 may be configured to receive from the second network entity a beamforming weight set based on the indication of diversity and the number of scheduled layers, the beamforming weight set being based on the SRS sample set. The weighting component 199 may be located within one or more processors of one or more of CU910, DU 930, and RU 940. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 902 may include various components configured for various functions. In one configuration, network entity 902 may include means for sending a first indication of diversity and a second indication of the number of scheduled layers associated with a first network entity to a second network entity. In some aspects, network entity 902 may include means for sending a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity. In some aspects, network entity 902 may include means for receiving a set of sounding reference signals (SRS) samples from the second network entity. In some aspects, network entity 902 may include means for calculating a beamforming weight set based on the SRS sample set. In some aspects, network entity 902 may include components for transmitting a set of probe reference signals (SRS) samples to a second network entity. In some aspects, network entity 902 may include components for receiving from the second network entity a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity. In some aspects, network entity 902 may include components for receiving from the second network entity a set of beamforming weights based on the indication of diversity and the number of scheduled layers, the beamforming weights being based on the SRS sample set. The component may be a component 199 of network entity 902 configured to perform the functions described therein.As described above, network entity 902 may include TX processor 316, RX processor 370, and controller / processor 375. Therefore, in one configuration, the component may be the TX processor 316, RX processor 370, and / or controller / processor 375 configured to perform the functions described therein.

[0128] Figure 10 Figure 1000 illustrates an example of a hardware implementation for network entity 1060. In one example, network entity 1060 may be within core network 120. Network entity 1060 may include at least one network processor 1012. Network processor 1012 may include on-chip memory 1012'. In some aspects, network entity 1060 may also include an additional memory module 1014. Network entity 1060 communicates with CU 1002 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 1080. On-chip memory 1012' and additional memory module 1014 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 1012 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by a corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor while executing the software.

[0129] As discussed above, weighting component 199 may be located at the DU and configured to send a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity to the second network entity. In some aspects, weighting component 199 may be configured to send a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity. In some aspects, weighting component 199 may be located at the RU and configured to send a set of sounding reference signals (SRS) samples to the second network entity. In some aspects, weighting component 199 may be configured to receive from the second network entity the first indication of diversity and the second indication of the number of scheduled layers associated with the first network entity. In some aspects, weighting component 199 may be configured to receive from the second network entity a beamforming weight set based on the indication of diversity and the number of scheduled layers, the beamforming weight set being based on the SRS sample set. Component 199 may be within network processor 1012. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1060 may include various components configured for various functions. In one configuration, network entity 1060 may include means for sending a first indication of diversity and a second indication of the number of scheduled layers associated with a first network entity to a second network entity. In some aspects, network entity 1060 may include means for sending a beamforming weight set based on the indication of diversity and the number of scheduled layers to the second network entity. In some aspects, network entity 1060 may include means for receiving a set of sounding reference signals (SRS) samples from the second network entity. In some aspects, network entity 1060 may include means for calculating a beamforming weight set based on the SRS sample set. In some aspects, network entity 1060 may include components for transmitting a set of probe reference signals (SRS) samples to a second network entity. In some aspects, network entity 1060 may include components for receiving from the second network entity a first indication of diversity and a second indication of the number of scheduled layers associated with the first network entity. In some aspects, network entity 1060 may include components for receiving from the second network entity a set of beamforming weights based on the indication of diversity and the number of scheduled layers, the beamforming weights being based on the SRS sample set. The component may be a component 199 of network entity 1060 configured to perform the functions described therein.

[0130] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of an exemplary approach. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts can be rearranged based on design preferences. Furthermore, some boxes can be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0131] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to execute a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to “output” data (such as transmission, signal, or message) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data.A device configured to "acquire" data (such as, transmit, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc., cannot replace the word "component." Therefore, no claim element will be construed as a functional component unless the element is explicitly recited using the phrase "component for..."

[0132] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0133] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0134] Aspect 1 is a method for wireless communication performed by a first network entity, the method comprising: sending to a second network entity a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity; and sending to the second network entity a beamforming weight set based on the indication of diversity and the first number of scheduled layers.

[0135] Aspect 2 is the method according to aspect 1, wherein the first indication of the subset indicates whether the first quantity of the scheduled layer is less than the second quantity of the forward stream.

[0136] Aspect 3 is the method according to any one of aspects 1 to 2, wherein the first indication of the diversity indicates whether a diversity variant is enabled to allow the first number of scheduled layers to be less than the second number of forward flows.

[0137] Aspect 4 is the method according to aspect 3, wherein the first indication is a binary flag indicating whether the diversity variant is enabled or disabled.

[0138] Aspect 5 is the method according to any one of aspects 1 to 4, wherein the second indication indicates the first quantity of the scheduled layer based on a specific value indicating a configuration value set.

[0139] Aspect 6 is the method according to any one of aspects 1 to 5, wherein the beamforming weight set includes a second number of beamforming weights, and wherein a third number of transceivers associated with the second network entity and associated with the number of beamforming weights is based on the diversity and equal to the total number of forward flows divided by the first number of scheduled layers.

[0140] Aspect 7 is the method according to aspect 6, wherein a second beamforming weight set corresponding to one or more forward currents is equal to zero, wherein the second beamforming weight set is different from the beamforming weight set.

[0141] Aspect 8 is the method according to any one of aspects 1 to 7, the method further comprising: receiving from the second network entity a third indication of the capability associated with the diversity; receiving from the second network entity a set of probe reference signals (SRS) samples; and calculating the beamforming weight set based on the SRS sample set.

[0142] Aspect 9 is a method for wireless communication performed by a first network entity, the method comprising: transmitting a set of sounding reference signals (SRS) samples to a second network entity; receiving from the second network entity a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity; and receiving from the second network entity a set of beamforming weights based on the indication of diversity and the first number of scheduled layers, the beamforming weights being based on the set of SRS samples.

[0143] Aspect 10 is the method according to aspect 9, wherein the first indication of the subset indicates whether the first quantity of the scheduled layer is less than the second quantity of the forward stream.

[0144] Aspect 11 is the method according to any one of aspects 9 to 10, wherein the first indication of the diversity indicates whether a diversity variant is enabled to allow the first number of scheduled layers to be less than the second number of forward flows.

[0145] Aspect 12 is the method according to aspect 11, wherein the first indication is a binary flag indicating whether the diversity variant is enabled or disabled.

[0146] Aspect 13 is the method according to any one of aspects 9 to 12, wherein the second indication indicates the first quantity of the scheduled layer based on a specific value indicating a configuration value set.

[0147] Aspect 14 is the method according to any one of aspects 9 to 13, wherein the beamforming weight set includes a second number of beamforming weights, and wherein a third number of transceivers associated with the second network entity and associated with the number of beamforming weights is based on the diversity and equal to the total number of forward flows divided by the first number of scheduled layers.

[0148] Aspect 15 is the method according to any one of aspects 9 to 14, wherein the second beamforming weight set associated with the remaining transceiver set, which is different from the third number of transceivers, is equal to zero.

[0149] Aspect 16 is an apparatus for wireless communication, the apparatus including at least one processor coupled to at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured to implement the method according to any one of aspects 1 to 15.

[0150] Aspect 17 may be combined with aspect 16 and also includes a transceiver coupled to the at least one processor.

[0151] Aspect 18 is a device for wireless communication, the device including components for implementing any one of aspects 1 to 15.

[0152] Aspect 19 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 15.

[0153] Various aspects have been described herein. These and other aspects are within the scope of the following claims.

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and based at least in part on information stored in the at least one memory, the at least one processor is configured individually or in any combination to cause the first network entity to: Send a first indication of diversity and a second indication of the first number of scheduled layers associated with the first network entity to the second network entity; and Send the first indication of the subset and the first number of beamforming weight sets of the scheduled layer to the second network entity.

2. The apparatus of claim 1, wherein the first indication of the diversity indicates whether the first quantity of the scheduled layer is less than the second quantity of the forward stream.

3. The apparatus of claim 1, wherein the first indication of the diversity indicates whether a diversity variant is enabled to allow the first number of scheduled layers to be less than the second number of forward flows.

4. The apparatus of claim 3, wherein the first indication is a binary flag indicating whether the diversity variant is enabled or disabled.

5. The apparatus of claim 1, wherein the second indication indicates the first quantity of the scheduling layer based on a specific value from a set of configuration values.

6. The apparatus of claim 1, wherein the beamforming weight set includes a second number of beamforming weights, and wherein a third number of transceivers associated with the second network entity and associated with the second number of beamforming weights is based on the diversity and equal to the total number of forward flows divided by the first number of scheduled layers.

7. The apparatus of claim 6, wherein the second beamforming weight set associated with the remaining transceiver set, which is different from the third number of transceivers, is equal to zero.

8. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination, to cause the first network entity to: Receive a third indication of the capabilities associated with the diversity from the second network entity; Receive a set of probe reference signal (SRS) samples from the second network entity; and The beamforming weight set is calculated based on the SRS sample set.

9. An apparatus for wireless communication at a first network entity, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and based at least in part on information stored in the at least one memory, the at least one processor is configured individually or in any combination to cause the first network entity to: Send a set of probe reference signals (SRS) samples to the second network entity; Receive a first indication of diversity from the second network entity and a second indication of a first number of scheduled layers associated with the first network entity; as well as The second network entity receives a beamforming weight set based on the first indication of the diversity and the first number of scheduled layers, the beamforming weight set being based on the SRS sample set.

10. The apparatus of claim 9, wherein the first indication of the diversity indicates whether the first quantity of the scheduled layer is less than the second quantity of the forward stream.

11. The apparatus of claim 9, wherein the first indication of the diversity indicates whether a diversity variant is enabled to allow the first number of scheduled layers to be less than the second number of forward flows.

12. The apparatus of claim 11, wherein the first indication is a binary flag indicating whether the diversity variant is enabled or disabled.

13. The apparatus of claim 9, wherein the second indication indicates the first quantity of the scheduling layer based on a specific value indicating a configuration value set.

14. The apparatus of claim 9, wherein the beamforming weight set includes a second number of beamforming weights, and wherein a third number of transceivers associated with the second network entity and associated with the second number of beamforming weights is based on the diversity and equal to the total number of forward flows divided by the first number of scheduled layers.

15. The apparatus of claim 14, wherein the second beamforming weight set associated with the remaining transceiver set, which is different from the third number of transceivers, is equal to zero.

16. A method for wireless communication performed by a first network entity, the method comprising: Send a first indication of diversity and a second indication of a first number of scheduled layers associated with the first network entity to the second network entity; as well as Send the first indication of the subset and the first number of beamforming weight sets of the scheduled layer to the second network entity.

17. The method of claim 16, wherein the first indication of the subset indicates whether the first number of the scheduled layer is less than the second number of the forward stream.

18. The method of claim 16, wherein the first indication of the diversity indicates whether a diversity variant is enabled to allow the first number of scheduled layers to be less than the second number of forward flows.

19. The method of claim 18, wherein the first indication is a binary flag indicating whether the diversity variant is enabled or disabled.

20. The method of claim 16, wherein the second indication indicates the first quantity of the scheduled layer based on a specific value from a set of configuration values.

21. The method of claim 16, wherein the beamforming weight set includes a second number of beamforming weights, and wherein a third number of transceivers associated with the second network entity and associated with the second number of beamforming weights is based on the diversity and equal to the total number of forward flows divided by the first number of scheduled layers.

22. The method of claim 21, wherein a second beamforming weight set corresponding to one or more forward currents is equal to zero, wherein the second beamforming weight set is different from the beamforming weight set.

23. The method according to claim 16, further comprising: Receive a third indication of the capabilities associated with the diversity from the second network entity; Receive a set of probe reference signal (SRS) samples from the second network entity; as well as The beamforming weight set is calculated based on the SRS sample set.

24. A method for wireless communication performed by a first network entity, the method comprising: Send a set of probe reference signals (SRS) samples to the second network entity; Receive a first indication of diversity from the second network entity and a second indication of a first number of scheduled layers associated with the first network entity; as well as The second network entity receives a beamforming weight set based on the first indication of the diversity and the first number of scheduled layers, the beamforming weight set being based on the SRS sample set.

25. The method of claim 24, wherein the first indication of the subset indicates whether the first number of the scheduled layer is less than the second number of the forward stream.

26. The method of claim 24, wherein the first indication of the diversity indicates whether a diversity variant is enabled to allow the first number of scheduled layers to be less than the second number of forward flows.

27. The method of claim 26, wherein the first indication is a binary flag indicating whether the diversity variant is enabled or disabled.

28. The method of claim 24, wherein the second indication indicates the first quantity of the scheduling layer based on a specific value indicating a configuration value set.

29. The method of claim 24, wherein the beamforming weight set includes a second number of beamforming weights, and wherein a third number of transceivers associated with the second network entity and associated with the second number of beamforming weights is based on the diversity and equal to the total number of forward flows divided by the first number of scheduled layers.

30. The method of claim 29, wherein the second beamforming weight set associated with the remaining transceiver set, which is different from the third number of transceivers, is equal to zero.

Images