Overlapping private networks - an emerging challenge for spectrum management

This post originally appeared in September 2023 on my LinkedIn feed, which is now my main platform for both short posts and longer-form articles. It can be found here, along with the comment stream. Please follow / connect to me on LinkedIn, to receive regular updates (about 1-3 / week)

File this one under “high quality problems”!
 
We’re starting to see a trend towards multiple enterprise private 5G networks on the same site, or very close to each other. That has a lot of implications.

Various large campus-style environments such as ports, airports and maybe business parks, industrial zones and others in future, will need to deal with the coexistence of several company-specific #5G networks.

For instance, an airport might have different networks deployed at the gates for aircraft turnaround, in the baggage-handling area for machinery, across the ramp area for vehicles, in the terminals for neutral host access, and in maintenance hangars for IoT and AR/VR.

Importantly, these may be deployed, owned and run by *different* companies - the airport authority, airlines, baggage handlers and a contracted indoor service provider, perhaps. In addition there could be other nearby private networks outside the airport fence, for hotels, warehouses and car parks.

This is something I speculated about a few years ago (I dug out the slide below from early 2020), but it is now starting to become a reality.

This is likely to need some clever coordination in terms of #spectrum management, as well as other issues such as roaming/interconnect and perhaps numbering resources such as MNC codes as well. It may need new forms of #neutralhost or multi-tenant setups.
 
Yesterday I attended a workshop run by the UK’s UK Spectrum Policy Forum. While the main focus was on the 3.8-4.2GHz band and was under Chatham House rule (so I can't cover the specifics), one speaker has allowed me to discuss his comments directly.

Koen Mioulet from European private network association EUWENA gave an example of the Port of Rotterdam, which has 5 different terminals, 3000 businesses including large facilities run by 28 different chemical companies. It already has two #PrivateLTE networks, and 5G used on a "container exchange route" for vehickes, plus more possible networks on ships themselves. It is quite possible to imagine 10+ overlapping networks in future.
 
While the UK has 400MHz potentially available in 3.8-4.2GHz, some countries only have 50-100MHz for P5G. That would pose significant coordination challenges and may necessitate an "umbrella" network run by (in this case) the Port Authority or similar organisation. An added complexity is synchronisation, especially if each network is set up for different uplink/downlink splits for specific applications.

MNOs could be involved too, in roles from wholesale provision, down to just spectrum leasing. Whatever happens, regulators and others need to start thinking about this.

In the past I’ve half-jokingly suggested that a new 6G target metric should be to have “1000 networks per sq km” rather than the usual “million devices per sq km” or similar.

Maybe we should start with 10 or 100 nearby networks, but that joke is now looking like a real problem, albeit a healthy one for the private cellular industry.

 

 

Enterprise 5G - evolving bottom-up from small islands, not top-down from national networks

This post originally appeared on September 29 on my LinkedIn feed, which is now my main platform for both short posts and longer-form articles. It can be found here, along with the comment stream. Please follow / connect to me on LinkedIn, to receive regular updates (about 1-3 / week)

While the broad concept of #privatewireless seems to be getting a lot more awareness in the wider tech industry, some of the implications haven't quite fully landed yet.

I've had a couple of meetings recently where there was still a prevailing view that #5G evolution would continue to be "top-down", with major MNOs setting the agenda, especially for enterprise. The belief is that national "umbrella" networks would address all the various localised applications, such as #industry40 and #smartagriculture, or #v2x networks along roads.

Such a set-up would mean that the network "mothership" would need all sorts of cloud-native elements for orchestration, security and control systems, both at the telcos and their clients, which would be a boon for vendors expecting a direct correlation with the promised $xxx billions of 5G value, coming from URLLC capabilities, slicing and other features.

But what is happening is much more bottom-up. The most cutting-edge uses of 5G are happening at specific locations - whether that is standalone networks at factories, or new #neutralhost deployments in offices and hotels (more on NH's in my next post btw). We can expect Release 16/17/18 features to appear at a micro level, long before they're switched on for the macro domain.

And while these small local networks are sometimes being deployed by MNOs, they are often based on dedicated infrastructure, perhaps using different vendors to the main umbrella national networks. It's often the B2B units running the show, with a variety of partners, rather than the central core network team.

Other small islands are getting their networks built by integrators, towercos & infracos, inhouse teams, industrial solutions suppliers and assorted others. It's very heterogeneous.

And each island can be *small*. A port's 5G network might have huge value for the site's operator, but only have 100 SIMs in cameras and vehicles. There might be redundancy, but it won't need a datacentre full of kit. There's often going to be a lot of customisation, and unique combination of applications and integrations with other systems

So if you're a vendor pitching umbrella-grade solutions, you might need to rethink how to re-orient towards small islands instead.