The deployment of outdoor small cell base stations has been inhibited by a number of complex issues: interference management between the macro and small cell layers, backhaul, traffic localization, logistics and cost of ownership. Major R&D spend has focused in recent years on small cells networks. Backhaul has received its share of that spending which I estimate at over $150 million during the last three years poured into new startup ventures and projects to design and commercialize 'small cell friendly' backhaul solutions.
Recently, I co-authored a report with Senza Fili Consulting that mapped the small cell backhaul space. What becomes apparent is that despite the different small cell wireless backhaul solutions available at the disposal of network operators there are fundamentally two technologies: non-line-of-sight (NLOS) and line-of-sight (LOS) solutions. Each of these solutions has their advantage and disadvantage. The investments have been on reducing the disadvantages of each category to reduce the barrier to small cell deployments.
LOS and NLOS solutions are diametrically opposed on the performance-usability continuum. Usability here means deep reach into the urban clutter where small cells are deployed. It also means ease of planning, installation and deployment.
LOS systems which operate in the microwave and millimeter wave bands provide far superior performance than NLOS systems which operate in sub-6 GHz bands. There's more bandwidth available in the higher frequency spectrum resulting in higher capacity. LOS systems have low latency on the order of a few hundred microseconds. They are also designed using well proven processes and techniques to achieve high link availability levels such as 99.99% of the time (or only 50 minute down time per year). On the other hand, LOS systems by definition requires clear, unobstructed path between the two end-nodes of the link which restricts the ability to reach a desired small cell location. Any future obstructions that arise can sever the backhaul link. This is no small problem in itself and I have seen many markets with extremely high density buildings rely on fiber backhaul for macrocells as LOS systems are prone to be blocked at some point.
NLOS systems on the other hand do not require clear, unobstructed path between the two link end-nodes. They will continue to operate despite at lower performance which can be managed through a design process prior to deployment. However, NLOS systems offer lower performance than LOS systems: lower capacity, higher latency and jitter, and lower link availability.
Figure 1 Small cell wireless backhaul systems differentiate along the performance-usability continuum
The disadvantages of either solution are inherent to baseline technologies and laws of physics. Mitigating these disadvantages is what vendors have focused on during the past three years. Today, we see two clear trends: attempts by LOS system vendors to improve usability and attempts by NLOS vendors to improve performance. Who will converge on the required solution for small cell deployments is still to be determined.
To improve usability, vendors of LOS systems began incorporating self-alignment features that allow the two end-nodes of a link to automatically align with minimal human intervention. Today, self-alignment is mechanical and it remains to be seen whether this provides a long-term solutions. But I don't think we are far from seeing one day electronic alignment that eliminates the chances of mechanical failure. As a further improvement to usability, LOS systems can be deployed in a relay configuration to reach deep into the urban clutter. The high capacity of these systems is well suited to carry traffic from multiple small cell in a relay configuration back to a main serving hub.
On the other hand, NLOS vendors have been working to implement techniques that improve performance. NLOS systems have limited capacity, mainly because they use narrow channel bandwidth (typically maximum of 20 MHz in licensed band; higher bandwidth are possible in unlicensed bands at a much increased risk of interference). NLOS also relies on MIMO to double the capacity, but MIMO is highly dependent on signal quality. MIMO also requires distinct propagation channels for its multiple streams which is difficult to achieve within the confines of a limited space. With respect to latency, it is often counted in the milliseconds. Finally, the link availability is a design factor that is governed by a large standard deviation. Hence, investment in this field has been towards hardening the NLOS solutions for carrier grade applications. Vendors have progressively increased the channel bandwidth and incorporated techniques to address the perennial nemesis of performance: interference. This includes beamforming antenna systems and interference cancellation among other techniques.
Small cells have triggered new innovations in the backhaul space because of unique requirements predicated by the deployment scenario. Both LOS and NLOS systems seek to converge on a workable tradeoff between performance and usability, but each is approaching the solution from a different route. Which solution will be there first may not matter as much as who gets to the right price point for total cost of ownership. In the meantime, there is no consensus by operators on a fixed set of performance requirements for outdoor small cells. Unless we can converge on a cost effective solution to a defined set of requirements, predictions for imminent massive outdoor small cells deployments will not be realized.
Looking for assistance in getting XRv 9000 operational on ESXi 6.5 I have tried different versions and feature sets of XRv 9000 version 6.5.3, to include the .ova and .iso.VRR, with VGA, non-VRR. Although the Cisco CSR 1000v installs without issues a...
Hi, We are facing issue with ASR 9904 line card. After power on line card status led is amber only and showing below errorRP/0/RSP0/CPU0:mes-ngl-pbx-pbx-cdi-1#0/RSP0/ADMIN0:Sep 19 15:14:28.524 UTC: canbus_driver: %PLATFORM-CANB_SERVER-3-ALARM_I...
How can I learn about ASR9K MPLS Label limits(LIB and LFIB max numbers).Is there any command to check on the device?
Are these limits changing with LCs and RSPs types.Is there any scaling document to get these values?
I want to learn about to 'Partially-programmed' errors at the output of command 'show l2vpn bridge-domain summary'. I can not find any related document about this part and how to troubleshoot if it is not equal to zero.
I am looking for...
Hi Friends, I have an ASR 1001(Cisco IOS XE Software, Version 03.16.01a.S/Cisco IOS Software Version 15.5(3)S1a).I checked it, but can't configure 'MPLS ldp', and no MPLS command under the interface. My question is which lowest release can ...