Multiple MNO resource agreement enforcement

A system enforces resource partitioning among MNOs by setting upper limits and dynamically managing resource allocation, addressing the lack of frameworks in O-RAN specifications to prevent overuse and maintain system integrity.

WO2026019932A1PCT designated stage Publication Date: 2026-01-22OUTDOOR WIRELESS NETWORKS LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/US2025/037926
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-07-16
Filing Date
2025-07-16
Publication Date
2026-01-22

AI Technical Summary

Technical Problem

Existing O-RAN specifications fail to provide frameworks for sharing and enforcing resource allocation among multiple mobile network operators (MNOs) in a shared radio unit (RU) configuration, leading to potential overuse and damage to system hardware.

Method used

Implement a system that monitors and enforces resource partitioning agreements among MNOs by using a neutral host to set upper limits and dynamically manage resource allocation, ensuring that each MNO's usage remains within agreed-upon boundaries, thereby preventing overprovisioning and protecting the shared system.

Benefits of technology

Ensures efficient and safe use of shared system resources by preventing overprovisioning, maintaining system performance, and allowing MNOs to onboard at different times without disrupting communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2025037926_22012026_PF_FP_ABST
    Figure US2025037926_22012026_PF_FP_ABST
Patent Text Reader

Abstract

Systems and methods for multiple MNO resource agreement enforcement are described herein. In certain embodiments, a system includes a network connected to a plurality of core networks, wherein each core network is managed by different mobile network operators, wherein the different mobile network operators partition resources of the network subject to a resource partitioning agreement. Further, the network includes one or more radio units, wherein the one or more radio units are configured to extend wireless communications from the plurality of core networks into a coverage area. Additionally, the network is configured to monitor usage of network resources by the different mobile network operators and enforce the resource partitioning agreement.
Need to check novelty before this filing date? Find Prior Art

Description

MULTIPLE MNO RESOURCE AGREEMENT ENFORCEMENTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Patent Application Serial No. 63 / 672,126 entitled “MULTIPLE MNO RESOURCE AGREEMENT ENFORCEMENT” 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 (ORAN-WG4.CUS.O- R003-V15.00) and O-RAN Alliance working group 4 management plane specification (ORAN-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 one or more radios. A radio transmits and / or receives data at one or more frequencies translated above baseband. The virtual baseband unit and radios are components of a communication system such as a cellular communication 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. For example, the connected MNOs may share the radio units within the shared cell provided by the neutral host.SUMMARY

[0005] Systems and methods for multiple MNO resource agreement enforcement are described herein. In certain embodiments, a system includes a network connected to a plurality of core networks, wherein each core network is managed by different mobile network operators, wherein the different mobile network operators partition resources of the network subject to a resource partitioning agreement. Further, the network includes one or more radio units, wherein the one or more radio units are configured to extend wireless communications from the plurality of core networks into a coverage area. Additionally, the network is configured to monitor usage of network resources by the different mobile network operators and enforce the resource partitioning agreement.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 multiple mobile network operators using a shared system according to an aspect of the present disclosure; and

[0009] FIG. 3 is a flowchart diagram of a method for enforcing resource agreements between multiple mobile network operators 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 O-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 O-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 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.

[0014] In some shared cell configurations, a neutral host may allocate or share resources of RUs amongst multiple mobile network operators (MNOs). For example, a neutral host may be a mobile network operator or a facility owner who owns, manages, or otherwise “hosts” the ORAN system used to extend coverage through RUs into a coverage area. The neutral host may allocate system resources for use by multiple MNOs, allowing the MNOs to operate carriers using their dedicated spectrum through the RUs of the neutral host system. How ever, for a shared RU, theORAN specification fails to specify frameworks for sharing and enforcing the sharing of resources through a shared RU. Thus, difficulties may arise if an MNO accidentally attempts to exceed the resources allocated to the MNO by the Neutral Host. For example, exceeding allocated resources may damage system hardware.

[0015] In certain embodiments, a shared system managed by a neutral host may enforce agreed-upon resource partitioning among multiple MNOs. For example, when an MNO agrees to use the system resources during the initial planning / deployment of a system provided by a neutral host, the MNO may provide the neutral host an upper limit of needed resources. Alternatively, the neutral host may define the upper limits based on public information describing spectrum ownership of the MNOs. Then, during the operation of the system, the MNO may dynamically modify the allocated resources as long as the allocated resources are within the previously established upper limits that were approved by a neutral host. Further, when initially deploying a system to be shared by multiple MNOs, the different MNOs may provide upper-limit boundaries to the neutral host. Whereupon the Neutral host can deploy a system capable of providing service to the different MNOs at the provided upper limits of allocated resources. When the system is established, each MNO may connect to the system when desired. Accordingly, the multiple MNOs are not required to onboard to the shared system at the same time as they can onboard at later and different times with little disruption to the communication through the cells of the shared system.

[0016] FIG. 1 is a block diagram illustrating an example of a communication system 100. In the example shown in FIG. 1, the communication sy stem 100 is implemented using an O-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, the 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 — 111-M (referenced herein generally as UE(s) 111) within the site at which wireless services is being provided.

[0017] 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 which wireless 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 1 11 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).

[0018] 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 5GNR gNB. In 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 / s witches 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.

[0019] In general, the communication system 100 is configured to provide wireless service to various items of user equipment (UEs) 111 (such as user equipment (UE) 111-1 and any quantify of optional user equipment (UE) 111-2 through optional user equipment (UE) 111-M). 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 111. Furthermore, it is also to be understood that 5GNR 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.

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

[0021] 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 / switches 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 ways of implementing a base station entity (for example, using a conventional baseband 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.

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

[0023] 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 application virtualization, 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 / switches 105, and RUs 107, and any of the specific features described here as being implemented thereby, can be implemented in other ways.

[0024] 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 network 117, the midhaul network, 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.

[0025] The RUs 107 may be deployed at a site to provide wireless coverage and capacity for one or more wireless netw ork 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, orother 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 wireless service is being provided is at least partially (and optionally entirely) indoors, but other alternatives are possible.

[0026] 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, mobile media device, mobile gaming device, laptop computer, vehicle-based computer, desktop computer, etc.

[0027] 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 beamforming schemes. For example, the CU 101, DUs 103, and RUs 107 can implement one or more of the 5G NR transmission modes. Moreover, the communication system 100 can be configured to support multiple air interfaces and / or to support multiple wireless operators.

[0028] In examples in 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 do vnlink user-plane messages to wirelessly transmit downlink radio frequency signals using a respective set of antennas for reception by UEs 111.

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

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

[0031] 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 the fronthaul 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 uphnk slot, the RU 107 generates uplink user-plane messages that include the baseband IQ data generated at that RU 107 for the various front-hauled RBs and antenna ports and communicates the uphnk user-plane messages northbound.

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

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

[0034] 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 acombined 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 bandw idth 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.

[0035] In additional embodiments, the system 100 may include a system manager 109 that communicates with the various components of the system 100 that are deployed within a system. The system manager 109 may function as a network management system that performs configuration management of the system components, fault management, performance management, resource provisioning, and software management. The system manager 109 may communicate the various components of the system 100 through ethemet connections, wireless communication links, and the like. The system manager 109 may allow a neutral host to manage the use of the components of the system 100 by one or more MNOs.

[0036] FIG. 2 is a block diagram illustrating a shared system 210 providing communications between multiple MNOs 240-1 - 240-N and multiple UEs 211-1 - 211-M. As described herein, the multiple MNOs 240-1 - 240-N may be referred to collectively and generally as MNO(s) 240. In a similar manner, the UEs 211-1 - 211- M may be referred to collectively and generally as UE(s) 211. Further, as used herein, an MNO 240 may refer to a wireless carrier, a cellular company, or other entity that provides wireless communications services. An MNO 240 may own or control communication infrastructure that delivers the wireless communications services through a core network, such as the core network 115 described above in connection with FIG. 1. The core networks 115 of multiple MNOs 240 may connect to the shared system 210 to extend their provided communication services throughout a venue 220. As used herein, a venue 220 may refer to a location (indoor, outdoor, or combination) where a system such as the system 100 described in FIG. 1 is deployed to extend coverage to multiple UEs 211 within the venue 220.

[0037] In certain embodiments, the shared system 210 is managed by a management system 230. The management system 230 may function similarly to the systemmanager 109 described above in connection with FIG. 1. In particular, the system manager 109 may manage certain aspects of the components in the shared system 210 that are used to extend wireless communication sen-ices from the MNOs 240 to the UEs 211 located within coverage areas associated with the venue.

[0038] Within the shared system 210, each of the MNOs 240 may be allocated resources for communication through the shared system 210 with UEs 211. For example, a first MNO 240-1 may be allocated a first particular bandwidth and / or transmission power through one or more RUs 107 in the shared system 210. Also, a second MNO 240-2 may be allocated a second particular bandwidth and / or transmission power through the one or more RUs 107. However, in some systems, the management system 230 or components within the shared system 210 may not be capable of enforcing the allocation of resources. When the management system 230 lacks the ability to enforce the allocations, resources may be overprovisioned to the MNOs 240. When resources are overprovisioned, multiple MNOs 240 may reserve more bandwidth through an RU 107 than the RU 107 can capably support, negatively affecting the ability of the RU 107 to support the provided communications. Also, multiple MNOs 240 may request more transmission power through the RU 107 than the RU 107 can support, which can cause an RU 107 to bum out or cause the RU 107 to impose performance limitations to prevent damage to the RU 107.

[0039] In certain embodiments, the shared system 210 may be equipped to enforce the allocation of resources to the MNOs 240 to prevent the overprovisioning of resources by the MNOs 240 using the shared system 210 from damaging or negatively affecting the performance of the shared system 210. In particular, the RUs 107, intermediate nodes / switches 105, the DU 103 (when included in the shared system 210), and the management system 230 may be able to monitor usage and enforce resource allocations to prevent the overprovisioning of resources from negatively affecting the operation of the shared system 210.

[0040] In some implementations, RUs 107 and intermediate nodes / switches 105 may store information about resource allocations for the different MNOs 240. For example, each MNO 240 may communicate through a defined portion of the spectrum that is owned by the MNO 240. Accordingly, an RU 107 or intermediate node / swdtch 105 may store information identifying the amount of bandwidth, transmission power, and other resources available for communication through the spectrum associatedwith a particular MNO. If an MNO attempts to provision resources through the RU 107 that exceed the allocation, the RU 107 or intermediate node / switch 105 may not apply the requested resource provision. In some implementations, the RU 107 may provision resources for the MNO up to, but not exceeding, the requested provision, or the RU 107 may not apply any provisions in response to the request. Additionally, the RU 107 or intermediate node / switch 105 that receives a request from an MNO 240 that exceeds the allocated resources for the MNO 240 may send an alert to. notify, or report the request to the management system 230 or other computing device associated with the neutral host that manages the shared system 210. Also, the RU 107 or intermediate node / switch 105 may report the request to the MNO 240 associated with the request. The neutral host organization may then use the information about requests that exceed allocated resources to improve the performance of the shared system 210. For example, the neutral host may alter the allocation of resources or add more HW resources to the shared system 210 to increase the available resources within the shared system 210. Additionally, if the MNO 240 determines that a determination about a resource request exceeding upper limits is in error, the MNO can attempt to fix and re-apply the desired configuration.

[0041] In further embodiments, ensuring that the shared system 210 has enough resources available for the MNOs 240 to communicate with the UEs 211 may help avoid the overprovisioning of resources and the enforcement of resource allocations. To ensure that enough resources are available, during initial planning and deployment of the shared system 210, the neutral host implementing the shared system 210 within the venue may communicate with the MNOs 240 that will connect their core networks 115 to the shared system 210 to identify an upper limit of the available resources that an MNO 240 might need to be provisioned to communicate with UEs 211 through the shared system 210. The upper limit may be determined in any manner, but the upper limit may represent the largest amount of resources that an MNO 240 may need to be provisioned at any time through an RU 107. The upper limit for an MNO 240 may be a system-wide upper limit, an RU-specific upper limit, or other type of upper limit. For example, an MNO 240 may identify the highest expected transmission power and bandwidth that an MNO 240 might need through the shared system 210 or through an RU 107 in the shared system 210. With information on the upper limits of the various MNOs 240 in communication with the shared system 210, a neutral host may designthe shared system 210 to provision resources for at least the upper limits determined by the MNOs 240 and provided to the neutral host. The management system 230 and components of the shared system 210 may use the provided upper limits as resource allocations for the MNOs 240.

[0042] In additional embodiments, where the shared system 210 uses the upper limits as resource allocations for the MNOs 240, the shared system 210 may dynamically provision the available resources for communications for the MNOs 240. For example, the shared system 210 may assume that each MNO 240 will not attempt to provision resources that exceed the defined upper limit. As there are adequate resources for the upper limit of the connected MNOs 240, the shared system 210 may dynamically modify the provisioning of resources to meet the requests of the MNOs 240 connected to the shared system 210.

[0043] In some systems specified by the ORAN framework, neutral hosts may onboard multiple MNOs at the same time. However, onboarding multiple MNOs at the same time may be difficult. Accordingly, in embodiments described herein, the neutral host may use the upper limits to plan the network deployment and identify the bill of materials for implementing the shared system 210. Then, with the available resources of the shared system 210 meeting the needs of the upper limits of the potential MNOs 240. the MNOs 240 need not be onboarded at the same time. For example, the MNOs 240 may be onboarded when a particular MNO 240 is ready to connect to the shared system 210.

[0044] FIG. 3 is a flow diagram of a method 300 for enforcing resource partitioning agreements of a network between multiple mobile network operators. The method 300 proceeds at 301, where a request for partition of network resources in a network comprising a plurality of radio units is received, wherein the request is for communication from at least one core network in a plurality of core networks, wherein the at least one core network is associated with a mobile network operator in a plurality of mobile network operators. Also, the method 300 proceeds at 303, where whether partitioned resources for the mobile network operator satisfy a resource partitioning agreement after receiving the request for partitioning is determined.Moreover, the method 300 proceeds at 305, where the resource partitioning agreement is enforced when the partitioned resources do not satisfy the resource partitioning agreement.Example Embodiments

[0045] Example 1 includes a system comprising: a network connected to a plurality7of core networks, wherein each core network is managed by different mobile network operators, wherein the different mobile network operators partition resources of the network subject to a resource partitioning agreement, wherein the network comprises: one or more radio units, wherein the one or more radio units are configured to extend wireless communications from the plurality of core networks into a coverage area; wherein the network is configured to monitor usage of network resources by the different mobile network operators and enforce the resource partitioning agreement.

[0046] Example 2 includes the system of Example 1, wherein a radio unit in the one or more radio units is configured to monitor the usage of radio unit resources by the different mobile network operators and enforce the resource partitioning agreement, wherein the radio unit is further configured to: monitor one or more resource requests for the radio unit by a mobile network operator in the different mobile network operators; determine whether the one or more resource requests cause the usage of the radio unit resources to exceed a resource allocation for the mobile network operator according to the resource partitioning agreement; and block the one or more resource requests for the mobile network operator when the one or more resource requests causes the usage of the radio unit resources to exceed the resource allocation.

[0047] Example 3 includes the system of Example 2, wherein the radio unit is further configured to alert at least one of a neutral host and an associated mobile network operator in the different mobile network operators when the one or more resource requests causes the usage of the radio unit resources to exceed the resource allocation, wherein the neutral host manages the network.

[0048] Example 4 includes the system of any of Examples 2-3, wherein the radio unit in the one or more radio units monitors the usage of the radio unit resources by identifying the usage of the radio unit resources in a portion of spectrum managed by the mobile network operator.

[0049] Example 5 includes the system of any of Examples 1-4, wherein the network further comprises one or more intermediate nodes in the network, wherein an intermediate node in the one or more intermediate nodes is configured to monitor theusage of the network resources by the different mobile network operators and enforce the resource partitioning agreement.

[0050] Example 6 includes the system of any of Examples 1-5, wherein the resource partitioning agreement identifies upper limits of network resource usage for the different mobile network operators.

[0051] Example 7 includes the system of Example 6, wherein the network allows the different mobile network operators to dynamically modify partitioning of the network resources when the partitioning is below the upper limits.

[0052] Example 8 includes the system of any of Examples 6-7, wherein the resource partitioning agreement is established before the plurality of core networks are connected to the network, and the plurality of core networks connect to the network at different times.

[0053] Example 9 includes a method comprising: receiving a request for partitioning of network resources in a network comprising a plurality of radio units, wherein the request is for communications from at least one core network in a plurality of core networks, wherein the at least one core network is associated with a mobile network operator in a plurality of mobile network operators; determining whether partitioned resources for the mobile network operator satisfies a resource partitioning agreement after receiving the request for the partitioning of the network resources; and when the partitioned resources do not satisfy the resource partitioning agreement, enforcing the resource partitioning agreement.

[0054] Example 10 includes the method of Example 9, wherein determining whether the partitioned resources for the mobile network operator satisfies the resource partitioning agreement comprises determining whether the partitioned resources exceed an upper limit for the mobile network operator defined in the resource partitioning agreement.

[0055] Example 11 includes the method of Example 10, wherein the resource partitioning agreement defines an upper limit for each radio unit in the plurality' of radio units.

[0056] Example 12 includes the method of any of Examples 10-11. further comprising allowing the mobile network operator to dynamically modify thepartitioning of the network resources when the partitioning of the network resources is below the upper limit for the mobile network operator.

[0057] Example 13 includes the method of any of Examples 9-12, wherein at least one radio unit in the plurality of radio units determines whether the partitioned resources satisfy the resource partitioning agreement.

[0058] Example 14 includes the method of any of Examples 9-13, wherein enforcing the resource partitioning agreement comprises blocking the request for the partitioning of the network resources.

[0059] Example 15 includes the method of any of Examples 9-14, wherein enforcing the resource partitioning agreement comprises notifying at least one of a neutral host and the mobile network operator associated with the request that does not satisfy the resource partitioning agreement, wherein the neutral host manages the network.

[0060] Example 16 includes the method of any of Examples 9-15, wherein the partitioned resources for the mobile network operator comprises usage of the network resources in a portion of spectrum managed by the mobile network operator.

[0061] Example 17 includes the method of any of Examples 9-16, wherein the network comprise one or more intermediate nodes, wherein an intermediate node in the one or more intermediate nodes determines whether the partitioned resources satisfy the resource partitioning agreement.

[0062] Example 18 includes the method of any of Examples 9-17, further comprising: establishing the resource partitioning agreement before the plurality of core networks connect to the network, wherein the plurality of core networks connect to the network at different times.

[0063] Example 19 includes a system comprising: a network connected to a plurality of core networks, wherein each core network is managed by different mobile network operators, wherein the different mobile network operators partition the resources of the network subject to a resource partitioning agreement, wherein the network comprises: one or more radio units, wherein the one or more radio units are configured to extend wireless communications from the plurality of core networks into a coverage area; wherein the network is configured to monitor usage of netw ork resources by the different mobile network operators and enforce the resource partitioning agreement; wherein the resource partitioning agreement establishes upperlimits of network resource usage for the different mobile network operators, and the network allows the different mobile network operators to dynamically modify partitioning of the network resources when resultant partitions are below the upper limits.

[0064] Example 20 includes the system of Example 19, wherein a radio unit in the one or more radio units is configured to monitor usage of radio unit resources by the different mobile network operators and enforce the resource partitioning agreement, wherein the radio unit is further configured to: monitor resource requests for a radio unit by a mobile network operator in the different mobile network operators; determine whether the resource requests cause usage of radio unit resources to exceed a resource allocation for the mobile network operator according to the resource partitioning agreement; and block the resource request for the mobile network operator when the resource request causes the usage of radio unit resources to exceed the resource allocation.

[0065] 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 specific embodiments shown. Therefore, it is manifestly intended that this invention be limited only by the claims and the equivalents thereof.

Claims

1. CLAIMSWhat is claimed is:

1. A system comprising: a network connected to a plurality of core networks, wherein each core network is managed by different mobile network operators, wherein the different mobile network operators partition resources of the network subject to a resource partitioning agreement, wherein the network comprises: one or more radio units, wherein the one or more radio units are configured to extend wireless communications from the plurality of core networks into a coverage area; wherein the network is configured to monitor usage of network resources by the different mobile network operators and enforce the resource partitioning agreement.

2. The system of claim 1, wherein a radio unit in the one or more radio units is configured to monitor the usage of radio unit resources by the different mobile network operators and enforce the resource partitioning agreement, wherein the radio unit is further configured to: monitor one or more resource requests for the radio unit by a mobile network operator in the different mobile network operators; determine whether the one or more resource requests cause the usage of the radio unit resources to exceed a resource allocation for the mobile network operator according to the resource partitioning agreement; and block the one or more resource requests for the mobile network operator when the one or more resource requests causes the usage of the radio unit resources to exceed the resource allocation.

3. The system of claim 2, wherein the radio unit is further configured to alert at least one of a neutral host and an associated mobile network operator in the different mobile network operators when the one or more resource requests causes the usage of the radio unit resources to exceed the resource allocation, wherein the neutral host manages the network.

4. The system of claim 2, wherein the radio unit in the one or more radio units monitors the usage of the radio unit resources by identifying the usage of the radio unit resources in a portion of spectrum managed by the mobile network operator.

5. The system of claim 1, wherein the network further comprises one or more intermediate nodes in the network, wherein an intermediate node in the one or more intermediate nodes is configured to monitor the usage of the network resources by the different mobile network operators and enforce the resource partitioning agreement.

6. The system of claim 1, wherein the resource partitioning agreement identifies upper limits of network resource usage for the different mobile network operators.

7. The system of claim 6, wherein the network allows the different mobile network operators to dynamically modify partitioning of the network resources when the partitioning is below the upper limits.

8. The system of claim 6, wherein the resource partitioning agreement is established before the plurality of core networks are connected to the network, and the plurality of core networks connect to the network at different times.

9. A method comprising: receiving a request for partitioning of network resources in a network comprising a plurality of radio units, wherein the request is for communications from at least one core network in a plurality of core networks, wherein the at least one core network is associated with a mobile network operator in a plurality of mobile netw ork operators; determining whether partitioned resources for the mobile network operator satisfies a resource partitioning agreement after receiving the request for the partitioning of the network resources; and when the partitioned resources do not satisfy the resource partitioning agreement, enforcing the resource partitioning agreement.

10. The method of claim 9, wherein determining whether the partitioned resources for the mobile netw ork operator satisfies the resource partitioning agreement comprises determining whether the partitioned resources exceed an upper limit for the mobile network operator defined in the resource partitioning agreement.

11. The method of claim 10, wherein the resource partitioning agreement defines an upper limit for each radio unit in the plurality of radio units.

12. The method of claim 10, further comprising allowing the mobile network operator to dynamically modify the partitioning of the network resources when the partitioning of the network resources is below the upper limit for the mobile network operator.

13. The method of claim 9, wherein at least one radio unit in the plurality of radio units determines whether the partitioned resources satisfy the resource partitioning agreement.

14. The method of claim 9, wherein enforcing the resource partitioning agreement comprises blocking the request for the partitioning of the network resources.

15. The method of claim 9, wherein enforcing the resource partitioning agreement comprises notify ing at least one of a neutral host and the mobile network operator associated with the request that does not satisfy the resource partitioning agreement, wherein the neutral host manages the network.

16. The method of claim 9, wherein the partitioned resources for the mobile network operator comprises usage of the network resources in a portion of spectrum managed by the mobile network operator.

17. The method of claim 9, wherein the network comprise one or more intermediate nodes, wherein an intermediate node in the one or more intermediate nodes determines whether the partitioned resources satisfy the resource partitioning agreement.

18. The method of claim 9, further comprising: establishing the resource partitioning agreement before the plurality of core networks connect to the network, wherein the plurality of core networks connect to the network at different times.

19. A system comprising: a network connected to a plurality of core networks, wherein each core network is managed by different mobile network operators, wherein the differentmobile network operators partition the resources of the network subject to a resource partitioning agreement, wherein the network comprises: one or more radio units, wherein the one or more radio units are configured to extend wireless communications from the plurality of core networks into a coverage area; wherein the network is configured to monitor usage of network resources by the different mobile network operators and enforce the resource partitioning agreement; wherein the resource partitioning agreement establishes upper limits of network resource usage for the different mobile network operators, and the network allows the different mobile network operators to dynamically modify partitioning of the network resources when resultant partitions are below the upper limits.

20. The system of claim 19, wherein a radio unit in the one or more radio units is configured to monitor usage of radio unit resources by the different mobile network operators and enforce the resource partitioning agreement, wherein the radio unit is further configured to: monitor resource requests for a radio unit by a mobile network operator in the different mobile network operators; determine whether the resource requests cause usage of radio unit resources to exceed a resource allocation for the mobile network operator according to the resource partitioning agreement; and block the resource request for the mobile network operator when the resource request causes the usage of radio unit resources to exceed the resource allocation.

Citation Information

Patent Citations

  • Flexible network sharing

    US20130303114A1

  • Resource allocation amongst parties sharing the same radio access network

    US20160044702A1

  • System and method for network control

    US20160249353A1

  • Partitioning radio resources to enable neutral host operation for a radio access network

    US20230021194A1

  • Intent based automation for partitioned radio systems

    WO2022258813A1