OmniNWDAF

OmniNWDAF is the Omnitouch Network Data Analytics Function (NWDAF) for the 5G Core. It implements the NWDAF role defined in 3GPP TS 23.501 §6.2.18 and the NWDAF architecture in 3GPP TS 23.288, exposing the Service Based Interface (SBI) services specified in 3GPP TS 29.520.

OmniNWDAF exposes two SBI services and registers with the NRF as NF type NWDAF:

• Nnwdaf_AnalyticsInfo - synchronous request/response analytics retrieval.
• Nnwdaf_EventsSubscription - subscribe/notify analytics delivery, including recurring notification, subscription read and modify, and durable storage.

It advertises support for the full standardised set of 16 analytics event IDs defined in 3GPP TS 29.520.

Analytics Coverage

OmniNWDAF provides the complete Nnwdaf API surface and delivery machinery. The load-oriented events are computed from live NRF data.

Computed from live NRF data (per-NF registration status and reported load, TS 29.510 NFProfile, collected by NRF discovery):

• NF_LOAD - one load-level entry per discovered NF, from its reported load and status.
• SLICE_LOAD_LEVEL and NSI_LOAD_LEVEL - average load of the NFs serving the requested S-NSSAI.
• NETWORK_PERFORMANCE - network-wide aggregates (active NF ratio, average reported load).

For these events, confidence reflects how much live data backed the result (the number of NFs with a usable load), and is 0 when no data was available.

Documentation

Operations and Monitoring

• Operations Guide - Service behaviour, request and subscribe/notify flows, and day-to-day operation.
• Metrics and Monitoring - Observability via structured logs and the liveness endpoint.

Configuration

• Configuration Reference - Every runtime.exs key and environment variable with type, default, and description.

Support

• Troubleshooting - Common issues and their resolutions.

Architecture Overview

OmniNWDAF sits on the SBI as an analytics producer. Consumers reach it over HTTP via the two Nnwdaf services. OmniNWDAF registers and heartbeats with the NRF, discovers NF instances from the NRF to compute the load-oriented analytics, and delivers outbound notification callbacks to each events-subscription subscriber's notificationURI. It does not collect data from other NFs directly or from OAM.

Features Overview

Core Functionality

• Nnwdaf_AnalyticsInfo - synchronous retrieval of analytics for a single event, selected by event-id. Load-oriented events are computed from live NRF data; the rest echo request filters.
• Nnwdaf_EventsSubscription - create, read, modify, and delete subscriptions; an immediate notification at creation plus recurring notification on a repetition period.
• Live load analytics from the NRF - NF_LOAD, SLICE_LOAD_LEVEL, NSI_LOAD_LEVEL, and NETWORK_PERFORMANCE are derived from NF registration status and reported load discovered from the NRF.
• Full event ID surface - all 16 standardised analytics event IDs are advertised and accepted. See the event ID reference table.
• Durable subscriptions - subscriptions are mirrored to a durable store and reloaded on restart, with recurring notifications re-armed.
• Best-effort notification delivery - bounded exponential-backoff retry per configuration.
• Liveness endpoint - a simple status endpoint for health checking.

Integration Points

• NRF (Nnrf_NFManagement / Nnrf_NFDiscovery) - registration and periodic heartbeat, advertising nnwdaf-analyticsinfo and nnwdaf-eventssubscription, both v1; plus NF discovery to feed the load-oriented analytics.
• Subscribers (outbound) - notification callbacks POSTed to each subscriber's notificationURI.

Quick Start

Configuration Structure

Minimal Configuration

config :omninwdaf,
  # SBI binding and advertised endpoint
  sbi_scheme: "http",
  sbi_addr: "127.0.0.23",
  sbi_port: 7777,

  # NRF registration target
  nrf_uri: "http://127.0.0.10:7777",

  # Served PLMN (override the 999-70 test default per deployment)
  mcc: "999",
  mnc: "70",

  # NRF heartbeat period (milliseconds)
  heartbeat_interval: 10_000,

  # Validity window applied to returned analytics expiry (seconds)
  analytics_validity_seconds: 3600,

  # Notification delivery retry tuning
  notification_max_attempts: 4,
  notification_backoff_ms: 500

Every parameter above is documented in the Configuration Reference.

Documentation Structure

By Role

Operators and Administrators:

1. Read the analytics coverage overview above.
2. Start with the Operations Guide.
3. Review Metrics and Monitoring.

System Integrators:

1. Start with the Configuration Reference.
2. Review the Operations Guide request and subscribe/notify flows.
3. Keep Troubleshooting handy for common issues.

By Topic

• Service behaviour and flows - Operations Guide
• Configuration and environment variables - Configuration Reference
• Observability - Metrics and Monitoring
• Problem solving - Troubleshooting

3GPP References

Specification	Title	Relevance
TS 29.520	Nnwdaf Services	Nnwdaf_AnalyticsInfo, Nnwdaf_EventsSubscription, event IDs
TS 23.288	Architecture enhancements for NWDAF	NWDAF analytics architecture
TS 23.501 §6.2.18	System architecture for the 5G System	NWDAF network function definition
TS 29.510	Nnrf Services	NRF registration, heartbeat, and NF discovery (NFProfile load for analytics)