Configuration of Wireless Unit Antenna Element

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a radio unit (RU, 240) can send a message (1305) to a controller (230, DU) of the RU that includes a list of ordered coordinates corresponding to a plurality of antenna elements in an antenna array of the RU. The RU can receive (1315) from the controller an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated. Numerous other aspects are described.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This patent application claims priority to U.S. Provisional Patent Application No. 63 / 366,200, entitled "CONFIGURATION OF RADIO UNIT ANTENNA ELEMENTS", filed on June 10, 2022, and U.S. Non - Provisional Patent Application No. 18 / 189,867, entitled "CONFIGURATION OF RADIO UNIT ANTENNA ELEMENTS", filed on March 24, 2023, which are hereby incorporated by reference in their entirety.

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatus for configuring radio unit antenna elements.

Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system can adopt a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). 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, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP (registered trademark)).

[0004] A wireless network may include one or more network nodes that support communication regarding wireless communication devices such as user equipment (UE) or multiple UEs. The UE can communicate with the network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks can support communication between terminals via local links (for example, among other examples, sidelink (SL), wireless local area network (WLAN) link, and / or wireless personal area network (WPAN) link).

[0005] The above multi-connectivity technology has been adopted in various telecommunications standards to provide a common protocol that enables various UEs to communicate at the urban, national, regional, and / or global levels. New Radio (NR), sometimes referred to as 5G, is a set of enhancements to the LTE mobile standard published by 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink and using CP-OFDM and / or Single-Carrier Frequency Division Multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, and by supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Since the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY OF THE INVENTION

[0006] Some aspects described in this specification relate to a method of wireless configuration performed by a radio unit (RU). The method may include transmitting, to a controller of the RU, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in an antenna array of the RU. The method may include receiving, from the controller, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0007] Some aspects described in this specification relate to a method of wireless configuration performed by a controller of the RU. The method may include receiving, from the RU, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in an antenna array of the RU. The method may include transmitting, to the RU, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0008] Some aspects described in this specification relate to an apparatus for wireless configuration in the RU. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a controller of the RU, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in an antenna array of the RU. The one or more processors may be configured to receive, from the controller, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0009] Some aspects described herein relate to an apparatus for a wireless configuration in a RU controller. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, from the RU, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the RU's antenna array. The one or more processors may be configured to transmit, to the RU, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0010] Some aspects described herein relate to a non-transitory computer-readable recording medium storing a set of instructions for wireless communication by a RU. When executed by one or more processors of the RU, the set of instructions may cause the RU to transmit, to the RU controller, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the RU's antenna array. When executed by one or more processors of the RU, the set of instructions may cause the RU to receive, from the controller, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0011] Some aspects described herein relate to a non-transitory computer-readable recording medium storing a set of instructions for wireless communication by a RU controller. When executed by one or more processors of the controller, the set of instructions may cause the controller to receive, from the RU, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the RU's antenna array. When executed by one or more processors of the controller, the set of instructions may cause the controller to transmit, to the RU, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a message including a list of ordered coordinates corresponding to a plurality of antenna elements within an antenna array of the apparatus to a controller of the apparatus. The apparatus may include means for receiving, from the controller, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a RU, a message including a list of ordered coordinates corresponding to a plurality of antenna elements within an antenna array of the RU. The apparatus may include means for transmitting, to the RU, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0014] Aspects are generally described, and illustrated, substantially as shown and described in connection with the drawings, the specification, and the accompanying documents, and include methods, apparatus, systems, computer program products, non-transitory computer-readable recording media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems.

[0015] In the foregoing, the features and technical advantages of the embodiments according to the present disclosure have been outlined rather extensively so as to enable a better understanding of the following "Modes for Carrying Out the Invention". Additional features and advantages will be described hereinafter. The disclosed concepts and specific embodiments can be readily utilized as a basis for modifying or designing other structures to accomplish the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their configurations and methods of operation, will be better understood along with the associated advantages by considering the following description in relation to the accompanying drawings. Each of the drawings is provided for purposes of illustration and description and is not provided as a definition of the limitations of the claims.

[0016] The aspects are illustrated in the present disclosure by way of example with respect to several embodiments, but those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using a variety of platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects can be implemented via an integrated chip embodiment, or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, and / or artificial intelligence devices). The aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the aspects and features described can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or analog adders) for analog and digital purposes. It is intended that the aspects described herein can be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures.

[0017] To gain a more detailed understanding of the features of the present disclosure listed above, a more detailed description, briefly summarized above, can be obtained by referring to the aspects, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings show only specific exemplary aspects of the present disclosure and, therefore, should not be considered as limiting the scope of the present disclosure, as the description may admit other equally effective aspects. The same reference numerals in different drawings can identify the same or similar elements.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

DETAILED DESCRIPTION OF THE INVENTION

[0019] Hereinafter, various aspects of the present disclosure will be described more fully with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to include any and all aspects of the present disclosure disclosed herein, regardless of whether they are implemented independently of any other aspect of the present disclosure or in combination with any other aspect of the present disclosure. For example, any number of the aspects described herein can be used to implement an apparatus or practice a method. Furthermore, the scope of the present disclosure is intended to include such apparatus or methods practiced using other structures, functionality, or a combination of structures and functionality in addition to, or other than, the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0020] Next, several aspects of the telecommunication system are presented with reference to various devices and technologies. These devices and technologies are described in the following "Modes for Carrying Out the Invention" and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the specific application example and the design constraints imposed on the overall system.

[0021] The aspects may be described herein using terms generally associated with 5G or New Radio (NR) radio access technology (RAT), but the aspects of the present disclosure can also be applied to other RATs such as 3G RAT, 4G RAT, and / or RATs following 5G (e.g., 6G).

[0022] FIG. 1 is a diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 can be, among other examples, a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or can include elements thereof. The wireless network 100 can include one or more network nodes 110 (shown as network nodes 110a, 110b, 110c, and 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, 120b, 120c, 120d, and 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 can include one or more network nodes. For example, the network node 110 can be an integrated network node, which means that the integrated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 can be a distributed network node (which may also be referred to as a distributed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs), etc.).

[0023] In some embodiments, network node 110 is a network node such as a RU that communicates with UE 120 via a radio access link, or includes such a network node. In some embodiments, network node 110 is a network node such as a DU that communicates with other network nodes 110 via a fronthaul link or a midhaul link, or includes such a network node. In some embodiments, network node 110 is a network node such as a CU that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, or includes such a network node. In some embodiments, network node 110 (such as an integrated network node 110 or a split network node 110) may include a plurality of network nodes such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission reception point (TRP), a DU, a RU, a CU, a network mobility element, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some embodiments, network node 110 can interconnect with each other within wireless network 100 or with one or more other network nodes 110 through various types of fronthaul, midhaul, and / or backhaul interfaces such as a direct physical connection, an air interface, or a virtual network using any suitable transport network.

[0024] In some embodiments, network node 110 can provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of network node 110 and / or the network node subsystem providing services in this coverage area, depending on the context in which the term is used. Network node 110 can provide communication coverage for macro cells, pico cells, femto cells, and / or another type of cell. A macro cell can cover a relatively large geographical area (e.g., several kilometers in radius) and can enable unrestricted access by UE 120 subscribed to the service. A pico cell can cover a relatively small geographical area and can enable unrestricted access by UE 120 subscribed to the service. A femto cell can cover a relatively small geographical area (e.g., a home) and can enable restricted access by UE 120 having relevance to that femto cell (e.g., UE 120 within a closed subscriber group (CSG)). Network node 110 related to a macro cell may be referred to as a macro network node. Network node 110 related to a pico cell may be referred to as a pico network node. Network node 110 related to a femto cell may be referred to as a femto network node or a home network node. In the embodiment shown in FIG. 1, network node 110a can be a macro network node related to macro cell 102a, network node 110b can be a pico network node related to pico cell 102b, and network node 110c can be a femto network node related to femto cell 102c. A network node can support one or more (e.g., three) cells. In some embodiments, a cell may not necessarily be fixed, and the geographical area of the cell may move according to the location of network node 110 (e.g., a mobile network node) which is mobile.

[0025] In some aspects, the term "base station" or "network node" may refer to a centralized base station, a distributed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more of their components. For example, in some aspects, the "base station" or "network node" may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a single device configured to perform one or more functions, such as the functions described herein in relation to network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of many different devices (which may be located at the same geographical location or different geographical locations) may be configured to perform at least a portion of a function or to perform at least a portion of a function redundantly, and the term "base station" or "network node" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations, or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions and not another. In this way, a single device may include two or more base stations.

[0026] Wireless network 100 may include one or more relay nodes. A relay node is a network node that can receive the transmission of data from an upstream node (e.g., network node 110 or UE 120) and transmit the transmission of that data to a downstream node (e.g., UE 120 or network node 110). The relay node can also be a UE 120 that can relay transmissions to other UEs 120. In the embodiment shown in FIG. 1, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 that relays communication may sometimes be referred to as a relay node, relay base station, relay network node, relay node, repeater, etc.

[0027] Wireless network 100 can be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmission power levels, different coverage areas, and / or different impacts on interference within wireless network 100. For example, a macro network node may have a high transmission power level (e.g., 5 to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have a lower transmission power level (e.g., 0.1 to 2 watts).

[0028] The network controller 130 may be coupled to or communicate with a set of network nodes 110 and can provide coordination and control regarding these network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 can communicate with each other directly or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 can be or include a CU or a core network device.

[0029] The UEs 120 can be distributed throughout the wireless network 100, and each UE 120 can be fixed or mobile. The UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UE 120 can be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a game device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0030] Some UEs 120 can be regarded as machine - type communication (MTC) UEs, or evolved or enhanced machine - type communication (eMTC) UEs. Examples of MTC UEs and / or eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 can be regarded as Internet - of - Things (IoT) devices and / or can be implemented as narrowband IoT (NB - IoT) devices. Some UEs 120 can be regarded as customer premise equipment. The UEs 120 can be included inside a housing that houses components of the UEs 120, such as processor components and / or memory components. In some embodiments, the processor component and the memory component can be integrally coupled. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) can be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0031] Generally, any number of wireless networks 100 can be deployed within a given geographical area. Each wireless network 100 can support a specific radio access technology (RAT) and can operate on one or more frequencies. The RAT may be referred to as a wireless technology, an air interface, etc. The frequency may be referred to as a carrier, a frequency channel, etc. To avoid interference between wireless networks of different RATs, each frequency can support a single RAT within a given geographical area. In some cases, an NR network or a 5G RAT network can be deployed.

[0032] In some embodiments, two or more UEs 120 (e.g., those shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., those that may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such embodiments, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by network node 110.

[0033] The devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various classes, bands, channels, etc. by frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is higher than 6 GHz, it should be understood that FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues can arise with respect to FR2, which, despite being different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band, is often (interchangeably) referred to as the "millimeter wave" band in documents and papers.

[0034] Frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating bands for these intermediate band frequencies are identified as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands within the range of FR3 can inherit the characteristics of FR1 and / or FR2, and thus, the features of FR1 and / or FR2 can be effectively extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands are identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is within the range of the EHF band.

[0035] With the above examples in mind, unless otherwise specified, terms such as "sub-6 GHz" may broadly represent frequencies that can be less than 6 GHz, frequencies that can be within the range of FR1, or frequencies that can include intermediate band frequencies when used in this specification. Furthermore, unless otherwise specified, terms such as "millimeter wave" may broadly represent frequencies that can include intermediate band frequencies, frequencies that can be within the range of FR2, FR4, FR4-a, or FR4-1, and / or FR5, or frequencies that can be within the range of the EHF band when used in this specification. It should be understood that the frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be subject to modification, and the technology described in this specification is contemplated to be applicable to those modified frequency ranges.

[0036] As described above, FIG. 1 is provided as one example. Other examples may be different from those described with respect to FIG. 1.

[0037] The deployment of a communication system, such as a 5G NR system, can be configured in multiple ways using various components or constituent parts. In a 5G NR system or network, a network node, network entity, network mobility element, RAN node, core network node, network element, base station, or network device can be implemented in an integrated architecture or a distributed architecture. For example, a base station (among others, such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell), or one or more units (or one or more components) that perform base station functionality can be implemented as an integrated base station (also known as a stand-alone base station or a monolithic base station) or a distributed base station. A "network entity" or "network node" may refer to a distributed base station, or one or more units of a distributed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0038] A centralized base station (e.g., a centralized network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A distributed base station (e.g., a distributed network node) can be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some embodiments, a CU can be implemented within a network node, one or more DUs can be co-located with that CU, or alternatively, one or more other network nodes can be geographically or virtually distributed across the entire network. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as, among other numerous examples, a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0039] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, a distributed base station can be utilized in an IAB network, an open radio access network (such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (also known as a vRAN or cloud radio access network (C-RAN)) to separate base station functionality into one or more individually deployable units, thereby facilitating the scaling of the communication system. The distributed base station can include functionality implemented across two or more units at various physical locations, as well as functionality that is virtually implemented with respect to at least one unit, which can enable flexibility in network design. The various units of the distributed base station can be configured to communicate, either wired or wirelessly, with at least one other unit of the distributed base station.

[0040] FIG. 2 is a diagram showing an exemplary distributed base station architecture 200 according to the present disclosure. The distributed base station architecture 200 can communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more distributed control units (such as the quasi-RTRIC 225 via the E2 link, or the non-RTRIC 215 associated with the Service Management and Orchestration (SMO) framework 205, or both), and may include a CU 210. The CU 210 can communicate with one or more DUs 230 via a corresponding midhaul link such as the F1 interface. Each of the DUs 230 can communicate with one or more RUs 240 via a corresponding fronthaul link. Each of the RUs 240 can communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, the UEs 120 can be served simultaneously by multiple RUs 240.

[0041] Each of the units, including CU210, DU230, RU240, as well as quasi-RT RIC225, non-RT RIC215, and SMO framework 205, may include one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired transmission medium or a wireless transmission medium, or may be coupled to such one or more interfaces. A related processor or controller that provides instructions to each of the units, or to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via the transmission medium. In some embodiments, each of the units includes a wired interface configured to receive or transmit signals via a wired transmission medium to one or more of the other units, and a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive, transmit, or both receive and transmit signals via a wireless transmission medium to one or more of the other units.

[0042] In some aspects, CU210 can host the control functions of one or more upper layers. Such control functions include, among numerous examples, the radio resource control (RRC) function, the packet data convergence protocol (PDCP) function, or the service data adaptation protocol (SDAP) function. Each control function can implement an interface configured to communicate signals with other control functions hosted by CU210. CU210 can be configured to process user plane functionality (e.g., Central Unit-User Plane (CU-UP) functionality), control plane functionality (e.g., Central Unit-Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, CU210 can be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface such as the E1 interface when implemented in an O-RAN configuration. CU210 can be implemented to communicate with DU230 as needed for network control and signaling.

[0043] Each DU230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs240. In some aspects, the DU230 can host one or more of the radio link control (RLC) layer, the MAC layer, and one or more upper physical (PHY) layers, at least partially in accordance with a functional split such as the functional split defined by 3GPP. In some aspects, one or more upper PHY layers can be implemented by one or more modules related to, among other examples, forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation. In some aspects, the DU230 can further host one or more lower PHY layers, such as those implemented by one or more modules related to, among other examples, fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or extraction and filtering of the physical random access channel (PRACH). Each layer (which may sometimes be referred to as a module) can implement an interface configured to communicate signals with other layers (and modules) hosted by the DU230 or with control functions hosted by the CU210.

[0044] Each RU240 can implement lower layer functionality. In some deployments, the RU240 controlled by the DU230 can correspond to a logical node that hosts, among other examples, an RF processing function or hosts lower PHY layer functions such as execution of FFT, execution of iFFT, digital beamforming, or extraction and filtering of PRACH, based on functional splitting (e.g., functional splitting defined by 3GPP), such as lower layer functional splitting. In such an architecture, each RU240 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, the real-time and non-real-time aspects of the control plane communication and user plane communication with the RU240 can be controlled by the corresponding DU230. In some scenarios, this configuration can enable implementation of each DU230 and CU210 in a cloud-based RAN architecture such as a vRAN architecture.

[0045] The SMO framework 205 can be configured to support the RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources related to RAN coverage requirements that can be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) platform 290) in order to perform lifecycle management of the network elements (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CU210, DU230, RU240, non-RT RIC215, and quasi-RT RIC225. In some implementations, the SMO framework 205 can communicate with hardware aspects of 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Furthermore, in some implementations, the SMO framework 205 can communicate directly with each of one or more RU240s via a corresponding O1 interface. The SMO framework 205 may also include a non-RT RIC215 that is configured to support the functionality of the SMO framework 205.

[0046] The non-RT RIC 215 can be configured to include logical functions that enable artificial intelligence / machine learning (AI / ML) workflows, such as non-real-time control and optimization of RAN elements and resources, training and updating of models, or policy-based guidance of applications / functions in the quasi-RT RIC 225. The non-RT RIC 215 can be coupled to the quasi-RT RIC 225 or can also communicate with the quasi-RT RIC 225 (e.g., via an A1 interface). The quasi-RT RIC 225 can be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data collection and actions through an interface connecting the one or more CU 210, the one or more DU 230, or both, and the O-eNB to the quasi-RT RIC 225 (e.g., via an E2 interface).

[0047] In some implementations, the non-RT RIC 215 can receive parameters or external enrichment information from an external server to generate an AI / ML model that will be deployed in the quasi-RT RIC 225. Such information can be utilized by the quasi-RT RIC 225 and can be received in the SMO framework 205 or the non-RT RIC 215 from a non-network data source or from a network function. In some examples, the non-RT RIC 215 or the quasi-RT RIC 225 can be configured to adjust the behavior or performance of the RAN. For example, the non-RT RIC 215 can monitor long-term trends and patterns regarding performance and employ an AI / ML model to execute corrective actions either through corrective actions via the SMO framework 205 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0048] In some aspects, the RU (e.g., RU240 and / or apparatus 1600 of FIG. 16) may include a communication manager 250. As described in more detail elsewhere herein, the communication manager 250 may transmit a message including a list of ordered coordinates corresponding to a plurality of antenna elements within the antenna array of the RU (e.g., to a controller of the RU such as DU230 and / or SMO framework 205), and may receive an indication of one or more low-level endpoints associated with one or more of the activated antenna elements among the plurality of antenna elements (e.g., from the controller). Further or alternatively, the communication manager 250 may perform one or more other operations described herein.

[0049] In some aspects, the controller of RU240 (e.g., DU230, SMO framework 205, and / or apparatus 1700 of FIG. 17) may include a communication manager 260. As described in more detail elsewhere herein, the communication manager 260 may receive a message including a list of ordered coordinates corresponding to a plurality of antenna elements within the antenna array of RU240 (e.g., from RU240), and may transmit an indication of one or more low-level endpoints associated with one or more of the activated antenna elements among the plurality of antenna elements (e.g., to RU240). Further or alternatively, the communication manager 260 may perform one or more other operations described herein.

[0050] As described above, FIG. 2 is provided as one example. Other examples may differ from those described with respect to FIG. 2.

[0051] FIG. 3 is a diagram showing an example 300 of a DU 230 communicating with an RU 240 within a wireless network 100 according to the present disclosure. The DU 230 can be equipped with a set of antennas 334a-334t, such as T antennas (T≥1). The RU 240 can be equipped with a set of antennas 352a-352r, such as R antennas (R≥1). The DU 230 of example 300 includes one or more radio frequency components, such as antenna 334 and modem 354. In some examples, the DU 230 can include an interface, a communication component, or another component that facilitates communication with the RU 240 or another network node. Some DUs 230 may not include radio frequency components that facilitate direct communication with the RU 240. For example, the DU 230 can communicate with the RU 240 over a wired connection (e.g., a wired Ethernet connection).

[0052] In DU230, the transmission processor 320 can receive data destined for RU240 (or a set of RU240s) from the data source 312. The transmission processor 320 can select one or more modulation and coding schemes (MCSs) for RU240. DU230 can process (e.g., encode and modulate) the data for RU240 based at least in part on the selected MCS and can provide data symbols for RU240. The transmission processor 320 can process system information (e.g., semi-static resource partitioning information (SRPI), etc.) and control information (e.g., channel quality indicator (CQI) requests, grants, and / or upper layer signaling, etc.) to provide overhead symbols and control symbols. The transmission processor 320 can generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 332 (e.g., T modems) shown as modems 332a - 332t. For example, each output symbol stream can be provided to the modulator components (shown as MOD) of the modem 332.Each modem 332 can obtain an output sample stream by processing a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component. Each modem 332 can further obtain a downlink signal by processing the output sample stream (e.g., converting to analog, amplifying, filtering, and / or upconverting) using a corresponding modulator component. Modems 332a - 332t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 334 (e.g., T antennas) shown as antennas 334a - 334t.

[0053] In RU240, the set of antennas 352 (shown as antennas 352a - 352r) can receive downlink signals from DU230 and / or other DU230s, and can provide a set of received signals (e.g., R received signals) to a set of modems 354 (e.g., R modems) shown as modems 354a - 354r. For example, each received signal can be provided to a demodulator component (shown as DEMOD) of the modem 354. Each modem 354 can obtain input samples by adjusting (e.g., filtering, amplifying, down - converting, and / or digitizing) the received signals using the corresponding demodulator component. Each modem 354 can apply weights for distributing those input samples across antenna elements (e.g., for OFDM) for (e.g., wireless transmission to the UE). The MIMO detector 356 can distribute the input samples across antenna elements that are logically grouped into a plurality of data streams. The receive processor 358 can process control information from DU230, provide control information and / or input samples for caching to the data sink 360, and provide control information and system information to the controller / processor 380. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. In some embodiments, one or more components of RU240 can be included within the housing 384.

[0054] CU210 may include a communication unit 394, a controller / processor 390, and a memory 392. CU210 may include, for example, one or more devices within the core network. CU210 can communicate with DU230 via the communication unit 394.

[0055] One or more antennas (e.g., antennas 334a - 334t and / or antennas 352a - 352r) can include, among numerous examples, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, or can include them internally. An antenna panel, an antenna group, a set of antenna elements, and / or an antenna array can include one or more antenna elements, a set of coplanar antenna elements, a set of non - coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting components and / or receiving components such as one or more components of FIG. 3, (within a single housing or multiple housings).

[0056] In RU240, the transmission processor 364 can receive and process signals from the antenna elements (e.g., those cached in the data source 362) and control information from the controller / processor 380. Symbols from the transmission processor 364 can be decoded by the TX MIMO processor 366, if applicable, and further processed by the modem 354 (e.g., for DFT - s - OFDM or CP - OFDM) and transmitted to the DU230. In some embodiments, the modem 354 of the RU240 can include a modulator and a demodulator. In some embodiments, the RU240 includes a transceiver. The transceiver can include any combination of the antenna 352, the modem 354, the MIMO detector 356, the reception processor 358, the transmission processor 364, and / or the TX MIMO processor 366. The transceiver can be used by a processor (e.g., the controller / processor 380) and the memory 382 to execute any aspect of the methods described herein (e.g., referring to FIGS. 4 - 14).

[0057] In DU230, signals from RU240 and / or other RU240s are received by antenna 334, processed by modem 332 (e.g., the demodulator component of modem 332 shown as DEMOD), detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain the decoded data and control information received at RU240. Receive processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340. DU230 can include communication unit 344 and can communicate with CU210 via communication unit 344. DU230 can include scheduler 346 for scheduling one or more RU240s for downlink communication and / or uplink communication (e.g., with one or more UEs). In some embodiments, modem 332 of DU230 can include a modulator and a demodulator. In some embodiments, DU230 includes a transceiver. The transceiver can include any combination of antenna 334, modem 332, MIMO detector 336, receive processor 338, transmit processor 320, and / or TX MIMO processor 330. The transceiver can be used by a processor (e.g., controller / processor 340) and memory 342 to perform any aspect of the methods described herein (e.g., with reference to FIGS. 4 - 14).

[0058] The controller / processor 340 of DU230, the controller / processor 380 of RU240, and / or any other component of FIG. 3 can perform one or more techniques associated with configuring the RU antenna element, as described in more detail elsewhere in this specification. For example, the controller / processor 340 of DU230, the controller / processor 380 of RU240, and / or any other component of FIG. 3 can execute or direct the operation of, for example, process 1400 of FIG. 14, process 1500 of FIG. 15, and / or other processes as described herein. Memory 342 and memory 382 can store data and program code, respectively, related to DU230 and RU240. In some embodiments, memory 342 and / or memory 382 can include a non-transitory computer-readable recording medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when the one or more instructions are executed by one or more processors of DU230 and / or RU240 (e.g., directly or after compilation, conversion, and / or interpretation), the one or more processors, RU240, and / or DU230 can be caused to execute or direct the operation of, for example, process 1400 of FIG. 14, process 1500 of FIG. 15, and / or other processes described herein. In some embodiments, executing the instructions can include, among other examples, executing the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions.

[0059] In some aspects, the RU (e.g., RU240 and / or apparatus 1600 of FIG. 16) includes means for transmitting to a controller of the RU (e.g., DU230, SMO framework 205, and / or apparatus 1700 of FIG. 17) a message including a list of ordered coordinates corresponding to a plurality of antenna elements within the antenna array of the RU, and / or means for receiving from the controller an indication of one or more low-level endpoints associated with one or more of the activated antenna elements of the plurality of antenna elements. In some aspects, those means for the RU to perform the operations described herein may include, for example, one or more of communication manager 250, antenna 352, modem 354, MIMO detector 356, receive processor 358, transmit processor 364, TX MIMO processor 366, controller / processor 380, or memory 382.

[0060] In some aspects, a controller of the RU (e.g., DU230, SMO framework 205, and / or apparatus 1700 of FIG. 17) includes means for receiving from the RU (e.g., RU240 and / or apparatus 1600 of FIG. 16) a message including a list of ordered coordinates corresponding to a plurality of antenna elements within the antenna array of the RU, and / or means for transmitting to the RU an indication of one or more low-level endpoints associated with one or more of the activated antenna elements of the plurality of antenna elements. In some aspects, those means for the controller to perform the operations described herein may include, for example, one or more of communication manager 260, transmit processor 320, TX MIMO processor 330, modem 332, antenna 334, MIMO detector 336, receive processor 338, controller / processor 340, memory 342, or scheduler 346.

[0061] The blocks in FIG. 3 are shown as individual components, but the functions described above with respect to these blocks can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to the transmit processor 364, receive processor 358, and / or TX MIMO processor 366 can be executed by the controller / processor 380 or under the control of the controller / processor 380.

[0062] As described above, FIG. 3 is provided as one example. Other examples may be different from those described with respect to FIG. 3.

[0063] A RU controller, such as a DU or SMO framework, receives from the RU a message that conveys information about the RU itself. Thus, the RU can be self-descriptive to the controller. These messages may include a tx array data structure and an rx array data structure that describe the antenna panel (and the antenna elements included thereon) available to the RU for transmission and reception. However, an O-RAN configuration (such as a network configuration supported by the O-RAN Alliance) generally assumes a rectangular antenna panel. In particular, the tx array data structure and the rx array data structure indicate the number of rows, the number of columns, the horizontal spacing, and the vertical spacing. Therefore, the tx array data structure and the rx array data structure cannot indicate a non-rectangular antenna panel or a rectangular antenna panel with irregular spacing.

[0064] Furthermore, an O-RAN configuration (such as a network configuration supported by the O-RAN Alliance) describes the antenna elements of an antenna panel in a static default order. This order is used when an input signal is provided from a controller to the RU (e.g., for transmission OTA). Thus, if the order switches between integrated circuits (ICs) that control the antenna elements, the input signal must be cached. In one example, if the first and third antenna elements in the order are controlled by a first IC and the second and fourth antenna elements in the order are controlled by a second IC, while supplying the input signal associated with the third antenna element to the first IC, the RU caches the input signal associated with the second antenna element and then retrieves the cached input signal and supplies it to the second IC along with the input signal associated with the fourth antenna element. As a result, power, processing resources, and memory are all wasted, and the latency between receiving the input signal and energizing the antenna elements increases.

[0065] Some of the techniques and apparatus described herein enable an RU (e.g., RU240) to report the antenna elements within an antenna panel to a controller (e.g., DU230 and / or SMO framework 205) as a list of ordered coordinates. As a result, RU240 can report a non-rectangular or non-planar antenna array, which can save power for some beamforming configurations. Non-rectangular and non-planar arrays may also be referred to as "freeform arrays".

[0066] Furthermore, the RU240 can report antenna elements in an order other than a static default order (e.g., from left to right and from bottom to top according to a network configuration supported by the O-RAN Alliance). Thus, the RU240 can report antenna elements, for example, in an order according to an IC that controls the antenna elements. As a result, the RU240 can reduce or even eliminate the caching of input signals from the controller in order to save power, processing resources, and memory. Furthermore, the RU240 shortens the latency between the reception of an input signal and the energization of an antenna element.

[0067] FIG. 4 is a diagram showing an embodiment 400 associated with a rectangular array of antenna elements according to the present disclosure. As shown in FIG. 4, the embodiment 400 includes an antenna panel of the RU240 having a plurality of antenna elements. In the embodiment 400, each antenna element has two possible polarization states. Thus, when describing an antenna element to a controller of the RU240 (e.g., the DU230 and / or the SMO framework 205) (e.g., in a tx array data structure or an rx array data structure), the RU240 can report a single polarization state of the antenna element (e.g., +45° or -45° among others), or a composite polarization state of the antenna element.

[0068] As described in connection with FIG. 13, RU240 can represent each antenna element within the antenna panel as an element within an ordered list. For example, RU240 can use an antenna element ordered list data structure that includes data elements (e.g., three-dimensional coordinate data elements such as x, y, and z coordinates, with polarization data elements) that describe the coordinates for each antenna element. The coordinates can be expressed in units of 0.01 millimeters (mm). Alternatively, the coordinates can be expressed in larger units (e.g., 0.1 mm, 0.2 mm, etc.) or smaller units (e.g., 0.005 mm, 0.001 mm, etc.). The coordinates are relative to an origin. In one embodiment, the origin can correspond to the bottom left antenna element 401. In other embodiments, the origin can correspond to a different antenna element or a point that does not coincide with an antenna element. The coordinates can therefore be positive or negative.

[0069] Furthermore, this list shows the antenna elements ordered (e.g., according to antenna element index data elements corresponding to each antenna element). Thus, as shown in FIG. 4, RU240 can report the antenna elements in an order other than left to right and bottom to top. In Example 400, RU240 reports the antenna elements by quadrant. Thus, antenna elements 401, 403, 405, and 407 are reported first and associated with the first quadrant, and antenna elements 409, 411, 413, and 415 are reported next and associated with the second quadrant. Similarly, antenna elements 417, 419, 421, and 423 are reported thereafter and associated with the third quadrant, and antenna elements 425, 427, 429, and 431 are reported next and associated with the fourth quadrant. In some aspects, each quadrant can be associated with an IC that controls the antenna elements within that quadrant.

[0070] By using the techniques as described in relation to FIG. 4, the RU240 can report antenna elements in an order other than a static default order (e.g., from left to right and from bottom to top according to a network configuration supported by the O-RAN Alliance). Thus, the RU240 can report antenna elements, for example, in an order according to an IC that controls the antenna elements. As a result, the RU240 can reduce or even eliminate the caching of input signals from the controller in order to save power, processing resources, and memory. Furthermore, the RU240 shortens the latency between the reception of an input signal and the energization of an antenna element.

[0071] In one embodiment, the controller can activate every other antenna element in the ordered list while saving power in the RU240 and without reducing the aperture of the beam formed by the activated antenna elements. For example, the controller can establish a low-level endpoint (such as described in relation to FIG. 13) to achieve these power savings. As used herein, a "low-level endpoint" refers to a portion of the RU associated with a certain address, whereby an input signal having that address is routed to the portion of the RU associated with that address.

[0072] Furthermore, or alternatively, the controller can activate a subset of the set of antenna elements to save power in the RU240. When activating the subset, the controller can refrain from establishing low-level endpoints associated with the non-activated antenna elements, so as to reduce the throughput from the controller to the RU240 when transmitting weights related to beamforming to the RU240, and thus the controller can save power and processing resources.

[0073] As described above, FIG. 4 is provided as an example. Other examples may differ from those described with respect to FIG. 4.

[0074] FIG. 5 is a diagram showing Example 500 associated with a sunflower-shaped antenna array according to the present disclosure. As shown in FIG. 5, Example 500 includes an antenna panel of RU240 having a plurality of antenna elements.

[0075] In Example 500, the antenna array is non-rectangular. Thus, RU240 is an ordered list including data elements (e.g., three-dimensional coordinate data elements such as x, y, and z coordinates, with polarization data elements) describing the coordinates for each antenna element, and can describe the antenna elements (e.g., in a tx array data structure or an rx array data structure) to a controller of RU240 (e.g., DU230 and / or SMO framework 205). The coordinates are with respect to the origin. In one example, the origin can correspond to the lowest antenna element 501. In other examples, the origin can correspond to a different antenna element or a point that does not coincide with an antenna element.

[0076] Furthermore, this list shows the antenna elements in order (e.g., according to the antenna element index data element corresponding to each antenna element). Thus, as shown in FIG. 5, RU240 can report the antenna elements in the order of antenna element 501, then antenna element 503, then antenna element 505, then antenna element 507, then antenna element 509, and so on. Since RU240 shows the coordinates for each antenna element, RU240 can select any order for reporting the antenna elements.

[0077] FIG. 6 is a diagram showing Example 600 associated with a triangular antenna array according to the present disclosure. As shown in FIG. 6, Example 600 includes an antenna panel of RU240 having a plurality of antenna elements.

[0078] In Example 600, the antenna array is non-rectangular. Thus, RU240 is an ordered list that includes data elements (e.g., three-dimensional coordinate data elements such as x, y, and z coordinates, with polarization data elements) that describe the coordinates for each antenna element, and the controller of RU240 (e.g., DU230 and / or SMO framework 205) can describe the antenna elements (e.g., in a tx array data structure or an rx array data structure). The coordinates are with respect to the origin. In one example, the origin can correspond to the bottom-left antenna element 601. In other examples, the origin can correspond to a different antenna element or a point that does not coincide with an antenna element. The coordinates can therefore be positive or negative.

[0079] Furthermore, this list shows the antenna elements ordered (e.g., according to antenna element index data elements corresponding to each antenna element). Thus, as shown in FIG. 6, RU240 can report the antenna elements in an order other than left-to-right and bottom-to-top. In Example 600, RU240 reports the antenna elements section by section. Thus, antenna elements 601, 603, 605, 607, and 609 are first reported and associated with a first section, and antenna elements 611, 613, 615, 617, 619, and 620 are next reported and associated with a second section. In some aspects, each section can be associated with an IC that controls the antenna elements within that section.

[0080] FIG. 7 is a diagram showing Example 700 associated with a hexagonal antenna array according to the present disclosure. As shown in FIG. 7, Example 700 includes an antenna panel of RU240 having a plurality of antenna elements.

[0081] In Example 700, the antenna array is non-rectangular. Thus, RU240 is an ordered list that includes data elements (e.g., three-dimensional coordinate data elements such as x, y, and z coordinates, with polarization data elements) that describe the coordinates for each antenna element, and the controller of RU240 (e.g., DU230 and / or SMO framework 205) can describe the antenna elements (e.g., in a tx array data structure or an rx array data structure). The coordinates are relative to the origin. In one example, the origin can correspond to the bottom left antenna element 701. In other examples, the origin can correspond to a different antenna element or a point that does not coincide with an antenna element. The coordinates can therefore be positive or negative.

[0082] Furthermore, this list shows the antenna elements ordered (e.g., according to the antenna element index data element corresponding to each antenna element). Thus, as shown in FIG. 7, RU240 can report the antenna elements in the order of antenna element 701, then antenna element 703, then antenna element 705, etc. For example, RU240 may report every other antenna element because RU240 is damaged and / or is conserving power.

[0083] FIG. 8 is a diagram showing Example 800 associated with a circular antenna array according to the present disclosure. As shown in FIG. 8, Example 800 includes an antenna panel of RU240 having a plurality of antenna elements.

[0084] In Example 800, the antenna array is non-rectangular. Thus, RU240 is an ordered list that includes data elements (e.g., three-dimensional coordinate data elements such as x, y, and z coordinates, with polarization data elements) that describe the coordinates for each antenna element, and the controller of RU240 (e.g., DU230 and / or SMO framework 205) can describe the antenna elements (e.g., in a tx array data structure or an rx array data structure). The coordinates are relative to the origin. In one embodiment, the origin can correspond to the lowest antenna element 801. In other embodiments, the origin can correspond to a different antenna element or a point that does not coincide with an antenna element. The coordinates can therefore be positive or negative.

[0085] Furthermore, this list shows the antenna elements in order (e.g., according to the antenna element index data elements corresponding to each antenna element). Thus, as shown in FIG. 8, RU240 can report the antenna elements in the order of antenna element 801, then antenna element 803, then antenna element 805, then antenna element 807, then antenna element 809, and so on. For example, RU240 may report every other antenna element because RU240 is damaged and / or is conserving power.

[0086] FIG. 9 is a diagram showing Example 900 associated with a spherical spiral antenna array according to the present disclosure. As shown in FIG. 9, Example 900 includes an antenna panel of RU240 having a plurality of antenna elements.

[0087] In Example 900, the antenna array is non-rectangular. Thus, RU240 is an ordered list that includes data elements (e.g., three-dimensional coordinate data elements such as x, y, and z coordinates, with polarization data elements) that describe the coordinates for each antenna element. The controller of RU240 (e.g., DU230 and / or SMO framework 205) can describe the antenna elements (e.g., in a tx array data structure or an rx array data structure). The coordinates are relative to an origin. In one example, the origin can correspond to the lowest antenna element 901. In other examples, the origin can correspond to a different antenna element or a point that does not coincide with an antenna element. The coordinates can therefore be positive or negative.

[0088] Furthermore, this list shows the antenna elements in an order (e.g., according to the antenna element index data elements corresponding to each antenna element). Thus, as shown in FIG. 9, RU240 can report the antenna elements in the order of antenna element 901, then antenna element 903, then antenna element 905, then antenna element 907, then antenna element 909, and so on. For example, RU240 can report alternate antenna elements rather than reporting them along a line.

[0089] Therefore, the ordered list described in connection with FIGS. 5-9 enables the description of non-rectangular antenna arrays (and rectangular antenna arrays with irregular spacing). Thus, by reporting the antenna elements as described in connection with FIGS. 5-9, the controller can provide weights for beamforming that use non-rectangular antenna arrays such as those in Examples 500, 600, 700, 800, and 900. As a result, the controller and RU240 can save power for some beamforming configurations by using a non-rectangular antenna panel.

[0090] As described above, FIGS. 5 to 9 are provided as examples. Other examples may be different from those described with respect to FIGS. 5 to 9.

[0091] FIG. 10 is a diagram showing Example 1000 associated with a rectangular antenna array according to the present disclosure. As shown in FIG. 10, Example 1000 includes an antenna panel of RU240 having a plurality of antenna elements. Example 1000 includes 64 antenna elements (indexed from 0 to 63), although other examples may include fewer or additional antenna elements.

[0092] In Example 1000, the antenna array is rectangular. Each cluster of eight antenna elements is controlled by a corresponding IC. In Example 1000, IC1001 controls the antenna elements associated with indices 0, 1, 2, 3, 16, 17, 18, and 19, IC1003 controls the antenna elements associated with indices 4, 5, 6, 7, 20, 21, 22, and 23, IC1005 controls the antenna elements associated with indices 8, 9, 10, 11, 24, 25, 26, and 27, and IC1007 controls the antenna elements associated with indices 12, 13, 14, 15, 28, 29, 30, and 31. Similarly, IC1009 controls the antenna elements associated with indices 32, 33, 34, 35, 48, 49, 50, and 51, IC1011 controls the antenna elements associated with indices 36, 37, 38, 39, 52, 53, 54, and 55, IC1013 controls the antenna elements associated with indices 40, 41, 42, 43, 56, 57, 58, and 59, and IC1015 controls the antenna elements associated with indices 44, 45, 46, 47, 60, 61, 62, and 63. Therefore, RU240 can report the antenna array so that the beamforming weights are received in the following order of antenna element indices: 0, 1, 2, 3, 16, 17, 18, 19; 4, 5, 6, 7, 20, 21, 22, 23; 8, 9, 10, 11, 24, 25, 26, 27; 12, 13, 14, 15, 28, 29, 30, 31; 44, 45, 46, 47, 60, 61, 62, 63; 40, 41, 42, 43, 56, 57, 58, 59; 36, 37, 38, 39, 52, 53, 54, 55; 32, 33, 34, 35, 48, 49, 50, 51. As a result, RU240 can supply the beamforming weights to each IC sequentially (e.g., in the order of IC1001, IC1003, IC1005, IC1007, IC1015, IC1013, IC1011, and IC1009), thereby reducing the caching of the beamforming weights.

[0093] As further shown in FIG. 10, the spacing between antenna elements controlled by the same IC (e.g., the spacing represented by s1 in FIG. 10 between antenna element 2 and antenna element 3, or between antenna element 0 and antenna element 16) can be made smaller than the spacing between antenna elements controlled by different ICs (e.g., the spacing represented by s2 in FIG. 10 between antenna element 3 and antenna element 4, or between antenna element 16 and antenna element 32). Thus, the RU240 can report the coordinates of each antenna element such that its unequal spacing is recognized by the RU240's controller. Other embodiments can use the spacing between antenna elements controlled by the same IC that is larger than the spacing between antenna elements controlled by different ICs.

[0094] FIG. 11 is a diagram showing Example 1100 associated with a triangular antenna array according to the present disclosure. As shown in FIG. 11, Example 1100 includes an antenna panel of the RU240 having a plurality of antenna elements. Example 1100 is similar to Example 1000 of FIG. 10, but is triangular in order to increase the density of the antenna elements.

[0095] As shown in FIG. 11, IC1101 controls the antenna elements associated with indices 0, 1, 2, 3, 16, 17, 18, and 19, IC1103 controls the antenna elements associated with indices 4, 5, 6, 7, 20, 21, 22, and 23, IC1105 controls the antenna elements associated with indices 8, 9, 10, 11, 24, 25, 26, and 27, and IC1107 controls the antenna elements associated with indices 12, 13, 14, 15, 28, 29, 30, and 31. Similarly, IC1109 controls the antenna elements associated with indices 32, 33, 34, 35, 48, 49, 50, and 51, IC1111 controls the antenna elements associated with indices 36, 37, 38, 39, 52, 53, 54, and 55, IC1113 controls the antenna elements associated with indices 40, 41, 42, 43, 56, 57, 58, and 59, and IC1115 controls the antenna elements associated with indices 44, 45, 46, 47, 60, 61, 62, and 63. Therefore, RU240 can report the antenna array so that the beamforming weights are received in the following order of antenna element indices: 0, 1, 2, 3, 16, 17, 18, 19; 4, 5, 6, 7, 20, 21, 22, 23; 8, 9, 10, 11, 24, 25, 26, 27; 12, 13, 14, 15, 28, 29, 30, 31; 44, 45, 46, 47, 60, 61, 62, 63; 40, 41, 42, 43, 56, 57, 58, 59; 36, 37, 38, 39, 52, 53, 54, 55; 32, 33, 34, 35, 48, 49, 50, 51. As a result, RU240 can supply the beamforming weights to each IC sequentially (e.g., in the order of IC1101, IC1103, IC1105, IC1107, IC1115, IC1113, IC1111, and IC1109), thus reducing the caching of the beamforming weights.

[0096] FIG. 12 is a diagram showing Example 1200 associated with a circular antenna array according to the present disclosure. As shown in FIG. 12, Example 1200 includes an antenna panel of RU240 having a plurality of antenna elements. Similar to Example 1000 and Example 1100, RU240 can report the coordinates of the antenna elements in an order corresponding to the IC that controls the antenna elements.

[0097] As described above, FIGS. 10 to 12 are provided as examples. Other examples may be different from those described with respect to FIGS. 10 to 12.

[0098] FIG. 13 is a diagram showing Example 1300 associated with configuring RU antenna elements using an ordered list according to the present disclosure. As shown in FIG. 13, RU240 and the controller of RU240 (for example, DU230) can communicate with each other (for example, on the front hole link as described in relation to FIG. 2). Although DU230 is described as the controller, other examples may include an SMO provider (for example, SMO framework 205) that communicates with RU240 (for example, on the O1 interface as described in relation to FIG. 2) as the controller.

[0099] As indicated by reference numeral 1305, RU240 can transmit and DU230 can receive a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the antenna array of RU240. For example, the ordered list can be as described in relation to FIG. 4 or FIG. 10 for a rectangular antenna array, or as described in relation to FIGS. 5 to 9 or FIGS. 11 to 12 for a non-rectangular antenna array.

[0100] RU240 can send its message as part of self-description during the startup procedure. Thus, the message can be sent on the management plane (M-plane) between RU240 and DU230. Alternatively, RU240 can also send the message on the control plane (C-plane) between RU240 and DU230. Alternatively, RU240 can also send the message on a new type of plane between RU240 and DU230.

[0101] In addition to the list of ordered coordinates, RU240 can indicate a normal vector (e.g., using a normal vector direction data structure that can indicate an azimuth angle and / or a zenith angle). The normal vector can indicate the outward direction of RF radiation from the antenna array. In one embodiment, the normal vector can correspond to the lower left antenna element. In other embodiments, the normal vector can correspond to different antenna elements or points that do not coincide with the antenna elements. Some embodiments may include a single normal vector, and other embodiments may include a set of normal vectors corresponding to a set of antenna elements within the antenna array. For example, a normal vector list index data structure can indicate the index of the antenna element to which those normal vectors correspond.

[0102] Furthermore, or alternatively, RU240 can indicate an antenna shape associated with the antenna array (e.g., from a plurality of possible antenna shapes within an enumerated list). Examples of possible antenna shapes include, among numerous examples, an ordered rectangular shape (e.g., for a rectangular array not using the standard ordering of O-RAN as described in relation to FIG. 10), an offset rectangular shape (e.g., for a rectangular array with non-uniform spacing as described in relation to FIG. 10), a regular triangular shape (e.g., as described in relation to FIGS. 6 and 11), a regular hexagonal shape (e.g., as described in relation to FIG. 7), a regular circular shape (e.g., as described in relation to FIGS. 8 and 12), or an irregular planar shape (e.g., for an irregular shape).

[0103] As indicated by reference numeral 1310, DU230 can perform setup of endpoints based on a list of ordered coordinates. For example, DU230 can map endpoints described by a low-level tx endpoint data structure and a low-level rx endpoint data structure to antenna elements indicated within a message (e.g., in a tx array data structure and an rx array data structure). An endpoint can represent a single antenna element, or a subset of antenna elements, from a set of antenna elements including a plurality of antenna elements. Thus, DU230 can use those endpoints to transmit an input signal for transmission OTA using those antenna elements (e.g., using weighted beamforming as described in relation to reference numeral 1325) to RU240.

[0104] As indicated by reference number 1315, the DU230 can send and the RU240 can receive an indication of one or more low-level endpoints associated with one or more activated antenna elements among a plurality of antenna elements. For example, as described above, the DU230 can send a low-level tx endpoint data structure and a low-level rx endpoint data structure.

[0105] Furthermore, the DU230 can configure carriers (e.g., component carriers (CCs)) for use by the activated antenna elements. For example, the DU230 can activate a tx array carrier data structure and an rx array carrier data structure and associate them with a low-level link that terminates at a low-level endpoint associated with the activated antenna elements.

[0106] Furthermore, as indicated by reference number 1320, the DU230 can determine beamforming weights based on a list of ordered coordinates. In some aspects, the DU230 can use beamforming of a predefined beam, weight-based dynamic beamforming (e.g., in the frequency domain, in the time domain, or hybrid beamforming in both the time domain and the frequency domain), attribute-based dynamic beamforming, or channel information-based beamforming.

[0107] As indicated by reference number 1325, the DU230 can transmit and the RU240 can receive a beamforming configuration associated with the activated antenna element. For example, the beamforming configuration can indicate beamforming weights determined based on a model applied by the DU230 (e.g., a beamforming model selected by the DU230). The DU230 can transmit an updated beamforming configuration (e.g., regarding dynamic beamforming) periodically, or can also transmit a static beamforming configuration (e.g., regarding beamforming of a default beam).

[0108] In some aspects, the indication of the low-level endpoint can be a static configuration that is not changed during active use of the carrier. For example, the low-level endpoint can be established in an M-plane configuration that is fixed during use of the carrier. Alternatively, this indication can be a dynamic configuration that is changed in real time during use of the activated antenna element. For example, the low-level endpoint can be established in a C-plane configuration that can be modified during use of the carrier.

[0109] For example, as indicated by reference number 1330, the DU230 can modify the low-level endpoint (e.g., by increasing or decreasing the amount of activated antenna elements). As indicated by reference number 1335, the DU230 can transmit and the RU240 can receive an updated indication.

[0110] By using the techniques as described in relation to FIG. 13, the RU240 reports multiple antenna elements in an order other than the static default order (e.g., from left to right and from bottom to top according to the network configuration supported by the O-RAN Alliance). As a result, the RU240 can reduce or even eliminate the caching of the input signal from the controller in order to save power, processing resources, and memory. Furthermore, the RU240 shortens the latency between the reception of the input signal and the energization of the antenna elements.

[0111] Furthermore, in some aspects, the DU230 can configure low-level endpoints to reduce the throughput from the DU230 to the RU240. For example, the DU230 can refrain from transmitting beamforming weights that will anyway be discarded by the RU240 (since the antenna elements corresponding to those weights are inactive), thereby saving power and processing resources and shortening the latency.

[0112] As described above, FIG. 13 is provided as one example. Other examples may be different from those described in relation to FIG. 13.

[0113] FIG. 14 is a diagram showing an exemplary process 1400, which is executed by, for example, an RU according to the present disclosure. The exemplary process 1400 is an example in which an RU (e.g., RU240 and / or the device 1600 in FIG. 16) executes operations associated with configuring RU antenna elements.

[0114] As shown in FIG. 14, in some aspects, process 1400 may include transmitting, to a RU controller (e.g., DU 230, SMO framework 205, and / or device 1700 of FIG. 17), a message that includes a list of ordered coordinates corresponding to a plurality of antenna elements within the RU's antenna array (block 1410). For example, the RU may (e.g., using communication manager 250 and / or transmission component 1604 shown in FIG. 16) transmit, as described herein, a message that includes a list of ordered coordinates corresponding to a plurality of antenna elements within the RU's antenna array, to the RU's controller.

[0115] As further shown in FIG. 14, in some aspects, process 1400 may include receiving, from the controller, an indication of one or more low-level endpoints associated with one or more of the activated antenna elements among the plurality of antenna elements (block 1420). For example, the RU may (e.g., using communication manager 250 and / or reception component 1602 shown in FIG. 16) receive, as described herein, an indication of one or more low-level endpoints associated with one or more of the activated antenna elements among the plurality of antenna elements, from the controller.

[0116] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere in this document.

[0117] In a first aspect, the indication is a static configuration that is not changed during active use of the carrier.

[0118] In a second aspect, alone or in combination with the first aspect, the indication is a dynamic configuration that is changed in real time during use of one or more of the activated antenna elements.

[0119] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1400 includes receiving, from a controller (e.g., using communication manager 250 and / or receive component 1602), a beamforming configuration associated with one or more active antenna elements.

[0120] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the antenna array is non-rectangular.

[0121] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the antenna array is rectangular and the ordered list indicates the plurality of antenna elements in an order other than left-to-right and bottom-to-top.

[0122] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the message and the instruction are associated with the M-plane between the RU and the controller.

[0123] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the message and the instruction are associated with the C-plane between the RU and the controller.

[0124] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the order of the ordered list is based on an IC that controls the plurality of antenna elements.

[0125] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the plurality of antenna elements are clustered according to an IC.

[0126] FIG. 14 shows exemplary blocks of process 1400, but in some aspects, process 1400 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 14. Further, or alternatively, two or more of the blocks of process 1400 may be executed in parallel.

[0127] FIG. 15 is a diagram showing an exemplary process 1500 executed, for example, by a RU controller according to the present disclosure. The exemplary process 1500 is an example in which a controller (e.g., DU230, SMO framework 205, and / or device 1700 of FIG. 17) performs operations associated with configuring RU antenna elements.

[0128] As shown in FIG. 15, in some aspects, process 1500 may include receiving, from a RU (e.g., RU240 and / or device 1600 of FIG. 16), a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the RU's antenna array (block 1510). For example, the controller can receive, as described herein, a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the RU's antenna array, from the RU (e.g., using communication manager 260 and / or receive component 1702 shown in FIG. 17).

[0129] As further shown in FIG. 15, in some aspects, process 1500 may include sending to the RU one or more low-level endpoint indications associated with one or more of the activated antenna elements among the plurality of antenna elements (block 1520). For example, the controller can send, as described herein, one or more low-level endpoint indications associated with one or more of the activated antenna elements among the plurality of antenna elements, to the RU (e.g., using communication manager 260 and / or transmit component 1704 shown in FIG. 17).

[0130] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects, described below and / or in connection with one or more other processes described elsewhere in this specification.

[0131] In a first aspect, the indication includes a static configuration that is not changed during active use of the carrier.

[0132] In a second aspect, alone or in combination with the first aspect, the indication includes a dynamic configuration that is changed in real time during use of one or more activated antenna elements.

[0133] In a third aspect, alone or in combination with one or more of the first and second aspects, Process 1500 includes transmitting a beamforming configuration associated with one or more activated antenna elements to the RU (e.g., using communication manager 260 and / or transmission component 1704).

[0134] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the antenna array is non-rectangular.

[0135] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the antenna array is rectangular and the ordered list indicates the plurality of antenna elements in an order other than from left to right and from bottom to top.

[0136] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the message and the indication are associated with the M plane between the RU and the controller.

[0137] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, messages and instructions are associated with the C-plane between the RU and the controller.

[0138] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the controller is a DU or an SMO provider.

[0139] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the order of the ordered list is based on an IC that controls a plurality of antenna elements.

[0140] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the plurality of antenna elements are clustered according to the IC.

[0141] FIG. 15 shows exemplary blocks of process 1500, but in some aspects, process 1500 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 15. Further, or alternatively, two or more of the blocks of process 1500 may be executed in parallel.

[0142] FIG. 16 is a diagram of an exemplary apparatus 1600 for wireless communication according to the present disclosure. The apparatus 1600 may be a RU or may include the RU. In some aspects, the apparatus 1600 includes a receiving component 1602 and a transmitting component 1604 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1600 can communicate with another apparatus 1606 (such as a DU, an SMO provider, or another wireless configured device) using the receiving component 1602 and the transmitting component 1604. Further shown, the apparatus 1600 may include a communication manager 250. The communication manager 250 may include, among other examples, a beamforming component 1608 and / or a caching component 1610.

[0143] In some aspects, the apparatus 1600 can be configured to perform one or more operations described herein in connection with FIGS. 4-13. Further or alternatively, the apparatus 1600 can be configured to perform one or more processes described herein, such as the process 1400 of FIG. 14, or a combination thereof. In some aspects, the apparatus 1600 and / or one or more components shown in FIG. 16 can include one or more components of the RU described in connection with FIG. 3. Further or alternatively, one or more components shown in FIG. 16 can be implemented within one or more components described in connection with FIG. 3. Further or alternatively, one or more components of a set of components can be implemented as software stored at least partially in memory. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable recording medium and executable by a controller or processor to perform the function or operation of the component.

[0144] The receiving component 1602 can receive communications such as an input signal, control information, or a combination thereof from the device 1606. The receiving component 1602 can provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 can perform signal processing (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and can provide those processed signals to one or more other components of the device 1600. In some aspects, the receiving component 1602 can include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the RU described in connection with FIG. 3.

[0145] The transmitting component 1604 can transmit communications such as control information, data communications, or a combination thereof to the device 1606. In some aspects, one or more other components of the device 1600 can generate communications and can provide those generated communications to the transmitting component 1604 for transmission to the device 1606. In some aspects, the transmitting component 1604 can perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communications and can transmit those processed signals to the device 1606. In some aspects, the transmitting component 1604 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the RU described in connection with FIG. 3. In some aspects, the transmitting component 1604 can be co-located with the receiving component 1602 within a transceiver.

[0146] In some aspects, the transmission component 1604 can send a message including a list of ordered coordinates corresponding to a plurality of antenna elements in the antenna array of the device 1600 to, for example, the device 1606 (such as a controller of the device 1600). Accordingly, the reception component 1602 can receive an indication of one or more low-level endpoints associated with one or more of the activated antenna elements among the plurality of antenna elements, for example, from the device 1606. Therefore, the ordered list indicates the plurality of antenna elements in an order such that the input signal can be directly supplied to the IC associated with one or more of the activated antenna elements without caching to rearrange the order of the input signals. Thus, the caching component 1610 can refrain from caching the input signals received from the device 1606.

[0147] In some aspects, the reception component 1602 can receive a beamforming configuration associated with one or more of the activated antenna elements, for example, from the device 1606. Accordingly, the beamforming component 1608 can apply weights to the input signals received from the device 1606 to form a beam using one or more of the activated antenna elements.

[0148] The number and configuration of the components shown in FIG. 16 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently from those shown in FIG. 16. Furthermore, two or more of the components shown in FIG. 16 can be implemented within a single component, or a single component shown in FIG. 16 can be implemented as a plurality of distributed components. Furthermore, alternatively, the set of (one or more) components shown in FIG. 16 can perform one or more functions described as being performed by another set of components shown in FIG. 16.

[0149] FIG. 17 is a diagram of an exemplary apparatus 1700 for wireless communication according to the present disclosure. The apparatus 1700 may be a controller of an RU, or the RU controller may include the apparatus 1700. In some aspects, the apparatus 1700 includes a receiving component 1702 and a transmitting component 1704 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1700 can use the receiving component 1702 and the transmitting component 1704 to communicate with another apparatus 1706 (such as an RU or another wireless configured device). Further shown, the apparatus 1700 may include a communication manager 260. The communication manager 260 may include one or more of, among other examples, an endpoint setting component 1708 and / or a beamforming component 1710.

[0150] In some aspects, the apparatus 1700 can be configured to perform one or more operations described herein in connection with FIGS. 4 - 13. Further or alternatively, the apparatus 1700 can be configured to perform one or more processes described herein, such as the process 1500 of FIG. 15, or a combination thereof. In some aspects, the apparatus 1700 and / or one or more components shown in FIG. 17 can include one or more components of the DU described in connection with FIG. 3. Further or alternatively, one or more components shown in FIG. 17 can be implemented within one or more components described in connection with FIG. 3. Further or alternatively, one or more components of a set of components can be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non - transitory computer - readable recording medium and executable by a controller or processor to perform the function or operation of that component.

[0151] The receiving component 1702 can receive communications such as an input signal, control information, or a combination thereof from the device 1706. The receiving component 1702 can provide the received communications to one or more other components of the device 1700. In some aspects, the receiving component 1702 can perform signal processing (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding) on the received communications, and can provide those processed signals to one or more other components of the device 1700. In some aspects, the receiving component 1702 can include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the DU described in connection with FIG. 3.

[0152] The transmitting component 1704 can transmit communications such as an input signal, control information, or a combination thereof to the device 1706. In some aspects, one or more other components of the device 1700 can generate the communications, and can provide those generated communications to the transmitting component 1704 for transmission to the device 1706. In some aspects, the transmitting component 1704 can perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communications, and can transmit those processed signals to the device 1706. In some aspects, the transmitting component 1704 can include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the DU described in connection with FIG. 3. In some aspects, the transmitting component 1704 can be co-located with the receiving component 1702 within a transceiver.

[0153] In some aspects, the receiving component 1702 can receive a message (from device 1706, e.g., RU) that includes a list of ordered coordinates corresponding to a plurality of antenna elements within the antenna array of device 1706. Accordingly, the transmitting component 1704 can transmit an indication of one or more low-level endpoints associated with one or more of the activated antenna elements among the plurality of antenna elements (to device 1706, e.g.). For example, the endpoint setting component 1708 can assign the antenna elements indicated in the ordered list to corresponding low-level endpoints, and thereby transmit from device 1700 to device 1706 to distribute an input signal according to those low-level endpoints.

[0154] In some aspects, the transmitting component 1704 can transmit a beamforming configuration associated with one or more of the activated antenna elements (to device 1706, e.g.). For example, the beamforming component 1710 can calculate weights for applying to an input signal from device 1700 so that device 1706 forms a beam using one or more of the activated antenna elements.

[0155] The number and arrangement of components shown in FIG. 17 are provided as one example. In practice, there may be additional components, fewer components, different components, or components arranged differently than those shown in FIG. 17. Further, two or more components shown in FIG. 17 can be implemented within a single component, or a single component shown in FIG. 17 can be implemented as a plurality of distributed components. Further, or alternatively, a set of (one or more) components shown in FIG. 17 can perform one or more functions described as being performed by another set of components shown in FIG. 17.

[0156] The following provides an overview of some aspects of the present disclosure.

[0157] Aspect 1: A method for wireless configuration, executed by a radio unit (RU), comprising transmitting a message including a list of ordered coordinates corresponding to a plurality of antenna elements in an antenna array of the RU to a controller of the RU; and receiving, from the controller, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0158] Aspect 2: The method of Aspect 1, wherein the indication includes a static configuration that is not changed during active use of the carrier.

[0159] Aspect 3: The method of Aspect 1, wherein the indication includes a dynamic configuration that is changed in real time during use of one or more of the activated antenna elements.

[0160] Aspect 4: The method according to any one of Aspects 1 to 3, further comprising receiving, from the controller, a beamforming configuration associated with one or more of the activated antenna elements.

[0161] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the antenna array is non-rectangular.

[0162] Aspect 6: The method according to any one of Aspects 1 to 4, wherein the antenna array is rectangular and the ordered list indicates the plurality of antenna elements in an order other than from left to right and from bottom to top.

[0163] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the message and the indication are associated with a management plane between the RU and the controller.

[0164] Aspect 8: The method according to any one of Aspects 1 to 6, wherein the message and the indication are associated with a control plane between the RU and the controller.

[0165] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the order of the ordered list is based on integrated circuits (ICs) that control a plurality of antenna elements.

[0166] Aspect 10: The method of Aspect 9, wherein a plurality of antenna elements are clustered according to an IC.

[0167] Aspect 11: A method for wireless configuration, executed by a controller of a radio unit (RU), the method including receiving, from the RU, a message including an ordered list of coordinates corresponding to a plurality of antenna elements in an antenna array of the RU, and transmitting, to the RU, an indication of one or more low-level endpoints associated with one or more of the plurality of antenna elements that are activated.

[0168] Aspect 12: The method of Aspect 11, wherein the indication includes a static configuration that is not changed during active use of the carrier.

[0169] Aspect 13: The method of Aspect 11, wherein the indication includes a dynamic configuration that is changed in real time during use of one or more activated antenna elements.

[0170] Aspect 14: The method according to any one of Aspects 11 to 13, further including transmitting, to the RU, a beamforming configuration associated with one or more activated antenna elements.

[0171] Aspect 15: The method according to any one of Aspects 11 to 14, wherein the antenna array is non-rectangular.

[0172] Aspect 16: The method according to any one of Aspects 11 to 14, wherein the antenna array is rectangular and the ordered list indicates a plurality of antenna elements in an order other than from left to right and from bottom to top.

[0173] Aspect 17: The method according to any one of Aspects 11 to 16, wherein the message and the indication are associated with a management plane between the RU and the controller.

[0174] Aspect 18: Any of the methods of Aspects 11 - 16, wherein messages and instructions are associated with the control plane between the RU and the controller.

[0175] Aspect 19: Any of the methods of Aspects 11 - 18, wherein the controller includes a distributed unit or a service management and orchestration provider.

[0176] Aspect 20: Any of the methods of Aspects 11 - 19, wherein the order of the ordered list is based on integrated circuits (ICs) that control a plurality of antenna elements.

[0177] Aspect 21: The method of Aspect 20, wherein a plurality of antenna elements are clustered according to an IC.

[0178] Aspect 22: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to perform one or more of the methods of Aspects 1 - 10.

[0179] Aspect 23: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein the one or more processors are configured to perform one or more of the methods of Aspects 1 - 10.

[0180] Aspect 24: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of Aspects 1 - 10.

[0181] Aspect 25: A non - transitory computer - readable recording medium storing code for wireless communication, wherein the code includes instructions executable by a processor to perform one or more of the methods of Aspects 1 - 10.

[0182] Aspect 26: A non-transitory computer-readable recording medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions, wherein when the one or more instructions are executed by one or more processors of a device, the device is caused to execute one or more of the methods of Aspects 1-10.

[0183] Aspect 27: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to execute one or more of the methods of Aspects 11-21.

[0184] Aspect 28: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein the one or more processors are configured to execute one or more of the methods of Aspects 11-21.

[0185] Aspect 29: An apparatus for wireless communication comprising at least one means for executing one or more of the methods of Aspects 11-21.

[0186] Aspect 30: A non-transitory computer-readable recording medium storing code for wireless communication, the code including instructions executable by a processor to execute one or more of the methods of Aspects 11-21.

[0187] Aspect 31: A non-transitory computer-readable recording medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions, wherein when the one or more instructions are executed by one or more processors of a device, the device is caused to execute one or more of the methods of Aspects 11-21.

[0188] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be added in light of the foregoing disclosure, or can be acquired from practice of the aspects.

[0189] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" is to be broadly construed to mean, among numerous examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, regardless of whether referred to by the name software, firmware, middleware, microcode, hardware description language, or other name. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods does not limit the aspects. Therefore, those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein, and thus the operation and behavior of the systems and / or methods are described herein without reference to specific software code.

[0190] As used herein, "meeting a threshold" may, depending on the context, refer to a value being greater than a threshold, being greater than or equal to a threshold, being less than a threshold, being less than or equal to a threshold, being equal to a threshold, not being equal to a threshold, and the like.

[0191] Even if a particular combination of features is recited in the claims and / or disclosed herein, such combinations are not intended to limit the disclosure in various aspects. Many of these features can be combined in ways not specifically recited in the claims and / or not disclosed herein. The disclosure in various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" includes a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination having multiple identical elements (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other arrangement of a, b, and c).

[0192] None of the elements, acts, or instructions used in this specification should be construed as indispensable or essential unless expressly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Furthermore, as used in this specification, the article "the" is intended to include one or more items referred to in relation to that article "the" and may be used interchangeably with "one or more". Additionally, as used in this specification, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar words are used. Also, as used in this specification, terms such as "has", "have", "having", etc. are also intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Moreover, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified. Also, as used in this specification, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and / or" except when otherwise specified (e.g., when used in combination with "either" or "only one of").

Claims

1. A device for wireless configuration in a wireless unit (RU), Memory and The memory is coupled to one or more processors, and the one or more processors are Sending a message to the controller of the RU containing an ordered list of coordinates corresponding to a plurality of antenna elements in the antenna array of the RU, wherein the ordered list of coordinates includes, for each of the plurality of antenna elements, its respective three-dimensional coordinate data element and its respective polarization data element. The system is configured to receive instructions from the controller for one or more low-level endpoints associated with one or more activated antenna elements among the plurality of antenna elements. Device.

2. The apparatus according to claim 1, wherein the instructions include a static configuration that is not changed during active use of the carrier.

3. The apparatus according to claim 1, comprising a dynamic configuration in which the instructions are changed in real time while the one or more activated antenna elements are in use.

4. The aforementioned one or more processors The apparatus according to claim 1, further configured to receive beamforming configurations associated with the one or more activated antenna elements from the controller.

5. The apparatus according to claim 1, wherein the antenna array is non-rectangular in shape.

6. The apparatus according to claim 1, wherein the antenna array is rectangular in shape, and the ordered list of coordinates indicates the plurality of antenna elements in an order other than left to right and bottom to top.

7. The aforementioned message and instruction are transmitted to the management plane between the RU and the controller, or The apparatus according to claim 1, which is associated with a control plane between the RU and the controller.

8. A device for wireless configuration in a controller of a wireless unit (RU), Memory and The system comprises one or more processors coupled to the memory, and the one or more processors are Receiving a message from the RU containing an ordered list of coordinates corresponding to multiple antenna elements in the antenna array of the RU, wherein the ordered list of coordinates includes, for each of the multiple antenna elements, its respective three-dimensional coordinate data element and its respective polarization data element. The RU is configured to transmit instructions for one or more low-level endpoints associated with one or more activated antenna elements among the plurality of antenna elements. Device.

9. The apparatus according to claim 8, wherein the controller includes a distributed unit or a service management and orchestration provider.

10. A method of wireless configuration performed by a wireless unit (RU), A step of transmitting a message to the controller of the RU, the message containing an ordered list of coordinates corresponding to a plurality of antenna elements in the antenna array of the RU, wherein the ordered list of coordinates includes, for each of the plurality of antenna elements, its respective three-dimensional coordinate data element and its respective polarization data element. A method comprising the step of receiving instructions from the controller for one or more low-level endpoints associated with one or more activated antenna elements among the plurality of antenna elements.

11. The further step includes receiving a beamforming configuration associated with one or more activated antenna elements from the controller. The method according to claim 10.

12. The method according to claim 10, wherein the antenna array is non-rectangular in shape.

13. The method according to claim 10, wherein the antenna array is rectangular in shape, and the ordered list of coordinates indicates the plurality of antenna elements in an order other than left to right and bottom to top.

14. The aforementioned message and instruction are transmitted to the management plane between the RU and the controller, or The method according to claim 10, which is associated with a control plane between the RU and the controller.

15. A method of wireless configuration performed by a controller of a wireless unit (RU), The step of receiving a message from the RU including an ordered list of coordinates corresponding to a plurality of antenna elements in the antenna array of the RU, wherein the ordered list of coordinates includes, for each of the plurality of antenna elements, a respective three-dimensional coordinate data element and a respective polarization data element. A method comprising the step of transmitting instructions for one or more low-level endpoints associated with one or more activated antenna elements among the plurality of antenna elements to the RU.

Images