The Telco Cloud Masterclass
from appliance boxes to a self-healing mesh
The complete cloudification journey — PNF → VNF → CNF — built verbatim from ETSI GS NFV, 3GPP, O-RAN and CNCF specifications. Every diagram, descriptor, interface and value is cited to its normative clause. Ten modules, forty-five animated lessons, hands-on labs.
Why we cloudified the network — PNF → VNF → CNF
A guided, fully-animated origin story: from welded-to-hardware appliances, through the 2012 ETSI NFV white paper, to the cloud-native mesh that 5G runs on.
ETSI GS NFV 002 · GS NFV 003 · 3GPP TS 23.501 §4 · O-RAN O-Cloud · CNCFThis module is part of the full course
You are watching the free preview.
Unlock the full course — $29 Back to the free moduleClassify the network function
Six real functions. Decide how each one is deployed today — and check yourself against the ETSI terminology in GS NFV 003.
PNF → VNF → CNF, explored
Click each stage to see how the network function is built — and what the standards call it.
The seven layers of a telco cloud
Bottom-up, from bare metal to OSS/BSS. Click a layer for its job and its spec.
PNF, VNF, CNF — defined by the standard
| Term | Full name | What it is | Runs on | Spec anchor |
|---|---|---|---|---|
| PNF | Physical Network Function | Software fused to dedicated, proprietary hardware — the classic appliance. | Its own vendor box | GS NFV 003 |
| VNF | Virtualized Network Function | The same NF software running as a virtual machine on a hypervisor. | NFVI (shared servers) | GS NFV 002 §7 |
| CNF | Cloud-Native Network Function | The NF decomposed into stateless microservices in containers. | Kubernetes / CaaS | GR NFV-IFA 029 |
Who defines the telco cloud
| Body | Owns | Key specs used in this course |
|---|---|---|
| ETSI NFV ISG | The NFV & MANO architecture | GS NFV 002/003 · GS NFV-MAN 001 · GS NFV-IFA 011/014 · GS NFV-SOL 001/003 |
| 3GPP | The 5G Service-Based Architecture | TS 23.501 · 23.502 · 29.500 · 29.244 · 28.531 |
| O-RAN Alliance | The O-Cloud & RIC for the RAN | WG6 O-Cloud · O2 (O2ims/O2dms) · SMO |
| CNCF / LF Networking | Containers, Kubernetes, CNFs | Kubernetes · Helm · Anuket RA-2 · Nephio |
The seven layers — job, owner, spec
Everything Lesson 1.2 walks through, in one table.
| Layer | What it does | Typically owned by | Spec anchor |
|---|---|---|---|
| 7 · OSS / BSS | Assurance, inventory, charging, slice management | Operator IT | TS 28.533 · 28.531 · 28.552 · 28.554 |
| 6 · NFV-MANO | Orchestration and lifecycle — NFVO, VNFM, VIM | MANO vendor / OSM / ONAP | GS NFV-MAN 001 · IFA 007/013 |
| 5 · VNF / CNF | The network functions themselves, plus their EM | NF vendor | GS NFV-IFA 011 (VNFD) |
| 4 · VIM / CISM | Owns and allocates the NFVI resource pool | Cloud platform team | IFA 005/006 · IFA 040 (CISM) |
| 3 · NFVI | The virtualized compute / hypervisor / network domains | Cloud infrastructure team | GS NFV 002 §7.1 |
| 2 · Virtualization | Hypervisor (KVM/QEMU) or container runtime via CRI | Cloud platform team | GS NFV-INF 003 · GR NFV-IFA 029 |
| 1 · Hardware | COTS servers, ToR switching, NIC / DPU, storage | Data-center team | GS NFV-INF 001 · Anuket RA |
The NFV-MANO reference points
The named contracts between blocks — these are what actually break in production.
| Reference point | Connects | Carries | Spec |
|---|---|---|---|
| Os-Ma-nfvo | OSS/BSS ↔ NFVO | Network-service lifecycle, package management | GS NFV-IFA 013 · SOL 005 |
| Or-Vnfm | NFVO ↔ VNFM | VNF lifecycle operations, resource granting | GS NFV-IFA 007 · SOL 003 |
| Or-Vi | NFVO ↔ VIM | Resource reservation and allocation | GS NFV-IFA 005 |
| Vi-Vnfm | VNFM ↔ VIM | Direct resource allocation for a VNF | GS NFV-IFA 006 |
| Ve-Vnfm-em | EM ↔ VNFM | Function configuration and fault reporting | GS NFV-IFA 008 |
| Ve-Vnfm-vnf | VNF ↔ VNFM | Lifecycle notifications from the function itself | GS NFV-IFA 008 |
| Vn-Nf | VNF ↔ NFVI | The execution environment the function consumes | GS NFV 002 §7 |
| Nf-Vi | NFVI ↔ VIM | Infrastructure control and monitoring | GS NFV 002 §7 |
How to read a document number
The letters carry authority. GS and TS are normative; GR and TR are studies.
| Family | Means | Answers | Examples |
|---|---|---|---|
| NFV 00x | Foundation | Framework and vocabulary | NFV 002 (architecture) · NFV 003 (terms) |
| NFV-MAN | Management | The MANO architecture | MAN 001 |
| NFV-IFA | Interfaces & Architecture | What an interface must do | IFA 011 (VNFD) · IFA 040 (CISM) |
| NFV-SOL | Solutions | How to encode it on the wire | SOL 001 (TOSCA) · SOL 004 (package) |
| 3GPP 23.x | Architecture (SA2) | System design | TS 23.501 (5G SBA) |
| 3GPP 28.x | Management (SA5) | OSS, slicing, KPIs | TS 28.533 · TS 28.554 |
| 3GPP 29.x | Protocols (CT4) | On-the-wire core protocols | TS 29.244 (PFCP) · TS 29.500 (SBI) |
Foundations quiz
Twelve questions across all three lessons. Answers and order reshuffle on every load.
Module 1 of 10 live · 3 narrated lessons · fully animated · English karaoke subtitles.