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.
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 →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 →Technology family
Network exposure and analytics · Core Network
- Rel-11 SCS/AS
- Rel-13 IWK-SCEF, SCEF
- Rel-15 CAPIF, NEF, NWDAF
- Rel-16 SCEF+NEF
- Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
- Rel-18 RE-NWDAF
- RE-NWDAF builds on NWDAF
“The NWDAF with roaming exchange capability is called Roaming Exchange NWDAF (RE-NWDAF).” TS 23.288
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Rel-18 defines the RE-NWDAF, an NWDAF with roaming exchange capability, as the entry/exit point for exchanging analytics and input data between PLMNs, with the Nnwdaf_RoamingData service in TS 29.520.
- “The NWDAF with roaming exchange capability is called Roaming Exchange NWDAF (RE-NWDAF).” TS 23.288 v18.13.0
- “An RE-NWDAF is the only consumer of these services” TS 23.288 v18.13.0
- “Upon the reception of an HTTP POST request with "{apiRoot}/nnwdaf-roamingdata/<apiVersion>/subscriptions" as Resource URI and RoamingDataSub data structure as request body, the RE-NWDAF shall:” TS 29.520 v18.15.0
RE-NWDAF behaviour in TS 29.520 was specified and corrected: notification flag muting/retrieval, immediate reporting, and rejection of requests whose analytics target period spans past and future with BOTH_STAT_PRED_NOT_ALLOWED.
- “the RE-NWDAF shall reject the request with an HTTP "400 Bad Request" response including the "cause" attribute set to "BOTH_STAT_PRED_NOT_ALLOWED"” TS 29.520 v19.8.0
- “the RE-NWDAF shall include the reports of the events subscribed within "immReport" attribute, if available, in the HTTP POST response” TS 29.520 v19.8.0
- RE-NWDAF behaviour when receiving notification flag TS 29.520CR0974
Rel-20 adds new TS 28.552 performance measurements for RE-NWDAF roaming data collection service: subscriptions received, accepted, rejected, notifications generated, and time consumed.
- “This measurement provides the number of subscriptions related to roaming data collection service received by an RE-NWDAF.” TS 28.552 v20.4.0
- “This measurement provides the time consumed by the RE-NWDAF to provide the roaming data collection service.” TS 28.552 v20.4.0
- Add new measurements related to the number of successful and failed roaming data collection service subscriptions received by RE-NWDAF TS 28.552CR0719
Defining Specifications
3GPP specifications that define or reference RE-NWDAF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |