Cloud Computing 7 min read

MEC Deployment Scenarios, Standards, and Security Threats in 5G Edge Computing

The article explains how 5G mobile edge computing (MEC) can be deployed in wide‑area and local‑area scenarios, outlines the relevant ETSI and 3GPP standards, and discusses the security threats and protection measures associated with edge nodes and data handling.

Architects' Tech Alliance
Architects' Tech Alliance
Architects' Tech Alliance
MEC Deployment Scenarios, Standards, and Security Threats in 5G Edge Computing

Considering latency, cost, and enterprise data security, MEC (Mobile Edge Computing) deployment is mainly realized by placing edge nodes in aggregation data centers (wide‑area MEC) or in campus/industrial parks (local‑area MEC).

Wide‑area MEC supports ultra‑low‑latency services (sub‑1 ms round‑trip) over hundreds of kilometers, making 5G public‑network edge suitable for vertical industries such as cloud gaming, OTT, corporate connectivity, URLLC private networks, and dedicated enterprise lines. Deploying MEC in secure aggregation data centers is the dominant operator strategy.

Local‑area MEC is preferred for highly sensitive industries that require data to remain on‑premise. Typical use cases include remote control of port cranes, steel‑plant overhead cranes, and many manufacturing, petrochemical, education, and medical campus scenarios. Local MEC provides URLLC ultra‑low latency, local breakout (LBO) for traffic offload, and enhanced isolation/authentication to prevent unauthorized public‑network access, effectively creating a 5G private network.

Enterprise sub‑networks formed via DNN, network slicing, etc., allowing only authorized wireless terminals.

Device‑card binding and secondary AAA authentication to restrict access to specific terminals.

Broadcast of dedicated PLMN ID/NID or CAG ID from base stations to limit connections to enterprise devices.

Standards for MEC are defined by ETSI (platform, VM, API management) and 3GPP (integration with 5G core). ETSI places the UPF as the MEC data‑plane element, while 3GPP specifies interaction with core network functions.

China’s CCSA also issues the "5G Core Network Edge Computing Technical Requirements" and is researching security specifications for 5G edge computing.

Security threats to 5G MEC include compromise of rich compute, communication, and storage resources, leading to confidentiality, integrity, and availability breaches; physical security challenges due to unattended sites; and increased attack surface from massive, heterogeneous devices, enabling DDoS, malware, buffer overflows, and data theft.

Data stored or processed by MEC platforms faces risks of loss (hardware failure, attacks, lack of backup) and leakage (insufficient classification, missing encryption or masking, non‑compliant sharing). The article provides download links for a 5G Edge Computing Security Whitepaper and related research reports.

network architecturecloud computingedge computingsecurityMEC5G
Architects' Tech Alliance
Written by

Architects' Tech Alliance

Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.