Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

RE-NWDAF

Roaming Exchange Network Data Analytics Function

Management →

RE-NWDAF rE-NWWDAF is a specialized NWDAF deployed in a roaming exchange that analyzes data from multiple networks to generate insights for optimizing roaming services, fraud detection, and quality of experience.

Introduced
Rel-18
Where
Core Network › 5G Core
Specifications
3 specs
RE-NWDAF Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Roaming Exchange Network Data Analytics Function (RE-NWDAF) is a deployment variant of the standard 3GPP NWDAF, tailored for the roaming exchange environment. An NWDAF is a 5G core network function defined for data collection and analytics. The RE-NWDAF is specifically instantiated within the infrastructure of a roaming exchange provider (also known as a Data Clearing House or IPX provider), which sits between the home Public Land Mobile Network (HPLMN) and the visited PLMN (VPLMN). Its primary role is to gain a holistic, cross-operator view of roaming traffic and performance, which is not visible to any single operator's NWDAF.

Architecturally, the RE-NWDAF interfaces with various network functions and data sources across the roaming ecosystem. This includes collecting data from the roaming exchange's own systems (e.g., signaling transfer points for Diameter and HTTP/2), as well as potentially subscribing to analytics events from NWDAFs in the HPLMN and VPLMN (via the Nnwdaf_EventsMonitoring service). It can ingest a wide array of data types: signaling messages (e.g., Nudm, Npcf, Namf), user plane events, policy control events, and performance measurements related to roaming sessions.

The RE-NWDAF applies machine learning (ML) models and analytics logic to this federated data set. It works by correlating events from both the home and visited network perspectives for the same subscriber session. This allows it to generate unique insights, such as end-to-end quality of experience (QoE) for a roaming user, identification of anomalies or fraud patterns that span multiple networks (e.g., simultaneous registration attacks), and analytics on roaming traffic trends and hotspots. It can provide its analytics outputs to the roaming exchange's own operational systems, or expose them as a service to subscribing network operators via standardized interfaces, helping them optimize roaming agreements and troubleshoot cross-border service issues.

Purpose & Motivation

The RE-NWDAF was introduced to address the specific data analytics challenges in the global roaming ecosystem. In 5G standalone roaming, the home and visited networks have limited visibility into each other's domains. A home operator's NWDAF sees only the home network control plane and aggregated reports, while the visited network's NWDAF sees only its local context. This creates a blind spot for end-to-end service assurance, fraud management, and optimization of the roaming experience.

Traditional roaming analytics relied on offline processing of billing records (TAP files) or signaling data from a single network's perspective, which was slow and incomplete. The motivation for RE-NWDAF stems from the need for real-time, cross-operator intelligence to support advanced 5G roaming services, network slicing across borders, and stringent service level agreements (SLAs). By leveraging the roaming exchange's unique position as a hub for inter-operator traffic, the RE-NWDAF can synthesize a complete picture. It solves problems like diagnosing the root cause of a roaming session drop (was it in the HPLMN, VPLMN, or the interconnect?), detecting sophisticated fraud that exploits jurisdictional gaps, and providing data-driven insights for negotiating and monitoring roaming partnerships.

What changed in its specifications

The latest release-to-release comparison of specifications that define RE-NWDAF. Each summary describes the whole specification, not only this term.

TS 23.288Rel-18 → Rel-19

Rel-19 adds signalling storm and QoS and Policy Assistance analytics IDs, plus VFL server identity and VFL capability registration with NRF in TS 23.288. It also adds UE IP address and PDU Session Pair ID inputs from SMF, and UE list and altitude handling for UAV analytics.

Full comparison in TS 23.288 →
TS 29.520Rel-18 → Rel-19

Rel-19 adds Vertical Federated Learning training and inference APIs to TS 29.520, along with signalling storm, QoS/policy, and roaming analytics subscriptions. It also extends NWDAF ML model provisioning, event subscription fields, and 308 Permanent Redirect responses.

Full comparison in TS 29.520 →

Release Timeline

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-18 1 change
  • Editorial changes to RE-NWDAF TS 23.288CR0926
Rel-19 2 changes
  • RE-NWDAF behaviour when receiving notification flag TS 29.520CR0974
  • Corrections related to RE-NWDAF TS 29.520CR1068

Defining Specifications

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

SpecificationTitleRelease
TS 23.288 vk20 5G Network Data Analytics Architecture Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read