3 OCNWDAF Interaction with 5G NFs and AF
This chapter describes how the OCNWDAF interacts with 5G NFs and AFs in the 5G environment.
3.1 Interaction with 5G NFs
The OCNWDAF interacts with Network Functions (NFs), Application Functions (AFs), and Operations, administration and management (OAMs) through the following gateways:
- The Ingress Gateway with functions such as Ingress connection management, TLS 1.2, and OAuth2.0.
- The Egress Gateway with functions such as Egress connection management Indirect, TLS 1.2 and OAuth2.0, retry and re-route in OCNWDAF Front End (FE). Also provide a Service Based Interface (SBI) for communication with other 5G NFs.
Ingress Gateway
This will be OCNWDAF's endpoint for accessing OCNWDAF services. Ambassador Proxy can be used as an API gateway. The Ingress Gateway provides the following capabilities:
- API path routing
- Proxy Service
- Load balancing
- Circuit breaking
- Security
- Internal microservices registry
Egress Gateway
All the outgoing communication from OCNWDAF to other NFs is routed through the Egress gateway.
3.2 Interaction with Application Functions (AFs)
The OCNWDAF can provide analytics reports to Application Functions (AFs).
If the AF is external, the communication between OCNWDAF and AF is carried out through the OCNEF. As defined in 3GPP TS 29.522, OCNEF supports CAPIF (Common API Framework) to ensure the external AF communicating with OCNWDAF is trusted.
The AF can obtain the analytics report from OC-NWDAF through the services exposed by OCNWDAF (For instance, Nnwdaf_AnalyticsInfo).