Extended antenna-carrier allocation policy for simplified switching

Apparatus, methods, and computer-readable media for facilitating simplified switching at an RU are disclosed herein. An example method for wireless communication at an RU includes transmitting, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints. The example method also includes receiving an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier. The example method also includes using a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics. Additionally, the example method includes using a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group.

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to communication utilizing an open radio access network (O-RAN).

INTRODUCTION

BRIEF SUMMARY

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a radio unit (RU). An example apparatus may transmit, to a distributed unit (DU), capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints. The example apparatus may also receive an extended Antenna-Carrier (eAxC) message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier. Additionally, the example apparatus may use a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics. The example apparatus may also use a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at an RU. An example apparatus may transmit, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints. The example apparatus may also receive an eAxC message from the DU, the eAxC message including a group index based on the capability information. Additionally, the example apparatus may route the eAxC message to a processing component based in part on the group index included in the eAxC message.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a DU. An example apparatus may receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints. The example apparatus may also encode, based on the capability information, an endpoint group associated with an eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier. Additionally, the example apparatus may encode an RU endpoint of the endpoint group using a second portion of the RU port identifier. The example apparatus may also transmit the eAxC message to the RU.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a DU. An example apparatus may receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints. The example apparatus may also allocate eAxC messages to RU endpoints within respective endpoint groups based in part on the capability information. Additionally, the example apparatus may transmit an eAxC message to the RU, the eAxC message including a group index associated with an endpoint group.

DETAILED DESCRIPTION

Aspects disclosed herein provide techniques for simplifying the routing of messages to the correct hardware component for processing (also referred to as “switching”). Disclosed techniques may configure an RU to determine the groups of endpoints in a transmission direction (e.g., uplink or downlink). The RU may then indicate to which group a receive endpoint (“rx-endpoint”) or a transmit endpoint (“tx-endpoint”) belongs. For example, the RU may advertise, via transmitting capability information to the DU, to which group a tx-endpoint or an rx-endpoint belongs. That is, for each endpoint (e.g., which may be referred generally to as a “Mx-endpoint”), the RU may indicate to which group the endpoint belongs. In some examples, the endpoints may be indicated via a respective “static-low-level-tx-endpoint” parameter or a “static-low-level-rx-endpoint” parameter.

Additionally, aspects disclosed herein configure the RU to receive an eAxC message (e.g., a message including an eAxC) and perform switching based on the RU port identifier of the eAxC message. For example, the DU may encode the RU port identifier to include a group index and a per-group layer index or a per-group stream index (referred to herein as a “per-group layer/stream index”). The group index may indicate a group and the per-group layer/stream index may indicate the RU endpoint. The RU may decode the group index and then route the eAxC message to the correct hardware component for processing based on the group index. By using a first portion and a second portion of an RU port identifier to index the eAxC message, aspects disclosed herein facilitate hierarchical addressing of RU endpoints of the RU.

FIG. 1is a diagram illustrating an example of a wireless communications system and an access network100including base stations102and180and UEs104.

The access network100may include an open radio access network (O-RAN) to provide a standardization of radio interfaces to procure interoperability between component radio equipment. A base station180may be an O-RAN base station, and the base station180may include a DU180A and an RU180B, based on a lower layer functional split. The O-RAN may include an open fronthaul (FH) interface between the DU180A and the RU180B.

In certain aspects, the RU180B, may be configured to manage one or more aspects of wireless communication by indicating support of endpoint groupings. For example, the RU180B may include an eAxC grouping advertising component198configured to transmit, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints. The example eAxC grouping advertising component198may also be configured to receive an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier. Additionally, the example eAxC grouping advertising component198may be configured to use a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics. The example eAxC grouping advertising component198may also be configured to use a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group.

In another configuration, the eAxC grouping advertising component198may be configured to transmit, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints. The example eAxC grouping advertising component198may also be configured to receive an eAxC message from the DU, the eAxC message including a group index based on the capability information. The example eAxC grouping advertising component198may also be configured to route the eAxC message to a processing component based in part on the group index included in the eAxC message.

In another configuration, the DU180A, may be configured to manage or more aspects of wireless communication by allocating eAxC endpoints based on the capabilities of the RU. For example, the DU180A may include an eAxC allocation component199configured to receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints. The example eAxC allocation component199may also be configured to encode, based on the capability information, an endpoint group associated with an eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier. Additionally, the example eAxC allocation component199may be configured to encode an RU endpoint of the endpoint group using a second portion of the RU port identifier. The example eAxC allocation component199may also be configured to transmit the eAxC message to the RU

In another configuration, the eAxC allocation component199may be configured to receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints. The example eAxC allocation component199may also be configured to allocate eAxC messages to RU endpoints within respective endpoint groups based in part on the capability information. Additionally, the example eAxC allocation component may be configured to transmit an eAxC message to the RU, the eAxC message including a group index associated with an endpoint group.

The aspects presented herein may enable improving RU ingress routing, for example, by simplifying switching based on an eAxC allocation policy and/or reducing costs associated with lookup table sizes and lookup table processing.

Although the following description provides examples directed to 5G NR (and, in particular, to O-RAN employing 5G NR), the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and/or other wireless technologies, in which the RAN may be configured via an open RAN.

FIG. 3is a block diagram that illustrates an example of a first wireless device that is configured to exchange wireless communication with a second wireless device. In the illustrated example, the first wireless device may comprise a base station310, the second wireless device may comprise a UE350, and the base station310may be in communication with the UE350in an access network. As shown inFIG. 3, the base station310includes a transmit processor (TX processor316), a transceiver318including a transmitter318aand a receiver318b, antennas320, a receive processor (RX processor370), a channel estimator374, a controller/processor375, and memory376. The example UE350includes antennas352, a transceiver354including a transmitter354aand a receiver354b, an RX processor356, a channel estimator358, a controller/processor359, memory360, and a TX processor368. In other examples, the base station310and/or the UE350may include additional or alternative components.

The UL transmission is processed at the base station310in a manner similar to that described in connection with the receiver function at the UE350. Each receiver318breceives a signal through its respective antenna320. Each receiver318brecovers information modulated onto an RF carrier and provides the information to the RX processor370.

At least one of the TX processor316, the RX processor370, and the controller/processor375may be configured to perform aspects in connection with the eAxC grouping advertising component198and/or the eAxC allocation component199ofFIG. 1.

To establish a connection in a network, a UE first connects to a radio access network (RAN). The RAN communicates directly with users and acts as a gateway between a UE and a network core, such as the core network190ofFIG. 1. The RAN may comprise a base station, such as the base station180ofFIG. 1, including a baseband unit (BBU) and radio equipment (RE). The BBU and the RE together may perform digital signal processing functions related to a protocol stack.

In some examples, the network may employ an O-RAN to provide a standardization of radio interfaces to procure interoperability between component radio equipment. For example, in an O-RAN, the RAN may be disaggregated into a centralized unit (CU), a distributed unit (DU), and a radio unit (RU). The RU (sometimes referred to herein as an “O-RU”) may facilitate transmitting, receiving, amplifying, and/or digitizing radio frequency (RF) signals. The RU may be located at, near, or integrated with, an antenna. The DU and the CU provide computational functions and may facilitate the transmission of digitized radio signals within the network. The DU (sometimes referred to herein as an “O-DU”) may be physically located at or near the RU. The CU (sometimes referred to herein as an “O-CU”) may be located near the core network.

The DU may provide downlink and uplink baseband processing, a supply system synchronization clock, signal processing, and an interface with the CU. The RU may provide downlink baseband signal conversion to an RF signal, and uplink RF signal conversion to a baseband signal. The O-RAN may include an open fronthaul (FH) interface between the DU and the RU.

Lower layer functions of the protocol stack may be split between the DU and the RU. In a first example split, RF functions, such as signal sampling and baseband uplink/downlink conversion, are performed by the RU. Such a split allows for a relatively simple and cost-effective RU and the DU performs most of the baseband processing. However, such a split also places strict latency limits on the FH, for example, to satisfy timing-sensitive protocols, such as HARQ. In a second example split, DU and RU functionalities may be split between the RLC layer and the PDCP layer. In such a split, timing-sensitive protocols (such as HARQ) may be moved from the DU to the RU, along with MAC layer functions and PHY layer functions. Such a split may allow latency limits on the FH to be relaxed. However, such a split may also increase the complexity of the RU.

In a third example split, the RU may perform digital beamforming functions, CP addition/removal functions, and FFT functions, while the DU may perform higher layer functions starting from resource element (RE) mapping/demapping. Such a split, also referred to as a “7.2x split,” results in data being transmitted over the FH to include in-phase and quadrature (I-Q) samples. The example 7.2x split may accommodate suitable data transfer speeds between the DU and the RU to facilitate time-sensitive protocols, while also balancing the processing workloads at the DU and the RU.

In some examples, the FH between the DU and the RU may be implemented via a fiber connection. The FH interface may include a control/user/synchronization (C/U/S) plane and a management (M) plane.

The C-plane is a control plane that may refer specifically to real-time control between the DU and the RU. The U-plane is a user plane that may refer to IQ sample data transferred between the DU and the RU. The S-plane is a synchronization plane that may refer to traffic between the RU or the DU to the synchronization controller. The M-plane is a management plane that may refer to management operations sharing the configuration management between the DU and the RU.

On boot-up of the network system, a set of configuration management messages may be exchanged on the M-plane between the DU and the RU. The DU and the RU may configure the M-plane accordingly and use the configuration for the C/U/S-plane communication.

After the network system boot-up, the M-plane configuration may be dynamically changed through remote procedure call (RPC) messages. For example, the DU and the RU may dynamically change the M-plane configuration with get-config and edit-config RPCs. In some aspects, the DU and the RU may exchange a protocol, such as a NETCONF protocol, using the RPC messages. The RPC messages may dynamically change the M-plane configuration between the DU and the RU.

Messages exchanged between the DU and the RU may use extended Antenna-Carrier (eAxC) identifiers as message source and message destination identifiers. The eAxC identifier may be included in a header portion of a message. As used herein, an “eAxC message” may generally refer to a message exchanged between the DU and the RU that includes an eAxC identifier, such as a C-plane message or a U-plane message.

FIG. 4is a diagram illustrating an example eAxC identifier400. The example eAxC identifier400may be used to facilitate communication in an O-RAN. In the example ofFIG. 4, the eAxC identifier400includes a DU port identifier402(“DU Port ID”), a band sector identifier404(“BandSector_ID”), a component carrier (CC) identifier406(“CC_ID”), and an RU port identifier408(“RU_Port_ID”).

FIG. 5is a diagram illustrating example eAxC allocations500for a DU, such as the example DU180A ofFIG. 1. The eAxC allocations500may facilitate communication an O-RAN. The example eAxC allocations500include different component carrier/bandwidth/layer combinations. For example, a configuration (also referred to as an “M-plane configuration”) may indicate a frequency range502(“Band”), a quantity of component carriers504(“CC”), a bandwidth allocation506associated with each component carrier (“BW MHz”), and a quantity of layers/streams508(“Layers/Streams”). The CC504, the bandwidth allocation506, and the quantity of layers/streams508may be used to determine a total layer/stream bandwidth allocation510(“BW”).

In the example ofFIG. 5, a configuration also indicts downlink groups512and uplink groups514. As shown inFIG. 5, the downlink groups512includes a quantity of downlink channel endpoints (“DL Channel”) (PDSCH) and a quantity of SSB endpoints (“SSB”). The uplink groups514includes a quantity of uplink channel endpoints (“UL Channel”) (PUSCH), a quantity of SRS endpoints (“SRS”), and a quantity of physical random access channel (PRACH) endpoints (“PRACH”). In the example ofFIG. 5, the downlink groups512and the uplink groups514are indicated per component carrier. The example eAxC allocations500also include a quantity of downlink eAxC allocations516(“eAxC DL”) and a quantity of uplink eAxC allocations518(“eAxC UL”). The quantity of downlink eAxC allocations516and the quantity of uplink eAxC allocations518are based on the quantity of component carriers504and the quantities indicated in the respective downlink groups512and uplink groups514.

For example, the eAxC allocations500include a first configuration520indicating an FR1 band, two component carriers, a bandwidth of 100 MHz, and 16 layers/streams, which results in a layer/stream bandwidth allocation of 3200 MHz (2*100 MHz*16=3200 MHz). The first configuration520also indicates a quantity of 34 downlink eAxC allocations516based on the two component carriers, the 16 downlink channel endpoints, and the one SSB endpoint (e.g., 2*(16+1)=34). The first configuration520also indicates a quantity of 168 uplink eAxC allocations518based on the two component carriers, the 16 uplink channel endpoints, the 64 SRS endpoints, and the four PRACH endpoints (e.g., 2*(16+64+4)=168).

Although the above description includes two example groups in the downlink direction (e.g., the downlink channel group and the SSB group) and three example groups in the uplink direction (e.g., the uplink channel group, the SRS group, and the PRACH group), other examples may include additional or alternative groups associated with a direction.

As shown inFIG. 5, it may be possible for the quantity of uplink eAxC allocations518and/or the quantity of downlink eAxC allocations516to be large. Moreover, when the RU receives a message, such as a control plane message, the RU may determine the hardware component to route the message to for processing. For example, in the uplink direction, the RU may receive control plane messages related to the uplink channel (PUSCH), to the SRS, or to the PRACH. In the downlink direction, the RU may receive control plane messages related to the downlink channel or to the SSB. Based on the direction and type of message, the RU may route the message to an appropriate hardware component for processing. For example, the RU may route PUSCH control plane messages to a first hardware component for processing, may route SRS control plane messages to a second hardware component for processing, may route PRACH control plane messages to a third hardware component for processing, may route PDSCH control plane messages to a fourth hardware component for processing, and may route SSB control plane messages to a fifth hardware component for processing.

It may be appreciated that two or more of the hardware components may be a same hardware component that applies different processing techniques for processing the respective control plane messages. For example, the RU may route PUSCH control plane messages, SRS control plane messages, and PRACH control plane messages to a first hardware component that applies different techniques for processing PUSCH control plane messages, SRS control plane messages, and PRACH control plane messages. The RU may also route PDSCH control plane messages and SSB control plane messages to a second hardware component that applies different techniques for processing PDSCH control plane messages and SSB control plane messages. In another example, the RU may route PRACH control plane messages to a first hardware component, may route PUSCH control plane messages and PDSCH control plane messages to a second hardware component, and may route SRS control plane messages and SSB control plane messages to a third hardware component. The second hardware component may be configured to apply different techniques for processing PUSCH control plane messages and PDSCH control plane messages. The third hardware component may be configured to apply different techniques for processing SRS control plane messages and SSB control plane messages. However, other examples may include additional or alternate combinations for routing messages to hardware components.

Aspects disclosed herein provide techniques for simplifying the routing of messages to the correct hardware component for processing. Disclosed techniques may configure the RU to determine the groups of endpoints in a transmission direction (e.g., uplink or downlink). For example, in the uplink direction, the RU may determine an uplink channel (PUSCH) group, an SRS group, and a PRACH group. In the downlink direction, the RU may determine a downlink channel group and an SSB group. The RU may then indicate to which group a receive endpoint (“rx-endpoint”) or a transmit endpoint (“tx-endpoint”) belongs. For example, the RU may advertise, via transmitting capability information to the DU, to which group a tx-endpoint or a rx-endpoint belongs. That is, for each endpoint (e.g., which may be referred generally to as a “Mx-endpoint”), the RU indicates to which group the endpoint belongs. In some examples, the endpoints may be indicated via a respective “static-low-level-tx-endpoint” parameter or a “static-low-level-rx-endpoint” parameter.

For example, the RU may determine that there are 85 rx-endpoints that may be grouped into three rx-endpoint groups A, B, and C. The RU may advertise that group A includes 50 rx-endpoints, group B includes 25 rx-endpoints, and group C includes 10 rx-endpoints. That is, for reach of the 85 rx-endpoints, the RU may indicate a group (e.g., group A, group B, or group C) to which the respective rx-endpoint belongs.

The DU may receive the advertised endpoint groupings and perform an eAxC identifier (“eAxCID”) allocation. The eAxCID allocation may include allocating an RU port allocation, such as allocating an RU port identifier for each eAxCID.

Aspects disclosed herein configure the RU to receive an eAxC message (e.g., a message including an eAxC identifier, such as the example eAxC identifier400ofFIG. 4) and perform switching based on the RU port identifier of the eAxC message. For example, the DU may encode a first portion of the RU port identifier to include a group index and may encode a second portion of the RU port identifier to include a per-group layer/stream index. The group index may indicate an endpoint group (e.g., the uplink channel group, the SRS group, or the PRACH group in the uplink direction, and the downlink channel group or the SRS group in the downlink direction) and the per-group layer/stream index may indicate an RU endpoint. The RU may decode the RU port identifier and use the first portion of the RU port identifier to determine an endpoint group. The RU may then use the second portion of the RU port identifier to determine an RU endpoint and route the eAxC message to the correct hardware component for processing based on the per-group layer/stream index.

As described above, the DU may allocate an RU port allocation for each eAxCID allocation. The DU may apply an encoding technique to the RU port identifier to indicate an endpoint group and an endpoint group layer/stream. In some examples, the encoding technique may include dedicated bits to the group index and to the per-group layer/stream index to indicate the respective endpoint group and group layer/stream (or RU endpoint). In some examples, the DU may apply an encoding technique including a bitmask to indicate the endpoint group.

FIG. 6is a diagram600illustrating an example allocation policy for grouping RU endpoints, as presented herein. For example, a DU may receive capability information from an RU indicating a quantity of groups and a quantity of endpoints associated with each of the respective groups. The illustrated example ofFIG. 6includes three example groups602,604,606(e.g., a group A, a group B, and a group C) including respective quantities of RU endpoints. As shown inFIG. 6, the first group602includes 50 endpoints, the second group604includes 25 endpoints, and the third group606includes 10 endpoints. In the illustrated example, the RU endpoints are associated with RU receiver endpoints (“rx-endpoints”).

In the example ofFIG. 6, the DU applies an encoding technique including dedicated bits to the group index and to the per-group layer/stream index. The DU may determine the quantity of bits to dedicate to the group index based on the quantity of groups. For example, the DU may determine to dedicate two bits of an RU port identifier to the group index based on the three groups602,604,606ofFIG. 6.

The DU may determine the quantity of bits to dedicate to the per-group layer/stream index based on the quantity of endpoints associated with each group. For example, with respect to the first group602(e.g., group A), the DU may allocate six bits to represent the 50 endpoints. In a similar manner, the DU may determine to allocate five bits to represent the 25 endpoints associated with the second group604(e.g., group B), and may determine to allocate four bits to represent the 10 endpoints associated with the third group606(e.g., group C).

In the example ofFIG. 6, the DU may use the maximum number of bits allocated to a group for representing the endpoints of each group. For example, based on the six bits allocated to represent the 50 endpoints associated with the first group602), the DU may determine to allocate two bits to indicate the group index and six bits to indicate the per-group layer/stream index. As shown inFIG. 6, an RU port identifier610includes eight bits including two bits dedicated to a group index612(“GrpIndex”) and six bits dedicated to a per-group layer/stream index614(“GrpLayerIndex”). The two bits of the group index612may represent each of the three groups602,604,606, and the six bits of the per-group layer/stream index614may represent each of the endpoints within any one group. Thus, the group index612and the per-group layer/stream index614are associated with respective static bit widths (or “length-in-bits”).

In the example ofFIG. 6, a first group index (“00”) may correspond to the first group602. The six bits of the per-group layer/stream index614may represent a first block620of 64 different group layers/streams, and 50 of the 64 different group layers/streams of the first block620may correspond to the 50 endpoints associated with the 50 endpoints of the first group602. A second block622of 64 different group layers/streams may represent group layers/streams 64 to 127 associated with a second group index (“01”), and 25 of the 64 different group layers/streams of the second block622may correspond to the 25 endpoints associated with the 25 endpoints of the second group604. A third block624may represent group layers/streams 128 to 191 associated with a third group index (“10”), and 10 of the 64 different group layers/streams endpoints of the third block624may correspond to the 10 endpoints associated with the 10 end points of the third group606. As shown inFIG. 6, a fourth block626may represent group layers/streams 192 to 255 associated with a fourth group index (“11”). However, in the example ofFIG. 6, none of the group layers/streams of the fourth block626may correspond to endpoints as 85 total endpoints across the three groups have already been allocated.

As shown, the example encoding technique ofFIG. 6includes dedicated bits for group indexing and dedicated bits for per per-group layer/stream indexing. Such an encoding technique provides for linear addressing across groups. For example, each of the groups602,604,606is associated with a group index (e.g., “00,” “01,” or “10”), each group index is associated with a block of 64 group layers/streams (e.g., blocks620,622,624), and each group layer/stream of a block may be mapped to an endpoint associated with a respective group. Additionally, the example encoding technique ofFIG. 6allows for simpler switching at the RU as the RU can determine the hardware component to route a message based on the group index indicated by the RU port identifier of the eAxC message instead of processing the full RU port identifier or by trying to route the messages to the different hardware components to determine the correct hardware component for the message. For example, in the example ofFIG. 6, the RU may use the two most significant bits (MSBs) of the RU port identifier610to determine where to route the eAxC message and route the eAxC message to the correct hardware component accordingly.

However, such an encoding technique, as shown inFIG. 6, may result in wasted group layers/streams as there are unused group layers/streams (e.g., group layers/streams that are unmapped to endpoints of a group). For example, while the third block624includes 64 group layers/streams, in the example ofFIG. 6, only ten of the group layers/streams are allocated to an endpoint.

In the example ofFIG. 6, the DU allocates eAxCIDs to each of the endpoints received in the capability information. For example, the DU allocates the 85 endpoints to 85 group layers/streams within the first three blocks620,622,624. In some examples, the DU may determine to allocate a subset of the endpoints. For example, the DU may determine to allocate eAxCIDs to half of the endpoints of the first group602. In such an example, the DU may allocate five bits to represent half of the endpoints (e.g., 25 endpoints) of the first group602, may allocate five bits to represent the 25 endpoints of the second group604, and may allocate four bits to represent the 10 endpoints of the third group606. By allocating eAxCIDs to only half of the endpoints of the first group602, the DU may reduce the size of the RU port identifier to seven total bits (e.g., two dedicated bits for the group index and five dedicated bits for the per-group layer/stream index). In such an example, the RU may still use the two MSBs of the RU port identifier to route messages.

FIG. 7is a diagram700illustrating another example allocation policy for grouping RU endpoints, as presented herein. Similar to the example ofFIG. 6, a DU may receive capability information from an RU indicating a quantity of groups and a quantity of endpoints associated with each of the respective groups. The illustrated example ofFIG. 7includes three example groups702,704,706(e.g., a group A, a group B, and a group C) including respective quantities of RU endpoints. As shown inFIG. 7, the first group702includes 50 endpoints, the second group704includes 25 endpoints, and the third group706includes 10 endpoints. In the illustrated example, the RU endpoints are associated with RU receiver endpoints (“rx-endpoints”). As described in connection with the example ofFIG. 6, the 50 endpoints of the first group702may be represented by six bits, the 25 endpoints of the second group704may be represented by five bits, and the 10 endpoints of the third group706may be represented by four bits.

In the example ofFIG. 7, the DU applies an encoding technique including a bitmask to indicate the endpoint group. For example, the location of a first value (e.g., a “1”) of the MSB may be used to indicate a group and to distinguish from other groups. The bit width of the per-group layer/stream index may vary based on the bitmask.

For example, inFIG. 7, the endpoints associated with the first group702may be indicated by setting the MSB bit0(“MSB_Bit_0”) of an RU port identifier710to the first value (e.g., “1”). Setting the MSB bit0to the first value may distinguish between group A endpoints and non-group A endpoints. The next six bits of the RU port identifier710(e.g., MSB bits1to6) may be allocated to referencing the endpoints associated with the first group702.

The endpoints associated with the second group704may be indicated by setting the MSB bit0to a second value (e.g., “0”) and setting the next MSB (“MSB_Bit_1”) to the first value (e.g., “1”). Setting the MSB bit0of the RU port identifier710to the second value (e.g., “0”) may indicate that the corresponding eAxC message is not associated with the first group702. However, when decoding the RU port identifier710, the RU may determine that the corresponding eAxC message is associated with the second group704based on the next MSB (“MSB_Bit_1”) being set to the first value (e.g., “1”). The remaining five bits of the RU port identifier710(e.g., MSB bits2to6) may be allocated to reference the endpoints associated with the second group704.

The endpoints associated with the third group706may be indicated by setting the MSB bit0and the MSB bit1to the second value (e.g., “0”) and setting the MSB bit2(“MSB Bit2”) of the RU port identifier710to the first value (e.g., “1”). When decoding the RU port identifier710, the RU may determine, based on the first two MSBs being set to the second value (e.g., “0”), that the corresponding eAxC message is not associated with the first group702and the second group704. However, the RU may determine that the corresponding eAxC message is associated with the third group706based on the next MSB (“MSB Bit2”) being set to the first value (e.g., “1”). The remaining four bits of the RU port identifier710(e.g., MSB bits3to6) may be allocated to reference the endpoints associated with the third group706.

Compared to the encoding technique ofFIG. 6, the encoding technique ofFIG. 7facilitates allocating eAxCIDs to each of the 85 endpoints using seven bits for the RU port identifier710. However, the bit width (or size) of the bitmask associated with such an encoding technique varies based on the quantity of groups. Additionally, addressing across the groups is non-linear. For example, there are 64 group layers/streams associated with a first block720(e.g., group layers/streams 0 to 63) based on the six bits allocated to reference the endpoints associated with the first group702, there are 32 group layers/streams associated with a second block722(e.g., group layers/streams 64 to 95) based on the five bits allocated to reference the endpoints associated with the second group704, and there are 16 group layers/streams associated with a third block724(e.g., group layers/streams 96 to 111) based on the four bits allocated to reference the endpoints associated with the third group706.

While the first example encoding technique (e.g., the dedicated bits (or static bit widths) ofFIG. 6) and the second example encoding technique (e.g., the bitmask ofFIG. 7) provide examples in which the second encoding technique results in a smaller RU port identifier (e.g., seven bits versus eight bits) based on an example of 85 endpoints, it may be appreciated that the second encoding technique may result in a smaller RU port identifier when applied to actual use cases. For example, referring to the example eAxC allocations500, the first example configuration520includes three groups in the uplink direction (e.g., the uplink channel group, the SRS group, and the PRACH group). The first group (e.g., the uplink channel group) includes 16 endpoints, the second group (e.g., the SRS group) includes 64 endpoints, and the third group (e.g., the PRACH group) includes 4 endpoints. By applying the first encoding technique, the RU port identifier includes eight total bits including two dedicated bits to indicate one of the three groups and six dedicated bits to reference the largest quantity of endpoints associated with a group (e.g., the 64 endpoints associated with the SRS group).

In contrast, by applying the second encoding technique to the first example configuration520, seven bits may be allocated to the RU port identifier. For example, to indicate the SRS endpoints, the MSB may be set to the first value (e.g., “1”) to indicate the SRS group, and then six additional bits may be used to reference the 64 SRS endpoints, which results in seven bits to indicate the SRS group and respective endpoints. To indicate the uplink channel endpoints, the MSB may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit1) may be set to the first value (e.g., “1”) to indicate the uplink channel group, and then four bits may be used to reference the 16 uplink channel endpoints, which results in six bits to indicate the uplink channel group and respective endpoints. However, as seven bits are needed to indicate the SRS endpoints, it may be appreciated that five bits may be used to reference the 16 uplink channel endpoints so that the size of the RU port identifier remains constant at seven bits. To indicate the PRACH endpoints, the first two MSBs may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit2) may be set to the first value (e.g., “1”), and then two additional bits may be used to reference the 4 PRACH endpoints, which results in five bits to indicate the PRACH group and respective endpoints. However, as seven bits are needed to indicate the SRS endpoints, it may be appreciated that four bits may be used to reference the 4 PRACH endpoints so that the size of the RU port identifier remains constant at seven bits.

Thus, referring to the first example configuration520of the eAxC allocations500, applying the second encoding technique results in a smaller RU port identifier (e.g., seven bits) compared to when applying the first encoding technique (e.g., eight bits).

In another example, a second example configuration522of the eAxC allocations500includes three groups in the uplink direction (e.g., the uplink channel group, the SRS group, and the PRACH group). The first group (e.g., the uplink channel group) includes 4 endpoints, the second group (e.g., the SRS group) includes 16 endpoints, and the third group (e.g., the PRACH group) includes 4 endpoints. By applying the first encoding technique, the RU port identifier includes six total bits including two dedicated bits to indicate one of the three groups and four dedicated bits to reference the largest quantity of endpoints associated with a group (e.g., the 16 endpoints associated with the SRS group).

In contrast, by applying the second encoding technique to the second example configuration522, five bits may be allocated to the RU port identifier. For example, to indicate the SRS endpoints, the MSB may be set to the first value (e.g., “1”) to indicate the SRS group, and then four additional bits may be used to reference the 16 SRS endpoints, which results in five bits to indicate the SRS group and respective endpoints. To indicate the uplink channel endpoints, the MSB may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit1) may be set to the first value (e.g., “1”) to indicate the uplink channel group, and then two bits may be used to reference the 4 uplink channel endpoints, which results in four bits to indicate the uplink channel group and respective endpoints. However, as five bits are needed to indicate the SRS endpoints, it may be appreciated that three bits may be used to reference the 4 uplink channel endpoints so that the size of the RU port identifier remains constant at five bits. To indicate the PRACH endpoints, the first two MSBs may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit2) may be set to the first value (e.g., “1”), and then two additional bits may be used to reference the 4 PRACH endpoints, which results in five bits to indicate the PRACH group and respective endpoints.

Thus, referring to the second example configuration522of the eAxC allocations500, applying the second encoding technique results in a smaller RU port identifier (e.g., five bits) compared to when applying the first encoding technique (e.g., six bits).

In another example, referring again to the first example configuration520, the downlink direction includes two groups (e.g., the downlink channel group and the SSB group). The first group (e.g., the downlink channel group) includes 16 endpoints and the second group (e.g., the SSB group) includes 1 endpoint. By applying the first encoding technique, the RU port identifier may be allocated five total bits including one dedicated bit to indicate one of the two groups and four dedicated bits to reference the largest quantity of endpoints associated with a group (e.g., the 16 endpoints associated with the downlink channel group).

By applying the second encoding technique to the first example configuration520, the RU port identifier may also be indicated using five bits. For example, to indicate the downlink channel endpoints, the MSB may be set to the first value (e.g., “1”) to indicate the downlink channel group, and then four additional bits may be used to reference the 16 endpoints of the downlink channel, which results in five bits to indicate the downlink channel group and respective endpoints. To indicate the SSB endpoint, the MSB may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit1) may be set to the first value (e.g., “1”) to indicate the SSB group, and then one bit may be used to reference the 1 SSB endpoint, which results in three bits to indicate the SSB group and respective endpoint. However, as five bits are needed to indicate the downlink channel endpoints, it may be appreciated that three bits may be used to reference the 1 SSB endpoint so that the size of the RU port identifier remains constant at five bits. To indicate the PRACH endpoints, the first two MSBs may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit2) may be set to the first value (e.g., “1”), and then two additional bits may be used to reference the 4 PRACH endpoints, which results in five bits to indicate the PRACH group and respective endpoints.

Thus, referring to the downlink direction of the first example configuration520of the eAxC allocations500, applying the first encoding technique and the second encoding technique results in an RU port identifier of a same bit width (e.g., five bits).

However, it may be appreciated that in some examples, it may be beneficial to use a static bit width for the encoding technique versus a bitmask. For example, a third example configuration524of the eAxC allocations500includes three groups in the uplink direction (e.g., the uplink channel group, the SRS group, and the PRACH group). The first group (e.g., the uplink channel group) includes 4 endpoints, the second group (e.g., the SRS group) includes 4 endpoints, and the third group (e.g., the PRACH group) includes 4 endpoints. By applying the first encoding technique, the RU port identifier may be allocated four total bits including two dedicated bits to indicate one of the three groups and two dedicated bits to reference the largest quantity of endpoints associated with a group (e.g., the four endpoints associated with the uplink channel group, the SRS group, or the PRACH group).

In contrast, by applying the second encoding technique to the third example configuration524, five bits may be allocated to the RU port identifier. For example, to indicate the SRS endpoints, the MSB may be set to the first value (e.g., “1”) to indicate the SRS group, and then two additional bits may be used to reference the 4 SRS endpoints, which results in three bits to indicate the SRS group and respective endpoints. To indicate the uplink channel endpoints, the MSB may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit1) may be set to the first value (e.g., “1”) to indicate the uplink channel group, and then two bits may be used to reference the 4 uplink channel endpoints, which results in four bits to indicate the uplink channel group and respective endpoints. To indicate the PRACH endpoints, the first two MSBs may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit2) may be set to the first value (e.g., “1”), and then two additional bits may be used to reference the 4 PRACH endpoints, which results in five bits to indicate the PRACH group and respective endpoints. As the largest number of bits is five bits associated with the PRACH group in this example, it may be appreciated that four bits (e.g., two extra bits) may be used to represent the 4 SRS endpoints and three bits (e.g., one extra bit) may be used to represent the 4 uplink channel endpoints so that the size of the RU port identifier remains constant at five bits.

Thus, referring to the third example configuration524of the eAxC allocations500, applying the first encoding technique results in a smaller RU port identifier (e.g., four bits) compared to when applying the second encoding technique (e.g., five bits).

In another example, a fourth example configuration526includes three groups in the uplink direction including 8 endpoints of the uplink channel group, 8 SRS endpoints, and 4 PRACH endpoints. By applying the first encoding technique, the RU port identifier may be allocated five total bits including two dedicated bits to indicate one of the three groups and three dedicated bits to reference the largest quantity of endpoints associated with a group (e.g., the 8 endpoints associated with the uplink channel group or the SRS group).

By applying the second encoding technique to the fourth example configuration526, five bits may be allocated to the RU port identifier. For example, to indicate the endpoints of the uplink channel, the MSB may be set to the first value (e.g., “1”) to indicate the uplink channel group, and then three additional bits may be used to reference the 8 endpoints of the uplink channel, which results in four bits to indicate the uplink channel group and respective endpoints. To indicate the SRS endpoints, the MSB may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit1) may be set to the first value (e.g., “1”) to indicate the SRS group, and then three bits may be used to reference the 8 SRS endpoints, which results in five bits to indicate the SRS group and respective endpoints. To indicate the PRACH endpoints, the first two MSBs may be set to the second value (e.g., “0”), the next MSB (e.g., MSB bit2) may be set to the first value (e.g., “1”) to indicate the PRACH group, and then two bits may be used to reference the four PRACH endpoints, which results in five bits to indicate the PRACH group and respective endpoints. As the largest number of bits is five bits associated with the SRS group and the PRACH group in this example, it may be appreciated that four bits (e.g., one extra bit) may be used to represent the 8 uplink channel endpoints so that the size of the RU port identifier remains constant at five bits.

Thus, referring to the uplink direction of the fourth example configuration526of the eAxC allocations500, applying the first encoding technique and the second encoding technique results in an RU port identifier of a same size (e.g., five bits).

FIG. 8illustrates an example communication flow800between an RU802and a DU804, as presented herein. In the illustrated example, the communication flow800facilitates simplified switching at the RU based on an eAxC allocation policy. The RU802and the DU804may facilitate communication via an O-RAN. Aspects of the RU802may be implemented by the RU180B ofFIG. 1. Aspects of the DU804may be implemented by the DU180A ofFIG. 1. Although not shown in the illustrated example ofFIG. 8, it may be appreciated that in additional or alternative examples, the RU802may be in communication with one or more UEs or other DUs, and/or the DU804may be in communication with one or more CUs or other RUs.

In the example ofFIG. 8, the RU802transmits capability information810that is received by the DU804. The RU802may transmit the capability information810via an M-plane message, a C-plane message, and/or a U-plane message. The capability information810may indicate a quantity of groups and a quantity of endpoints associated with each group. Referring to the examples ofFIGS. 6 and/or 7, the capability information810may indicate that there are three groups and the quantity of endpoints associated with each group (e.g., 50 endpoints associated with a group A, 25 endpoints associated with a group B, and 10 endpoints associated with a group C).

In some examples, the capability information810may indicate the endpoints associated with each group. For example, the capability information810may indicate each RU transmit endpoint (“tx-endpoint”) and the uplink direction groups (e.g., the uplink channel group, the SRS group, or the PRACH group) to which the respective tx-endpoints belong. The capability information810may indicate each tx-endpoint via a static-low-level-tx-endpoint parameter. The capability information810may additionally or alternatively indicate each rx-endpoint and the downlink direction groups (e.g., the downlink channel group or the SSB group) to which the respective rx-endpoints belong. The capability information810may indicate each rx-endpoint via a static-low-level-rx-endpoint parameter.

At820, the DU804may allocate eAxCIDs to RU endpoints based on the capability information810. For example, the DU804may allocate group indices based on the quantity of groups indicated by the capability information810. The DU804may also allocate group layers/streams within a group based on the quantity of endpoints indicated by the capability information810.

At822, the DU804may apply an encoding technique to the RU port identifier of an eAxC message. In some examples, the DU804may use the eAxCIDs allocations to apply the encoding technique. In some examples, the DU804may apply a first encoding technique in which dedicated bits are allocated to a group index and to a per-group layer/stream index. In some examples, the DU804may apply a second encoding technique in which a bitmask may be used to indicate the group and a varying quantity of bits may be used to reference the endpoints associated with the respective group.

At824, the DU804may encode a group index based on the encoding technique. For example, the DU804may use a first portion of the RU port identifier to encode the group index. At826, the DU804may encode an RU endpoint based on the encoding technique. For example, the DU804may use a second portion of the RU port identifier to encode the per-group layer/stream index.

Referring to the example ofFIG. 6, the first portion of the RU port identifier may correspond to the group index612. In such examples, the first portion of the RU port identifier may correspond to a static bit width (e.g., two bits). The DU804may determine to which of the blocks620,622,624the eAxC message corresponds based on the eAxCIDs allocations. The DU804may then encode information regarding the block via the group index and the first portion of the RU port identifier (e.g., at824). The second portion of the RU port identifier may correspond to the per-group layer/stream index614. Similar to the first portion of the RU port identifier, the second portion of the RU port identifier may correspond to a static bit width (e.g., six bits) to accommodate the maximum quantity of endpoints within an endpoint group. The DU804may encode information regarding the RU endpoint via the per-group layer/stream index and the second portion of the RU port identifier (e.g., at826).

Referring to the example ofFIG. 7, the first portion of the RU port identifier may correspond to a bitmask with a bit width that may be based on the quantity of endpoint groups. The DU804may determine the endpoint group and the block720,722,724based on the bitmask. The DU804may then encode information regarding the block via the group index and the first portion of the RU port identifier (e.g., at824). The second portion of the RU port identifier may correspond to the remaining bits of the RU port identifier after the bitmask. As shown inFIG. 7, the bit width of the second portion of the RU port identifier may depend on the bit width of the RU port identifier and the bit width of the bitmask. The DU804may encode information regarding the RU endpoint via the per-group layer/stream index and the second portion of the RU port identifier (e.g., at826).

In some examples, the DU804may transmit an eAxC allocation configuration830that is received by the RU802. The eAxC allocation configuration830may indicate whether the DU804is applying the first encoding technique or the second encoding technique to the RU port identifiers of an eAxC message. The eAxC allocation configuration830may additionally or alternatively indicate a mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration830may indicate that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group. In an example in which the DU804applies the second encoding technique, the eAxC allocation configuration830may indicate that the MSB set to a first value (“1”) corresponds to the first group, the first two MSBs set to a second value (“01”) corresponds to the second group, and the first three MSBs set to a third value (“001”) corresponds to the third group.

At840, the RU802may configure endpoint groups based on the eAxC allocation configuration830. For example, based on the encoding technique, the RU802may determine how to decode the RU port identifier of an eAxC message to determine which group the eAxC message belongs. The RU802may use the group index to determine where (e.g., to which hardware component) to route the eAxC message for processing.

As shown inFIG. 8, the DU804may transmit an eAxC message850that is received by the RU802. The eAxC message850may include an RU port identifier that is encoded using the first encoding technique or the second encoding technique.

At860, the RU802may decode the RU port identifier of the eAxC message850. The RU802may apply the configured endpoints groups (e.g., at840) to decode the RU port identifier. At862, the RU802may identify an endpoint group based on the decoded RU port identifier. For example, a first portion of the RU port identifier may be encoded with a group index corresponding to the endpoint group. At864, the RU802may index the eAxC message. For example, the RU802may use a second portion of the RU port identifier to determine an RU endpoint of the endpoint group.

Referring to the example ofFIG. 6, the first portion of the RU port identifier may correspond to the group index612. In such examples, the first portion of the RU port identifier may correspond to a static bit width (e.g., two bits). The RU802may determine which of the blocks620,622,624the eAxC message corresponds to based on the group index612. The second portion of the RU port identifier may correspond to the per-group layer/stream index614. Similar to the first portion of the RU port identifier, the second portion of the RU port identifier may correspond to a static bit width (e.g., six bits) to accommodate the maximum quantity of endpoints within an endpoint group.

Referring to the example ofFIG. 7, the first portion of the RU port identifier may correspond to a bitmask with a bit width that may be based on the quantity of endpoint groups. The RU802may determine the endpoint group and the block720,722,724based on the bitmask. The second portion of the RU port identifier may correspond to the remaining bits of the RU port identifier after the bitmask. As shown inFIG. 7, the bit width of the second portion of the RU port identifier may depend on the bit width of the RU port identifier and the bit width of the bitmask.

At870, the RU802may route the eAxC message850to the hardware component configured to process the eAxC message. For example, the RU802may route PUSCH control plane messages to a first hardware component for processing, may route SRS control plane messages to a second hardware component for processing, may route PRACH control plane messages to a third hardware component for processing, may route PDSCH control plane messages to a fourth hardware component for processing, and may route SSB control plane messages to a fifth hardware component for processing. However, other examples may include additional or alternate combinations for routing messages to appropriate hardware components.

In the above description ofFIG. 8, the DU804transmits an eAxC allocation configuration830that the RU802may use to configure the endpoints groups (e.g., at840). In some examples, the DU804may forego transmitting the eAxC allocation configuration830to the RU802. In such examples, the RU802may sample, at832, one or more eAxC messages to configure the endpoints groups (e.g., at840). For example, the RU802may receive eAxC messages834from the DU804. The RU802may use properties of the eAxC messages834to determine the message type associated with the eAxC messages834. For example, the RU802may determine that a first eAxC message of the eAxC messages834corresponds to a PRACH control plane message based on properties of the first eAxC message. Based on properties of a second eAxC message and a third eAxC message of the eAxC messages834, the RU802may determine that the second eAxC message corresponds to an uplink channel control plane message and that the third eAxC message corresponds to an SRS control plane message. The RU802may use the MSBs of the RU port identifier associated with the respective eAxC messages to map the MSBs to the respective group. For example, the RU802may determine that two MSBs are used to indicate a group and the remaining bits of the RU port identifier are used to indicate the RU endpoint within the group. In such examples, the RU802may determine that the DU804applied the first encoding technique and associate a group index (e.g., “00,” “01,” and “11”) with each of the three uplink direction groups.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

In another example, the RU802may determine that an MSB bit is being set to a first value (e.g., a “1”) to indicate a group and that a varying quantity of bits are being used to indicate the RU endpoint within the group. In such examples, the RU802may determine that the DU804applied the second encoding technique and associate a bitmask (e.g., “1,” “01,” and “001”) with each of the three uplink direction groups.

The RU802may then configure the endpoint groups, at840, based on the sampling of the eAxC messages834. For example, based on the sampling of the eAxC messages834(e.g., at832), the RU802may determine whether the DU804applied the first encoding technique or the second encoding technique. When the first encoding technique is applied, the RU802may determine that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group. When the second encoding technique is applied, the RU802may determine that the MSB set to a first value (“1”) corresponds to the first group, the first two MSBs set to a second value (“01”) corresponds to the second group, and the first three MSBs set to a third value (“001”) corresponds to the third group.

FIG. 9is a flowchart900of a method of wireless communication. The method may be performed by an RU of a base station (e.g., the RU180B, the RU802, and/or an apparatus1302ofFIG. 13). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the RU may facilitate communication in an O-RAN.

At902, the RU transmits, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints, as described in connection with the capability information810ofFIG. 8. For example,902may be performed by a capability component1340of the apparatus1302ofFIG. 13. The endpoint groups may include a first set of groups for uplink endpoints and/or a second set of groups for downlink endpoints.

In some examples, the capability information may indicate a quantity of endpoint groups, and a quantity of RU endpoints associated with respective endpoint groups.

At904, the RU receives an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier, as described in connection with the eAxC message850ofFIG. 8. For example,904may be performed by a message component1342of the apparatus1302ofFIG. 13.

At906, the RU uses a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics, as described in connection with862ofFIG. 8. For example,906may be performed by a first portion component1344of the apparatus1302ofFIG. 13.

In some examples, the set of characteristics may be based on one or more of a data layer, a spatial stream, a numerology, and a channel.

At908, the RU uses a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group, as described in connection with864ofFIG. 8. For example,908may be performed by a second portion component1346of the apparatus1302ofFIG. 13.

In some examples, the first portion of the RU port identifier may correspond to a group index, and the second portion of the RU port identifier may correspond to a per-group layer/stream index.

In some examples, the first portion and the second portion may facilitate hierarchical addressing of RU endpoints of the RU.

FIG. 10is a flowchart1000of a method of wireless communication. The method may be performed by an RU of a base station (e.g., the RU180B, the RU802, and/or an apparatus1102ofFIG. 11). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the RU may facilitate communication in an O-RAN.

At1002, the RU transmits, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints, as described in connection with the capability information810ofFIG. 8. For example,1002may be performed by a capability component1340of the apparatus1302ofFIG. 13. The endpoint groups may include a first set of groups for uplink endpoints and/or a second set of groups for downlink endpoints.

In some examples, the capability information may indicate a quantity of endpoint groups, and a quantity of RU endpoints associated with respective endpoint groups.

At1006, the RU receives an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier, as described in connection with the eAxC message850ofFIG. 8. For example,1006may be performed by a message component1342of the apparatus1302ofFIG. 13.

At1010, the RU uses a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics, as described in connection with862ofFIG. 8. For example,1010may be performed by a first portion component1344of the apparatus1302ofFIG. 13.

In some examples, the set of characteristics may be based on one or more of a data layer, a spatial stream, a numerology, and a channel.

At1014, the RU uses a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group, as described in connection with864ofFIG. 8. For example,1014may be performed by a second portion component1346of the apparatus1302ofFIG. 13.

In some examples, the first portion of the RU port identifier may correspond to a group index, and the second portion of the RU port identifier may correspond to a per-group layer/stream index.

In some examples, the first portion and the second portion may facilitate hierarchical addressing of RU endpoints of the RU.

At1016, the RU may route the eAxC message to a processing component based on the RU endpoint of the endpoint group, the processing component configured to process eAxC messages associated with the set of characteristics, as described in connection with870ofFIG. 8. For example,1016may be performed by a routing component1348of the apparatus1302ofFIG. 13.

At1004, the RU may sample a quantity of received eAxC messages to determine an encoding technique associated with respective RU port identifiers of the received eAxC messages, the encoding technique used to encode the first portion and the second portion of the respective RU port identifiers, as described in connection with832ofFIG. 8. For example,1004may be performed by a sampling component1350of the apparatus1302ofFIG. 13.

At1008, the RU may decode the first portion of the RU port identifier based on the encoding technique, as described in connection with862ofFIG. 8. For example,1008may be performed by a decoding component1352of the apparatus1302ofFIG. 13.

At1012, the RU may decode the second portion of the RU port identifier based on the encoding technique, as described in connection with864ofFIG. 8. For example,1012may be performed by the decoding component1352of the apparatus1302ofFIG. 13.

In some examples, the decoding of the first portion of the RU port identifier may be based on a static bit width, and the decoding of the second portion of the RU port identifier may be based on a linear addressing of RU endpoints across the endpoint groups, as described in connection with the example ofFIG. 6

In some examples, the decoding of the first portion of the RU port identifier may be based on a bitmask with a bit width corresponding to the endpoint group, and the decoding of the second portion of the RU port identifier may be based on an RU port identifier bit width and the bit width of the bitmask, as described in connection with the example ofFIG. 7.

FIG. 11is a flowchart1100of a method of wireless communication. The method may be performed by an RU of a base station (e.g., the RU180B, the RU802, and/or an apparatus1302ofFIG. 13). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the RU may facilitate communication in an O-RAN.

At1102, the RU transmits capability information indicating support of endpoint groups, as described in connection with the capability information810ofFIG. 8. For example,1102may be performed by a capability component1340of the apparatus1302ofFIG. 13. In some examples, the capability information may indicate a quantity of endpoint groups and a respective set of endpoints associated with each endpoint group. For example, the capability information may indicate that there are 50 endpoints associated with a first group, 25 endpoints associated with a second group, and 10 endpoints associated with a third group. In some examples, the capability information may indicate which endpoints are associated with which endpoint group (e.g., via a static-low-level-[tr]x-endpoint parameter).

In some examples, the endpoint groups include a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint groups may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint groups may include a downlink channel group and an SSB group associated with the downlink direction. However, other examples may include additional or alternative groups associated with a direction.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

At1104, the RU receives an eAxC message from the DU, as described in connection with the eAxC message850ofFIG. 8. For example,1104may be performed by a message component1342of the apparatus1302ofFIG. 13. The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC. For example, the eAxC may include a DU port identifier, a band sector identifier, a CC identifier, and an RU port identifier, as described in connection with the eAxC400ofFIG. 4. The RU port identifier may be encoded to include a group index and a per-group layer/stream index, as described in connection with the RU port identifier610ofFIG. 6and/or the RU port identifier710ofFIG. 7. The group index and the per-group layer/stream index may be based on the capability information.

At1106, the RU routes the eAxC message to a processing component based in part on the group index included in the eAxC message, as described in connection with870ofFIG. 8. For example, 1106 may be performed by a routing component1348of the apparatus1302ofFIG. 13.

FIG. 12is a flowchart1200of a method of wireless communication. The method may be performed by an RU of a base station (e.g., the RU180B, the RU802, and/or an apparatus1302ofFIG. 13). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the RU may facilitate communication in an O-RAN.

At1202, the RU transmits capability information indicating support of endpoint groups, as described in connection with the capability information810ofFIG. 8. For example,1202may be performed by a capability component1340of the apparatus1302ofFIG. 13. In some examples, the capability information may indicate a quantity of endpoint groups and a respective set of endpoints associated with each endpoint group. For example, the capability information may indicate that there are 50 endpoints associated with a first group, 25 endpoints associated with a second group, and 10 endpoints associated with a third group. In some examples, the capability information may indicate which endpoints are associated with which endpoint group (e.g., via a static-low-level-[tr]x-endpoint parameter).

In some examples, the endpoint groups include a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint groups may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint groups may include a downlink channel group and an SSB group associated with the downlink direction. However, other examples may include additional or alternative groups associated with a direction.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

At1210, the RU receives an eAxC message from the DU, as described in connection with the eAxC message850ofFIG. 8. For example,1210may be performed by a message component1342of the apparatus1302ofFIG. 13. The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC. For example, the eAxC may include an DU port identifier, a band sector identifier, a CC identifier, and an RU port identifier, as described in connection with the eAxC identifier400ofFIG. 4. The RU port identifier may be encoded to include a group index and a per-group layer/stream index, as described in connection with the RU port identifier610ofFIG. 6and/or the RU port identifier710ofFIG. 7. The group index and the per-group layer/stream index may be based on the capability information.

At1214, the RU routes the eAxC message to a processing component based in part on the group index included in the eAxC message, as described in connection with870ofFIG. 8. For example,1214may be performed by a routing component1348of the apparatus1302ofFIG. 13.

In some examples, the RU may decode, at1212, the RU port identifier of the eAxC message to determine the group index included in the eAxC message, as described in connection with860ofFIG. 8. For example,1212may be performed by a decoding component1352of the apparatus1302ofFIG. 13. In some examples, the RU may use the MSBs of the RU port identifier to determine the group index. For example, the first encoding technique (e.g., dedicated bits for the group index and the per-group layer/stream index) may be used to encode the RU port identifier to include the group index. When the first encoding technique is used to encode the RU port identifier, the RU may determine the group index based on a static size field for the group index. For example, in the example ofFIG. 6, the group index612may be determined based on the two MSBs of the RU port identifier610. The RU port identifier may also include a static size field dedicated to the per-group layer/stream index. For example, in the example ofFIG. 6, each group index is associated with a block of 64 group layers/streams based on the six bits dedicated to the per-group layer/stream index614of the RU port identifier610. Based on the static size field dedicated to the per-group layer/stream index, addressing of the per-group layer/stream indexes across the endpoint groups may be linear.

In other examples, the second encoding technique (e.g., a bitmask and a varying per-group layer/stream index size) may be used to encode the RU port identifier to include the group index. When the second encoding technique is used to encode the RU port identifier, the RU may determine the group index based on the location of the first value (e.g., “1”) in the MSBs of the RU port identifier. For example, in the example ofFIG. 7, a first group index may be indicated when the MSB is set to the first value (e.g., “1”), a second group index may be indicated when the next MSB is set to the first value (e.g., “01”), and a third group index may be indicated when the next MSB is set to the first value (e.g., “001”). When a bitmask is used to indicate the group index, the size of the bits used to indicate the per-group layer/stream index may vary. For example, the size of the per-group layer/stream index may be based on the quantity of bits of the RU port identifier and the quantity of bits used to indicate the group index. For example, in the example ofFIG. 7in which the RU port identifier is seven bits, the size of the per-group layer/stream index varies between four bits and six bits based on the quantity of bits used to indicate the group index.

In some examples, the RU may decode the RU port identifier (e.g., at1212) based on configured endpoint groups. For example, at1204, the RU may receive an eAxC allocation configuration, as described in connection with the eAxC allocation configuration830ofFIG. 8. For example,1204may be performed by a configuration component1354of the apparatus1302ofFIG. 13. The eAxC allocation configuration may indicate whether the DU is applying the first encoding technique or the second encoding technique to the RU port identifiers of an eAxC message. The eAxC allocation configuration may additionally or alternatively indicate a mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration may indicate that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group. When applying the second encoding technique, the eAxC allocation configuration may indicate that the MSB set to a first value (“1”) corresponds to the first group, the first two MSBs set to a second value (“01”) corresponds to the second group, and the first three MSBs set to a third value (“001”) corresponds to the third group.

At1208, the RU may configure endpoint groups based on the eAxC allocation configuration, as described in connection with840ofFIG. 8. For example,1208may be performed by the configuration component1354of the apparatus1302ofFIG. 13. For example, based on the encoding technique, the RU may determine how to decode the RU port identifier of an eAxC message to determine which group the eAxC message belongs.

In some examples, the RU may determine endpoint groups without receiving an eAxC allocation configuration from the DU. For example, at1206, the RU may sample a quantity of eAxC messages to determine the encoding technique associated with the RU port identifiers of the received eAxC messages, as described in connection with832ofFIG. 8. For example,1206may be performed by a sampling component1350of the apparatus1302ofFIG. 13. For example, the RU may receive eAxC messages834from the DU804. The RU may use properties of the eAxC messages to determine the message type associated with the received eAxC messages. For example, the RU may determine that a first eAxC message of the plurality of eAxC messages corresponds to a PRACH control plane message based on properties of the first eAxC message. Based on properties of a second eAxC message and a third eAxC message of the plurality of eAxC messages, the RU may determine that the second eAxC message corresponds to an uplink channel control plane message and that the third eAxC message corresponds to an SRS control plane message. The RU may use the MSBs of the RU port identifier associated with the respective eAxC messages to map the MSBs to the respective group. For example, the RU may determine that two MSBs are used to indicate a group and the remaining bits of the RU port identifier are used to indicate the RU endpoint within the group. In such examples, the RU may determine that the DU applied the first encoding technique and associate a group index (e.g., “00,” “01,” and “11”) with each of the three uplink direction groups.

In another example, the RU may determine that an MSB bit is being set to a first value (e.g., a “1”) to indicate a group and that a varying quantity of bits are being used to indicate the RU endpoint within the group. In such examples, the RU may determine that the DU applied the second encoding technique and associate a bitmask (e.g., “1,” “01,” and “001”) with each of the three uplink direction groups.

At1208, the RU may then configure the endpoint groups based on the sampling of the eAxC messages, as described in connection with840ofFIG. 8. For example,1208may be performed by the configuration component1354of the apparatus1302ofFIG. 13. For example, based on the sampling of the plurality of eAxC messages, the RU may determine whether the DU applied the first encoding technique or the second encoding technique. When the first encoding technique is applied, the RU may determine that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group. When the second encoding technique is applied, the RU may determine that the MSB set to a first value (“1”) corresponds to the first group, the first two MSBs set to a second value (“01”) corresponds to the second group, and the first three MSBs set to a third value (“001”) corresponds to the third group.

FIG. 13is a diagram1300illustrating an example of a hardware implementation for an apparatus1302. The apparatus1302is an RU of a base station, a component of a base station, or may implement base station functionality. The apparatus1302includes a baseband unit1304. The baseband unit1304may communicate through a cellular RF transceiver1322with the UE104and/or the DU180A. The baseband unit1304may include a computer-readable medium/memory. The baseband unit1304is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit1304, causes the baseband unit1304to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit1304when executing software. The baseband unit1304further includes a reception component1330, a communication manager1332, and a transmission component1334. The communication manager1332includes the one or more illustrated components. The components within the communication manager1332may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit1304. The baseband unit1304may be a component of the base station310and may include the memory376and/or at least one of the TX processor316, the RX processor370, and the controller/processor375.

The communication manager1332includes a capability component1340that is configured to transmitting, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints, for example, as described in connection with902ofFIG. 9 and/or 1002ofFIG. 10. The example capability component1340may also be configured to transmit capability information indicating support of endpoint groups, for example, as described in connection with1102ofFIG. 11 and/or 1202ofFIG. 12.

The communication manager1332also includes a message component1342that is configured to receive an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier, for example, as described in connection with904ofFIG. 9 and/or 1006ofFIG. 10. The example message component1342may also be configured to receive an eAxC message from a DU, for example, as described in connection with1104ofFIG. 11 and/or 1210ofFIG. 12.

The communication manager1332also includes a first portion component1344that is configured to use a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics, for example, as described in connection with906ofFIG. 9 and/or 1010ofFIG. 10.

The communication manager1332also includes a second portion component1346that is configured to use a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group, for example, as described in connection with908ofFIG. 9 and/or 1014ofFIG. 10.

The communication manager1332also includes a routing component1348that is configured to route the eAxC message to a processing component based on the RU endpoint of the endpoint group, the processing component configured to process eAxC messages associated with the set of characteristics, for example, as described in connection with1016ofFIG. 10. The example routing component1348may also be configured to route the eAxC message to a processing component based in part on the group index included in the eAxC message, for example, as described in connection with1106ofFIG. 11 and/or 1214ofFIG. 12.

The communication manager1332also includes a sampling component1350that is configured to sample a quantity of received eAxC messages to determine an encoding technique associated with respective RU port identifiers of the received eAxC messages, the encoding technique used to encode the first portion and the second portion of the respective RU port identifiers, for example, as described in connection with1004ofFIG. 10. The example sampling component1350may also be configured to sample a quantity of received eAxC messages to determine an encoding technique associated with RU port identifiers of the received eAxC messages, for example, as described in connection with1206ofFIG. 12.

The communication manager1332also includes a decoding component1352that is configured to decode the first portion of the RU port identifier based on the encoding technique, for example, as described in connection with1008ofFIG. 10. The example decoding component1352may also be configured to decode the second portion of the RU port identifier based on the encoding technique, for example, as described in connection with1012ofFIG. 10. The example decoding component1352may also be configured to decode the RU port identifier of the eAxC message to determine the group index, for example, as described in connection with1212ofFIG. 12.

The communication manager1332also includes a configuration component1354that is configured to receive an eAxC allocation configuration, for example, as described in connection with1204ofFIG. 12. The example configuration component1354may also be configured to configure endpoints groups, for example, as described in connection with1208ofFIG. 12.

As shown, the apparatus1302may include a variety of components configured for various functions. In one configuration, the apparatus1302, and in particular the baseband unit1304, includes transmitting, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints

The example apparatus1302also includes means for receiving an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier. The example apparatus1302also includes means for using a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics. The example apparatus1302also includes means for using a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group.

In another configuration, the example apparatus1302also includes means for routing the eAxC message to a processing component based on the RU endpoint of the endpoint group, the processing component configured to process eAxC messages associated with the set of characteristics.

In another configuration, the example apparatus1302also includes means for sampling a quantity of received eAxC messages to determine an encoding technique associated with respective RU port identifiers of the received eAxC messages, the encoding technique used to encode the first portion and the second portion of the respective RU port identifiers. The example apparatus1302also includes means for decoding the first portion of the RU port identifier based on the encoding technique. The example apparatus1302also includes means for decoding the second portion of the RU port identifier based on the encoding technique.

In another configuration, the example apparatus1302also includes means for decoding the first portion of the RU port identifier is based on a static bit width. The example apparatus1302also includes means for decoding the second portion of the RU port identifier is based on linear addressing of RU endpoints across the endpoint groups.

In another configuration, the example apparatus1302also includes means for decoding the first portion of the RU port identifier is based on a bitmask with a bit width corresponding to the endpoint group. The example apparatus1302also includes means for decoding the second portion of the RU port identifier is based on an RU port identifier bit width and the bit width of the bitmask.

In another configuration, the example apparatus1302also includes means for facilitating hierarchical addressing of RU endpoints of the RU.

In another configuration, the example apparatus1302includes means for transmitting, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints. The example apparatus1302also includes means for receiving an eAxC message from the DU, the eAxC message including a group index based on the capability information. The example apparatus1302also includes means for routing the eAxC message to a processing component based in part on the group index included in the eAxC message.

In another configuration, the example apparatus1302also includes means for sampling a quantity of received eAxC messages to determine an encoding technique associated with RU port identifiers of the received eAxC messages, the encoding technique used to encode the group index and a per-group layer/stream index of the RU port identifiers.

In another configuration, the example apparatus1302also includes means for receiving an eAxC allocation configuration from the DU.

In another configuration, the example apparatus1302also includes means for configuring endpoints groups.

In another configuration, the example apparatus1302also includes means for decoding the RU port identifier of the eAxC message to determine the group index.

The means may be one or more of the components of the apparatus1302configured to perform the functions recited by the means. As described supra, the apparatus1302may include the TX processor316, the RX processor370, and the controller/processor375. As such, in one configuration, the means may be the TX processor316, the RX processor370, and the controller/processor375configured to perform the functions recited by the means.

FIG. 14is a flowchart1400of a method of wireless communication. The method may be performed by a DU of a base station (e.g., the DU180A, the DU804, and/or an apparatus1802ofFIG. 18). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the DU may facilitate communication in an O-RAN.

At1402, the DU receives, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints, as described in connection with the capability information810ofFIG. 8. For example,1402may be performed by a capability component1840of the apparatus1802ofFIG. 18.

In some examples, the capability information may indicate a quantity of endpoint groups and a respective set of endpoints associated with each endpoint group. For example, the capability information may indicate that there are 50 endpoints associated with a first group, 25 endpoints associated with a second group, and 10 endpoints associated with a third group. In some examples, the capability information may indicate which endpoints are associated with which endpoint group (e.g., via a static-low-level-[tr]x-endpoint parameter).

In some examples, the endpoint groups include a first set of groups for uplink endpoints and/or a second set of groups for downlink endpoints. For example, the endpoint groups may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint groups may include a downlink channel group and an SSB group associated with the downlink direction. However, other examples may include additional or alternative groups associated with a direction.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

At1404, the DU encodes, based on the capability information, an endpoint group associated with the eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier, as described in connection with824ofFIG. 8. For example,1404may be performed by a first portion component1846of the apparatus1802ofFIG. 18.

At1406, the DU encodes an RU endpoint of the endpoint group using a second portion of the RU port identifier, as described in connection with826ofFIG. 8. For example,1406may be performed by a second portion component1848of the apparatus1802ofFIG. 18.

In some examples, the first portion and the second portion may facilitate hierarchical addressing of RU endpoints of the RU.

In some examples, the encoding of the endpoint group using the first portion of the RU port identifier may be based on a static bit width, and the encoding of the RU endpoint point using the second portion of the RU port identifier may be based on a linear addressing of RU endpoints across the endpoint groups, as described in connection with the example ofFIG. 6

In some examples, the encoding of the endpoint group using the first portion of the RU port identifier may be based on a bitmask with a bit width corresponding to the endpoint group, and the encoding of the RU endpoint point using the second portion of the RU port identifier may be based on an RU port identifier bit width and the bit width of the bitmask, as described in connection with the example ofFIG. 7.

At1408, the DU transmits the eAxC message to the RU, as described in connection with the eAxC message850ofFIG. 8. For example,1408may be performed by a message component1850of the apparatus1802ofFIG. 18. The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC identifier.

FIG. 15is a flowchart1500of a method of wireless communication. The method may be performed by a DU of a base station (e.g., the DU180A, the DU804, and/or an apparatus1802ofFIG. 18). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the DU may facilitate communication in an O-RAN.

At1502, the DU receives, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints, as described in connection with the capability information810ofFIG. 8. For example,1502may be performed by a capability component1840of the apparatus1802ofFIG. 18.

In some examples, the capability information may indicate a quantity of endpoint groups and a respective set of endpoints associated with each endpoint group. For example, the capability information may indicate that there are 50 endpoints associated with a first group, 25 endpoints associated with a second group, and 10 endpoints associated with a third group. In some examples, the capability information may indicate which endpoints are associated with which endpoint group (e.g., via a static-low-level-[tr]x-endpoint parameter).

In some examples, the endpoint groups include a first set of groups for uplink endpoints and/or a second set of groups for downlink endpoints. For example, the endpoint groups may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint groups may include a downlink channel group and an SSB group associated with the downlink direction. However, other examples may include additional or alternative groups associated with a direction.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

At1504, the DU may allocate an eAxC message to an RU endpoint of an endpoint group based on a set of characteristics associated with the eAxC message, as described in connection with820ofFIG. 8. For example,1504may be performed by an allocation component1842of the apparatus1802ofFIG. 18. The DU may allocate group indices based on the quantity of groups indicated by the capability information. The DU may also allocate group layers/streams within a group based on the quantity of endpoints indicated by the capability information. The set of characteristics may be based on one or more of a data layer, a spatial stream, a numerology, and a channel.

At1506, the DU may apply an encoding technique to an RU port identifier, as described in connection with822ofFIG. 8. For example,1506may be performed by an encoding component1844of the apparatus1802ofFIG. 18. In some examples, the DU may use the encoding technique to encode a group index using a first portion of the RU port identifier and a per-group layer/stream index using a second portion of the RU port identifier.

At1508, the DU encodes, based on the capability information, an endpoint group associated with the eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier, as described in connection with824ofFIG. 8. For example,1508may be performed by a first portion component1846of the apparatus1802ofFIG. 18.

At1510, the DU encodes an RU endpoint of the endpoint group using a second portion of the RU port identifier, as described in connection with826ofFIG. 8. For example,1510may be performed by a second portion component1848of the apparatus1802ofFIG. 18.

In some examples, the first portion and the second portion may facilitate hierarchical addressing of RU endpoints of the RU.

At1512, the DU transmits the eAxC message to the RU, as described in connection with the eAxC message850ofFIG. 8. For example,1512may be performed by a message component1850of the apparatus1802ofFIG. 18. The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC identifier.

In some examples, the encoding of the endpoint group using the first portion of the RU port identifier may be based on a static bit width, and the encoding of the RU endpoint point using the second portion of the RU port identifier may be based on a linear addressing of RU endpoints across the endpoint groups, as described in connection with the example ofFIG. 6

In some examples, the encoding of the endpoint group using the first portion of the RU port identifier may be based on a bitmask with a bit width corresponding to the endpoint group, and the encoding of the RU endpoint point using the second portion of the RU port identifier may be based on an RU port identifier bit width and the bit width of the bitmask, as described in connection with the example ofFIG. 7.

FIG. 16is a flowchart1600of a method of wireless communication. The method may be performed by a DU of a base station (e.g., the DU180A, the DU804, and/or an apparatus1802ofFIG. 18). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the DU may facilitate communication in an O-RAN.

At1602, the DU receives capability information indicating support of endpoint groups from an RU, as described in connection with the capability information810ofFIG. 8. For example,1602may be performed by a capability component1840of the apparatus1802ofFIG. 18. In some examples, the capability information may indicate a quantity of endpoint groups and a respective set of endpoints associated with each endpoint group. For example, the capability information may indicate that there are 50 endpoints associated with a first group, 25 endpoints associated with a second group, and 10 endpoints associated with a third group. In some examples, the capability information may indicate which endpoints are associated with which endpoint group (e.g., via a static-low-level-Mx-endpoint parameter).

In some examples, the endpoint groups include a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint groups may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint groups may include a downlink channel group and an SSB group associated with the downlink direction. However, other examples may include additional or alternative groups associated with a direction.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

At1604, the DU allocates eAxC messages to RU endpoints within respective endpoint groups baes in part on the capability information, as described in connection with820ofFIG. 8. For example,1604may be performed by an allocation component1842of the apparatus1802ofFIG. 18. For example, the DU may allocate group indices based on the quantity of groups indicated by the capability information. The DU may also allocate group layers/streams within a group based on the quantity of endpoints indicated by the capability information.

At1606, the DU transmits an eAxC message to the RU, the eAxC message including the group index associated with an endpoint group, as described in connection with the eAxC message850ofFIG. 8. For example,1606may be performed by a message component1850of the apparatus1802ofFIG. 18.

The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC. For example, the eAxC may include a DU port identifier, a band sector identifier, a CC identifier, and an RU port identifier, as described in connection with the eAxC identifier400ofFIG. 4. The RU port identifier may be encoded to include a group index and a per-group layer/stream index, as described in connection with the RU port identifier610ofFIG. 6and/or the RU port identifier710ofFIG. 7. The group index and the per-group layer/stream index may be based on the capability information.

FIG. 17is a flowchart1700of a method of wireless communication. The method may be performed by a DU of a base station (e.g., the DU180A, the DU804, and/or an apparatus1802ofFIG. 18). The method may facilitate simplified switching at the RU based on an eAxC allocation policy. In some examples, the DU may facilitate communication in an O-RAN.

At1702, the DU receives capability information indicating support of endpoint groups from an RU, as described in connection with the capability information810ofFIG. 8. For example,1702may be performed by a capability component1840of the apparatus1802ofFIG. 18. In some examples, the capability information may indicate a quantity of endpoint groups and a respective set of endpoints associated with each endpoint group. For example, the capability information may indicate that there are 50 endpoints associated with a first group, 25 endpoints associated with a second group, and 10 endpoints associated with a third group. In some examples, the capability information may indicate which endpoints are associated with which endpoint group (e.g., via a static-low-level-Mx-endpoint parameter).

In some examples, the endpoint groups include a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint groups may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint groups may include a downlink channel group and an SSB group associated with the downlink direction. However, other examples may include additional or alternative groups associated with a direction.

In some examples, the RU endpoints associated with a group may be associated with a same set of characteristics. For example, uplink endpoints may be associated with a first set of properties and downlink endpoints may be associated with a second set of properties. In some examples, uplink channel endpoints may be associated with a first set of properties, SRS endpoints may be associated with a second set of properties, PRACH endpoints may be associated with a third set of properties, downlink channel endpoints may be associated with a fourth set of properties, and SSB endpoints may be associated with a fifth set of properties.

At1704, the DU allocates eAxC messages to RU endpoints within respective endpoint groups baes in part on the capability information, as described in connection with820ofFIG. 8. For example,1704may be performed by an allocation component1842of the apparatus1802ofFIG. 18. For example, the DU may allocate group indices based on the quantity of groups indicated by the capability information. The DU may also allocate group layers/streams within a group based on the quantity of endpoints indicated by the capability information.

At1706, the DU may transmit an eAxC allocation configuration to the RU, as described in connection with the eAxC allocation configuration830ofFIG. 8. For example,1706may be performed by a configuration component1852of the apparatus1802ofFIG. 18. The eAxC allocation configuration may indicate whether the DU is applying the first encoding technique or the second encoding technique to the RU port identifiers of an eAxC message. The eAxC allocation configuration may additionally or alternatively indicate a mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration may indicate that a first group index (“00”) corresponds to the first group, a second group index (“01”) corresponds to the second group, and a third group index (“10”) corresponds to the third group. When applying the second encoding technique, the eAxC allocation configuration may indicate that the MSB set to a first value (“1”) corresponds to the first group, the first two MSBs set to a second value (“01”) corresponds to the second group, and the first three MSBs set to a third value (“001”) corresponds to the third group.

At1708, the DU may forego transmitting the eAxC allocation configuration to the RU. For example,1708may be performed by the configuration component1852of the apparatus1802ofFIG. 18.

At1710, the DU may apply an encoding technique to an RU port identifier of an eAxC message to encode the group index and the per-group layer/stream index, as described in connection with822ofFIG. 8. For example,1710may be performed by an encoding component1844of the apparatus1802ofFIG. 18.

In some examples, the DU may apply a first encoding technique in which dedicated bits are allocated to a group index and to a per-group layer/stream index. For example, the first encoding technique (e.g., dedicated bits for the group index and the per-group layer/stream index) may be used to encode the RU port identifier to include the group index. When the first encoding technique is used to encode the RU port identifier, the DU may encode the group index based on a static size field for the group index. For example, in the example ofFIG. 6, the group index612may be encoded based on the two MSBs of the RU port identifier610. The RU port identifier may also include a static size field dedicated to the per-group layer/stream index. For example, in the example ofFIG. 6, each group index is associated with a block of 64 group layers/streams based on the six bits dedicated to the per-group layer/stream index614of the RU port identifier610. Based on the static size field dedicated to the per-group layer/stream index, addressing of the per-group layer/stream indexes across the endpoint groups may be linear.

In other examples, the second encoding technique (e.g., a bitmask and a varying per-group layer/stream index size) may be used to encode the RU port identifier to include the group index. When the second encoding technique is used to encode the RU port identifier, the DU may encode the group index based on the location of the first value (e.g., “1”) in the MSBs of the RU port identifier. For example, in the example ofFIG. 7, a first group index may be indicated when the MSB is set to the first value (e.g., “1”), a second group index may be indicated when the next MSB is set to the first value (e.g., “01”), and a third group index may be indicated when the next MSB is set to the first value (e.g., “001”). When a bitmask is used to indicate the group index, the size of the bits used to indicate the per-group layer/stream index may vary. For example, the size of the per-group layer/stream index may be based on the quantity of bits of the RU port identifier and the quantity of bits used to indicate the group index. For example, in the example ofFIG. 7in which the RU port identifier is seven bits, the size of the per-group layer/stream index varies between four bits and six bits based on the quantity of bits used to indicate the group index.

At1712, the DU transmits an eAxC message to the RU, the eAxC message including the group index associated with an endpoint group, as described in connection with the eAxC message850ofFIG. 8. For example,1712may be performed by a message component1850of the apparatus1802ofFIG. 18.

The eAxC message may include an M-plane message, a C-plane message, or an S-plane message including an eAxC. For example, the eAxC may include a DU port identifier, a band sector identifier, a CC identifier, and an RU port identifier, as described in connection with the eAxC identifier400ofFIG. 4. The RU port identifier may be encoded to include a group index and a per-group layer/stream index, as described in connection with the RU port identifier610ofFIG. 6and/or the RU port identifier710ofFIG. 7. The group index and the per-group layer/stream index may be based on the capability information.

FIG. 18is a diagram1800illustrating an example of a hardware implementation for an apparatus1802. The apparatus1802is a DU of a base station, a component of a base station, or may implement base station functionality. The apparatus1102includes a baseband unit1804. The baseband unit1804may communicate through a cellular RF transceiver1822with the UE104and/or the RU180B. The baseband unit1804may include a computer-readable medium/memory. The baseband unit1804is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit1804, causes the baseband unit1804to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit1804when executing software. The baseband unit1804further includes a reception component1830, a communication manager1832, and a transmission component1834. The communication manager1832includes the one or more illustrated components. The components within the communication manager1832may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit1804. The baseband unit1804may be a component of the base station310and may include the memory376and/or at least one of the TX processor316, the RX processor370, and the controller/processor375.

The communication manager1832includes a capability component1840that is configured to receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints, for example, as described in connection with1402ofFIG. 14 and/or 1502ofFIG. 15. The example capability component1840may also be configured to receive capability information indicating support of endpoint groups from an RU, for example, as described in connection with1602ofFIG. 16 and/or 1702ofFIG. 17.

The communication manager1832also includes an allocation component1842that is configured to allocate the eAxC message to the RU endpoint of the endpoint group based on a set of characteristics associated with the eAxC message, for example, as described in connection with1504ofFIG. 15. The example allocation component1842may also be configured to allocate eAxC messages to RU endpoints within respective endpoint groups based in part on the capability information, for example, as described in connection with1604ofFIG. 16 and/or 1704ofFIG. 17.

The communication manager1832also includes an encoding component1844that is configured to apply an encoding technique to an RU port identifier of the eAxC message to encode the group index and a per-group layer/stream index, for example, as described in connection with1506ofFIG. 15 and/or 1710ofFIG. 17.

The communication manager1832also includes a first portion component1846that is configured to encode, based on the capability information, an endpoint group associated with an eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier, for example, as described in connection with1404ofFIG. 14 and/or 1508ofFIG. 15.

The communication manager1832also includes a second portion component1848that is configured to encode an RU endpoint of the endpoint group using a second portion of the RU port identifier, for example, as described in connection with1406ofFIG. 14 and/or 1510ofFIG. 15.

The communication manager1832also includes a message component1850that is configured to transmit the eAxC message to the RU, for example, as described in connection with1408ofFIG. 14 and/or 1512ofFIG. 15. The example message component1850may also be configured to transmit an eAxC message to the RU, the eAxC message including a group index associated with an endpoint group, for example, as described in connection with1606ofFIG. 16 and/or 1712ofFIG. 17.

The communication manager1832also includes a configuration component1852that is configured to transmit an eAxC allocation configuration, for example, as described in connection with1706ofFIG. 17. The example configuration component1852may also be configured to forego transmitting an eAxC allocation configuration, for example, as described in connection with1708ofFIG. 17.

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts ofFIGS. 14, 15, 16, and/or17. As such, each block in the flowcharts ofFIGS. 14, 15, 16, and/or17may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus1802may include a variety of components configured for various functions. In one configuration, the apparatus1802, and in particular the baseband unit1804, includes means for receiving, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints. The example apparatus1802also includes means for encoding, based on the capability information, an endpoint group associated with an eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier. The example apparatus1802also includes means for encoding an RU endpoint of the endpoint group using a second portion of the RU port identifier. The example apparatus1802also includes means for transmitting the eAxC message to the RU.

In another configuration, the example apparatus1802also includes means for allocating the eAxC message to the RU endpoint of the endpoint group based on a set of characteristics associated with the eAxC message.

In another configuration, the example apparatus1802also includes means for encoding the endpoint group using the first portion of the RU port identifier is based on a static bit width. The example apparatus1802also includes means for encoding the RU endpoint using the second portion of the RU port identifier is based on linear addressing of RU endpoints across the endpoint groups.

In another configuration, the example apparatus1802also includes means for encoding the endpoint group using the first portion of the RU port identifier is based on a bitmask with a bit width corresponding to the endpoint group. The example apparatus1802also includes means for encoding the RU endpoint using the second portion of the RU port identifier is based on an RU port identifier bit width and the bit width of the bitmask.

In another configuration, the example apparatus1802also includes means for facilitating hierarchical addressing of RU endpoints of the RU.

In another configuration, the example apparatus1802includes means for receiving, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints. The example apparatus1802also includes means for allocating eAxC messages to RU endpoints within respective endpoint groups based in part on the capability information. The example apparatus1802also includes means for transmitting an eAxC message to the RU, the eAxC message including a group index associated with an endpoint group.

In another configuration, the example apparatus1802also includes means for applying an encoding technique to an RU port identifier of the eAxC message to encode the group index and a per-group layer/stream index.

In another configuration, the example apparatus1802also includes means for transmitting an eAxC allocation configuration to the RU.

In another configuration, the example apparatus1802also includes means for foregoing transmitting an eAxC allocation configuration to the RU.

The means may be one or more of the components of the apparatus1802configured to perform the functions recited by the means. As described supra, the apparatus1802may include the TX processor316, the RX processor370, and the controller/processor375. As such, in one configuration, the means may be the TX processor316, the RX processor370, and the controller/processor375configured to perform the functions recited by the means.

Aspects disclosed herein configure an RU to receive an eAxC message and to perform switching based on the RU port identifier of the eAxC message. For example, a DU may encode the RU port identifier to indicate a group index via a first portion of the RU port identifier and to indicate a per-group layer/stream index via a second portion of the RU port identifier. The group index may indicate an endpoint group (e.g., the uplink channel group, the SRS group, or the PRACH group in the uplink direction, and the downlink channel group or the SRS group in the downlink direction) and the per-group layer/stream index may indicate the RU endpoint. The RU may decode the RU port identifier to determine the endpoint group and the group layer/stream, and then route the eAxC message to the correct hardware component for processing based on the group index. By using the first portion and the second portion of the RU port identifier to index the eAxC message, aspects disclosed herein facilitate hierarchical addressing of RU endpoints of the RU.

Additionally, aspects disclosed herein configure the RU to receive an eAxC message and to perform switching based on the RU port identifier of the eAxC message. For example, the DU may encode the RU port identifier to include a group index and a per-group layer/stream index. The group index may indicate an endpoint group and the per-group layer/stream index may indicate the RU endpoint. The RU may decode the group index and then route the eAxC message to the correct hardware component for processing based on the group index.

The aspects presented herein may enable improving RU ingress routing, for example, by simplifying switching based on an eAxC allocation policy and/or reducing costs associated with lookup table sizes and lookup table processing.

Aspect 1 is an apparatus for wireless communication RAN RU including at least one processor coupled to a memory and configured to transmit, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints; receive an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier; use a first portion of the RU port identifier to identify an endpoint group, the respective set of RU endpoints of the endpoint group associated with a set of characteristics; and use a second portion of the RU port identifier to index the eAxC message to an RU endpoint of the endpoint group.

Aspect 2 is the apparatus of aspect 1, further including that the memory and the at least one processor are further configured to route the eAxC message to a processing component based on the RU endpoint of the endpoint group, the processing component configured to process eAxC messages associated with the set of characteristics.

Aspect 3 is the apparatus of any of aspects 1 and 2, further including that the endpoint groups include one or more of a first set of groups for uplink endpoints, and a second set of groups for downlink endpoints.

Aspect 4 is the apparatus of any of aspects 1 to 3, further including that the first portion of the RU port identifier corresponds to a group index and the second portion of the RU port identifier corresponds to a per-group layer/stream index.

Aspect 5 is the apparatus of any of aspects 1 to 4, further including that the capability information indicates a quantity of endpoint groups, and a quantity of RU endpoints associated with respective endpoint groups.

Aspect 6 is the apparatus of any of aspects 1 to 5, further including that the memory and at least one processor are further configured to sample a quantity of received eAxC messages to determine an encoding technique associated with respective RU port identifiers of the received eAxC messages, the encoding technique used to encode the first portion and the second portion of the respective RU port identifiers; decode the first portion of the RU port identifier based on the encoding technique; and decode the second portion of the RU port identifier based on the encoding technique.

Aspect 7 is the apparatus of any of aspects 1 to 6, further including that decoding the first portion of the RU port identifier is based on a static bit width, and decoding the second portion of the RU port identifier is based on linear addressing of RU endpoints across the endpoint groups

Aspect 8 is the apparatus of any of aspects 1 to 6, further including that decoding the first portion of the RU port identifier is based on a bitmask with a bit width corresponding to the endpoint group, and decoding the second portion of the RU port identifier is based on an RU port identifier bit width and the bit width of the bitmask

Aspect 9 is the apparatus of any of aspects 1 to 8, further including that the first portion and the second portion facilitate hierarchical addressing of RU endpoints of the RU.

Aspect 10 is the apparatus of any of aspects 1 to 9, further including that the set of characteristics are based on one or more of a data layer, a spatial stream, a numerology, and a channel.

Aspect 11 is a method of wireless communication for implementing any of aspects 1 to 10.

Aspect 12 is an apparatus for wireless communication including means for implementing any of aspects 1 to 10.

Aspect 13 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 1 to 10.

Aspect 14 is an apparatus for wireless communication at a RAN DU including at least one processor coupled to a memory and configured to receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints; encode, based on the capability information, an endpoint group associated with an eAxC message using a first portion of an RU port identifier, the eAxC message including a DU port identifier, a band sector identifier, a component carrier identifier, and the RU port identifier; encode an RU endpoint of the endpoint group using a second portion of the RU port identifier; and transmit the eAxC message to the RU.

Aspect 15 is the apparatus of aspect 14, further including that the memory and the at least one processor are further configured to allocate the eAxC message to the RU endpoint of the endpoint group based on a set of characteristics associated with the eAxC message.

Aspect 16 is the apparatus of any of aspects 14 and 15, further including that the set of characteristics are based on one or more of a data layer, a spatial stream, a numerology, and a channel.

Aspect 17 is the apparatus of any of aspects 14 to 16, further including that the endpoint groups include one or more of a first set of groups for uplink endpoints, and a second set of groups for downlink endpoints.

Aspect 18 is the apparatus of any of aspects 14 to 17, further including that the first portion of the RU port identifier corresponds to a group index and the second portion of the RU port identifier corresponds to a per-group layer/stream index.

Aspect 19 is the apparatus of any of aspects 14 to 18, further including that the capability information indicates a quantity of endpoint groups, and a quantity of RU endpoints associated with respective endpoint groups.

Aspect 20 is the apparatus of any of aspects 14 to 19, further including that the encoding the endpoint group using the first portion of the RU port identifier is based on a static bit width, and encoding the RU endpoint using the second portion of the RU port identifier is based on linear addressing of RU endpoints across the endpoint groups

Aspect 21 is the apparatus of any of aspects 14 to 19, further including that the encoding the endpoint group using the first portion of the RU port identifier is based on a bitmask with a bit width corresponding to the endpoint group, and encoding the RU endpoint using the second portion of the RU port identifier is based on an RU port identifier bit width and the bit width of the bitmask.

Aspect 22 is the apparatus of any of aspects 14 to 21, further including that the first portion and the second portion facilitate hierarchical addressing of RU endpoints of the RU.

Aspect 23 is a method of wireless communication for implementing any of aspects 14 to 22.

Aspect 24 is an apparatus for wireless communication including means for implementing any of aspects 14 to 22.

Aspect 25 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 14 to 22.

Aspect 26 is an apparatus for wireless communication at a RAN RU including at least one processor coupled to a memory and configured to transmit, to a DU, capability information indicating support of endpoint groups, each endpoint group associated with a respective set of RU endpoints; receive an eAxC message from the DU, the eAxC message including a group index based on the capability information; and route the eAxC message to a processing component based in part on the group index included in the eAxC message.

Aspect 27 is the apparatus of aspect 26, further including that the eAxC message includes a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier, the RU port identifier including the group index and a per-group layer/stream index.

Aspect 28 is the apparatus of any of aspects 26 and 27, further including that the endpoint groups include a first set of groups for uplink endpoints and a second set of groups for downlink endpoints.

Aspect 29 is the apparatus of any of aspects 26 to 28, further including that RU endpoints allocated to a same endpoint group are associated with a same set of characteristics.

Aspect 30 is the apparatus of any of aspects 26 to 29, further including that the capability information indicates a quantity of endpoint groups and a quantity of RU endpoints associated with each of the respective endpoint groups.

Aspect 31 is the apparatus of any of aspects 26 to 30, further including that the memory and the at least one processor are further configured to sample a quantity of received eAxC messages to determine an encoding technique associated with RU port identifiers of the received eAxC messages, the encoding technique used to encode the group index and a per-group layer/stream index of the RU port identifiers.

Aspect 32 is the apparatus of any of aspects 26 to 31, further including that the encoding technique includes a static size field for the group index and linear addressing of per-group layer/stream indexes across the endpoint groups.

Aspect 33 is the apparatus of any of aspects 26 to 31, further including that the encoding technique includes a bitmask for the group index and a size of the per-group layer/stream index associated with a respective group index is based on a size of the RU port identifier and a size of the respective bitmask.

Aspect 34 is a method of wireless communication for implementing any of aspects 26 to 33.

Aspect 35 is an apparatus for wireless communication including means for implementing any of aspects 26 to 33.

Aspect 36 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 26 to 33.

Aspect 37 is an apparatus for wireless communication at a RAN RU including at least one processor coupled to a memory and configured to receive, from an RU, capability information indicating support of endpoint groups by the RU, each endpoint group associated with a respective set of RU endpoints; allocate eAxC messages to RU endpoints within respective endpoint groups based in part on the capability information; and transmit an eAxC message to the RU, the eAxC message including a group index associated with an endpoint group.

Aspect 38 is the apparatus of aspect 37, further including that the eAxC message includes a DU port identifier, a band sector identifier, a component carrier identifier, and an RU port identifier, the RU port identifier including the group index and a per-group layer/stream index.

Aspect 39 is the apparatus of any of aspects 37 and 38, further including that the endpoint groups include a first set of groups for uplink endpoints and a second set of groups for downlink endpoints.

Aspect 40 is the apparatus of any of aspects 37 to 39, further including that RU endpoints allocated to a same endpoint group are associated with a same set of characteristics.

Aspect 41 is the apparatus of any of aspects 37 to 40, further including that the capability information indicates a quantity of endpoint groups and a quantity of RU endpoints associated with each of the respective endpoint groups.

Aspect 42 is the apparatus of any of aspects 37 to 41, further including that the memory and the at least one processor are further configured to apply an encoding technique to an RU port identifier of the eAxC message to encode the group index and a per-group layer/stream index.

Aspect 43 is the apparatus of any of aspects 37 to 42, further including that the encoding technique includes a static size field for the group index and linear addressing of per-group layer/stream indexes across the endpoint groups.

Aspect 44 is the apparatus of any of aspects 37 to 42, further including that the encoding technique includes a bitmask for the group index and a size of the per-group layer/stream index associated with a respective group index is based on a size of the RU port identifier and a size of the respective bitmask.

Aspect 45 is a method of wireless communication for implementing any of aspects 37 to 44.

Aspect 46 is an apparatus for wireless communication including means for implementing any of aspects 37 to 44.

Aspect 47 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 37 to 44.