Emerging Technologies (IoT, SDN/NFV, Cloud, Edge)
This domain tests the vocabulary and design logic of newer architectures: how IoT devices connect, what SDN and NFV actually separate, how cloud service models differ, and why edge computing changes latency and backhaul economics.
IoT connectivity
- LPWAN options: NB-IoT uses a 180 kHz carrier in-band, guard-band or standalone, offers roughly 20 dB coverage improvement and supports PSM/eDRX for years of battery life, but very low throughput. LTE-M (eMTC) adds mobility and voice-capable rates; LoRa uses chirp spread spectrum in ISM bands; Sigfox is an ultra-narrowband alternative.
- Application protocols: MQTT (publish/subscribe over TCP), CoAP (REST-like over UDP), LwM2M for device management. Choice follows power, latency and reliability constraints, not fashion.
SDN, NFV and cloud
- SDN separates the control plane from the forwarding plane: a controller holds topology and policy, OpenFlow is a common southbound protocol, REST APIs face northbound. Benefit is centralised, programmable policy.
- NFV decouples network functions from dedicated hardware, running VNFs on virtual machines or containers. ETSI MANO comprises NFVO, VNFM and VIM; service chaining orders VNFs into a service.
- Cloud service models: IaaS (compute/storage), PaaS (runtime), SaaS (application). Deployment models include public, private and hybrid; containers and Kubernetes dominate orchestration.
- Edge/MEC places compute near the radio site, enabling local breakout, caching and low-latency services; end-to-end network slicing spans RAN, transport and core with per-slice SLAs and isolation.
Worked example
50,000 cameras stream 4 Mbit/s each; at 25% simultaneous viewing that is 12,500 × 4 Mbit/s = 50 Gbit/s, which a 10 Gbit/s central backhaul cannot carry. Processing at the edge and forwarding only events and metadata (say 100 Mbit/s aggregate) removes the backhaul upgrade; the analytics stay local while latency drops from tens of milliseconds to single digits. The decision is arithmetic plus latency, not a vendor preference.
Traps that cost marks
- Treating SDN and NFV as the same thing: one separates planes, the other virtualises functions.
- Choosing NB-IoT for video or high-rate telemetry - it is designed for low throughput and long battery life.
- Confusing MEC with private cloud: MEC is defined by proximity and latency, not ownership.
- Assuming a network slice is just a VPN; it requires orchestration, isolation and per-slice assurance.