Application Originated Mobile Terminated

Description

Application Originated Mobile Terminated (AOMT) is a 3GPP service capability that enables applications, typically residing in application servers outside the 3GPP network or within network functions, to initiate communication sessions toward User Equipment (UE) that may be in various power-saving states. Unlike traditional mobile-terminated communications that require the UE to be in connected mode or periodically monitoring paging channels, AOMT provides mechanisms for the network to efficiently reach UEs that are in idle or inactive states, particularly those configured with extended discontinuous reception (eDRX) or power saving mode (PSM) for IoT applications.

The architecture supporting AOMT involves several key network functions. The Service Capability Exposure Function (SCEF) in 4G or the Network Exposure Function (NEF) in 5G acts as the entry point for external applications to request AOMT services. These functions authenticate and authorize application requests, then interface with core network functions like the Mobility Management Entity (MME) in 4G or the Access and Mobility Management Function (AMF) in 5G. When an application needs to reach a UE, it sends a request to the SCEF/NEF, which then triggers the appropriate core network procedures to locate and page the UE, even if it's in deep sleep states with extended monitoring cycles.

The technical operation of AOMT involves sophisticated timing and state management. For UEs configured with power saving features, the network maintains knowledge of the UE's reachability patterns, including eDRX cycles and PSM active timer values. When an AOMT request arrives, the network determines the optimal time to page the UE based on its configured monitoring windows. This requires precise synchronization between the network's knowledge of UE sleep patterns and the actual UE behavior, which is maintained through registration procedures and periodic updates.

AOMT supports various service delivery models including mobile-terminated data delivery, network-initiated service requests, and application-triggered notifications. The system includes mechanisms for handling delivery failures, with options for retry policies, and expiration timers. For IoT devices, AOMT is designed to minimize the impact on device battery life by optimizing the paging procedures and network policies. The service includes quality of service parameters and security considerations to ensure that only authorized applications can initiate communications, with proper authentication and authorization checks at multiple levels.

Purpose & Motivation

AOMT was created to address the fundamental challenge of enabling efficient network-initiated communications to power-constrained IoT devices and mobile terminals operating in advanced power-saving modes. Traditional mobile-terminated communications assumed devices were either connected or regularly monitoring paging channels, but IoT deployments with eDRX and PSM introduced extended sleep periods ranging from minutes to hours, making conventional paging mechanisms ineffective. Without AOMT capabilities, applications would need to wait for devices to wake up and initiate contact, creating unacceptable latency for many IoT use cases like emergency alerts, remote configuration updates, or real-time command delivery.

The historical context for AOMT development lies in the evolution of 3GPP standards to support massive IoT deployments. As Release 13 introduced enhanced machine-type communication (eMTC) and narrowband IoT (NB-IoT) with advanced power-saving features, it became apparent that existing mechanisms for reaching devices were insufficient. Previous approaches either required devices to remain in connected states (draining battery) or imposed impractical latency for network-initiated communications. AOMT provides the standardized interface and procedures that allow applications to reliably reach devices while respecting their power-saving configurations.

Beyond IoT, AOMT addresses broader 5G requirements for efficient service delivery in scenarios where devices spend most of their time in energy-efficient states. It enables new service models where network-initiated communications are essential, such as push notifications, software updates, emergency alerts, and remote device management. By standardizing these capabilities in Release 16 and beyond, 3GPP ensures interoperability between network equipment, devices, and application servers from different vendors, creating a consistent ecosystem for network-triggered service delivery.

Key Features

• Enables applications to initiate communications to UEs in power-saving states
• Supports devices configured with eDRX and PSM for IoT applications
• Provides standardized interfaces through SCEF (4G) and NEF (5G)
• Includes mechanisms for handling delivery failures and retry policies
• Maintains security through authentication and authorization of application requests
• Optimizes paging procedures to minimize impact on UE battery life

Evolution Across Releases

Defining Specifications