Fixed wireless access growth: To 20% homes by 2025

=======================================================================================

Download the additional file on the left for the PPT chart pack accompanying this report

=======================================================================================

Fixed wireless access growth forecast

Fixed Wireless Access (FWA) networks use a wireless “last mile” link for the final connection of a broadband service to homes and businesses, rather than a copper, fibre or coaxial cable into the building. Provided mostly by WISPs (Wireless Internet Service Providers) or mobile network operators (MNOs), these services come in a wide range of speeds, prices and technology architectures.

Some FWA services are just a short “drop” from a nearby pole or fibre-fed hub, while others can work over distances of several kilometres or more in rural and remote areas, sometimes with base station sites backhauled by additional wireless links. WISPs can either be independent specialists, or traditional fixed/cable operators extending reach into areas they cannot economically cover with wired broadband.

There is a fair amount of definitional vagueness about FWA. The most expansive definitions include cheap mobile hotspots (“Mi-Fi” devices) used in homes, or various types of enterprise IoT gateway, both of which could easily be classified in other market segments. Most service providers don’t give separate breakouts of deployments, while regulators and other industry bodies report patchy and largely inconsistent data.

Our view is that FWA is firstly about providing permanent broadband access to a specific location or premises. Primarily, this is for residential wireless access to the Internet and sometimes typical telco-provided services such as IPTV and voice telephony. In a business context, there may be a mix of wireless Internet access and connectivity to corporate networks such as VPNs, again provided to a specific location or building.

A subset of FWA relates to M2M usage, for instance private networks run by utility companies for controlling grid assets in the field. These are typically not Internet-connected at all, and so don’t fit most observers’ general definition of “broadband access”.

Usually, FWA will be marketed as a specific service and package by some sort of network provider, usually including the terminal equipment (“CPE” – customer premise equipment), rather than allowing the user to “bring their own” device. That said, lower-end (especially 4G) offers may be SIM-only deals intended to be used with generic (and unmanaged) portable hotspots.
There are some examples of private network FWA, such as a large caravan or trailer park with wireless access provided from a central point, and perhaps in future municipal or enterprise cellular networks giving fixed access to particular tenant structures on-site – for instance to hangars at an airport.

Enter your details below to request an extract of the report

FWA today

Today, fixed-wireless access (FWA) is used for perhaps 8-9% of broadband connections globally, although this varies significantly by definition, country and region. There are various use cases (see below), but generally FWA is deployed in areas without good fixed broadband options, or by mobile-only operators trying to add an additional fixed revenue stream, where they have spare capacity.

Fixed wireless internet access fits specific sectors and uses, rather than the overall market

FWA Use Cases

Source: STL Partners

FWA has traditionally been used in sparsely populated rural areas, where the economics of fixed broadband are untenable, especially in developing markets without existing fibre transport to towns and villages, or even copper in residential areas. Such networks have typically used unlicensed frequency bands, as there is limited interference – and little financial justification for expensive spectrum purchases. In most cases, such deployments use proprietary variants of Wi-Fi, or its ill-fated 2010-era sibling WiMAX.

Increasingly however, FWA is being used in more urban settings, and in more developed market scenarios – for example during the phase-out of older xDSL broadband, or in places with limited or no competition between fixed-network providers. Some cellular networks primarily intended for mobile broadband (MBB) have been used for fixed usage as well, especially if spare capacity has been available. 4G has already catalysed rapid growth of FWA in numerous markets, such as South Africa, Japan, Sri Lanka, Italy and the Philippines – and 5G is likely to make a further big difference in coming years. These mostly rely on licensed spectrum, typically the national bands owned by major MNOs. In some cases, specific bands are used for FWA use, rather than sharing with normal mobile broadband. This allows appropriate “dimensioning” of network elements, and clearer cost-accounting for management.

Historically, most FWA has required an external antenna and professional installation on each individual house, although it also gets deployed for multi-dwelling units (MDUs, i.e. apartment blocks) as well as some non-residential premises like shops and schools. More recently, self-installed indoor CPE with varying levels of price and sophistication has helped broaden the market, enabling customers to get terminals at retail stores or delivered direct to their home for immediate use.

Looking forward, the arrival of 5G mass-market equipment and larger swathes of mmWave and new mid-band spectrum – both licensed and unlicensed – is changing the landscape again, with the potential for fibre-rivalling speeds, sometimes at gigabit-grade.

Enter your details below to request an extract of the report

Table of contents

  • Executive Summary
  • Introduction
    • FWA today
    • Universal broadband as a goal
    • What’s changed in recent years?
    • What’s changed because of the pandemic?
  • The FWA market and use cases
    • Niche or mainstream? National or local?
    • Targeting key applications / user groups
  • FWA technology evolution
    • A broad array of options
    • Wi-Fi, WiMAX and close relatives
    • Using a mobile-primary network for FWA
    • 4G and 5G for WISPs
    • Other FWA options
    • Customer premise equipment: indoor or outdoor?
    • Spectrum implications and options
  • The new FWA value chain
    • Can MNOs use FWA to enter the fixed broadband market?
    • Reinventing the WISPs
    • Other value chain participants
    • Is satellite a rival waiting in the wings?
  • Commercial models and packages
    • Typical pricing and packages
    • Example FWA operators and plans
  • STL’s FWA market forecasts
    • Quantitative market sizing and forecast
    • High level market forecast
  • Conclusions
    • What will 5G deliver – and when and where?
  • Index

Open RAN: What should telcos do?

————————————————————————————————————–

Related webinar: Open RAN: What should telcos do?

In this webinar STL Partners addressed the three most important sub-components of Open RAN (open-RAN, vRAN and C-RAN) and how they interact to enable a new, virtualized, less vendor-dominated RAN ecosystem. The webinar covered:

* Why Open RAN matters – and why it will be about 4G (not 5G) in the short term
* Data-led overview of existing Open RAN initiatives and challenges
* Our recommended deployment strategies for operators
* What the vendors are up to – and how we expect that to change

Date: Tuesday 4th August 2020
Time: 4pm GMT

Access the video recording and presentation slides

————————————————————————————————————————————————————————-

For the report chart pack download the additional file on the left

What is the open RAN and why does it matter?

The open RAN’ encompasses a group of technological approaches that are designed to make the radio access network (RAN) more cost effective and flexible. It involves a shift away from traditional, proprietary radio hardware and network architectures, driven by single vendors, towards new, virtualised platforms and a more open vendor ecosystem.

Legacy RAN: single-vendor and inflexible

The traditional, legacy radio access network (RAN) uses dedicated hardware to deliver the baseband function (modulation and management of the frequency range used for cellular network transmission), along with proprietary interfaces (typically based on the Common Public Radio Interface (CPRI) standard) for the fronthaul from the baseband unit (BBU) to the remote radio unit (RRU) at the top of the transmitter mast.

Figure 1: Legacy RAN architecture

Source: STL Partners

This means that, typically, telcos have needed to buy the baseband and the radio from a single vendor, with the market presently dominated largely by the ‘big three’ (Ericsson, Huawei and Nokia), together with a smaller market share for Samsung and ZTE.

The architecture of the legacy RAN – with BBUs typically but not always at every cell site – has many limitations:

  • It is resource-intensive and energy-inefficient – employing a mass of redundant equipment operating at well below capacity most of the time, while consuming a lot of power
  • It is expensive, as telcos are obliged to purchase and operate a large inventory of physical kit from a limited number of suppliers, which keeps the prices high
  • It is inflexible, as telcos are unable to deploy to new and varied sites – e.g. macro-cells, small cells and micro-cells with different radios and frequency ranges – in an agile and cost-effective manner
  • It is more costly to manage and maintain, as there is less automation and more physical kit to support, requiring personnel to be sent out to remote sites
  • It is not very programmable to support the varied frequency, latency and bandwidth demands of different services.

Enter your details below to request an extract of the report

Moving to the open RAN: C-RAN, vRAN and open-RAN

There are now many distinct technologies and standards emerging in the radio access space that involve a shift away from traditional, proprietary radio hardware and network architectures, driven by single vendors, towards new, virtualised platforms and a more open vendor ecosystem.

We have adopted ‘the open RAN’ as an umbrella term which encompasses all of these technologies. Together, they are expected to make the RAN more cost effective and flexible. The three most important sub-components of the open RAN are C-RAN, vRAN and open-RAN.

Centralised RAN (C-RAN), also known as cloud RAN, involves distributing and centralising the baseband functionality across different telco edge, aggregation and core locations, and in the telco cloud, so that baseband processing for multiple sites can be carried out in different locations, nearer or further to the end user.

This enables more effective control and programming of capacity, latency, spectrum usage and service quality, including in support of 5G core-enabled technologies and services such as network slicing, URLLC, etc. In particular, baseband functionality can be split between more centralised sites (central baseband units – CU) and more distributed sites (distributed unit – DU) in much the same way, and for a similar purpose, as the split between centralised control planes and distributed user planes in the mobile core, as illustrated below:

Figure 2: Centralised RAN (C-RAN) architecture

Cloud RAN architecture

Source: STL Partners

Virtual RAN (vRAN) involves virtualising (and now also containerising) the BBU so that it is run as software on generic hardware (General Purpose Processing – GPP) platforms. This enables the baseband software and hardware, and even different components of them, to be supplied by different vendors.

Figure 3: Virtual RAN (vRAN) architecture

vRAN architecture

Source: STL Partners

Open-RANnote the hyphenation – involves replacing the vendor-proprietary interfaces between the BBU and the RRU with open standards. This enables BBUs (and parts thereof) from one or multiple vendors to interoperate with radios from other vendors, resulting in a fully disaggregated RAN:

Figure 4: Open-RAN architecture

Open-RAN architecture

Source: STL Partners

 

RAN terminology: clearing up confusion

You will have noticed that the technologies above have similar-sounding names and overlapping definitions. To add to potential confusion, they are often deployed together.

Figure 5: The open RAN Venn – How C-RAN, vRAN and open-RAN fit together

Open-RAN venn: open-RAN inside vRAN inside C-RAN

Source: STL Partners

As the above diagram illustrates, all forms of the open RAN involve C-RAN, but only a subset of C-RAN involves virtualisation of the baseband function (vRAN); and only a subset of vRAN involves disaggregation of the BBU and RRU (open-RAN).

To help eliminate ambiguity we are adopting the typographical convention ‘open-RAN’ to convey the narrower meaning: disaggregation of the BBU and RRU facilitated by open interfaces. Similarly, where we are dealing with deployments or architectures that involve vRAN and / or cloud RAN but not open-RAN in the narrower sense, we refer to those examples as ‘vRAN’ or ‘C-RAN’ as appropriate.

In the coming pages, we will investigate why open RAN matters, what telcos are doing about it – and what they should do next.

Table of contents

  • Executive summary
  • What is the open RAN and why does it matter?
    • Legacy RAN: single-vendor and inflexible
    • The open RAN: disaggregated and flexible
    • Terminology, initiatives & standards: clearing up confusion
  • What are the opportunities for open RAN?
    • Deployment in macro networks
    • Deployment in greenfield networks
    • Deployment in geographically-dispersed/under-served areas
    • Deployment to support consolidation of radio generations
    • Deployment to support capacity and coverage build-out
    • Deployment to support private and neutral host networks
  • How have operators deployed open RAN?
    • What are the operators doing?
    • How successful have deployments been?
  • How are vendors approaching open RAN?
    • Challenger RAN vendors: pushing for a revolution
    • Incumbent RAN vendors: resisting the open RAN
    • Are incumbent vendors taking the right approach?
  • How should operators do open RAN?
    • Step 1: Define the roadmap
    • Step 2: Implement
    • Step 3: Measure success
  • Conclusions
    • What next?

Enter your details below to request an extract of the report