System and method for securely hosting multiple network operators in a shared spectrum access system in a single virtual base station environment

Abstract

A virtual base station capable of hosting multiple network operators and / or private networks in a single computing environment. The virtual base station includes a plurality of virtual baseband processors configured to communicate with the plurality of mobile network operators, a monitor module, a fronthaul network interface configured to connect to one or more remote units, and a Key Performance Indicator (KPI) coordinator module connected to the monitor module and the one or more virtual baseband processors. The base station can have one or more Citizens Broadband Radio Service (CBRS) daemons to act as agents to obtain grants for CBRS channels and allocate the CBRS channels to the mobile network operators.

Description

TECHNICAL FIELD

[0001] The present invention relates to wireless systems and, in particular, to a virtual base station that can host multiple operators in the same computing environment, in a neutral host deployment. BACKGROUND

[0002] The advent of virtual base stations implemented purely in software provides an opportunity to host multiple network operators on a single wireless communication infrastructure. Hosting multiple network operators in a single computing environment presents several challenges. First, the computing environment must be secure enough so that a given network operator is not vulnerable to hacking or denial of service attacks. Second, the entire base station - from the computing environment hosting the virtual eNodeBs (Evolved Node Bs) and / or gNodeBs (next generation Node Bs) to the remote radio units - must not be subject to interference or blocking, as interference or blocking can cause an increase in activity within one network operator that can impact the allocation of computing, network, or radio resources to another network operator. Third, a neutral host hosting the virtual base station must be able to assess the performance of the system to provide each network operator with appropriate service and be able to provide each network operator with appropriate service without any one network operator being impacted by the presence of another network operator. Fourth, the advent of dedicated networks and shared spectrum access systems presents additional challenges, as the base station and computing environment must be able to cope with various grant, grant revocation, and channel switching scenarios in which a given network operator or dedicated network can change shared spectrum access channels without impacting any other network operator or dedicated network.

[0003] Accordingly, what is needed is a system and method for hosting eNodeBs / gNodeBs (one eNodeB / gNodeB per network operator or dedicated network) in a secure environment that provides unimpeded access to computing, network, and radio resources and to multiple network operators and is able to dynamically respond to changes in available shared spectrum access channels. SUMMARY

[0004] A method for configuring and operating a virtual base station hosting multiple network operators in a shared spectrum access system is disclosed, comprising:

[0005] instantiating, by a processor of a virtual base station, a plurality of baseband processors for the virtual base station, each baseband processor corresponding to a different one of a plurality of network operators, each baseband processor having one or more microcell group processors, wherein each microcell group processor has a plurality of band-specific microcell processors, wherein each of the plurality of baseband processors operates independently of any of the other ones of the plurality of baseband processors;

[0006] allocating, by the processor, a different plurality of shared spectrum access channels to each of the plurality of baseband processors of the virtual base station;

[0007] receiving an assignment of one or more of the plurality of shared spectrum access channels corresponding to each baseband processor;

[0008] allocating, by each of the plurality of baseband processors independently, each of the different plurality of shared spectrum access channels to a band-specific microcell processor of the corresponding one of the plurality of baseband processors of the virtual base station.

[0009] further, configuring each band-specific microcell processor assigned an assigned shared spectrum access channel to be in an active state; and configuring each band-specific microcell processor not assigned an assigned shared spectrum access channel to be in a locked state.

[0010] further, obtaining operator-specific information corresponding to each of the plurality of network operators; and configuring each of the plurality of baseband processors using the operator-specific information corresponding to the network operator of the baseband processor.

[0011] further, the operator-specific information includes licensed band information; and Citizens Broadband Radio Service (CBRS) priority access license information.

[0012] further, configuring each of a plurality of remote units to operate on a corresponding assigned shared spectrum access channel.

[0013] further, connecting each band-specific microcell processor in the active state to a fronthaul interface; and connecting each of the plurality of remote units to the fronthaul interface.

[0014] further, the step of connecting each band-specific microcell processor in the active state to a fronthaul interface includes connecting each band-specific microcell processor in the active state to a Common Public Radio Interface (CPRI) fronthaul interface.

[0015] Furthermore, the step of connecting each active band-specific microcell processor to the CPRI fronthaul interface includes connecting each active band-specific microcell processor to a CPRI fronthaul interface direct memory access (DMA) buffer.

[0016] Furthermore, the step of connecting each active band-specific microprocessor to the fronthaul interface includes connecting each active band-specific microprocessor to an Ethernet router.

[0017] Further, receiving a revocation of authorization corresponding to a revocation shared spectrum access channel among the plurality of authorized shared spectrum access channels, the revocation shared spectrum access channel corresponding to a revocation remote unit; and

[0018] A command is issued to the revocation remote unit to shut down a radio corresponding to the revoked shared spectrum access channel.

[0019] Furthermore, it also includes disconnecting the active band-specific microcell processor from any UE or fronthaul interface.

[0020] Furthermore, this includes switching the active band-specific microcell processor corresponding to the revocation of the shared spectrum access channel to a locked state.

[0021] Furthermore, including:

[0022] Issue an authorization request to access an unused shared spectrum access channel;

[0023] Receive an authorization to grant the unused shared spectrum access channel, such that the unused shared spectrum access channel now becomes a newly authorized shared spectrum access channel;

[0024] Switch the frequency band-specific micro-unit processor corresponding to the newly licensed shared spectrum access channel to an active state;

[0025] A command is issued to the revocation remote unit to activate a radio corresponding to the newly licensed shared spectrum access channel; and

[0026] The band-specific microcell processor corresponding to the newly licensed shared spectrum access channel is connected to the fronthaul interface.

[0027] Furthermore, the step of configuring each of the plurality of remote units to operate on its corresponding licensed shared spectrum access channel includes configuring one or more of the plurality of remote units to perform low physical (PHY) layer functions of the licensed shared spectrum access channel.

[0028] Further, the step of configuring one or more of the plurality of remote units to perform low physical (PHY) level functions includes configuring one or more of the plurality of remote units to perform low physical (PHY) level functions according to a split option 7-2x.

[0029] Further, the step of configuring each of the plurality of remote units to operate its corresponding licensed shared access channel includes configuring one or more of the plurality of remote units to operate as a gNodeB distributed unit.

[0030] The present application also discloses a computer system comprising a processor and a memory having software which, when executed, implements a virtual base station configured to perform any of the above methods.

[0031] The present application also discloses a non-transitory computer readable memory with encoded instructions which, when executed by one or more processors, cause the one or more processors to implement any of the above methods.

[0032] The present application discloses a method for hosting a plurality of network operators in a single computing environment, comprising:

[0033] allocating an operator-specific plurality of shared spectrum access channels to each of a plurality of baseband processors of a virtual base station, each of the plurality of baseband processors corresponding to one of the plurality of network operators, the operator-specific plurality of shared spectrum access channels having a required subset of shared spectrum access channels and a backup subset of shared spectrum access channels;

[0034] requesting, by each baseband processor of the virtual base station, an access grant for its corresponding required subset of shared spectrum access channels;

[0035] receiving a reply access grant for each required subset of shared spectrum access channels;

[0036] receiving, by a first baseband processor of the virtual base station, a revoked shared spectrum access channel corresponding to one of the required subset of shared spectrum access channels; and

[0037] requesting, by the first baseband processor of the virtual base station, an access grant for its corresponding backup subset of shared spectrum access channels.

[0038] The present application also discloses a computer system comprising a processor and a memory having software which, when executed, implements a virtual base station configured to perform the above methods.

[0039] The application also discloses a non-transitory computer-readable memory with encoded instructions that, when executed by one or more processors, cause the one or more processors to implement the method described above.

[0040] A method of configuring and operating a virtual base station is disclosed, comprising:

[0041] instantiating a baseband processor for the virtual base station, wherein the baseband processor has at least one or more microcell group processors, wherein each microcell group processor has a plurality of band-specific microcell processors;

[0042] allocating a plurality of shared spectrum access channels to the baseband processor;

[0043] receiving a grant of one of the plurality of shared spectrum access channels;

[0044] assigning each of the plurality of shared spectrum access channels to a respective band-specific microcell processor;

[0045] setting each band-specific microcell processor that is allocated a granted shared spectrum access channel to an active state, and setting any of the plurality of band-specific microcell processors that is not allocated a granted shared spectrum access channel to a locked state;

[0046] connecting a remote unit to the band-specific microcell processor that is allocated the granted shared spectrum access channel via a network interface;

[0047] in response to the remote unit being revoked, receiving a grant revocation corresponding to the granted shared spectrum access channel;

[0048] issuing an instruction to the remote unit to shut down a radio corresponding to the granted shared spectrum access channel for which the grant revocation has been received.

[0049] Further comprising: disconnecting any UE or fronthaul interface associated with the band-specific microcell processor.

[0050] Further comprising: switching the band-specific microcell processor corresponding to the revoked shared spectrum access channel from the active state to the locked state.

[0051] Further comprising:

[0052] issuing a grant request to request access to an unused shared spectrum access channel;

[0053] receiving a grant of the unused shared spectrum access channel, such that the unused shared spectrum access channel now becomes a newly granted shared spectrum access channel;

[0054] switching the band-specific microcell processor corresponding to the newly licensed shared spectrum access channel from a locked state to an active state;

[0055] issuing an instruction to the remote unit to turn on a radio corresponding to the newly licensed shared spectrum access channel; and

[0056] connecting, via the network interface, the band-specific microcell processor corresponding to the newly licensed shared spectrum access channel to the remote unit.

[0057] The present invention also discloses a computer system comprising a processor and a memory having software which, when executed, implements a virtual base station configured to perform any of the methods described above.

[0058] The present invention also discloses a non-transitory computer readable memory with encoded instructions which, when executed by one or more processors, cause the one or more processors to implement a method as described above.

[0059] One aspect of the present invention relates to a method for configuring and operating a virtual base station that carries multiple network operators. The method comprises instantiating a plurality of baseband processors, each baseband processor corresponding to one of the plurality of network operators, each baseband processor having one or more microcell group processors, wherein each microcell group processor has a plurality of band-specific microcell processors; allocating a distinct plurality of shared spectrum access channels to each of the plurality of baseband processors; receiving a license for one or more of the distinct plurality of shared spectrum access channels corresponding to each baseband processor; and assigning each shared spectrum access channel of the distinct plurality of shared spectrum access channels for each of the plurality of baseband processors to a respective band-specific microcell processor for each.

[0060] Another aspect of the disclosure relates to a non-transitory computer readable medium having encoded instructions that, when executed by one or more processors, cause the one or more processors to implement a process to configure and operate a virtual base station that carries multiple network operators. The process includes instantiating a plurality of baseband processors, each baseband processor corresponding to one of the multiple network operators, each baseband processor having one or more micro-cell group processors, where each micro-cell group processor has a plurality of band-specific micro-cell processors; allocating an explicit plurality of shared spectrum access channels to each of the plurality of baseband processors; receiving a grant of one or more shared spectrum access channels of the explicit plurality of shared spectrum access channels corresponding to each baseband processor; and assigning each shared spectrum access channel of the explicit plurality of shared spectrum access channels for each of the plurality of baseband processors to a respective band-specific micro-cell processor for each.

[0061] Another aspect of the disclosure relates to a server. The server has at least one network interface configured to communicate with a plurality of core networks and a plurality of remote units. The server also has at least one processor. The server also has a non-transitory computer readable medium having encoded instructions that, when executed by the one processor, cause the at least one processor to implement a process. The process includes routing, by the at least one network interface, a first communication between a first core network and the remote units, where the first communication uses a first set of communication channels allocated to the first core network. The process also includes routing, by the at least one network interface, a second communication between a second core network and the remote units, where the second communication uses a second set of communication channels allocated to the second core network. The process also includes receiving, by the at least one network interface, information that changes the first set of communication channels; and changing the first set of communication channels in accordance with the information.

[0062] Another aspect of the present disclosure relates to a method for hosting multiple network operators in a single computing environment. The method includes allocating an operator-specific plurality of shared spectrum access channels to each of a plurality of baseband processors, each of the plurality of baseband processors corresponding to one of the plurality of network operators, the operator-specific plurality of shared spectrum access channels having a required subset of shared spectrum access channels and a backup subset of shared spectrum access channels; requesting, by each baseband processor, an access grant for its corresponding required subset of shared spectrum access channels; receiving a reply access grant for each required subset of shared spectrum access channels; receiving, by a first baseband processor, a revoked shared spectrum access channel corresponding to one of the required subset of shared spectrum access channels; and requesting, by the first baseband processor, an access grant for its corresponding backup subset of shared spectrum access channels. BRIEF DESCRIPTION OF DRAWINGS

[0063] Figure 1A An exemplary virtual base station for hosting multiple network operators in accordance with the present disclosure is shown.

[0064] Figure 1B A fronthaul interface mapping module in accordance with the present disclosure is shown.

[0065] Figure 1C An exemplary computing environment in which the disclosed virtual base station can be deployed is shown.

[0066] Figure 2 An exemplary 5G (Fifth Generation) virtual base station configured to host multiple network operators in accordance with the present disclosure is shown.

[0067] Figure 3 An exemplary process for setting up and configuring a base station in accordance with the present disclosure is shown.

[0068] Figure 4 Multiple instantiated and configured virtual baseband processors are shown, each virtual baseband processor having a plurality of groups of microcells and constituent active and inactive microcells.

[0069] Figure 5A An exemplary deployment of virtual baseband processors is shown, each virtual baseband processor having a group of microcells connected to a plurality of remote units in a multicast daisy chain fashion.

[0070] Figure 5B An exemplary process for setting up and configuring a base station in accordance with the present disclosure is shown. Figure 5AExample deployments in which access to a "Citizens Broadband Radio Service" (CBRS) band in a "Citizens Broadband Radio Service Device" (CBSD) has been revoked. DETAILED DESCRIPTION

[0071] Figure 1A An example virtual base station 100 (hereafter "base station 100") for hosting multiple network operators in accordance with the present application is shown. The base station 100 is a virtual base station implemented in software in a computing environment. The computing environment has hardware components, including one or more processors and a non-transitory computer-readable memory, and when configured with appropriate software, the hardware components operate to implement the base station 100. In some embodiments, the software is stored in the non-transitory computer-readable memory of the computing environment. In other embodiments, the software is stored elsewhere but executed in the computing environment, for example, through an "Application Programing Interface" (API) provided by the computing environment.

[0072] In this example, base station 100 hosts two mobile network operators (A and B) that share a remote radio infrastructure. As used herein, the term "mobile network operator" can also include a private network, with the main difference being that a private network would not have licensed spectrum, but would instead rely on a shared spectrum access system. Base station 100 can have one or more virtual baseband processors 105A / B; a local monitor module 112A connected to baseband processor 105A; a CBRS-Daemon 114A connected to baseband processor 105A; a local monitor module 112B connected to baseband processor 105B; a CBRS-Daemon 114B connected to baseband processor 105B; a master monitor module 110; a "key performance indicator" (KPI) coordinator module 115; and a fronthaul interface 120 (also referred to herein as "fronthaul interface 120"). Connected to KPI coordinator module 115 are: a KPI processing module 125 for mobile network operator A; a KPI processing module 130 for mobile network operator B; a KPI processing module 135 for the system; a shared KPI processing module 140 corresponding to mobile network operator A that can be shared with other components within virtual base station 100; and a shared KPI processing module 145 corresponding to mobile network operator B that can be shared with other components within virtual base station 100. As shown, baseband processor 105A communicates with the core network 150 for the mobile network operator A over a dedicated SI interface 155, while baseband processor 105B communicates with the core network 160 for the mobile network operator B over a dedicated SI interface 165. Base station 100 is further connected to one or more remote units 170 over a fronthaul link 175.

[0073] In some embodiments, as shown, each virtual baseband processor 105A / B is a "Long-Term Evolution" (LTE) eNodeB. However, other virtual baseband processors are possible, such as a 5G New Radio (5G NR) gNodeB. As used herein, the term "baseband processor" can refer to a virtual eNodeB or a virtual gNodeB. If a gNodeB, the term "baseband processor" can refer to a gNodeB Central Unit (gNodeB CU), a gNodeB Distributed Unit (gNodeB DU), or a combined gNodeB CU+DU. It should be understood that such variations are possible and within the scope of the present application. If a baseband processor is an eNodeB or a gNodeB CU+DU combination, each can perform upper physical (PHY) level functions of a physical (PHY) split scheme, such as Split Option 7-2x specified by the "Open Access Radio Network (O-RAN) Alliance".

[0074] Each CBRS-Daemon 114A / B can be connected to a CBRS SAS (Spectrum Allocation System) 182 over an internet connection. Each CBRS-Daemon 114A / B can operate independently, and each CBRS-Daemon 114A / B can each be connected to a single Spectrum Allocation System (SAS) or to different Spectrum Allocation Systems (SASes). Alternatively, the base station 100 can have a single CBRS-Daemon that serves all of the baseband processors 105A / B. It should be understood that such variations are possible and within the scope of the present application.

[0075] The fronthaul interface 120 can comprise, for example, a Common Public Radio Interface (CPRI) that can be implemented on a Peripheral Component Interconnect Express (PCIe) board. Alternatively, the fronthaul link 175 can be an Ethernet connection, depending on the configuration of the base station 100. In this case, the communication between the fronthaul interface 120 and the remote unit 170 can be a packet-based enhanced Common Public Radio Interface (eCPRI) connection that can carry packetized eCPRI data representing TD (time domain) or FD (frequency domain) baseband signals between the fronthaul interface 120 and the remote unit, high-low physical layer split data (e.g., as specified by the O-RAN Alliance as split option 7-2x), or Fl interface data (if each “eNodeB” 105A / B is a gNodeB CU and each remote unit 170 has gNodeB DU functionality). It should be understood that various different implementations of a fronthaul link 175 and fronthaul interface 120 are possible and within the scope of the present application.

[0076] The master monitor module 110 sets up and configures the components within the base station 100 with the intent that eNodeBs of other network operators do not impair the functionality of each baseband processor 105A / B or cause underperformance as measured by each mobile network operator’s KPIs. As shown, the master monitor module 110 is connected to each baseband processor 105A / B (through their respective local monitor modules 112A / B), the KPI coordinator 115, and the fronthaul interface 120. The master monitor module 110 can further communicate with a neutral host 180 that operates the base station 100 through an internet connection. The communication between the master monitor module 110 and the neutral host 180 can take the form of a user interface or the like. In addition, the master monitor module 110 can grant the neutral host 180 access to the system KPI module 135 and the shared KPI modules 140 / 145 of each mobile network operator A / B. Depending on how the base station 100 is configured, the master monitor module 110 can or can not have access to the KPI processing modules 125 / 130 of each mobile network operator A / B.

[0077] The master monitor module 110 can also have an internet connection with the respective core networks 150 / 160 of the mobile network operators A / B. This can facilitate the transfer of configuration information, such as carrier and CBRS channel information, as well as KPI information through the KPI coordinator 115. Otherwise, or in addition, the KPI modules 125 / 130 can transfer KPI information directly to their respective mobile network operator core networks 150 / 160 through their respective baseband processors 105A / B. It should be understood that such variations are possible and within the scope of the present invention.

[0078] Each of the baseband processors 105A / B can include software modules that perform RRC (Radio Resource Control), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and a physical (PHY) component for the LTE (“Long Term Evolution”) or 5G protocol stack for the control and data planes. By employing container technology, the master monitor module 110 can instantiate and de-instantiate each baseband processor 105A / B independently of one another, along with the operating system of the computing environment of the base station 100. The master monitor module 110 can instantiate each local monitor module 112A / B, which can in turn configure and operate its corresponding baseband processor 105A / B (further described below). Each baseband processor 105A / B is connected to the fronthaul interface 120 through a bidirectional digital BB (baseband) I / Q (in-phase / quadrature) data connection 107. If a DL (download) signal, the BB I / Q data on the data connection 107 is subsequently merged by the fronthaul interface 120 into a CPRI signal (e.g., each BB signal is assigned to a CPRI antenna carrier), which is then transmitted to the digital representation of the BB (baseband) signal of each remote unit 170. Each remote unit 170 retrieves the intended signal from the CPRI data stream, up-converts the signal to an analog RF (radio frequency) signal, which is then amplified and transmitted through the antenna corresponding to the remote unit 170. If a UL (uplink) signal, the BB I / Q data on the data connection 107 is a digital representation of the down-converted RF signal that is detected by the antenna of the one or more remote units 170, which amplify and digitize the signal, format the signal according to the CPRI specification, and then transmit it to the fronthaul interface 120. The fronthaul interface 120 then identifies and extracts the BB I / Q data corresponding to the carrier assigned to the baseband processor 105A / B, which is then forwarded to the appropriate eNodeB through the data connection 107.

[0079] Figure 1B An exemplary fronthaul interface 120 is shown that includes a mapping module 185 that overlays a CPRI transport layer 195. The mapping module 185 acts as a coordinator between the baseband processors 105A / B and the CPRI transport layer 195, enabling different baseband processors 105A / B to operate independently of one another without affecting any other baseband processor. This can be particularly important because a baseband processor of one network operator can be rebooted, configured, or reconfigured (e.g., single microcell lock or activation) without affecting the operation of other network operators. This also enables the base station 100 to dynamically instantiate and add - or de-instantiate and remove - additional baseband processors.

[0080] The mapping module 185 within the fronthaul interface 120 can achieve this by mapping a given baseband processor 105A / B (through their respective bidirectional digital baseband I / Q data connections 107) to an allocated DMA (direct memory access) buffer 192, and then mapping the allocated DMA buffer 192 to a certain sample range within a given CPRI block in the CPRI transport layer 195. The CPRI connection is synchronous, and through the CPRI connection a fixed amount of data can be transmitted in a fixed time. The size of the CPRI transport block is fixed according to the bandwidth of the CPRI link (fronthaul link 175), which keeps the CPRI link at 100% utilization at all times. The mapping module 185 maps the samples corresponding to each baseband processor 105A / B to certain portions of each CPRI block. For example, the mapping module 185 can allocate the first bandwidth portion of the CPRI block (e.g. 1.4, 3, 5, 10, 15, or 20 MHz, as known how many component carriers correspond to the baseband processor 105A / B) for its data to baseband processor 105A. Even though a portion of the CPRI block can be blank, the entire block will be transmitted by the fronthaul interface 120 (with padding on the unused portions) at the appropriate time interval. The mapping module 185 can assign baseband processor 105B to a second bandwidth allocation (e.g. one of the bandwidths listed above, as applicable to the corresponding component carriers of the other baseband processor 105A / B) through a second DMA buffer 192 to a second portion of the CPRI block. The mapping module 185 can do this so that the CPRI block is used contiguously, as the allocated CPRI block for each eNodeB is appended to the CPRI block of the previous eNodeB. The mapping module 185 can likewise accommodate additional eNodeBs. For example, the host supervisor module 110 can instantiate two additional baseband processors 105C / D (not shown), and configure the fronthaul interface module 120 for the two new baseband processors 105C / D and their respective bandwidth requirements. Given the available space within the CPRI block and the bandwidth requirements of each additional baseband processor 105C / D, the mapping module can allocate the remaining bandwidth of the CPRI block to baseband processor 105C and baseband processor 105D through additional DMA buffers 192, which can result in padding the CPRI block. This would require the mapping module to allocate a new DMA buffer 192 for each new baseband processor 105C / D, and map the DMA buffer 192 to an allocated slot within the CPRI block in the CPRI transport layer 195.Next, the master supervisor module 110 can shut down baseband processors 105B and 105D and instruct the fronthaul interface 120 (and thus the mapping module 185) to remove these two baseband processors from the CPRI block, e.g., depending on the fluctuation in connectivity needs. Thus, the mapping module 185 can also do so - disconnect the corresponding DMA buffers 192 from the disconnected baseband processors 105B / D, leaving the corresponding parts of the CPRI block unused, so that the fronthaul interface module 120 can fill the unused data parts.

[0081] If a known baseband processor locks or otherwise shuts down a microcell, or if the master supervisor module 110 shuts down a given baseband processor, the CPRI block allocated to that microcell or the entire baseband processor can be available to the mapping module 185 for reallocation. For example, if a given baseband processor has locked or shut down a microcell, the mapping module 185 can reallocate the newly freed CPRI block to the same baseband processor or to another baseband processor, with the expectation of activating a new microcell. Alternatively, the mapping module 185 can reallocate the newly freed CPRI block to a new baseband processor.

[0082] Each baseband processor 105A / B can load and extract data asynchronously from its corresponding DMA buffer 192. The DMA buffer 192 can handle the synchronization of the loading / extracting data process to / from the CPRI transport layer 195.

[0083] The CPRI data can be in time domain I / Q or frequency domain I / Q format.

[0084] One advantage of the mapping module 185 is that it enables the removal and addition of baseband processors without interrupting the operation of other running baseband processors.

[0085] The KPI coordinator module 115 configures and maintains the KPI modules 125 / 130 / 135 / 140 / 145 according to the configuration information provided by the master monitor module 110. The KPI coordinator module 115 can control, for example, access to each of these KPI modules such that mobile network operator A can only access KPI modules 125 / 140 / 145, mobile network operator B can only access KPI modules 130 / 140 / 145, and the master monitor module 110 can only access KPI modules 135 / 140 / 145. In another example, the master monitor module 110 can access all of the KPI modules 125 / 130 / 135 / 140 / 145. The KPI coordinator module 115 can intercept or extract relevant data from each baseband processor 105A / B, or each KPI module can be directly connected to its corresponding baseband processor 105A / B. For example, KPI module 125 can be directly connected to baseband processor 105A, and as a purely virtual and software-implemented processor, baseband processor 105A can be configured to be instrumented such that relevant KPIs or their underlying data can be directly accessed by KPI module 125. It should be understood that such variations are possible and within the scope of the present application.

[0086] The KPI modules 125 / 130 can include proprietary code provided by the mobile network operators A / B and hosted as an agent in the computing environment of the base station 100. Each of the KPI modules 125 / 130 can intercept or extract data from the fronthaul interface 120 and use the data to measure its intended KPIs. All or some of the specific algorithms and implementation of KPI extraction and analysis for one mobile network operator can be hidden from the neutral host 180 and other mobile network operators. Further, the KPI modules 125 / 130 can be integrated into the respective baseband processors 105A / B. The KPI modules 125 / 130 can each provide data to the shared KPI processing modules 140 / 145, which can in turn provide reports or generate alerts to the KPI coordinator 115. Further, the master monitor module 110 can authorize the neutral host 180 access to the system KPI module 315 and the shared KPI modules 140 / 145 of each of the mobile network operators A / B. One example of this aspect can be the case where the KPI module 125 of mobile network A, using its proprietary KPI data and analysis, identifies an anomaly in a hardware component (e.g., an amplifier) of a given remote unit 170 and issues an alert to the neutral host 180 through the KPI coordinator 115. Thus, examples of shared KPIs can include hardware anomalies within the remote unit 170 or the fronthaul link 175. If a KPI module 125 / 130 measures a KPI or identifies an anomaly that it is configured to share with the system 100, the KPI module 125 / 130 can store this information in its respective shared KPI module 140 / 145 so that the information is available to the KPI coordinator 115. Examples of KPIs include those defined by 3GPP (Third Generation Partnership Project) in TS 32.450, such as "Evolved UTRAN (Universal Terrestrial Radio Access Network) Radio Access Bearer" (ERAB) accessibility, ERAB retainability, Internet Protocol (IP) throughput, IP delay, microcell availability and mobility, as well as proprietary KPIs.

[0087] The KPI module 125 / 130 can generate proprietary alarms for the mobile network operators A / B and generate and provide KPI data and reports that it can send periodically (e.g., every 15 minutes) to the mobile network operators A / B over a northbound interface (not shown). In one example, the KPI module 125 / 130 can easily extract and compile proprietary data for the mobile network operators A / B to process in their respective core networks 150 / 160 and perform minimal, if any, embedded analytics in the base station 100. It should be understood that such variations are possible and within the scope of the present application.

[0088] The system KPI processing module 135 can extract or receive data from each remote unit 170 regarding its health. Thus, each remote unit 170 and the front-haul interface 120 can be instrumented with embedded sensors and software components that monitor the functioning of the components and report anomalies to the system KPI processing module 135. In addition, the system KPI processing module 135 can compile data regarding the functioning of the computing environment that hosts the base station 10, such as the average and peak processing load for each thread corresponding to the software modules described herein.

[0089] The remote units 170 can include, for example, one or more conventional macro remote units, one or more DAS (Distributed Antenna Systems) and / or one or more TEKO TM systems provided by JMA Wireless TMCell Hubs. If the fronthaul link 175 is a CPRI link, then the remote units 170, regardless of their specific type, can have on-board processing such as (DL, out-of-sequence), DAC (digital to analog converter), up-conversion to a particular RF carrier frequency, signal combining from multiple CPRI antenna carriers to a single RF signal, and power amplification. For the UL, each remote unit 170 can include low noise amplification, filtering, down-conversion to baseband, ADC (analog to digital converter), and possibly a pooling function that can pool the known CPRI antenna carrier data with those of other remote units 170. In variations where the fronthaul link 175 uses an eCPRI connection to transport packetized time or frequency domain data, each remote unit 170 can have the circuitry and / or processing capability to unpacketize the DL data stream into a digital stream (which can then be processed into an analog RF signal) and to packetize the received digitized UL signal for transmission to the appropriate baseband processor 105A / B. In variations where the baseband processor 105A / B operates using a physical (PHY) layer split such as a 7-2x O-RAN split option, then each remote unit 170 can have the appropriate circuitry and / or processing capability to perform the low physical layer functions. In variations where one or more of the baseband processors 105A / B function as gNodeB CUs, then each remote unit 170 can have the appropriate circuitry and / or processing capability to perform 5G DU functions. In further variations where the fronthaul link 175 is an Ethernet connection, each remote unit 170 can have the capability to perform any combination of TD / FD eCPRI, 7-2x split, and 5G DU processing. It should be understood that such variations are possible and within the scope of the present application.

[0090] As Figure 1A shown in FIG. 1C, the remote units 170 can be arranged in a daisy chain configuration, or can be arranged in a hub or spoke configuration, or as a combination thereof.

[0091] The remote units 170 can be dispersed throughout a large site, such as a university campus or a sports stadium, so that the risk of interference between them is minimal. In addition to this variation, the locations of the remote units 170 can be such that any known remote unit 170 can experience the majority of traffic at any given time. In the sports stadium example, the first remote unit 170 (RU 1) can be deployed in a sports stadium bowl; while the third remote unit 170 (RU 3) can be deployed in a concourse. At any given time during an event, the majority of UE (user equipment) traffic can be in the parking lot, in the concourse, in the sports stadium bowl, again in the concourse, and again in the parking lot. In this case, it can be advantageous to treat all three remote units 170 as one microcell (they share one CPRI antenna carrier). In this example, a single virtual baseband processor 105 A can transmit DL data in a single CPRI antenna carrier to all three remote units 170 in a multicast mode. The scheduler within the baseband processor 105 A will thus allocate a different set of REs (resource elements) to each UE (user equipment) within the coverage area of any one of the remote units 170, while each remote unit 170 will receive the same DL CPRI antenna carrier. However, in the UL, each remote unit 170 will not receive the same signal, since each remote unit 170 will receive UL signals from a different set of UEs. In this case, each remote unit 170 can add its own CPRI antenna carrier data to that of its previous remote unit 170, due to the daisy chain structure and the fact that each UE is allocated a unique set of REs (resource elements). For example, RU 2 can add its UL CPRI antenna carrier data to that of RU 1, while RU 3 can add its UL CPRI antenna carrier data to the aggregate CPRI antenna carrier data from RU 2. A variety of different implementations for the aggregation are possible, and are within the scope of the application. For example, a simple addition of the time domain signals (e.g., all frequency windows within a given subframe of a single TTI (transmission time interval)) can be done in deployments where high signal to noise ratios are expected, such as in an indoor deployment. In addition, interference mitigation algorithms can be used to ensure reliable uplink channels in the presence of high co-channel activity.

[0092] The above exemplary embodiments are for an embodiment in which the fronthaul link 175 is a CPRI link and BB time domain data is communicated between the base station 100 and the remote unit 170. In another variation, the remote unit 170 can perform low level physical (PHY) functions that would otherwise be done by the baseband processor 105A / B. In this example of physical layer splitting, the fronthaul link 175 can be considered a midhaul link, and the term "fronthaul link" as used herein can also refer to a midhaul link. For example, the physical layer splitting can be done according to "7.2 Split" as described in 3GPP TR 38.816 vl.0.0, although other proposed physical layer splitting schemes are possible depending on the bandwidth available to the fronthaul link 175. In this example using the 7.2 split option, the data communicated over the fronthaul link 175 can be encapsulated data representing frequency domain data streams for PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), PDCCH (Physical Downlink Control Channel), and PDSCH (Physical Downlink Shared Channel) data for each UE connected to the remote unit 170, and the fronthaul interface 120 can be an Ethernet interface and / or router. In addition to this example, as described above, the remote units 170 in the daisy chain structure shown can add the UL data it receives to the UL data of the previous remote unit 170. Since the sum will be done in the frequency domain, this example has advantages. It should be understood that such variations are possible and within the scope of the present application.

[0093] In a variation to the virtual base station 100, the virtual baseband processors 105A / B can be gNodeB CUs, and the DUs can be embedded in the remote unit 170 through the gNodeB CUs. In this case, the data connection 107, the fronthaul interface 120, and the fronthaul link 175 can implement an Fl interface over Ethernet. It should be understood that such variations are possible and within the scope of the present application.

[0094] Figure 1CAn exemplary computing environment 101 in which a virtual base station 100 can be deployed is shown. The computing environment 101 includes a server 113, which can include one or more rack-mounted or blade servers, each of which can have multiple processor cores. The server 113 has one or more processor cores 117 that are connected to one or more storage devices 131. The server 113 is connected to the Internet 121 through an Internet connection 123 and a server network interface 127. The server 113 can also have a fronthaul network interface card 129. If the fronthaul is implemented according to the CPRI specification, the fronthaul network interface card 129 can be a PCIe board that has circuitry to convert digital signal data to CPRI format and CPRI format data to digital signal data for transmission over the fronthaul link 175. The server 113 can also have hardware accelerator components, such as FPGAs (field programmable gate arrays) that deploy on standard computer interface cards, using well-known IP (intellectual property) blocks, to perform specific high-speed computations as needed to process signals.

[0095] While the illustrated example shows the server 113 having two separate network interfaces 127 and 129, it should be understood that other implementations are possible. In another embodiment, a single network interface is provided for communicating with the Internet 121 and the remote unit 170. More generally, the server 113 has at least one network interface for communicating with the Internet 121 and the remote unit 170. The server 113 can communicate with a core network through the Internet 121. Thus, the server 113 can route communications between the core network and the remote unit as described herein. Such routing can include bidirectional communications or unidirectional communications. As described herein, routing of communications from a core network to the remote unit can include multicast communications.

[0096] Figure 2 A second exemplary virtual base station 200 according to the present application (hereafter "base station 200") is shown. The base station 200 is a virtual base station that is implemented in software in a computing environment (e.g., the computing environment 101 shown in FIG. 1). Figure 1C The computing environment has hardware components, including one or more processors and a non-transitory computer readable memory, that, when configured with appropriate software, operate to implement the base station 200. In some embodiments, the software is stored in the non-transitory computer readable memory of the computing environment. In other embodiments, the software is stored elsewhere but executed in the computing environment, e.g., through an "application programming interface" (API) provided by the computing environment.

[0097] The base station 200 includes a master monitor module 210, one or more DUs 205 (two DUs 205A / B are shown here, one for each mobile network operator). Connected to the KPI coordinator module 215 are a KPI processing module 225 for mobile network operator A, a KPI processing module 230 for mobile network operator B, a system KPI processing module 235, a KPI processing module 240 corresponding to mobile network operator A that can be shared with other components within the virtual base station 200, and a KPI processing module 245 corresponding to mobile network operator B that can be shared with other components within the virtual base station 200. Although not shown, the base station 200 can have local monitor modules corresponding to the DUs 205A / B similar to those of the base station 100, and CBRS-Daemons connected to the CUs 252A / B.

[0098] One difference between the base station 200 and the base station 100 is that there is a CU / DU (Central Unit / Distributed Unit) split within each virtual gNodeB, and the virtual CUs 252A / B can be hosted on computing infrastructure belonging to mobile network operators or private networks A and B, respectively. In other words, the CUs 252A / B can be deployed within the core networks 150 / 160 of the mobile network operators or private networks A and B, respectively. Thus, the CU 252A is connected to the DU 205A hosted in the computing environment of the base station 200 over an Fl interface 272. Similarly, the CU 252B is connected to the DU 205B hosted in the computing environment of the base station 200 over its own Fl interface 272. The Fl interface 272 can be implemented over an Ethernet connection established by the Ethernet interface 257. Each DU 205A / B can include a mix of pure software implementations executed on traditional processor hardware and dedicated hardware such as FPGAs and other hardware accelerators.

[0099] The base station 200 is connected to one or more remote units 270 over a fronthaul link 275 and a fronthaul network interface 220. As described above, the fronthaul network interface 220 can be substantially similar to the fronthaul network interface 220, including the CPRI implementation and the Ethernet-based “7.2 Split Option” variations. As discussed above with respect to the base station 100, the fronthaul link 275 can include a CPRI link or an Ethernet link, depending on the fronthaul architecture. The fronthaul implementations (e.g., CPRI, TD eCPRI, FD eCPRI, and 7-2x) and example daisy chain architectures (including uplink antenna carriers) of the remote units 270 apply to the base station 200 as well as the base station 100.

[0100] The remote units 270 can include, for example, one or more traditional macro remote units, one or more small micro cells, one or more DAS, and / or one or more TEKO Cell Hubs provided by JMA Wireless. In one variation, the remote units 270 can each have embedded low physical layer processing, in which case the fronthaul links 275 can instead be midhaul links, and the DUs 205A / B perform the upper physical layer processing. The specific partitioning of the physical layer can vary. As previously noted, it should be understood that such variations are possible and within the scope of the present application.

[0101] The master monitor module 210 sets and configures the components within the base station 200 with the intent that the base station 200 does not impair the functionality of each DU 205A / B or cause underperformance as measured by each mobile network operator’s KPIs. As shown, the master monitor module 210 is connected to each DU 205A / B, the KPI coordinator 215, and the fronthaul network interface 220. The master monitor module 210 can further communicate with the neutral host 180 that operates the base station 200. The communication between the master monitor module 210 and the neutral host 180 can take the form of a user interface or the like. In addition, the master monitor module 210 can authorize the neutral host 180 to access the system KPI module 235 and the respective shared KPI modules 240 / 255 of mobile network operators A / B. One example of this can be a situation where the KPI module 125 of mobile network A can identify an anomaly in a hardware component (e.g., an amplifier) of a given remote unit 170 / 270 using its proprietary KPI data and analysis, and issue an alert to the neutral host 180 through the KPI coordinator 115 / 215. Depending on how the base station 200 is configured, the master monitor module 210 can not have access to the respective KPI processing modules 225 / 230 of mobile network operators A and B.

[0102] The master monitor module 210 can also have an internet connection with the respective core networks 150 / 160 of the mobile network operators A / B. This can facilitate the transfer of configuration information, such as carrier and CBRS channel information, as well as KPI information from the KPI coordinator 215. Otherwise, or in addition, the KPI modules 225 / 230 can transfer KPI information directly to their respective mobile network operator core networks 150 / 160 through their respective DUs 205A / B. The coordinator module 215 and the KPI modules 225 / 230 / 235 / 240 / 245 can be substantially similar to the KPI modules 115 / 125 / 130 / 135 / 140 / 145 described above. It should be understood that such variations are possible and within the scope of the present application.

[0103] Each software-based component within the base station 100 / 200 can be deployed within their computing environment using container technology, which allows the components to operate independently and makes it possible to instantiate / destroy components according to instructions issued by the master supervisor module 110 / 210.

[0104] Each component or module within the base station 100 / 200 can include machine- readable instructions encoded within one or more non-transitory memory devices and executed on one or more processors that perform their respective functions. As used herein, the term "module" can refer to a set of machine-readable instructions encoded in a non-transitory memory that is executable by one or more processors to perform the functions specified for that module according to the present application. Each of the modules can be executed as one or more threads of execution, which can be executed by the one or more processors using container technology. As used herein, the term "non-transitory computer-readable memory" can refer to any tangible storage medium (as opposed to an electromagnetic or optical signal), and refers to the medium itself, not the data stored thereon (e.g., RAM vs. ROM). For example, a non-transitory medium can refer to an embedded, volatile memory that can need to be reloaded with appropriate machine-readable instructions after a periodic power-up, according to the instructions.

[0105] There are many possibilities for the non-transitory computer-readable memory. Some possibilities include: an SSD (solid state drive), an HD (hard disk), a CD (compact disc), a DVD (digital video disc), a BD (Blu-ray disc), a memory stick, or any appropriate combination thereof. In some embodiments, the non-transitory computer-readable medium is part of the computing environment 101. In some embodiments, the non-transitory computer-readable medium is separate from the computing environment 101.

[0106] Figure 3 An exemplary process 300 for instantiating and configuring an exemplary base station 100 / 200 according to the present application is shown. The process 300 can be performed by one or more processors associated with the base station 100 / 200 (hereinafter "the processor(s)"), as machine-readable instructions stored on a non-transitory memory and implemented as functional modules as described above. While the following discussion can occasionally refer to components within the base station 100, it should be understood that this can also apply to the base station 200. Furthermore, it should be understood that the discussion regarding the process 300 can apply to any combination of eNodeBs, gNodeBs (CU or CU+DU combination), or DUs within the base station 100 / 200.

[0107] In step 305, the processor executes instructions to instantiate the master monitor module 110 / 210 and perform a system discovery scan. In doing so, the operating system of the processor can employ container technology to instantiate the master monitor module 110 / 210 and other modules of the base station 100 / 200. In step 305, the processor executes instructions causing the master monitor module 110 / 210 to establish communication with each of the remote units 170 over the fronthaul interface 120 / 220 to obtain address, channel capacity, location, and power information for each remote unit 170 / 270. This can include establishing communication with each POI (point of interface) within the remote unit 170 / 270. In addition to step 305, the master monitor module 110 / 210 can create a database with the information obtained in the system discovery scan.

[0108] In step 310, the processor executes instructions causing the master monitor module 110 / 210 to establish communication with the core networks 150 / 160 of the network operators and the neutral host 180 and obtain mobile network operator configuration data, which can include licensed spectrum carrier parameters and KPI information from each of the mobile network operators, through their respective core networks 150 / 160. In addition, the master monitor module 110 / 210 can query the mobile network operators for any CBRS PAL (priority access license) numbers that the mobile network operators can have. The master monitor module 110 / 210 can also establish communication with any private networks that need to be deployed and supported by the base station 100 / 200. This can include the master monitor module 110 / 210 querying one or more private network servers for any CBRS PAL numbers or other network configuration information. The master monitor module 110 / 210 can load the appropriate obtained data into the database for later use in configuring the eNodeBs / gNodeBs / DUs and KPI coordinator module, respectively. The master monitor module 110 / 210 can allocate channels within the remote units 170 / 270 (e.g., POIs) corresponding to each mobile network operator’s licensed spectrum channels and load the appropriate information in the database to match the channels within the remote units 170 / 270 to each mobile network operator. The master monitor module 110 / 210 can further allocate CBRS channels to each mobile network operator and private network and load the appropriate information into the database.

[0109] While the following description refers to CBRS, it should be understood that the present application can be applied to any shared spectrum access system through which a base station can require access to one or more shared spectrum channels or bands.

[0110] In addition to step 310, the processor executes instructions to instantiate the baseband processors 105A / B (base station 100) or DUs 205A / B (base station 200), the local monitor modules 112A / B, and the CBRS-Daemons 114A / B. This can be done using container technology. Each mobile network operator and private network has its own baseband processor, local monitor module, and CBRS-Daemon, as well. The master monitor module 110 / 210 can map CPU and bus resources to each baseband processor 105A / B according to their respective capacity requirements.

[0111] In addition to step 310, the processor executes instructions to cause the monitor 110 to assign CBRS channels to each baseband processor 105A / B. The monitor 110 can also do this according to a pre-arranged priority order, where a given network operator A / B pays for a given number of CBRS channels according to the pre-arranged priority order, which can be in addition to any CBRS channels it can have a PAL number for. For example, as shown in Figure 5B The monitor 110 can assign CBRS channels 1-3 to baseband processor 105A and CBRS channels 4-6 to baseband processor 105B, as shown in

[0112] In step 315, each CBRS-Daemon 114A / B registers its remote units 170 / 270 with the CBRS SAS (spectrum allocation system) 182. In doing so, each CBRS-Daemon 114A / B acts as a domain proxy for the channels it assigns in each remote unit 170 / 270 to register each remote unit 170 / 270 as a CBSD. In Figure 5B In the example shown, CBRS-Daemon 114A will register CBRS channels 1-3 with SAS 182, and CBRS-Daemon 114B will register CBRS channels 4-6 with SAS 182. This can be done in an array, where each remote unit 170 / 270 is an element in the array, and the CBRS-Daemons 114A / B can specify that they will be responsible for in-group interference coordination. As part of the registration process, if the response from the mobile network operator corresponding to the CBRS-Daemon 114A / B (in step 310) indicates that the mobile network operator or private network has a PAL authorization, the CBRS-Daemon 114A / B indicates this in the registration process so that each CBSD is registered as being within the PPA (PAL protection area) and is therefore authorized to access a PAL backup CBRS channel.

[0113] In step 325, the processor executes instructions causing the CBRS-Daemon 114A / B serving its CBSDs to transmit a license request to the SAS. This license request can be in the form of an array for group requests, each single CBSD request within the array explicitly requesting the CBRS channel assigned to it by the master monitor module 110 / 210 in step 310. Depending on the number of mobile network operators and private networks and available computing resources in the computing environment of the base station 100 / 200, the master monitor module 110 / 210 can limit the number of CBRS channels the given CBRS-Daemon 114A / B can issue license requests for, which can be a subset of its CBRS channel assignment. The remaining subset of CBRS channels can be reserved for the given baseband processor to use in case of CBRS channel license revocation. Each license request in the array can correspond to a particular CBSD, and for each channel requested for each CBSD, each license request includes which channels are requested under PAL license and which channels are requested prior to GAA license. Each license request in the array can include a frequency range and a desired EIRP (Effective Isotropic Radiated Power) corresponding to each frequency range.

[0114] In addition to step 325, each CBRS-Daemon 114A / B receives a license grant from the SAS. For each CBSD, the license grant can include authorization for PAL backup channels and authorization for channels granted under GAA (General Authorized Access). Each channel grant can include a maximum EIRP. It is understood that the SAS is not guaranteed to grant access to each requested CBRS channel. The SAS can deny access to a given channel and can recommend an alternative channel. Each BRS-Daemon 114A / B can store information corresponding to the CBRS grant and related parameters locally for configuring its corresponding baseband processor 105A / B.

[0115] In step 340, the processor can execute instructions to cause each local monitor module 112A / B to configure its corresponding baseband processor 105A / B. In doing so, each local monitor module 112A / B can query the database for all information related to its corresponding mobile network operator or private network, such as: licensed spectrum carriers; assigned CBRS channels, whether or not access has been granted to a given CBRS channel in step 325; CBRS channels for which access has been granted in step 325 and their related parameters; addresses of POIs or remote unit channels; and any other relevant information obtained in step 310. Since it is necessary to maintain security and isolate the resources of each mobile network operator and private network from other resources, the master monitor module 110 / 210 can create a copy of the database for each local monitor 112A / B, where the copy contains only information related to that particular mobile network operator or private network. Each local monitor 112A / B configures its corresponding baseband processor 105A / B by provisioning a microcell for each licensed spectrum carrier and each assigned CBRS channel. In doing so, each local monitor 112A / B can assign each assigned CBRS channel to a given band-specific microcell processor 420 / 425 / 420. The local monitor module 112A / B can activate microcells corresponding to CBRS channels for which access was granted in step 325. Any microcells corresponding to assigned CBRS channels for which access was denied in step 325 are kept in an inactive or locked state by the local monitor module 112A / B. Furthermore, in the case where the master monitor module 110 / 210 has configured the CBRS-Daemon 114A / B to require authorization only for a subset of the assigned CBRS channels (active subset), the local monitor module 112A / B can configure any microcells corresponding to the remaining CBRS channels (inactive subset) to be in a locked or inactive state. A locked microcell (i.e., a microcell in a locked state) can be an instantiation of a protocol stack implementation of a band-specific microcell processor (further described below) in which there is no connection to the fronthaul interface 120 / 220 and, thus, no connected UEs.

[0116] Creating a locked microcell can proceed as follows. The local monitor module 112 can execute instructions to instantiate a microcell within a baseband processor 105. The local monitor 112 can pre-configure the locked microcell for a given CBRS channel, but not assign it a slot within the fronthaul interface 120 / 220. In this case, the processor running the given baseband processor 105 / 205 can consume a small amount of resources in performing the operations of the locked microcell without connected UEs and without any resources assigned to the fronthaul interface 110 / 210. A given baseband processor 105 / 205 - or the system 100 / 200 as a whole - can maintain multiple locked microcells, each pre-configured for a given CBRS channel to be in a locked or "parked" state in the event the SAS 182 authorizes access to the channel. For example, many baseband processors 105 / 205 can each maintain a locked microcell for the same CBRS channel, and only one or more given baseband processors 105 / 205 can be selected by the master monitor module 110 / 210 to have an active microcell in the CBRS channel. In the case of multiple baseband processors 105 / 205 sharing a given CBRS channel, the master monitor module 110 / 210 can coordinate with the corresponding local monitor modules 112 to allocate unique component carriers in the CBRS channel. In allocating component carriers, the local monitor module 112 can instantiate one or more band-specific microcell processors, one for each component carrier.

[0117] In the variation where the fronthaul link 175 is implemented over Ethernet and the fronthaul interface 120 is a router, the corresponding baseband processor can be deprived of connectivity to the router for a given locked microcell.

[0118] If the given baseband processor 105 / 205 is authorized to access the pre-configured CBRS channel, the local monitor module 112 can execute instructions to assign the appropriate slot in the fronthaul interface 120 / 220 to the corresponding band-specific microcell processor, and issue instructions to the band-specific microcell processor to connect with UEs as described below with respect to subsequent steps 345 and 350. This approach can be necessary if the base layer software of a virtual baseband processor 105 / 205 does not facilitate dynamic channel reconfiguration upon CBRS authorization changes. It should be understood that such variations are possible and within the scope of the present invention.

[0119] Figure 4A plurality of instantiated and configured virtual baseband processors (depicted here as 105A, B...N) are shown. In this example, baseband processor 105A has three microcell groups 405A-C, each of which can correspond to a remote unit 170 / 270. Instantiated within microcell groups 405A-C are one or more band-specific microcell processor 415 / 420 / 425 / 430 of a set, each of which includes a protocol stack implementation that handles one or more component carriers of its designated band. In the example shown, band-specific microcell processor 415 is designated to licensed band 415 of the mobile network operator; band-specific microcell processor 420 is designated to CBRS channel 1; band-specific microcell processor 425 is designated to CBRS channel 2; and band-specific microcell processor 430 is designated to CBRS channel 3. Each of these band-specific microcell processors 415 / 420 / 425 / 430 can be executed by a software-based protocol stack implementation embodied in a set of machine-readable instructions encoded within a non-transitory memory. Each microcell group 405A-C can have a scheduler component 410 that performs MAC layer scheduling and carrier aggregation among each set of component carriers within the given microcell.

[0120] Each of the microcell groups 405A-C can be referred to as a microcell group processor. A microcell group processor can be defined as a set of band-specific microcell processors capable of serving a given UE or a set of UEs within a single coverage area. The use of multiple band-specific microcell processors enables carrier aggregation across multiple bands to occur within the microcell group processor. Furthermore, in the case of a shared spectrum access system such as CBRS, having multiple CBRS channels (one per band-specific microcell processor) provides redundancy in the event of a license revocation by having one that stays in an inactive or multiple-subscription state and designated to a currently unused CBRS channel. Each band-specific microcell processor can be a software-implemented LTE (Long Term Evolution) or 5G NR (5G New Radio) protocol stack that operates on one or more component carriers within its designated band or CBRS channel. Each protocol stack can include its own scheduler (e.g., MAC layer), and the local scheduler 410 can coordinate with the schedulers to implement carrier aggregation, etc.

[0121] In Figure 4In the example shown, the SAS 182 (not shown) has granted access to CBRS channels 1 and 2 to each CBSD in step 325 for the corresponding proxy authorization request issued by the CBRS-Daemon 114A. Each CBSD can be mapped to a given remote unit 170 / 270. The local monitor 112 has configured band-specific microcell processor 420 and 425 for CBRS channels 1 and 2, respectively, and has configured band-specific microcell processor 430 (designated for CBRS channels) to be in a locked state.

[0122] It should be understood that, Figure 4 The example shown in FIG. 4A involves a baseband processor 105A corresponding to a network operator. If the baseband processor 105A is designated for a private network, band-specific microcell processor 415 can be omitted and the baseband processor 105A can operate alone on a shared spectrum access channel (e.g., CBRS). It should be understood that such variations are possible and within the scope of the present application.

[0123] Returning to Figure 3 The process 300 shown in FIG. 3, in step 345, the processor executes instructions to set up the fronthaul interface 120 / 220, which, as described above, can include instantiating any software modules that configure and operate the fronthaul interface (such as a mapping module 185), perform any necessary data conversions, and act as a router between the baseband processors 105A / B or DUs 205A / B and the fronthaul interface 120 / 220. This can include setting up ports for DMA buffers 192 for allocation to each baseband processor 105A / B or DU 205A / B. Alternatively, if the fronthaul interface 120 / 220 is an Ethernet interface that supports packet-based communications between the baseband processors 105A / B or DUs 205A / B, the fronthaul interface 120 / 220 can be configured as a packet-switched network fabric between the baseband processors 105A / B or DUs 205A / B and the remote unit 170 / 270.

[0124] In step 350, the processor executes instructions to establish communications between the base station 100 / 200 and the remote unit 170 / 270 to configure the remote unit 170 / 270 for carrier selection band and power level to be used by mobile network operators A and B as well as any private networks.

[0125] In step 355, the processor executes instructions to instantiate the KPI coordinator 115 / 215 and the KPI modules 125 / 225, 130 / 230, 135 / 235, 140 / 240, and 145 / 245, and establish communication channels between the designated KPI modules and their respective baseband processors 105A / B or DUs 205A / B.

[0126] With all software modules instantiated, the processor can execute instructions for the master monitor module 110 / 210 to establish inter-task communications between the software modules depicted in FIGS. 1 and 2.

[0127] At this stage of the process 300, the base station 100 / 200 can begin operation as scheduled, with each mobile network operator and private network operating independently with different resources within a shared computing environment, fronthaul, and topology of the remote unit 170 / 270. The remainder of the discussion regarding the process 300 relates to an example scenario in which the SAS revokes authorization to use one or more CBRS channels and / or recommends a switch to a new CBRS channel, which can occur at any time during operation.

[0128] During operation, each CBRS-Daemon 114A / B can issue heartbeat requests to the SAS 182 on behalf of and as a proxy for its CBSDs (and their channels within the remote unit 170 / 270), and thus receive heartbeat responses from the SAS 182.

[0129] In step 360, a CBRS-Daemon 114A / B can receive an indication from the SAS 182 that authorization to a given CBSD for a given CBRS channel is revoked. This can occur via the CBRS heartbeat response according to known procedures.

[0130] In step 365, if authorization revocation occurs, the affected CBRS-Daemon 114A / B can do two things: (1) send a signal to its corresponding local monitor module 112A / B indicating that authorization to an assigned CBRS channel is revoked; and (2) send a new authorization request to the SAS 182 requesting authorization to one or more of its assigned CBRS channels within its non-active subset of channels. If the SAS 182 authorizes access to the newly requested CBRS channels, the local monitor module 112A / B can activate pre-configured pre-existing lock cells for the newly authorized CBRS channels (described in step 370 below).

[0131] There can be a case where a given baseband processor 105A / B has a microcell that spans two CBRS channels. For example, referring to Figure 4 , microcell group 1 (405A) can have a single microcell whose frequencies exist in CBRS 1 (420) and CBRS 2 (425). In this case, a license revocation can eliminate access to a portion of the spectrum that the given microcell is using. In response, the CBRS-Daemon 114A / B, the local monitor module 112 of microcell group 1 (405A), the scheduler 410, and the master monitor module collectively perform either of the following: (1) lock the microcell that spans the two CBRS bands and transmit a request for a license that enables the microcell to handle two newly assigned CBRS channels; or (2) limit the bandwidth of the microcell to fit within the still licensed CBRS channel and then transmit a request for a license for another assigned CBRS channel for which the scheduler 410 can provide carrier aggregation between the still licensed CBRS channel and the newly licensed CBRS channel.

[0132] In step 370, the local monitor module 112A / B can transfer or handoff the UEs connected to the CBSD and CBRS channel to other active microcells within its microcell group (possibly including the newly activated microcell corresponding to the newly licensed CBRS channel in step 365) and then lock the band-specific microcell processor corresponding to the CBRS channel with the revoked license.

[0133] The step of handing off the UEs connected to the CBSD and CBRS channel to another microcell in the microcell group can be performed in the following manner. In one example, the scheduler 410 can issue an instruction to handoff the UEs from the revoked CBRS channel using conventional methods specified in the 3GPP specification. Alternatively, the local monitor module 112A / B can issue an instruction to the master monitor module 110 / 210 to issue a command to the appropriate remote unit 170 / 270 (corresponding to the revoked CBSD(s)) to reduce the transmit power corresponding to the revoked CBRS channel. In doing so, the UEs connected to the revoked CBSD will autonomously identify an alternative microcell within its microcell group and connect to the microcell with the stronger signal. One advantage of this approach is that it takes advantage of the ability of the UE to identify the most suitable alternative microcell and connect without intervention by the scheduler 410. Another advantage of this approach is that the CBRS rules regarding prompt shutdown of radios in the event of a license revocation can be facilitated by this approach.

[0134] In addition to step 370, the processor executable instructions cause the master monitor module 110 / 210 to issue commands to the fronthaul network interface 110 / 210 (and to the mapping module 185) to connect the newly activated microcell to the remote units 170 / 270 affected by the CBSD authorization revocation, which can include: causing the corresponding to the revoked CBRS channels to be separated from their respective DMA buffers 192 and connecting the newly activated band-specific microcell processor to the corresponding DMA buffer 192; issuing commands to the affected remote units 170 / 270 to start at an identified start frame, to transmit and receive on the new CBRS channels and to stop transmitting on the revoked channels; issuing commands to the affected remote units 170 / 270 of the daisy chain to aggregate the uplink signals for the new CBRS channels; and issuing commands to the remote units 170 / 270 corresponding to the non-revoked CBSDs to no longer aggregate the uplink data from the remote units 170 / 270 affected by the revocation. In addition to step 370, the master monitor module 110 / 210 can issue a notification to the associated core network 150 / 160 that the associated CUs 252 corresponding to the revoked CBRS channels need to switch to the new channels. The band-specific microcell processor assigned to the revoked CBRS channels can then run in a locked-down state, disconnected from any UEs or the fronthaul interface 120 / 220, consuming little processor resources while idle.

[0135] While the above example illustrates the use of CBRS, it should be understood that the present application is to belong to any dynamic shared spectrum allocation system in which one or more frequency ranges are provided on a time-dependent requirement / authorization basis to a remote unit or base station (where channels are otherwise publicly provided). As used herein, a CBRS channel is an example of a shared spectrum allocation channel. Further, while the example discloses a CBRS-Daemon, it should be understood that the present application is to belong to any dynamic shared spectrum domain agent that obtains authorization and revocations from the dynamic shared spectrum allocation system on behalf of one or more remote units.

[0136] Figure 5A An exemplary deployment of baseband processors 100 / 200 is shown, including baseband processors 105A / B, each of which is associated with Figure 4The baseband processors are similar in depiction. In this example, each baseband processor 105A / B has at least one group of microcells 405 configured for multicast operations. A band-specific microcell processor for each set of licensed band and CBRS channels (415 / 420 / 425 in this example) is connected to the fronthaul interface 120 through a bidirectional digital baseband I / Q data connection 107. As shown, baseband processor 105A has a locked band-specific microcell processor 430 for CBRS 3, while baseband processor 105B has a locked band-specific microcell processor 430 for CBRS 6. Each CBSD / remote unit 170 has an RF processing block for the licensed band for mobile network operator A (505), an RF processing block for the licensed band for mobile network operator B (510), an RF processing block for CBRS channel 1 allocated to mobile network operator A (515), an RF processing block for CBRS channel 2 allocated to mobile network operator A (520), an RF processing block for inactive CBRS channel 3 (525), an RF processing block for CBRS channel 4 allocated to mobile network operator B (530), an RF processing block for CBRS channel 5 allocated to mobile network operator B (535), and an RF processing block for inactive CBRS channel 6 (540). Each processing block can include low-level LTE or 5G protocol stack processing, such as physical (PHY) layer processing.

[0137] For the example shown in Figure 5A For the example shown in

[0138] In Figure 5AIn the example shown, each of the single RF processing blocks 505 / 510 / 515 / 520 / 530 / 535 (excluding RF processing blocks 525 / 540) are daisy-chained and connected to a corresponding set of component carriers within the microcell group 405 of baseband processor 105A or baseband processor 105B. This enables a multicast operation in which multiple remote CBSDs 170 can share a microcell. In this example, all UEs connected to the remote CBSDs 170 at a given component carrier can share a single data frame. For the downlink (DL), a given baseband processor 105A / B can use a single component carrier processing thread (and thus a single data frame) for all daisy-chained CBSDs; thus, a copy of a single data frame can be replicated and transmitted to all CBSDs 170. However, for the uplink (UL), a given RF processing block within a single CBSD 170 (e.g., CBRS 4 (530)) can only receive signals of that frequency from UEs connected to that CBSD 170. Other CBSDs 170 will receive signals of a unique set of UEs from a distinct set of REs within the data frame allocated to that component carrier. In view of this, each CBSD 170 aggregates the signals it receives from its own antennas with the data it receives from the downstream neighbor CBSD 170.

[0139] As described above, the daisy-chained topology of the remote units 170 enables multicast for the DL and aggregation of component carriers for the UL. In this case, CBSD 2 can aggregate the band-specific UL signals it receives from its connected UEs with the corresponding band-specific signal data it receives from CBSD 3; and CBSD 1 can aggregate the UL signals of its connected UEs with the corresponding band-specific signal data it receives from CBSD 2.

[0140] In addition to the example shown in Figure 5A both baseband processors 105A / B have a microcell group processor 405 configured for multicast operation. However, as shown in Figure 4 each baseband processor 105A / B can have other microcell group processors that can be configured for multicast operation with other remote units (not shown) or configured in a pattern in which each microcell group is connected to one or more remote units that are not multicast-enabled. It should be understood that such variations are possible and within the scope of the present application.

[0141] In addition to the example shown in Figure 5AExamples, the fronthaul interface 120 and fronthaul link 175 can involve a CPRI link. In this case, each RF processing block includes circuitry to: receive a CPRI stream from a downstream remote unit 170; extract CPRI stream data corresponding to a given frequency band for that RF processing block; aggregate the extracted CPRI stream data with data generated by the RF processing block from signals received from its antennas (from UEs connected thereto); insert the aggregated data into a corresponding CPRI block; and transmit the new CPRI data upstream to the next remote unit 170 or fronthaul interface 120. As noted above, the aggregation can be on a single TTI (Transmission Time Interval). In a variation where the fronthaul link 175 is an Ethernet connection, then the fronthaul interface 120 can be a router through which each baseband processor 105A / B can communicate with different remote units 170 using encapsulated data streams. In this example, uplink aggregation can occur at the fronthaul interface 120 or at the appropriate baseband processor 105A / B.

[0142] Figure 5B after display of a single CBSD 170 revocation of a single CBRS channel license, Figure 5Aof the system. In this example, baseband processor 105A initially has its licensed band active band-specific microcell processor-415, CBRS1 (420) and CBRS2 (425). Upon a grant revocation, referring to step 360 of process 300, the CBRS-Daemon (not shown) of baseband processor 105A receives a grant revocation from the SAS revoking access to CBRS channel 2 in CBSD 2. As specified in step 365, the CBRS-Daemon can transmit a grant request to the SAS requesting a grant for CBRS 3, CBRS 3 being specified to a pre-configured and locked band-specific microcell processor 430 within baseband processor 105A. If the SAS grants access to CBRS 3, the CBRS-Daemon can issue commands to the local monitor module (not shown) of baseband processor 105A instructing that CBRS2 RF processing block 520 in CBSD 2 be shut down and UEs connected to CBRS2 RF processing block 520 in CBSD 2 be handed over to other channels according to step 370. In response, the local monitor module of baseband processor 105A can: unlock and activate band-specific microcell processor 430 corresponding to CBRS 3; hand over affected UEs to other channels (e.g., by reducing the power of RF processing block 520 of CBSD 2 to trigger the UEs to establish connections with other channels within CBSD 2); and lock the CBRS2 band-specific microcell processor 425. In addition, the master monitor module (not shown) can: issue commands to the fronthaul interface module 120 instructing it to allocate a CPRI slot (and thus a DMA buffer) to the CBRS 3 band-specific microcell processor 425 of baseband processor 105A; issue commands to CBSD 1 and CBSD 3 instructing them to remove CBSD 2 from the daisy chain structure of CBRS2; issue commands to CBSD 2 to activate RF processing block 525 for CBRS 3, including information about the newly allocated CPRI slot for the CBRS 3 band-specific microcell processor 430 of baseband processor 105A; and issue commands to CBSD 2 to shut down RF processing block 520 for CBRS2. The new I / Q data connection for the CBRS 3 band-specific microcell processor 430 of baseband processor 105A is shown as data connection 107A Figure 5B (darker line); the new fronthaul link between fronthaul interface 120 and CBRS for CBSD 2 is shown as fronthaul link 175A Figure 5B (darker line); and the new link between CBSD 1 and CBSD 3 for CBRS2 is shown as data connection 175B Figure 5BMid color darker line).

[0143] Unless specifically stated otherwise, the term "subset" can refer to a portion or all of its corresponding set. Furthermore, as used herein, a channel denial can include an authorization revocation (for a previously authorized channel) and a denial (for a channel that has not been authorized).

Claims

1. A method for configuring and operating a virtual base station carrying multiple network operators in a shared spectrum access system, comprising: instantiating, by a processor of a virtual base station, a plurality of baseband processors for the virtual base station, each baseband processor corresponding to a different one of a plurality of network operators, each baseband processor having one or more microcell group processors, wherein each microcell group processor has a plurality of band-specific microcell processors, wherein each of the plurality of baseband processors operates independently of any of the other of the plurality of baseband processors; allocating, by the processor, a different plurality of shared spectrum access channels to each of the plurality of baseband processors of the virtual base station; receiving a grant of one or more of the plurality of shared spectrum access channels corresponding to each baseband processor; allocating, by each of the plurality of baseband processors independently, each of the different plurality of shared spectrum access channels to a band-specific microcell processor of the corresponding one of the plurality of baseband processors of the virtual base station.

2. The method of claim 1, further comprising: configuring each band-specific microcell processor assigned a granted shared spectrum access channel to be in an active state; and configuring each band-specific microcell processor not assigned a granted shared spectrum access channel to be in a locked state.

3. The method of claim 1, further comprising: obtaining operator-specific information corresponding to each of the plurality of network operators; and configuring each of the plurality of baseband processors using the operator-specific information corresponding to the network operator of the baseband processor.

4. The method of claim 3, wherein the operator-specific information comprises: licensed band information; and Citizens Broadband Radio Service (CBRS) priority access license information.

5. The method of claim 2, further comprising: configuring each of a plurality of remote units to operate on a corresponding granted shared spectrum access channel.

6. The method of claim 5, further comprising: connecting each band-specific microcell processor in an active state to a fronthaul interface; and connecting each of the plurality of remote units to the fronthaul interface.

7. The method of claim 6, wherein connecting each band-specific microcell processor in an active state to a fronthaul interface comprises connecting each band-specific microcell processor in an active state to a Common Public Radio Interface (CPRI) fronthaul interface.

8. The method of claim 7, wherein connecting each band-specific microcell processor in an active state to the CPRI fronthaul interface comprises connecting each band-specific microcell processor in an active state to a CPRI fronthaul interface direct memory access (DMA) buffer. ​ ​ ​ ​ 9. The method of claim 6, wherein the step of connecting each band-specific microcell processor in an active state to the fronthaul interface comprises connecting each band-specific microcell processor in an active state to an Ethernet router.

10. The method of claim 6, further comprising: receiving a grant revocation corresponding to a revoked shared spectrum access channel within the plurality of granted shared spectrum access channels, the revoked shared spectrum access channel corresponding to a revoked remote unit; and issuing an instruction to the revoked remote unit to turn off a radio corresponding to the revoked shared spectrum access channel.

11. The method of claim 10, further comprising disconnecting the band-specific microcell processor in an active state from any UE or fronthaul interface.

12. The method of claim 10, further comprising switching the band-specific microcell processor corresponding to the revoked shared spectrum access channel to a locked state.

13. The method of claim 10, further comprising: issuing a grant request to request access to an unused shared spectrum access channel; receiving a grant of the unused shared spectrum access channel such that the unused shared spectrum access channel now becomes a new granted shared spectrum access channel; switching the band-specific microcell processor corresponding to the new granted shared spectrum access channel to an active state; issuing an instruction to the revoked remote unit to turn on a radio corresponding to the new granted shared spectrum access channel; and connecting the band-specific microcell processor corresponding to the new granted shared spectrum access channel to the fronthaul interface.

14. The method of claim 5, wherein the step of configuring each remote unit of the plurality of remote units to operate on its corresponding granted shared spectrum access channel comprises configuring one or more remote units of the plurality of remote units to perform low physical (PHY) level functions of the granted shared spectrum access channel.

15. The method of claim 14, wherein the step of configuring one or more remote units of the plurality of remote units to perform low physical (PHY) level functions comprises configuring one or more remote units of the plurality of remote units to perform low physical (PHY) level functions according to split option 7-2x.

16. The method of claim 5, wherein the step of configuring each remote unit of the plurality of remote units to operate on its corresponding granted shared spectrum access channel comprises configuring one or more remote units of the plurality of remote units to operate as a gNodeB distributed unit.

17. A computer system comprising a processor and a memory having software that, when executed, implements a virtual base station configured to perform the method of any of claims 1-16. ​ 18. A non-transitory computer-readable memory with encoded instructions that, when executed by one or more processors, cause the one or more processors to implement a method as claimed in any of claims 1-16.

19. A method for hosting multiple network operators in a single computing environment, comprising: allocating a plurality of operator-specific shared spectrum access channels to each baseband processor of a plurality of baseband processors of a virtual base station, each baseband processor of the plurality of baseband processors corresponding to one of the plurality of network operators, the plurality of operator-specific shared spectrum access channels having a required subset of shared spectrum access channels and a backup subset of shared spectrum access channels; requesting, by each baseband processor of the virtual base station, an access grant for its corresponding required subset of shared spectrum access channels; receiving a reply access grant for each required subset of shared spectrum access channels; receiving, by a first baseband processor of the virtual base station, a revoked shared spectrum access channel corresponding to one of the required subset of shared spectrum access channels; and requesting, by the first baseband processor of the virtual base station, an access grant for its corresponding backup subset of shared spectrum access channels.

20. A computer system comprising a processor and a memory having software that, when executed, implements a virtual base station configured to perform a method as claimed in claim 19.

21. A non-transitory computer-readable memory with encoded instructions that, when executed by one or more processors, cause the one or more processors to implement a method as claimed in claim 19.

22. A method of configuring and operating a virtual base station, comprising: instantiating a baseband processor for the virtual base station, wherein the baseband processor has at least one or more microcell group processors, wherein each microcell group processor has a plurality of band-specific microcell processors; allocating a plurality of shared spectrum access channels to the baseband processor; receiving a grant of one of the plurality of shared spectrum access channels; designating each of the plurality of shared spectrum access channels to a corresponding band-specific microcell processor; setting each band-specific microcell processor allocated a granted shared spectrum access channel to an active state, and setting any of the plurality of band-specific microcell processors not allocated a granted shared spectrum access channel to a locked state; connecting, through a network interface, a remote unit to the specific microcell processor of the granted shared spectrum access channel; in accordance with the remote unit being revoked, receiving a grant revocation corresponding to the granted shared spectrum access channel; issuing an instruction to the remote unit to shut down a radio corresponding to the granted shared spectrum access channel for which the grant revocation has been received.

23. The method of claim 22, further comprising: disconnecting any UE or fronthaul interface associated with the band-specific microcell processor.

24. The method of claim 22, further comprising: switching the band-specific microcell processor corresponding to the revoked shared spectrum access channel from an active state to a locked state.

25. The method of claim 22, further comprising: issuing a grant request to request access to an unused shared spectrum access channel; receiving a grant of the unused shared spectrum access channel such that the unused shared spectrum access channel now becomes a newly-granted shared spectrum access channel; switching the band-specific microcell processor corresponding to the newly-granted shared spectrum access channel from a locked state to an active state; issuing an instruction to the remote unit to turn on a radio corresponding to the newly-granted shared spectrum access channel; and connecting, via the network interface, the band-specific microcell processor corresponding to the newly-granted shared spectrum access channel to the remote unit.

26. A computer system comprising a processor and a memory having software which, when executed, implements a virtual base station configured to perform the method of any of claims 22-25.

27. A non-transitory computer readable memory with encoded instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of claims 22-25. ​

Images