Mobile Originated Application Terminated

Description

Mobile Originated Application Terminated (MOAT) is a 3GPP service capability defined from Release 16 onwards, facilitating scenarios where a User Equipment (UE) originates a request that results in an application-level action being terminated at the UE or a network application. It is particularly relevant for IoT and Machine-to-Machine (M2M) communication, where a device may send a signal to initiate a downstream process, such as triggering a firmware update or a configuration change. The architecture involves the UE, the 3GPP network (including RAN and CN), and application servers, with procedures standardized to ensure seamless interaction.

How it works: In an MOAT scenario, the UE sends an uplink message, often a service request or data packet, to the network. This message is routed to an application server (e.g., via the UPF in 5G). Based on this initiation, the application server then triggers a terminated action towards the same UE or another entity. For example, a sensor sending a threshold alert (mobile-originated) might cause a server to send a command back to the sensor (application-terminated) to adjust its settings. The process leverages existing 3GPP mechanisms for data transmission and session management, with enhancements to support the signaling and service layer interactions. Key components include the UE's application client, the network's user plane for data transport, and the application server that processes the MOAT trigger.

MOAT's role is to enable efficient, event-driven communication in automated systems, reducing latency and overhead by coupling the mobile-originated event with the terminated action. It is specified in documents like 22.262 (service requirements) and 23.554 (architecture), ensuring it integrates with 5G core network functions like the NEF (Network Exposure Function) for API-based triggers. This capability supports use cases in industrial IoT, smart cities, and remote management, where devices need to initiate network-triggered responses.

Purpose & Motivation

MOAT was created to address the need for streamlined, device-initiated interactions in IoT and M2M ecosystems, where traditional client-server models were inefficient. Prior to its standardization, scenarios requiring a device to trigger a network action often involved complex, proprietary setups or multiple round-trip messages, leading to increased latency and resource usage. The limitations included lack of unified procedures across different services and networks, making interoperability challenging.

The motivation for MOAT stems from the growth of automated services in 5G, such as remote device management, predictive maintenance, and real-time control systems. 3GPP Release 16 introduced MOAT as part of enhanced service capabilities, solving the problem of enabling a mobile-originated event to seamlessly cause an application-terminated action. This reduces signaling overhead and improves responsiveness, which is critical for time-sensitive IoT applications. Historically, earlier M2M solutions relied on bespoke implementations; MOAT provides a standardized framework within 3GPP, aligning with trends towards network slicing and edge computing to support diverse vertical industry requirements.

Key Features

• Enables UE-initiated requests to trigger application-terminated actions
• Supports IoT and M2M use cases like remote triggers and updates
• Integrates with 5G Core Network functions (e.g., NEF, UPF)
• Reduces latency by coupling origination and termination events
• Standardized in 3GPP for interoperability across networks
• Facilitates event-driven communication for automation

Evolution Across Releases

Defining Specifications