Cross-Reference to Related Applications

[0001] This application claims priority under PCT Art. 8 and/or 35 U.S.C. § 119(e) to U.S. Provisional Pat. App. No. 62/801,032, filed February 4, 2019, titled“Hybrid Base Station and RRH,” which is hereby incorporated by reference in its entirety for all purposes. This application hereby incorporates by reference, for all purposes, each of the following U.S. Patent Application Publications in their entirety: US20170013513A1; US20170026845 Al; US20170055186A1; US20170070436A1; US20170077979A1; US20170019375A1; US20170111482A1; US20170048710A1; US20170127409A1; US20170064621A1; US20170202006A1; US20170238278A1; US20170171828A1; US20170181119A1; US20170273134A1; US20170272330A1; US20170208560A1; US20170288813 Al; US20170295510A1; US20170303163A1; and US20170257133A1. This application also hereby incorporates by reference U.S. Pat. No. 8,879,416, “Heterogeneous Mesh Network and Multi -RAT Node Used Therein,” filed May 8, 2013; U.S. Pat. No. 9,113,352,“Heterogeneous Self-Organizing Network for Access and Backhaul,” filed September 12, 2013; U.S. Pat. No. 8,867,418,“Methods of

Incorporating an Ad Hoc Cellular Network Into a Fixed Cellular Network,” filed

February 18, 2014; U.S. Pat. App. No. 14/034,915,“Dynamic Multi-Access Wireless Network Virtualization,” filed September 24, 2013; U.S. Pat. App. No. 14/289,821, “Method of Connecting Security Gateway to Mesh Network,” filed May 29, 2014; U.S. Pat. App. No. 14/500,989,“Adjusting Transmit Power Across a Network,” filed

September 29, 2014; U.S. Pat. App. No. 14/506,587,“Multicast and Broadcast Services Over a Mesh Network,” filed October 3, 2014; U.S. Pat. App. No. 14/510,074,

“Parameter Optimization and Event Prediction Based on Cell Heuristics,” filed October 8, 2014, U.S. Pat. App. No. 14/642,544,“Federated X2 Gateway,” filed March 9, 2015, and U.S. Pat. App. No. 14/936,267,“Self-Calibrating and Self- Adjusting Network,” filed November 9, 2015; U.S. Pat. App. No. 15/607,425,“End-to-End Prioritization for Mobile Base Station,” filed May 26, 2017; U.S. Pat. App. No. 15/803,737,“Traffic Shaping and End-to-End Prioritization,” filed November 27, 2017, each in its entirety for all purposes, having attorney docket numbers PWS-71700US01, US02, US03, 71710US01,

71721US01, 71729US01, 71730US01, 71731US01, 71756US01, 71775US01,

71865US01, and 71866US01, respectively. This document also hereby incorporates by reference U.S. Pat. Nos. 9107092, 8867418, and 9232547 in their entirety. This document also hereby incorporates by reference U.S. Pat. App. No. 14/822,839, U.S. Pat. App. No. 15/828427, U.S. Pat. App. Pub. Nos. US20170273134A1, US20170127409A1 in their entirety.

Background

[0002] A Converged Wireless System (CWS) is a multi-RAT base station with 3G, LTE/4G, 5G and Wi-Fi technologies that provides a flexible outdoor and in-vehicle solution in conjunction with a coordination node, variously known as a radio access network controller (RAN controller), radio access network intelligent controller (RIC), aggregator, coordination node, or Parallel Wireless Heterogeneous Network Gateway (HNG). The combined system is a cloud-based network orchestration system that maximizes virtualization, and functions to bring 3G, LTE/4G, 5G and Wi-Fi operators better technology at lower cost. The combination of the HNG and the CWS addresses key challenges in delivering coverage, capacity, and quality of service (QoS), regardless of the cell size, e.g., femtocell, pico cell, micro cell, metro cell, or macro cell. In some embodiments, the CWS may be a multi-RAT base station with Wi-Fi and LTE access capability; integrated flexible backhaul including line of sight (LOS) and non-line of sight, fiber, Ethernet, and LTE backhaul; multi-radio multipoint-to-multipoint wireless mesh capability; control, security and traffic prioritization capability; self-organizing network (SON)-based interference mitigation for superior subscriber experience and dynamic RF power adjustments.

Some base stations are designed as all-in-one devices, but customer demand is not one- size- fits-all. As demands increase, hard to swap out the baseband card. Future upgradeability is a requirement, including for 5G. There is also substantial market demand for remote radio heads of various types, as well as various splits of baseband processing, from full baseband processing at the base station to centralized baseband processing (CRAN or“baseband hotel”) to distributed or aggregated baseband processing schemes of various types. Baseband can be processed outside of the base station as long as radio samples are able to be transported and processed within a latency budget that is the consequence of standards set by the radio access technology (RAT), e.g.,

2G/3G/4G/5G/Wi-Fi/etc.

Summary

[0003] Systems, methods and compute readable medium instructions for providing base station and Remote Radio Head (RRH) functionality in a base station are described. In one embodiment, a method may be disclosed for providing base station and Remote Radio Head (RRH) functionality in a base station. The method includes providing a baseband card; providing a radio head, the radio head coupled to the baseband card by way of an interface; and wherein the radio head includes a Common Public Radio Interface (CPRI) enabling use of the base station as a remote radio head, thereby providing dual base station and remote radio head functionality.

[0004] In another embodiment, a system may be disclosed, the system including a baseband card; a radio head, the radio head coupled to the baseband card by way of an interface; and wherein the radio head includes a Common Public Radio Interface (CPRI) enabling use of the base station as a remote radio head, thereby providing dual base station and remote radio head functionality.

[0005] In another embodiment, a non-transitory computer-readable medium is disclosed, the computer readable medium containing instructions for providing base station and Remote Radio Head (RRH) functionality in a base station, which, when executed, cause a base station to perform steps comprising: providing a baseband card; providing a radio head, the radio head coupled to the baseband card by way of an interface; and wherein the radio head includes a Common Public Radio Interface (CPRI) enabling use of the base station as a remote radio head, thereby providing dual base station and remote radio head functionality.

Brief Description of the Drawings [0006] FIG. l is a block diagram showing the connectors on a base station, in accordance with some embodiments.

[0007] FIG. 2A is a flowchart depicting a process for utilizing an external baseband unit, in accordance with some embodiments.

[0008] FIG. 2B is a flowchart depicting a process for switching between two external BBU input signals, in accordance with some embodiments.

[0009] FIG. 3 is a block diagram showing the system including an antenna, radio head, and baseband unit, in accordance with some embodiments.

[0010] FIG. 4 is a block diagram showing processing components, in accordance with some embodiments.

[0011] FIG. 5 is a network diagram, in accordance with some embodiments.

[0012] FIG. 6 is an enhanced eNodeB for performing the methods described herein, in accordance with some embodiments.

[0013] FIG. 7 is a coordinating server for providing services and performing methods as described herein, in accordance with some embodiments.

Detailed Description

[0014] An exemplary design includes a baseband card sharing an enclosure with a radio head, wherein the radio head is coupled to the baseband card via any proprietary or standard interface. The radio head also has a standard CPRI interface, enabling a CPRI passthrough. Enabling a CPRI connection to the radio head allows the device to operate functionally as a RRH, giving it dual base station and RRH functionality.

[0015] FIG. 1 is a block diagram showing the connectors on a base station, in accordance with some embodiments. Referring to FIG. 1, a block diagram rear view of a CWS base station providing base station and RRH functionality 100 is shown. The CWS includes a power connector 101, a Small Form Factor Pluggable (SFP) port 102, an RJ45 connector for Power Over Ethernet (POE) 103, a first antenna port 104, and a second antenna port 105. Also shown is an alarm port 106 and Antenna Interface Standards Group (AISG) connectors 107 and 108. Port 103 can be used for backhaul via SFP.

However, port 103 can also be replaced and/or turned into a CPRI passthrough for an external BBU, in some embodiments. SFP is a pluggable module with a cage, with a light to electrical transducer. Connects to internal Ethernet switch. SFP is 1.25 G SERDES; SFP+ is a variant of SFP with lOGbps performance.

[0016] Thus, as shown in FIG. 1, there is potential to replace the RJ45/POE with a second SFP. Would be able to run a second fiber down from the CWS, so that there was the capability to do a future expansion to a BBU (example: CPRI). A disadvantage with this approach is you lose both the RJ45 and the POE, so cannot easily plug in a BHM. Additionally, have an extra“dark” fiber that may or may not work, when needed. We can retain the RJ45/POE and just use a single SDFP for Ethernet backhaul or CPRI (one at a time).

[0017] As known in the art, the CPRI protocol enables transfer of EQ data (samples) for radio, using 15-bit words. CPRI also adds: Control commands (“turn TX up” or“give me RSSI”), timing (start stop, frame boundaries) and clocking (Frequency band is controlled by clocking accuracy; critical since EQ is time domain data). CPRI is carried at line rate of underlying PHY. CPRI is a master-slave interface. Master provides clocking, typically with GPS clock disciplining. 4.1952 Gbps is fast enough to provide 2X2 T2R @ 30.72 samples per sec (20 MHz band), e.g., 2 LTE carriers. eCPRI sends no I/Q, sends commands. Where the word CPRI is used herein, it is understood that eCPRI or another equivalent protocol may also be substituted therein.

[0018] CPRI versus Ethernet. CPRI does its own framing, does not use Ethernet PHY. Auto-detect Ethernet or CPRI based on signals on the chip. CPRI sends whole frame, and it will be decoded at the CPRI receiving end.

[0019] Overview of CPRI processing. EQ samples are digitized at DAC. FPGA creates CPRI frame. Send CPRI signal out via SFP port to BBU. External BBU processes it.

[0020] CPRI processing is well-known, but the use of it in a hybrid approach is not. As well, the auto-detect is not known. This arrangement enables flexible RAN splits a la 5G deployment models. Full base station or RRH or both. [0021] There is a way to“autodetect” whether a fiber is connected to a BBU (CPRI) or to an Ethernet device (example a router). When SFP+ port is connected to an Ethernet switch - in this case it is an ethernet backhaul connection, and it is connected to the Ethernet switch onboard. When SFP+ port is connected to BBU - it is a CPRI connection, and connected to the FPGA. When in this configuration, the CPRI control channel can be routed back to the onboard Ethernet switch to provide backhaul.

[0022] The present disclosure contemplates at least the following scenarios:

[0023] - A base station with baseband card. May be a multi -RAT base station, e.g., 2G + 4G, or 3G + 4G, or any other combination. RATs could include: 2G/3G/4G/5G/Wi-Fi, others. May include hardware accelerators, e.g., FPGA, DPDK etc, for performing processing of the RATs. Radio includes CPRI input and direct input for baseband card.

[0024] - A remote baseband unit coupled to the CPRI input. Could be located at the bottom of the tower, in a cabinet. Could be used to provide another RAT, e.g., if baseband card provides 2G + 4G, the R-BBU could provide 3G. R-BBU could provide high-end features and expandability: carrier aggregation, CoMP, etc. Could be located further from the tower as well, as long as latency requirements are met.

[0025] - A switchable version of the above two embodiments, which may be referred to as hybrid, such that eBBU/rBBU functionality is available and may be turned on via software or hardware switching. In some embodiments, it may be decided by the telecom operator which radio interfaces and radio technologies are supported by a baseband processor at the base station itself versus in a remote baseband or external baseband.

[0026] - In some embodiments, multiple basebands coupled to a single radio are generally contemplated. In some embodiments, multiple basebands that use switchable ports between CPRI and Ethernet are contemplated. In some embodiments, switching one or more ports as needed between CPRI for external BBU and Ethernet backhauling based on performance needs is contemplated.

[0027] Hybrid base station/radio head is thus the best of both worlds. Switchable to act as one or the other. Upgradable capability based on what is plugged into the CPRI port. RJ45 is cheaper than a copper SFP. Base station can provide PoE. Install once, with single fiber run. Subsequently upgrade from Ethernet backhaul to CPRI. Saves fiber run and ensures that fiber works when you go to upgrade to CPRI. Form factor can be similar to other small cells and small macro cells.

[0028] FIG. 2A is a flowchart depicting a process for utilizing an external baseband unit, in accordance with some embodiments. At step 201, 1/Q samples are digitized at a DAC. At step 202, a processor, which may be a FPGA, creates the CPRI frames. At step 203, this CPRI signal is sent out via the SFP port to the external BBU. At step 204, the external BBU processes it.

[0029] FIG. 2B is a flowchart depicting a process for switching between two external BBU input signals, in accordance with some embodiments. At step 205, an input signal is received by the base station. At step 206, a relatively fast processor capable of handling either CPRI or Ethernet frames at an appropriate bandwidth is employed to determine whether this input signal appears to be CPRI or Ethernet; these protocols are different enough that this is a simple task. If CPRI is found, this CPRI signal may be sent out via an SFP port to the radio directly, or, in some embodiments, if another FPGA is present to provide additional functionality such as crest factor reduction (CFR) or digital pre distortion (DPD), the CPRI signal may be passed to that chip. If Ethernet is found, the system may make the determination that these are not radio samples, and that the input signal should be sent to a baseband processor that is located onboard.

[0030] FIG. 3 is a diagram showing a system 300 having a mast 301 with an antenna 302 disposed on the mast. While only a single antenna is shown, it should be appreciated that multiple antennas may be used. Also shown is a radio head 303 in communication with antenna 302. A baseband unit 305 is shown disposed remote from the radio head 303 and in communication with the radio head 303 by way of CPRI connection 304.

[0031] There may be a condition when the signal when both the BBU (connected via CPRI) and the baseband card are overlaid. These do not get put on the same bus at the same time. If they were to get put on the same bus, they have different framing. Autodetect will detect which frames are which and can optionally send different frames to different targets.

[0032] CWS with local baseband capability that can run a multi -RAT architecture, including 5G, but that can also work as a split architecture where some of the processing stack can move“down the stack” to a BBU in some circumstances, or can also act as a pure remote radio head without base station functionality.

[0033] Various combinations of BBU processing are contemplated, up to and including being able to fully and dynamically mix and match RRH and BS for each RAT. For example, this enables upgradability from one“G” to another“G” by adding hardware BBU; and upgradability by adding external offload capability, thereby enabling the base station portion to provide additional capability (e.g., BBU provides 3G offload, BS now available to provide 2G/4G).

[0034] FIG. 4 is a block diagram showing processing components, in accordance with some embodiments. Base station 401 includes PoE Ethernet port 402, coupled to RJ45 interface 404, which is coupled to an internal Ethernet switch 405. An additional CPRI (to BBU) or Ethernet (switchable) port 403 is also provided, coupled to an SFP+ interface 414. A repeater/mux 416 is used to perform switching either between the internal Ethernet switch 405 or the radio support FPGA 407, depending on the type of input signal, as described herein.

[0035] The Ethernet switch 405 is also coupled to onboard baseband processors 1 and 2, denoted 415. The baseband processors utilize Ethernet backhaul 402 via the switch, and perform baseband processing for one or more carriers using one or more radio access technologies, e.g., 2G/3G, 2G/4G, 3G/4G, 4G/4G, and output radio samples to the radio, which first passes through the radio support FPGA 407. In some embodiments the Ethernet switch is also directly coupled to the radio support FPGA 407.

[0036] The radio support FPGA 407 performs various functions that improve the performance of the radio, however, after the radio signal has been created digitally. For example, crest factor reduction (CFR) and digital pre-distortion (DPD) are contemplated.

As these are processor-intensive, an FPGA or other ASIC may be used. [0037] The output of this FPGA 407 goes to the radio, here labeled RFIC 408. This is a digital radio and may be a discrete solution. The radio generates the radio signals and puts them into the RF transmit chain (or receives from the RF receive chain), consisting of power amplifiers and low noise amplifiers 410, and, duplexers 411, finally terminating in antennas 412.

[0038] Radio access technology/ Access Mode Technology (Access): 2G/3G/4G/5G. The present disclosure can be used to support the PW“any G” concept, as applicable to the band of operation of the CWS radio the internal baseband or external baseband is integrated with. By swapping out the external baseband using CPRI, any G can be supported, in conjunction with the internal baseband, which may supply baseband processing at a minimum for 4G/4G, 2G/4G, or 3G/4G in some embodiments. This is particularly relevant as 2G physical layer processing can be performed without overly intensive processing resources and therefore is a good candidate to be performed at the onboard BBU. Note: 2G is relevant to 3GPP Bands 2, 3, 5, 8.

[0039] Band(s) Supported (Backhaul): Band agnostic; the baseband card can support any CWS 3 GPP band TDD or FDD.

[0040] Technology Standard: 3GPP Release 11 and higher, etc. All requirements of this standard to be met as a minimum unless otherwise stated.

[0041] MIMO (LTE): 2 x 2, HW Ready to support 2x2 MIMO LTE / 4G or above. Assumes capability at the UE is matched for this mode of operation.

[0042] # Carriers (Tx 2G/3G/4G/5G): Multiple carriers for each G can be supported.

[0043] All Carrier Combinations for Multi-RAT are contemplated.

[0044] Number of Users is dependent on the system configuration e.g. if internal (embedded processor) or external BBU.

[0045] CPRI Backhaul shall be supported and shall support fiber data connection running CPRI. Note: some customization may be required for backhauling. [0046] CPRI Line Rate: Rate 5, At least 4.9152Gbps to be supported. Note: CPRI rate 5 supports 4 x 20MHz LTE AxC.

[0047] CWS backhaul over CPRI - In CPRI mode the CPRI control channel may be routed back to the internal Ethernet switch to provide backhaul to the CWS.

[0048] Multiple CPRI lanes could be used. CPRI lanes could be dedicated to different RATs.

[0049] SFP Detect Function: Card shall detect and be able to report the fitted SPF to ensure it is compatible / fit for purpose Card may be able to determine the type of SPF fitted and assess some or all of the following parameters: SFP Type / Manufacturer;

Serial Number; Temperature; Data Rate / Capability. Interface with SFP shall be supported Interface (e.g. I2C) for allowing interrogation of the SFP type and functions.

[0050] Backhaul CPRI. CPRI Auto-detect - to auto-detect whether a fiber connection is CPRI and hence adapt to use CPRI as Backhaul.

[0051] CPRI synchronization to be used when in CPRI mode. Note: 1588 is not a function of the hybrid BS. GPS not relevant to CPRI. In backhaul mode it goes to the FPGA not main processor.

[0052] Fiber Input SFP: Shall support SFP (small form-factor pluggable transceiver). For use in the CWS the physical interface shall remain the same.

[0053] Fiber Input SFP+: Shall support SFP+ (enhanced small form-factor pluggable transceiver). For use in the CWS with same form factor as SFP.

[0054] Ethernet Backhaul: Shall be supported. Shall support fiber data connection running Ethernet up to lGbps.

[0055] Backhaul Ethernet. Ethernet Auto-Detect - to auto- detect whether a fiber is Ethernet and hence shall adapt to use Ethernet as Backhaul.

[0056] PoE+ Connector: RJ45 Uses the RJ-45 connector.

[0057] PoE+ Power Output: Through PoE Connector. [0058] PoE+: 802.3at From RJ-45 data connector for powering local ancillary equipment e g. PW BHM.

[0059] Any number of CPRIs could be supported. JESD buses could be supported. Higher power BBU could provide 5G, CoMP, high user count, or other high performance capabilities.

[0060] Optical module can handle either CPRI or Ethernet.

[0061] Further details are provided regarding the implementation of CPRI/Ethernet switching. 1. Serializer/deserializer (SERDES) mux listens to signal. Start with Eth, wait for link to come up, ask switch if link is up (Wait 5 secs to acquire signal). Alternately, CPU can also give us a’’Link Up” signal. Ask SFP+: Is module plugged in? ... Is the light on? If we can’t decide we could just send the signal to both ETH and CPRI.

[0062] We discriminate between CPRI signals using clock, then timing, then control messages. We discriminate ETH using link status. Can also use Retimement chip with mux or a 3-position high speed switch. Logic is all in SW on main CWS processor

[0063] FIG. 5 is a network diagram in accordance with some embodiments. In some embodiments, as shown in FIG. 5, a base station 1 501, a base station 2 502, and a base station 3 503 are RAN nodes of a conventional type or according to embodiments of the disclosure herein. Base stations 501, 502, and 503 may be mesh nodes and may form a mesh network establishing mesh network links 506, 507, 508, 509, and 510 with a base station 504. The mesh network links are flexible and are used by the mesh nodes to route traffic around congestion within the mesh network as needed. The base station 504 acts as gateway node or mesh gateway node, and provides backhaul connectivity to a core network to the base stations 501, 502, and 503 over backhaul link 514 to a coordinating server(s) 505 and towards core network 515. The Base stations 501, 502, 503, 504 may also provide eNodeB, NodeB, Wi-Fi Access Point, Femto Base Station etc. functionality, and may support radio access technologies such as 2G, 3G, 4G, 5G, Wi-Fi etc. The base stations 501, 502, 503 may also be known as mesh network nodes 501, 502, 503. [0064] The coordinating servers 505 are shown as two coordinating servers 505a and 505b. The coordinating servers 505a and 505b may be in load-sharing mode or may be in active- standby mode for high availability. The coordinating servers 505 may be located between a radio access network (RAN) and the core network and may appear as core network to the base stations in a radio access network (RAN) and a single eNodeB to the core network, i.e., may provide virtualization of the base stations towards the core network. As shown in FIG. 5, various user equipments 511a, 511b, 51 lc are connected to the base station 501. The base station 501 provides backhaul connectivity to the user equipments 511a, 511b, and 511c connected to it over mesh network links 506, 507, 508, 509, 510 and 514. The user equipments may be mobile devices, mobile phones, personal digital assistant (PDA), tablet, laptop etc. The base station 502 provides backhaul connection to user equipments 512a, 512b, 512c and the base station 503 provides backhaul connection to user equipments 513a, 513b, and 513c. The user equipments 511a, 511b, 511c, 512a, 512b, 512c, 513a, 513b, 513c may support any radio access technology such as 2G, 3G, 4G, 5G, Wi-Fi, WiMAX, LTE, LTE-Advanced etc.

supported by the mesh network base stations, and may interwork these technologies to IP.

[0065] In some embodiments, depending on the user activity occurring at the user equipments 511a, 511b, 511c, 512a, 512b, 512c, 513a, 513b, and 513c, the uplink 514 may get congested under certain circumstances. As described above, to continue the radio access network running and providing services to the user equipments, the solution requires prioritizing or classifying the traffic based at the base stations 501, 502, 503. The traffic from the base stations 501, 502, and 503 to the core network 515 through the coordinating server 505 flows through an IPSec tunnel terminated at the coordinating server 505. The mesh network nodes 501, 502, and 503 adds IP Option header field to the outermost IP Header (i.e., not to the pre-encapsulated packets). The traffic may from the base station 501 may follow any of the mesh network link path such as 507, 506-110, 506-108-109 to reach to the mesh gateway node 504, according to a mesh network routing protocol. [0066] Although the above systems and methods for providing interference mitigation are described in reference to the Long Term Evolution (LTE) standard, one of skill in the art would understand that these systems and methods could be adapted for use with other wireless standards or versions thereof. The inventors have understood and appreciated that the present disclosure could be used in conjunction with various network

architectures and technologies. Wherever a 4G technology is described, the inventors have understood that other RATs have similar equivalents, such as a gNodeB for 5G equivalent of eNB. Wherever an MME is described, the MME could be a 3G RNC or a 5G AMF/SMF. Additionally, wherever an MME is described, any other node in the core network could be managed in much the same way or in an equivalent or analogous way, for example, multiple connections to 4G EPC PGWs or SGWs, or any other node for any other RAT, could be periodically evaluated for health and otherwise monitored, and the other aspects of the present disclosure could be made to apply, in a way that would be understood by one having skill in the art.

[0067] Additionally, the inventors have understood and appreciated that it is

advantageous to perform certain functions at a coordination server, such as the Parallel Wireless HetNet Gateway, which performs virtualization of the RAN towards the core and vice versa, so that the core functions may be statefully proxied through the coordination server to enable the RAN to have reduced complexity. Therefore, at least four scenarios are described: (1) the selection of an MME or core node at the base station; (2) the selection of an MME or core node at a coordinating server such as a virtual radio network controller gateway (VRNCGW); (3) the selection of an MME or core node at the base station that is connected to a 5G-capable core network (either a 5G core network in a 5G standalone configuration, or a 4G core network in 5G non-standalone configuration); (4) the selection of an MME or core node at a coordinating server that is connected to a 5G-capable core network (either 5G SA or NSA). In some embodiments, the core network RAT is obscured or virtualized towards the RAN such that the coordination server and not the base station is performing the functions described herein, e.g., the health management functions, to ensure that the RAN is always connected to an appropriate core network node. Different protocols other than S1AP, or the same protocol, could be used, in some embodiments.

[0068] Shown above is a schematic network architecture diagram for 3G and other-G prior art networks. The diagram shows a plurality of“Gs,” including 2G, 3G, 4G, 5G and Wi-Fi. 2G is represented by GERAN 501, which includes a 2G device 501a, BTS 501b, and BSC 501c. 3G is represented by UTRAN 502, which includes a 3G UE 502a, nodeB 502b, RNC 502c, and femto gateway (FGW, which in 3GPP namespace is also known as a Home nodeB Gateway or HNBGW) 502d. 4G is represented by EUTRAN or E-RAN 503, which includes an LTE UE 503a and LTE eNodeB 503b. Wi-Fi is represented by Wi-Fi access network 504, which includes a trusted Wi-Fi access point 504c and an untrusted Wi-Fi access point 504d. The Wi-Fi devices 504a and 504b may access either AP 504c or 504d. In the current network architecture, each“G” has a core network. 2G circuit core network 505 includes a 2G MSC/VLR; 2G/3G packet core network 506 includes an SGSN/GGSN (for EDGE or UMTS packet traffic); 3G circuit core 507 includes a 3G MSC/VLR; 4G circuit core 508 includes an evolved packet core (EPC); and in some embodiments the Wi-Fi access network may be connected via an ePDG/TTG using S2a/S2b. Each of these nodes are connected via a number of different protocols and interfaces, as shown, to other, non-“G”-specific network nodes, such as the SCP 530, the SMSC 531, PCRF 532, HLR/HSS 533, Authentication, Authorization, and Accounting server (AAA) 534, and IP Multimedia Subsystem (IMS) 535. An HeMS/AAA 536 is present in some cases for use by the 3G UTRAN. The diagram is used to indicate schematically the basic functions of each network as known to one of skill in the art, and is not intended to be exhaustive. For example, 5G core 517 is shown using a single interface to 5G access 516, although in some cases 5G access can be supported using dual connectivity or via a non- standalone deployment architecture.

[0069] Noteworthy is that the RANs 501, 502, 503, 504 and 536 rely on specialized core networks 505, 506, 507, 508, 509, 537 but share essential management databases 530, 531, 532, 533, 534, 535, 538. More specifically, for the 2G GERAN, a BSC 501c is required for Abis compatibility with BTS 501b, while for the 3G UTRAN, an RNC 502c is required for Iub compatibility and an FGW 502d is required for Iuh compatibility. These core network functions are separate because each RAT uses different methods and techniques. On the right side of the diagram are disparate functions that are shared by each of the separate RAT core networks. These shared functions include, e.g., PCRF policy functions, AAA authentication functions, and the like. Letters on the lines indicate well-defined interfaces and protocols for communication between the identified nodes.

[0070] The system may include 5G equipment. 5G networks are digital cellular networks, in which the service area covered by providers is divided into a collection of small geographical areas called cells. Analog signals representing sounds and images are digitized in the phone, converted by an analog to digital converter and transmitted as a stream of bits. All the 5G wireless devices in a cell communicate by radio waves with a local antenna array and low power automated transceiver (transmitter and receiver) in the cell, over frequency channels assigned by the transceiver from a common pool of frequencies, which are reused in geographically separated cells. The local antennas are connected with the telephone network and the Internet by a high bandwidth optical fiber or wireless backhaul connection.

[0071] 5G uses millimeter waves which have shorter range than microwaves, therefore the cells are limited to smaller size. Millimeter wave antennas are smaller than the large antennas used in previous cellular networks. They are only a few inches (several centimeters) long. Another technique used for increasing the data rate is massive MIMO (multiple-input multiple-output). Each cell will have multiple antennas communicating with the wireless device, received by multiple antennas in the device, thus multiple bitstreams of data will be transmitted simultaneously, in parallel. In a technique called beamforming the base station computer will continuously calculate the best route for radio waves to reach each wireless device, and will organize multiple antennas to work together as phased arrays to create beams of millimeter waves to reach the device.

[0072] FIG. 6 is an enhanced eNodeB for performing the methods described herein, in accordance with some embodiments. Mesh network node 600 may include processor 602, processor memory 604 in communication with the processor, baseband processor 606, and baseband processor memory 608 in communication with the baseband processor. Mesh network node 600 may also include first radio transceiver 612 and second radio transceiver 614, internal universal serial bus (USB) port 616, and subscriber information module card (SIM card) 618 coupled to USB port 616. In some embodiments, the second radio transceiver 614 itself may be coupled to USB port 616, and communications from the baseband processor may be passed through USB port 616. The second radio transceiver may be used for wirelessly backhauling eNodeB 600.

[0073] Processor 602 and baseband processor 606 are in communication with one another. Processor 602 may perform routing functions, and may determine if/when a switch in network configuration is needed. Baseband processor 606 may generate and receive radio signals for both radio transceivers 612 and 614, based on instructions from processor 602. In some embodiments, processors 602 and 606 may be on the same physical logic board. In other embodiments, they may be on separate logic boards.

[0074] Processor 602 may identify the appropriate network configuration, and may perform routing of packets from one network interface to another accordingly. Processor 602 may use memory 604, in particular to store a routing table to be used for routing packets. Baseband processor 606 may perform operations to generate the radio frequency signals for transmission or retransmission by both transceivers 610 and 612. Baseband processor 606 may also perform operations to decode signals received by transceivers 612 and 614. Baseband processor 606 may use memory 608 to perform these tasks.

[0075] The first radio transceiver 612 may be a radio transceiver capable of providing LTE eNodeB functionality, and may be capable of higher power and multi-channel OFDMA. The second radio transceiver 614 may be a radio transceiver capable of providing LTE UE functionality. Both transceivers 612 and 614 may be capable of receiving and transmitting on one or more LTE bands. In some embodiments, either or both of transceivers 612 and 614 may be capable of providing both LTE eNodeB and LTE UE functionality. Transceiver 612 may be coupled to processor 602 via a Peripheral Component Interconnect-Express (PCI-E) bus, and/or via a daughtercard. As transceiver 614 is for providing LTE UE functionality, in effect emulating a user equipment, it may be connected via the same or different PCI-E bus, or by a USB bus, and may also be coupled to SIM card 618. First transceiver 612 may be coupled to first radio frequency (RF) chain (filter, amplifier, antenna) 622, and second transceiver 614 may be coupled to second RF chain (filter, amplifier, antenna) 624.

[0076] SIM card 618 may provide information required for authenticating the simulated UE to the evolved packet core (EPC). When no access to an operator EPC is available, a local EPC may be used, or another local EPC on the network may be used. This information may be stored within the SIM card, and may include one or more of an international mobile equipment identity (IMEI), international mobile subscriber identity (IMSI), or other parameter needed to identify a UE. Special parameters may also be stored in the SIM card or provided by the processor during processing to identify to a target eNodeB that device 600 is not an ordinary UE but instead is a special UE for providing backhaul to device 600.

[0077] Wired backhaul or wireless backhaul may be used. Wired backhaul may be an Ethernet-based backhaul (including Gigabit Ethernet), or a fiber-optic backhaul connection, or a cable-based backhaul connection, in some embodiments. Additionally, wireless backhaul may be provided in addition to wireless transceivers 612 and 614, which may be Wi-Fi 802.1 la/b/g/n/ac/ad/ah, Wi-Fi 5, Wi-Fi 6, any other Wi-Fi,

Bluetooth, ZigBee, microwave (including line-of-sight microwave), or another wireless backhaul connection. Any of the wired and wireless connections described herein may be used flexibly for either access (providing a network connection to UEs) or backhaul (providing a mesh link or providing a link to a gateway or core network), according to identified network conditions and needs, and may be under the control of processor 602 for reconfiguration.

[0078] A GPS module 630 may also be included, and may be in communication with a GPS antenna 632 for providing GPS coordinates, as described herein. When mounted in a vehicle, the GPS antenna may be located on the exterior of the vehicle pointing upward, for receiving signals from overhead without being blocked by the bulk of the vehicle or the skin of the vehicle. Automatic neighbor relations (ANR.) module 632 may also be present and may run on processor 602 or on another processor, or may be located within another device, according to the methods and procedures described herein.

[0079] Other elements and/or modules may also be included, such as a home eNodeB, a local gateway (LGW), a self-organizing network (SON) module, or another module. Additional radio amplifiers, radio transceivers and/or wired network connections may also be included.

[0080] FIG. 7 is a coordinating server for providing services and performing methods as described herein, in accordance with some embodiments. Coordinating server 700 includes processor 702 and memory 704, which are configured to provide the functions described herein. Also present are radio access network coordination/routing (RAN Coordination and routing) module 706, including ANR module 706a, RAN configuration module 708, and RAN proxying module 710. The ANR module 706a may perform the ANR tracking, PCI disambiguation, ECGI requesting, and GPS coalescing and tracking as described herein, in coordination with RAN coordination module 706 (e.g., for requesting ECGIs, etc.). In some embodiments, coordinating server 700 may coordinate multiple RANs using coordination module 706. In some embodiments, coordination server may also provide proxying, routing virtualization and RAN virtualization, via modules 710 and 708. In some embodiments, a downstream network interface 712 is provided for interfacing with the RANs, which may be a radio interface (e.g., LTE), and an upstream network interface 714 is provided for interfacing with the core network, which may be either a radio interface (e.g., LTE) or a wired interface (e.g., Ethernet).

[0081] Coordinator 700 includes local evolved packet core (EPC) module 720, for authenticating users, storing and caching priority profile information, and performing other EPC-dependent functions when no backhaul link is available. Local EPC 720 may include local HSS 722, local MME 724, local SGW 726, and local PGW 728, as well as other modules. Local EPC 720 may incorporate these modules as software modules, processes, or containers. Local EPC 720 may alternatively incorporate these modules as a small number of monolithic software processes. Modules 706, 708, 710 and local EPC 720 may each run on processor 702 or on another processor, or may be located within another device.

[0082] In any of the scenarios described herein, where processing may be performed at the cell, the processing may also be performed in coordination with a cloud coordination server. A mesh node may be an eNodeB. An eNodeB may be in communication with the cloud coordination server via an X2 protocol connection, or another connection. The eNodeB may perform inter-cell coordination via the cloud communication server, when other cells are in communication with the cloud coordination server. The eNodeB may communicate with the cloud coordination server to determine whether the UE has the ability to support a handover to Wi-Fi, e.g., in a heterogeneous network.

[0083] Although the methods above are described as separate embodiments, one of skill in the art would understand that it would be possible and desirable to combine several of the above methods into a single embodiment, or to combine disparate methods into a single embodiment. For example, all of the above methods could be combined. In the scenarios where multiple embodiments are described, the methods could be combined in sequential order, or in various orders as necessary.

[0084] Although the above systems and methods for providing interference mitigation are described in reference to the Long Term Evolution (LTE) standard, one of skill in the art would understand that these systems and methods could be adapted for use with other wireless standards or versions thereof. The inventors have understood and appreciated that the present disclosure could be used in conjunction with various network

architectures and technologies. Wherever a 4G technology is described, the inventors have understood that other RATs have similar equivalents, such as a gNodeB for 5G equivalent of eNB. Wherever an MME is described, the MME could be a 3G RNC or a 5G AMF/SMF. Additionally, wherever an MME is described, any other node in the core network could be managed in much the same way or in an equivalent or analogous way, for example, multiple connections to 4G EPC PGWs or SGWs, or any other node for any other RAT, could be periodically evaluated for health and otherwise monitored, and the other aspects of the present disclosure could be made to apply, in a way that would be understood by one having skill in the art.

[0085] Additionally, the inventors have understood and appreciated that it is

advantageous to perform certain functions at a coordination server, such as the Parallel Wireless HetNet Gateway, which performs virtualization of the RAN towards the core and vice versa, so that the core functions may be statefully proxied through the coordination server to enable the RAN to have reduced complexity. Therefore, at least four scenarios are described: (1) the selection of an MME or core node at the base station; (2) the selection of an MME or core node at a coordinating server such as a virtual radio network controller gateway (VRNCGW); (3) the selection of an MME or core node at the base station that is connected to a 5G-capable core network (either a 5G core network in a 5G standalone configuration, or a 4G core network in 5G non-standalone configuration); (4) the selection of an MME or core node at a coordinating server that is connected to a 5G-capable core network (either 5G SA or NSA). In some embodiments, the core network RAT is obscured or virtualized towards the RAN such that the coordination server and not the base station is performing the functions described herein, e.g., the health management functions, to ensure that the RAN is always connected to an appropriate core network node. Different protocols other than SI AP, or the same protocol, could be used, in some embodiments.

[0086] In some embodiments, the software needed for implementing the methods and procedures described herein may be implemented in a high level procedural or an object- oriented language such as C, C++, C#, Python, Java, or Perl. The software may also be implemented in assembly language if desired. Packet processing implemented in a network device can include any processing determined by the context. For example, packet processing may involve high-level data link control (HDLC) framing, header compression, and/or encryption. In some embodiments, software that, when executed, causes a device to perform the methods described herein may be stored on a computer- readable medium such as read-only memory (ROM), programmable-read-only memory (PROM), electrically erasable programmable-read-only memory (EEPROM), flash memory, or a magnetic disk that is readable by a general or special purpose-processing unit to perform the processes described in this document. The processors can include any microprocessor (single or multiple core), system on chip (SoC), microcontroller, digital signal processor (DSP), graphics processing unit (GPU), or any other integrated circuit capable of processing instructions such as an x86 microprocessor.

[0087] In some embodiments, the radio transceivers described herein may be base stations compatible with a Long Term Evolution (LTE) radio transmission protocol or air interface. The LTE-compatible base stations may be eNodeBs. In addition to supporting the LTE protocol, the base stations may also support other air interfaces, such as

UMTS/HSPA, CDMA/CDMA2000, GSM/EDGE, GPRS, EVDO, 2G, 3G, 5G, legacy TDD, or other air interfaces used for mobile telephony.

[0088] In some embodiments, the base stations described herein may support Wi-Fi air interfaces, which may include one or more of IEEE 802.1 la/b/g/n/ac/af/p/h, Wi-Fi 5, Wi Fi 6, etc. In some embodiments, the base stations described herein may support IEEE 802.16 (WiMAX), to LTE transmissions in unlicensed frequency bands (e.g., LTE-U, Licensed Access or LA-LTE), to LTE transmissions using dynamic spectrum access (DSA), to radio transceivers for ZigBee, Bluetooth, or other radio frequency protocols, or other air interfaces.

[0089] The foregoing discussion discloses and describes merely exemplary embodiments of the present invention. In some embodiments, software that, when executed, causes a device to perform the methods described herein may be stored on a computer-readable medium such as a computer memory storage device, a hard disk, a flash drive, an optical disc, or the like. As will be understood by those skilled in the art, the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, wireless network topology can also apply to wired networks, optical networks, and the like. The methods may apply to LTE-compatible networks, to UMTS-compatible networks, or to networks for additional protocols that utilize radio frequency data transmission. Various components in the devices described herein may be added, removed, split across different devices, combined onto a single device, or substituted with those having the same or similar functionality.

[0090] Although the present disclosure has been described and illustrated in the foregoing example embodiments, it is understood that the present disclosure has been made only by way of example, and that numerous changes in the details of

implementation of the disclosure may be made without departing from the spirit and scope of the disclosure, which is limited only by the claims which follow. Various components in the devices described herein may be added, removed, or substituted with those having the same or similar functionality. Various steps as described in the figures and specification may be added or removed from the processes described herein, and the steps described may be performed in an alternative order, consistent with the spirit of the invention. Features of one embodiment may be used in another embodiment. Other embodiments are within the following claims.