Selecting open radio capability based on configured features

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a network entity may send a first set of capabilities of the network entity to an open distributed unit (O-DU), the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The network entity may receive, from the O-DU, an indication of one or more features configured by the O-DU. The network entity may select a second set of capabilities of the network entity based at least in part on the one or more features configured by the O-DU. The network entity may send the second set of capabilities of the network entity to the O-DU. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 481,956, filed October 5, 2023, entitled “SELECTION OF OPEN RADIOUNIT CAPABILITIES BASED ON CONFIGURED FEATURES”, which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is 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) capabilities. 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. UEs 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).

[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] Communication systems, such as 5G New Radio (NR) systems, can be deployed with a variety of components or constituent parts in various ways. In a 5G NR system, network nodes can be implemented in either a converged or decomposed architecture. For example, a base station (e.g., an evolved NB (eNB), a 5G NB, or a gNB) or one or more components performing base station functionality can be implemented as a decomposed base station (e.g., a decomposed network node). Decomposed base stations can be configured to utilize protocol stacks that are physically or logically distributed across 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-RANs) (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 independently.

[0008] An Open RU (O-RU) can support radio-level capabilities (capacities) applicable to the entire O-RU or its endpoints. An endpoint can be a construct representing a processing unit. An O-RU can have multiple endpoints. Capabilities at an endpoint can be endpoint-level capabilities. These capabilities can include static endpoints, static low-level transmit endpoints, and static low-level receive endpoints. Such endpoints can be statically configured and bundled together. The O-RU can advertise its static configuration to the Open DU (O-DU) at startup. The initially advertised capabilities can be considered basic capabilities.

[0009] The O-RU can send capability exchange parameters, such as capability sets (e.g., basic capabilities). The O-DU can support or be configured with certain features. The O-DU can identify the features to be supported based on the capability set. The O-DU can conform to the features indicated by the O-RU. The O-DU can send indications of the features configured by the O-DU.

[0010] However, factors influence the static capabilities supported by the O-RU. The O-RU may be able to advertise a set of features including enhanced endpoint capabilities (capacity beyond the basic capabilities), but the O-DU may not support some of these features, and therefore it is unclear which enhanced endpoint capabilities the O-DU can or cannot apply. The O-DU may determine whether certain features advertised by the O-RU are enabled or disabled. The O-RU has no way to indicate that if the O-DU does not support a given feature or determines that a given feature is disabled, the O-RU's capabilities may be reduced to below the capabilities advertised by the O-RU at startup (e.g., becoming read-only capabilities). This can negatively impact the O-RU's overall capacity. Furthermore, the O-RU may only support one optional feature that will help the O-RU enhance its processing (e.g., reflected in support for more layers or more carriers). If the O-RU supports more than one enhanced feature, there is no mechanism to help the O-RU advertise its enhanced capabilities. Additionally, the O-RU and O-DU may operate with different versions of features or capabilities. Furthermore, the O-DU may determine any combination of component carriers (CCs) after the O-RU advertises per-band supported capabilities. Combinations of configurations can affect endpoint capacity, and endpoint capacity can be associated with a specific CC. Such effects can reduce the processing capacity of the O-RU, which may introduce latency.

[0011] Based on the various aspects described herein, endpoint and O-RU-level capabilities for an O-RU can be negotiated. For example, an O-RU may transmit a first set of capabilities (e.g., total O-RU capabilities and / or endpoint-specific capabilities). An O-DU may indicate features configured at the O-DU. The O-RU may select a second set of capabilities based at least in part on the configured features. The O-RU may add, remove, or change parameters of O-RU capabilities or endpoint capabilities in the first set of capabilities to form the second set of capabilities. For example, a certain beam capability may be advertised by the O-RU as a basic capability in the first set of capabilities. The O-DU may indicate support for the basic capability. However, above the basic capability, the O-DU may indicate support for the total number of enhanced beams that can be supported per endpoint or the total number of enhanced beams that the O-RU can support. The O-DU may comply with this second set of capabilities. The O-RU may be able to increment beam capabilities and indicate new beam capabilities in the second set of capabilities. In this way, the O-RU and O-DU can negotiate enhanced capabilities to optimize the capabilities of the O-RU.

[0012] Some aspects described herein relate to a method for wireless communication performed by a network entity. The method may include transmitting a first set of capabilities of the network entity to an O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The method may include receiving from the O-DU an indication of one or more features configured by the O-DU. The method may include selecting a second set of capabilities of the network entity based at least in part on one or more features configured by the O-DU. The method may include transmitting the second set of capabilities of the network entity to the O-DU.

[0013] Some aspects described herein relate to a method for wireless communication performed by a network entity. The method may include receiving a first set of capabilities from an O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The method may include sending an indication to the O-RU of one or more features configured by the network entity when operating as an O-DU. The method may include receiving a second set of capabilities from the O-RU that is different from the first set of capabilities.

[0014] 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 configured to transmit a first set of capabilities of the network entity to an O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The one or more processors may be configured to receive from the O-DU an indication of one or more features configured by the O-DU. The one or more processors may be configured to select a second set of capabilities of the network entity based at least in part on the one or more features configured by the O-DU. The one or more processors may be configured to transmit the second set of capabilities of the network entity to the O-DU.

[0015] 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 configured to receive a first set of capabilities from an O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The one or more processors may be configured to send to the O-RU indications of one or more features configured by the network entity when operating as an O-DU. The one or more processors may be configured to receive a second set of capabilities from the O-RU that is different from the first set of capabilities.

[0016] 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 transmit a first set of capabilities of the network entity to an O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. When executed by one or more processors of the network entity, the set of instructions enables the network entity to receive from the O-DU indications for one or more features configured by the O-DU. When executed by one or more processors of the network entity, the set of instructions enables the network entity to select a second set of capabilities of the network entity at least in part based on one or more features configured by the O-DU. When executed by one or more processors of the network entity, the set of instructions enables the network entity to transmit the second set of capabilities of the network entity to the O-DU.

[0017] 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 a first set of capabilities from an O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. When executed by one or more processors of the network entity, the set of instructions enables the network entity to send instructions to the O-RU for one or more features configured by the network entity when operating as an O-DU. When executed by one or more processors of the network entity, the set of instructions enables the network entity to receive a second set of capabilities from the O-RU, different from the first set of capabilities.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting a first set of capabilities of network entities to an O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The apparatus may include components for receiving from the O-DU an indication of one or more features configured by the O-DU. The apparatus may include components for selecting a second set of capabilities of network entities, at least in part based on one or more features configured by the O-DU. The apparatus may include components for transmitting the second set of capabilities of network entities to the O-DU.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: components for receiving a first set of capabilities from an O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability; components for transmitting to the O-RU an indication of one or more features configured by a network entity when operating as an O-DU; and components for receiving a second set of capabilities from the O-RU that is different from the first set of capabilities.

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

[0021] The features and technical advantages of the examples according to this disclosure have been summarized rather broadly 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.

[0022] 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

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

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

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

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

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

[0028] Figure 5 This is a diagram illustrating an example of another set of capabilities according to the instructions of this disclosure.

[0029] Figure 6 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.

[0030] Figure 7 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.

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

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

[0033] 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 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 aspects of the disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of these claims.

[0034] 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 blocks, 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.

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

[0036] 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 an aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, 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 central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0037] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. 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, Transmit / Receive 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).

[0038] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. 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., 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).

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

[0040] 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, repeater, etc.

[0041] 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, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in 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).

[0042] Network controller 130 may be coupled to or communicate with a set 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.

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

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

[0045] 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 may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, 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.

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

[0047] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency 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 generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (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).

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

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

[0050] In some aspects, a network entity configured to operate as an Open RU (O-RU) (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a first set of capabilities of the network entity to an Open Distributed Unit (O-DU), the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The communication manager 150 may receive from the O-DU indications for one or more features configured by the O-DU. The communication manager 150 may select a second set of capabilities of the network entity based at least in part on one or more features configured by the O-DU. The communication manager 150 may send the second set of capabilities of the network entity to the O-DU. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0051] In some aspects, a network entity configured to operate as an O-DU (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a first set of capabilities from the O-RU, which includes one or more of at least one O-RU capability or at least one endpoint capability. The communication manager 150 may send instructions to the O-RU regarding one or more features configured by the network entity when operating as an O-DU. The communication manager 150 may receive a second set of O-RU capabilities from the O-RU that is different from the first set of O-RU capabilities. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

[0053] 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 antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). Network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0054] At network node 110, transmitting processor 220 may receive data from data source 212 intended for use by UE 120 (or a set of UEs 120). Transmitting processor 220 may 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 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmitting processor 220 may 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 may 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 provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can 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 transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0055] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can 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" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as 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 UE 120 may be included in housing 284.

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

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

[0058] 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 9 ( ) aspects of any of the methods described.

[0059] 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 to schedule 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., reference). Figures 4 to 9 ( ) aspects of any of the methods described.

[0060] As described in more detail elsewhere in this document, 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 selecting and instructing O-RU capabilities. 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 6 Process 600 Figure 7 The operation of process 700 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, the one or more instructions may, 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), cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example... Figure 6 Process 600 Figure 7 The operation of process 700 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0061] In some aspects, a network entity (e.g., network node 110) includes: components for transmitting a first set of capabilities of the network entity to the O-DU; components for receiving from the O-DU an indication of one or more features configured by the O-DU; components for selecting a second set of capabilities of the network entity based at least in part on one or more features configured by the O-DU; and / or components for transmitting the second set of capabilities of the network entity to the O-DU. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0062] In some aspects, a network entity (e.g., network node 110) includes: components for receiving a first set of capabilities from an O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability; components for sending instructions to the O-RU to one or more features configured by the network entity when operating as an O-DU; and / or components for receiving a second set of capabilities from the O-RU that is different from the first set of capabilities. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0063] In some respects, individual processors can be described as performing all functions executed by the one or more processors. In other respects, the one or more processors can collectively perform a set of functions. For example, the processors of a first set (one or more) of the one or more processors can be described as performing a first function executed by the one or more processors, and the processors of a second set (one or more) of the one or more processors can be described as performing a second function executed by the one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more processors" should be understood as referring to a combination of processors. 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.

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

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

[0066] 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 a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) that perform 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).

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

[0068] 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, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. 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.

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

[0070] Each unit in the cells (including CU 310, DU 330, RU 340), as well as 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 unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other cells via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other cells via a wireless transmission media, or both.

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

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

[0073] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a 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 such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, the real-time and non-real-time aspects of communication with the control plane and user plane of 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.

[0074] 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 4G RAN hardware aspects 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.

[0075] 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, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0076] 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).

[0077] 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 in the YANG modeling language). 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.

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

[0079] Figure 4 Figure 400 illustrates an example of a feature associated with an O-DU configuration according to this disclosure. Figure 4 As shown, O-RU 410 and O-DU 420 can communicate with each other in a decomposed base station architecture such as decomposed base station architecture 300.

[0080] The O-RU 410 supports radio-level capabilities (capacity) applicable to the entire O-RU 410. The O-RU 410 may also support another level of capability or endpoint-level capability. An endpoint can be a construct representing a processing unit. An O-RU may have multiple endpoints. Capabilities at an endpoint can be endpoint-level capabilities. These capabilities may include static endpoints, static low-level transmit endpoints, and static low-level receive endpoints. Such endpoints can be statically configured and bundled together. The O-RU 410 may advertise a static configuration to the O-DU at startup. The initially advertised capabilities may be considered basic capabilities. Static configurations may include, for example, the number of spatial streams, the maximum number of carriers in the uplink, and / or the maximum number of carriers in the downlink. The O-RU 410 may also advertise static per-endpoint-level capabilities, which may include the maximum number of beams per symbol and / or the maximum number of beams per timeslot.

[0081] Example 400 illustrates that the O-RU 410 can support a single endpoint capability. This may involve basic endpoint capabilities with fundamental features. The O-RU 410 can be configured to support multiple endpoint capabilities based on several optional features, such as those for control plane message passing (CPLANE-MESSAGE-PROCESSING-LIMITS) and beaming (e.g., BEAM-UPDATE-CONTENTION-CONTROL). The control plane message passing limitation feature may have parameters for the basic endpoint capacity, such as parameters for the maximum number of beams per symbol, the maximum number of beams per time slot, or the maximum highest priority portion per time slot. The beam update contention control feature may have parameters for the basic endpoint capability, such as the maximum number of beams per symbol or the maximum number of beam updates per symbol. Other optional features of O-RU may include channel information physical resource block (PRB) group, user plane message processing limits, non-scheduled UE ID, configurable UE ID range, or multi-user MIMO user group optimization.

[0082] As shown by reference numeral 425, O-RU 410 can send capability exchange parameters, such as a capability set (e.g., basic capabilities). O-RU 410 can use YANG parameters to indicate the capability set, which are parameters communicated using the YANG modeling language. O-DU 420 can support or be configured with certain features. O-DU 420 can identify features to be supported based on the capability set. O-DU 420 can be configured with supported features. As shown by reference numeral 430, O-DU 420 can identify configured features. O-DU 420 can conform to features indicated by O-RU 410. As shown by reference numeral 435, O-DU 420 can send indications of features configured by O-DU 420.

[0083] However, factors influence the static capabilities supported by the O-RU 410. The O-RU 410 may be able to advertise a set of features including enhanced endpoint capabilities (capabilities beyond basic capabilities), but the O-DU 420 may not support some of these features, and therefore it is unclear which enhanced endpoint capabilities the O-DU 420 can or cannot apply. The O-RU 410 has no way to indicate that if the O-DU 420 does not support a given feature or determines that a given feature is disabled, the O-RU 410's capabilities will be reduced to below the capabilities advertised by the O-RU 410 at startup (e.g., becoming read-only capabilities). The O-DU 420 may determine whether to enable or disable certain features advertised by the O-RU 410. This can negatively impact the overall capacity of the O-RU 410. Furthermore, the O-RU 410 may only support one optional feature that would help the O-RU 410 enhance its processing (e.g., reflected in support for more layers or more carriers). If the O-RU 410 supports more than one enhancement feature, there is no mechanism to help the O-RU 410 announce its enhancement capabilities.

[0084] Furthermore, O-RU 410 and O-DU 420 can operate with different versions of features or capabilities. These versions may support different features or may be incompatible. For example, O-RU 410 may use version 7 for CPLANCE-MESSAGE-PROCESSING-LIMITS, version 8 for BEAM-UPDATE-CONTENTION-CONTROL and CHANNEL-INFORMATION-PRB-GROUP, version 12 for UPLANCE-MESSAGE-PROCESSING LIMITS and NON-SCHEDULED-UEID, and version 14 for CONFIGURABLE-UE-ID-RANGE-SUPPORT and MUMIMO_USR_GRP_OPTIMIZATION. A lower version of O-DU 420 may not be able to resolve these new features and their corresponding YANG parameters, which is the same as O-DU 420 that does not support these features. This will affect the O-RU 410 capacity advertised by O-RU 410. O-RU only announces a set of endpoints and O-RU-level capabilities, regardless of the O-RU version.

[0085] Furthermore, after the O-RU 410 announces per-band support capabilities using module capability parameters such as maximum supported frequencies for downlinks, minimum supported frequencies per downlink, maximum supported bandwidth for downlinks, maximum carrier bandwidth for downlinks, or minimum carrier bandwidth for downlinks, the O-DU 420 can determine any combination of configured component carriers (CCs). The configured combination may affect endpoint capacity, and endpoint capacity may be associated with a specific CC. Such effects may reduce the O-RU's processing capacity, which may introduce latency.

[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 examples described are different.

[0087] Figure 5 This is a diagram illustrating example 500 of another set of capabilities according to the instructions of this disclosure. For example... Figure 5 As shown, O-RU 510 (e.g., network node 110) and O-DU 520 (e.g., network node 110) can communicate with each other in a decomposed base station architecture such as decomposed base station architecture 300.

[0088] Based on the various aspects described herein, endpoint and O-RU-level capabilities of the O-RU can be negotiated between the O-RU and O-DU. For example, the O-RU may send a first set of capabilities (e.g., total O-RU capabilities and / or endpoint-specific capabilities). The O-DU may indicate features supported or configured at the O-DU. The O-RU may select a second set of capabilities based at least in part on the configured features. The O-RU may add, remove, or change parameters for O-RU capabilities or endpoint capabilities in the first set of capabilities to form the second set of capabilities. For example, a certain beam capability may be advertised by the O-RU as a basic capability in the first set of capabilities. The O-DU may indicate support for the basic capability. However, above the basic capability, the O-DU may indicate support for the total number of enhanced beams that can be supported per endpoint or the total number of enhanced beams that the O-RU can support. The O-DU may comply with this second set of capabilities. The O-RU may be able to increment beam capabilities and indicate new beam capabilities in the second set of capabilities. In this way, the O-RU and O-DU can negotiate enhanced capabilities to optimize the capabilities of the O-RU.

[0089] Example 500 illustrates this negotiation. As shown by reference numeral 525, O-RU 510 may send indications of a first set of capabilities. These may be O-RU capabilities and / or endpoint capabilities initially announced. As shown by reference numeral 530, O-DU 520 may identify configured features. As shown by reference numeral 535, O-DU 520 may send indications of configured features.

[0090] As indicated by reference numeral 540 in the accompanying drawings, O-RU 510 may select a second capability set at least in part based on configuration features. In some aspects, O-RU 510 may select a second capability set at least in part based on configuration features associated with the same endpoint capabilities as indicated in the first capability set. O-RU 510 may select a second capability set at least in part based on configuration features associated with common endpoint capabilities for a set of endpoints, wherein the common endpoint capabilities are indicated in the first capability set. O-RU 510 may select a second capability set at least in part based on configuration features associated with enhanced O-RU capabilities or endpoint capabilities. O-RU 510 may select a second capability set at least in part based on configuration features that are optional O-RU features. In some aspects, O-RU 510 may select a second capability set at least in part based on configuration features that are at least in part based on a mismatch between feature versions of O-RU 510 and feature versions of O-DU 520.

[0091] The O-DU selection for array carrier configuration may affect endpoint and O-RU capabilities. In some aspects, O-RU 510 may select a second capability set based at least in part on carrier parameters and / or bandwidth parameters configured by O-DU 520. For example, a list of O-RU transmit (tx) array capabilities or receive (rx) array capabilities. Each tx / rx array may be associated with one or more static low-level tx / rx endpoints. Parameters in the capabilities may include the maximum or minimum supported frequencies for the downlink, the maximum number of carriers for the downlink, the maximum or minimum carrier bandwidth for the downlink, and / or the supported technologies for the downlink. O-DU 520 may use the capability list advertised by the O-RU to configure the tx array carriers and / or rx array carriers. In some aspects, O-RU 510 may select a second capability set based at least in part on beamforming methods and / or delay profiles configured by the O-DU. As indicated by reference numeral 545, O-RU 510 may transmit an indication of the second capability set. In some respects, the O-DU 520 can send instructions for updates to features configured by the O-DU 520, at least in part, based on a second set of capabilities.

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

[0093] Figure 6 This is a diagram illustrating an example process 600 performed, for example, at a network entity or a device of a network entity, according to the present disclosure. Example process 600 is an example in which a device or network entity (e.g., network node 110, O-RU 510) performs operations associated with capability selection.

[0094] like Figure 6 As shown, in some aspects, process 600 may include sending a first set of capabilities of a network entity to the O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability (box 610). For example, the network entity (e.g., using...) Figure 8 The transmitting component 804 and / or communication manager 806 described herein may transmit a first set of capabilities of network entities to the O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability, as described above.

[0095] like Figure 6 As further shown, in some aspects, process 600 may include receiving an indication from the O-DU for one or more features configured by the O-DU (box 620). For example, a network entity (e.g., using receiving component 802 and / or communication manager 806, such as...) Figure 8The device described above can receive instructions from the O-DU on one or more features configured by the O-DU.

[0096] like Figure 6 As further shown, in some aspects, process 600 may include selecting a second set of capabilities of network entities based at least in part on one or more features configured by the O-DU (box 630). For example, network entities (e.g., using...) Figure 8 The communication manager 806 described herein can select a second set of capabilities of network entities, at least in part, based on one or more features configured by the O-DU, as described above.

[0097] like Figure 6 As further shown, in some aspects, process 600 may include sending a second set of capabilities of network entities to the O-DU (box 640). For example, network entities (e.g., using...) Figure 8 The transmitting component 804 and / or communication manager 806 described herein can transmit a second set of network entity capabilities to the O-DU, as described above.

[0098] Process 600 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 herein.

[0099] In the first aspect, selecting the second capability set includes removing one or more capabilities from the first capability set to form the second capability set, based at least in part on one or more features configured by the O-DU.

[0100] In a second aspect, either alone or in combination with the first aspect, selecting a second capability set includes adding one or more capabilities to the first capability set to form a second capability set, based at least in part on one or more features configured by the O-DU.

[0101] In a third aspect, either alone or in combination with one or more of the first and second aspects, selecting a second capability set includes at least in part modifying one or more parameters of the O-RU capabilities or endpoint capabilities in the first capability set to form the second capability set based on one or more features configured by the O-DU.

[0102] In the fourth aspect, selecting the second capability set, either alone or in combination with one or more of the first to third aspects, includes selecting the second capability set based at least in part on two or more of one or more features being associated with the same endpoint capability as indicated in the first capability set.

[0103] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, selecting the second capability set includes selecting the second capability set based at least in part on two or more of one or more features associated with common endpoint capabilities for a set of endpoints, wherein the common endpoint capabilities are indicated in the first capability set.

[0104] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, selecting the second capability set includes selecting the second capability set based at least in part on two or more of one or more features being associated with enhanced O-RU capabilities or endpoint capabilities.

[0105] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the selection of the second capability set includes selecting the second capability set based at least in part on two or more of one or more features being optional O-RU features.

[0106] In the eighth aspect, the selection of the second O-RU capability set, either alone or in combination with one or more of the first to seventh aspects, includes selecting the second O-RU capability set based at least in part on the mismatch between the feature versions of network entities and the feature versions of O-DUs.

[0107] In the ninth aspect, the selection of the second capability set, either alone or in combination with one or more of the first to eighth aspects, includes selecting the second capability set based at least in part on one or more of the carrier parameters or bandwidth parameters configured by the O-DU.

[0108] In the tenth aspect, the selection of the second capability set, either alone or in combination with one or more of the first to ninth aspects, includes selecting the second capability set based at least in part on one or more of the beamforming method or delay profile configured by the O-DU.

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

[0110] Figure 7 This is a diagram illustrating an example process 700 performed, for example, at a network entity or a device of a network entity, according to the present disclosure. Example process 700 is an example in which a device or network entity (e.g., network node 110, O-DU 520) performs operations associated with capability selection.

[0111] like Figure 7As shown, in some aspects, process 700 may include receiving a first set of capabilities from an O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability (box 710). For example, a network entity (e.g., using...) Figure 9 The receiving component 902 and / or communication manager 906 depicted herein may receive a first set of capabilities from the O-RU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability, as described above.

[0112] like Figure 7 As further shown, in some aspects, process 700 may include sending an indication to the O-RU of one or more features configured by the network entity when operating as an O-DU (box 720). For example, the network entity (e.g., using...) Figure 9 The transmitting component 904 and / or communication manager 906 described herein can send instructions to the O-RU for one or more features configured by the network entity when operating as an O-DU, as described above.

[0113] like Figure 7 As further shown, in some aspects, process 700 may include receiving a second set of capabilities from the O-RU that is different from the first set of capabilities (box 730). For example, network entities (e.g., using...) Figure 9 The receiving component 902 and / or communication manager 906 depicted herein may receive a second capability set from the O-RU that is different from the first capability set, as described above.

[0114] Process 700 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 herein.

[0115] In the first aspect, one or more features include two or more features associated with the same endpoint capability as indicated in the first capability set.

[0116] In the second aspect, either alone or in combination with the first aspect, one or more features include two or more features associated with a common endpoint capability for a set of endpoints, wherein the common endpoint capability is indicated in a first capability set.

[0117] In the third aspect, either alone or in combination with one or more of the first and second aspects, one or more features include two or more features associated with enhanced O-RU capability or endpoint capability.

[0118] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, one or more features include two or more optional O-RU features.

[0119] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 700 includes sending an updated indication of one or more features configured by the network entity operating as an O-DU.

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

[0121] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be a network entity (e.g., O-RU 510), or a network entity may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806 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 806 is combined with... Figure 1 The described communication manager 150. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0122] In some respects, device 800 can be configured to perform the functions described herein. Figures 1 to 5 One or more operations described herein. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process is 600. In some respects, Figure 8 The illustrated device 800 and / or one or more components may include a combination Figure 2 One or more components of the described network entity. Additionally or alternatively, Figure 8 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.

[0123] Receiver 802 may receive communications from device 808, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components of device 800. In some aspects, receiver 802 may include combinations of... Figure 2 The described network entity 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.

[0124] Transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 808. In some aspects, one or more other components of device 800 can generate communications and provide the generated communications to transmitting component 804 for transmission to device 808. In some aspects, transmitting component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signals to device 808. In some aspects, transmitting component 804 may include combinations of... Figure 2 The described network entity 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 804 may co-located with the receive component 802 in one or more transceivers.

[0125] The communication manager 806 may support the operation of the receiving component 802 and / or the transmitting component 804. For example, the communication manager 806 may receive information associated with configuring communication reception by the receiving component 802 and / or configuring communication transmission by the transmitting component 804. Additionally or alternatively, the communication manager 806 may generate and / or provide control information to the receiving component 802 and / or the transmitting component 804 to control the reception and / or transmission of communication.

[0126] The transmitting component 804 can transmit a first set of capabilities of a network entity to the O-DU, the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability. The receiving component 802 can receive from the O-DU an indication of one or more features configured by the O-DU. The communication manager 806 can select a second set of capabilities of the network entity based at least in part on one or more features configured by the O-DU. The transmitting component 804 can transmit the second set of capabilities of the network entity to the O-DU.

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

[0128] Figure 9 This is a diagram of an example device 900 for wireless communication according to the present disclosure. Device 900 may be a network entity (e.g., O-DU 520), or a network entity may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 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 906 is combined with... Figure 1 The described communication manager 150. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0129] In some respects, device 900 can be configured to perform the functions described herein. Figures 1 to 5 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 7 The process is 700. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described network entity. Additionally or alternatively, Figure 9 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.

[0130] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described network entity 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.

[0131] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described network entity 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 904 may co-located with the receive component 902 in one or more transceivers.

[0132] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring communication reception by the receiving component 902 and / or configuring communication transmission by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communication.

[0133] The receiving component 902 can receive a first capability set from the O-RU, the first capability set including one or more of at least one O-RU capability or at least one endpoint capability. The transmitting component 904 can send an indication to the O-RU of one or more features configured by a network entity when operating as an O-DU. The receiving component 902 can receive a second capability set from the O-RU that is different from the first capability set.

[0134] The transmitting component 904 can send an indication of an update to one or more features configured by a network entity operating as an O-DU.

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

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

[0137] Aspect 1: A method for wireless communication performed by a network entity, the method comprising: transmitting a first set of capabilities of the network entity to an Open Distributed Unit (O-DU), the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability; receiving from the O-DU an indication of one or more features configured by the O-DU; selecting a second set of capabilities of the network entity based at least in part on the one or more features configured by the O-DU; and transmitting the second set of capabilities of the network entity to the O-DU.

[0138] Aspect 2: According to the method of aspect 1, selecting the second capability set includes removing one or more capabilities from the first capability set to form the second capability set, at least in part based on the one or more features configured by the O-DU.

[0139] Aspect 3: The method according to any one of Aspects 1 to 2, wherein selecting the second capability set includes adding one or more capabilities to the first capability set to form the second capability set, at least in part based on the one or more features configured by the O-DU.

[0140] Aspect 4: The method according to any one of Aspects 1 to 3, wherein selecting the second capability set includes at least in part modifying one or more parameters of the O-RU capabilities or endpoint capabilities in the first capability set to form the second capability set based on one or more features configured by the O-DU.

[0141] Aspect 5: The method according to any one of Aspects 1 to 4, wherein selecting the second capability set includes selecting the second capability set based at least in part on two or more of the one or more features being associated with the same endpoint capability as indicated in the first capability set.

[0142] Aspect 6: The method according to any one of Aspects 1 to 5, wherein selecting the second capability set includes selecting the second capability set based at least in part on two or more of the one or more features being associated with common endpoint capabilities for a set of endpoints, wherein the common endpoint capabilities are indicated in the first capability set.

[0143] Aspect 7: The method according to any one of Aspects 1 to 6, wherein selecting the second capability set includes selecting the second capability set based at least in part on two or more of the one or more features being associated with enhanced O-RU capabilities or endpoint capabilities.

[0144] Aspect 8: The method according to any one of Aspects 1 to 7, wherein selecting the second capability set includes selecting the second capability set based at least in part on two or more of the one or more features being optional O-RU features.

[0145] Aspect 9: The method according to any one of Aspects 1 to 8, wherein selecting the second O-RU capability set includes selecting the second O-RU capability set based at least in part on the mismatch between the feature version of the network entity and the feature version of the O-DU.

[0146] Aspect 10: The method according to any one of Aspects 1 to 9, wherein selecting the second capability set includes selecting the second capability set based at least in part on one or more of the carrier parameters or bandwidth parameters configured by the O-DU.

[0147] Aspect 11: The method according to any one of Aspects 1 to 10, wherein selecting the second capability set includes selecting the second capability set based at least in part on one or more of the beamforming method or delay profile configured by the O-DU.

[0148] Aspect 12: A method of wireless communication performed by a network entity, the method comprising: receiving a first set of capabilities from an open radio unit (O-RU), the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability; sending to the O-RU an indication of one or more features configured by the network entity when operating as an open distributed unit (O-DU); and receiving from the O-RU a second set of capabilities different from the first set of capabilities.

[0149] Aspect 13: According to the method of aspect 12, wherein the one or more features include two or more features associated with the same endpoint capability as indicated in the first capability set.

[0150] Aspect 14: The method according to any one of Aspects 12 to 13, wherein the one or more features include two or more features associated with a common endpoint capability for a set of endpoints, wherein the common endpoint capability is indicated in the first capability set.

[0151] Aspect 15: The method according to any one of Aspects 12 to 14, wherein the one or more features include two or more features associated with enhanced O-RU capability or endpoint capability.

[0152] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the one or more features include two or more optional O-RU features.

[0153] Aspect 17: The method according to any one of Aspects 12 to 16, the method further comprising sending an indication of updating one or more features configured by the network entity as an O-DU operation.

[0154] Aspect 18: 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 17.

[0155] Aspect 19: 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 17.

[0156] Aspect 20: 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 17.

[0157] Aspect 21: 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 17.

[0158] Aspect 22: 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 17.

[0159] Aspect 23: A device for wireless communication, the device comprising: a processing system including 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 17.

[0160] Aspect 24: 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 17.

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

[0162] 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 in this document 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.

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

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

[0165] 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 set of claims. 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).

[0166] 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 “set” and “group” 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 “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in combination 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: Send a first set of capabilities of the network entity to an Open Distributed Unit (O-DU), the first set of capabilities including one or more of at least one Open Radio Unit (O-RU) capability or at least one endpoint capability; Receive instructions from the O-DU for one or more features configured by the O-DU; The second set of capabilities of the network entity is selected at least in part based on one or more features configured by the O-DU; and Send the second capability set of the network entity to the O-DU.

2. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to remove one or more capabilities from the first capability set at least in part based on the one or more features configured by the O-DU to form the second capability set.

3. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to add one or more capabilities to the first capability set at least in part based on the one or more features configured by the O-DU to form the second capability set.

4. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to modify one or more parameters of the O-RU capabilities or endpoint capabilities in the first capability set, at least in part, based on the one or more features configured by the O-DU, to form the second capability set.

5. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to select the second capability set based at least in part on two or more of the one or more features associated with the same endpoint capability as indicated in the first capability set.

6. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to select the second capability set based at least in part on two or more of the one or more features associated with common endpoint capabilities for a set of endpoints, wherein the common endpoint capabilities are indicated in the first capability set.

7. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to select the second capability set based at least in part on two or more of the one or more features associated with enhanced O-RU capabilities or endpoint capabilities.

8. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to select the second capability set at least in part based on two or more of the one or more features being optional O-RU features.

9. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or jointly configured to cause the network entity to select the second O-RU capability set at least in part based on the mismatch between the feature version of the network entity and the feature version of the O-DU.

10. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to select the second capability set at least in part based on one or more of the carrier parameters or bandwidth parameters configured by the O-DU.

11. The apparatus of claim 1, wherein, in order to select the second capability set, the one or more processors are individually or collectively configured to cause the network entity to select the second capability set at least in part based on one or more of the beamforming method or delay profile configured by the O-DU.

12. 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 a first set of capabilities from an open radio unit (O-RU), the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability; Send an indication to the O-RU of one or more features configured by the network entity when operating as an Open Distributed Unit (O-DU); as well as Receive a second capability set that is different from the first capability set from the O-RU.

13. The apparatus of claim 12, wherein one or more features include two or more features associated with the same endpoint capability as indicated in the first capability set.

14. The apparatus of claim 12, wherein the one or more features include two or more features associated with a common endpoint capability for a set of endpoints, wherein the common endpoint capability is indicated in the first capability set.

15. The apparatus of claim 12, wherein the one or more features comprise two or more features, the two or more features comprising two or more optional O-RU features or two or more features associated with enhanced O-RU capabilities or endpoint capabilities.

16. The apparatus of claim 12, wherein the one or more processors are individually or collectively configured to cause the network entity to send an indication of an update to one or more features configured by the network entity as an O-DU operation.

17. A method for wireless communication performed by a network entity, the method comprising: Send a first set of capabilities of the network entity to an Open Distributed Unit (O-DU), the first set of capabilities including one or more of at least one Open Radio Unit (O-RU) capability or at least one endpoint capability; Receive instructions from the O-DU for one or more features configured by the O-DU; The second set of capabilities of the network entity is selected at least in part based on one or more features configured by the O-DU; and Send the second capability set of the network entity to the O-DU.

18. The method of claim 17, wherein selecting the second set of capabilities comprises selecting the second set of capabilities based at least in part on two or more of the one or more features being associated with the same endpoint capability as indicated in the first set of capabilities.

19. The method of claim 17, wherein selecting the second capability set comprises selecting the second capability set based at least in part on two or more of the one or more features being associated with common endpoint capabilities for a set of endpoints, wherein the common endpoint capabilities are indicated in the first capability set.

20. The method of claim 17, wherein selecting the second capability set comprises selecting the second capability set based at least in part on two or more of the one or more features being associated with enhanced O-RU capabilities or endpoint capabilities.

21. The method of claim 17, wherein selecting the second capability set comprises selecting the second capability set at least in part based on two or more of the one or more features being optional O-RU features.

22. The method of claim 17, wherein selecting the second O-RU capability set comprises selecting the second O-RU capability set based at least in part on the mismatch between the feature version of the network entity and the feature version of the O-DU.

23. The method of claim 17, wherein selecting the second capability set includes selecting the second capability set at least in part based on one or more of the carrier parameters or bandwidth parameters configured by the O-DU.

24. The method of claim 17, wherein selecting the second capability set comprises selecting the second capability set at least in part based on one or more of the beamforming method or delay profile configured by the O-DU.

25. A method for wireless communication performed by a network entity, the method comprising: Receive a first set of capabilities from an open radio unit (O-RU), the first set of capabilities including one or more of at least one O-RU capability or at least one endpoint capability; Send an indication to the O-RU of one or more features configured by the network entity when operating as an Open Distributed Unit (O-DU); as well as Receive a second capability set that is different from the first capability set from the O-RU.

26. The method of claim 25, wherein the one or more features include two or more features associated with the same endpoint capability as indicated in the first capability set.

27. The method of claim 25, wherein the one or more features include two or more features associated with common endpoint capabilities for a set of endpoints, wherein the common endpoint capabilities are indicated in the first capability set.

28. The method of claim 25, wherein the one or more features include two or more features associated with enhanced O-RU capability or endpoint capability.

29. The method of claim 25, wherein the one or more features comprise two or more optional O-RU features.

30. The method of claim 25, further comprising sending an indication of updating one or more features configured by the network entity as an O-DU operation.

Images