Showing posts with label Operator Softbank. Show all posts
Showing posts with label Operator Softbank. Show all posts

Tuesday, 12 May 2026

Can Physical AI Finally Justify MEC and AI-RAN?

The telecoms industry has spent years searching for a use case that genuinely requires edge computing, ultra-low latency and a more intelligent RAN. Multi-access Edge Computing (MEC) has long been presented as a foundational element of future network architecture, yet many early deployments struggled to move beyond limited trials and niche applications. AI-RAN has followed a similar path. While the concept has generated significant industry interest, many operators have continued to question where the real commercial and technical value lies.

Recent demonstrations by SoftBank and Ericsson around network-enabled Physical AI suggest the industry may finally have found a use case that naturally brings these technologies together.

Unlike earlier MEC demonstrations focused on content delivery, video optimisation or traffic offload, Physical AI introduces a closed-loop interaction between robots, AI inference and the network itself. Rather than treating AI as an application that operates independently on top of the network, SoftBank is positioning AI as something that must be tightly integrated with connectivity, compute and radio infrastructure. This has important implications for MEC, distributed compute and the future evolution of telecoms infrastructure.

The concept behind Physical AI is relatively straightforward. Autonomous robots, drones and industrial systems need to perceive their environment, process information and make decisions in real time. Some AI inference can run locally on the device, but onboard compute is often constrained by size, thermal limits, cost and power consumption. More advanced AI models may require significantly more processing capability than can realistically be embedded into every endpoint.

SoftBank’s approach is to treat MEC as an extension of the robot’s compute environment. The network effectively becomes part of the control loop rather than simply acting as a transport layer between devices and the cloud.

This model requires a much tighter relationship between the RAN and application workloads than traditional mobile networks were originally designed to support. In conventional architectures, the RAN largely operates independently of application behaviour. SoftBank’s AI-RAN architecture, developed in collaboration with Ericsson, instead monitors radio conditions, compute availability and application requirements simultaneously. AI workloads can then move dynamically between the device and MEC infrastructure depending on latency, congestion and processing demands.

Ericsson’s role is particularly important because it demonstrates how differentiated connectivity becomes part of the AI execution framework itself. Network slicing, priority handling and RAN automation are integrated into the orchestration process so that the network can continuously adapt to changing AI workload requirements rather than relying on static QoS policies.

A robot performing real-time perception and navigation may initially process workloads locally. If additional compute power is required, inference tasks can be offloaded to nearby MEC resources. If network conditions deteriorate or latency increases, workloads may shift back onto the device. The network continuously orchestrates these decisions while attempting to maintain predictable, deterministic performance levels.

This is significantly different from the fixed slicing models often discussed during the early 5G era. Instead of static policies, the network dynamically adjusts connectivity and workload placement according to application behaviour and infrastructure conditions.

SoftBank’s broader strategy reinforces this direction through its Telco AI Cloud architecture, which combines GPU infrastructure, MEC platforms and RAN intelligence under a unified orchestration framework. The objective is to support AI workloads that span cloud, edge and endpoint devices across sectors such as industrial automation, logistics and construction.

A critical milestone in this development is the interworking between SoftBank’s AITRAS orchestrator and the Ericsson Intelligent Automation Platform (EIAP). This collaboration reflects a future where AI orchestration platforms and RAN automation systems operate through tightly integrated control and policy frameworks. By integrating these layers, the orchestrator can make informed decisions about where to place an AI workload based on a real-time view of the RAN’s capacity and health.

This shift highlights why many previous MEC deployments struggled to achieve large-scale commercial success. Early edge computing use cases rarely demanded strict latency guarantees or continuous workload mobility between device and edge. In many scenarios, centralised cloud platforms remained entirely sufficient.

Physical AI changes that. Real-time robotics and autonomous systems require predictable latency and continuous responsiveness. They also require the ability to distribute AI workloads dynamically across multiple compute domains without interrupting operations. Achieving this level of coordination demands a far deeper integration between MEC, AI orchestration and the RAN than most operators currently deploy.

If the network is expected to participate directly in AI execution and workload placement decisions, the RAN itself becomes part of the distributed AI infrastructure platform.

The implications for telecoms infrastructure are substantial. Operators aiming to support Physical AI applications may need to rethink network architecture around distributed compute rather than centralised capacity. MEC deployments would require tighter integration with radio infrastructure, orchestration systems and AI frameworks.

The industry has discussed this convergence for years through initiatives such as the AI-RAN Alliance and broader work around AI-native networking. What makes the SoftBank and Ericsson work particularly interesting is that it connects these ideas into a practical end-to-end implementation focused on real-world autonomous systems.

Physical AI may finally provide the commercial and technical justification the industry has been searching for to move MEC and AI RAN from research projects and isolated trials into mainstream network architecture. It hints at a future where operators are no longer simply connectivity providers, but providers of distributed AI infrastructure platforms capable of supporting real-time autonomous systems.

Related Posts

Monday, 5 October 2020

Softbank Demoed Drone Wireless Relay System

Back in 2016, I was involved with doing testing using drones and Helikite with the UK operator EE. You can read more about that here. Since then, many different operators have tested the use of drones mainly for disaster recovery kinds of scenarios. The Japanese operator Softbank recently tried the same.


The press release from them provided the following details:

When typhoons, earthquakes, landslides and other types of natural disasters strike, mobile phones serve as an important lifeline for people to get information and to stay in touch with their family, friends and colleagues. SoftBank Corp. recognizes the importance of restoring communications lifelines quickly, and is engaged in developing and building systems for disaster preparedness.

One such service restoration initiative SoftBank has been working on is the “Drone Wireless Relay System.” On August 31, 2020, SoftBank demonstrated the solution for the press at Katsuma Radio Control Airstrip in Ichihara City, Chiba Prefecture, just east of Tokyo.

Thanks to their portability and ease-of-use, drone-based wireless relay base stations are showing promise as a means of providing connectivity when outages occur in the wake of natural disasters. SoftBank has been working with theTokyo Institute of Technology (Tokyo Tech)’s Department of Electrical and Electronic Engineering since 2019 to conduct research on drone-based wireless relay systems that use a wired power feed.

SoftBank’s drone-based relay base station rises to an altitude of 100 meters, covering a 10km radius. The drone can be transported in a small vehicle and is easy to set up. Compared to another SoftBank network recovery solution, the moored-balloon relay system, the time to deployment is much shorter. In addition, the wired power supply allows the drone to fly continuously for three days or longer, making it suitable for operations over the short- to medium-term.

The moored-balloon wireless relay system is capable of lifting wireless relay equipment to an altitude of 100 meters, covering a five-kilometer radius in open terrain. SoftBank 3G (mobile phone) (2.1 GHz band) voice communications and packet transmissions (email, Internet, etc.) can be used within the coverage area. We are also conducting trial tests of a new moored-balloon wireless relay system for SoftBank 4G LTE that can be deployable from ships, as part of our efforts to continuously improve this system.

A video from the recent drone event is as follows:

Related Posts:

Friday, 13 May 2016

Small Cells Deployment Stories


I recently got an opportunity to hear about the small cell deployment studies, organised as SCWS pre-conference workshop. The combined slides from the presentation are embedded below and available to download from Small Cell Forum page here.


Wednesday, 7 May 2014

Open, Closed and Hybrid Access Small Cells

A question that often keeps cropping up regularly is regarding the open access and closed access small cells. Before we look at the explanation of these cells, lets see the different types of cells (from 3GPP TS 36.304) in brief:

Acceptable cell: An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and receive ETWS and CMAS notifications).

Suitable cell: A "suitable cell" is a cell on which the UE may camp on to obtain normal service. It is mandatory for the UE to have a USIM card belonging to the operator to which this cell belongs.

Barred cell: A cell is "barred" if it is so indicated in the system information. Its not available for use by anyone.

Reserved cell: A cell is reserved if it is so indicated in system information. It is reserved for operator use only.

Restricted Cell: A cell on which camping is allowed, but access attempts are disallowed for UEs whose access classes are indicated as barred.

Camping on the cell: With the cell selection, the UE searches for a suitable cell of the selected PLMN and chooses that cell to provide available services, further the UE shall tune to its control channel. This choosing is known as "camping on the cell".

To keep the discussion simple, I have ignored that some UE's may belong to MVNO and the PLMN Id of the operator would be stored as Equivalent PLMN Id.



Now lets look at a simple explanation of the different types of small cells.

Open Access: All (suitable) cells are open access by default. This means that they can be accessed by any device belonging to the operator whom the cell belongs to. Some people also refer to these cells as Open Subscriber Group (OSG) cells.

Closed Access: A (suitable) cell is closed when only certain devices can camp on them. These devices form a part of whitelist stored in a database to allow camping on the cell. Devices that are not part of the whitelist are not allowed to camp on this cell, even though they belong to the same operator and this cell is a suitable cell. The devices are said to belong to ‘Closed Subscriber Group’ (CSG). The cell is said to be a CSG cell as its transmitting CSG Indication set to 'true' and the CSG Identity.

Residential Femtocells are generally Closed Access but there are exceptions. Softbank, Japan for example gives open access Femtocells that can also provide coverage to users nearby. Another example is the operator Free in France that also offers similar open access Femtocells.

Hybrid Access: A (suitable) cell can also be hybrid access, thereby allowing all devices that either belong to a CSG or non-CSG to camp onto it. A hybrid cell may offer prioritised and/or additional services to the users that belongs to the CSG it is a part of.

I am not aware of any Hybrid Access Small Cells deployment to date. Please feel free to correct me.