5G roadblock: labor

Thu Jan 2 14:09:05 UTC 2020

I know there are a couple companies doing it, but compute at the tower isn't going to go anywhere. It makes very little sense to put it at the tower when you can put it in one location per metro area. 

----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest-IX 
http://www.midwest-ix.com 

----- Original Message -----

From: "Brandon Butterworth" <brandon at rd.bbc.co.uk> 
To: jdambrosia at gmail.com 
Cc: "North American Network Operators Group" <nanog at nanog.org> 
Sent: Wednesday, January 1, 2020 9:35:15 AM 
Subject: Re: 5G roadblock: labor 

On Wed Jan 01, 2020 at 09:29:20AM -0500, jdambrosia at gmail.com wrote: 
> Given the deployment of Wi-Fi into so many different applications 
> - your statement that 5G is to "replace" WiFi seems overly ambitious 

We might think that but it is serious. They want to own it all 
and there is a small cabal of operators owning the spectrum so 
little room for new competitors. 

Here's a project we did exploring some of the ambition 
https://www.bbc.co.uk/rd/blog/2019-02-5g-mobile-augmented-reality-bath 

Previously we avoided the old Telco CDNs by sticking to regular 
Internet CDNs and building our own but edge compute (mobile CDN 
but a better name to compete with AWS) is more insidious as you 
may not be able to get the same result from CDNs out on the net. 

Either the content providers or the external CDNs they use will 
have to pay to use the mobile CDN. How they will scale that at all 
those sites will be interesting to see. 

> Perhaps preventing WiFi from further penetration is a better way 
> to look at it? 

If the mobile companies are providing the WiFi routers they can 
control it (see LTE WiFi attempt) and one day replace it with 
5G or 6G in all the things. If they make a better job of it than 
everyones devices fighting for 5GHz then they may succeed. 

brandon 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200102/a26afa49/attachment.html>