Extended antenna carrier allocation strategy for simplified handover

Abstract

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

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. nonprovisional patent application serial number 17 / 374,770, filed July 13, 2021, entitled “Extended Antenna-Carrier Allocation Policy for Simplified Switching,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to communication systems, and more specifically, to communication utilizing an Open Radio Access Network (O-RAN). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. One example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CLE) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0006] A simplified summary of one or more aspects is given below to provide a basic understanding of these aspects. This summary is not a broad overview of all anticipated aspects, nor is it intended to identify key or essential elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description given later.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication at a radio unit (RU). An exemplary apparatus may transmit capability information indicating support for endpoint groups to a distributed unit (DU), each endpoint group being associated with a corresponding set of RU endpoints. The exemplary apparatus may also receive, based on the capability information, an extended antenna carrier (eAxC) message from the DU, the eAxC message including a DU port identifier, a frequency band sector identifier, a component carrier identifier, and an RU port identifier. Additionally, the exemplary apparatus may use a first portion of the RU port identifier to identify an endpoint group, the corresponding set of RU endpoints for which the endpoint group is associated with a feature set. The exemplary apparatus may also use a second portion of the RU port identifier to index the eAxC message to the RU endpoints of the endpoint group.

[0008] In another aspect of this disclosure, methods, computer-readable media, and apparatus for wireless communication at an RU are provided. An exemplary apparatus may send capability information to a DU indicating support for endpoint groups, each endpoint group associated with a corresponding set of RU endpoints. The exemplary apparatus may also receive an eAxC message from the DU, the eAxC message including a group index based on the capability information. Additionally, the exemplary apparatus may route the eAxC message to a processing component in part based on the group index included in the eAxC message.

[0009] In another aspect of this disclosure, methods, computer-readable media, and apparatus for wireless communication at a DU are provided. An exemplary apparatus can receive capability information from an RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints. The exemplary apparatus can also, based on the capability information, encode the 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 frequency band sector identifier, a component carrier identifier, and the RU port identifier. Additionally, the exemplary apparatus can use a second portion of the RU port identifier to encode the RU endpoints of the endpoint group. The exemplary apparatus can also transmit the eAxC message to the RU.

[0010] In another aspect of this disclosure, methods, computer-readable media, and apparatus for wireless communication at a DU are provided. An exemplary apparatus may receive capability information from a RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints. The exemplary apparatus may also allocate eAxC messages to RU endpoints within a corresponding endpoint group, in part based on the capability information. Additionally, the exemplary apparatus may send an eAxC message to the RU, the eAxC message including a group index associated with the endpoint group.

[0011] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some illustrative features of one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of these aspects may be employed, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A This is an illustration showing an example of the first frame of various aspects according to this disclosure.

[0014] Figure 2B This is an illustration showing an example of a DL channel within a subframe according to various aspects of this disclosure.

[0015] Figure 2C This is an illustration of an example of a second frame showing various aspects of this disclosure.

[0016] Figure 2D This is an illustration showing an example of a UL channel within a subframe according to various aspects of this disclosure.

[0017] Figure 3 This is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0018] Figure 4 This is a diagram illustrating an exemplary extended antenna carrier (eAxC) identifier.

[0019] Figure 5 This is a diagram illustrating an exemplary eAxC allocation for DU.

[0020] Figure 6 This is a diagram illustrating an exemplary allocation strategy for grouping RU endpoints.

[0021] Figure 7 This is a diagram illustrating another exemplary allocation strategy for grouping RU endpoints.

[0022] Figure 8 This is an exemplary communication flow between the RU and DU according to the teachings disclosed herein.

[0023] Figure 9 This is a flowchart of a method for wireless communication at the RU based on the teachings disclosed herein.

[0024] Figure 10 This is a flowchart of a method for wireless communication at the RU based on the teachings disclosed herein.

[0025] Figure 11 This is a flowchart of a method for wireless communication at the RU based on the teachings disclosed herein.

[0026] Figure 12 This is a flowchart of a method for wireless communication at the RU based on the teachings disclosed herein.

[0027] Figure 13 This is an illustration showing an example of a hardware implementation of an exemplary device in accordance with the teachings disclosed herein.

[0028] Figure 14 This is a flowchart of a method for wireless communication at a DU based on the teachings disclosed herein.

[0029] Figure 15 This is a flowchart of a method for wireless communication at a DU based on the teachings disclosed herein.

[0030] Figure 16 This is a flowchart of a method for wireless communication at a DU based on the teachings disclosed herein.

[0031] Figure 17 This is a flowchart of a method for wireless communication at a DU based on the teachings disclosed herein.

[0032] Figure 18 This is an illustration showing an example of a hardware implementation of an exemplary device in accordance with the teachings disclosed herein. Detailed Implementation

[0033] The detailed description below, illustrated with reference to the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0034] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). Such elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0035] For example, elements, any part of elements, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0036] Accordingly, in one or more example aspects, the described functionality can be implemented using hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium capable of being used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0037] While aspects and implementations are described in this application through illustrations of some examples, those skilled in the art will understand that additional implementations and use cases may arise in many other arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and / or uses may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) enabled devices, etc.). While some examples may or may not specifically point to a use case or application, the applicability of various types of the described innovations can be observed. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, aggregated or deaggregated components, end-user equipment, etc., of different sizes, shapes, and constructions.

[0038] The aspects disclosed herein provide techniques for simplifying message routing to the correct hardware components for processing (also known as "switching"). The disclosed techniques configure an RU to determine the group of endpoints in the transmission direction (e.g., uplink or downlink). The RU can then indicate which group a receiving endpoint ("rx endpoint") or sending endpoint ("tx endpoint") belongs to. For example, the RU can announce which group a tx endpoint or rx endpoint belongs to by sending capability information to a DU. That is, for each endpoint (e.g., which may generally be referred to as a "[tr]x endpoint"), the RU can indicate which group that endpoint belongs to. In some examples, the endpoint can be indicated via a corresponding "static low-level tx endpoint" parameter or "static low-level rx endpoint" parameter.

[0039] Furthermore, the aspects disclosed herein configure the RU to receive eAxC messages (e.g., messages including 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 tier index or flow index per group (referred to herein as a "tier / flow index per group"). The group index indicates the group, and the tier / flow index per group indicates 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 indexing the eAxC message using the first and second parts of the RU port identifier, the aspects disclosed herein facilitate hierarchical addressing of the RU endpoints.

[0040] Figure 1 This is an illustration of an example of a wireless communication system and access network 100 including base station 102, base station 180, and UE 104.

[0041] Access network 100 may include an Open Radio Access Network (O-RAN) to provide standardized radio interfaces to facilitate interoperability between component radio equipment. Base station 180 may be an O-RAN base station, and based on low-level functional partitioning, base station 180 may include DU 180A and RU 180B. The O-RAN may include an Open Fronthaul (FH) interface between DU 180A and RU 180B.

[0042] In some aspects, the RU 180B can be configured to manage one or more aspects of wireless communication by indicating support for endpoint groups. For example, the RU 180B may include an eAxC packet announcement component 198 configured to send capability information indicating support for endpoint groups to the DU, each endpoint group being associated with a corresponding set of RU endpoints. The exemplary eAxC packet announcement component 198 may 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 frequency band sector identifier, a component carrier identifier, and an RU port identifier. Additionally, the exemplary eAxC packet announcement component 198 may be configured to use a first portion of the RU port identifier to identify an endpoint group, the corresponding set of RU endpoints for which the endpoint group is associated with a feature set. The exemplary eAxC packet announcement component 198 may also be configured to use a second portion of the RU port identifier to index the eAxC message to the RU endpoints of the endpoint group.

[0043] In another configuration, the eAxC packet advertisement component 198 can be configured to send capability information indicating support for endpoint groups to the DU, each endpoint group being associated with a corresponding set of RU endpoints. The exemplary eAxC packet advertisement component 198 can also be configured to receive eAxC messages from the DU, the eAxC messages including a group index based on the capability information. The exemplary eAxC packet advertisement component 198 can also be configured to route the eAxC message to a processing component in part based on the group index included in the eAxC message.

[0044] In another configuration, the DU 180A can be configured to manage one or more aspects of wireless communication by allocating eAxC endpoints based on the capabilities of the RU. For example, the DU 180A may include an eAxC allocation component 199 configured to receive capability information from the RU indicating the RU's support for endpoint groups, each endpoint group associated with a corresponding set of RU endpoints. The exemplary eAxC allocation component 199 can 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 frequency band sector identifier, a component carrier identifier, and the RU port identifier. Additionally, the exemplary eAxC allocation component 199 can be configured to encode RU endpoints of the endpoint group using a second portion of the RU port identifier. The exemplary eAxC allocation component 199 can also be configured to send the eAxC message to the RU.

[0045] In another configuration, the eAxC allocation component 199 can be configured to receive capability information from an RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints. The exemplary eAxC allocation component 199 can also be configured to allocate eAxC messages to RU endpoints within a corresponding endpoint group, in part based on the capability information. Additionally, the exemplary eAxC allocation component can be configured to send an eAxC message to the RU, the eAxC message including a group index associated with the endpoint group.

[0046] The aspects presented in this paper can enable improvements to RU ingress routing, for example, by simplifying switching and / or reducing the costs associated with lookup table size and lookup table processing through an eAxC-based allocation strategy.

[0047] While the following description provides examples for 5G NR (and particularly for O-RAN with 5G NR), the concepts described herein are applicable to other similar domains where the RAN can be configured via open RAN (such as LTE, LTE-A, CDMA, GSM and / or other wireless technologies).

[0048] Figure 1Examples of wireless communication systems (also known as wireless wide area networks (WWANs)) include base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0049] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can be connected to core network 190 via a second backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and transmission of alarm messages. Base stations 102 can communicate directly or indirectly with each other via a third backhaul link 134 (e.g., an X2 interface) (e.g., via EPC 160 or core network 190). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0050] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolution Node B (eNB) (HeNB), which can provide service to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a carrier aggregation totaling up to YxMHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0051] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0052] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in unlicensed spectrum at 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0053] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

[0054] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often referred to as the "below 6GHz" band (interchangeably). A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

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

[0056] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0057] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short ranging. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0058] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0059] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services in the Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 belonging to a Multicast-Broadcast Single Frequency Network (MBSFN) area belonging to a broadcast-specific service, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0060] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node for processing signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0061] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable terminology. Base station 102 provides access to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term. In some contexts, the term UE may also be applied to one or more accompanying devices, such as in a device constellation arrangement. One or more of these devices may jointly access the network and / or individually access the network.

[0062] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Multiplexing (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Multiplexing (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown with slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format by receiving a Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically controlled via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0063] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure can be applied to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 subframes (1 ms) of the same size. Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and digital scheme. The digital scheme defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0064]

[0065] For a normal CP (14 symbols / slot), different digital schemes μ0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, digital scheme 2 allows 4 slots per subframe. Accordingly, for both the normal CP and digital scheme μ0, there are 14 symbols / slot and 2 slots per subframe. μ One time slot / subframe. The subcarrier spacing can be equal to 2. μ*15kHz, where μ represents digital schemes 0 through 4. Thus, the subcarrier spacing is 15kHz for digital scheme μ=0 and 240kHz for digital scheme μ=4. The symbol length / duration is inversely correlated with the subcarrier spacing. Figures 2A to 2D Examples are provided for a normal CP with 14 symbols per time slot and a digital scheme μ=2 with 4 time slots per subframe. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific digital scheme and CP (standard or extended).

[0066] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0067] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0068] Figure 2BExamples of various DL channels within a subframe of the illustrated frame. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs). Each CCE includes six RE Groups (REGs), and each REG includes 12 consecutive REs within an OFDM symbol of an RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) is located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on this PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0069] like Figure 2C As shown, some REs carry DM-RS (denoted as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or second symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a probe reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0070] Figure 2DExamples of various UL channels within a subframe of the illustrated frame. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / NACK) feedback. The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0071] Figure 3 This is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. In the example shown, the first wireless device may include a base station 310, the second wireless device may include a UE 350, and the base station 310 may communicate with the UE 350 in an access network. Figure 3 As shown, base station 310 includes a transmit processor (TX processor 316), a transceiver 318 including transmitter 318a and receiver 318b, an antenna 320, a receive processor (RX processor 370), a channel estimator 374, a controller / processor 375, and a memory 376. Example UE 350 includes an antenna 352, a transceiver 354 including transmitter 354a and receiver 354b, an RX processor 356, a channel estimator 358, a controller / processor 359, a memory 360, and a TX processor 368. In other examples, base station 310 and / or UE 350 may include additional or replacement components.

[0072] In the DL, IP packets from EPC 160 can be provided to the controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] The TX processor 316 and RX processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping for the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to generate a physical channel for carrying the time-domain OFDM symbol stream. The OFDM streams are spatially precoded to produce multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimate can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318a. Each transmitter 318a can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0074] In UE 350, each receiver 354b receives signals via its corresponding antenna 352. Each receiver 354b recovers the information modulated onto the RF carrier and provides this information to the RX processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 310. These soft decisions can be based on the channel estimate calculated by channel estimator 358. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0075] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0076] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0077] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to a different antenna 352 via separate transmitters 354a. Each transmitter 354a can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0078] UL transmissions are processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318b receives signals via its respective antenna 320. Each receiver 318b recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0079] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0080] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform and Figure 1 The various aspects of the combination of the eAxC group notification component 198 and / or the eAxC allocation component 199.

[0081] To establish a connection in the network, the UE first connects to the radio access network (RAN). This RAN communicates directly with the user and acts as the interface between the UE and the network core (such as...). Figure 1 The RAN may include gateways between the core network 190 and other networks. This RAN may include base stations, such as… Figure 1 The base station 180 includes a baseband unit (BBU) and radio equipment (RE). The BBU and RE together perform digital signal processing functions related to the protocol stack.

[0082] In some examples, the network may employ an O-RAN to provide standardized radio interfaces to facilitate interoperability between component radio equipment. For instance, in an O-RAN, the RAN may be decomposed into centralized units (CUs), distributed units (DUs), and radio units (RUs). The RU (sometimes referred to herein as an "O-RU") facilitates the transmission, reception, amplification, and / or digitization of radio frequency (RF) signals. The RU may be located at, near, or integrated with an antenna. The DU and CU provide computing capabilities and 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.

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

[0084] The lower-level functions of this protocol stack can be split between the DU and the RU. In the first example split, RF functions (such as signal sampling and baseband uplink / downlink switching) are performed by the RU. This type of split allows for a relatively simple and cost-effective RU, with the DU performing most of the baseband processing. However, this type of split also imposes strict latency constraints on the FH, for example, to meet timing-sensitive protocols such as HARQ. In the second example split, the DU and RU functions can be split between the RLC layer and the PDCP layer. In this type of split, timing-sensitive protocols (such as HARQ) can be moved from the DU to the RU along with MAC layer functions and PHY layer functions. This type of split allows for a relaxation of latency constraints on the FH. However, this type of split can also increase the complexity of the RU.

[0085] In the third example split, the RU performs digital beamforming, CP add / remove, and FFT functions, while the DU performs higher-level functions starting from resource element (RE) mapping / demapping. This type of split, also known as a "7.2x split," results in data transmitted on the FH including in-phase and quadrature (IQ) samples. This exemplary 7.2x split can be adapted to an appropriate data transfer rate between the DU and the RU to facilitate time-sensitive protocols, while also balancing the processing workload at the DU and the RU.

[0086] In some examples, the FH (Frequency Host) between the DU and the RU can be implemented via a fiber optic connection. This FH interface may include a control / user / synchronization (C / U / S) plane and a management (M) plane.

[0087] The C-plane is the control plane, which specifically refers to the real-time control between the DU and the RU. The U-plane is the user plane, which refers to the IQ sample data transmitted between the DU and the RU. The S-plane is the synchronization plane, which refers to the traffic between the RU or the DU and the synchronization controller. The M-plane is the management plane, which refers to the management operations that share configuration management between the DU and the RU.

[0088] During network system startup, a set of configuration management messages can be exchanged on the M-plane between the DU and the RU. The DU and the RU can then configure the M-plane accordingly and use this configuration for C / U / S plane communication.

[0089] After the network system starts up, the M-plane configuration can be dynamically changed via Remote Procedure Call (RPC) messages. For example, the DU and RU can dynamically change the M-plane configuration with get-config and edit-config RPCs. In some aspects, the DU and RU can use the RPC messages to exchange protocols, such as the NETCONF protocol. The RPC messages can dynamically change the M-plane configuration between the DU and the RU.

[0090] Messages exchanged between the DU and the RU may use an extended antenna carrier (eAxC) identifier as both the source and destination identifier. This eAxC identifier may be included in the message header. As used herein, "eAxC message" can 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.

[0091] Figure 4 This is an illustration of an exemplary eAxC identifier 400. The exemplary eAxC identifier 400 can be used to facilitate communication in the O-RAN. Figure 4 In the example, the eAxC identifier 400 includes the DU port identifier 402 (“DU_Port_ID”), the band sector identifier 404 (“BandSector_ID”), the component carrier (CC) identifier 406 (“CC_ID”), and the RU port identifier 408 (“RU_Port_ID”).

[0092] Figure 5 It is shown that it is used for DU (such as Figure 1 An illustration of an exemplary eAxC allocation 500 of an exemplary DU 180A. The eAxC allocation 500 can facilitate communication in the O-RAN. The exemplary eAxC allocation 500 includes different component carrier / bandwidth / layer combinations. For example, a configuration (also referred to as an “M-plane configuration”) may indicate a frequency range 502 (“band”), the number of component carriers 504 (“CC”), the bandwidth allocation 506 (“BW MHz”) associated with each component carrier, and the number of layers / streams 508 (“layers / streams”). The number of CC 504, bandwidth allocation 506, and layer / stream 508 can be used to determine the total layer / stream bandwidth allocation 510 (“BW”).

[0093] exist Figure 5 In the example, the configuration also indicates downlink group 512 and uplink group 514. For example... Figure 5As shown, downlink group 512 includes a number of downlink channel endpoints (“DL channels”) (PDSCH) and a number of SSB endpoints (“SSB”). Uplink group 514 includes a number of uplink channel endpoints (“UL channels”) (PUSCH), a number of SRS endpoints (“SRS”), and a number of Physical Random Access Channel (PRACH) endpoints (“PRACH”). Figure 5 In the example, downlink group 512 and uplink group 514 are indicated for each component carrier. The exemplary eAxC allocation 500 also includes a number of downlink eAxC allocations 516 (“eAxC DL”) and a number of uplink eAxC allocations 518 (“eAxC UL”). This number of downlink eAxC allocations 516 and the number of uplink eAxC allocations 518 are based on the number of component carriers 504 and the number indicated in the respective downlink group 512 and uplink group 514.

[0094] For example, eAxC allocation 500 includes a first configuration 520 that indicates an FR1 band, two component carriers, a 100MHz bandwidth, and 16 layers / streams, resulting in a 3200MHz layer / stream bandwidth allocation (2 * 100MHz * 16 = 3200MHz). The first configuration 520 also indicates a number of 34 downlink eAxC allocations 516 based on the two component carriers, 16 downlink channel endpoints, and one SSB endpoint (e.g., 2 * (16 + 1) = 34). The first configuration 520 also indicates a number of 168 uplink eAxC allocations 518 based on the two component carriers, 16 uplink channel endpoints, 64 SRS endpoints, and four PRACH endpoints (e.g., 2 * (16 + 64 + 4) = 168).

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

[0096] like Figure 5As shown, the number of uplink eAxC allocations 518 and / or downlink eAxC allocations 516 can be large. Furthermore, when the RU receives a message such as a control plane message, it can determine the hardware component to which the message should be processed. For example, in the uplink direction, the RU can receive control plane messages associated with the uplink channel (PUSCH), SRS, or PRACH. In the downlink direction, the RU can receive control plane messages associated with the downlink channel or SSB. Based on the direction and type of the message, the RU can route the message to the appropriate hardware component for processing. For example, the RU can route PUSCH control plane messages to a first hardware component, SRS control plane messages to a second hardware component, PRACH control plane messages to a third hardware component, PDSCH control plane messages to a fourth hardware component, and SSB control plane messages to a fifth hardware component.

[0097] It is understood that two or more of these hardware components can be the same hardware component applying different processing techniques to process the corresponding control plane messages. For example, the RU can route PUSCH control plane messages, SRS control plane messages, and PRACH control plane messages to a first hardware component that applies different techniques to process these messages. The RU can also route PDSCH control plane messages and SSB control plane messages to a second hardware component that applies different techniques to process these messages. In another example, the RU can route PRACH control plane messages to the first hardware component, PUSCH and PDSCH control plane messages to the second hardware component, and SRS and SSB control plane messages to a third hardware component. The second hardware component can be configured to apply different techniques to process PUSCH and PDSCH control plane messages. The third hardware component can be configured to apply different techniques to process SRS and SSB control plane messages. However, other examples may include additional or alternative combinations for routing messages to hardware components.

[0098] The aspects disclosed herein provide techniques for simplifying message routing to the correct hardware components for processing. The disclosed techniques configure the RU to determine the group of endpoints in the transmission direction (e.g., uplink or downlink). For example, in the uplink direction, the RU may determine the uplink channel (PUSCH) group, SRS group, and PRACH group. In the downlink direction, the RU may determine the downlink channel group and SSB group. The RU may then indicate which group a receiving endpoint (“rx endpoint”) or transmitting endpoint (“tx endpoint”) belongs to. For example, the RU may announce which group a tx endpoint or rx endpoint belongs to by sending capability information to the DU. That is, for each endpoint (e.g., which may generally be referred to as a “[tr]x endpoint”), the RU indicates which group the endpoint belongs to. In some examples, the endpoint may be indicated via a corresponding “static low-level tx endpoint” parameter or a “static low-level rx endpoint” parameter.

[0099] For example, the RU can determine that there are 85 rx endpoints, which can be grouped into three rx endpoint groups A, B, and C. The RU can announce that group A includes 50 rx endpoints, group B includes 25 rx endpoints, and group C includes 10 rx endpoints. That is, in order to reach the 85 rx endpoints, the RU can indicate the group to which the corresponding rx endpoint belongs (e.g., group A, group B, or group C).

[0100] The DU can receive advertised endpoint packets and perform eAxC identifier (“eAxCID”) allocation. The eAxCID allocation may include allocating RU port allocations, such as assigning an RU port identifier to each eAxCID.

[0101] Additionally, the aspects disclosed herein configure the RU to receive eAxC messages (e.g., including messages such as...). Figure 4 The DU can use an exemplary eAxC identifier 400 (the eAxC identifier of the message) and perform a handover 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 a second portion of the RU port identifier to include a layer / flow index for each group. The group index may indicate an endpoint group (e.g., an uplink channel group, SRS group, or PRACH group in the uplink direction, and a downlink channel group or SRS group in the downlink direction), and the layer / flow index for each group 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 the endpoint group. The RU may then use the second portion of the RU port identifier to determine the RU endpoint and route the eAxC message to the correct hardware component for processing based on the layer / flow index for each group.

[0102] As described above, the DU can assign RU port allocations to each eAxCID allocation. The DU can apply encoding techniques to the RU port identifier to indicate the endpoint group and endpoint group tier / flow. In some examples, the encoding technique may include dedicated bits for the group index and for the tier / flow index for each group to indicate the corresponding endpoint group and group tier / flow (or RU endpoint). In some examples, the DU may apply encoding techniques including bitmasking to indicate the endpoint group.

[0103] Figure 6 Figure 600 illustrates an exemplary allocation strategy for grouping RU endpoints, as presented herein. For example, a DU may receive capability information from the RU indicating the number of groups and the number of endpoints associated with each group. Figure 6 The examples shown include three example groups 602, 604, and 606 (e.g., group A, group B, and group C), each containing a corresponding number of RU endpoints. Figure 6 As shown, the first group 602 includes 50 endpoints, the second group 604 includes 25 endpoints, and the third group 606 includes 10 endpoints. In the example shown, the RU endpoint is associated with the RU receiving endpoint (“rx endpoint”).

[0104] exist Figure 6 In the example, the DU will apply an encoding technique that includes dedicated bits to the group index and the layer / stream index for each group. The DU can determine the number of bits dedicated to the group index based on the number of groups. For example, the DU can be based on... Figure 6 The three groups 602, 604, and 606 determine that two bits of the RU port identifier will be dedicated to that group index.

[0105] The DU can determine the number of bits dedicated to the layer / stream index for each group based on the number of endpoints associated with each group. For example, regarding the first group 602 (e.g., group A), the DU can allocate six bits to represent the 50 endpoints. In a similar manner, the DU can determine to allocate five bits to represent the 25 endpoints associated with the second group 604 (e.g., group B), and can determine to allocate four bits to represent the 10 endpoints associated with the third group 606 (e.g., group C).

[0106] exist Figure 6 In the example, the DU can use the maximum number of bits allocated to a group to represent the endpoints of each group. For instance, based on the six bits allocated to represent the 50 endpoints associated with the first group 602, the DU might determine to allocate two bits to indicate the group index and six bits to indicate the tier / stream index for each group. Figure 6As shown, the RU port identifier 610 comprises eight bits, including two bits dedicated to the group index 612 (“GrpIndex”) and six bits dedicated to the layer / stream index 614 (“GrpLayerIndex”) for each group. The two bits of the group index 612 can represent each of the three groups 602, 604, and 606, and the six bits of the layer / stream index 614 for each group can represent each endpoint within any group. Therefore, the group index 612 and the layer / stream index 614 for each group are associated with a corresponding static bit width (or “length in bits”).

[0107] exist Figure 6 In the example, the first group index (“00”) may correspond to the first group 602. The six bits of the layer / stream index 614 of each group may represent the first block 620 of 64 different group layers / streams, and 50 of the 64 different group layers / streams in the first block 620 may correspond to the 50 endpoints associated with the 50 endpoints of the first group 602. The second block 622 of 64 different group layers / streams may represent group layers / streams 64 to 127 associated with the second group index (“01”), and 25 of the 64 different group layers / streams in the second block 622 may correspond to the 25 endpoints associated with the 25 endpoints of the second group 604. The third block 624 may represent group layers / flows 128 to 191 associated with the third group index (“10”), and 10 of the 64 different group layer / flow endpoints of the third block 624 may correspond to the 10 endpoints associated with the 10 endpoints of the third group 606. Figure 6 As shown, the fourth block 626 can represent group layers / flows 192 to 255 associated with the fourth group index (“11”). However, in Figure 6 In the example, the group layer / flow of the fourth block 626 cannot correspond to an endpoint because a total of 85 endpoints across these three groups have been assigned.

[0108] As shown in the figure Figure 6 Example encoding techniques include dedicated bits for group indices and dedicated bits for layer / stream indices per group. Such encoding techniques provide linear addressing across groups. For example, each group in 602, 604, and 606 is 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., blocks 620, 622, and 624), and each group layer / stream of a block can be mapped to an endpoint associated with the corresponding group. Additionally, Figure 6The example encoding technique allows for simpler switching at the RU because the RU can determine the hardware component to route the message based on the group index indicated by the RU port identifier of the eAxC message, rather than processing the complete RU port identifier or trying to route the message to a different hardware component to determine the correct hardware component. For example, in Figure 6 In the example, the RU can use the two most significant bits (MSB) of the RU port identifier 610 to determine where to route the eAxC message and route the eAxC message to the correct hardware component accordingly.

[0109] However, as Figure 6 As shown, this type of encoding technique can lead to wasted group layers / streams because there are unused group layers / streams (e.g., group layers / streams not mapped to the endpoints of a group). For example, while the third block 624 includes 64 group layers / streams, in... Figure 6 In the example, only ten groups / flows from these groups / flows are assigned to the endpoints.

[0110] exist Figure 6 In one example, the DU assigns an eAxCID to each of the endpoints received in the capability information. For example, the DU assigns 85 endpoints to 85 groups of layers / streams within the first three blocks 620, 622, and 624. In some examples, the DU may determine to assign a subset of the endpoints. For example, the DU may determine to assign eAxCIDs to half of the endpoints in the first group 602. In such an example, the DU may allocate five bits to represent half of the endpoints in the first group 602 (e.g., 25 endpoints), five bits to represent 25 endpoints in the second group 604, and four bits to represent 10 endpoints in the third group 606. By assigning eAxCIDs only to half of the endpoints in the first group 602, the DU can reduce the size of the RU port identifier to a total of seven bits (e.g., two dedicated bits for the group index and five dedicated bits for the layer / stream index per group). In such an example, the RU can still use the two MSBs of the RU port identifier to route messages.

[0111] Figure 7 This is illustration 700, showing another exemplary allocation strategy for grouping RU endpoints, as presented herein. Similar to... Figure 6 For example, the DU can receive capability information from the RU, which indicates the number of groups and the number of endpoints associated with each group. Figure 7 The illustrated examples include three example groups 702, 704, and 706 (e.g., group A, group B, and group C), each containing a corresponding number of RU endpoints. Figure 7As shown, the first group 702 includes 50 endpoints, the second group 704 includes 25 endpoints, and the third group 706 includes 10 endpoints. In the example shown, the RU endpoint is associated with the RU receiving endpoint (“rx endpoint”). (As combined with...) Figure 6 As described in the examples, the 50 endpoints of the first group 702 can be represented by six bits, the 25 endpoints of the second group 704 can be represented by five bits, and the 10 endpoints of the third group 706 can be represented by four bits.

[0112] exist Figure 7 In the example, the DU application includes bitmask encoding techniques to indicate the endpoint group. For example, the position of the first value of the MSB (e.g., "1") can be used to indicate the group and distinguish it from other groups. The bit width of the layer / stream index for each group can vary based on the bitmask.

[0113] For example, in Figure 7 In this context, the endpoint associated with the first group 702 can be indicated by setting the MSB bit 0 (“MSB_Bit_0”) of the RU port identifier 710 to a first value (e.g., “1”). Setting the MSB bit 0 to the first value distinguishes the group A endpoint from the non-group A endpoint. The next six bits of the RU port identifier 710 (e.g., MSB bits 1 to 6) can be assigned to reference the endpoint associated with the first group 702.

[0114] The endpoint associated with the second group 704 can be indicated by setting MSB bit 0 to a second value (e.g., "0") and setting the next MSB ("MSB_Bit_1") to a first value (e.g., "1"). Setting MSB bit 0 of the RU port identifier 710 to a second value (e.g., "0") indicates that the corresponding eAxC message is not associated with the first group 702. However, when the RU port identifier 710 is decoded, the RU can determine that the corresponding eAxC message is associated with the second group 704 based on the next MSB ("MSB_Bit_1") being set to a first value (e.g., "1"). The remaining five bits of the RU port identifier 710 (e.g., MSB bits 2 to 6) can be allocated to reference the endpoint associated with the second group 704.

[0115] The endpoint associated with the third group 706 can be indicated by setting MSB bits 0 and 1 to a second value (e.g., "0") and setting MSB bit 2 ("MSB_Bit_2") of the RU port identifier 710 to a first value (e.g., "1"). When the RU port identifier 710 is decoded, the RU can determine that the corresponding eAxC message is not associated with the first group 702 and the second group 704 based on the first two MSBs set to the second value (e.g., "0"). However, the RU can determine that the corresponding eAxC message is associated with the third group 706 based on the next MSB ("MSB_Bit_2") set to the first value (e.g., "1"). The remaining four bits of the RU port identifier 710 (e.g., MSB bits 3 to 6) can be allocated to reference the endpoint associated with the third group 706.

[0116] and Figure 6 Compared to other encoding techniques, Figure 7 The encoding technique facilitates the allocation of eAxCID to each of the 85 endpoints using the seven bits allocated to the RU port identifier 710. However, the bit width (or size) of the bitmask associated with such an encoding technique varies based on the number of groups. Furthermore, addressing across these groups is non-linear. For example, based on the six bits allocated to reference endpoints associated with the first group 702, there are 64 group layers / streams associated with the first block 720 (e.g., group layers / streams 0 to 63); based on the five bits allocated to reference endpoints associated with the second group 704, there are 32 group layers / streams associated with the second block 722 (e.g., group layers / streams 64 to 95); and based on the four bits allocated to reference endpoints associated with the third group 706, there are 16 group layers / streams associated with the third block 724 (e.g., group layers / streams 96 to 111).

[0117] Although the first exemplary encoding technique (e.g., Figure 6 The dedicated bits (or static bit width) and the second exemplary encoding technique (e.g., Figure 7The bitmask provided provides an example where the second encoding technique, based on an example of 85 endpoints, produces a smaller RU port identifier (e.g., seven bits to eight bits). However, it is understood that the second encoding technique may produce a smaller RU port identifier when applied to real-world use cases. For example, referring to exemplary eAxC allocation 500, a first exemplary configuration 520 includes three groups in the uplink direction (e.g., an uplink channel group, an SRS group, and a 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 a total of eight bits, including two dedicated bits indicating one of the three groups and six dedicated bits referencing the maximum number of endpoints associated with the group (e.g., the 64 endpoints associated with the SRS group).

[0118] Conversely, by applying this second encoding technique to the first exemplary configuration 520, seven bits can be allocated to the RU port identifier. For example, to indicate an SRS endpoint, the MSB can be set to a first value (e.g., "1") to indicate the SRS group, and then six additional bits can be used to reference 64 SRS endpoints, resulting in seven bits being used to indicate the SRS group and the corresponding endpoint. To indicate an uplink channel endpoint, the MSB can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 1) can be set to a first value (e.g., "1") to indicate the uplink channel group, and then four bits can be used to reference 16 uplink channel endpoints, resulting in six bits being used to indicate the uplink channel group and the corresponding endpoint. However, since seven bits are required to indicate an SRS endpoint, it is understood that five bits can be used to reference 16 uplink channel endpoints, keeping the size of the RU port identifier constant at seven bits. To indicate PRACH endpoints, the first two MSBs can be set to the second value (e.g., "0"), and the next MSB (e.g., MSB bit 2) can be set to the first value (e.g., "1"). Then, two additional bits can be used to reference four PRACH endpoints, resulting in five bits used to indicate the PRACH group and its corresponding endpoint. However, since seven bits are needed to indicate SRS endpoints, it is understandable that four bits can be used to reference four PRACH endpoints, keeping the size of the RU port identifier constant at seven bits.

[0119] Therefore, referring to the first exemplary configuration 520 of eAxC allocation 500, applying the second encoding technique results in a smaller RU port identifier (e.g., seven bits) compared to applying the first encoding technique (e.g., eight bits).

[0120] In another example, the second exemplary configuration 522 of the eAxC allocation 500 includes 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 a total of six bits, including two dedicated bits indicating one of the three groups and four dedicated bits referencing the maximum number of endpoints associated with the group (e.g., the 16 endpoints associated with the SRS group).

[0121] Conversely, by applying this second encoding technique to the second exemplary configuration 522, five bits can be allocated to the RU port identifier. For example, to indicate an SRS endpoint, the MSB can be set to a first value (e.g., "1") to indicate the SRS group, and then four additional bits can be used to reference 16 SRS endpoints, resulting in five bits being used to indicate the SRS group and the corresponding endpoint. To indicate an uplink channel endpoint, the MSB can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 1) can be set to a first value (e.g., "1") to indicate the uplink channel group, and then two bits can be used to reference 4 uplink channel endpoints, resulting in four bits being used to indicate the uplink channel group and the corresponding endpoint. However, since five bits are required to indicate an SRS endpoint, it is understood that three bits can be used to reference 4 uplink channel endpoints, keeping the size of the RU port identifier constant at five bits. To indicate a PRACH endpoint, the first two MSBs can be set to the second value (e.g., "0"), and the next MSB (e.g., MSB bit 2) can be set to the first value (e.g., "1"). Then, two additional bits can be used to reference four PRACH endpoints, resulting in five bits used to indicate the PRACH group and the corresponding endpoint.

[0122] Therefore, referring to the second exemplary configuration 522 of eAxC allocation 500, applying the second encoding technique results in a smaller RU port identifier (e.g., five bits) compared to applying the first encoding technique (e.g., six bits).

[0123] In another example, again referring to the first exemplary configuration 520, 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 includes a total of five bits, including one dedicated bit indicating one of the two groups and four dedicated bits referencing the maximum number of endpoints associated with the group (e.g., the 16 endpoints associated with the downlink channel group).

[0124] By applying this second encoding technique to the first exemplary configuration 520, five bits can also be used to indicate the RU port identifier. For example, to indicate a downlink channel endpoint, the MSB can be set to a first value (e.g., "1") to indicate the downlink channel group, and then four additional bits can be used to reference the endpoints of 16 downlink channels, resulting in five bits being used to indicate the downlink channel group and the corresponding endpoint. To indicate an SSB endpoint, the MSB can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 1) can be set to a first value (e.g., "1") to indicate the SSB group, and then one bit can be used to reference one SSB endpoint, resulting in three bits being used to indicate the SSB group and the corresponding endpoint. However, since five bits are required to indicate a downlink channel endpoint, it is understood that three bits can be used to reference one SSB endpoint, keeping the size of the RU port identifier constant at five bits. To indicate a PRACH endpoint, the first two MSBs can be set to the second value (e.g., "0"), and the next MSB (e.g., MSB bit 2) can be set to the first value (e.g., "1"). Then, two additional bits can be used to reference four PRACH endpoints, resulting in five bits used to indicate the PRACH group and the corresponding endpoint.

[0125] Therefore, referring to the downlink direction of the first exemplary configuration 520 of eAxC allocation 500, applying the first encoding technique and the second encoding technique results in RU port identifiers of the same bit width (e.g., five bits).

[0126] However, it is understood that in some examples, using a static bit width for the encoding technique can be advantageous compared to using a bit mask for the encoding technique. For example, a third exemplary configuration 524 of eAxC allocation 500 includes three groups (e.g., the uplink channel group, the SRS group, and the PRACH group) in the uplink direction. 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 this first encoding technique, the RU port identifier can be allocated a total of four bits, including two dedicated bits indicating one of the three groups and two dedicated bits referencing the maximum number of endpoints associated with the group (e.g., the four endpoints associated with the uplink channel group, the SRS group, or the PRACH group).

[0127] Conversely, by applying this second encoding technique to the third exemplary configuration 524, five bits can be allocated to the RU port identifier. For example, to indicate an SRS endpoint, the MSB can be set to a first value (e.g., "1") to indicate the SRS group, and then two additional bits can be used to reference four SRS endpoints, resulting in three bits being used to indicate the SRS group and the corresponding endpoint. To indicate an uplink channel endpoint, the MSB can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 1) can be set to a first value (e.g., "1") to indicate the uplink channel group, and then two bits can be used to reference four uplink channel endpoints, resulting in four bits being used to indicate the uplink channel group and the corresponding endpoint. To indicate a PRACH endpoint, the first two MSBs can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 2) can be set to a first value (e.g., "1"), and then two additional bits can be used to reference four PRACH endpoints, resulting in five bits being used to indicate the PRACH group and the corresponding endpoint. Since the maximum number of bits in this example is five bits associated with the PRACH group, it can be understood that four bits (e.g., two extra bits) can be used to represent four SRS endpoints, and three bits (e.g., one extra bit) can be used to represent four uplink channel endpoints, so that the size of the RU port identifier remains constant at five bits.

[0128] Therefore, referring to the third exemplary configuration 524 of eAxC allocation 500, applying the first encoding technique results in a smaller RU port identifier (e.g., four bits) compared to applying the second encoding technique (e.g., five bits).

[0129] In another example, the fourth exemplary configuration 526 includes three groups in the uplink direction, including eight endpoints of the uplink channel group, eight SRS endpoints, and four PRACH endpoints. By applying the first encoding technique, the RU port identifier can be allocated a total of five bits, including two dedicated bits indicating one of the three groups and three dedicated bits referencing the maximum number of endpoints associated with the group (e.g., eight endpoints associated with the uplink channel group or the SRS group).

[0130] By applying this second encoding technique to the fourth exemplary configuration 526, five bits can be allocated to the RU port identifier. For example, to indicate an endpoint of an uplink channel, the MSB can be set to a first value (e.g., "1") to indicate the uplink channel group, and then three additional bits can be used to reference the eight endpoints of the downlink channel, resulting in four bits being used to indicate the uplink channel group and the corresponding endpoints. To indicate an SRS endpoint, the MSB can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 1) can be set to a first value (e.g., "1") to indicate the SRS group, and then three bits can be used to reference the eight SRS endpoints, resulting in five bits being used to indicate the SRS group and the corresponding endpoints. To indicate a PRACH endpoint, the first two MSBs can be set to a second value (e.g., "0"), and the next MSB (e.g., MSB bit 2) can be set to a first value (e.g., "1") to indicate the PRACH group, and then two bits can be used to reference the four PRACH endpoints, resulting in five bits being used to indicate the PRACH group and the corresponding endpoints. Since the maximum number of bits in this example is five bits associated with the SRS group and the PRACH group, it is understandable that four bits (e.g., one extra bit) can be used to represent eight uplink channel endpoints, keeping the size of the RU port identifier constant at five bits.

[0131] Therefore, referring to the uplink direction of the fourth exemplary configuration 526 of eAxC allocation 500, applying the first encoding technique and the second encoding technique results in an RU port identifier of the same size (e.g., five bits).

[0132] Figure 8 This is an exemplary communication flow 800 between RU 802 and DU 804, as presented herein. In the example shown, communication flow 800 facilitates a simplified handover at the RU based on an eAxC allocation strategy. RU 802 and DU 804 can facilitate communication via the O-RAN. Aspects of RU 802 can be... Figure 1 This is achieved using the RU 180B. Various aspects of the DU 804 can be implemented using... Figure 1 This is achieved using the DU 180A. Although in Figure 8 As not shown in the example, but it can be understood that in the additional or alternative examples, RU 802 may communicate with one or more UEs or other DUs, and / or DU 804 may communicate with one or more CUs or other RUs.

[0133] exist Figure 8 In the example, RU 802 can send capability information 810, which is received by DU 804. RU 802 can send capability information 810 via M-plane messages, C-plane messages, and / or U-plane messages. Capability information 810 can indicate the number of groups and the number of endpoints associated with each group. (See reference...) Figure 6 and / or Figure 7 For example, capability information 810 may indicate the existence of three groups and the number of endpoints associated with each group (e.g., 50 endpoints associated with group A, 25 endpoints associated with group B, and 10 endpoints associated with group C).

[0134] In some examples, capability information 810 may indicate the endpoints associated with each group. For example, capability information 810 may indicate each RU transmit endpoint (“tx endpoint”) and the uplink direction group to which the corresponding tx endpoint belongs (e.g., the uplink channel group, the SRS group, or the PRACH group). Capability information 810 may indicate each tx endpoint via static low-level tx endpoint parameters. Capability information 810 may additionally or alternatively indicate each rx endpoint and the downlink direction group to which the corresponding rx endpoint belongs (e.g., the downlink channel group or the SSB group). Capability information 810 may indicate each rx endpoint via static low-level rx endpoint parameters.

[0135] At 820, DU 804 can assign eAxCIDs to RU endpoints based on capability information 810. For example, DU 804 can assign group indexes based on the number of groups indicated by capability information 810. DU 804 can also assign group layers / flows within a group based on the number of endpoints indicated by capability information 810.

[0136] At 822, DU 804 can apply encoding techniques to the RU port identifier of eAxC messages. In some examples, DU 804 can apply this encoding technique using eAxCIDs allocation. In some examples, DU 804 can apply a first encoding technique, where dedicated bits are allocated to the group index and the tier / stream index for each group. In some examples, DU 804 can apply a second encoding technique, where a bit mask can be used to indicate the group, and a varying number of bits can be used to reference the endpoint associated with the corresponding group.

[0137] At 824, DU 804 can encode the group index based on this encoding technique. For example, DU 804 can use the first part of the RU port identifier to encode the group index. At 826, DU 804 can encode the RU endpoints based on this encoding technique. For example, DU 804 can use the second part of the RU port identifier to encode the layer / flow index for each group.

[0138] Reference Figure 6 For example, the first part of the RU port identifier may correspond to group index 612. In such examples, the first part of the RU port identifier may correspond to a static bit width (e.g., two bits). DU 804 may determine which of blocks 620, 622, or 624 the eAxCIDs allocation corresponds to. DU 804 may then encode information for that block via the group index and the first part of the RU port identifier (e.g., at 824). The second part of the RU port identifier may correspond to the layer / stream index 614 for each group. Similar to the first part of the RU port identifier, the second part of the RU port identifier may correspond to a static bit width (e.g., six bits) to accommodate the maximum number of endpoints within an endpoint group. DU 804 may encode information for that RU endpoint via the layer / stream index for each group and the second part of the RU port identifier (e.g., at 826).

[0139] Reference Figure 7 For example, the first part of the RU port identifier may correspond to a bit mask having a bit width that can be based on the number of endpoint groups. DU 804 can determine the endpoint groups and blocks 720, 722, and 724 based on this bit mask. DU 804 can then encode information for the block via the group index and the first part of the RU port identifier (e.g., at 824). The second part of the RU port identifier may correspond to the remaining bits of the RU port identifier following the bit mask. For example... Figure 7 As shown, the bit width of the second part of the RU port identifier may depend on the bit width of the RU port identifier and the bit width of the bit mask. DU 804 may encode information for the RU endpoint via the layer / stream index of each group and the second part of the RU port identifier (e.g., at 826).

[0140] In some examples, DU 804 may send an eAxC allocation configuration 830, which is received by RU 802. The eAxC allocation configuration 830 may indicate whether DU 804 is applying the first or second encoding technique to the RU port identifier of the eAxC message. The eAxC allocation configuration 830 may additionally or alternatively indicate the mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration 830 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. In an example where DU 804 applies the second encoding technique, the eAxC allocation configuration 830 may indicate that the MSB set to the first value (“1”) corresponds to the first group, the first two MSBs set to the second value (“01”) correspond to the second group, and the first three MSBs set to the third value (“001”) correspond to the third group.

[0141] At 840, RU 802 can configure endpoint groups based on eAxC allocation configuration 830. For example, based on this encoding technique, RU 802 can determine how to decode the RU port identifier of an eAxC message to determine which group the eAxC message belongs to. RU 802 can use this group index to determine where to route the eAxC message (e.g., to which hardware component) for processing.

[0142] like Figure 8 As shown, DU 804 can send an eAxC message 850, which is received by RU 802. The eAxC message 850 may include an RU port identifier, which is encoded using the first encoding technique or the second encoding technique.

[0143] At 860, RU 802 can decode the RU port identifier of eAxC message 850. RU 802 can apply a configured endpoint group (e.g., at 840) to decode the RU port identifier. At 862, RU 802 can identify the endpoint group based on the decoded RU port identifier. For example, the first part of the RU port identifier can be encoded using a group index corresponding to the endpoint group. At 864, RU 802 can index the eAxC message. For example, RU 802 can use the second part of the RU port identifier to determine the RU endpoint of the endpoint group.

[0144] Reference Figure 6For example, the first part of the RU port identifier may correspond to group index 612. In such examples, the first part of the RU port identifier may correspond to a static bit width (e.g., two bits). RU 802 can determine which of blocks 620, 622, or 624 the eAxC message corresponds to based on group index 612. The second part of the RU port identifier may correspond to layer / stream index 614 for each group. Similar to the first part of the RU port identifier, the second part of the RU port identifier may correspond to a static bit width (e.g., six bits) to accommodate the maximum number of endpoints within an endpoint group.

[0145] Reference Figure 7 For example, the first part of the RU port identifier may correspond to a bit mask having a bit width that can be based on the number of endpoint groups. RU 802 can determine the endpoint groups and blocks 720, 722, and 724 based on this bit mask. The second part of the RU port identifier may correspond to the remaining bits of the RU port identifier following the bit mask. For example... Figure 7 As shown, the bit width of the second part of the RU port identifier can depend on the bit width of the RU port identifier and the bit width of the bit mask.

[0146] At 870, RU 802 can route eAxC message 850 to a hardware component configured to process the eAxC message. For example, RU 802 can route PUSCH control plane messages to a first hardware component for processing, SRS control plane messages to a second hardware component for processing, PRACH control plane messages to a third hardware component for processing, PDSCH control plane messages to a fourth hardware component for processing, and SSB control plane messages to a fifth hardware component for processing. However, other examples may include additional or alternative combinations for routing messages to appropriate hardware components.

[0147] exist Figure 8In the above description, DU 804 sends eAxC allocation configuration 830, which RU 802 can use to configure the endpoint group (e.g., at 840). In some examples, DU 804 may choose not to send eAxC allocation configuration 830 to RU 802. In such examples, RU 802 may sample one or more eAxC messages at 832 to configure the endpoint group (e.g., at 840). For example, RU 802 may receive eAxC message 834 from DU 804. RU 802 can use the attributes of eAxC message 834 to determine the message type associated with eAxC message 834. For example, RU 802 may determine that the first eAxC message in eAxC message 834 corresponds to a PRACH control plane message based on the attributes of the first eAxC message in eAxC message 834. Based on the attributes of the second and third eAxC messages in eAxC message 834, RU 802 can determine that the second eAxC message corresponds to an uplink channel control plane message, and the third eAxC message corresponds to an SRS control plane message. RU 802 can use the MSB of the RU port identifier associated with the corresponding eAxC message to map the MSB to the corresponding group. For example, RU 802 can determine that two MSBs are used to indicate the group, and the remaining bits of the RU port identifier are used to indicate the RU endpoints within the group. In such an example, RU 802 can determine that DU 804 has applied the first encoding technique and associates the group indices (e.g., "00", "01", and "11") with each of the three uplink direction groups.

[0148] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0149] In another example, RU 802 can determine that the MSB bit is being set to a first value (e.g., "1") to indicate a group, and is using a varying number of bits to indicate RU endpoints within that group. In such an example, RU 802 can determine that DU 804 has applied the second encoding technique and associates a bit mask (e.g., "1", "01", and "001") with each of the three uplink direction groups.

[0150] Then, at 840, RU 802 can configure the endpoint group based on sampling of eAxC message 834. For example, based on sampling of eAxC message 834 (e.g., at 832), RU 802 can determine whether DU 804 applies the first encoding technique or the second encoding technique. When applying the first encoding technique, RU 802 can determine that the first group index (“00”) corresponds to the first group, the second group index (“01”) corresponds to the second group, and the third group index (“10”) corresponds to the third group. When applying the second encoding technique, RU 802 can determine that the MSB set to the first value (“1”) corresponds to the first group, the first two MSBs set to the second value (“01”) correspond to the second group, and the first three MSBs set to the third value (“001”) correspond to the third group.

[0151] Figure 9 This is a flowchart 900 of a wireless communication method. The method can be implemented by a base station RU (e.g., RU 180B, RU 802, and / or...). Figure 13 The method is executed by device 1302. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the RU can facilitate communication within the O-RAN.

[0152] At position 902, the RU sends capability information to the DU indicating support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints, such as in combination. Figure 8 The capability information described in 810. For example, 902 can be... Figure 13 The capability component 1340 of the device 1302 performs this function. The endpoint group may include a first set of groups for uplink endpoints and / or a second set of groups for downlink endpoints.

[0153] In some examples, this capability information may indicate the number of endpoint groups and the number of RU endpoints associated with the corresponding endpoint group.

[0154] At position 904, the RU receives an eAxC message from the DU based on this capability information. This eAxC message includes the DU port identifier, frequency band sector identifier, component carrier identifier, and RU port identifier, as combined with... Figure 8 As described in eAxC message 850. For example, 904 can be... Figure 13 The message component 1342 of the device 1302 is used to execute.

[0155] At 906, the RU uses the first part of its RU port identifier to identify an endpoint group, the corresponding set of RU endpoints in which the endpoint group is associated with a set of characteristics, such as in combination. Figure 8 As described in 862. For example, 906 can be derived from... Figure 13 The first part of the device 1302, component 1344, performs the operation.

[0156] In some examples, this set of features may be based on one or more of the following: data layer, spatial stream, digital scheme, and channel.

[0157] At 908, the RU uses the second part of its RU port identifier to index the eAxC message to the RU endpoint of that endpoint group, as combined with... Figure 8 As described in 864. For example, 908 can be derived from... Figure 13 The second part of the device 1302, component 1346, performs the operation.

[0158] In some examples, the first part of the RU port identifier may correspond to a group index, and the second part of the RU port identifier may correspond to a layer / flow index for each group.

[0159] In some examples, the first part and the second part can facilitate hierarchical addressing of the RU endpoints of the RU.

[0160] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be implemented using a base station RU (e.g., RU 180B, RU 802, and / or...). Figure 11 The method is executed by device 1102. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the RU can facilitate communication within the O-RAN.

[0161] At position 1002, the RU sends capability information to the DU indicating support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints, such as in combination. Figure 8 The capability information described in 810. For example, 1002 can be... Figure 13 The capability component 1340 of the device 1302 performs this function. The endpoint group may include a first set of groups for uplink endpoints and / or a second set of groups for downlink endpoints.

[0162] In some examples, this capability information may indicate the number of endpoint groups and the number of RU endpoints associated with the corresponding endpoint group.

[0163] At position 1006, the RU receives an eAxC message from the DU based on this capability information. This eAxC message includes the DU port identifier, frequency band sector identifier, component carrier identifier, and RU port identifier, as combined with... Figure 8 As described in eAxC message 850. For example, 1006 can be... Figure 13 The message component 1342 of the device 1302 is used to execute.

[0164] At 1010, the RU uses the first part of its RU port identifier to identify an endpoint group, the corresponding set of RU endpoints in which the endpoint group is associated with a set of characteristics, such as in combination. Figure 8 As described in 862. For example, 1010 can be derived from... Figure 13 The first part of the device 1302, component 1344, performs the operation.

[0165] In some examples, this set of features may be based on one or more of the following: data layer, spatial stream, digital scheme, and channel.

[0166] At 1014, the RU uses the second part of its RU port identifier to index the eAxC message to the RU endpoint of that endpoint group, as combined with... Figure 8 As described in 864. For example, 1014 can be derived from... Figure 13 The second part of the device 1302, component 1346, performs the operation.

[0167] In some examples, the first part of the RU port identifier may correspond to a group index, and the second part of the RU port identifier may correspond to a layer / flow index for each group.

[0168] In some examples, the first part and the second part can facilitate hierarchical addressing of the RU endpoints of the RU.

[0169] At 1016, the RU can route the eAxC message to a processing component based on the RU endpoints of the endpoint group. This processing component is configured to process eAxC messages associated with the feature set, such as in combination with... Figure 8 As described in 870. For example, 1016 can be derived from... Figure 13 The routing component 1348 of the device 1302 is used to perform this.

[0170] At position 1004, the RU can sample a certain amount of received eAxC messages to determine the encoding technique associated with the corresponding RU port identifier of the received eAxC message. This encoding technique is used to encode the first and second parts of the corresponding RU port identifier, such as combining... Figure 8 As described in 832. For example, 1004 can be derived from... Figure 13 The sampling component 1350 of the device 1302 is used to perform the sampling.

[0171] At position 1008, the RU can decode the first part of the RU port identifier based on this encoding technique, such as in combination with... Figure 8 As described in 862. For example, 1008 can be derived from... Figure 13 The decoding component 1352 of the device 1302 is used to perform this.

[0172] At position 1012, the RU can decode the second part of the RU port identifier based on this encoding technique, such as in combination with... Figure 8 As described in 864. For example, 1012 can be derived from... Figure 13 The decoding component 1352 of the device 1302 is used to perform this.

[0173] In some examples, the decoding of the first part of the RU port identifier may be based on a static bit width, and the decoding of the second part of the RU port identifier may be based on linear addressing of the RU endpoints across the endpoint group, as combined with... Figure 6 The example described.

[0174] In some examples, the decoding of the first part of the RU port identifier may be based on a bit mask having a bit width corresponding to the endpoint group, and the decoding of the second part of the RU port identifier may be based on the bit width of the RU port identifier and the bit width of the bit mask, such as in combination. Figure 7 The example described.

[0175] Figure 11 This is a flowchart 1100 of a wireless communication method. The method can be implemented using a base station RU (e.g., RU 180B, RU 802, and / or...). Figure 13 The method is executed by device 1302. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the RU can facilitate communication within the O-RAN.

[0176] At 1102, the RU sends capability information indicating support for the endpoint group, such as in conjunction with... Figure 8 The capability information described in 810. For example, 1102 can be derived from... Figure 13 The capability component 1340 of the device 1302 performs this function. In some examples, the capability information may indicate the number of endpoint groups and the corresponding set of endpoints associated with each endpoint group. For example, the capability information may indicate the presence of 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 (e.g., via a static low-level [tr]x endpoint parameter) indicate which endpoints are associated with which endpoint group.

[0177] In some examples, the endpoint group includes a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint group may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint group 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 the direction.

[0178] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0179] At position 1104, the RU receives the eAxC message from the DU, as combined with... Figure 8 As described in eAxC message 850. For example, 1104 can be generated by... Figure 13 The message component 1342 of the device 1302 performs the execution. The eAxC message may include an M-plane message, C-plane message, or S-plane message containing the eAxC. For example, the eAxC may include a DU port identifier, a frequency band sector identifier, a CC identifier, and a RU port identifier, such as in combination. Figure 4 As described in eAxC 400. The RU port identifier can be encoded to include a group index and a stratum / flow index for each group, as combined with... Figure 6 RU port identifier 610 and / or Figure 7 The RU port identifier 710 describes this. This group index and the layer / flow index for each group can be based on this capability information.

[0180] At 1106, the RU routes the eAxC message to the processing component in part based on the group index included in the eAxC message, such as in combination with... Figure 8 As described in 870. For example, 1106 can be derived from... Figure 13 The routing component 1348 of the device 1302 is used to perform this.

[0181] Figure 12 This is a flowchart 1200 of a wireless communication method. The method can be implemented using a base station RU (e.g., RU 180B, RU 802, and / or...). Figure 13 The method is executed by device 1302. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the RU can facilitate communication within the O-RAN.

[0182] At 1202, the RU sends capability information indicating support for the endpoint group, such as in conjunction with... Figure 8 The capability information described in 810. For example, 1202 can be... Figure 13The capability component 1340 of the device 1302 performs this function. In some examples, the capability information may indicate the number of endpoint groups and the corresponding set of endpoints associated with each endpoint group. For example, the capability information may indicate the presence of 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 (e.g., via a static low-level [tr]x endpoint parameter) indicate which endpoints are associated with which endpoint group.

[0183] In some examples, the endpoint group includes a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint group may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint group 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 the direction.

[0184] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0185] At position 1210, the RU receives the eAxC message from the DU, as combined with... Figure 8 As described in eAxC message 850. For example, 1210 can be generated by... Figure 13 The message component 1342 of the device 1302 performs the execution. The eAxC message may include an M-plane message, C-plane message, or S-plane message containing the eAxC. For example, the eAxC may include a DU port identifier, a frequency band sector identifier, a CC identifier, and a RU port identifier, such as in combination. Figure 4 The eAxC identifier 400 describes this. The RU port identifier can be encoded to include a group index and a stratum / flow index for each group, as combined with... Figure 6 RU port identifier 610 and / or Figure 7 The RU port identifier 710 describes this. This group index and the layer / flow index for each group can be based on this capability information.

[0186] At 1214, the RU routes the eAxC message to the processing component in part based on the group index included in the eAxC message, such as in combination with... Figure 8 As described in 870. For example, 1214 can be derived from... Figure 13The routing component 1348 of the device 1302 is used to perform this.

[0187] In some examples, the RU can decode the RU port identifier of the eAxC message at 1212 to determine the group index included in the eAxC message, such as in combination with Figure 8 As described in 860. For example, 1212 can be derived from... Figure 13 The decoding component 1352 of the device 1302 performs this operation. In some examples, the RU can use the MSB of the RU port identifier to determine the group index. For example, the RU port identifier can be encoded to include the group index using a first encoding technique (e.g., dedicated bits for the group index and the layer / stream index for each group). When the first encoding technique is used to encode the RU port identifier, the RU can determine the group index based on a static size field used for the group index. For example, in Figure 6 In the example, group index 612 can be determined based on two MSBs of RU port identifier 610. This RU port identifier may also include a static size field dedicated to the tier / stream index for each group. For example, in... Figure 6 In the example, each group index is associated with a block of 64 group layers / flows based on six bits of the layer / flow index 614 dedicated to the RU port identifier 610. Addressing of the layer / flow index of each group across the endpoint group can be linear based on the static size field dedicated to the layer / flow index of each group.

[0188] In other examples, a second encoding technique (e.g., bitmasking and varying layer / stream index sizes per group) can be used to encode the RU port identifier to include the group index. When this second encoding technique is used to encode the RU port identifier, the RU can determine the group index based on the position of a first value (e.g., "1") in the MSB of the RU port identifier. For example, in Figure 7 In the example, a first group of indices can be indicated when the MSB is set to a first value (e.g., "1"), a second group of indices can be indicated when the next MSB is set to a first value (e.g., "01"), and a third group of indices can be indicated when the next MSB is set to a first value (e.g., "001"). When a bitmask is used to indicate a group of indices, the size of the bits used to indicate each group of layer / stream indices can vary. For example, the size of each group of layer / stream indices can be based on the number of bits in the RU port identifier and the number of bits used to indicate the group of indices. For example, in a RU port identifier of seven bits... Figure 7 In the example, the size of the layer / stream index for each group varies between four and six bits, depending on the number of bits used to indicate the group's index.

[0189] In some examples, the RU can decode its port identifier based on the configured endpoint group (e.g., at 1212). For example, at 1204, the RU can receive eAxC allocation configurations, such as in conjunction with... Figure 8 The eAxC allocation configuration 830 is described. For example, 1204 can be configured by... Figure 13 The configuration component 1354 of the device 1302 performs this operation. The eAxC allocation configuration can indicate whether the DU is applying the first encoding technique or the second encoding technique to the RU port identifier of the eAxC message. The eAxC allocation configuration can additionally or alternatively indicate the mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration can 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 the second encoding technique is applied, the eAxC allocation configuration can indicate that the MSB set to the first value (“1”) corresponds to the first group, the first two MSBs set to the second value (“01”) correspond to the second group, and the first three MSBs set to the third value (“001”) correspond to the third group.

[0190] At 1208, the RU can configure endpoint groups based on the eAxC allocation configuration, such as in conjunction with... Figure 8 As described in 840. For example, 1208 can be derived from... Figure 13 The configuration component 1354 of the device 1302 performs this function. For example, based on this encoding technique, the RU can determine how to decode the RU port identifier of the eAxC message to determine which group the eAxC message belongs to.

[0191] In some examples, the RU can determine the endpoint group without receiving eAxC allocation configuration from the DU. For example, at 1206, the RU can sample a certain number of eAxC messages to determine the encoding technique associated with the RU port identifier of the received eAxC messages, such as combining... Figure 8 As described in 832. For example, 1206 can be derived from... Figure 13The sampling component 1350 of the device 1302 performs this function. For example, the RU may receive an eAxC message 834 from DU 804. The RU may use the attributes of the eAxC message to determine the message type associated with the received eAxC message. For example, the RU may determine that the first eAxC message corresponds to a PRACH control plane message based on the attributes of the first eAxC message among a plurality of eAxC messages. Based on the attributes of the second and third eAxC messages among the plurality of eAxC messages, the RU may determine that the second eAxC message corresponds to an uplink channel control plane message and the third eAxC message corresponds to an SRS control plane message. The RU may use the MSB of the RU port identifier associated with the corresponding eAxC message to map the MSB to the corresponding group. For example, the RU may determine that two MSBs are used to indicate the group and use the remaining bits of the RU port identifier to indicate the RU endpoints within the group. In such an example, the RU can determine that the DU has applied the first encoding technique and associate the group index (e.g., “00”, “01”, and “11”) with each of the three uplink direction groups.

[0192] In another example, the RU can determine that the MSB bit is being set to a first value (e.g., "1") to indicate a group, and is using a varying number of bits to indicate the RU endpoints within that group. In such an example, the RU can determine that the DU has applied the second encoding technique and associate a bit mask (e.g., "1", "01", and "001") with each of the three uplink direction groups.

[0193] At 1208, the RU can then configure the endpoint group based on a sample of the eAxC message, such as in conjunction with... Figure 8 As described in 840. For example, 1208 can be derived from... Figure 13 The configuration component 1354 of the device 1302 performs this function. For example, based on sampling of the plurality of eAxC messages, the RU can determine whether the DU applies the first encoding technique or the second encoding technique. When the first encoding technique is applied, the RU can determine that the first set of indices ("00") corresponds to the first group, the second set of indices ("01") corresponds to the second group, and the third set of indices ("10") corresponds to the third group. When the second encoding technique is applied, the RU can determine that the MSB set to the first value ("1") corresponds to the first group, the first two MSBs set to the second value ("01") correspond to the second group, and the first three MSBs set to the third value ("001") correspond to the third group.

[0194] Figure 13Figure 1300 illustrates an example of a hardware implementation for device 1302. Device 1302 is a RU of a base station, a component of a base station, or a device that implements base station functions. Device 1302 includes a baseband unit 1304. Baseband unit 1304 can communicate with UE 104 and / or DU 180A via cellular RF transceiver 1322. Baseband unit 1304 may include computer-readable medium / memory. Baseband unit 1304 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by baseband unit 1304, causes baseband unit 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1304 when executing the software. Baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. Communication manager 1332 includes one or more of the components shown. Components within the communication manager 1332 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1304. The baseband unit 1304 may be a component of the base station 310 and may include a memory 376 and / or at least one of a TX processor 316, an RX processor 370, and a controller / processor 375.

[0195] Communication manager 1332 includes capability component 1340, which is configured to send capability information to the DU indicating support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints, for example, as combined with Figure 9 902 and / or Figure 10 As described in 1002. Exemplary capability component 1340 can also be configured to send capability information indicating support for endpoint groups, for example, as in conjunction with... Figure 11 1102 and / or Figure 12 As described in 1202.

[0196] Communication manager 1332 also includes message component 1342, configured to receive eAxC messages from the DU based on the capability information. These eAxC messages include a DU port identifier, a frequency band sector identifier, a component carrier identifier, and a RU port identifier, for example, in combination with... Figure 9 904 and / or Figure 10 As described in 1006. Exemplary message component 1342 can be configured to receive eAxC messages from a DU, for example, as in conjunction with... Figure 11 1104 or Figure 12 As described in 1210.

[0197] Communication manager 1332 also includes a first part component 1344 configured to use the first part of the RU port identifier to identify an endpoint group, the corresponding set of RU endpoints of which is associated with a set of characteristics, such as, in combination with Figure 9 906 and / or Figure 10 As described in 1010.

[0198] Communication manager 1332 also includes a second part component 1346, which is configured to use the second part of the RU port identifier to index the eAxC message to the RU endpoint of the endpoint group, for example, as in combination Figure 9 908 and / or Figure 10 As described in 1014.

[0199] Communication manager 1332 also includes routing component 1348, configured to route the eAxC message to a processing component based on the RU endpoints of the endpoint group. This processing component is configured to process the eAxC message associated with the feature set, for example, by combining... Figure 10 As described in 1016. For example, exemplary routing component 1348 may also be configured to route the eAxC message to a processing component in part based on the group index included in the eAxC message, such as in conjunction with Figure 11 1106 and / or Figure 12 As described in 1214.

[0200] The communication manager 1332 also includes a sampling component 1350 configured to sample a certain amount of received eAxC messages to determine an encoding technique associated with a corresponding RU port identifier of the received eAxC message. This encoding technique is used to encode a first portion and a second portion of the corresponding RU port identifier, for example, by combining... Figure 10 As described in section 1004. The exemplary sampling component 1350 can also be configured to sample a certain amount of received eAxC messages to determine the encoding technique associated with the RU port identifier of the received eAxC message, for example, such as in conjunction with... Figure 12 As described in 1206.

[0201] Communication manager 1332 also includes decoding component 1352, which is configured to decode the first part of the RU port identifier based on the encoding technique, for example, as in combination with Figure 10 As described in 1008. The exemplary decoding component 1352 can also be configured to decode the second part of the RU port identifier based on this encoding technique, for example, as in combination with... Figure 10 As described in 1012. Exemplary decoding component 1352 can also be configured to decode the RU port identifier of the eAxC message to determine the group index, for example, as in conjunction with... Figure 12 As described in 1212.

[0202] Communication manager 1332 includes configuration component 1354, which is configured to receive eAxC allocation configuration, for example, as combined with Figure 12As described in section 1204. Exemplary configuration component 1354 can also be configured to configure a group of endpoints, for example, as in conjunction with... Figure 12 As described in 1208.

[0203] The device may include execution Figure 9 , Figure 10 , Figure 11 and / or Figure 12 The flowchart shows the algorithm as an additional component for each box. Therefore, Figure 9 , Figure 10 , Figure 11 and / or Figure 12 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0204] As shown in the figure, device 1302 may include various components configured for various functions. In one configuration, device 1302 (particularly baseband unit 1304) includes sending capability information to the DU indicating support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints.

[0205] The exemplary device 1302 further includes a unit for receiving an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a frequency band sector identifier, a component carrier identifier, and an RU port identifier. The exemplary device 1302 also includes a unit for using a first portion of the RU port identifier to identify an endpoint group, the corresponding set of RU endpoints of the endpoint group being associated with a feature set. The exemplary device 1302 further includes a unit for using a second portion of the RU port identifier to index the eAxC message to the RU endpoints of the endpoint group.

[0206] In another configuration, exemplary device 1302 further includes a unit for routing the eAxC message to a processing component based on the RU endpoints of the endpoint group, the processing component being configured to process the eAxC message associated with the feature set.

[0207] In another configuration, exemplary device 1302 further includes units for sampling a quantity of received eAxC messages to determine an encoding technique associated with a corresponding RU port identifier of the received eAxC messages, the encoding technique being used to encode a first portion and a second portion of the corresponding RU port identifier. Exemplary device 1302 also includes units for decoding the first portion of the RU port identifier based on the encoding technique. Exemplary device 1302 further includes units for decoding the second portion of the RU port identifier based on the encoding technique.

[0208] In another configuration, exemplary device 1302 further includes units for decoding a first portion of the RU port identifier based on a static bit width. Exemplary device 1302 also includes units for decoding a second portion of the RU port identifier based on linear addressing of RU endpoints across the endpoint group.

[0209] In another configuration, exemplary device 1302 further includes units for decoding a first portion of the RU port identifier based on a bit mask having a bit width corresponding to the endpoint group. Exemplary device 1302 also includes units for decoding a second portion of the RU port identifier based on the bit width of the RU port identifier and the bit width of the bit mask.

[0210] In another configuration, exemplary device 1302 also includes a unit for facilitating hierarchical addressing of the RU endpoints.

[0211] In another configuration, exemplary device 1302 includes units for sending capability information indicating support for endpoint groups to a DU, each endpoint group being associated with a corresponding set of RU endpoints. Exemplary device 1302 also includes units for receiving an eAxC message from the DU, the eAxC message including a group index based on the capability information. Exemplary device 1302 further includes units for routing the eAxC message to a processing component, in part, based on the group index included in the eAxC message.

[0212] In another configuration, exemplary device 1302 further includes a unit for sampling a quantity of received eAxC messages to determine an encoding technique associated with an RU port identifier of the received eAxC message, the encoding technique being used to encode a group index and a layer / stream index for each group of the RU port identifier.

[0213] In another configuration, exemplary device 1302 also includes a unit for receiving eAxC allocation configuration from the DU.

[0214] In another configuration, exemplary device 1302 also includes a unit for configuring an endpoint group.

[0215] In another configuration, exemplary device 1302 also includes a unit for decoding the RU port identifier of the eAxC message to determine the set of indices.

[0216] The unit may be one or more components of the device 1302 configured to perform the functions described therein. As described above, the device 1302 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Accordingly, in one configuration, the unit may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions described therein.

[0217] Figure 14 This is a flowchart 1400 of a wireless communication method. The method can be implemented using a base station's DU (e.g., DU 180A, DU 804, and / or...). Figure 18 The method is executed by device 1802. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the DU can facilitate communication in the O-RAN.

[0218] At 1402, the DU receives capability information from the RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints, such as in combination. Figure 8 The capability information described in 810. For example, 1402 can be derived from... Figure 18 The capability component 1840 of the device 1802 is used to perform this.

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

[0220] In some examples, the endpoint group includes a first set of groups for uplink endpoints and / or a second set of groups for downlink endpoints. For example, the endpoint group may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint group 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 the direction.

[0221] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0222] At 1404, the DU, based on this capability information, encodes the endpoint group associated with the eAxC message using the first part of the RU port identifier. This eAxC message includes the DU port identifier, band sector identifier, component carrier identifier, and the RU port identifier, as combined with... Figure 8 As described in 824. For example, 1404 can be derived from... Figure 18 The first part of the device 1802, component 1846, performs the operation.

[0223] At 1406, the DU encodes the RU endpoints of the endpoint group using the second part of the RU port identifier, as combined with... Figure 8 As described in 826. For example, 1406 can be derived from... Figure 18 The second part of the device 1802, component 1848, performs the operation.

[0224] In some examples, the first part and the second part can facilitate hierarchical addressing of the RU endpoints of the RU.

[0225] In some examples, the encoding of the endpoint group using the first part of the RU port identifier can be based on a static bit width, and the encoding of the RU endpoint using the second part of the RU port identifier can be based on linear addressing of the RU endpoints across the endpoint group, such as in combination. Figure 6 The example described.

[0226] In some examples, the encoding of the endpoint group using the first part of the RU port identifier can be based on a bit mask having a bit width corresponding to the endpoint group, and the encoding of the RU endpoint using the second part of the RU port identifier can be based on the bit width of the RU port identifier and the bit width of the bit mask, such as in combination. Figure 7 The example described.

[0227] At position 1408, the DU sends the eAxC message to the RU, as combined with... Figure 8 As described in eAxC message 850. For example, 1408 can be generated by... Figure 18The message component 1850 of the device 1802 performs the operation. The eAxC message may include an M-plane message, a C-plane message, or an S-plane message containing an eAxC identifier.

[0228] Figure 15 This is a flowchart 1500 of a wireless communication method. The method can be implemented using a base station's DU (e.g., DU 180A, DU 804, and / or...). Figure 18 The method is executed by device 1802. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the DU can facilitate communication in the O-RAN.

[0229] At 1502, the DU receives capability information from the RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints, such as in combination. Figure 8 The capability information described in 810. For example, 1502 can be derived from... Figure 18 The capability component 1840 of the device 1802 is used to perform this.

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

[0231] In some examples, the endpoint group includes a first set of groups for uplink endpoints and / or a second set of groups for downlink endpoints. For example, the endpoint group may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint group 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 the direction.

[0232] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0233] At 1504, the DU can assign the eAxC message to the RU endpoint of the endpoint group based on the set of characteristics associated with the eAxC message, such as combining... Figure 8As described in 820. For example, 1504 can be derived from... Figure 18 The allocation component 1842 of the device 1802 performs this operation. The DU can allocate group indices based on the number of groups indicated by the capability information. The DU can also allocate group layers / streams within a group based on the number of endpoints indicated by the capability information. The set of characteristics can be based on one or more of the following: data layer, spatial stream, digital scheme, and channel.

[0234] At position 1506, this DU can apply encoding techniques to the RU port identifier, such as in combination with... Figure 8 As described in 822. For example, 1506 can be derived from... Figure 18 The encoding component 1844 of the device 1802 performs this operation. In some examples, the DU may utilize this encoding technique to encode the group index using the first part of the RU port identifier and to encode the layer / stream index of each group using the second part of the RU port identifier.

[0235] At 1508, the DU, based on this capability information, encodes the endpoint group associated with the eAxC message using the first part of the RU port identifier. This eAxC message includes the DU port identifier, band sector identifier, component carrier identifier, and the RU port identifier, as combined with... Figure 8 As described in 824. For example, 1508 can be derived from... Figure 18 The first part of the device 1802, component 1846, performs the operation.

[0236] At 1510, the DU uses the second part of the RU port identifier to encode the RU endpoints of the endpoint group, as combined with... Figure 8 As described in 826. For example, 1510 can be derived from... Figure 18 The second part of the device 1802, component 1848, performs the operation.

[0237] In some examples, the first part and the second part can facilitate hierarchical addressing of the RU endpoints of the RU.

[0238] At position 1512, the DU sends the eAxC message to the RU, as combined with... Figure 8 As described in eAxC message 850. For example, 1512 can be generated by... Figure 18 The message component 1850 of the device 1802 performs the operation. The eAxC message may include an M-plane message, a C-plane message, or an S-plane message containing an eAxC identifier.

[0239] In some examples, the encoding of the endpoint group using the first part of the RU port identifier can be based on a static bit width, and the encoding of the RU endpoint using the second part of the RU port identifier can be based on linear addressing of the RU endpoints across the endpoint group, such as in combination. Figure 6The example described.

[0240] In some examples, the encoding of the endpoint group using the first part of the RU port identifier can be based on a bit mask having a bit width corresponding to the endpoint group, and the encoding of the RU endpoint using the second part of the RU port identifier can be based on the bit width of the RU port identifier and the bit width of the bit mask, such as in combination. Figure 7 The example described.

[0241] Figure 16 This is a flowchart 1600 of a wireless communication method. The method can be implemented using a base station's DU (e.g., DU 180A, DU 804, and / or...). Figure 18 The method is executed by device 1802. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the DU can facilitate communication in the O-RAN.

[0242] At 1602, the DU receives capability information from the RU indicating support for endpoint groups, such as in conjunction with... Figure 8 The capability information described in 810. For example, 1602 can be derived from... Figure 18 The capability component 1840 of the device 1802 performs this function. In some examples, the capability information may indicate the number of endpoint groups and the corresponding set of endpoints associated with each endpoint group. For example, the capability information may indicate the presence of 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 (e.g., via a static low-level [tr]x endpoint parameter) indicate which endpoints are associated with which endpoint group.

[0243] In some examples, the endpoint group includes a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint group may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint group 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 the direction.

[0244] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0245] At 1604, the DU partially allocates eAxC messages to RU endpoints within the corresponding endpoint group based on this capability information, such as in combination with... Figure 8 As described in 820. For example, 1604 can be derived from... Figure 18 The allocation component 1842 of the device 1802 performs this function. For example, the DU can allocate group indices based on the number of groups indicated by the capability information. The DU can also allocate group layers / flows within a group based on the number of endpoints indicated by the capability information.

[0246] At position 1606, the DU sends an eAxC message to the RU, which includes a group index associated with the endpoint group, such as in conjunction with... Figure 8 As described in eAxC message 850. For example, 1606 can be generated by... Figure 18 The message component 1850 of the device 1802 is used to execute.

[0247] The eAxC message may include an M-plane message, C-plane message, or S-plane message containing the eAxC. For example, the eAxC may include a DU port identifier, a frequency band sector identifier, a CC identifier, and a RU port identifier, such as in combination. Figure 4 The eAxC identifier 400 describes this. The RU port identifier can be encoded to include a group index and a stratum / flow index for each group, as combined with... Figure 6 RU port identifier 610 and / or Figure 7 The RU port identifier 710 describes this. This group index and the layer / flow index for each group can be based on this capability information.

[0248] Figure 17 This is a flowchart 1700 of a wireless communication method. The method can be implemented using a base station's DU (e.g., DU 180A, DU 804, and / or...). Figure 18 The method is executed by device 1802. This method facilitates simplified handover at the RU based on the eAxC allocation strategy. In some examples, the DU can facilitate communication in the O-RAN.

[0249] At 1702, the DU receives capability information from the RU indicating support for endpoint groups, such as in conjunction with... Figure 8 The capability information described in 810. For example, 1702 can be derived from... Figure 18 The capability component 1840 of the device 1802 performs this function. In some examples, the capability information may indicate the number of endpoint groups and the corresponding set of endpoints associated with each endpoint group. For example, the capability information may indicate the presence of 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 (e.g., via a static low-level [tr]x endpoint parameter) indicate which endpoints are associated with which endpoint group.

[0250] In some examples, the endpoint group includes a first set of groups for uplink endpoints and a second set of groups for downlink endpoints. For example, the endpoint group may include an uplink channel group, an SRS group, and a PRACH group associated with the uplink direction. The endpoint group 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 the direction.

[0251] In some examples, RU endpoints associated with a group may be associated with the same set of attributes. For example, an uplink endpoint may be associated with a first set of attributes, and a downlink endpoint may be associated with a second set of attributes. In some examples, an uplink channel endpoint may be associated with a first set of attributes, an SRS endpoint may be associated with a second set of attributes, a PRACH endpoint may be associated with a third set of attributes, a downlink channel endpoint may be associated with a fourth set of attributes, and an SSB endpoint may be associated with a fifth set of attributes.

[0252] At 1704, the DU partially allocates eAxC messages to RU endpoints within the corresponding endpoint group based on this capability information, such as in combination with... Figure 8 As described in 820. For example, 1704 can be derived from... Figure 18 The allocation component 1842 of the device 1802 performs this function. For example, the DU can allocate group indices based on the number of groups indicated by the capability information. The DU can also allocate group layers / flows within a group based on the number of endpoints indicated by the capability information.

[0253] At position 1706, the DU can send the eAxC allocation configuration to the RU, such as in conjunction with... Figure 8 The eAxC allocation configuration 830 is described. For example, 1706 can be configured by... Figure 18 The configuration component 1852 of the device 1802 performs this operation. The eAxC allocation configuration can indicate whether the DU is applying the first encoding technique or the second encoding technique to the RU port identifier of the eAxC message. The eAxC allocation configuration can additionally or alternatively indicate the mapping between endpoint groups and endpoints. For example, the eAxC allocation configuration can 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 the second encoding technique is applied, the eAxC allocation configuration can indicate that the MSB set to the first value (“1”) corresponds to the first group, the first two MSBs set to the second value (“01”) correspond to the second group, and the first three MSBs set to the third value (“001”) correspond to the third group.

[0254] At 1708, the DU may relinquish the ability to send the eAxC allocation configuration to the RU. For example, 1708 may be... Figure 18The configuration component 1852 of the device 1802 is used to perform this.

[0255] At 1710, this DU can apply encoding techniques to the RU port identifier of the eAxC message to encode the group index and the layer / stream index of each group, such as in combination with Figure 8 As described in 822. For example, 1710 can be derived from... Figure 18 The encoding component 1844 of the device 1802 is used to perform this.

[0256] In some examples, the DU may apply a first encoding technique, in which dedicated bits are allocated to the group index and the tier / stream index for each group. For example, the RU port identifier may be encoded to include the group index using the first encoding technique (e.g., dedicated bits for the group index and the tier / stream index for each group). 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 used for the group index. For example, in Figure 6 In the example, group index 612 can be encoded based on two MSBs of the RU port identifier 610. This RU port identifier may also include a static size field dedicated to the tier / stream index for each group. For example, in... Figure 6 In the example, each group index is associated with a block of 64 group layers / flows based on six bits of the layer / flow index 614 dedicated to the RU port identifier 610. Addressing of the layer / flow index of each group across the endpoint group can be linear based on the static size field dedicated to the layer / flow index of each group.

[0257] In other examples, a second encoding technique (e.g., bitmasking and varying layer / stream index sizes per group) can be used to encode the RU port identifier to include the group index. When this second encoding technique is used to encode the RU port identifier, the DU can encode the group index based on the position of a first value (e.g., "1") within the MSB of the RU port identifier. For example, in Figure 7 In the example, a first group of indices can be indicated when the MSB is set to a first value (e.g., "1"), a second group of indices can be indicated when the next MSB is set to a first value (e.g., "01"), and a third group of indices can be indicated when the next MSB is set to a first value (e.g., "001"). When a bitmask is used to indicate a group of indices, the size of the bits used to indicate each group of layer / stream indices can vary. For example, the size of each group of layer / stream indices can be based on the number of bits in the RU port identifier and the number of bits used to indicate the group of indices. For example, in a RU port identifier of seven bits... Figure 7 In the example, the size of the layer / stream index for each group varies between four and six bits, depending on the number of bits used to indicate the group's index.

[0258] At position 1712, the DU sends an eAxC message to the RU, which includes a group index associated with the endpoint group, such as in conjunction with... Figure 8 As described in eAxC message 850. For example, 1712 can be generated by... Figure 18 The message component 1850 of the device 1802 is used to execute.

[0259] The eAxC message may include an M-plane message, C-plane message, or S-plane message containing the eAxC. For example, the eAxC may include a DU port identifier, a frequency band sector identifier, a CC identifier, and a RU port identifier, such as in combination. Figure 4 The eAxC identifier 400 describes this. The RU port identifier can be encoded to include a group index and a stratum / flow index for each group, as combined with... Figure 6 RU port identifier 610 and / or Figure 7 The RU port identifier 710 describes this. This group index and the layer / flow index for each group can be based on this capability information.

[0260] Figure 18 Figure 1800 illustrates an example of a hardware implementation for device 1802. Device 1802 is a DU of a base station, a component of a base station, or a device that implements base station functions. Device 1802 includes a baseband unit 1804. Baseband unit 1804 can communicate with UE 104 and / or RU 180B via cellular RF transceiver 1822. Baseband unit 1804 may include computer-readable medium / memory. Baseband unit 1804 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by baseband unit 1804, causes baseband unit 1804 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1804 when executing the software. Baseband unit 1804 also includes a receiving component 1830, a communication manager 1832, and a transmitting component 1834. Communication manager 1832 includes one or more of the components shown. Components within the communication manager 1832 may be stored in the computer-readable medium / memory and / or configured as hardware within the baseband unit 1804. The baseband unit 1804 may be a component of the base station 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0261] Communication manager 1832 includes capability component 1840, which is configured to receive capability information from an RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints, for example, as combined Figure 14 1402 and / or Figure 15As described in 1502. Exemplary capability component 1840 can also be configured to receive capability information from the RU indicating support for endpoint groups, for example, as in conjunction with... Figure 16 1602 and / or Figure 17 As described in 1702.

[0262] Communication manager 1832 also includes allocation component 1842, which is configured to allocate the eAxC message to RU endpoints of the endpoint group based on a set of characteristics associated with the eAxC message, for example, as combined with Figure 15 As described in 1504. The exemplary allocation component 1842 can also be configured to allocate eAxC messages to RU endpoints within the corresponding endpoint group, in part based on this capability information, for example, as in conjunction with... Figure 16 1604 and / or Figure 17 As described in 1704.

[0263] Communication manager 1832 also includes encoding component 1844, which is configured to apply encoding techniques to the RU port identifier of the eAxC message to encode the set of indices and the layer / stream indices of each set, for example, as combined with Figure 15 1506 and / or Figure 17 As described in 1710.

[0264] Communication manager 1832 also includes a first part component 1846 configured to encode, based on the capability information, a group of endpoints associated with an eAxC message using a first part of the RU port identifier, the eAxC message including a DU port identifier, a frequency band sector identifier, a component carrier identifier, and the RU port identifier, for example, in combination with... Figure 14 1404 and / or Figure 15 As described in 1508.

[0265] Communication manager 1832 also includes a second part component 1848, which is configured to encode the RU endpoints of the endpoint group using the second part of the RU port identifier, for example, as in combination Figure 14 1406 and / or Figure 15 As described in 1510.

[0266] Communication manager 1832 also includes message component 1850, which is configured to send eAxC messages to the RU, for example, as in combination with Figure 14 1408 and / or Figure 15 As described in 1512. Exemplary message component 1850 can also be configured to send an eAxC message to the RU, the eAxC message including a group index associated with the endpoint group, for example, as combined with... Figure 16 1606 and / or Figure 17 As described in 1712.

[0267] Communication manager 1832 also includes configuration component 1852, which is configured to send eAxC allocation configuration, for example, as combined with Figure 17 As described in 1706. Exemplary configuration component 1852 can also be configured to abandon sending eAxC allocation configurations, for example, as in conjunction with... Figure 17 As described in 1708.

[0268] The device may include execution Figure 14 , Figure 15 , Figure 16 and / or Figure 17 The flowchart shows the algorithm as an additional component for each box. Therefore, Figure 14 , Figure 15 , Figure 16 and / or Figure 17 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0269] As shown in the figure, device 1802 may include various components configured for various functions. In one configuration, device 1802 (particularly baseband unit 1804) includes receiving capability information from an RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints. Exemplary device 1802 may also include unit for encoding the endpoint group associated with an eAxC message using a first portion of an RU port identifier based on the capability information. The eAxC message includes a DU port identifier, a frequency band sector identifier, a component carrier identifier, and the RU port identifier. Exemplary device 1802 also includes unit for encoding the RU endpoints of the endpoint group using a second portion of the RU port identifier. Exemplary device 1802 also includes unit for transmitting the eAxC message to the RU.

[0270] In another configuration, exemplary device 1802 also includes a unit for assigning the eAxC message to the RU endpoint of the endpoint group based on a set of characteristics associated with the eAxC message.

[0271] In another configuration, exemplary device 1802 further includes units for encoding the endpoint group using a first portion of the RU port identifier based on a static bit width. Exemplary device 1802 also includes units for encoding the RU endpoint using a second portion of the RU port identifier based on linear addressing of RU endpoints across the endpoint group.

[0272] In another configuration, exemplary device 1802 further includes units for encoding the endpoint group using a first portion of the RU port identifier based on a bit mask having a bit width corresponding to the endpoint group. Exemplary device 1802 also includes units for encoding the RU endpoint using a second portion of the RU port identifier based on the bit width of the RU port identifier and the bit width of the bit mask.

[0273] In another configuration, exemplary device 1802 also includes a unit for facilitating hierarchical addressing of the RU endpoints of the RU.

[0274] In another configuration, exemplary device 1802 includes units for receiving capability information from an RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints. Exemplary device 1802 also includes units for allocating eAxC messages to RU endpoints within the corresponding endpoint group, in part based on the capability information. Exemplary device 1802 further includes units for sending an eAxC message to the RU, the eAxC message including a group index associated with the endpoint group.

[0275] In another configuration, exemplary device 1802 also includes a unit for applying encoding techniques to the eAxC message's RU port identifier to encode the group index and the layer / stream index of each group.

[0276] In another configuration, exemplary device 1802 also includes a unit for sending eAxC allocation configuration to the RU.

[0277] In another configuration, exemplary device 1802 also includes a unit for abandoning the transmission of eAxC allocation configuration to the RU.

[0278] The unit may be one or more components of the device 1802 configured to perform the functions described therein. As described above, the device 1802 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Accordingly, in one configuration, the unit may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions described therein.

[0279] The aspects disclosed herein configure the RU to receive eAxC messages and perform handover based on the RU port identifier of the eAxC message. For example, the DU may encode the RU port identifier to indicate a group index via a first portion of the RU port identifier and a tier / flow index for each group via a second portion of the RU port identifier. The group index may indicate an endpoint group (e.g., an uplink channel group, SRS group, or PRACH group in the uplink direction, and a downlink channel group or SRS group in the downlink direction), and the tier / flow index for each group may indicate the RU endpoint. The RU may decode the RU port identifier to determine the endpoint group and group tier / flow, and then route the eAxC message to the correct hardware component for processing based on the group index. By indexing the eAxC message using the first and second portions of the RU port identifier, the aspects disclosed herein facilitate hierarchical addressing of the RU endpoints.

[0280] Furthermore, the aspects disclosed herein configure the RU to receive eAxC messages 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 tier / flow index for each group. The group index may indicate an endpoint group, and the tier / flow index for each group 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.

[0281] The aspects presented in this paper can enable improvements to RU ingress routing, for example, by simplifying switching and / or reducing the costs associated with lookup table size and lookup table processing through an eAxC-based allocation strategy.

[0282] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely illustrative of the example method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims provide the elements of each box in the sample order, but this does not imply limitation to the given specific order or hierarchy.

[0283] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein elements referred to in the singular are not intended to mean “one and only one,” but rather “one or more” unless specifically stated otherwise. Terms such as “if,” “when,” and “at the same time as,” should be interpreted as “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as “when,” do not imply a response to the occurrence of an action or an immediate action during the occurrence of an action, but simply suggest that if the condition is met, then the action will occur, but no specific or immediate time limit is required for the action to occur. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specifically stated, the term “some” means one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” and “device” cannot replace the term “unit.” Accordingly, no claim can be made that an element should be interpreted as a functional unit unless the element is explicitly described using the phrase “unit for…”.

[0284] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0285] Aspect 1 is an apparatus for a wireless communication RAN RU, the apparatus comprising at least one processor coupled to a memory and configured to send capability information to a DU indicating support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints; receiving an eAxC message from the DU based on the capability information, the eAxC message including a DU port identifier, a frequency band sector identifier, a component carrier identifier, and an RU port identifier; using a first portion of the RU port identifier to identify an endpoint group, the corresponding set of RU endpoints of the endpoint group being associated with a feature set; and using a second portion of the RU port identifier to index the eAxC message to the RU endpoints of the endpoint group.

[0286] Aspect 2 is the apparatus according to aspect 1, the apparatus further comprising: the memory and the at least one processor, the memory and the at least one processor being further configured to: route the eAxC message to a processing component based on the RU endpoint of the endpoint group, the processing component being configured to process the eAxC message associated with the feature set.

[0287] Aspect 3 is an apparatus according to any one of Aspects 1 and 2, the apparatus further comprising: the endpoint group comprising one or more of the following: a first set of groups for uplink endpoints and a second set of groups for downlink endpoints.

[0288] Aspect 4 is an apparatus according to any one of Aspects 1 to 3, the apparatus further comprising: a first portion of the RU port identifier corresponding to a group index, and a second portion of the RU port identifier corresponding to a layer / flow index for each group.

[0289] Aspect 5 is an apparatus according to any one of aspects 1 to 4, the apparatus further comprising: the capability information indicating: the number of endpoint groups, and the number of RU endpoints associated with the respective endpoint groups.

[0290] Aspect 6 is an apparatus according to any one of Aspects 1 to 5, the apparatus further comprising: the memory and the at least one processor being configured to: sample a quantity of received eAxC messages to determine an encoding technique associated with a corresponding RU port identifier of the received eAxC messages, the encoding technique being used to encode a first portion and a second portion of the corresponding RU port identifier; 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.

[0291] Aspect 7 is an apparatus according to any one of aspects 1 to 6, the apparatus further comprising: decoding a first portion of the RU port identifier based on a static bit width, and decoding a second portion of the RU port identifier based on linear addressing of RU endpoints across the endpoint group.

[0292] Aspect 8 is an apparatus according to any one of Aspects 1 to 6, the apparatus further comprising: decoding a first portion of the RU port identifier based on a bit mask having a bit width corresponding to the endpoint group, and decoding a second portion of the RU port identifier based on the bit width of the RU port identifier and the bit width of the bit mask.

[0293] Aspect 9 is an apparatus according to any one of aspects 1 to 8, the apparatus further comprising: the first portion and the second portion facilitating hierarchical addressing of the RU endpoints of the RU.

[0294] Aspect 10 is an apparatus according to any one of aspects 1 to 9, the apparatus further comprising: the feature set being based on one or more of the following: data layer, spatial stream, digital scheme and channel.

[0295] Aspect 11 is a method for implementing wireless communication as described in any one of aspects 1 to 10.

[0296] Aspect 12 is an apparatus for performing wireless communication, the apparatus comprising units for implementing any one of aspects 1 to 10.

[0297] Aspect 13 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 1 to 10.

[0298] Aspect 14 is an apparatus for wireless communication at a RAN DU, the apparatus comprising at least one processor coupled to a memory and configured to receive from a RU capability information indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints; 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 frequency band sector identifier, a component carrier identifier, and the RU port identifier; encoding RU endpoints of the endpoint group using a second portion of the RU port identifier; and transmitting the eAxC message to the RU.

[0299] Aspect 15 is an apparatus according to aspect 14, the apparatus further comprising: the memory and the at least one processor, the memory and the at least one processor being further configured to: assign the eAxC message to the RU endpoint of the endpoint group based on a set of characteristics associated with the eAxC message.

[0300] Aspect 16 is an apparatus according to any one of aspects 14 and 15, the apparatus further comprising: the feature set being based on one or more of the following: data layer, spatial stream, digital scheme and channel.

[0301] Aspect 17 is an apparatus according to any one of aspects 14 to 16, the apparatus further comprising: the endpoint group comprising one or more of the following: a first set of groups for uplink endpoints and a second set of groups for downlink endpoints.

[0302] Aspect 18 is an apparatus according to any one of aspects 14 to 17, the apparatus further comprising: a first portion of the RU port identifier corresponding to a group index, and a second portion of the RU port identifier corresponding to a layer / flow index for each group.

[0303] Aspect 19 is an apparatus according to any one of aspects 14 to 18, the apparatus further comprising: the capability information indicating: the number of endpoint groups, and the number of RU endpoints associated with the respective endpoint groups.

[0304] Aspect 20 is an apparatus according to any one of aspects 14 to 19, the apparatus further comprising: encoding the endpoint group using a first portion of the RU port identifier based on a static bit width, and encoding the RU endpoints using a second portion of the RU port identifier based on linear addressing of RU endpoints across the endpoint group.

[0305] Aspect 21 is an apparatus according to any one of aspects 14 to 19, the apparatus further comprising: encoding the endpoint group using a first portion of the RU port identifier based on a bit mask having a bit width corresponding to the endpoint group, and encoding the RU endpoints using a second portion of the RU port identifier based on the bit width of the RU port identifier and the bit width of the bit mask.

[0306] Aspect 22 is an apparatus according to any one of aspects 14 to 21, the apparatus further comprising: the first portion and the second portion facilitating hierarchical addressing of the RU endpoints of the RU.

[0307] Aspect 23 is a method for implementing wireless communication as described in any one of aspects 14 to 22.

[0308] Aspect 24 is an apparatus for performing wireless communication, the apparatus comprising units for implementing any one of aspects 14 to 22.

[0309] Aspect 25 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 14 to 22.

[0310] Aspect 26 is an apparatus for wireless communication at a RAN RU, the apparatus including at least one processor coupled to a memory and configured to send capability information to a DU indicating support for endpoint groups, each endpoint group being associated with a corresponding 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 in part based on the group index included in the eAxC message.

[0311] Aspect 27 is the apparatus according to aspect 26, the apparatus further comprising: the eAxC message including a DU port identifier, a frequency band sector identifier, a component carrier identifier, and an RU port identifier, wherein the RU port identifier includes the group index and a layer / stream index for each group.

[0312] Aspect 28 is an apparatus according to any one of aspects 26 and 27, the apparatus further comprising: the endpoint group comprising a first set of groups for uplink endpoints and a second set of groups for downlink endpoints.

[0313] Aspect 29 is an apparatus according to any one of aspects 26 to 28, the apparatus further comprising: RU endpoints assigned to the same endpoint group are associated with the same set of characteristics.

[0314] Aspect 30 is an apparatus according to any one of aspects 26 to 29, the apparatus further comprising: the capability information indicating: the number of endpoint groups, and the number of RU endpoints associated with each endpoint group in the respective endpoint group.

[0315] Aspect 31 is an apparatus according to any one of aspects 26 to 30, the apparatus further comprising: the memory and the at least one processor, the memory and the at least one processor being further configured to: sample a quantity of received eAxC messages to determine an encoding technique associated with an RU port identifier of the received eAxC messages, the encoding technique being used to encode the group index of the RU port identifier and the layer / stream index of each group.

[0316] Aspect 32 is an apparatus according to any one of aspects 26 to 31, the apparatus further comprising: the encoding technique including a static size field for the group index and linear addressing of the layer / stream index for each group across the endpoint groups.

[0317] Aspect 33 is an apparatus according to any one of aspects 26 to 31, the apparatus further comprising: the encoding technique including a bitmask for the group index, and the size of the layer / stream index of each group associated with the respective group index being based on the size of the RU port identifier and the size of the respective bitmask.

[0318] Aspect 34 is a method for implementing wireless communication as described in any one of aspects 26 to 33.

[0319] Aspect 35 is an apparatus for performing wireless communication, the apparatus comprising units for implementing any one of aspects 26 to 33.

[0320] Aspect 36 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 26 to 33.

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

[0322] Aspect 38 is the apparatus according to aspect 37, the apparatus further comprising: the eAxC message including a DU port identifier, a frequency band sector identifier, a component carrier identifier, and an RU port identifier, wherein the RU port identifier includes the group index and a layer / stream index for each group.

[0323] Aspect 39 is an apparatus according to any one of aspects 37 and 38, the apparatus further comprising: the endpoint group comprising a first set of groups for uplink endpoints and a second set of groups for downlink endpoints.

[0324] Aspect 40 is an apparatus according to any one of aspects 37 to 39, the apparatus further comprising: RU endpoints assigned to the same endpoint group are associated with the same set of characteristics.

[0325] Aspect 41 is an apparatus according to any one of aspects 37 to 40, the apparatus further comprising: the capability information indicating: the number of endpoint groups, and the number of RU endpoints associated with each endpoint group in the respective endpoint group.

[0326] Aspect 42 is an apparatus according to any one of aspects 37 to 41, the apparatus further comprising: the memory and the at least one processor, the memory and the at least one processor being further configured to: apply an encoding technique to the RU port identifier of the eAxC message to encode the group index and the layer / stream index of each group.

[0327] Aspect 43 is an apparatus according to any one of aspects 37 to 42, the apparatus further comprising: the encoding technique including a static size field for the group index and linear addressing of the layer / stream index for each group across the endpoint groups.

[0328] Aspect 44 is an apparatus according to any one of aspects 37 to 42, the apparatus further comprising: the encoding technique including a bitmask for the group index, and the size of the layer / stream index of each group associated with the respective group index being based on the size of the RU port identifier and the size of the respective bitmask.

[0329] Aspect 45 is a method for implementing wireless communication as described in any one of aspects 37 to 44.

[0330] Aspect 46 is an apparatus for performing wireless communication, the apparatus comprising units for implementing any one of aspects 37 to 44.

[0331] Aspect 47 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 37 to 44.

Claims

1. An apparatus for wireless communication at a radio unit RU in a radio access network RAN, the apparatus comprising: At least one memory containing instructions; and At least one processor is configured to execute the instructions to cause the device to: Send capability information indicating support for endpoint groups to the Distributed Unit (DU), each endpoint group being associated with a corresponding RU endpoint set; Based on the capability information, the extended antenna carrier eAxC message is received from the DU, the eAxC message including DU port identifier, frequency band sector identifier, component carrier identifier and RU port identifier; The first part of the RU port identifier is used to identify the endpoint group, and the corresponding set of RU endpoints of the endpoint group is associated with the same set of characteristics; as well as The second part of the RU port identifier is used to index the eAxC message to the RU endpoint of the endpoint group.

2. The apparatus of claim 1, wherein the at least one processor is further configured to cause the apparatus to: The eAxC message is routed to a processing component based on the RU endpoint of the endpoint group, the processing component being configured to process the eAxC message associated with the feature set.

3. The apparatus of claim 1, wherein the set of endpoints comprises one or more of the following: The first set of groups used for uplink endpoints, and The second set of groups used for downlink endpoints.

4. The apparatus of claim 1, wherein 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 layer / flow index for each group.

5. The apparatus of claim 1, wherein the capability information indicates: The number of endpoint groups, and The number of RU endpoints associated with the corresponding endpoint group.

6. The apparatus of claim 1, wherein the at least one processor is further configured to cause the apparatus to: A certain amount of received eAxC messages are sampled to determine an encoding technique associated with a corresponding RU port identifier of the received eAxC message, the encoding technique being used to encode a first part and a second part of the corresponding RU port identifier; The first part of the RU port identifier is decoded based on the encoding technique described above; as well as The second part of the RU port identifier is decoded based on the encoding technique.

7. The apparatus of claim 6, wherein the at least one processor is configured to cause the apparatus to: Decode the first part of the RU port identifier based on the static bit width, and The second part of the RU port identifier is decoded based on linear addressing of the RU endpoints across the endpoint group.

8. The apparatus of claim 6, wherein the at least one processor is configured to cause the apparatus to: The first portion of the RU port identifier is decoded based on a bitmask, the bitmask having a bit width corresponding to the endpoint group, and The second part of the RU port identifier is decoded based on the bit width of the RU port identifier and the bit width of the bit mask.

9. The apparatus of claim 1, wherein the first portion and the second portion facilitate hierarchical addressing of the RU endpoints of the RU.

10. The apparatus of claim 1, wherein the set of characteristics is based on one or more of the following: Data layer Spatial flow, Digital solutions, and Channel.

11. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor.

12. A method for wireless communication at a radio unit RU in a radio access network (RAN), the method comprising: Send capability information indicating support for endpoint groups to the Distributed Unit (DU), each endpoint group being associated with a corresponding RU endpoint set; Based on the capability information, the extended antenna carrier eAxC message is received from the DU, the eAxC message including DU port identifier, frequency band sector identifier, component carrier identifier and RU port identifier; The first part of the RU port identifier is used to identify the endpoint group, and the corresponding set of RU endpoints of the endpoint group is associated with the same set of characteristics; as well as The second part of the RU port identifier is used to index the eAxC message to the RU endpoint of the endpoint group.

13. The method according to claim 12, further comprising: The eAxC message is routed to a processing component based on the RU endpoint of the endpoint group, the processing component being configured to process the eAxC message associated with the feature set.

14. The method according to claim 12, further comprising: A certain amount of received eAxC messages are sampled to determine an encoding technique associated with the corresponding RU port identifier of the received eAxC message, the encoding technique being used to encode a first part and a second part of the corresponding RU port identifier; The first part of the RU port identifier is decoded based on the encoding technique described above; as well as The second part of the RU port identifier is decoded based on the encoding technique.

15. The method of claim 14, wherein Decode the first part of the RU port identifier based on the static bit width, and The second part of the RU port identifier is decoded based on linear addressing of the RU endpoints across the endpoint group.

16. The method of claim 14, wherein The first portion of the RU port identifier is decoded based on a bitmask, the bitmask having a bit width corresponding to the endpoint group, and The second part of the RU port identifier is decoded based on the bit width of the RU port identifier and the bit width of the bit mask.

17. An apparatus for wireless communication at a distributed unit (DU) in a radio access network (RAN), the apparatus comprising: At least one memory containing instructions; and At least one processor is configured to execute the instructions to cause the device to: Receive capability information from radio unit RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints; Based on the capability information, the first part of the RU port identifier is used to encode the endpoint group associated with the extended antenna carrier eAxC message, which includes the DU port identifier, the frequency band sector identifier, the component carrier identifier, and the RU port identifier, wherein the corresponding RU endpoint set of the endpoint group is associated with the same feature set. The RU endpoints of the endpoint group are encoded using the second part of the RU port identifier; as well as Send the eAxC message to the RU.

18. The apparatus of claim 17, wherein the at least one processor is further configured to cause the apparatus to: The eAxC message is assigned to the RU endpoint of the endpoint group based on the set of characteristics associated with it.

19. The apparatus of claim 18, wherein the set of characteristics is based on one or more of the following: Data layer Spatial flow, Digital solutions, and Channel.

20. The apparatus of claim 17, wherein the set of endpoints comprises one or more of the following: The first set of groups used for uplink endpoints, and The second set of groups used for downlink endpoints.

21. The apparatus of claim 17, wherein 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 layer / flow index for each group.

22. The apparatus of claim 17, wherein the capability information indicates: The number of endpoint groups, and The number of RU endpoints associated with the corresponding endpoint group.

23. The apparatus of claim 17, wherein the at least one processor is configured to cause the apparatus to: The endpoint group is encoded using the first portion of the RU port identifier based on the static bit width, and The RU endpoints are encoded using the second part of the RU port identifier for linear addressing across the endpoint group of RU endpoints.

24. The apparatus of claim 17, wherein the at least one processor is configured to cause the apparatus to: The endpoint group is encoded using the first portion of the RU port identifier based on a bitmask, the bitmask having a bit width corresponding to the endpoint group, and The RU endpoint is encoded using the second part of the RU port identifier based on the bit width of the RU port identifier and the bit width of the bit mask.

25. The apparatus of claim 17, wherein the first portion and the second portion facilitate hierarchical addressing of the RU endpoints of the RU.

26. The apparatus of claim 17, further comprising a transceiver coupled to the at least one processor.

27. A method for wireless communication at a distributed unit (DU) in a radio access network (RAN), the method comprising: Receive capability information from radio unit RU indicating the RU's support for endpoint groups, each endpoint group being associated with a corresponding set of RU endpoints; Based on the capability information, the first part of the RU port identifier is used to encode the endpoint group associated with the extended antenna carrier eAxC message, which includes the DU port identifier, the frequency band sector identifier, the component carrier identifier, and the RU port identifier, wherein the corresponding RU endpoint set of the endpoint group is associated with the same feature set. The RU endpoints of the endpoint group are encoded using the second part of the RU port identifier; as well as Send the eAxC message to the RU.

28. The method of claim 27, further comprising: The eAxC message is assigned to the RU endpoint of the endpoint group based on the set of characteristics associated with it.

29. The method of claim 27, wherein The endpoint group is encoded using the first portion of the RU port identifier based on the static bit width, and The RU endpoints are encoded using the second part of the RU port identifier for linear addressing across the endpoint group of RU endpoints.

30. The method of claim 27, wherein The endpoint group is encoded using the first portion of the RU port identifier based on a bitmask, the bitmask having a bit width corresponding to the endpoint group, and The RU endpoint is encoded using the second part of the RU port identifier based on the bit width of the RU port identifier and the bit width of the bit mask.

31. A computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 12 to 16.

32. A computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 27 to 30.

Images