Skip to main content
  1. Blog
  2. Article

Eduardo Aguilar Pelaez
on 2 April 2020

Edge AI in a 5G world – part 2: Why make cell towers smart?


This is part of a blog series on the impact that 5G and GPUs at the edge will have on the roll out of new AI solutions. You can read the other posts here.

Recap

In part 1 we talked about the industrial applications and benefits that 5G and fast compute at the edge will bring to AI products. In this part we will go deeper into how you can benefit from this new opportunity.

Photo by NASA

Embedded compute vs Cost

Decades of Moore’s Law have given us smartphones at a price we’re willing to pay but IoT devices need to be much cheaper than that. Adding today’s fastest CPUs or GPUs to IoT devices costs a significant amount which put a hard limit on what the market is currently willing to buy at scale.

The IoT devices that are currently on the market are usually underpowered and have limited connectivity. With 5G connectivity and shared compute resources at the Edge these constrained devices will soon be able to do much more.

For instance, adding a GPU to each IoT device for the purposes of AI model inference would mean a significant increase in the hardware bill of materials. This cost would be passed onto the consumer and because it is more expensive would drastically reduce the target audience. Instead, 5G allows for heavy computation to be offloaded to nearby shared GPUs and get a response with minimal latency.

We will dive into this approach in the next section.

AI training & ML operations

Creating a new AI product has two engineering aspects to it, namely; 

  1. Model training and
  2. Inference

Model training refers to the machine learning that is usually done with ‘labelled data’ or simulations. This has big data and compute requirements.

Once the model has been trained, the implementation and operations of the inference is where much of the complexity appears. This is where we will focus most on this post, and in particular on real-time AI solutions.

During this blog series we will keep these two in mind given that the input data of today needs to be kept for it to be used as the training data of tomorrow. 

To illustrate this further in the next blog we will do a gap analysis of the technical requirements for model training, AI operations, as well as new techniques available to overcome these.


Related posts


Pedro Lazzarotto
11 June 2026

AI at the edge: simplifying infrastructure with Cisco and Canonical

AI Article

Legacy infrastructure was not designed for the requirements of the AI era. While large-scale model training remains centralized in data centers, test-time inference is rapidly shifting to the edge to reduce latency and bandwidth consumption. This shift creates a new frontier for enterprise AI, but deploying at the edge introduces signific ...


estelacarmona
11 June 2026

The next era of telco clouds: get open infrastructure choice with Sylva and Canonical Kubernetes

5G Article

Achieving vendor neutrality in telco clouds requires an infrastructure layer that respects open standards, without wrapping them in rigid platform layers. By combining upstream alignment with up to 15 years of support longevity, Canonical’s approach to Sylva is built around a requirement that matters deeply to telcos: follow upstream clou ...


Benjamin Ryzman
9 June 2026

What is RDMA over Converged Ethernet (RoCE)?

AI Networking

Previous articles walked through RDMA (Remote Direct Memory Access) as a programming model and InfiniBand as the fabric that was built around it. Both led to the same conclusion, even if it was never stated outright: moving data, not compute, becomes the bottleneck once systems scale. So what happens when you want RDMA, but you’re ...