Carrier configuration section types and analog beamforming extensions

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a radio unit (RU) can receive, from a distributed unit (DU), a control plane message associated with a zone type dedicated to information that applies to all resource blocks and spatial layers in a carrier or band sector group, wherein the control plane message includes information that applies to all resource blocks and spatial layers in the indicated carrier or band sector group. The RU can perform, based at least in part on the information included in the control plane message, beamforming for one or more communications with a user equipment (UE). Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. nonprovisional patent application No. 17 / 445,563, filed on August 20, 2021, entitled “CARRIER CONFIGURATIONSECTION TYPE AND ANALOG BEAMFORMING EXTENSION,” which is expressly incorporated herein by reference. Technical Field

[0003] In summary, various aspects of this disclosure relate to wireless communications and techniques and apparatus for carrier configuration segment types and analog beamforming extensions in Open Radio Access Networks (O-RAN). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems can utilize multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit 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 / Improved LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communication for user equipment (UE) or multiple UEs. UEs may communicate with base stations via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the base station.

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different UEs to communicate at the city, national, regional, and / or global levels. New Radio (NR) (which can also be referred to as 5G) is an enhancement set to the LTE mobile standard released by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and using CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation to better support mobile broadband internet access. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR, and other radio access technologies remain useful. Attached Figure Description

[0007] To gain a more detailed understanding of the features described above in this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are shown in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit its scope, as the specification may allow for other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0008] Figure 1 This is a schematic diagram illustrating an example of a wireless network according to this disclosure.

[0009] Figure 2 This is a schematic diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0010] Figure 3 This is a schematic diagram illustrating an example of a time slot format according to this disclosure.

[0011] Figure 4 This is a schematic diagram illustrating an example of an Open Radio Access Network (O-RAN) architecture according to this disclosure.

[0012] Figure 5 This is a schematic diagram illustrating an example of a transmission header for a message in O-RAN according to this disclosure.

[0013] Figure 6-8 This is a schematic diagram illustrating an example of how carrier configuration segment types and analog beamforming spreads in O-RAN are associated with the present disclosure.

[0014] Figure 9-12 This is a schematic diagram illustrating an example process associated with carrier configuration segment type and analog beamforming spread in O-RAN according to the present disclosure.

[0015] Figures 13-14 This is a schematic diagram of an example device for wireless communication according to the present disclosure. Summary of the Invention

[0016] Some aspects described herein relate to a radio unit (RU) for wireless communication. The radio unit may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive from a distributed unit (DU) a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in an indicated carrier or band sector group. The one or more processors may be configured to perform beamforming for communication with one or more user equipment (UE) devices, at least in part, based on the information included in the control plane message.

[0017] Some aspects described herein relate to a radio unit (RU) for wireless communication. The radio unit may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive control plane messages from a radio unit (DU) including analog beamforming information applied to all resource blocks and spatial layers of one or more carriers. The one or more processors may be configured to perform beamforming for one or more communications with a user equipment (UE) based at least in part on the analog beamforming information.

[0018] Some aspects described herein relate to a method for wireless communication performed by a RU. The method may include receiving from a DU a control plane message associated with a segment type dedicated to information applied to all resource blocks and spatial layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and spatial layers in an indicated carrier or band sector group. The method may include performing beamforming for communication with one or more UEs based at least in part on the information included in the control plane message.

[0019] Some aspects described herein relate to a method for wireless communication performed by a RU. The method may include receiving control plane messages from a DU that include analog beamforming information applied to all resource blocks and spatial layers of one or more carriers. The method may include performing beamforming for communication with one or more UEs based at least in part on the analog beamforming information.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication performed by an RU. When executed by one or more processors of the RU, the set of instructions enables the RU to receive from a DU control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in the indicated carrier or band sector group. When executed by one or more processors of the RU, the set of instructions enables the RU to perform beamforming for communication with one or more UEs, at least in part, based on the information included in the control plane message.

[0021] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication performed by a RU. When executed by one or more processors of the RU, the set of instructions enables the RU to receive control plane messages from a DU that include analog beamforming information applied to all resource blocks and spatial layers of one or more carriers. When executed by one or more processors of the RU, the set of instructions enables the RU to perform beamforming for communication with one or more UEs, at least in part, based on the analog beamforming information.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include units for receiving from a DU a control plane message associated with a segment type dedicated to information applied to all resource blocks and spatial layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and spatial layers in an indicated carrier or band sector group. The apparatus may include units for performing beamforming for communication with one or more UEs, at least in part based on the information included in the control plane message.

[0023] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include units for receiving control plane messages from a DU that include analog beamforming information applied to all resource blocks and space layers of one or more carriers. The apparatus may also include units for performing beamforming for communication with one or more UEs, at least in part, based on the analog beamforming information.

[0024] The aspects generally include, as fully described herein with reference to the accompanying drawings and description, and as illustrated by the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems.

[0025] The foregoing has provided a fairly broad overview of the features and technical advantages of examples according to this disclosure in order to better understand the following specific embodiments. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and their associated advantages will be better understood when considered in conjunction with the accompanying drawings, based on the following description. Each of the accompanying drawings is provided for illustrative and descriptive purposes and is not intended to limit the scope of the claims.

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

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

[0028] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings, through various frames, 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 an element is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0030] Figure 1This is a diagram illustrating an example of a wireless network 100 according to this disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. Base station 110 is the entity that communicates with UE 120. Base station 110 (sometimes referred to as BS) 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, and / or a Transmit / Receive Point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term “cell” can refer to the coverage area of ​​base station 110 and / or the base station subsystem serving that coverage area, depending on the context in which the term is used.

[0031] Base station 110 can provide communication coverage for macro cells, pico cells, femtocells, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UE 120 associated with a femtocell (e.g., UE 120 in a Closed User Group (CSG)). Base station 110 for macro cells can be referred to as a macro base station. Base station 110 for pico cells can be referred to as a pico base station. Base station 110 for femtocells can be referred to as a femtocell base station or a home base station. Figure 1 In the example shown, BS110a can be a macro base station for macro cell 102a, BS110b can be a pico base station for pico cell 102b, and BS110c can be a femto base station for femto cell 102c. A base station can support one or more (e.g., three) cells.

[0032] In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of a mobile base station 110 (e.g., a mobile base station). In some examples, base stations 110 may be interconnected with each other and / or with one or more other base stations 110 or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0033] Wireless network 100 may include one or more relay stations. A relay station is an entity that receives data transmissions from an upstream station (e.g., base station 110 or UE 120) and sends data transmissions to a downstream station (e.g., UE 120 or base station 110). A relay station may be a UE 120 capable of relaying transmissions to other UEs 120. Figure 1 In the example shown, BS110d (e.g., a relay base station) can communicate with BS110a (e.g., a macro base station) and UE 120d to facilitate communication between BS110a and UE 120d. The base station 110 for relay communication can also be referred to as a relay station, relay base station, relay, etc.

[0034] Wireless network 100 can be a heterogeneous network comprising different types of base stations 110 (such as macro base stations, pico base stations, femto base stations, relay base stations, etc.). These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro base stations may have higher transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0035] Network controller 130 can be coupled to or communicate with a group of base stations 110, and can provide coordination and control for these base stations 110. Network controller 130 can communicate with base stations 110 via a backhaul communication link. Base stations 110 can also communicate directly or indirectly with each other via a wireless or wired backhaul link.

[0036] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or 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 GPS device, and / or any other suitable device configured to communicate via a wireless medium.

[0037] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 can be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 can be considered user premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] Typically, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. To avoid interference between wireless networks using different RATs, each frequency can support a single RAT within a given geographical area. In some cases, NR or 5G RAT networks can be deployed.

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

[0040] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, the two initial operating frequency bands have been designated as frequency range names FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally referred to (interchangeably) as the “Sub-6 GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although it differs from the Extremely High Frequency (EHF) band (30GHz–300GHz), it is frequently (interchangeably) referred to as the “millimeter wave” band in documents and articles, and the EHF band is recognized as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0041] Frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR research has identified the operating bands of these IF bands as the frequency range name FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and therefore can effectively extend the characteristics of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating bands have been identified as the frequency range names FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0042] In light of the foregoing, unless otherwise specifically stated, the term "sub-6 GHz" or similar terms (if used herein) should be understood to broadly refer to frequencies that may be below 6 GHz, within FR1, or may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, the terms "millimeter wave," etc., if used herein, can broadly refer to frequencies that may include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. It is anticipated that frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] As indicated above, Figure 1 This is provided as an example. Other examples may differ from the one provided. Figure 1 The example described.

[0044] Figure 2 This is a schematic diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0045] At base station 110, transmitting processor 220 can receive data from data source 212 intended for UE 120 (or a set of UE 120). Transmitting processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 can process (e.g., code and modulate) the data for UE 120, and can provide data symbols for UE 120, at least in part, based on the MCS selected for UE 120. Transmitting processor 220 can process system information (e.g., for Semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, permission, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 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 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems), shown as modems 232a to 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can further use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0046] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 and / or other base stations 110, and can provide a set of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition the received signal (e.g., filter, amplify, down-convert, and / or digitize) to obtain an input sample. Each modem 254 can use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbol from modem 254, can perform MIMO detection on the received symbol (if applicable), and can provide the detected symbol. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data from the UE 120 to the data sink 260, and provide decoding control information and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0047] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0048] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, collections of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a collection of coplanar antenna elements, a collection of non-coplanar antenna elements, and / or be coupled to one or more transmitting and / or receiving components (such as...) Figure 2 One or more antenna elements (one or more components in the process).

[0049] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmit processor 264 can be pre-encoded (if applicable) by the TX MIMO processor 266, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The processor (e.g., controller / processor 280) and memory 282 can use a transceiver to perform aspects of any of the methods described herein (e.g., references). Figures 6-14 ).

[0050] At base station 110, uplink signals from UE 120 and / or other UEs can be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of base station 110 may include modulator and demodulator. In some examples, base station 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. Processors (e.g., controller / processor 240) and memory 242 may be used with the transceiver to perform aspects of any of the methods described herein (e.g., references). Figures 6-14 ).

[0051] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other components may perform one or more techniques associated with carrier configuration segment types and analog beamforming spreads in an Open Radio Access Network (O-RAN), as described in more detail elsewhere herein. In some aspects, the radio unit (RU) described herein is Figure 2 The base station 110 shown is included in or comprises one or more components of the base station 110. In some aspects, the distributed unit (DU) described herein is Figure 2 The base station 110 shown is included in the base station 110, or includes one or more components of the base station 110. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component can perform or direct, for example Figure 9 The process 900 Figure 10 Process 1000 Figure 11 Process 1100 Figure 12 The operation of process 1200 and / or other processes described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 9 The process 900 Figure 10 Process 1000 Figure 11 Process 1100 Figure 12 The operation of process 1200, and / or other processes described herein. In some examples, the execution instructions may include: run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0052] In some aspects, the RU includes: a unit for receiving from the DU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in an indicated carrier or band sector group; and / or a unit for performing beamforming for one or more communications with the UE based at least in part on the information included in the control plane message. In some aspects, the unit for the RU to perform the operations described herein may include one or more of, for example, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0053] In some aspects, the RU includes: a unit for receiving control plane messages from the DU that include analog beamforming information applied to all resource blocks and spatial layers of one or more carriers; and / or a unit for performing beamforming for one or more communications with the UE, at least in part based on the analog beamforming information. In some aspects, the unit for the RU to perform the operations described herein may include one or more of, for example, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0054] In some aspects, the DU includes a unit for transmitting to the RU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in the indicated carrier or band sector group. In some aspects, the unit for the DU to perform the operations described herein may include one or more of, for example, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0055] In some aspects, the DU includes units for transmitting control plane messages to the RU including analog beamforming information applied to all resource blocks and space layers in one or more carriers. In some aspects, units for the DU to perform the operations described herein may include one or more of, for example, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

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

[0057] As pointed out above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0058] Figure 3 This is a schematic diagram illustrating example 300 of a timeslot format according to this disclosure. Figure 3 As shown, time-frequency resources in a radio access network can be divided into resource blocks (shown as a single resource block (RB) 305). RB 305 is sometimes referred to as a physical resource block (PRB). RB 305 includes a set of subcarriers (e.g., 12 subcarriers) and a set of symbols (e.g., 14 symbols) that can be scheduled by base station 110 as a unit. In some aspects, RB 305 may include a set of subcarriers in a single timeslot. As shown, a single time-frequency resource included in RB 305 may be referred to as a resource element (RE) 310. RE 310 may include a single subcarrier (e.g., in frequency) and a single symbol (e.g., in time). The symbol may be referred to as an orthogonal frequency division multiplexing (OFDM) symbol. RE 310 may be used to transmit a modulation symbol, which may be a real-valued or complex-valued symbol.

[0059] In some telecommunications systems (e.g., NR), the RB 305 can span 12 subcarriers over a duration of 0.1 milliseconds (ms), with subcarrier spacings of, for example, 15 kHz, 30 kHz, 60 kHz, or 120 kHz, and other examples. A radio frame can include 40 time slots and can have a length of 10 ms. Therefore, each time slot can have a length of 0.25 ms. However, the time slot length can vary depending on the digital scheme used for communication (e.g., subcarrier spacing and / or cyclic prefix format). Time slots can be configured with a link direction for transmission (e.g., downlink or uplink). In some aspects, the link direction for time slots can be configured dynamically. Figure 3As shown, in some examples, RB 305 may include a control area and a data area. In 5G / NR, the control area can be optional and may not exist in all RB 305s. In the absence of a control area in an RB 305, that area can be used for data.

[0060] As pointed out above, Figure 3 This is provided as an example. Other examples may differ from the one provided. Figure 3 The example described.

[0061] Figure 4 This is a block diagram illustrating an example 400 of an O-RAN architecture according to this disclosure. Figure 4 As shown, the O-RAN architecture may include a control unit (CU) 410, which communicates with the core network 420 via a backhaul link. Furthermore, the CU 410 may communicate with one or more DUs 430 via corresponding midhaul links. Each DU 430 may communicate with one or more RUs 440 via a corresponding forward link, and each RU 440 may communicate with a corresponding UE 120 via a radio frequency (RF) access link. The DUs 430 and RUs 440 may also be referred to as O-RAN DU (O-DU) 430 and O-RAN RU (O-RU) 440, respectively.

[0062] In some aspects, the DU 430 and RU 440 can be implemented according to a functional split architecture, wherein the functionality of base station 110 (e.g., eNB or gNB) is provided by the DU 430 and one or more RU 440 communicating via a frontend link. Therefore, as described herein, base station 110 may include the DU 430 and one or more RU 440, which may be co-located or geographically distributed. In some aspects, the DU 430 and associated RU 440 may communicate via a frontend link to exchange real-time control plane information via a Lower Layer Split (LLS) Control Plane (LLS-C) interface, non-real-time management information via an LLS Management Plane (LLS-M) interface, and / or user plane information via an LLS User Plane (LLS-U) interface.

[0063] Therefore, DU 430 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 440s. For example, in some aspects, DU 430 can host the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on lower-layer function splitting. Higher-layer control functions (such as Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and / or Service Data Adaptation Protocol (SDAP)) can be hosted by CU410. RU 440 controlled by DU 430 can correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, and / or Physical Random Access Channel (PRACH) extraction and filtering) based at least in part on lower-layer function splitting. Therefore, in the O-RAN architecture, RU 440 handles over-the-air (OTA) communication with UE120, and the real-time and non-real-time aspects of control and user plane communication with RU 440 are controlled by the corresponding DU 430, which enables DU 430 and CU 410 to be implemented in a cloud-based RAN architecture.

[0064] As pointed out above, Figure 4 This is provided as an example. Other examples may differ from the one provided. Figure 4 The example described.

[0065] Figure 5 This is a schematic diagram illustrating an example 500 of a transmission header for a message in O-RAN according to this disclosure. Figure 5 As shown, transport headers can be included in messages sent between network nodes in an O-RAN architecture. For example, transport headers can be included in messages sent from a DU to an RU or from an RU to a DU. Transport headers can be included in control plane (C-plane) messages, user plane (U-plane) messages, and / or management plane (M-plane) messages. Figure 5 As shown, the transport header can be an 8-byte transport header. In some aspects, the transport header can be an Enhanced Shared Public Radio Interface (eCPRI) transport header. In some aspects, the transport header can be included within the message payload (e.g., an Ethernet payload).

[0066] The transport header can indicate information about the message, such as message type, transport source identifier, destination identifier, and / or sequence number identifier. For example, the transport header can indicate eCPRI version information (e.g., the eCPRI protocol version) in the eCPRI version field of the transport header (e.g., in bits 0-3 of octet 1). The transport header may include a concatenation indicator in the eCPRI Continuation field (e.g., in bit 7 of octet 1). The concatenation indicator can indicate whether the message is associated with other messages in the eCPRI Protocol Data Unit (PDU) (e.g., the concatenation indicator can indicate whether the message is the last message in the eCPRI PDU, or whether another message follows a message within the eCPRI PDU). Figure 5 As shown, bit fields 4-6 of the octet 1 of the transmission header can be preserved (e.g., not used).

[0067] The transport header may include an eCPRIMessage field (e.g., in byte 2) indicating the message type associated with the message. For example, the eCPRIMessage field may indicate whether the message is a C-plane message or a U-plane message. The transport header may include an eCPRIPayload field (e.g., in byte 3 and / or byte 4) indicating the payload size of the message (e.g., in bytes).

[0068] The transport header may include fields indicating message source and destination information in byte 5 and / or byte 6. For example, if the message is a C-plane message, the message source and destination information may be included in the eCPRIRtcid field. If the message is a U-plane message, the message source and destination information may be included in the eCPRIPcid field. The message source and destination information may be indicated by extended antenna-carrier (eAxC) information. For example, eAxC information may include a transmitting device port identifier, a frequency band sector identifier, a transmitting antenna identifier, a component carrier identifier, a receiving device port identifier, a receiving antenna identifier, an indication of the MIMO spatial stream and / or an indication of the MIMO layer, and other examples. The message source and destination information may indicate an eAxC identifier associated with the message. The transport header may include an eCPRISeqID field (e.g., in byte 7 and / or byte 8) indicating a sequence identifier associated with the message.

[0069] As pointed out above, Figure 5 This is provided as an example. Other examples may differ from the one provided. Figure 5 The example described.

[0070] The DU can send C-plane messages to the RU via the fronthaul interface. In some examples, a two-layer header approach can be used to encapsulate C-plane messages. The first layer may include an eCPRI header, which may include fields indicating the message type. The second layer may be an application layer, including fields for control and synchronization. Within the application layer, a "segment" defines the characteristics of the U-plane data to be transmitted or received by the RU using a beam with an associated mode identifier. Various segment types are defined for segments in the application layer, and the structure of the C-plane message may differ for different segment types. In some cases, segment types in the O-RAN fronthaul interface standard (e.g., segment type 0, segment type 1, and / or segment type 3, etc.) are designed to provide information based on per eAxC (e.g., per spatial layer) and per RB (or RB group). Such segment types can be well-suited for information such as digital beamforming information, which can vary based on per RB or per spatial layer. However, information such as analog beamforming information, time-domain duplex (TDD) configuration, and / or idle or guard periods can be applied to carrier or band sector groups. For example, such information can be applied to all RBs and spatial layers in a carrier or band sector group. Repeatedly transmitting such information per RB and per spatial layer can incur significant C-plane signaling overhead, which can increase processing time for RUs and reduce network speed.

[0071] In some cases, additional restrictions can be imposed on existing defined segment types (e.g., a restriction that the number of RBs indicated in the segment header associated with the segment type is equal to 0), and the use of one or more extensions (e.g., extension type 7) can be implemented to transmit information applicable to all RBs and / or all eAxCs. However, in this case, the RU may not be able to determine from a quick check that a packet (e.g., a C-plane message) includes information applicable to all RBs and / or all eAxCs. Instead, the RU may need to process each packet (e.g., each C-plane message) within the C-plane receive window to extract relevant information. In this case, the RU may not be able to prioritize processing information applicable to all RBs and / or all eAxCs in the earlier part of the C-plane processing window, which could prevent any reduction in beamforming processing time for the RU using that information.

[0072] Some of the techniques and apparatus described herein enable the DU to send C-plane messages to the RU associated with segment types dedicated to information applied to all RBs and space layers in a carrier or band sector group. The C-plane messages may include information applied to all RBs and space layers in the indicated carrier or band sector group. The RU can receive the C-plane messages associated with segment types dedicated to information applied to all RBs and space layers in a carrier or band sector group, and the RU can perform beamforming for one or more communications with the UE based at least in part on the information included in the C-plane messages. Therefore, the C-plane signaling overhead for providing information to the RU can be reduced. Furthermore, the RU can prioritize the C-plane messages associated with segment types dedicated to information applied to all RBs and space layers in a carrier or band sector group, which can reduce the processing time of beamforming performed by the RU.

[0073] Beamforming is a technique in which an array of antenna elements is used to transmit or receive radio signals in a specific beam direction. In some examples, the RU (Radio Unit) can use hybrid beamforming, which combines analog and digital beamforming. In this case, the DU (Radio Unit) can specify both analog and digital beamforming information based on per RB (Radio Base) and per spatial layer. However, while digital beamforming can vary based on per RB and per spatial layer, analog beamforming is broadband and applied to all RBs and all spatial layers for a carrier. Therefore, the same analog beamforming information can be repeated multiple times with digital beamforming information, resulting in significant signaling overhead. Furthermore, in order for the RU to extract the analog beamforming information for a symbol, it may be necessary for the RU to process all digital beams within the carrier. For example, in some cases, there may be approximately 4000 digital beams per carrier.

[0074] Some of the techniques and apparatus described herein enable the DU to send C-plane messages to the RU that include analog beamforming information applied to all RBs and space layers of one or more carriers. The RU can receive the C-plane messages, and the RU can perform beamforming for one or more communications with the UE based at least in part on the analog beamforming information. In some aspects, the analog beamforming information can be included in an extension of a segment header associated with a segment type dedicated to information applied to all RBs and space layers of a carrier or band sector group. As a result, the DU can provide analog beamforming information for symbols in a single message, thereby reducing C-plane signaling overhead and reducing the processing time required for the RU to process the analog beamforming information.

[0075] Figure 6 This is a schematic diagram illustrating example 600 associated with carrier configuration segment type and analog beamforming spread in O-RAN according to the present disclosure. Figure 6As shown, Example 600 includes communication between DU 605, RU 610, and UE 120. In some aspects, DU 605 and RU 610 can be included in an O-RAN architecture. For example, DU 605 can be combined in a manner similar to that described above. Figure 4 The DU 430 and RU 610 described above can be combined in a similar manner. Figure 4 The described RU 440, DU 605, and RU 610 can communicate via a fronthaul link (e.g., via a fronthaul interface). RU 610 and UE 120 can communicate via a radio access link (which may include an uplink and a downlink).

[0076] like Figure 6 As shown, and via reference numeral 615, DU 605 can send a C-plane message to RU 610, including information applicable to all RBs and space layers in a carrier group (e.g., component carrier (CC)) or frequency band sector. RU 610 can receive the C-plane message sent by DU 605. In some aspects, the C-plane message can be associated with a segment type dedicated to information applicable to all RBs and space layers in a carrier or frequency band sector group. In some aspects, the segment type dedicated to information applicable to all RBs and space layers in a carrier or frequency band sector group can be associated with an index used to identify the message associated with that segment type. For example, this segment type can be associated with index 8 (e.g., segment type 8) or another index value. Hereinafter, the segment type dedicated to information applicable to all RBs and space layers in a carrier or frequency band sector group may be referred to as a "dedicated segment type" or "segment type 8".

[0077] By using a C-plane message associated with a dedicated segment type, the DU 605 can transmit a single C-plane message containing information applicable to all RBs and all space layers in a carrier or band sector group (e.g., TDD configuration information, idle and / or active symbol information, and / or analog beamforming information, etc.). In some aspects, the C-plane message associated with a dedicated segment type may include a transport header, an application header, and one or more segment headers associated with the dedicated segment type. The transport header may be an eCPRI transport header, such as the combination described above. Figure 5The eCPRI transport header is described. The application header may include an indication that the segment type is a dedicated segment type (e.g., segment type 8). The application header may also indicate the number of segments for which information is included in the C-plane message. In some aspects, the C-plane message may include information for one or more segments of a dedicated segment type, and each segment may define the characteristics of U-plane data to be transmitted or received using a corresponding beam direction. For example, different segments of a dedicated segment type may be associated with different carrier or frequency band sector groups and / or different symbol groups (e.g., OFDM symbols) in a time slot. In some aspects, the C-plane message may include a corresponding segment header associated with the dedicated segment type for each segment. For example, the number of segment headers included in the C-plane message may correspond to the number of segments indicated in the application layer. The segment header associated with the dedicated segment type may include information applied to all RBs and spatial layers for a carrier or frequency band sector group.

[0078] In some aspects, a segment header associated with a dedicated segment type may indicate a group of carriers or frequency band sectors for which the information in the segment header applies. For example, the segment header may include an eAxC mask whose identifier (e.g., at least in part based on an eAxC identifier) ​​indicates the indicated group of carriers or frequency band sectors for which the information in the segment header applies. For example, the eAxC mask may indicate a set of eAxC identifiers, and RU 610 may identify the group of frequency band sectors based on a frequency band sector identifier associated with an eAxC identifier or a group of component carriers from a component carrier identifier associated with an eAxC identifier. In some aspects, the indicated group of carriers or frequency band sectors may include one or more carriers or frequency band sectors.

[0079] In some aspects, the segment header associated with a dedicated segment type can indicate the symbols in the time slot for which the information in the segment header is applied. For example, the segment header can include a symbol mask that identifies the symbols in the time slot for which RU 610 will apply the information included in the segment header (e.g., the symbols in the time slot for which RU 610 will perform beamforming using the information included in the segment header).

[0080] In some aspects, the segment header associated with a dedicated segment type may include TDD configurations applied to all RBs and space layers in a carrier or band sector group indicated in the segment header. For example, the segment header may include a direction pattern for providing TDD configurations for symbols in a time slot (or a subset of symbols in a time slot indicated by a symbol mask). In this case, the direction pattern may indicate the corresponding direction (e.g., downlink or uplink) associated with each symbol.

[0081] In some aspects, the segment header associated with a dedicated segment type can indicate idle and / or active information for symbols in a time slot. For example, the segment header may include an indication of patterns of idle and active symbols for symbols in a time slot (or a subset of symbols in a time slot indicated by a symbol mask). In this case, for each symbol, the patterns of idle and active symbols can indicate whether the symbol is idle or active.

[0082] In some aspects, the segment header associated with a dedicated segment type may not include RB information. For example, the segment header may not identify RBs, and the information included in the segment header may apply to all RBs in the indicated carrier or frequency band sector group. In some aspects, the segment header associated with a dedicated segment type may allow for the inclusion of optional additional information, such as information on all RBs and space layers applied to the carrier or frequency band sector group. The C-plane message associated with a dedicated segment type and the segment header associated with a dedicated segment type are discussed below. Figure 7 To describe and depict in more detail.

[0083] In some aspects, the information included in the C-plane message may include simulated beamforming information applied to all RBs and space layers of a carrier or a group of carriers (or frequency band sectors). In some aspects, the simulated beamforming information may include an indication of simulated beams applied to all RBs and space layers of a carrier. In some aspects, for each of one or more carriers (e.g., each carrier in a group of carriers or frequency band sectors), the simulated beamforming information may include a corresponding indication of simulated beams applied to all RBs and space layers of that carrier. For example, the indication of simulated beams for a carrier may be a simulated beam for hybrid beamforming of all RBs and space layers of that carrier. In some aspects, the indication of simulated beams for a carrier may identify the set of antenna element weights associated with the simulated beams for the carrier. In some aspects, the indication of simulated beams for a carrier may include an indication of a beam identifier for the simulated beam. In this case, the beam identifier for the simulated beam may be mapped to the set of antenna element weights associated with the simulated beam for the carrier. For example, RU 610 can determine the weights of antenna elements for an analog beam used for a carrier from a lookup table, at least in part, based on indications of beam identifiers included in the analog beamforming information.

[0084] In some aspects, analog beamforming information may be included in a C-plane message associated with a dedicated segment type (e.g., a segment type dedicated to information applied to all RBs and space layers in a carrier or band sector group). For example, analog beamforming information may be included in an analog beamforming extension included in a C-plane message associated with a dedicated segment type. In some aspects, the analog beamforming extension may be included in a segment header associated with a dedicated segment type. For example, each segment header associated with a dedicated segment type may include a corresponding analog beamforming extension indicating the corresponding analog beam for a carrier in a carrier or band sector group indicated in the segment header. In some aspects, the analog beamforming extension may be associated with an index used to identify the extension type. For example, the analog beamforming extension may be associated with index 21 (e.g., extension 21) or another index value. The following is in conjunction with... Figure 8 A more detailed description and depiction may be included in the simulated beamforming spread in the C-plane message associated with the dedicated segment type.

[0085] like Figure 6 As further shown, and by reference numeral 620, RU 610 can perform beamforming for one or more communications with UE 120 based at least in part on information included in the C-plane message received from DU 605. For example, RU 610 can use information included in the C-plane message that applies to all RBs and space layers in a carrier or band sector group to perform beamforming. In some aspects, RU 610 can use TDD configuration, idle and active modes, and / or analog beamforming information included in the C-plane message in beamforming to form transmit (Tx) beams for transmitting downlink communications to UE 120 in the indicated symbols of the time slot (e.g., in the symbol mask of the segment header) and / or receive (Rx) beams for receiving uplink communications from UE 120. For example, RU 610 can use TDD configuration, idle and active modes, and / or simulated beamforming information for all RBs and space layers of an indicated carrier or band sector group in beamforming for that group.

[0086] In some aspects, RU 610 can perform hybrid beamforming using analog beamforming information indicated for all RBs and space layers in a carrier (or carrier group). In this case, RU 610 can combine analog beamforming information for RBs and space layers in that carrier with digital beamforming information based on per-RB and per-space-layer indications (e.g., in other C-plane messages).

[0087] In some aspects, RU 610 can prioritize C-plane messages associated with a dedicated segment type (e.g., compared to C-plane messages associated with other segment types). For example, RU 610 can prioritize C-plane messages associated with a dedicated segment type over other C-plane messages received within the C-plane receive window. This allows RU 610 to determine information for different carrier or frequency band sector groups applied to all RBs and space layers for earlier timeslot / symbol processing timelines, saving RU 610 processing time during beamforming.

[0088] In some aspects, DU 605 transmits additional messages to RU 610 that include supplementary information related to beamforming (e.g., additional C-plane messages associated with other segment types). In this case, RU 610 may perform beamforming at least in part based on C-plane messages associated with dedicated segment types, and this information is included in one or more other messages (e.g., other C-plane messages) received from DU 605.

[0089] like Figure 6 As further shown, and by reference numeral 625, RU 610 may use beams generated by beamforming to transmit one or more downlink communications to UE 120 and / or receive one or more uplink communications from UE 120. For example, RU 610 may use one or more Tx beams generated by beamforming to transmit one or more downlink communications to UE 120. Alternatively or additionally, RU 610 may use one or more Rx beams generated by beamforming to receive one or more uplink communications. UE 120 may receive one or more downlink communications from RU 610 and / or transmit one or more uplink communications to RU 610 using Rx beams and / or Tx beams corresponding to the Tx beams and / or Rx beams used by RU 610.

[0090] As described above, DU 605 can send a C-plane message to RU 610 associated with a segment type dedicated to information applied to all RBs and space layers in a carrier or band sector group. The C-plane message may include information applied to all RBs and space layers in the indicated carrier or band sector group. RU 610 can receive the C-plane message associated with the dedicated segment type, and RU 610 can perform beamforming for one or more communications with UE 120 based at least in part on the information included in the C-plane message. As a result, the C-plane signaling overhead for providing information to RU 610 can be reduced. For example, without the dedicated segment type described herein, RU 610 might need to process hundreds of segment 1 C-plane messages to determine the TDD configuration for all band sectors; however, with the dedicated segment type described herein, RU 610 can determine the TDD configuration for all band sectors from only a few C-plane messages associated with the dedicated segment type. In addition, the RU 610 can prioritize C-plane messages associated with dedicated segment types, which can reduce the processing time of beamforming performed by the RU 610.

[0091] As described above, C-plane messages can include analog beamforming information applied to all RBs and space layers in one or more carriers. In some aspects, the analog beamforming information can be included in an extension to the segment header associated with the dedicated segment type. As a result, C-plane signaling overhead can be reduced. For example, without the analog beamforming extension described herein, the RU 610 might need to process all 4000 digital beams to extract a single analog beam for a symbol within a carrier; however, with the analog beamforming extension, the RU 610 can determine the analog beam for a symbol in a carrier from a single C-plane message. This can save processing time required for the RU to process the analog beamforming information. In some examples, without the dedicated segment type and analog beamforming extension, the RF switch (RFSW) of the RU 610 may have approximately 20 μs to process the analog beamforming information; however, with the dedicated segment and analog beamforming extension, the RFSW of the RU 610 may have approximately 120 μs to process the analog beamforming information.

[0092] As pointed out above, Figure 6 This is provided as an example. Other examples may differ from the one provided. Figure 6 The example described.

[0093] Figure 7 This is a schematic diagram illustrating example 700 related to carrier configuration segment type and analog beamforming spread in O-RAN according to the present disclosure. Figure 7As shown, Example 700 illustrates an example of the structure of a C-plane message associated with a segment type (e.g., "dedicated segment type" or "segment type 8") that is dedicated to information applied to all RBs and space layers in a carrier or band sector group.

[0094] like Figure 7 As shown, a C-plane message associated with a private segment type may include a transport header 705, an application header 710, and one or more segment headers 715 associated with the private segment type. In some aspects, the transport header 705 may be an eCPRI transport header, such as the combination described above. Figure 5 The eCPRI transport header is described. The application header 710 may include a field indicating the segment type for the C-plane message. For example, the segment type field may indicate that the segment type is a dedicated segment type (e.g., segment type 8). The application header 710 may also include a field indicating the number of segments whose information is included in the C-plane message. For example, different segments of a dedicated segment type may be associated with different carrier or frequency band sector groups and / or different symbol groups (e.g., OFDM symbols) in a time slot. In some aspects, the C-plane message may include a corresponding segment header 715 for each segment. For example, the number of segment headers 715 included in the C-plane message may correspond to the number of segments indicated in the application header 710. The application header 710 may also include fields indicating data direction, payload version, frame ID, subframe ID, time slot ID, and start symbol ID.

[0095] like Figure 7 As shown, the segment header 715 associated with a dedicated segment type can indicate a carrier or frequency band sector group for which the information in the segment header applies. For example, the segment header 715 may include an eAxC mask field (eAxCMask) that identifies (e.g., using an eAxC identifier) ​​the indicated carrier or frequency band sector group for which the information in the segment header 715 applies. For example, the eAxC mask field may include 16 bits (e.g., eAxCMask[7:0] and eAxCMask[15:8]) for indicating an eAxC identifier that identifies the frequency band sector or carrier group for which the information in the segment header 715 applies.

[0096] like Figure 7 As further shown, the segment header 715 may include a symbol mask field (SymmMask) that identifies the symbol in the time slot for which the information included in the segment header is applied. For example, the symbol mask field may include 14 bits (e.g., SymmMask[7:0] and SymmMask[13:8]), and each bit may provide an indication of the corresponding symbol in the time slot.

[0097] like Figure 7 As further shown, the segment header 715 can indicate the TDD configuration of all RBs and spatial layers applied to the carrier or frequency band sector group indicated in the segment header 715. For example, the segment header 715 may include a direction pattern field indicating the TDD configuration for a symbol in a time slot (or a subset of symbols in a time slot indicated by a symbol mask). In this case, the direction pattern field may include 14 bits (e.g., directionPattern[7:0] and directionPattern[13:8]) indicating the corresponding direction (e.g., downlink or uplink) for a symbol in a time slot.

[0098] like Figure 7 As further shown, the segment header 715 can indicate idle and / or activity information for symbols in a time slot. For example, the segment header 715 may include an idle pattern field that indicates the pattern of idle and active symbols for symbols in a time slot (or a subset of symbols in a time slot indicated by a symbol mask). In this case, the idle pattern field may include 14 bits (e.g., idlePattern[7:0] and idlePattern[13:8]) that provide a corresponding indication of whether a symbol in a time slot is idle or active.

[0099] In some aspects, the segment header 715 associated with a dedicated segment type may not include RB information. For example, the segment header may not identify RBs, and the information included in the segment header may be applied to all RBs in the indicated carrier or frequency band sector group. In some aspects, the segment header 715 associated with a dedicated segment type may allow for the inclusion of optional additional information on all RBs and space layers applied to the carrier or frequency band sector group.

[0100] As pointed out above, Figure 7 This is provided as an example. Other examples may be provided in conjunction with [the relevant information]. Figure 7 The descriptions differ.

[0101] Figure 8 This is a schematic diagram illustrating example 800 associated with carrier configuration segment type and analog beamforming spread in O-RAN according to the present disclosure. Figure 8 As shown, Example 800 illustrates an example of the structure for an analog beamforming extension for a C-plane message associated with a segment type dedicated to information applied to all RBs and space layers in a carrier or band sector group. In some aspects, the analog beamforming extension may be an extension included in a segment header (e.g., segment header 715) associated with the dedicated segment type.

[0102] like Figure 8 As shown, simulated beamforming extension can indicate the extension type (e.g., in the extType field) and the extension length (e.g., in the extLen field). For example... Figure 8 As further shown, the analog beamforming extension may also include one or more analog beam indication fields (e.g., analogBeam 0-analogBeam N) that provide indication of the corresponding analog beam for one or more carriers (e.g., carrier 0-carrier N). For example, the analog beamforming extension may include a corresponding indication of the analog beam for each carrier in a carrier or band sector group that indicates a segment header (e.g., segment header 715) associated with a dedicated segment type. Figure 8 As shown, the analog beam indication field (e.g., analogBeam0) may include 16 bits (e.g., analogBeam0[7:0] and analogBeam0[15:8]) for providing an indication of the analog beam for the carrier. In some aspects, the indication of the analog beam for the carrier may identify the set of antenna element weights associated with the analog beam for the carrier. In some aspects, the indication of the analog beam for the carrier may include an indication of a beam identifier for the analog beam. In this case, the beam identifier for the analog beam may be mapped to the set of antenna element weights associated with the analog beam for the carrier.

[0103] As pointed out above, Figure 8 This is provided as an example. Other examples may differ from the one provided. Figure 8 The example described.

[0104] Figure 9 This is a diagram illustrating an example process 900 performed by an RU, for example, according to this disclosure. Example process 900 is an example of an RU (e.g., RU 610) performing operations associated with carrier configuration segment type and analog beamforming spread in the O-RAN.

[0105] like Figure 9 As shown, in some aspects, process 900 may include: receiving from the DU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in the indicated carrier or band sector group (block 910). For example, the RU (e.g., using...) Figure 13The receiving component 1302 depicted herein can receive from the DU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in an indicated carrier or band sector group, as described above. Figure 6-8 As described.

[0106] like Figure 9 As further shown, in some aspects, process 900 may include: performing beamforming for communication with one or more UEs based at least in part on information included in the control plane messages (block 920). For example, RU (e.g., using...) Figure 13 The beamforming component 1308 described herein can perform beamforming for communication with one or more UEs based at least in part on information included in the control plane messages, as described above. Figure 6-8 As described.

[0107] Process 900 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0108] In the first aspect, the control plane message includes an indication of a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and a segment header associated with the segment type, wherein the segment header includes information applied to all resource blocks and space layers in the indicated carrier or band sector group.

[0109] In a second aspect, either alone or in combination with the first aspect, the segment header includes an indication of an eAxC mask, which identifies the indicated carrier or frequency band sector group for which the information included in the segment header is applied.

[0110] In the third aspect, either alone or in combination with one or more of the first and second aspects, the information included in the segment header includes TDD configurations for all resource blocks and space layers applied to the indicated carrier or band sector group.

[0111] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the information included in the segment header includes patterns of idle and active symbols for all resource blocks and space layers in the indicated carrier or band sector group.

[0112] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the segment header includes an indication of symbols in the time slot for information included in the segment header for its application.

[0113] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the information included in the control plane message includes analog beamforming information for the indicated carrier or band sector group.

[0114] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the control plane message includes a segment header associated with a segment type specifically used for information applied to all resource blocks and space layers in a carrier or band sector group, and analog beamforming information is included in the analog beamforming extension in the segment header.

[0115] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, for each carrier in the indicated carrier or band sector group, the simulated beamforming information includes an indication of the corresponding simulated beams applied to all resource blocks and space layers in that carrier.

[0116] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, for each carrier in the indicated carrier or band sector group, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0117] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 900 includes using one or more beams generated by beamforming to communicate with the UE.

[0118] Although Figure 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include... Figure 9 The boxes depicted in the diagram can be compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Alternatively, two or more boxes in process 900 can be executed in parallel.

[0119] Figure 10 This is a diagram illustrating an example process 1000 performed by an RU, for example, in accordance with this disclosure. Example process 1000 is an example of an RU (e.g., RU 610) performing operations associated with carrier configuration segment type and analog beamforming spread in the O-RAN.

[0120] like Figure 10 As shown, in some aspects, process 1000 may include: receiving from the DU a control plane message including analog beamforming information applied to all resource blocks and space layers of one or more carriers (block 1010). For example, the RU (e.g., using...) Figure 13The receiving component 1302 depicted in the diagram can receive control plane messages from the DU that include analog beamforming information applied to all resource blocks and space layers of one or more carriers, as described above. Figure 6-8 As described.

[0121] like Figure 10 As further shown, in some aspects, process 1000 may include: performing beamforming for communication with one or more UEs based at least in part on analog beamforming information (block 1020). For example, RU (e.g., using...) Figure 13 The beamforming component 1308 described herein can perform beamforming for communication with one or more UEs based at least in part on analog beamforming information, as described above. Figure 6-8 As described.

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

[0123] In the first aspect, for each of one or more carriers, the simulated beamforming information includes indications of the corresponding simulated beams applied to all resource blocks and space layers in that carrier.

[0124] In the second aspect, either alone or in combination with the first aspect, for each of one or more carriers, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0125] In the third aspect, either alone or in combination with one or more of the first and second aspects, control plane messages are associated with segment types dedicated to information applied to all resource blocks and space layers in a carrier or band sector group.

[0126] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the control plane message includes a segment header associated with a segment type specifically used for information applied to all resource blocks and space layers in a carrier or band sector group, and analog beamforming information is included in the analog beamforming extension in the segment header.

[0127] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1000 includes using one or more beams generated by beamforming to communicate with the UE.

[0128] Although Figure 10An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include... Figure 10 The boxes depicted in the diagram can be compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Alternatively, two or more boxes in process 1000 can be executed in parallel.

[0129] Figure 11 This is a schematic diagram illustrating, for example, an example process 1100 performed by a DU according to this disclosure. Example process 1100 is an example of an operation performed by a DU (e.g., DU 605) associated with carrier configuration segment type and analog beamforming spread in the O-RAN.

[0130] like Figure 11 As shown, in some aspects, process 1100 may include: sending a control plane message to the RU associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in the indicated carrier or band sector group (block 1110). For example, DU (e.g., using...) Figure 4 The transmitting component 1404 depicted can transmit to the RU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or frequency band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in the indicated carrier or frequency band sector group, as described above. Figure 6-8 As described.

[0131] Process 1100 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere in this document.

[0132] In the first aspect, the control plane message includes an indication of a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and a segment header associated with the segment type, wherein the segment header includes information applied to all resource blocks and space layers in the indicated carrier or band sector group.

[0133] In a second aspect, either alone or in combination with the first aspect, the segment header includes an indication of an eAxC mask, which identifies the indicated carrier or frequency band sector group for which the information included in the segment header is applied.

[0134] In the third aspect, either alone or in combination with one or more of the first and second aspects, the information included in the segment header includes TDD configurations for all resource blocks and space layers applied to the indicated carrier or band sector group.

[0135] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the information included in the segment header includes patterns of idle and active symbols for all resource blocks and space layers in the indicated carrier or band sector group.

[0136] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the segment header includes an indication of symbols in the time slot for information included in the segment header for its application.

[0137] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the information included in the control plane message includes analog beamforming information for the indicated carrier or band sector group.

[0138] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the control plane message includes a segment header associated with a segment type specifically used for information applied to all resource blocks and space layers in a carrier or band sector group, and analog beamforming information is included in the analog beamforming extension in the segment header.

[0139] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, for each carrier in the indicated carrier or band sector group, the simulated beamforming information includes an indication of the corresponding simulated beams applied to all resource blocks and space layers in that carrier.

[0140] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, for each carrier in the indicated carrier or band sector group, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0141] Although Figure 11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include... Figure 11 The boxes depicted in the diagram can be compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Alternatively, two or more boxes in process 1100 can be executed in parallel.

[0142] Figure 12 This is a schematic diagram illustrating, for example, an example process 1200 performed by a DU according to this disclosure. Example process 1200 is an example of an operation performed by a DU (e.g., DU 605) associated with carrier configuration segment type and analog beamforming spread in the O-RAN.

[0143] like Figure 12 As shown, in some aspects, process 1200 may include: sending a control plane message (block 1210) to the RU including analog beamforming information applied to all resource blocks and space layers of one or more carriers. For example, the DU (e.g., using...) Figure 14 The transmitting component 1404 depicted in the text can transmit control plane messages to the RU including analog beamforming information applied to all resource blocks and space layers in one or more carriers, as described above. Figure 6-8 As described.

[0144] Process 1200 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere in this document.

[0145] In the first aspect, for each of one or more carriers, the simulated beamforming information includes indications of the corresponding simulated beams applied to all resource blocks and space layers in that carrier.

[0146] In the second aspect, for each of one or more carriers, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0147] In the third aspect, control plane messages are associated with segment types that are dedicated to information applied to all resource blocks and space layers in a carrier or band sector group.

[0148] In the fourth aspect, the control plane message includes a segment header associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and analog beamforming information is included in the analog beamforming extension within the segment header.

[0149] Although Figure 12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include... Figure 12 The boxes depicted in the diagram can be compared to additional boxes, fewer boxes, different boxes, or boxes arranged differently. Alternatively, two or more boxes in process 1200 can be executed in parallel.

[0150] Figure 13This is a schematic diagram of an example device 1300 for wireless communication. Device 1300 may be a RU, or a RU may include device 1300. In some aspects, device 1300 includes a receiving component 1302 and a transmitting component 1304, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1300 can use the receiving component 1302 and the transmitting component 1304 to communicate with another device 1306 (such as a UE, DU, or another wireless communication device). As further shown, device 1300 may include a beamforming component 1308 and other examples.

[0151] In some respects, device 1300 can be configured to perform the functions described herein. Figure 6-8 One or more operations described herein. Alternatively or concurrently, the apparatus 1300 may be configured to perform one or more processes described herein, such as... Figure 9 The process 900 Figure 10 The process 1000 or a combination thereof. In some respects, Figure 13 The device 1300 and / or one or more components shown may include a combination Figure 2 One or more components of the described RU. Alternatively or alternatively, Figure 13 One or more components shown can be combined Figure 2 Implemented within one or more components described. Alternatively or additionally, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of that component.

[0152] Receiver 1302 may receive communications from device 1306, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The described RU includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0153] Transmitting component 1304 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 can generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1306. In some aspects, transmitting component 1304 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 1306. In some aspects, transmitting component 1304 can include combinations of... Figure 2 The described RU includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1304 may be co-located with the receive component 1302 in a transceiver.

[0154] The receiving component 1302 can receive from the DU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in the indicated carrier or band sector group. The beamforming component 1308 can perform beamforming for one or more communications with the UE based at least in part on the information included in the control plane message.

[0155] The receiving component 1302 and / or the transmitting component 1304 may use one or more beams generated by beamforming to communicate with the UE.

[0156] The receiving component 1302 can receive control plane messages from the DU that include analog beamforming information applied to all resource blocks and space layers in one or more carriers. The beamforming component 1308 can perform beamforming for one or more communications with the UE based at least in part on the analog beamforming information.

[0157] The receiving component 1302 and / or the transmitting component 1304 may use one or more beams generated by beamforming to communicate with the UE.

[0158] Figure 13 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 13 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, in Figure 13 The two or more components shown can be implemented within a single component, or in Figure 13 The single component shown can be implemented as multiple distributed components. Alternatively, in Figure 13 The set (one or more) components shown can perform actions described by [the following]: Figure 13 The other set of components shown performs one or more functions.

[0159] Figure 14 This is a schematic diagram of an example device 1400 for wireless communication. Device 1400 may be a DU, or a DU may include device 1400. In some aspects, device 1400 includes a receiving component 1402 and a transmitting component 1404, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1400 can use the receiving component 1402 and the transmitting component 1404 to communicate with another device 1406 (such as a UE, RU, or another wireless communication device). As further shown, device 1400 may include a determining component 1408.

[0160] In some respects, device 1400 can be configured to perform the functions described herein. Figure 6-8 One or more operations described herein. Alternatively or concurrently, the apparatus 1400 may be configured to perform one or more processes described herein, such as... Figure 11 Process 1100 Figure 12 Process 1200 or a combination thereof. In some aspects, device 1400 and / or Figure 14 One or more components shown may include combinations Figure 2 One or more components of the DU described. Alternatively or alternatively, Figure 14 One or more components shown can be combined Figure 2 Implemented within one or more components described. Alternatively or additionally, one or more components in the set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of that component.

[0161] Receiver 1402 may receive communications from device 1406, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1400. In some aspects, receiver 1402 may include combinations of... Figure 2The DU described includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0162] Transmitting component 1404 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1406. In some aspects, one or more other components of device 1400 can generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1406. In some aspects, transmitting component 1404 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 1406. In some aspects, transmitting component 1404 can include combinations of... Figure 2 The described DU includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1404 may be co-located with the receive component 1402 in a transceiver.

[0163] The transmitting component 1404 can transmit to the RU a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in an indicated carrier or band sector group.

[0164] The determining component 1408 can determine information about all resource blocks and space layers applied to an indicated carrier or band sector group.

[0165] The transmitting component 1404 can send control plane messages to the RU that include analog beamforming information applied to all resource blocks and space layers in one or more carriers.

[0166] Component 1408 can determine the simulated beamforming information.

[0167] Figure 14 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 14 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, in Figure 14 The two or more components shown can be implemented within a single component, or in Figure 14 The single component shown can be implemented as multiple distributed components. Alternatively, in Figure 14 The set (one or more) components shown can perform actions described by [the following]: Figure 14The other set of components shown performs one or more functions.

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

[0169] Aspect 1: A method of wireless communication performed by a radio unit (RU), comprising: receiving from a distributed unit (DU) a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in an indicated carrier or band sector group; and performing beamforming for communication with one or more user equipment (UE) based at least in part on the information included in the control plane message.

[0170] Aspect 2: According to the method of Aspect 1, wherein the control plane message includes an indication of the segment type for information specifically applied to all resource blocks and space layers in a carrier or band sector group, and a segment header associated with the segment type, wherein the segment header includes the information applied to all resource blocks and space layers in the indicated carrier or band sector group.

[0171] Aspect 3: According to the method of aspect 2, wherein the segment header includes an indication of an extended antenna-carrier (eAxC) mask, the extended antenna-carrier (eAxC) mask identifying the indicated carrier or band sector group for which the information included in the segment header is applied.

[0172] Aspect 4: The method according to any one of Aspects 2-3, wherein the information included in the segment header includes time-domain duplex (TDD) configurations applied to all resource blocks and spatial layers in the indicated carrier or frequency band sector group.

[0173] Aspect 5: The method according to any one of Aspects 2-4, wherein the information included in the segment header includes patterns of idle and active symbols for all resource blocks and space layers in the indicated carrier or band sector group.

[0174] Aspect 6: The method according to any one of Aspects 2-5, wherein the segment header includes an indication of a symbol for applying the information included in the segment header to a time slot.

[0175] Aspect 7: The method according to any one of Aspects 1-6, wherein the information included in the control plane message includes analog beamforming information for an indicated carrier or band sector group.

[0176] Aspect 8: The method according to aspect 7, wherein the control plane message includes a segment header associated with the segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and wherein the analog beamforming information is included in the analog beamforming extension in the segment header.

[0177] Aspect 9: The method according to any of Aspects 7-8, wherein, for each carrier in the indicated carrier or band sector group, the analog beamforming information includes an indication of a corresponding analog beam applied to all resource blocks and space layers in that carrier.

[0178] Aspect 10: The method according to aspect 9, wherein, for each carrier in the indicated carrier or band sector group, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0179] Aspect 11: The method according to any one of aspects 1-10 further includes: communicating with the UE using one or more beams generated by the beamforming.

[0180] Aspect 12: A method of wireless communication performed by a radio unit (RU), comprising: receiving from a distributed unit (DU) a control plane message including analog beamforming information applied to all resource blocks and space layers of one or more carriers; and performing beamforming for communication with one or more user equipment (UE) based at least in part on the analog beamforming information.

[0181] Aspect 13: According to the method of aspect 12, wherein, for each of the one or more carriers, the simulated beamforming information includes an indication of a corresponding simulated beam applied to all resource blocks and space layers in that carrier.

[0182] Aspect 14: The method according to aspect 13, wherein, for each of the one or more carriers, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0183] Aspect 15: The method according to any one of Aspects 12-14, wherein the control plane message is associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group.

[0184] Aspect 16: The method according to any one of Aspects 12-15, wherein the control plane message includes a segment header associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and wherein the analog beamforming information is included in the analog beamforming extension in the segment header.

[0185] Aspect 17: The method according to any one of aspects 12-16 further includes: communicating with the UE using one or more beams generated by the beamforming.

[0186] Aspect 18: A method of wireless communication performed by a distributed unit (DU), comprising: transmitting to a radio unit (RU) a control plane message associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, wherein the control plane message includes information applied to all resource blocks and space layers in an indicated carrier or band sector group.

[0187] Aspect 19: The method according to aspect 18, wherein the control plane message includes an indication of the segment type for information specifically applied to all resource blocks and space layers in a carrier or band sector group, and a segment header associated with the segment type, wherein the segment header includes the information applied to all resource blocks and space layers in the indicated carrier or band sector group.

[0188] Aspect 20: The method according to aspect 19, wherein the segment header includes an indication of an extended antenna-carrier (eAxC) mask, the extended antenna-carrier (eAxC) mask identifying an indicated carrier or band sector group for which the information included in the segment header is applied.

[0189] Aspect 21: The method according to any one of Aspects 19-20, wherein the information included in the segment header includes time-domain duplex (TDD) configurations applied to all resource blocks and spatial layers in the indicated carrier or frequency band sector group.

[0190] Aspect 22: The method according to any one of Aspects 19-21, wherein the information included in the segment header includes patterns of idle and active symbols for all resource blocks and space layers in the indicated carrier or band sector group.

[0191] Aspect 23: The method according to any one of aspects 19-22, wherein the segment header includes an indication of a symbol for applying the information included in the segment header to a time slot.

[0192] Aspect 24: The method according to any one of aspects 18-23, wherein the information included in the control plane message includes analog beamforming information for an indicated carrier or band sector group.

[0193] Aspect 25: The method according to aspect 24, wherein the control plane message includes a segment header associated with the segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and wherein the analog beamforming information is included in the analog beamforming extension in the segment header.

[0194] Aspect 26: The method according to any of Aspects 24-25, wherein, for each carrier in an indicated group of carriers or frequency band sectors, the analog beamforming information includes an indication of a corresponding analog beam applied to all resource blocks and space layers in that carrier.

[0195] Aspect 27: The method according to aspect 26, wherein, for each carrier in the indicated carrier or band sector group, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0196] Aspect 28: A method of wireless communication performed by a distributed unit (DU), comprising: transmitting to a radio unit (RU) a control plane message including analog beamforming information applied to all resource blocks and space layers in one or more carriers.

[0197] Aspect 29: According to the method of aspect 28, wherein, for each of the one or more carriers, the simulated beamforming information includes an indication of a corresponding simulated beam applied to all resource blocks and space layers in that carrier.

[0198] Aspect 30: The method according to aspect 29, wherein, for each of the one or more carriers, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, and wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

[0199] Aspect 31: The method according to any one of Aspects 28-30, wherein the control plane message is associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group.

[0200] Aspect 32: The method according to any one of Aspects 28-31, wherein the control plane message includes a segment header associated with a segment type dedicated to information applied to all resource blocks and space layers in a carrier or band sector group, and wherein the analog beamforming information is included in an analog beamforming extension in the segment header.

[0201] Aspect 33: An apparatus for wireless communication at 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 apparatus to perform the method according to one or more of aspects 1-11.

[0202] Aspect 34: An apparatus for wireless communication at 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 apparatus to perform the method according to one or more aspects of aspects 12-17.

[0203] Aspect 35: An apparatus for wireless communication at 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 apparatus to perform the method according to one or more aspects of aspects 18-27.

[0204] Aspect 36: An apparatus for wireless communication at 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 apparatus to perform the method according to one or more aspects of aspects 28-32.

[0205] Aspect 37: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the methods of one or more aspects of aspects 1-11.

[0206] Aspect 38: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the methods of one or more aspects of aspects 12-17.

[0207] Aspect 39: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the methods of one or more aspects of aspects 18-27.

[0208] Aspect 40: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the methods of one or more aspects of aspects 28-32.

[0209] Aspect 41: An apparatus for wireless communication, comprising at least one unit for performing the methods of one or more aspects of aspects 1-11.

[0210] Aspect 42: An apparatus for wireless communication, comprising at least one unit for performing the methods of one or more aspects of aspects 12-17.

[0211] Aspect 43: An apparatus for wireless communication, comprising at least one unit for performing the methods of one or more aspects of aspects 18-27.

[0212] Aspect 44: An apparatus for wireless communication, comprising at least one unit for performing the methods of one or more aspects of aspects 28-32.

[0213] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform methods of one or more aspects of aspects 1-11.

[0214] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform methods of one or more aspects of aspects 12-17.

[0215] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform methods of one or more aspects of aspects 18-27.

[0216] Aspect 48: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform methods of one or more aspects of aspects 28-32.

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

[0218] Aspect 50: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 12-17.

[0219] Aspect 51: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 18-27.

[0220] Aspect 52: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 28-32.

[0221] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from practice in the various aspects.

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

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

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

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

Claims

1. A radio unit (RU) for wireless communication, comprising: Memory; as well as One or more processors coupled to the memory are configured to: Receive a control plane message indicating a segment type from a distributed unit (DU), the segment type indicating that the control plane message includes information applicable to multiple spatial layers. The header of the control plane message includes a direction mode field indicating the time-domain duplex (TDD) configuration applied to the plurality of spatial layers, the direction mode field including multiple bits indicating a separate uplink or downlink direction for a symbol of a time slot; as well as The information applied to the multiple spatial layers is used for communication, at least in part based on the segment type.

2. The RU according to claim 1, wherein, The control plane message includes a segment header associated with the segment type, wherein the segment header includes the information applied to the plurality of spatial layers.

3. The RU according to claim 2, wherein, The segment header includes an indication of an extended antenna-carrier (eAxC) mask, which identifies the plurality of spatial layers to which the information included in the segment header is applied.

4. The RU according to claim 2, wherein, The information included in the segment header includes the TDD configuration.

5. The RU according to claim 2, wherein, The information included in the segment header includes patterns for idle and active symbols applied to the multiple spatial layers.

6. The RU according to claim 1, wherein, The control plane message includes the segment header containing an indication of the symbols included in the segment header for the information in the time slot.

7. The RU according to claim 1, wherein, The information included in the control plane message includes simulated beamforming information for the plurality of space layers.

8. The RU according to claim 7, wherein, The control plane message includes a segment header associated with the segment type, and wherein the analog beamforming information is included in the analog beamforming extension in the segment header.

9. The RU according to claim 7, wherein, For each carrier in an indicated carrier or band sector group, the analog beamforming information includes an indication of the corresponding analog beams applied to all resource blocks and space layers in that carrier.

10. The RU according to claim 9, wherein, For each carrier in the indicated carrier or band sector group, the indication for the corresponding analog beam includes an indication for a beam identifier for the corresponding analog beam, wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

11. The RU according to claim 1, wherein, The one or more processors are further configured to: At least in part, based on the information applied to the plurality of space layers, one or more beams generated by beamforming are used to communicate with the user equipment (UE).

12. A radio unit (RU) for wireless communication, comprising: Memory; as well as One or more processors coupled to the memory are configured to: The control plane message received from the distributed unit (DU) includes simulated beamforming information applied to multiple space layers, at least in part based on a segment type indicated by a control plane message, the segment type indicating that the control plane message includes information applicable to the multiple space layers. The header of the control plane message includes a direction mode field indicating the time-domain duplex (TDD) configuration applied to the plurality of spatial layers, the direction mode field including multiple bits indicating a separate uplink or downlink direction for a symbol of a time slot; as well as The simulated beamforming information applied to the multiple spatial layers is used for communication, at least in part based on the segment type.

13. The RU according to claim 12, wherein, For each of the one or more carriers, the simulated beamforming information includes an indication of the corresponding simulated beams applied to all resource blocks and space layers in that carrier.

14. The RU according to claim 13, wherein, For each of the one or more carriers, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

15. The RU according to claim 12, wherein, The segment type is specifically used for information applied to all resource blocks and spatial layers within a carrier or band sector group.

16. The RU according to claim 12, wherein, The control plane message includes a segment header associated with the segment type, and wherein the simulated beamforming information is included in the simulated beamforming extension in the segment header.

17. The RU according to claim 12, wherein, The one or more processors are further configured to: The user equipment (UE) communicates using one or more beams generated by the beamforming.

18. A method for wireless communication performed by a radio unit (RU), comprising: Receive a control plane message indicating a segment type from a distributed unit (DU), the segment type indicating that the control plane message includes information applicable to multiple spatial layers. The header of the control plane message includes a direction mode field indicating the time-domain duplex (TDD) configuration applied to the plurality of spatial layers. The direction mode field includes multiple bits indicating a separate uplink or downlink direction for a symbol of a time slot. The information applied to the multiple spatial layers is used for communication, at least in part based on the segment type.

19. The method according to claim 18, wherein, The control plane message includes a segment header associated with the segment type, wherein the segment header includes the information applied to the plurality of spatial layers.

20. The method according to claim 19, wherein, The segment header includes an indication of an extended antenna-carrier (eAxC) mask, which identifies the plurality of spatial layers for which the information included in the segment header is applied.

21. The method according to claim 19, wherein, The information included in the segment header includes the TDD configuration.

22. The method according to claim 19, wherein, The information included in the segment header includes patterns for idle and active symbols applied to the multiple spatial layers.

23. The method according to claim 18, wherein, The control plane message includes the segment header containing an indication of the symbols included in the segment header for the information in the time slot.

24. The method according to claim 18, wherein, The information included in the control plane message includes simulated beamforming information for the plurality of space layers.

25. The method according to claim 24, wherein, The control plane message includes a segment header associated with the segment type, and wherein the analog beamforming information is included in the analog beamforming extension in the segment header.

26. The method according to claim 24, wherein, For each carrier in an indicated carrier or band sector group, the analog beamforming information includes an indication of the corresponding analog beams applied to all resource blocks and space layers in that carrier.

27. A method for wireless communication performed by a radio unit (RU), comprising: The control plane message received from the distributed unit (DU) includes simulated beamforming information applied to multiple space layers, at least in part based on a segment type indicated by a control plane message, the segment type indicating that the control plane message includes information applicable to the multiple space layers. The header of the control plane message includes a direction mode field indicating the time-domain duplex (TDD) configuration applied to the plurality of spatial layers. The direction mode field includes multiple bits indicating a separate uplink or downlink direction for a symbol of a time slot. The simulated beamforming information applied to the multiple spatial layers is used for communication, at least in part based on the segment type.

28. The method according to claim 27, wherein, For each of one or more carriers, the simulated beamforming information includes an indication of the corresponding simulated beams applied to all resource blocks and space layers within that carrier.

29. The method according to claim 28, wherein, For each of the one or more carriers, the indication for the corresponding analog beam includes an indication of a beam identifier for the corresponding analog beam, wherein the beam identifier for the corresponding analog beam is mapped to an antenna element weight set for the corresponding analog beam.

30. The method according to claim 27, wherein, The control plane message includes a segment header associated with the segment type, and wherein the simulated beamforming information is included in the simulated beamforming extension in the segment header.

Images