Edge platform: operator as edge compute provider
AI and AR/VR need compute close to the customer. Operator has unique edge (cell sites). By 2040 — distinct B2B revenue stream.
Discuss Your ChallengeWhat is an edge platform for the operator
Edge computing — compute capacity placed close to the end user (on cell site, region) for low-latency services. Not cloud (far datacentre), not device (limited resources). An intermediate layer.
Use cases:
- AR/VR — frame rendering needs <20ms latency that public cloud does not deliver.
- AI inference — real-time response for ML-heavy apps.
- IoT — local aggregation and control in a private network.
- Gaming — low-latency multiplayer.
- Autonomous systems — drones, robotics, vehicles.
Why the operator has an advantage
Real estate. Cell sites are already physically close to customers.
Spectrum. Operator is already a spectrum holder, can offer connectivity + compute as a bundle.
Customer access. Operator has billing relationships, identity verified.
Local presence. Hyperscalers (AWS Wavelength, Azure Edge) try to enter, but without local relationships are dependent on operator partnerships.
Business model
B2B primarily. Manufacturers with private 5G, healthcare with remote diagnostics, autonomous fleet operators, gaming studios.
B2C limited. Most consumer apps do not need edge to work — cloud is good enough.
Pricing — usage-based (compute time, bandwidth) + reservation (dedicated edge resources).
Where the cracks are
Hyperscaler partnerships — AWS Wavelength, Google Distributed Cloud Edge sit on operator infrastructure. Operator may become landlord (real estate provider), not platform owner.
Standardisation. Without edge orchestration standards each operator makes a proprietary solution. Partner adoption slow.
Capacity sizing — over-provision and unprofitable, under-provision and no demand.
What the operator should do now
Pilot 1-2 verticals (manufacturing, healthcare).
Partner with hyperscaler as distribution channel, but keep ownership of data and customer relationships.
Standards engagement — participate in industry consortia (3GPP edge, MEC).
Talent build — edge requires a skill set between network engineering and cloud.
Related
- /en/insights/future-telecom-2040/ — 2040
- /en/decisions/telecom-cloud-strategy/ — cloud
- /en/insights/future-telecom-network-as-a-service/ — NaaS
- /en/insights/telecom-5g-economics/ — 5G economics
What else is worth exploring
Topics from the same area we usually explore together
CRM
Not an off-the-shelf CRM, but a properly built customer management contour — from first contact to loyalty.
→SolutionBI
Analytics is not pretty charts on the wall. It's the answer to 'why?' before the problem becomes a loss.
→SolutionContact Center
The contact center is not a phone station — it's the point where a client decides: stay with you or leave. The question is how it's built…
→SolutionIntegrations
Integrations are invisible but critical. When they work — systems talk. When they don't — data is lost and people copy from window to…
→I do not just write about this. I can come in, examine your situation and design a solution for your specific landscape.
Discuss applying this →Ready to discuss your challenge?
Tell me what's not working or what needs to be built. First conversation — no obligations.
Usually respond within a few hours