Dynamic placement of FHM and FHGW in fh

Abstract

Systems and methods for the dynamic placement of fronthaul multiplexing and fronthaul gateway in a fronthaul are described herein. In certain embodiments, a network system includes one or more intermediate nodes. Further, the network system includes one or more radio units configured to extend wireless communications from one or more core networks into a coverage area, wherein the one or more radio units communicate with the one or more core networks through one or more paths extending through the one or more intermediate nodes. Additionally, the one or more intermediate nodes are configured to dynamically implement at least one of fronthaul multiplexing functionality and fronthaul gateway functionality.

Description

DYNAMIC PLACEMENT OF FHM AND FHGW IN FHCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Patent Application Serial No. 63 / 672,157 entitled “DYNAMIC PLACEMENT OF FHM AND FHGW IN FH,” filed on July 16, 2024, which is incorporated herein by reference in its entirety.BACKGROUND

[0002] Wireless communications service providers are deploying 5G radio access networks (RANs). Such 5G radio access networks are configured to satisfy the open radio access network (O-RAN) Alliance specifications (“O-RAN specifications”). The O-RAN specifications include, without limitation, the O-RAN fronthaul working group control, user and synchronization plane specification (O-RAN- WG4.C US.0- R003-V15.00) and O-RAN Alliance working group 4 management plane specification (0-RAN-WG4.MP.0-R003-vl5.00); the O-RAN specifications are hereby incorporated by reference herein in their entirety.

[0003] The O-RAN specifications permit interoperability of RAN components, e.g., O-RAN specification compliant radios (or O-RAN radio units or O-RAN radios) and O-RAN specification compliant distributed units (or O-RAN distributed units), made by different vendors. The O-RAN distributed unit may be executed on a server system, e.g., local server network(s) and / or cloud computing system(s). The O-RAN distributed unit (O-DU) may comprise virtual baseband unit(s)). The O-RAN specifications utilize message protocols to communicate between remote radio units and virtual baseband units that differ from those used in legacy systems, e g., 4G specification compliant radio access networks (or 4G radio access networks). A virtual baseband unit processes, e.g., encodes, baseband data received from and sent to the radio(s). A radio transmits and / or receives data at one or more frequencies translated above baseband. The virtual baseband unit and radio(s) are components of a communications system such as a cellular communications system.

[0004] Systems following the O-RAN specification may be used to provide communication services within a shared cell, where the system is provided by a neutral host. In particular, multiple mobile network operators (MNOs) may beconnected to a single communication system to provide communication services within the coverage area associated with the shared cell. The different MNOs may use different communication hardware to connect to the shared cell communication system, and the communication system may use various radio units provided by the neutral host to communicate with user equipment within the coverage area provided by the system.SUMMARY

[0005] Systems and methods for the dynamic placement of fronthaul multiplexing and fronthaul gateway in a fronthaul are described herein. In certain embodiments, a network system includes one or more intermediate nodes. Further, the network system includes one or more radio units configured to extend wireless communications from one or more core networks into a coverage area, wherein the one or more radio units communicate with the one or more core networks through one or more paths extending through the one or more intermediate nodes. Additionally, the one or more intermediate nodes are configured to dynamically implement at least one of fronthaul multiplexing functionality and fronthaul gateway functionality.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Drawings accompany this description and depict only some embodiments associated with the scope of the appended claims. Thus, the described and depicted embodiments should not be considered limiting in scope. The accompanying drawings and specification describe the exemplary embodiments, and features thereof, with additional specificity and detail, in which:

[0007] FIG. 1 is a block diagram illustrating a shared network system according to an aspect of the present disclosure;

[0008] FIG. 2 is a block diagram illustrating a shared network system implementing dynamic FHM and FHGW according to an aspect of the present disclosure; and

[0009] FIG. 3 is a flowchart diagram of a method for implementing dynamic FHM and FHGW according to an aspect of the present disclosure.

[0010] Per common practice, the drawings do not show the various described features according to scale, but the drawings show the features to emphasize the relevance of the features to the example embodiments.DETAILED DESCRIPTION

[0011] The following detailed description refers to the accompanying drawings that form a part of the present specification. The drawings, through illustration, show specific illustrative embodiments. However, it is to be understood that other embodiments may be used and that logical, mechanical, and electrical changes may be made.

[0012] In 0-RAN, a base station is typically implemented in a disaggregated manner in which each base station is partitioned into at least one central unit (CU), at least one distributed unit (DU), and one or more radio units (RUs). Used herein, the terms “north” or “northbound” mean “upstream” or toward the DU. while the terms “south” or “southbound” mean "downstream" or away from the DU.

[0013] The 0-RAN specifications define a “shared cell” configuration or implementation in which a single cell is served using multiple RUs. The O-RAN shared cell implementation attempts to make more efficient use of bandwidth to and from DUs (compared to O-RAN 1.0) in order to support communicating front-haul data with the multiple RUs. The O-RAN shared cell implementation is described in detail in Section 13, “Support of Shared Cell” in the O-RAN Working Group 4 (Open Fronthaul Interfaces WG) Control, User and Synchronization Plane Specification version 10.0 from October 2022 (0-RAN.WG4.CUS.0-R003-vl5.00, hereinafter “Support of Shared Cell O-RAN Specification,” available at pages 295-314 of PDF at https: / / specifications.o-ran.org / specifications ), which is incorporated herein by reference. One having skill in the art would understand that the standards presented in the cited documents are subject to periodic updates. The embodiments disclosed herein may, where applicable, be adapted to later versions of the standard, provided such adaptations do not rely on features absent from version 15.

[0014] In the O-RAN shared cell implementation, there are generally two modes of operation in the fronthaul: Fronthaul Multiplexer (FHM) mode and Cascade mode. Examples of implementing a shared cell include an FHM or fronthaul gateway (FHGW) in order to more efficiently support one-DU-to-many-RU mapping. In particular, FHM enables RU selection for transmission and reception from a set of RUs. and FHGW enables protocol translations to / from O-RAN. In one example. FHM (1) replicates the downlink packet stream (from the DU) for each RU and (2)uses combining / digital summation on the uplink packet stream from the RUs (before sending to the DU). The combining / digital summation includes: (1) adding the corresponding in-phase (I) samples in corresponding physical resource blocks (PRBs) (from all the RUs); (2) adding the corresponding quadrature-phase (Q) samples in corresponding PRBs (from all the RUs); and (3) sending a combined stream of I / Q data from the FHM to the DU. The combining / digital summation may optionally include some overflow management. Using the shared cell implementation, the DU can send and receive a single packet stream (with a bandwidth of approximately N PRBs) instead of M packet streams (one for each RU with a total bandwidth of approximately N PRBs x M RUs). By reducing the DU transmitted and received data to a single stream of N PRBs, the shared cell implementation reduces bandwidth (between the DU and multiple RUs).

[0015] An FHM may be limited in how many RUs can connect to it (such as no more than 8 RUs in some examples). In some implementations, multiple FHMs are cascaded from one another to support larger quantities of RUs. In some examples, each FHM implements front-haul transport functionality and does not include radio functionality for transmitting and receiving RF signals with UEs. In some examples, multicast is used in the downlink to reduce fronthaul bandwidth, and unicast is used in the uplink.

[0016] With FHM and FHGW, O-RAN gives operators a lot of flexibility for deployment operations. For example, a system may employ an O-RAN DU operating with a non-O-RAN RU while abstracting the RU for operation with the DU. However, for an O-RAN DU, determining whether to employ the FHM and FHGW functions is often need-based and depends on the node and location of the node connected to the DU. Further, the determination as to the deployment of FHM and FHGW is often a manual determination calling for operator intervention. When DUs and RUs are deployed in multi-operator and multi-vendor environments, the cost of making determinations concerning FHM and FHGW and subsequent maintenance is significant.

[0017] In certain embodiments, FHM and FHGW functions may be dynamically placed in the fronthaul path with minimal operator intervention. In particular, nodes within the fronthaul path may be configured to host the FHM and FHGW functions. Accordingly, the nodes may employ the FHM and FHGW functions dynamicallybased on the operative needs of a system. Further, methods to incorporate the dynamic placement of FHM and FHGW functions may be M-plane driven or C-plane driven.

[0018] In embodiments where the dynamic placement of FHM and FHGW functions are M-plane driven, input from an operator concerning protocols supported by an RU and information about expected bandwidth may be used to determine whether to exercise dynamically placed FHM and FHGW functionality. When the dynamic placement of FHM and FHGW functions are C-plane driven, the sensing of protocols in components may be used to determine whether to exercise the dynamically placed FHM and FHGW functionality . The placement of these dynamic functions on the path between a DU and a RU may reduce costs by reducing the hardware footprint, energy' needs, and human capital used to manage networks.

[0019] FIG. 1 is a block diagram illustrating an example of a communication system 100. In the example shown in FIG. 1, the communication system 100 is implemented using an 0-RAN or other point-to-multipoint distributed base station architecture. The communication system 100 may also be referred to here as an “O-RAN” or an “O- RAN system.” In some examples, communication system 100 includes one or more central units 101 at least one distributed unit (DU or O-DU) 103, one or more intermediate nodes / switches 105-1 - 105-3 (referenced herein generally as intermediate nodes / switches 105), at least one system manager 109, and one or more radio units (RU or O-RU) (such as radio unit (RU) 107-1 and any quantity of optional radio unit (RU) 106-2 through optional radio unit (RU) 107-X, referenced herein generally as RU(s) 107) configured to serve at least one user equipment (UE) 111-1 — 1 11-M (referenced herein generally as UE(s) 111) within the site at which wireless services is being provided.

[0020] In some examples, the at least one CU 101 and at least one DU 103 may implement a ‘‘base station,” “base station entity,” or “base station system” (which in the context of a fourth generation (4G) Long Term Evolution (LTE) system, may also be referred to as an “evolved NodeB,” “eNodeB,” or “eNB”; in the context of a fifth generation (5G) New Radio (NR) system, may also be referred to as a “gNodeB” or “gNB”; and may take different names in other current or future generations of radio access networks (RAN) and communication networks). In some examples, the at least one CU 101 and / or at least one DU 103 are located remotely from the site at whichwireless service is being provided, e g., in centralized banks of nodes. In optional embodiments, some of the functionality of the CU 101 and DU 103 may be implemented as part of a baseband controller 106 located at a site, where the baseband controller 106 communicates with a device management system such as the system manager 109. Additionally, the RUs 107 may be physically separated from each other at the site at which wireless service is being provided, although they are each communicatively coupled to the one or more DUs 103 via the at least one fronthaul network 113. A base station may be used to provide UEs 111 with mobile access to a mobile network operator’s (MNO) core network 115 to enable UEs 111 to wirelessly communicate data and voice (using, for example, Voice over LTE (VoLTE) technology or a 3GPP 5G RAN providing wireless service using a 5G air interface).

[0021] In certain embodiments, the communication system 100 implements a base station as a respective 5GNR gNB. In such a configuration, each CU 101 implements Layer 3 and non-time critical Layer 2 functions for the 5G NR gNB. In some examples, each CU 101 may be further partitioned into at least one control-plane entity (“CU-CP”) and at least one user-plane entity (“CU-UP”) that handles the control-plane and user-plane processing of the CU 101, respectively. In examples, each DU 103 is configured to implement the time-critical Layer 2 functions and, except as described below, at least some of the Layer 1 functions for the gNB. In this example, each RU 107 is configured to implement the physical layer functions for the gNB that are not implemented in the DU 103, as well as the RF interface. Further, in some implementations, the intermediate nodes / switches 105 may also perform some of the Layer 2 or physical layer functions. Also, each RU 107 includes or is coupled to a respective set of one or more antennas used to radiate downlink RF signals to UEs 111 and receive uplink RF signals transmitted by UEs 111.

[0022] In general, the communication system 100 is configured to provide wireless service to various items of user equipment (UEs) 110 (such as user equipment (UE) 110-1 and any quantity of optional user equipment (UE) 110-2 through optional user equipment (UE) 110-B). Unless explicitly stated to the contrary, references to Layer 1, Layer 2, Layer 3, and other or equivalent layers (such as the Physical Layer or the Media Access Control (MAC) Layer) refer to layers of the particular wireless interface (for example. Fourth Generation (4G) Long Term Evolution (LTE) or Fifth Generation (5G) New Radio (NR)) used for wirelessly communicating with UEs 110.Furthermore, it is also to be understood that 5G NR embodiments can be used in both standalone and non-standalone modes (or other modes developed in the future), and the following description is not intended to be limited to any particular mode. Moreover, although some embodiments are described here as being implemented for use with 5G NR, other embodiments can be implemented for use with other wireless interfaces, and the following description is not intended to be limited to any particular wireless interface.

[0023] In examples, the at least one CU 101 is communicatively coupled to at least one corresponding core network 115 of the associated wireless operator via at least one backhaul network 117. The at least one backhaul network 117 is typically a public wide area network such as the Internet, though it is understood that the at least one backhaul network 117 can be implemented in other ways. In examples, at least one DU 103 is communicatively coupled to at least one CU 101 via at least one midhaul network. In examples, the midhaul interface promulgated by the O-RAN Alliance is used for the midhaul network between the DU 103 and the at least one CU 101. In examples, at least one RU 107 is communicatively coupled to at least one DU 103 via at least one fronthaul network 113. In examples, the fronthaul interface promulgated by the O-RAN Alliance is used for the fronthaul network 113 between each RUs 107 and the respective DU 103. In examples, each of the backhaul network 117, the midhaul network, and / or the fronthaul network 113 may be implemented with one or more switches, routers, and / or other networking devices. For example, the fronthaul network 113 may include the intermediate node / s witches 105. In some examples, the backhaul network 117, the midhaul network, and / or the fronthaul network 113 may be implemented with switched Ethernet using a switched Ethernet network and an Ethernet switch.

[0024] Although FIG. 1 (and the description set forth herein more generally) is described in the context of 5G embodiments where each logical base station entity is partitioned into a CU 101, DUs 103, and RUs 107 and, for at least some of the physical channels, some physical-layer processing is performed in the DUs 103 with the remaining physical-layer processing being performed in the RUs 107 or intermediate node / sw itches 105, it is to be understood that the techniques described here can be used with other wireless interfaces (for example, 4G LTE) and with other w ays of implementing a base station entity (for example, using a conventionalbaseband band unit (BBU) / remote radio head (RRH) architecture). Accordingly, references to a CU, DU, or RU in this description and associated figures can also be considered to refer more generally to any entity (including, for example, any '‘base station” or “RAN” entity) implementing any of the functions or features described here as being implemented by a CU, DU, or RU.

[0025] Each CU 101, DU 103, intermediate nodes / switches 105, and RUs 107 and any of the specific features described here as being implemented thereby, can be implemented in hardware, software, or combinations of hardware and software, and the various implementations (whether hardware, software, or combinations of hardware and software) can also be referred to generally as “circuitry,” a “circuit,” or “circuits” that is or are configured to implement at least some of the associated functionality. When implemented in software, such software can be implemented in software or firmware executing on one or more suitable programmable processors (or other programmable device) or configuring a programmable device (for example, processors or devices included in or used to implement special-purpose hardware, general-purpose hardware, and / or a virtual platform). In such a software example, the software can comprise program instructions that are stored (or otherwise embodied) on or in an appropriate non-transitory storage medium or media (such as flash or other non-volatile memory, magnetic disc drives, and / or optical disc drives) from which at least a portion of the program instructions are read by the programmable processor or device for execution thereby (and / or for otherwise configuring such processor or device) in order for the processor or device to perform one or more functions described here as being implemented the software. Such hardware or software (or portions thereof) can be implemented in other ways (for example, in a field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc.).

[0026] Moreover, each CU 101, DU 103, intermediate nodes / switches 105, and RUs 107, can be implemented as a physical network function (PNF) (for example, using dedicated physical programmable devices and other circuitry) and / or a virtual network function (VNF) (for example, using one or more general purpose servers (possibly with hardware acceleration) in a scalable cloud environment and in different locations within an operator's network (for example, in the operator’s “edge cloud” or “central cloud”). Each VNF can be implemented using hardware virtualization, operating system virtualization (also referred to as containerization), and applicationvirtualization, as well as various combinations of two or more of the preceding. Where containerization is used to implement a VNF, it may also be referred to as a ■‘containerized network function’’ (CNF). For example, in the exemplary embodiment shown in FIG. 1, each RU 107 and FHM is implemented as a PNF and is deployed in or near a physical location where radio coverage is to be provided, and each CU 101 and DU 103 is implemented using a respective set of one or more VNFs deployed in a distributed manner within one or more clouds (for example, within an “edge” cloud or “central” cloud). Each CU 101, DU 103, intermediate nodes / s witches 105, and RUs 107, and any of the specific features described here as being implemented thereby, can be implemented in other ways.

[0027] The links shown in the communication system 100 in FIG. 1 show' all the RUs 107 being connected to the fronthaul network 113 (which could be implemented with one or more intermediate nodes / switches 105. which may include switches, routers, and / or other networking devices). The actual physical links between devices in the backhaul netw ork 117, the midhaul netw ork, and / or the fronthaul network 113 may be implemented using different media, such as conductive media (copper, multi-rate, multi-mode cables, etc.) and optical media (fiber optic cables). In examples, each RU 107 and each physical node on which each DU 103 is implemented includes one or more Ethernet network interfaces to couple each RU 107 and each physical node implementing the DU 103 to the fronthaul network 113 in order to facilitate communications between the DU 103 and the RUs 107.

[0028] The RUs 107 may be deployed at a site to provide wireless coverage and capacity for one or more wireless network operators. The site at which wireless service is being provided may cover, for example, a building or campus or other grouping of buildings (used, for example, by one or more businesses, governments, or other enterprise entities) or some other public venue (such as a hotel, resort, amusement park, hospital, shopping center, university campus, arena, or an outdoor area such as a ski area, stadium or a densely populated downtown area). In some configurations, the site at which w ireless service is being provided is at least partially (and optionally entirely) indoors, but other alternatives are possible.

[0029] Each UE 111 may be a computing device with at least one processor that executes instructions stored in memory', e.g., a mobile phone, tablet computer, mobilemedia device, mobile gaming device, laptop computer, vehicle-based computer, desktop computer, etc.

[0030] Each CU 101, DU 103. intermediate node / switch 105, and RU 107 can be implemented so as to use an air interface that supports one or more of frequencydivision duplexing (FDD) and / or time-division duplexing (TDD). Also, the CU 101 , DUs 103, intermediate node / switch 105, and RUs 107 can be implemented to use an air interface that supports one or more of the multiple-input-multiple-output (MIMO), single-input-single-output (SISO), single-input-multiple-output (SIMO), and / or beam forming schemes. For example, the CU 101, DUs 103, and RUs 107 can implement one or more of the 5GNR transmission modes. Moreover, the communication system 100 can be configured to support multiple air interfaces and / or to support multiple wireless operators.

[0031] In examples for the downlink, the DU 103 communicates downlink controlplane messages, downlink user-plane messages, and uplink control-plane messages to the RU 107-1, which uses the downlink control-plane and downlink user-plane messages to wirelessly transmit downlink radio frequency signals using a respective set of antennas for reception by UEs 110.

[0032] In examples in the uplink, the RUs 107 wirelessly receive uplink radio frequency signals transmitted from UEs 111 using a respective set of antennas and generate uplink user-plane data from the received RF signals. In examples, an intermediate node / switch 105 may also combine user data received from the RUs 107. In examples, the combining is an uplink summation. In examples, the combining is uplink coherent combining that requires phase information for the data.

[0033] In examples in the uplink, for each uplink slot, the serving DU 103 schedules one or more UEs 111 to transmit during that slot. In examples, the DU 103 sends uplink control-plane messages to each RU 107 identifying the resource blocks (RBs) for which the RU 107 should provide baseband IQ data. The RBs for which the RU 107 should provide baseband IQ data are also referred to here as “front-hauled RBs.’’

[0034] In embodiments where the baseband IQ data communicated over the fronthaul comprises frequency -domain baseband IQ data, the front-hauled RBs comprise only those RBs that have been assigned to the scheduled UEs 111 for uplink transmissions during that slot. In embodiments where the baseband IQ data communicated over thefronthaul comprises time-domain baseband IQ data, the front-hauled RBs comprise all of the RBs for the slot (due to the time-domain nature of the baseband IQ data).During each uplink slot, for each antenna port, each RU 107 generates respective baseband IQ data for each front-hauled RB from an uplink RF analog signal received via a respective one of the antennas associated with that RU 107. For each RU 107, for each uplink slot, the RU 107 generates an uplink user-plane message that includes the baseband IQ data generated at that RU 107 for the various front-hauled RBs and antenna ports and communicates the uplink user-plane messages northbound.

[0035] Each CU 101, DU 103, intermediate node / switch 105, and RU 107, and any of the specific features described here as being implemented thereby, can be implemented in other ways. Additionally, it should be noted that the systems and methods described herein may also be used in other distributed RANs, e.g., a distributed antenna system (DAS).

[0036] In additional embodiments, the DU 103 and intermediate node / switches 105 may implement fronthaul multiplexers (FHM). For example, FHM functionality may be integrated into the DU 103, one or more of the intermediate node / switches 105, or one or more of the RUs 107. Alternatively, one or more of the intermediate node / switches may operate as independent FHMs.

[0037] In embodiments employing FHM, the DU 103 may replicate downlink packet streams (from the DU) for each RU 107. Also, intermediate nodes / switches 105 may use combining / digital summation on the uplink packet stream from the RUs 107 (before sending to the DU). The combining / digital summation includes: (1) adding the corresponding in-phase (I) samples in corresponding physical resource blocks (PRBs) (from all the connected RUs 107); (2) adding the corresponding quadrature-phase (Q) samples in corresponding PRBs (from all the connected RUs 107); and (3) sending a combined stream of I / Q data from the node employing FHM to the DU 103. The combining / digital summation may optionally include some overflow management. Using the shared cell implementation, the DU 103 can send and receive a single packet stream (with a bandwidth of approximately N PRBs) instead of M packet streams (one for each RU 107 with a total bandwidth of approximately N PRBs x M RUs). By reducing the transmitted to and received data from the RU 107 to a single stream of N PRBs, the employment of FHM within a shared cell implementation more efficiently uses the available bandwidth. In some embodiments, the intermediatenodes / switches 105 between the DU 103 and the RUs 107 may dynamically employ FHM and FHGW functionality.

[0038] FIG. 2 is a diagram of a system 200 that dynamically employs FHM and / or FHGW within nodes of the system. For example, With FHM and FHGW, O-RAN provides for deployment flexibility. For example, a system 200 may employ an O- RAN DU 203 operating with a non-O-RAN RU 207, where FHGW may abstract the RU 207 to conform with O-RAN protocols for proper operation with the DU 203. However, determining when to implement the FHM or FHGW between the DU 203 and an RU 207 for an O-RAN DU is often need-based and may depend on the nodes and locations of the nodes connected to the DU. Further, determining whether to deploy FHM and FHGW is often manually performed through operator intervention. When DUs 203 and RUs 207 are deployed in multi-operator and multi-vendor environments, the cost of making determinations concerning FHM and FHGW and subsequent maintenance is significant.

[0039] In certain embodiments, FHM and FHGW functions may be dynamically placed in the fronthaul path with minimal operator intervention. In particular, the system 200 may include intermediate nodes / switches 205 within the fronthaul path 113, where the intermediate nodes / switches 205 may be dynamically configured to host FHM and FHGW functions. Accordingly, the intermediate nodes / switches 205 may employ the FHM and FHGW functions dynamically based on the operative needs of a system.

[0040] In some embodiments, the FHM and FHGW functionality may be dynamically used to facilitate the connection of DUs 203 to RUs 207, where the DUs 203 and RUs 207 support different protocols. For example, when a mobile network operator (MNO) connects to the system 200 either through a DU 203 that is part of the system 200 or through a DU 203 provided by the MNO, where the DU 203 provided by the MNO connects to an intermediate node / switch 205 of the system 200, the DU 203 or MNO hardware may support various protocols. In one implementation, the DU 203 may support the protocol defined by O-RAN LLS 7.2, and some of the RUs 207 may support other protocols. Accordingly, one of the intermediate nodes / switches 205 between the RU 207 and the DU 203 may include FHGW functionality to perform protocol translation between the DU 203 and the RU 207. Thus, the incorporation of dynamic FHGW and FHM functionality in the nodes may enable the connection ofMNO hardware to the system 200 without requiring manual operator intervention to perform maintenance. Also, the dynamic FHGW and FHM functionality enables connecting the system to new MNOs without having to update the RUs 207 when the DUs 203 associated with the MNO use a different protocol than the RUs 207.

[0041] In additional embodiments, the FHM and FHGW functionality may be dynamically used to improve bandwidth usage based on expected bandwidth usage and bandwidth thresholds for the intermediate nodes / switches 205 between a DU 203 and an RU 207. For example, the system 200 may extend wireless service from an MNO through a DU 203 into a coverage area associated with a stadium. During an event, the FHM and FHGW functionality may be controlled to provide more capacity within the stadium. After the completion of the event, the FHM and FHGW functionality may be dynamically controlled to shift the capacity from within the stadium to the outside of the stadium, adjusting the capacity to match the expected movement of people and the expected usage of the network. Accordingly, the system 200 may require less hardware, manual intervention, and maintenance to provide communication services within a coverage area for multiple MNOs.

[0042] In some embodiments, the FHM and FHGW functionality may be dynamically controlled by a system manager 209. The system manager 209 may communicate with the various intermediate nodes / switches 205 through the M-plane or through the C-plane to dynamically manage the FHM and FHGW functionality. Further, the FHM and FHGW functionality may be incorporated as part of the hardware / software used to implement the intermediate nodes / switches 205.

[0043] In certain embodiments, the dynamic placement of FHM and FHGW functionality may be managed by the system manager 209 through the M-plane. When the dynamic placement of FHM and FHGW functionality is managed through the M-plane, the FHM and FHGW functionality may allow for the selection of supported protocols (0-RAN, CPRI, etc.) between the RU 207 and the DU 203. Also, the M-plane management may permit the dynamic selection of intermediate nodes / switches 205 that execute the FHM and FHGW functions. For example, the system manager 209 may select whether an ethernet switch, a DU, or other node between a DU 203 and a RU 207 executes the FHM and FHGW functions.

[0044] Further, when managing the FHM and FHGW functions through the M-plane, when connecting a new MNO to the system 200, a management function on the system manager 209 may determine how the new MNO will affect the usage of the shared infrastructures. Also, the management function may determine the FHM and FHGW needs for the DU 203 of the new MNO based on the protocols used by the DU 203 of the new MNO. Using the expected usage information and the protocols supported by the DU 203 of the new MNO, the management function may identify the intermediate nodes / switches 205 in the system 200 that should have dynamic FHM and FHGW functionality to enable communications between RUs 207 and the DUs 203 and also to effectively manage bandwidth usage within the shared infrastructure of the system 200.

[0045] When the management function on the system manager 209 has identified the intermediate nodes / switches 205 that should have the FHM and FHGW functionality, the management function can communicate with the different intermediate nodes / switches 205 to deploy and run the identified FHM and FHGW configurations. In particular, the management function on the system manager 209 may indicate which ports on the intermediate nodes / switches 205 should perform protocol translation. Also, the management function may indicate which ports and switches should perform copy and combining functionality. Additionally, the management function on the system manager 209 may indicate when the ports and switches of the intermediate nodes / switches 205 should perform copying and combining based on the expected usage and computed expected headroom at the various nodes. Thus, controlling the FHM and FHGW configurations through the M-plane may help improve the onboarding of new operators and also improve the bandwidth usage of the system 200.

[0046] In certain embodiments, the dynamic placement of FHM and FHGW functionality may be managed through the C-plane. When the dynamic placement of FHM and FHGW functionality is managed through the C-plane, the FHM and FHGW functionality may also allow for the selection of supported protocols (O-RAN, CPRI, etc.) between the RU 207 and the DU 203. Also, like the M-plane management, the C-plane management permits the dynamic selection of intermediate nodes / switches 205 that execute the FHM and FHGW functions. However, where the M-plane management was performed by a management function on the system manager 209,C-plane management may be performed by the intermediate nodes / switches 205 directly. In particular, intermediate nodes / switches 205 may be equipped with sensors that detect information that the intermediate nodes / switches 205 can use to determine whether to execute FHM and FHGW functionality.

[0047] In some embodiments, when managing the FHM and FHGW functions through the C-plane, a protocol sensor may be incorporated on the intermediate nodes / switches 205 between the DUs 203 and the RUs 207. During link establishment between an RU 207 and a DU 203, a protocol sensor on an intermediate node / switch may determine the protocol in use and any split option employed by the RU 207 and the DU 203. Further, one or more of the intermediate nodes / switches 205 on the communication path between the DU 203 and RU 207 may determine the fronthaul bandwidth headroom for the different intermediate nodes / switches 205 between the DU 203 and the RU 207. When one or more of the intermediate nodes / switches 205 determines the fronthaul bandwidth headroom, the respective intermediate nodes / switches 205 may do so without coordination or receiving information from the other nodes.

[0048] In further embodiments, the intermediate nodes / switches 205 may use the protocol sensor to determine if FHM or FHGW functions need to be placed in a path between the DU 203 and the RU 207. If the FHM or FHGW function is to be placed in the path, the FHM or FHGW functions may perform protocol conversion as needed between the protocol of the RU 207 and the protocol of the DU 203. Further, the intermediate nodes / switches 205 may deploy FHM and FHGW functions on needed ports as required to perform protocol translation. Further, the intermediate nodes / switches 205 may perform protocol sensing at the time of link establishment for the RUs.

[0049] In additional embodiments, software and / or hardware on the intermediate nodes / switches 205 in the system 200 may sense the actual usage and threshold for each intermediate link between the DU 203 and the RU 207. Further, software and / or hardware may compute the actual headroom at the intermediate nodes / switches 205. From the determinations of the actual usage, thresholds for the links, and headroom, the intermediate nodes / switches may communicate through the C-plane to perform bandwidth optimization. For example, the intermediate nodes / switches may configure the ports and switches to perform copy and combine functions to and from the variousRUs 207 to improve the use of bandwidth by the system 200. The intermediate nodes / switches 205 may periodically perform measurements of the actual bandwidth utilization and headroom.

[0050] As described above, the dynamic placement of FHM and FHGW functions may be M-plane driven, where input from an operator concerning protocols supported by an RU and information about expected bandwidth may be used to determine whether to exercise dynamically placed FHM and FHGW functionality. When the dynamic placement of FHM and FHGW functions are C-plane driven, the sensing of protocols and usage in components may be used to determine whether to exercise the dynamically placed FHM and FHGW functionality. The use of the M-plane or C- plane when dynamically placing FHM and FHGW functionality may depend on whether prior knowledge of the network is available or whether the expected usage may be predetermined. The placement of these dynamic functions on the path between a DU and a RU may reduce costs by reducing a hardware footprint, energy needs, and human capital used to manage networks.

[0051] FIG. 3 is a flowchart diagram of a method 300 for implementing dynamic FHM and FHGW. The method 300 proceeds at 301, where data is transmitted between one or more radio units and one or more core networks through one or more intermediate nodes in a communication network. Further, the method 300 proceeds at 303, where at least one fronthaul multiplexing functionality and fronthaul gateway functionality is implemented in at least one intermediate node in the one or more intermediate nodes. Also, the method 300 proceeds at 305, where at least one of the fronthaul multiplexing functionality and the fronthaul gateway functionality is used to control the transmission of the data between the one or more radio units and the one or more core networks along one or more paths in the communication network.Example Embodiments

[0052] Example 1 includes a network system comprising: one or more intermediate nodes; and one or more radio units configured to extend wireless communications from one or more core networks into a coverage area, wherein the one or more radio units communicate with the one or more core networks through one or more paths extending through the one or more intermediate nodes; wherein the one or moreintermediate nodes are configured to dynamically implement at least one of fronthaul multiplexing functionality and fronthaul gateway functionality.

[0053] Example 2 includes the network system of Example 1, wherein the fronthaul gateway functionality is configured to convert communication protocols between the one or more radio units and the one or more core networks.

[0054] Example 3 includes the network system of any of Examples 1-2, wherein the fronthaul multiplexing functionality is configured to dynamically associate bandwidth with at least one path in the one or more paths based on usage of the one or more paths extending through the one or more intermediate nodes.

[0055] Example 4 includes the network system of any of Examples 1-3, further comprising a system manager configured to execute a management function that dynamically configures the fronthaul gateway functionality and the fronthaul multiplexing functionality through a management plane.

[0056] Example 5 includes the network system of Example 4, wherein the system manager is configured to implement at least one of the fronthaul multiplexing functionality based on expected usage of the one or more paths and the fronthaul gateway functionality based on differences in protocol between the one or more radio units and the one or more core networks.

[0057] Example 6 includes the network system of any of Examples 1-5, wherein the one or more intermediate nodes comprises a protocol sensor configured to sense communication protocols in communication received through the one or more intermediate nodes.

[0058] Example 7 includes the network system of Example 6, wherein the one or more intermediate nodes implements the fronthaul gateway functionality to convert the communication protocols based on the sensed communication protocols.

[0059] Example 8 includes the network system of any of Examples 1-7, wherein the one or more intermediate nodes are configured to measure at least one of bandwidth usage of the one or more paths and headroom of the one or more intermediate nodes.

[0060] Example 9 includes the network system of Example 8, wherein the one or more intermediate nodes implement the fronthaul multiplexing functionality to adjust the bandwidth usage of the one or more paths based on at least one of the bandwidthusage of the one or more paths and the headroom of the one or more intermediate nodes.

[0061] Example 10 includes a method comprising: transmitting data between one or more radio units and one or more core networks through one or more intermediate nodes in a communication network; implementing at least one of fronthaul multiplexing functionality and fronthaul gateway functionality in at least one intermediate node in the one or more intermediate nodes; and using at least one of the fronthaul multiplexing functionality and the fronthaul gateway functionality to control transmission of the data between the one or more radio units and the one or more core networks along one or more paths in the communication network.

[0062] Example 11 includes the method of Example 10, further comprising using the fronthaul gateway functionality to convert communication protocols between the one or more radio units and the one or more core networks.

[0063] Example 12 includes the method of any of Examples 10-11, using the fronthaul multiplexing functionality to dynamically associate bandwidth with at least one path in the one or more paths based on usage of the one or more paths extending through the one or more intermediate nodes in the communication network.

[0064] Example 13 includes the method of any of Examples 10-12, further comprising executing a management function that dynamically configures the fronthaul gateway functionality and fronthaul multiplexer functionality through a management plane.

[0065] Example 14 includes the method of Example 13, further comprising using the management function to direct at least one of the fronthaul multiplexer functionality based on expected usage of the one or more paths and the fronthaul gateway functionality based on differences in protocol between the one or more radio units and the one or more core networks.

[0066] Example 15 includes the method of any of Examples 10-14, further comprising sensing communication protocols in communications received through the one or more intermediate nodes.

[0067] Example 16 includes the method of Example 15, further comprising using the fronthaul gateway functionality in the one or more intermediate nodes to convert the communication protocols based on the sensed communication protocols.

[0068] Example 17 includes the method of any of Examples 10-16, further comprising measuring at least one of bandwidth usage of the one or more paths and headroom of the one or more intermediate nodes.

[0069] Example 18 includes the method of Example 17, further comprising using the fronthaul multiplexing functionality to adjust the bandwidth usage of the one or more paths based on at least one of the bandwidth usage of the one or more paths and the headroom of the one or more intermediate nodes.

[0070] Example 19 includes a system comprising: one or more intemiediate nodes, wherein at least one intermediate node in the one or more intermediate nodes comprises a protocol sensor, and the at least one intermediate node is configured to monitor bandwidth usage of paths through the at least one intermediate node and headroom of the at least one intermediate node; one or more radio units configured to extend wireless communications from one or more core networks into a coverage area, wherein the one or more radio units communicate with the one or more core networks through one or more paths extending through the one or more intermediate nodes; and a system manager configured to execute a management function; wherein the system manager is configured to dynamically implement at least one of fronthaul multiplexing functionality and fronthaul gateway functionality through a management plane; and wherein the one or more intermediate nodes are configured to dynamically implement at least one of the fronthaul multiplexing functionality and the fronthaul gateway functionality through a configuration plane.

[0071] Example 20 includes the system of Example 19, wherein the fronthaul gateway functionality is configured to convert protocol differences between at least one radio unit in the one or more radio units and at least one core network in the one or more core networks, and the fronthaul multiplexing functionality is configured to adjust the bandwidth usage of the one or more paths based on at least one of the bandwidth usage of the one or more paths and the headroom of the one or more intermediate nodes.

[0072] Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement, which is calculated to achieve the same purpose, may be substituted for the specificembodiments shown. Therefore, it is manifestly intended that this invention be limited only by the claims and the equivalents thereof.

Claims

CLAIMSWhat is claimed is:

1. A network system comprising: one or more intermediate nodes; and one or more radio units configured to extend wireless communications from one or more core networks into a coverage area, wherein the one or more radio units communicate with the one or more core networks through one or more paths extending through the one or more intermediate nodes; wherein the one or more intermediate nodes are configured to dynamically implement at least one of fronthaul multiplexing functionality and fronthaul gateway functionality.

2. The network system of claim 1, wherein the fronthaul gateway functionality is configured to convert communication protocols between the one or more radio units and the one or more core networks.

3. The network system of claim 1, wherein the fronthaul multiplexing functionality is configured to dynamically associate bandwidth with at least one path in the one or more paths based on usage of the one or more paths extending through the one or more intermediate nodes.

4. The network system of claim 1, further comprising a system manager configured to execute a management function that dynamically configures the fronthaul gateway functionality and the fronthaul multiplexing functionality through a management plane.

5. The network system of claim 4, wherein the system manager is configured to implement at least one of the fronthaul multiplexing functionality based on expected usage of the one or more paths and the fronthaul gateway functionality based on differences in protocol between the one or more radio units and the one or more core networks.

6. The network system of claim 1, wherein the one or more intermediate nodes comprises a protocol sensor configured to sense communication protocols in communication received through the one or more intermediate nodes.

7. The network system of claim 6, wherein the one or more intermediate nodes implements the fronthaul gateway functionality to convert the communication protocols based on the sensed communication protocols.

8. The network system of claim 1, wherein the one or more intermediate nodes are configured to measure at least one of bandwidth usage of the one or more paths and headroom of the one or more intermediate nodes.

9. The network system of claim 8, wherein the one or more intermediate nodes implement the fronthaul multiplexing functionality to adjust the bandwidth usage of the one or more paths based on at least one of the bandwidth usage of the one or more paths and the headroom of the one or more intermediate nodes.

10. A method comprising: transmitting data between one or more radio units and one or more core networks through one or more intermediate nodes in a communication network; implementing at least one of fronthaul multiplexing functionality and fronthaul gateway functionality in at least one intermediate node in the one or more intermediate nodes; and using at least one of the fronthaul multiplexing functionality' and the fronthaul gateway functionality to control transmission of the data between the one or more radio units and the one or more core networks along one or more paths in the communication network.

11. The method of claim 10, further comprising using the fronthaul gateway functionality to convert communication protocols between the one or more radio units and the one or more core networks.

12. The method of claim 10, using the fronthaul multiplexing functionality to dynamically associate bandwidth with at least one path in the one or more paths based on usage of the one or more paths extending through the one or more intermediate nodes in the communication network.

13. The method of claim 10, further comprising executing a management function that dynamically configures the fronthaul gateway functionality and fronthaul multiplexer functionality through a management plane.

14. The method of claim 13, further comprising using the management function to direct at least one of the fronthaul multiplexer functionality based on expected usageof the one or more paths and the fronthaul gateway functionality based on differences in protocol between the one or more radio units and the one or more core networks.

15. The method of claim 10, further comprising sensing communication protocols in communications received through the one or more intermediate nodes.

16. The method of claim 15, further comprising using the fronthaul gateway functionality in the one or more intermediate nodes to convert the communication protocols based on the sensed communication protocols.

17. The method of claim 10, further comprising measuring at least one of bandwidth usage of the one or more paths and headroom of the one or more intermediate nodes.

18. The method of claim 17, further comprising using the fronthaul multiplexing functionality to adjust the bandwidth usage of the one or more paths based on at least one of the bandwidth usage of the one or more paths and the headroom of the one or more intermediate nodes.

19. A system comprising: one or more intermediate nodes, wherein at least one intermediate node in the one or more intermediate nodes comprises a protocol sensor, and the at least one intermediate node is configured to monitor bandwidth usage of paths through the at least one intermediate node and headroom of the at least one intermediate node; one or more radio units configured to extend wireless communications from one or more core networks into a coverage area, wherein the one or more radio units communicate with the one or more core networks through one or more paths extending through the one or more intermediate nodes; and a system manager configured to execute a management function; wherein the system manager is configured to dynamically implement at least one of fronthaul multiplexing functionality and fronthaul gateway functionality through a management plane; and wherein the one or more intermediate nodes are configured to dynamically implement at least one of the fronthaul multiplexing functionality and the fronthaul gateway functionality through a configuration plane.

20. The system of claim 19, wherein the fronthaul gateway functionality is configured to convert protocol differences between at least one radio unit in the one or more radio units and at least one core network in the one or more core networks, and the fronthaul multiplexing functionality is configured to adjust the bandwidth usage of the one or more paths based on at least one of the bandwidth usage of the one or more paths and the headroom of the one or more intermediate nodes.

Images