← Back to the chapter · Next detail →

Technical detail · NB-IoT Architecture

Named CIoT nodes and interfaces

Replace the generic phrase “the cellular core” with the actual path. The user equipment (UE) first reaches an NB-IoT-capable eNodeB in the CIoT radio access network. From there, control and user data can take different routes.

InterfaceEndpointsPlane and responsibility
UuUE—eNodeBRadio synchronization, random access, RRC, scheduling, paging, uplink and downlink transfer
S1-MMEeNodeB—MMEControl signalling for registration, authentication context, mobility, bearer control; also participates in control-plane CIoT optimisation
S1-UeNodeB—Serving Gateway (SGW)User-plane bearer packets when the normal user-plane path is active
S11MME—SGWBearer and session control between mobility control and the serving gateway
S5/S8SGW—Packet Data Network Gateway (PGW)User-plane and bearer control toward the packet-data network; S8 is used across serving/home network boundaries
SGiPGW—external packet-data serviceIP delivery toward an enterprise endpoint, broker, or CIoT application service
T6aMME—Service Capability Exposure Function (SCEF)Control-plane non-IP data delivery and service exposure path
T8SCEF—application serverExposed service API boundary, including authorization and delivery policy

Follow a normal user-plane packet first: UE -> eNodeB -> S1-U -> SGW -> S5/S8 -> PGW -> SGi -> service. The MME establishes and controls the bearer through S1-MME and S11, but application payload does not normally pass through the MME on this route.

Now follow control-plane CIoT small data. The UE carries data with signalling toward the MME over the radio and S1-MME control path. The core can deliver it through the SCEF using T6a for non-IP data delivery, with the external service reached through the exposure interface. This can avoid maintaining a conventional user-plane bearer for a tiny transfer, but it moves payload handling, authorization, size limits, acknowledgements, and charging into a different operational boundary. Record which path the subscription and firmware actually use; “NB-IoT connected” does not identify it.

← Back to the chapter · Next detail →