Edge Notification Server

Description

The Edge Notification Server (ENS) is a service capability defined within the 5G system architecture, starting from 3GPP Release 18. It is part of the broader Edge Computing and service exposure framework, designed as an application-level server that provides a generic, efficient mechanism for delivering asynchronous notifications to external Application Functions (AFs). The ENS acts as an intermediary that manages subscription requests from AFs for specific events related to User Equipments (UEs) and then pushes corresponding notifications when those events occur, without the AF needing to continuously poll the network.

Architecturally, the ENS is a logical function that can be deployed within the operator's network, potentially at the edge for low latency. It interacts with the 5G Core Network's Network Exposure Function (NEF) or directly with other Network Functions (NFs) like the Unified Data Management (UDM) or Access and Mobility Management Function (AMF) to subscribe to and receive internal network events. The primary interface for service consumers is the ENS Application Interface, through which AFs establish subscriptions. A subscription request includes parameters such as the target UE group (identified by GPSI, group ID, or area), the type of event (e.g., UE reachability status change, location reporting, loss of connectivity), and the destination callback URI for notifications.

How it works involves a continuous monitoring and matching process. Upon receiving a valid subscription, the ENS translates the application-level request into corresponding network-level event subscriptions via the NEF or other NFs. When the subscribed event is detected by the network (e.g., a UE in the target group enters a specific area), the relevant NF sends an event report to the ENS. The ENS then processes this report, potentially aggregating or filtering events based on the subscription criteria, and finally delivers a structured notification (e.g., in JSON format) to the AF's provided callback URI via HTTP/2. This model is highly efficient for group-based scenarios, such as notifying a fleet management server when any vehicle in a fleet becomes available, or alerting a content delivery network when a critical mass of users enters a stadium area.

Purpose & Motivation

The ENS was created to address the inefficiency of the polling model commonly used by applications to check for changes in UE state or network events. Before ENS, an AF would need to periodically send queries (e.g., via NEF) to the network, which consumes signaling resources, increases latency for the application, and may miss transient events between polls. This is particularly problematic for event-driven applications serving large groups of UEs, such as IoT, vehicular, or immersive media services.

The motivation stems from the 5G-Advanced vision of enabling efficient edge-native applications and network automation. There was a clear need for a standardized, network-assisted notification service that could offload event monitoring from applications and provide reliable, timely push-based updates. The ENS provides this by leveraging the network's intrinsic awareness of UE status and location. It solves the problem of scalable event distribution for group-based services, reduces redundant signaling, and enables low-latency reactive applications at the network edge. Its creation is part of the ongoing evolution to make 5G networks more programmable and service-aware, facilitating new vertical use cases.

Key Features

• Provides a generic asynchronous notification delivery service to external Application Functions (AFs).
• Supports subscription to events for a group of UEs (identified by list, group ID, or geographical area).
• Event types include UE reachability, loss of connectivity, location reporting, and communication failure.
• Interworks with 5GC Network Functions (like NEF, UDM) to obtain network-triggered events.
• Delivers notifications via HTTP/2 callbacks to a URI provided by the subscribing AF.
• Enables efficient, push-based communication model, eliminating the need for application polling.

Evolution Across Releases

Defining Specifications