Description
The Ambient IoT Function (AIoTF) is a core network function defined within the 5G System (5GS) architecture specifically for the support of Ambient IoT, a new class of IoT introduced in 3GPP Release 19. Ambient IoT devices are characterized by their extreme simplicity, ultra-low cost, and lack of a conventional power source; they operate by harvesting energy from ambient radio frequency (RF) signals, such as those from cellular base stations or dedicated readers. The AIoTF acts as the central network entity responsible for managing the lifecycle and connectivity of these uniquely constrained devices. It resides within the control plane of the 5G Core Network (5GC) and interfaces with other core network functions like the Access and Mobility Management Function (AMF) and the Unified Data Management (UDM) to provide a complete service framework for Ambient IoT.
Architecturally, the AIoTF is designed to handle the specific communication patterns and constraints of Ambient IoT devices. These devices cannot initiate communication or perform complex signaling procedures like traditional UEs. Instead, they operate in a 'reader-talks-first' or network-initiated paradigm. The AIoTF supports procedures for device registration and reachability management that account for this asymmetry. A key architectural aspect is the AIoTF's role in maintaining a context for Ambient IoT devices, which includes a minimal set of subscription and status information. This context is essential because the devices themselves are not always powered on and cannot store complex state. The AIoTF may also be involved in managing paging or wake-up signaling directed towards groups of Ambient IoT devices to trigger their response, a process coordinated with the Radio Access Network (RAN).
From a procedural standpoint, the AIoTF works by interfacing with the AMF, which is the first point of contact for device-originated signaling. When an Ambient IoT device harvests enough energy to power its minimal circuitry, it may transmit a simple signal or respond to a network query. This signal is received by the RAN and forwarded to the AMF. The AMF, recognizing the device type, interacts with the AIoTF to authenticate the device and retrieve or update its context. The AIoTF leverages the UDM for subscription data. For downlink communication, an application server sends data destined for an Ambient IoT device to the 5GC. The AIoTF is then responsible for determining the device's reachability status and, if necessary, triggering a RAN procedure (like a group wake-up signal) to make the device active so it can receive the data. This entire process is optimized for minimal signaling overhead and energy consumption on the device side.
The AIoTF's role is critical for integrating Ambient IoT into the 5G ecosystem. It abstracts the complexities of managing these passive devices from other network functions and application servers. By providing standardized procedures for registration, authentication, and data delivery, the AIoTF enables scalable and secure deployment of billions of Ambient IoT devices for use cases like asset tracking, smart sensing, and digital product passports, where device cost and energy autonomy are paramount.
Purpose & Motivation
The AIoTF was created to address the fundamental challenge of integrating a new category of ultra-constrained, battery-free IoT devices into the 5G network. Prior to Release 19, 3GPP standards for IoT, such as NB-IoT and LTE-M, were designed for devices with some onboard power (batteries) and the capability to perform active network procedures like random access and periodic registration. These technologies were not suitable for devices that harvest energy from ambient RF sources, as they are only intermittently powered and lack the energy budget for complex, bidirectional signaling sequences. The industry demand for item-level tracking (e.g., for logistics, retail, and manufacturing) required a cellular solution with near-zero device cost and perpetual lifetime, which motivated the standardization of Ambient IoT.
The primary problem the AIoTF solves is providing a network-based management entity for devices that cannot manage their own network state. Traditional IoT devices maintain a protocol context with the network. Ambient IoT devices cannot do this due to their intermittent operation. The AIoTF exists to maintain this context on behalf of the device within the network. It solves the problems of device authentication in a stateless manner, manages reachability without relying on device-originated periodic updates, and enables efficient downlink communication through network-initiated wake-up mechanisms. Without a dedicated function like the AIoTF, the existing 5G core network functions would be burdened with non-standard procedures and optimizations, hindering scalability and interoperability.
Historically, similar concepts for managing very simple devices existed in RFID systems, but these were isolated, non-cellular solutions. The creation of the AIoTF within 3GPP represents the convergence of RFID-like functionality with global cellular infrastructure. It addresses the limitations of previous non-cellular approaches (limited range, proprietary systems) and previous cellular IoT approaches (too high device cost and power consumption). By defining the AIoTF, 3GPP provides a standardized, scalable, and secure architectural framework that allows Ambient IoT to leverage the ubiquitous coverage and management capabilities of 5G networks, unlocking massive-scale deployment scenarios.
Key Features
- Manages registration and context for battery-free Ambient IoT devices
- Supports network-initiated 'reader-talks-first' communication procedures
- Interfaces with AMF for device authentication and reachability management
- Coordinates with RAN for group-based wake-up signaling to devices
- Leverages UDM for subscription data of Ambient IoT subscriptions
- Enables efficient downlink data delivery to intermittently powered devices
Evolution Across Releases
Introduced the Ambient IoT Function (AIoTF) as a new 5G Core Network function. Defined its initial architecture, service-based interfaces (e.g., Naiotf), and basic procedures for Ambient IoT device registration, authentication, and reachability management. Established its interactions with the AMF, UDM, and the RAN to support the fundamental 'reader-talks-first' paradigm for battery-free devices.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.369 | 3GPP TS 23.369 |
| TS 24.369 | 3GPP TS 24.369 |
| TS 28.540 | 3GPP TS 28.540 |
| TS 29.510 | 3GPP TS 29.510 |
| TS 29.518 | 3GPP TS 29.518 |
| TS 32.291 | 3GPP TR 32.291 |
| TS 33.369 | 3GPP TR 33.369 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.401 | 3GPP TR 38.401 |
| TS 38.410 | 3GPP TR 38.410 |
| TS 38.412 | 3GPP TR 38.412 |
| TS 38.413 | 3GPP TR 38.413 |