M365Con 2027 – כנס אונליין חינמי · 11–22 Jan 2027 · 120 sessions m365con.net

Multi-access edge computing (MEC)

Concept

Multi-access edge computing places compute, storage and application hosting physically close to where data is generated, typically alongside a 5G network. It enables real-time processing without round trips to a distant cloud region.

✦ CONCEPTMulti-access edgecomputing (MEC)M365.FM
Title graphic: Multi-access edge computing (MEC) (Concept)

נושאים שנדונים גם

בפרק על Multi-access edge computing (MEC) עולים גם: Azure IoT Edge, Azure Private 5G Core, Azure Stack Edge, Network slicing, Private 5G ו-Edge computing.

Description

Multi-access edge computing (MEC) is a network architecture concept that places compute, storage and application hosting physically close to where data is generated, typically alongside a 5G network. It enables real-time processing without round trips to a distant cloud region. The term was formerly known as mobile edge computing. According to the source material, the concept is defined by ETSI and brings cloud computing and an IT service environment to the edge of cellular networks and, more generally, of any network. ETSI created an Industry Specification Group for it in 2014.

The core idea is to run applications and processing closer to users. Doing so reduces network congestion and improves application performance. MEC is designed to run at cellular base stations or other edge nodes. This lets operators deploy new services quickly and open their radio access network (RAN) to authorized third parties such as developers and content providers. Listed benefits include lower latency, reduced core signaling load and lower hosting cost.

The central component is a MEC application server that is integrated with the RAN. It offers compute, storage, connectivity and real-time RAN information in a multitenant hosting environment. Applications are delivered to this environment as virtual machine images or containers. Because the server sits at or near the network edge, applications can use local radio information and avoid sending every request across the wider network to a central data center.

Typical use cases named in the sources include computational offloading, content delivery and caching, mobile big data analytics, connected cars, smart venues, healthcare, smart grids and indoor positioning. A common thread across these scenarios is that responsiveness matters and that moving all data to a distant cloud region would add delay or cost. The same material notes that few applications had adopted MEC at the time of writing, and it names AWS Wavelength as the first larger-scale commercial MEC product.

In practice, deciding where to run a workload comes down to what needs to happen locally and what can wait for the cloud. The M365.FM episode "Cloud Latency and Edge Computing Strategy" frames this as a strategy of processing workloads at the edge, filtering out noise and sending only what matters to the cloud, which it says keeps systems responsive and cost-effective. The episode describes breaking through the latency wall by combining private 5G networks with MEC. In that picture, data processing moves even closer to where devices operate, often within the same building or campus, so that not every piece of data has to travel to a distant cloud.

The episode also explains the role of the private 5G network in this combination. A private 5G network gives a dedicated wireless network in which the operator controls who connects and how data flows. Together with MEC, this arrangement keeps both connectivity and processing local, while the cloud remains the destination for the data that is worth forwarding.

MEC therefore sits between devices and the central cloud as an intermediate tier. It does not replace cloud regions; it complements them by handling latency-sensitive or high-volume processing nearby and passing on filtered results. Teams evaluating the concept typically weigh the latency requirements of the application, the volume of data generated at the site, and the cost of transporting that data, which are the same considerations the episode raises when discussing responsiveness and cost-effectiveness.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Maintained by Mirko Peters (Microsoft MVP) · Last updated: