Robots Atlas>ROBOTS ATLAS
Deployment

Edge Computing

2016ActivePublished: 21 October 2026Updated: 21 October 2026Published
Key innovation
Moving data processing out of the centralized cloud to near the data source (on the device or at the network edge), drastically reducing latency and dependence on the link to a data center.
Category
Deployment
Abstraction level
Paradigm
Operation level
DeploymentInferenceServing
Use cases
On-device AI inference (e.g. NVIDIA Jetson)Autonomous robotics and real-time controlInternet of Things (IoT) and Industry 4.0Autonomous vehiclesSmart cameras and computer visionSmart citiesPrivacy-preserving sensor data processing

How it works

Data is processed on the end device or on a nearby edge node (server, gateway, cloudlet), typically in a three-tier architecture: device — edge — cloud. As much computation as local resources allow is performed at the edge (filtering, aggregation, model inference), while only processed data or tasks requiring more power are sent to the cloud. This shortens response time and reduces the amount of data transmitted. In AI applications the model is compressed (quantization, distillation) so it fits within the constrained resources of the edge device and runs at acceptable latency.

Problem solved

The centralized cloud introduces latency, consumes network bandwidth and requires sending sensitive data to a remote data center. With the explosive growth of IoT devices and sensors, shipping all raw data to the cloud is costly and too slow for real-time applications.

Components

Edge deviceData source and site of on-device inference

End device (sensor, camera, robot, phone) that generates data and often performs local computation.

Edge node / serverIntermediate compute layer close to devices

Server, gateway or cloudlet near the devices that takes over part of the computation and data aggregation.

Cloud (backend)Heavy-compute tasks and global storage

Centralized data center handling tasks beyond the edge capacity and model training.

Orchestration layerManaging deployments and workload placement

Mechanisms deciding which tasks run on the device, at the edge, or in the cloud; managing model updates.

Implementation

Implementation pitfalls
Constrained device resourcesHigh

AI models must be compressed (quantization, distillation) to fit the edge memory and power budget.

Fix:Apply quantization, pruning and knowledge distillation; choose lightweight architectures.
Distributed security modelHigh

Data travels between many nodes, requiring cloud-independent encryption and a decentralized trust model.

Fix:End-to-end encryption, node authentication, network segmentation.
Orchestration and update complexityMedium

Managing deployments and model updates across thousands of heterogeneous devices is operationally hard.

Fix:Use edge orchestration platforms (e.g. KubeEdge) and OTA update mechanisms.

Evolution

Original paper · 2016 · IEEE Internet of Things Journal, 2016 · Weisong Shi
Edge Computing: Vision and Challenges
Weisong Shi, Jie Cao, Quan Zhang, Youhuizi Li, Lanyu Xu
1998
Content delivery networks (CDN)

First systems bringing content closer to users (e.g. Akamai) — the root of the edge idea.

2009
Cloudlet concept

M. Satyanarayanan et al. (Carnegie Mellon) introduce the cloudlet — a small edge data center for mobile applications.

2012
Fog computing

Cisco popularizes fog computing as an extension of the cloud toward the edge for IoT.

2014
ETSI Mobile Edge Computing and term popularization

ETSI establishes the Mobile Edge Computing group; Karim Arabi popularizes the term "edge computing" in an IEEE DAC 2014 keynote.

2014
NVIDIA Jetson TK1 — AI at the edge

The first Jetson module with an embedded GPU enables on-device AI inference, key for robotics.

2016
"Edge Computing: Vision and Challenges"
Inflection point

The paper by Shi et al. (IEEE IoT Journal) becomes the academic foundation for framing edge computing.

2017
Multi-access Edge Computing (MEC)

ETSI renames the standard from Mobile to Multi-access Edge Computing, extending it beyond cellular networks.

Compute bottleneck

Constrained edge-device resources

Edge devices have limited compute, memory and power budget, which constrains the size and complexity of the models that can run on them.

Parallelism

Parallelism level
Partially parallel

The workload is distributed across many independent edge devices and nodes.

Scope
Across devicesInference

Hardware requirements

Primary

Edge computing is a deployment paradigm independent of any specific hardware architecture.

Good fit

Embedded GPUs (e.g. NVIDIA Jetson) accelerate AI inference at the edge.

Good fit

Edge TPU-class accelerators are designed for energy-efficient inference at the edge.

Possible

Neuromorphic chips offer very low power draw, attractive for edge devices.