Wireless IoT Technologies and 4G Evolved Packet System (EPC): Complete 2026 Guide
Introduction Wireless IoT Technologies
Wireless IoT Technologies The Internet of Things (IoT) is transforming the way devices, machines, sensors and applications communicate with each other. From smart meters and industrial monitoring systems to connected vehicles and smart-city infrastructure, IoT networks enable billions of devices to exchange information with application platforms.
An IoT device may communicate with one or more IoT application servers and, in some deployments, with other IoT devices. Connectivity can be provided through wired or wireless technologies. However, wireless connectivity has become particularly important because it provides flexibility, scalability and mobility.
Several wireless technologies are available for IoT deployments. Some are standardized by the 3rd Generation Partnership Project (3GPP), while others are developed by organizations outside the 3GPP ecosystem.Wireless IoT Technologies
Examples of 3GPP wireless IoT technologies include:
LTE-M
NB-IoT
EC-GSM-IoT
Non-3GPP technologies include:
LoRaWAN
Wi-Fi
Zigbee
Bluetooth
Among these technologies, LTE-M and NB-IoT have played a particularly important role in cellular IoT because they were specifically optimized for devices requiring low cost, low power consumption, extended coverage and massive scalability.

What Are Wireless IoT Technologies?
Wireless IoT technologies provide the communication link between IoT devices and the network infrastructure.
A typical IoT communication path can be represented as:
IoT Device → Wireless Network → Core Network → IoT Platform/Application Server
Depending on the technology and application, IoT traffic may be transported through a traditional user-plane connection or through optimized control-plane mechanisms.
The choice of wireless technology depends on several factors:
Required data rate
Device cost
Battery life
Coverage requirements
Mobility
Latency
Network scalability
Deployment environment
Application requirements
This is why a technology designed for smartphones is not necessarily the best choice for an IoT sensor.
3GPP and Non-3GPP Wireless IoT Technologies
The IoT ecosystem contains technologies from multiple standards organizations.
3GPP-Defined Technologies
3GPP has standardized several cellular IoT technologies, including:
Technology |
Major Characteristics |
LTE-M |
Higher data rate and mobility compared with NB-IoT |
NB-IoT |
Very low bandwidth, low power and extended coverage |
EC-GSM-IoT |
IoT enhancement based on GSM |
Non-3GPP Technologies
Other popular wireless IoT technologies include:
Technology |
Typical Strength |
LoRaWAN |
Long range and low power |
Wi-Fi |
High data rate and local connectivity |
Zigbee |
Low-power mesh networking |
Bluetooth |
Short-range device connectivity |
For cellular IoT, LTE-M and NB-IoT remain particularly important because they can leverage cellular network infrastructure and spectrum.
What Is LPWA IoT?
Low-Power Wide-Area IoT (LPWA IoT) is a category of IoT connectivity designed for devices that need:
Very low power consumption
Long battery life
Wide-area coverage
Low device cost
Small amounts of data
Large-scale deployment
Improved indoor and underground coverage
LTE-M, NB-IoT and LoRaWAN are commonly considered LPWA technologies.
Unlike smartphones, many LPWA devices do not need to continuously transmit large amounts of data.
For example, a smart water meter may only need to send a few measurements periodically.
The design objective is therefore not maximum throughput but efficient and reliable connectivity at extremely low device cost and power consumption.
LPWA IoT Use Cases
LPWA technologies are useful across many industries.
Smart Utilities
Examples include:
Smart electricity meters
Smart gas meters
Smart water meters
Logistics
IoT devices can be used for:
Asset tracking
Shipment monitoring
Location tracking
Condition monitoring
Industrial IoT
Industrial deployments can include:
Tank monitoring
Equipment monitoring
Environmental sensors
Industrial asset tracking
Smart Cities
Applications include:
Smart parking
Intelligent street lighting
Waste management
Environmental monitoring
Agriculture
IoT sensors can monitor:
Soil conditions
Livestock
Temperature
Humidity
Irrigation
Smart Buildings
Examples include:
Alarm systems
HVAC monitoring
Energy management
Occupancy sensing
Industrial IoT and 5G
Industrial IoT (IIoT) is another major area of wireless connectivity.
Unlike many LPWA applications, certain industrial applications require:
Very high reliability
Very low latency
High data rates
Precise synchronization
Deterministic communication
Examples include automated manufacturing, industrial robotics and real-time machine control.
These requirements are closely associated with the Ultra-Reliable Low-Latency Communications (URLLC) usage scenario of 5G.
As a result, the 3GPP NR radio interface is important for high-performance industrial IoT applications.
This also establishes an important evolution path:
LTE-M / NB-IoT → 5G IoT → Advanced 5G → 6G IoT
LTE vs LTE-M vs NB-IoT
LTE, LTE-M and NB-IoT share some fundamental cellular technologies but are optimized for different requirements.
All three technologies use OFDM-based radio interfaces and can operate within cellular network architectures.
However, their bandwidth, device complexity, data rate and mobility capabilities are significantly different.
Feature |
LTE |
LTE-M |
NB-IoT |
Primary Target |
Smartphones/Data |
IoT |
Massive IoT |
Maximum Channel Bandwidth |
20 MHz |
1.4 MHz |
200 kHz |
Typical Data Rate |
Mbps |
Hundreds of kbps |
Tens of kbps |
Device Complexity |
Higher |
Lower |
Very Low |
Power Consumption |
Higher |
Low |
Very Low |
Mobility |
Full |
Full |
Simplified |
Voice |
VoLTE |
Supported |
Generally not supported |
Duplex |
FDD/TDD |
FDD/TDD |
Half-duplex FDD |
LTE-M Channel Bandwidth
LTE-M was designed to reduce device complexity and bandwidth requirements while retaining many LTE capabilities.
An LTE-M device supports up to six physical resource blocks (PRBs).
Each PRB corresponds to 180 kHz, resulting in:
6 × 180 kHz = 1.08 MHz
When guard bands are considered, the LTE-M channel bandwidth is approximately 1.4 MHz.
This is significantly smaller than the 20 MHz bandwidth supported by conventional LTE devices.
NB-IoT Channel Bandwidth
NB-IoT takes bandwidth reduction even further.
An NB-IoT carrier occupies one PRB:
1 PRB = 180 kHz
Including the guard band, the channel bandwidth is approximately:
200 kHz
This narrowband operation helps simplify the device and reduce power and hardware requirements.
Device Complexity
Traditional LTE smartphones may use multiple antennas and RF chains.
LTE-M and NB-IoT devices can use much simpler hardware.
A simplified IoT device design can reduce:
RF complexity
Baseband processing requirements
Device size
Manufacturing cost
Power consumption
This is particularly valuable when millions of sensors need to be deployed.
Power Saving in LTE-M and NB-IoT
Battery life is one of the most important considerations for IoT devices.
Many IoT sensors may be installed in locations where replacing batteries frequently is impractical.
Two important mechanisms help cellular IoT devices save energy:
Power Saving Mode — PSM
Power Saving Mode (PSM) allows the device to enter a deep power-saving state.
While in PSM, the device does not continuously monitor paging messages.
This can significantly reduce energy consumption.
Extended Discontinuous Reception — eDRX
eDRX increases the time between successive monitoring opportunities.
Instead of continuously monitoring control information, the device can remain inactive for longer periods.
Together, PSM and eDRX can substantially increase battery life.
LTE-M vs NB-IoT Data Rates
The simplified bandwidth and processing capabilities of LTE-M and NB-IoT naturally restrict their achievable data rates.
Traditional LTE can provide Mbps or even tens of Mbps depending on network conditions and configuration.
LTE-M is designed for significantly lower data rates, commonly in the hundreds-of-kbps range.
NB-IoT is optimized for even smaller data volumes and generally supports data rates in the tens-of-kbps range.
Therefore:
LTE → High Data Rate
LTE-M → Moderate IoT Data Rate
NB-IoT → Low Data Rate / Massive IoT
Duplexing in LTE, LTE-M and NB-IoT
Duplexing determines how uplink and downlink transmissions share spectrum.
Full-Duplex FDD
In Frequency Division Duplexing (FDD), separate frequency resources are used for uplink and downlink.
Transmission and reception can occur simultaneously.
TDD
Time Division Duplexing uses the same spectrum for uplink and downlink but separates transmissions in time.
Half-Duplex FDD
NB-IoT can use half-duplex FDD.
The device does not need to transmit and receive simultaneously.
This simplifies RF implementation and can reduce device complexity and cost.
Mobility: LTE vs LTE-M vs NB-IoT
Mobility management is another important difference.
LTE and LTE-M support full mobility, including handover procedures while a device is in the connected state.
A conventional handover can involve:
Measurement reporting
Serving-cell evaluation
Target-cell resource preparation
Handover command
UE connection to the target cell
NB-IoT uses a simplified mobility approach.
Instead of the complete conventional handover procedure, NB-IoT can use cell reselection, reducing processing requirements for the IoT device.
What Is the 4G Evolved Packet System?
The Evolved Packet System (EPS) is the core architecture used by LTE networks.
It consists primarily of:
UE + E-UTRAN + EPC
The Evolved Universal Terrestrial Radio Access Network (E-UTRAN) contains evolved NodeBs (eNBs).
The EPC provides core-network functions required to connect users and devices to external packet networks.
A simplified architecture is:
UE → eNB → S-GW → P-GW → IP Network
Control and subscriber-management functions interact with components such as the MME and HSS.
Major Components of 4G EPC
The major EPC components include:
MME
S-GW
P-GW
HSS
PCRF
Each component performs a specific role.
Mobility Management Entity — MME
The Mobility Management Entity (MME) is a key control-plane component.
Its responsibilities include:
NAS signaling
Authentication
Mobility management
UE location tracking
EPS bearer establishment
Paging
Interaction with the HSS
During the LTE attach procedure, the MME obtains authentication information from the HSS and participates in mutual authentication.
The MME also works with other EPC components to establish the necessary EPS bearer for user traffic.
Serving Gateway — S-GW
The Serving Gateway (S-GW) primarily handles user-plane traffic.
One of its important roles is acting as a local mobility anchor.
When a UE moves between eNBs, the S-GW helps maintain user-plane connectivity.
The S-GW also buffers downlink traffic when a UE is temporarily idle.
Packet Data Network Gateway — P-GW
The P-GW provides connectivity between the EPC and external packet networks.
Its responsibilities can include:
IP address allocation
External network connectivity
Packet forwarding
Policy enforcement
Traffic from the Internet or another external network reaches the P-GW before being forwarded toward the appropriate S-GW.
Home Subscriber Server — HSS
The HSS maintains subscriber information.
It supports the MME during authentication and stores information required for subscriber and network services.
For IoT deployments, the HSS can also store information associated with IoT device triggering and serving network nodes.
PCRF and Policy Control
The Policy and Charging Rules Function (PCRF) is part of the Policy and Charging Control framework.
It helps determine appropriate QoS and charging policies.
The PCRF can translate application-level requirements into LTE-specific QoS parameters.
The resulting policies can influence how an EPS bearer is established and managed.
How Does IoT Traffic Travel Through EPC?
One of the most interesting aspects of cellular IoT is that IoT traffic does not have to use only one transport mechanism.
There are multiple approaches.
The major choices include:
User-plane transport
Control-plane transport
SMS-based transport
IP-based transport
Non-IP Data Delivery
User-Plane IoT Data Transport
In the user-plane approach, IoT traffic travels through an EPS bearer.
A simplified path is:
IoT UE → eNB → S-GW → P-GW → External Network
This approach is generally suitable when the IoT application needs to transfer larger amounts of data.
Control-Plane IoT Data Transport
For small amounts of data, using the control plane can be more efficient.
In this model, IoT data is carried inside NAS signaling.
The NAS message is transported between the UE and MME and is encapsulated within RRC signaling over the radio interface.
This approach can reduce the overhead associated with establishing and maintaining a traditional user-plane path for very small data transfers.
SMS-Based IoT Communication
SMS can also be used for IoT traffic.
LTE networks can support SMS delivery using:
NAS signaling
IMS
When NAS signaling is used, communication occurs between the UE and MME.
When IMS is used, the SMS-related traffic can be transported using IP connectivity and an EPS bearer.
IP-Based vs Non-IP IoT Traffic
Not every IoT device needs a complete IP protocol stack.
This is particularly important for simple, constrained devices.
IP-Based Data
With IP-based communication:
IoT Data → IP Packet → Cellular Network → IoT Server
The network can allocate an IP address to the device.
Non-IP Data Delivery
With Non-IP Data Delivery (NIDD), the device can send IoT data without requiring traditional IP connectivity.
This can reduce protocol overhead and simplify connectivity for constrained IoT devices.
IoT-Centric EPC Architecture
3GPP introduced additional network functions to provide more flexibility for IoT deployments.
Important components include:
SCEF
SCS
MTC-IWF
MTC Application Server
These components help operators provide specialized IoT services and expose network capabilities to applications.
What Is an MTC Application Server?
The Machine-Type Communication Application Server (MTC AS) is an application-side system that communicates with IoT devices.
For example, an IoT device might periodically send:
Temperature
Pressure
Water level
Energy consumption
Location
Equipment status
The application server receives and processes these measurements.
IoT application traffic can use protocols such as:
CoAP
MQTT-SN
Standards organizations and industry groups such as oneM2M and OMA have also contributed to IoT application and service frameworks.
Direct and Indirect IoT Service Models
There are two broad service models.
Direct Model
In a direct model, IoT traffic can travel more directly between the network and the application server.
IoT Device → Cellular Network → Application Server
Indirect Model
In an indirect model, IoT traffic passes through a Service Capability Server (SCS).
IoT Device → Cellular Network → SCS → MTC Application Server
The SCS can provide additional value-added services.
For example, it may support device triggering and other IoT service capabilities.
What Is the SCEF?
The Service Capability Exposure Function (SCEF) is one of the important IoT-related functions in the cellular core network.
It securely exposes network services and capabilities to authorized application servers through APIs.
Major functions include:
API exposure
Authentication
Authorization
Non-IP Data Delivery
Policy enforcement
Traffic throttling
SCEF can therefore act as an important bridge between cellular network capabilities and IoT application platforms.
Non-IP Data Delivery Using SCEF
NIDD can use the SCEF for transporting IoT data.
A simplified architecture is:
IoT UE → eNB → MME → SCEF → SCS / Application Platform
The IoT device exchanges data through NAS signaling, while the SCEF handles communication toward the application-side service infrastructure.
This is useful for constrained IoT devices that do not require traditional IP connectivity.
What Is MTC-IWF?
The Machine-Type Communication Inter-Working Function (MTC-IWF) provides authorization and coordination for certain IoT service interactions.
One of its roles is supporting device triggering.
Depending on the deployment and required transport mechanism, the MTC-IWF can help select an appropriate network element, such as:
MME
IP Short Message Gateway (IP-SM-GW)
This allows IoT services to trigger devices using appropriate cellular mechanisms.
IoT Device Triggering
Device triggering is important for applications where the network or application server needs to cause an IoT device to initiate communication.
For example, an application may need to request a sensor to:
Wake up
Establish communication
Collect a measurement
Send the measurement to the application server
Return to a power-saving state
This approach is particularly valuable for battery-powered IoT devices.
LTE-M vs NB-IoT: Which One Should You Choose?
The answer depends on the application.
Choose LTE-M when you need:
Higher data rates
Mobility
More flexible IoT applications
Lower latency than NB-IoT
Voice support in suitable deployments
Broader functionality
Choose NB-IoT when you need:
Extremely low power consumption
Low-cost devices
Small data transfers
Deep coverage
Massive numbers of sensors
Simple device architecture
A useful rule of thumb is:
LTE-M = More capability and mobility
NB-IoT = Maximum simplicity and efficiency for small-data IoT
LTE-M vs NB-IoT Comparison
Parameter |
LTE-M |
NB-IoT |
Bandwidth |
Up to 1.4 MHz |
Around 200 kHz |
Data Rate |
Higher |
Lower |
Mobility |
Strong |
Simplified |
Voice |
Possible |
Generally not |
Device Complexity |
Low |
Very low |
Power Consumption |
Low |
Very low |
Coverage |
Extended |
Highly extended |
Application Type |
More interactive IoT |
Massive sensor deployments |
Typical Data |
Small to moderate |
Very small |
Best Fit |
Mobile/connected IoT |
Static sensors |
Why 4G EPC Matters for IoT
The EPC provides a mature cellular foundation for IoT connectivity.
It offers:
Subscriber management
Authentication
Mobility management
Packet routing
QoS
Policy control
IP connectivity
IoT-specific mechanisms
The addition of functions such as SCEF, SCS and MTC-IWF further extends the capabilities of the cellular core for machine-type communication.
Evolution from 4G IoT to 5G and 6G
Wireless IoT is evolving rapidly.
The progression can be viewed as:
2G/3G M2M → 4G LTE IoT → LTE-M/NB-IoT → 5G IoT → 5G Advanced → 6G IoT
4G cellular IoT technologies are particularly suitable for low-power, wide-area applications.
However, demanding industrial applications require capabilities beyond traditional LPWA connectivity.
5G introduces technologies and architectural capabilities designed for:
Ultra-low latency
High reliability
Massive IoT
Industrial automation
Private networks
Edge computing
Network slicing
Future 6G systems are expected to further integrate AI, sensing, distributed intelligence and advanced wireless connectivity.
Real-World Example: Smart Water Meter
Consider a smart water meter installed underground.
The device needs to:
Measure water consumption
Send readings periodically
Operate for several years on battery
Work in challenging coverage conditions
Transfer only a small amount of data
A conventional LTE smartphone-oriented connection would be excessive for this use case.
NB-IoT can be a better fit because it focuses on:
Low power + wide coverage + low data volume + low device complexity
The meter can periodically wake up, send its reading and return to a power-saving state.
Real-World Example: Asset Tracking
Consider a logistics company tracking valuable assets.
The tracker may need:
Periodic location updates
Mobility support
Moderate data transfer
Battery efficiency
LTE-M can be attractive because it provides more mobility and capability than NB-IoT while maintaining IoT-oriented power efficiency.
Key Benefits of Cellular IoT
Cellular IoT technologies provide several advantages:
1. Wide Coverage
Devices can operate over large geographic areas.
2. Operator Infrastructure
IoT deployments can leverage existing cellular infrastructure.
3. Security
Cellular networks provide standardized authentication and security mechanisms.
4. Scalability
The network can support large numbers of connected devices.
5. Mobility
LTE-M can support applications requiring device movement.
6. Low Power
PSM and eDRX can extend battery life.
7. IoT-Specific Core Functions
Functions such as SCEF and MTC-IWF enable specialized IoT services.
Challenges in Wireless IoT
Despite its benefits, IoT connectivity also presents challenges.
These include:
Massive device density
Battery replacement
Coverage in difficult environments
Network congestion
Device security
Data management
Interoperability
Long device lifecycles
Integration with cloud platforms
Network scalability
These challenges become even more important as IoT deployments move from thousands to millions or billions of connected devices.
The Role of IoT in 2026
In 2026, IoT is no longer limited to simple sensor connectivity.
Modern IoT ecosystems increasingly combine:
IoT + 5G + Edge Computing + AI + Cloud + Automation
For example, an industrial sensor may collect data through cellular IoT connectivity, send it to an edge platform, use AI to identify an abnormal condition and automatically trigger an industrial control process.
This convergence is creating new opportunities for telecom engineers and IoT professionals.
FAQs
What are the main 3GPP wireless IoT technologies?
Major cellular IoT technologies include LTE-M, NB-IoT and EC-GSM-IoT.
What is LPWA IoT?
LPWA IoT refers to low-power wide-area connectivity designed for low-cost devices that require long battery life, wide coverage and relatively small data transfers.
What is LTE-M?
LTE-M is a cellular IoT technology optimized for lower device complexity, power consumption and bandwidth while retaining capabilities such as mobility.
What is NB-IoT?
NB-IoT is a narrowband cellular IoT technology designed for highly power-efficient, low-data-rate and wide-area IoT applications.
What is EPC in 4G?
EPC stands for Evolved Packet Core. It is the core network architecture used with LTE and provides functions such as mobility management, authentication, packet routing and connectivity to external networks.
What is SCEF?
SCEF stands for Service Capability Exposure Function. It securely exposes selected cellular network capabilities to authorized application servers through APIs and supports functions such as NIDD.
What is NIDD?
NIDD stands for Non-IP Data Delivery. It enables IoT data to be transported without requiring conventional IP connectivity for the IoT device.
Is NB-IoT suitable for high-data-rate applications?
No. NB-IoT is optimized for small data transfers and power-efficient sensor applications rather than high-throughput applications.
Is LTE-M better than NB-IoT?
Neither is universally better. LTE-M is generally more suitable when mobility, higher data rates or broader capabilities are required, while NB-IoT is well suited to simple, low-data-rate and highly power-efficient deployments.
Conclusion
Wireless IoT technologies have become a fundamental part of modern telecommunications. LTE-M and NB-IoT address different requirements from traditional smartphone connectivity by focusing on low cost, low power consumption, extended coverage and massive device scalability.
The 4G Evolved Packet System provides the core network foundation required to connect these devices with external applications and services. Components such as the MME, S-GW, P-GW and HSS provide essential network functions, while IoT-specific capabilities such as SCEF, SCS and MTC-IWF introduce additional flexibility for IoT traffic and services.
The most important takeaway is that IoT connectivity is not based on a single architecture. Depending on the application, traffic can use the user plane, control plane, SMS, IP or Non-IP Data Delivery.
As the industry moves toward 5G Advanced and 6G, cellular IoT will increasingly converge with AI, edge computing, cloud platforms, private networks and industrial automation.
Understanding LTE-M, NB-IoT and the 4G EPC therefore provides an important foundation for anyone working toward a career in 5G, 6G, IoT, telecom networking and industrial connectivity.
Recommended External Resources
For technical readers, useful standards and industry resources include:
3GPP specifications — cellular standards for LTE, LTE-M, NB-IoT and 5G.
GSMA IoT resources — industry guidance and cellular IoT ecosystem information.
oneM2M — IoT service-layer standards.
Open Mobile Alliance (OMA) — IoT and device-management related specifications.
Suggested Internal Links
5G Technology Deep Dive Certification Course 2026
5G Core Network Training
5G Network Optimization in Depth
5G O-RAN Certification
5G/6G Non-Terrestrial Networks (NTN) Certification Program
4G/5G Protocol Testing & Log Analysis
4G/5G Automation with Python & AI
6G Essential Training & Certification




Comments