What does EPC stand for, and what does it do?

EPC stands for Evolved Packet Core. It is the all-IP core network of an LTE system that connects the radio base stations your device talks to with the internet or a private data network.

Why is the EPC better suited to IoT than older cellular cores?

Older networks were built for voice calls first and data second, using circuit-switched designs. The EPC is packet-switched and all-IP from the start, so it efficiently handles the data-only traffic that IoT devices send.

What is the difference between the MME and the HSS?

The MME is the control-plane component that runs the live signaling — authenticating devices, setting up sessions, and managing mobility and paging. The HSS is the database it consults, storing each subscriber's identity, keys, and permissions.

Where does my IoT device get its IP address?

The PGW (Packet Data Network Gateway) assigns your device its IP address as it sets up the connection, either from a shared pool or as a static assignment.

How does knowing the EPC help me troubleshoot?

The components map directly to failure domains: a radio problem points to the eNodeB, an attach or authentication problem points to the MME/HSS, and a data-delivery problem points to the SGW/PGW. This lets you narrow down where an issue lives instead of guessing.

courses > Cellular IoT Foundations > Cellular network architecture and radio fundamentals

chapter 02

Cellular network architecture and radio fundamentals

2.1Evolved Packet Core (EPC)2.2Control plane vs. user plane: MME versus SGW and PGW 2.3Resource scheduling: How cellular networks allocate specific "resource blocks"

2.1

Evolved Packet Core (EPC)

TL;DR

Key takeaways

The EPC is the all-IP LTE core.

It sits between the radio base stations and the internet, and because it is packet-switched from the ground up, it is well-suited to data-only IoT traffic.

Five components do the work.

The eNodeB handles radio access, the MME handles control signaling, the HSS stores subscriber identity, the SGW routes local data, and the PGW is the gateway to the internet.

Signaling and data travel separate paths.

Data flows through the user plane (eNodeB → SGW → PGW), while signaling flows through the control plane (eNodeB → MME → HSS).

The MME enables IoT power saving.

Because it tracks which devices are asleep and when they wake, it is the component behind Power Saving Mode (PSM) and eDRX.

The PGW shapes your connectivity choices.

It assigns IP addresses and applies APN and QoS policies, so decisions like private vs. public APN are really PGW-configuration decisions.

Knowing the EPC is a diagnostic skill.

When a device won't attach, the components tell you whether to look at the radio (eNodeB), the signaling (MME/HSS), or the data path (SGW/PGW).

When your IoT device sends a simple temperature reading, that pulse of data triggers a high-speed relay race across a sophisticated infrastructure called the Evolved Packet Core (EPC) — the all-IP backbone of modern LTE networks. This lesson traces the path your data takes from the radio base station through the network core to the internet. By the end, you'll have the mental model needed to troubleshoot connection issues and optimize device performance with confidence.

What you'll learn

What the Evolved Packet Core (EPC) is and why it was built for data

The EPC is the "core network" — the infrastructure that sits between the radio base stations your device connects to and the internet or private data networks your data needs to reach. Introduced in the 3GPP Release 8 specification, it is an all-IP, packet-switched architecture, meaning there is no circuit-switched voice legacy baked in — everything is data packets from the start. Before LTE, cellular networks were built for voice calls first and data second; the EPC changed that completely. This matters for IoT because IoT devices almost never make voice calls — they send data — and the EPC was designed from the ground up to handle that traffic efficiently.

What the eNodeB does at the edge of the network

The eNodeB (Evolved Node B) is the base station — the cell tower your IoT device communicates with over the air. It handles the radio interface, managing everything from signal modulation to scheduling which devices get to transmit and when. In LTE, the eNodeB is smarter than its 2G and 3G predecessors: it makes many radio resource decisions locally, which reduces latency and improves efficiency. It connects to the core network through two separate interfaces — the S1-MME interface for control signaling and the S1-U interface for user data.

What the MME and HSS do to manage and authenticate devices

The MME (Mobility Management Entity) is the brain of the control plane. It handles all the signaling between your device and the network:

When a device powers on and tries to attach, the MME authenticates it, verifies its SIM credentials with the HSS, and sets up the data session.
It manages handovers when a device moves from one cell to another.
It handles paging — finding a device that is in an idle or power-saving state when the network needs to deliver data to it.
For IoT specifically, it supports Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX) by tracking which devices are asleep, for how long, and when they'll wake up.

The HSS (Home Subscriber Server) is the network's primary database of subscriber information. It stores the device's identity (the IMSI from the SIM), its authentication keys, its service profile, and its current location. When the MME needs to authenticate a device, it queries the HSS — think of the HSS as the network's "identity and permissions" database.

What the SGW and PGW do to route your data

The SGW (Serving Gateway) is the first stop for user data — the actual payload your device sends. It acts as a local data anchor, routing packets between the eNodeB and the PGW, managing the data-path switch during handovers so packets aren't lost, and buffering downlink data when a device is idle until the MME pages it awake.

The PGW (Packet Data Network Gateway) is where your device's data exits the cellular network and enters the internet or a private enterprise network. It assigns your device its IP address, enforces Quality of Service (QoS) policies, and handles charging and accounting. It's also where operators can apply traffic filtering, deep packet inspection, or route traffic through a private APN for security.

How data actually flows through the EPC

A simple transmission from your temperature sensor follows a clear path:

The device's modem transmits the data over the air to the eNodeB.
The eNodeB forwards it through the S1-U interface to the SGW.
The SGW routes it through the S5/S8 interface to the PGW.
The PGW applies any QoS or filtering policies, then forwards the packet to the internet, where it reaches your cloud platform.

Meanwhile, the signaling that set up this session — authentication, bearer establishment, security — flows through a parallel path: from the eNodeB through S1-MME to the MME, and from the MME to the HSS for credential verification. These components work as an integrated system, not isolated boxes.

quiz

Lesson 2.1 Self-assessment

1. What is the Evolved Packet Core (EPC)?

A. The radio antenna inside an IoT device

B. The all-IP core network that sits between the radio base stations and the internet

C. A type of SIM card used only for IoT devices

2. Which EPC component assigns your IoT device its IP address?

A. The eNodeB

B. The HSS (Home Subscriber Server)

C. The PGW (Packet Data Network Gateway)

3. In the EPC, which path does user data take from the device to the internet?

A. eNodeB → SGW → PGW → internet

B. eNodeB → MME → HSS → internet

C. eNodeB → PGW → MME → internet

faq

Frequently asked questions

next lesson

Control plane vs. user plane: MME versus SGW and PGW

Understand what the Control Plane and User Plane are, why they're separated, and what the MME, SGW, and PGW each do within their respective planes.

Start lesson