ITU-T Y.2060 IoT Reference Model

Trace an IoT design through the ITU-T Y.2060 layers and cross-cutting capabilities

animation
itu
reference-model
architecture
interactive
An interactive ITU-T Y.2060 reference model explorer for mapping devices, networks, service support, applications, management, and security across realistic IoT scenarios.
ITU-T Y.2060 4 layers Management + Security Scenario trace

Map a real IoT system through the ITU-T reference model.

Follow one telemetry event from a physical thing through device, network, service support, and application layers while management and security responsibilities span the full stack.

Smart meter NB-IoT Scenario
All layers Focus
Layered Security posture
Managed Operations

ITU-T model controls and outputs

Device layer starts the observation

A thing is observed by a device or gateway. ITU-T separates the physical object from the connected device that exposes data.

Step 1 of 6
ITU-T Y.2060 layer model Interactive diagram showing device, network, service support, and application layers with management and security capabilities spanning the stack.
Layer focus Device

Thing, sensor, actuator, gateway, and local device capabilities.

Event load 1,040/min

Planning estimate after link retry pressure.

Support fit Generic + specific

Common platform services plus scenario-specific logic.

Architecture risk Low

Management and security are assigned across layers.

Sense: the device layer observes the physical thing and emits a telemetry event with device identity and timestamp.

Model Reading

What each layer owns
  • Device: physical things, sensors, actuators, gateways, and device capabilities.
  • Network: access and transport capabilities that move IoT data between endpoints and platforms.
  • Service support and application support: common platform services plus application-specific support logic.
  • Application: domain applications and user or business functions built on supported services.

Accuracy Notes

Use the standard carefully
  • Y.2060 is a reference model, not a required product stack or protocol stack.
  • Telecom examples fit the model well, but the model does not require cellular or 5G.
  • Management and security are cross-cutting responsibilities, not features to add only at the end.
  • The event-load number here is a planning estimate for comparison, not an ITU-T formula.

Try It

Review prompts
  1. Switch from Smart meter to Factory 5G and compare which layer carries the most design pressure.
  2. Turn off security, inject the weak-auth incident, and identify which layers now need remediation.
  3. Hide the support split and decide what ambiguity appears between generic platform services and domain-specific logic.