Glossary term · Management

AOI

Area of Interest

Management →

AOI is a 3GPP management concept that defines a geographical or logical area for which performance data is collected and analyzed to enable targeted network monitoring and optimization.

Introduced
Rel-17
Specifications
2 specs
Category
Management
Introduced
Rel-17
Specifications
2 specs
AOI Description Purpose Related Classification Detected Changes Specifications

Description

The Area of Interest (AOI) is a fundamental construct within the 5G network management framework, specifically defined in the Management Data Analytics (MDA) and Network Data Analytics Function (NWDAF) contexts. It represents a defined geographical region (e.g., a cell, a tracking area, a set of GPS coordinates) or a logical domain (e.g., a specific network slice instance, a group of User Equipment) that is the target for data collection, analytics, and subsequent management actions. The AOI acts as a scoping parameter, allowing network management functions to focus their intelligence-gathering and decision-making processes on a relevant subset of the entire network infrastructure.

Architecturally, the AOI is primarily utilized by the NWDAF and the management system defined in 3GPP TS 28.552. An analytics consumer, such as a Network Slice Management Function (NSMF) or an Operations, Administration, and Maintenance (OAM) system, can request analytics from the NWDAF for a specific AOI. The request includes the AOI definition, which instructs the analytics function on where to source its input data. The NWDAF then collects relevant data, such as performance measurements, load information, or Quality of Service (QoS) flow metrics, specifically from network functions and entities within or associated with that AOI.

The operation involves several key components. First is the AOI definition itself, which can be specified using various identifiers like Cell ID, Tracking Area Code, or geographic coordinates. Second is the analytics consumer that formulates the request with the AOI parameter. Third is the NWDAF, which interprets the AOI, interfaces with the appropriate data repositories (like the Network Repository Function (NRF) for discovery and other Network Functions (NFs) for data), and performs the analysis. Finally, the output is a tailored analytics report (e.g., predicted load, abnormal behavior detection, service experience) applicable only to the defined area, enabling precise, localized network optimization and automation.

In the broader network ecosystem, AOI plays a critical role in enabling granular and efficient network automation. By moving away from network-wide, blanket analytics, operators can implement targeted policies, optimize resource allocation for high-demand zones, pre-emptively manage congestion in specific areas, and guarantee service-level agreements (SLAs) for premium services or slices in designated locations. This granularity is essential for supporting advanced 5G use cases like factory automation, smart stadiums, and vehicular networks, where performance requirements are highly localized.

Purpose & Motivation

AOI was introduced to address the limitations of monolithic, network-wide management and analytics approaches that were inefficient and lacked precision for 5G's diverse service requirements. Previous generations often relied on broad performance indicators that could mask localized issues or opportunities for optimization. As 5G introduced concepts like network slicing, ultra-reliable low-latency communication (URLLC), and massive IoT, the need to monitor and manage performance at a granular, context-aware level became paramount. AOI provides the necessary scoping mechanism to achieve this.

The primary problem AOI solves is the inefficient consumption of processing and signaling resources in analytics engines. Collecting and analyzing data for an entire Public Land Mobile Network (PLMN) is computationally expensive and often unnecessary when an operator only needs insights for a specific industrial campus, a dense urban cell, or a particular network slice instance. AOI allows analytics requests to be precisely targeted, reducing the load on the NWDAF and the volume of data transferred across management interfaces, leading to more scalable and responsive network intelligence.

Historically, management actions were often reactive and applied broadly. The creation of AOI, alongside the NWDAF in 5G's service-based architecture, was motivated by the shift towards proactive, closed-loop automation and intent-based management. By defining an Area of Interest, operators can express their management 'intent' for a specific domain. This enables automated systems to continuously monitor that area, apply machine learning models to predict trends or anomalies specifically within it, and trigger automated remediation actions (like scaling resources) only where needed, thereby realizing the vision of a truly self-optimizing network (SON) for complex 5G deployments.

Classification

Part ofNWDAF

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 2 changes
  • Add visited AOI(s) to analytics filter for UE mobility analytics TS 29.520CR0391
  • Adding NF load over AOI to analytics subset TS 29.520CR0474
Rel-19 1 change
  • Wrong conditions for AOI attributes TS 29.520CR0962

Explore further

Broader topics and technologies where AOI plays a role.

Defining Specifications

3GPP specifications that define or reference AOI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 28.552 vk30 5G Performance Measurements & Network Slicing Rel-20
TS 29.520 vk00 5G Network Data Analytics Function Services Rel-20