Open radio unit group identifier

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, an open distributed unit (O-DU) may generate a unique group identifier (ID) for each of one or more user groups, each user group including a group of user equipments (UEs) sharing time-frequency resources in a time slot but occupying a different spatial layer. The O-DU may send one or more messages to an open radio unit (O-RU), each message associated with a respective user group including a group ID for the respective user group. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 587,422, filed October 2, 2023, entitled “OPEN RADIO UNIT GROUPIDENTIFIERS,” and U.S. Non-Provisional Patent Application No. 18 / 894,464, filed September 24, 2024, entitled “OPEN RADIO UNIT GROUP IDENTIFIERS,” both of which are assigned to the assignee of this patent application. The disclosures of these earlier applications are considered part of this patent application and are incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication in general, and to technologies and apparatus associated with Open Radio Unit (O-RU) user groups. 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 employ 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 / LTE-Advanced 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 network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] Some aspects described herein relate to a method for wireless communication performed by a network entity. The method may include generating a unique group identifier (ID) for each of one or more user groups, each user group comprising user equipment (UEs) sharing time-frequency resources in a time slot but occupying different spatial layers. The method may include sending one or more messages to an open radio unit (O-RU), wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to that corresponding user group.

[0008] Some aspects described herein relate to a method for wireless communication performed by a network entity. The method may include receiving one or more messages from an Open Distributed Unit (O-DU), each of the one or more messages including a group ID of a user group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. The method may include classifying the one or more messages into corresponding user groups based at least in part on these group IDs. The method may include generating one or more beam weights for the spatial layer associated with each corresponding user group based at least in part on spatial layer information from other coordination degrees of the corresponding user group.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include: one or more memories; and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the network entity to: generate a unique group ID for each of one or more user groups, each user group comprising a group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. The one or more processors may be individually or collectively configured to cause the network entity to send one or more messages to an O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a unique group ID for that corresponding user group.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include: one or more memories; and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the network entity to receive one or more messages from an O-DU, each of the one or more messages including a group ID of a user group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. The one or more processors may be individually or collectively configured to cause the network entity to classify the one or more messages into corresponding user groups based at least in part on these group IDs. The one or more processors may be individually or collectively configured to cause the network entity to generate one or more beam weights for the spatial layer associated with each corresponding user group based at least in part on spatial layer information from other coordination degrees of the corresponding user group.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. When executed by one or more processors of the network entity, the set of instructions enables the network entity to generate a unique group ID for each of one or more user groups, each user group comprising a group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. When executed by one or more processors of the network entity, the set of instructions enables the network entity to send one or more messages to an O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a unique group ID for that corresponding user group.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. When executed by one or more processors of the network entity, the set of instructions enables the network entity to receive one or more messages from an O-DU, each of the one or more messages including a group ID of a user group of UEs sharing time-frequency resources in a shared time slot but occupying different spatial layers. When executed by one or more processors of the network entity, the set of instructions enables the network entity to group the one or more messages into corresponding user groups, at least in part, based on the group ID. When executed by one or more processors of the network entity, the set of instructions enables the network entity to generate one or more beam weights for the spatial layer associated with each corresponding user group, at least in part, based on spatial layer information from other coordination degrees of the corresponding user group.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for generating a unique group ID for each of one or more user groups, each user group comprising a group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. The apparatus may also include components for sending one or more messages to an O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to that corresponding user group.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving one or more messages from an O-DU, each of the one or more messages including a group ID of a user group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. The apparatus may include components for classifying the one or more messages into corresponding user groups, at least in part based on these group IDs. The apparatus may include components for generating one or more beam weights for the spatial layer associated with each corresponding user group, at least in part based on spatial layer information from other coordination degrees of the corresponding user group.

[0015] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0016] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. 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, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0017] While aspects are described herein by way of example, 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 implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, 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 practicing 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 practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0018] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

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

[0021] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0022] Figure 4 This is a diagram illustrating an example of a feature associated with a feature supported by an Open Distributed Unit (O-DU) according to this disclosure.

[0023] Figure 5 This is a diagram illustrating an example of an O-DU using a user group identifier (ID) according to this disclosure.

[0024] Figure 6 This is a diagram illustrating an example of an O-DU using a user group ID according to this disclosure.

[0025] Figure 7 This is a diagram illustrating an example of an O-DU using a user group ID according to this disclosure.

[0026] Figure 8 This is a diagram illustrating an example of using a user group ID for an Open Radio Unit (O-RU) message according to this disclosure.

[0027] Figure 9 This is a diagram illustrating an example process performed, for example, at a network entity or a device of a network entity, according to the present disclosure.

[0028] Figure 10 This is a diagram illustrating an example process performed, for example, at a network entity or a device of a network entity, according to the present disclosure.

[0029] Figure 11 This is a diagram of an example device for wireless communication according to the present disclosure.

[0030] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0031] Communication systems, such as 5G New Radio (NR) systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, base stations, or network equipment can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5G NB, access points (APs), transmit / receive points (TRPs), or cells, etc.) or one or more units (or components) performing base station functionality can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations. Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize protocol stacks physically or logically distributed between two or more units (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). Decomposed base stations can be utilized in open radio access networks (O-RAN, such as network configurations initiated by the O-RAN Alliance) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed separately.

[0032] An Open RU (O-RU) can receive messages from an Open DU (O-DU). These messages can be associated with a UE and can partially overlap across multiple user multiple-input multiple-output (MU-MIMO) user groups. Each user group may include time-frequency resource allocations (e.g., resource blocks (RBs)) within a time slot. UEs within the same user group may share time-frequency resources but are assigned to different spatial layers. Constructing MU-MIMO user groups from per-UE / per-layer control plane (C-plane) segments (information messages) requires a considerable amount of O-RU processing, which is spent identifying these partial overlaps and constructing separate MU-MIMO user groups from per-UE / per-layer segment. Directly using segments such as segment 5 and segment extension 10 (ST 5+SE 10) to transmit MU-MIMO user groups via O-DUs does not allow for per-UE or per-layer O-DU C-plane implementation.

[0033] According to the various aspects described herein, the O-DU can generate group IDs to identify user groups, where each user group has a unique group ID. When the O-DU sends a message, it can generate a group ID and assign it to the message to identify the user group to which the message belongs. In some aspects, the message may include a segment. For example, the message may be in a segment (e.g., ST 5 or a new segment type). In some aspects, the message may include fields or segments specific to the group ID. In some aspects, the message may include extensions to the segment. The O-RU can receive messages and use the group ID assigned to the user group to classify the message into the user group. The O-RU can generate one or more beam weights for the spatial layer associated with each corresponding user group, at least in part, based on information from other spatial layers of coordination from the corresponding user group. Each layer can influence the beam weights of another layer, especially for adjacent layers. This information may include pilot information, such as pilot signals associated with channel estimation. The O-RU can use the beam weights from signals from the UE to form a receive beam.

[0034] Group IDs allow the O-DU to send C-plane messages per layer, per UE, per Code Division Multiplexing (CDM) group, or per MU-MIMO user group, while allowing the O-RU to use unique group IDs to simplify MU-MIMO group derivation. By having the O-DU generate and assign group IDs to user groups, rather than having the O-RU figure out how to organize user group messages, the O-RU saves processing resources and reduces latency. User group IDs enable the O-RU to identify each group of users across different spatial layers within the same time-frequency resource and determine beam weights that account for any interference between different spatial layers. User group IDs remove the complexity of determining user coverage across different spatial layers from the O-RU.

[0035] 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 comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently 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 of practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods implemented using structures, functions, or structures and functions other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0036] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0037] While terms generally associated with 5G or NR radio access technology (RAT) may be used to describe aspects herein, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0038] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more CUs, one or more DUs, or one or more RUs).

[0039] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via radio access links. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via fronthaul or midhaul links. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via midhaul links or with the core network via backhaul links. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, TRPs, DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0040] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0041] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. Thus, a single device can include more than one base station.

[0042] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, or repeater, etc.

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

[0044] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0045] 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, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0046] Some UEs 120 may 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, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer 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.

[0047] Generally, 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 be referred to as a radio technology or air interface, etc. A frequency can be referred to as a carrier or frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0048] 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 network node 110 as an intermediary device 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 network node 110.

[0049] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0051] Considering the examples above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0052] In some aspects, network entities (e.g., network node 110) may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may generate a unique group identifier (ID) for each of one or more user groups, each user group comprising UEs that share time-frequency resources in a time slot but occupy different spatial layers. Communication manager 150 may send one or more messages to the O-RU, each of the one or more messages being associated with a corresponding user group and including a group ID unique to the corresponding user group. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0053] In some aspects, network entities (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive one or more messages from the O-DU, each of which includes a group ID of a user group of UEs sharing time-frequency resources in a time slot but occupying different spatial layers. The communication manager 150 may classify one or more messages into corresponding user groups based at least in part on the group ID. The communication manager 150 may generate one or more beam weights for the spatial layer associated with each corresponding user group based at least in part on spatial layer information from other coordination degrees of the corresponding user group. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0054] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0055] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 110 may be equipped with a set of antennas 234a to 234t, such as... T One antenna ( T ≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0056] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and can provide data symbols 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, grants, 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 signals (CRS) or demodulation reference signals (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., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T Each output symbol stream is provided to the corresponding set of modems 232 (e.g., ...). T Each modem 232a to 232t can be used to process a corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. For example, each output symbol stream can be provided to a modulator component (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 also 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 be used via a corresponding antenna set 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0057] At UE 120, antenna set 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can store the set of received signals (e.g., R The received signals are provided to the modem set 254 (e.g., RA modem 254 (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may 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 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0058] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0059] 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 sets 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 sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, 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 a )

[0060] 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 generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 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 transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 4 to 12 ( ) any aspect of the methods described in the method.

[0061] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 for scheduling one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 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. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., references). Figures 4 to 12 ( ) any aspect of the methods described in the method.

[0062] The controller / processor of the network entity (e.g., controller / processor 240 of network node 110), the controller / processor 280 of UE 120, and / or Figure 2 Any other component may perform one or more technologies associated with the selection and indication of O-RU capabilities, as described in more detail elsewhere herein. The O-RU and O-DU described herein may be network entities or may be included within network entities. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 9 The process 900 Figure 10 The operation of process 1000 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 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, these one or more instructions may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 9 The process 900 Figure 10 The operation of process 1000 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0063] In some aspects, a network entity configured to operate as an O-DU (e.g., network node 110) includes components for: generating a unique group ID for each of one or more user groups, each user group comprising groups of UEs sharing time-frequency resources in a time slot but occupying different spatial layers (e.g., using controller / processor 240, memory 242, etc.); and / or components for sending one or more messages to the O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a unique group ID for that corresponding user group (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, memory 242, etc.). In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0064] In some aspects, a network entity configured to operate as an O-RU (e.g., network node 110) includes components for receiving one or more messages from an O-DU, each of which includes a group ID of a user group of UEs that share time-frequency resources in a time slot but occupy different spatial layers (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.); components for classifying one or more messages into the corresponding user group based at least in part on the group ID (e.g., using controller / processor 240, memory 242, etc.); and / or components for generating one or more beam weights for the spatial layer associated with each corresponding user group based at least in part on spatial layer information from other coordination degrees of the corresponding user group (e.g., using controller / processor 240, memory 242, etc.).

[0065] In some respects, a single processor can perform all functions described as being executed by that one or more processors. In other respects, the one or more processors can jointly execute a set of functions. For example, a first set (one or more) of the one or more processors can perform a first function described as being executed by that one or more processors, and a second set (one or more) of the one or more processors can perform a second function described as being executed by that one or more processors. The processors in the first set and the processors in the second set can be the same set of processors or they can be different sets of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. Figure 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... Figure 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

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

[0067] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2The examples described are different.

[0068] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as an NB, eNB, NR base station, 5G NB, AP, TRP, or cell, etc.) or one or more units (or components) performing base station functions can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0069] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0070] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, O-RAN (such as network configurations initiated by the O-RAN Alliance), or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed individually. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0071] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0072] Each of these units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO frame 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, may be configured to communicate with one or more other units via transmission media. In some examples, each of these units may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more other units, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more other units, or both.

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

[0074] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0075] Each RU 340 can implement lower-layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0076] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

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

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

[0079] DU and RU can exchange management configurations on the management plane (M plane) between DU and RU. RU can advertise O-RU capabilities via the M plane (e.g., via parameters of a modeling language such as YANG or other data modeling / network configuration / management languages). O-RU capabilities may include endpoint capabilities, which are the ability to process data streams at the sending endpoint (e.g., static low-level sending endpoint) or the receiving endpoint (e.g., static low-level receiving endpoint) of the data stream.

[0080] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0081] Figure 4 This is an illustration of example 400 associated with features supported by O-DU according to this disclosure.

[0082] Example 400 illustrates a MU-MIMO scenario with four UEs (UE1, UE2, UE3, and UE4). The O-RU can receive messages from the O-DU. These messages can be specific to a UE and can partially overlap across multiple MU-MIMO user groups. For example, message 402 could be specific to UE4 but span resource allocations (e.g., RBs) for user groups 410, 412, 414, and 416. Message 404 could be specific to UE3 in user group 410. Message 406 could be specific to UE2 across user groups 410, 412, and 414. Message 408 could be specific to UE1 across user groups 410 and 412.

[0083] Each user group may include UEs that share time-frequency resources in a time slot but are in different spatial layers. That is, no two UEs can be in the same spatial layer in a time slot. Multiple layers can be scheduled for some UEs. For example, message 406 is for UE2 in multiple spatial layers (layer 2, layer 3), and message 408 is for UE1 in multiple spatial layers (layer 0 and layer 1).

[0084] Partial overlap can be described by the O-DU using per-UE or per-layer C-plane segments, which are formatted control messages. For example, a layer segment description (e.g., description #1) may include: segment 5 (ST 5) for RB0-RB99, ueId-30. Segment description #2 (one layer) may include ST 5 for RB0-RB18, ueId-24. Segment description #3 (two layers) may include ST 5 + segment 10 (SE 10) for RB0-RB46, ueId-10 and 11. Segment description #4 (two layers) may include ST 5 + SE 10 for RB0-RB33, ueId-1 and 2.

[0085] Constructing MU-MIMO user groups from per UE / per layer C-plane segment requires a considerable amount of O-RU processing, which is incurred to identify these partial overlaps and construct MU-MIMO user groups from per UE / per layer segment. Directly using SE5+SE10 to transmit MU-MIMO user groups in the O-DU does not allow for per-UE or per layer O-DU C-plane implementation.

[0086] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The descriptions are different.

[0087] Figure 5 This is an example diagram illustrating an O-DU using a user group ID according to this disclosure.

[0088] According to the various aspects described herein, the O-DU can generate group IDs to identify user groups, each user group having a unique group ID. When the O-DU sends a message, it can generate a group ID and assign it to the message to identify the user group to which the message belongs. In some aspects, the message may include segments. For example, the message may be in a segment (e.g., ST 5 or new ST 12). In some aspects, the message may include fields or segments specific to indicating the group ID.

[0089] In some respects, the message may include extensions to the segment. For example, the group ID may be a DMRS group ID that is part of the DMRS segment extension “X” specification. Segment extension “X” may be a new extension for transmitting DMRS configuration and DMRS port information, as well as ST 5 for DMRS beamforming (BF). The C-plane segment of the MU-MIMO subscriber group may be populated with this unique group ID in the segment extension “X”.

[0090] The O-RU can receive messages and classify them into user groups using group IDs assigned to user groups. The O-RU can generate one or more beam weights for each spatial layer in or associated with each corresponding user group, based at least in part on information from other spatial layers of coordination from the corresponding user group. Each layer can influence the beam weights of another layer, especially for adjacent layers. This information may include pilot information, such as pilot signals associated with channel estimation.

[0091] Group IDs allow O-DUs to use per-layer, per-UE, per-CDM group, or MU-MIMO group C-plane messaging, while allowing O-RUs to use unique group IDs to simplify MU-MIMO group export. By having O-DUs generate and assign group IDs to user groups, rather than having O-RUs figure out how to organize user group messages, O-RUs save processing resources and reduce latency.

[0092] Example 500 illustrates user groups 410 to 416. MU-MIMO user group 1 (RB0-RB18) may include UE ID 1, UE ID 2, UE ID 10, UE ID 11, UE ID 24, and UE ID 30 mapped to layers 0-5. MU-MIMO user group 2 (RB19-RB33) may include UE ID 1, UE ID 2, UE ID 10, and UE ID 11 mapped to layers 0-3, and UE ID 30 mapped to layer 5. MU-MIMO user group 3 (RB34-RB46) may include UE ID 10 and UE ID 11 mapped to layers 2-3, and UE ID 30 mapped to layer 5. MU-MIMO user group 4 (RB47-RB99) may include UE ID 30 mapped to layer 5.

[0093] In some respects, the O-DU can use a separate C-plane segment to indicate each stratum in the MU-MIMO user group. The SE "X" can be used to indicate the DMRS port assignment for that stratum, as well as other DMRS configuration information, including the DMRS group ID. The O-RU can use a common DMRS group ID spanning the ST 5 segment to identify all strata in the MU-MIMO user group. Such per-stratum messaging may include, for example: Layer 0 (ueID1) Segment 0-Segment 1: ST 5+SE“X” RB0-RB18: DMRS GroupId=0 RB19-RB33: DMRS GroupId=1 Layer 1 (ueId2) Segment 2-Segment 3: ST 5+SE“X” RB0-RB18: DMRS GroupId=0 RB19-RB33: DMRS GroupId=1 Layer 2 (ueId10) Segment 4-Segment 6: ST 5+SE“X” RB0-RB18: DMRS GroupId=0 RB19-RB33: DMRS GroupId=1 RB34-RB46: DMRS GroupId=2 Layer 3 (ueId11) Segment 7-Segment 9: ST 5+SE“X” RB0-RB18: DMRS GroupId=0 RB19-RB33: DMRS GroupId=1 RB34-RB46: DMRS GroupId=2 Layer 4 (ueId24) Segment 10: ST 5+SE“X” RB0-RB18: DMRS GroupId=0 Layer 3 (ueId11) Segment 11-Segment 15: ST 5+SE“X” RB0-RB18: DMRS GroupId=0 RB19-RB33: DMRS GroupId=1 RB34-RB46: DMRS GroupId=2 RB34-RB46: DMRS GroupId=3 As indicated above, Figure 5This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0094] Figure 6 This is an example diagram 600 illustrating the use of a user group ID in accordance with this disclosure for an O-DU.

[0095] In some respects, the O-DU can use SE 10 to group UE layers within a C-plane segment. SE "X" can indicate a list of DMRS ports for all UE layers, along with other DMRS configuration information, including the common DMRS GroupId. The O-RU can use the common DMRS GroupId across ST5 segments to identify all UEs in a MU-MIMO user group. Examples of this information may include: UE1 (ueID1,2) segment #1: ST 5+SE 10+SE“X” RB0-RB18: ueId 1,2 with DMRS GroupId 0 Section #2: ST 5 + SE 10 + SE“X” RB19-RB33: ueId 1,2 with DMRS GroupId 1 UE2 (ueID10,11) segment #3: ST 5+SE 10+ SE“X” RB0-RB18: ueId 10,11 with DMRS GroupId 0 Section #4: ST 5 + SE 10 + SE“X” RB19-RB33: ueId 10,11 with DMRS GroupId 1 Section #5: ST 5 + SE 10 + SE“X” RB34-RB46: ueId 10,11 with DMRS GroupId 2 UE2 (ueID24) segment #6: ST 5+SE “X” RB19-RB33: ueId 24 with DMRS GroupId 0 UE3 (ueID30) segment #7: ST 5+SE “X” RB0-RB18: ueId 30 with DMRS GroupId 0 Section #8: ST 5 + SE“X” RB19-RB33: ueId 30 with DMRS GroupId 1 Section #9: ST 5 + SE“X” RB34-RB46: ueId 30 with DMRS GroupId 2 Section #10: ST 5 + SE“X” RB34-RB46: ueId 30 with DMRS GroupId 3 As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0096] Figure 7 This is an example 700 illustrating an O-DU using a user group ID according to this disclosure.

[0097] In some respects, the O-DU can optionally combine all MU-MIMO user group layers to create an optimal C-plane using SE 10. The O-DU can use an M-plane switch to control the operating mode. SE "X" can be used to indicate the list of DMRS ports for all MU-MIMO group layers, as well as other DMRS configuration information such as the DMRS GroupId. Since all MU-MIMO user group layers are indicated using a single C-plane segment, the O-RU may not need to aggregate layer information across multiple ST 5 segments. The DMRS GroupId can be optional.

[0098] Examples of this information may include: MU-MIMO User Group #1 Section #1: ST 5 + SE 10 + SE“X” RB0-RB18: ueId 1,2 with DMRS GroupId 0 MU-MIMO User Group #2 Section #2: ST 5 + SE 10 + SE“X” RB19-RB33: ueId 1, 2, 10, 11, 30 with DMRS GroupId 1 MU-MIMO User Group #3 Section #3: ST 5 + SE 10 + SE“X” RB34-RB46: ueId 10, 11, 30 with DMRS GroupId 2 MU-MIMO User Group #4 Section #4: ST 5 + SE“X” RB47-RB99: ueId 30 with DMRS GroupId 3 As indicated above, Figure 7This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0099] Figure 8 This is a diagram illustrating example 800 of using a user group ID in an O-RU message according to this disclosure. (See diagram 800 for example 800.) Figure 8 As shown, O-RU 820 (e.g., network node 110) and O-DU 810 (e.g., network node) can communicate with each other in a decomposed base station architecture such as decomposed base station architecture 300. O-RU 820 can communicate with one or more UEs such as UE 830 (e.g., UE 120).

[0100] Example 800 illustrates an example of generating a group ID and using it in O-RU messages. As shown by reference numeral 835, the O-DU 810 can generate a group ID for each user group. The O-DU 810 can consider UEs sharing the same time-frequency resources in a time slot and select them into the same user group. The O-DU 810 can also select UEs for user groups based at least in part on UE location, UE type, and / or UE capabilities. As shown by reference numeral 840, the O-DU 810 can send one or more messages, each message including the group ID of the corresponding user group associated with that message.

[0101] As shown by reference numeral 845 in the attached figure, the O-RU 820 can classify messages into appropriate user groups based on group IDs. Classification may include identifying which user group a message belongs to, at least in part, based on the group ID in the message. This can be advantageous because messages can be received from various UEs at different times. The O-RU 820 can save processing resources and without increasing latency by using group IDs.

[0102] As shown by reference numeral 850, the O-RU 820 can generate beam weights for spatial layers within a user group. For example, the O-RU 820 can generate one or more beam weights for each spatial layer, at least in part, based on information from each of the other spatial layers (e.g., pilot signals used for channel estimation). The O-RU 820 can form beams with beam weights to receive signals from the UE on these layers without excessive interference between them. As shown by reference numeral 855, the O-RU can utilize this beam to receive signals from the UE (such as UE 830). The O-RU 820 can receive signals and process information in the signals at the spatial layers. As shown by reference numeral 860, the O-RU 820 can transmit the spatial layer (spatial layer information) to the O-DU 810.

[0103] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0104] Figure 9 This is a diagram illustrating an example process 900 performed, for example, at a network entity or a device of a network entity, according to the present disclosure. Example process 900 is an example in which a device or network entity (e.g., network node 110, O-DU 810) performs an operation associated with using a group ID for an O-RU message.

[0105] like Figure 9 As shown, in some aspects, process 900 may include generating a unique group ID for each of one or more user groups, each user group comprising groups of UEs that share the same time-frequency resources in a shared time slot but occupy different spatial layers (box 910). O-DU 810 is used to resolve any partial sharing before assigning group IDs. For example, network entities (e.g., using...) Figure 11 The communication manager 1106 described herein can generate a unique group ID for each of one or more user groups. Each user group includes groups of UEs that share time-frequency resources in a time slot but occupy different spatial layers, as shown in the example above. Figure 5 , Figure 6 , Figure 7 and / or Figure 8 As described.

[0106] like Figure 9 Further shown, in some aspects, process 900 may include sending one or more messages to the O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to that corresponding user group (box 920). For example, network entities (e.g., using...) Figure 11 The communication manager 1106 and / or sending component 1104 depicted herein can send one or more messages to the O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to that corresponding user group, as shown above, for example, in reference to Figure 5 , Figure 6 , Figure 7 and / or Figure 8 As described. Each message is associated with a corresponding user group and includes the group ID of that user group.

[0107] Process 900 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.

[0108] In the first aspect, the network entity includes an O-DU, and the O-DU is configured to select a user (UE) for a user group in one or more user groups.

[0109] In the second aspect, either alone or in combination with the first aspect, each of the one or more messages includes a segment.

[0110] In the third aspect, either alone or in combination with one or more of the first and second aspects, each of the one or more messages includes an extension attached to the segment.

[0111] In the fourth aspect, the extension includes the DMRS extension, either alone or in combination with one or more of the first to third aspects.

[0112] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, each of the one or more messages includes a field specific to the indicator group ID.

[0113] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0114] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, at a network entity or a device of a network entity, according to the present disclosure. Example process 1000 is an example in which a device or network entity (e.g., network node 110, O-RU 820) performs an operation associated with using a group ID for an O-RU message.

[0115] like Figure 10 As shown, in some aspects, process 1000 may include receiving one or more messages from the O-DU, each message including a group ID of a user group of UEs that share time-frequency resources in a time slot but occupy different spatial layers (box 1010). For example, a network entity (e.g., using...) Figure 12 The communication manager 1206 and / or receiving component 1202 depicted herein can receive one or more messages from the O-DU, each message including the group ID of a user group of a UE that shares time-frequency resources in a time slot but occupies a different spatial layer, as shown above, for example, in reference to Figure 5 , Figure 6 , Figure 7 and / or Figure 8 As described.

[0116] like Figure 10 As further shown, in some aspects, process 1000 may include classifying one or more messages into appropriate user groups based at least in part on group IDs (box 1020). For example, network entities (e.g., using...) Figure 12The communication manager 1206 described herein can classify one or more messages into corresponding user groups, at least in part, based on group IDs, as illustrated above, for example, in reference to [reference missing]. Figure 5 , Figure 6 , Figure 7 and / or Figure 8 As described.

[0117] like Figure 10 Further shown, in some aspects, process 1000 may include generating one or more beam weights for the spatial layer in or associated with each corresponding user group, at least in part based on information from other spatial layers of coordination from the corresponding user group (box 1030). For example, network entities (e.g., using...) Figure 12 The communication manager 1206 described herein can generate one or more beam weights for each spatial layer in or associated with each corresponding user group, based at least in part on information from other spatial layers of coordination from the corresponding user group, as described above, for example, in reference to Figure 5 , Figure 6 , Figure 7 and / or Figure 8 As described.

[0118] 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.

[0119] In the first aspect, network entities include O-RUs.

[0120] In the second aspect, either alone or in combination with the first aspect, the information includes pilot signals associated with channel estimation.

[0121] In the third aspect, either alone or in combination with one or more of the first and second aspects, each of the one or more messages includes a segment.

[0122] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, each of the one or more messages includes an extension attached to the segment.

[0123] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the extension includes the DMRS extension.

[0124] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, each of the one or more messages includes a field specifically for indicating the group ID.

[0125] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1000 includes receiving one or more signals from one or more UEs, beamforming the one or more signals being received with one or more beam weights to generate a spatial layer; and transmitting the spatial layer for the one or more signals to the O-DU.

[0126] although Figure 10 An example box of process 1000 is shown, but in some respects, process 1000 may include... Figure 10 The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0127] Figure 11 This is a diagram of an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be an O-DU, or an O-DU may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... Figure 1 The described communication manager 150. As shown, device 1100 can communicate with another device 1108 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1102 and transmitting component 1104.

[0128] In some respects, device 1100 can be configured to perform the functions described herein. Figures 1 to 8 The described one or more operations. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 9 The process is 900. In some respects, Figure 11 The illustrated device 1100 and / or one or more components may include a combination Figure 2 One or more components of the described O-DU. Additionally or alternatively, Figure 11 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

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

[0130] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and may transmit the processed signals to device 1108. In some aspects, transmitting component 1104 may include combinations of... Figure 2 The described O-DU includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

[0131] The communication manager 1106 may support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 may receive information associated with configuring the receiving component 1102 to receive communication and / or the transmitting component 1104 to transmit communication. Additionally or alternatively, the communication manager 1106 may generate control information and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 to control the receiving and / or transmitting of communication.

[0132] The communication manager 1206 can generate a unique group ID for each of one or more user groups, each user group comprising UEs that share time-frequency resources in a time slot but occupy different spatial layers. The transmitting component 1204 can send one or more messages to the O-RU, wherein each of the one or more messages is associated with a corresponding user group and includes a unique group ID for the corresponding user group.

[0133] Figure 11 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The collection of (one or more) components shown is executable and described as being composed of Figure 11 Another set of components shown performs one or more functions.

[0134] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be an O-RU, or an O-RU may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1206 is combined with... Figure 1 The described communication manager 150. As shown, device 1200 can communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1202 and transmitting component 1204.

[0135] In some respects, device 1200 can be configured to perform the functions described herein. Figures 1 to 8 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 10 The process is 1000. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described O-RU. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

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

[0137] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described O-RU includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.

[0138] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the reception of communications by the receiving component 1202 and / or the transmission of communications by the transmitting component 1204. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the reception and / or transmission of communications.

[0139] The receiving component 1202 can receive one or more messages from the O-DU, each message including a group ID of a user group of UEs that share time-frequency resources in a time slot but occupy different spatial layers. The communication manager 1206 can classify one or more messages into corresponding user groups based at least in part on the group ID. The communication manager 1206 can generate one or more beam weights for each corresponding user group or the spatial layer associated with each corresponding user group based at least in part on spatial layer information from other coordination degrees of the corresponding user group.

[0140] The receiving component 1202 can receive one or more signals from one or more UEs, and perform beamforming on the received signals using one or more beam weights to generate a spatial layer. The transmitting component 1204 can transmit the spatial layer for one or more signals to the O-DU.

[0141] Figure 12 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 The other set of components shown performs one or more functions.

[0142] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a network entity, the method comprising: generating a unique group identifier (ID) for each of one or more user groups, each user group comprising a group of user equipment (UEs) sharing time-frequency resources in a time slot but occupying different spatial layers; and sending one or more messages to an open radio unit (O-RU), wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to the corresponding user group.

[0143] Aspect 2: According to the method of aspect 1, the network entity includes an Open Distributed Unit (O-DU).

[0144] Aspect 3: According to the method of aspect 2, the method further includes: selecting a user for a user group in the one or more user groups.

[0145] Aspect 4: The method according to any one of aspects 1 to 3, wherein each of the one or more messages includes a segment.

[0146] Aspect 5: The method according to any one of Aspects 1 to 3, wherein each of the one or more messages includes an extension attached to the segment.

[0147] Aspect 6: The method according to aspect 5, wherein the extension includes a demodulation reference signal extension.

[0148] Aspect 7: The method according to any one of Aspects 1 to 6, wherein each of the one or more messages includes a field specific to the indication group ID.

[0149] Aspect 8: A method for wireless communication performed by a network entity, the method comprising: receiving one or more messages from an Open Distributed Unit (O-DU), each of the one or more messages including a group identifier (ID) of a user group of user equipment (UE) sharing time-frequency resources in a time slot but occupying different spatial layers; classifying the one or more messages into a corresponding user group at least in part based on the group ID; and generating one or more beam weights for the spatial layer associated with each corresponding user group at least in part based on spatial layer information from other coordination degrees of the corresponding user group.

[0150] Aspect 9: According to the method of aspect 8, the network entity includes an Open Radio Unit (O-RU).

[0151] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the information includes pilot signals associated with channel estimation.

[0152] Aspect 11: The method according to any one of aspects 8 to 10, wherein each of the one or more messages includes a segment.

[0153] Aspect 12: The method according to any one of aspects 8 to 11, wherein each of the one or more messages includes an extension attached to the segment.

[0154] Aspect 13: The method according to aspect 12, wherein the extension includes a demodulation reference signal extension.

[0155] Aspect 14: The method according to any one of Aspects 8 to 13, wherein each of the one or more messages includes a field specific to the indication group ID.

[0156] Aspect 15: The method according to any one of Aspects 8 to 14, the method further comprising: receiving one or more signals from one or more UEs, beamforming the one or more signals being received by means of the one or more beam weights to generate a spatial layer; and transmitting the spatial layer for the one or more signals to the O-DU.

[0157] Aspect 16: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 15.

[0158] Aspect 17: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 15.

[0159] Aspect 18: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 15.

[0160] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 15.

[0161] Aspect 20: 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 the method according to one or more of aspects 1 to 15.

[0162] Aspect 21: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 15.

[0163] Aspect 22: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 15.

[0164] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various practices.

[0165] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning 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, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art 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 limiting in any way. Therefore, no specific software code is referenced herein to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0166] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0167] 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.

[0168] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase referring to “at least one of” the list of items means 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, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0169] No element, action, or instruction used herein should be construed as essential 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 used interchangeably with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “having” and the like 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 open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the network entity to: Generate a unique group identifier (ID) for each user group in one or more user groups. Each user group includes groups of user equipment (UEs) that share time-frequency resources in a time slot but occupy different spatial layers. as well as Send one or more messages to an Open Radio Unit (O-RU), wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to the corresponding user group.

2. The apparatus of claim 1, wherein the network entity comprises an Open Distributed Unit (O-DU).

3. The apparatus of claim 2, wherein the one or more processors are individually or collectively configured to cause the network entity to select users for a user group within the one or more user groups.

4. The apparatus of claim 1, wherein each of the one or more messages comprises a segment.

5. The apparatus of claim 1, wherein each of the one or more messages includes an extension attached to the segment.

6. The apparatus of claim 5, wherein the extension includes a demodulation reference signal extension.

7. The apparatus of claim 1, wherein each of the one or more messages includes a field specific to an indication group ID.

8. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the network entity to: Receive one or more messages from the Open Distributed Unit (O-DU), each of the one or more messages including a group identifier (ID) of a user group of user equipment (UE) that shares time-frequency resources in a time slot but occupies a different spatial layer; The one or more messages are categorized into corresponding user groups based at least in part on the group ID; and One or more beam weights are generated for the spatial layer associated with each corresponding user group, based at least in part on information from other spatial layers of coordination from the corresponding user group.

9. The apparatus of claim 8, wherein the network entity comprises an Open Radio Unit (O-RU).

10. The apparatus of claim 8, wherein the information includes pilot signals associated with channel estimation.

11. The apparatus of claim 8, wherein each of the one or more messages comprises a segment.

12. The apparatus of claim 8, wherein each of the one or more messages includes an extension attached to the segment.

13. The apparatus of claim 12, wherein the extension includes a demodulation reference signal extension.

14. The apparatus of claim 8, wherein each of the one or more messages includes a field specific to an indication group ID.

15. The apparatus of claim 8, wherein the one or more processors are individually or jointly configured to cause the network entity to: Receive one or more signals from one or more UEs, and perform beamforming on the received one or more signals using the one or more beam weights to generate a space layer; and The space layer is sent to the O-DU for the one or more signals.

16. A method for wireless communication performed by a network entity, the method comprising: Generate a unique group identifier (ID) for each user group in one or more user groups. Each user group includes groups of user equipment (UEs) that share time-frequency resources in a time slot but occupy different spatial layers. as well as Send one or more messages to an Open Radio Unit (O-RU), wherein each of the one or more messages is associated with a corresponding user group and includes a group ID unique to the corresponding user group.

17. The method of claim 16, wherein the network entity includes an Open Distributed Unit (O-DU), and wherein the method includes selecting a UE for a user group within the one or more user groups.

18. The method of claim 16, wherein each of the one or more messages includes an extension attached to the segment.

19. The method of claim 18, wherein the extension includes a demodulation reference signal extension.

20. The method of claim 16, wherein each of the one or more messages includes a field specific to an indication group ID.

Images