1 Introduction

This document provides information about the role of Oracle Communications Cloud Native Core, Network Exposure Function (NEF) in 5G Service Based Architecture (SBA) and how to configure and use the NEF functionality and services.

NEF installation is supported over the following platforms:
  • Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) Oracle Cloud Infrastructure (OCI)
  • For more information, see Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.

1.1 Overview

NEF is a key component of the 5G Service Based Architecture. It provides a platform to securely expose the network services and capabilities offered by the 5G Network Functions (NFs) to either third-party applications or the internal Application Functions (AFs). Located between the 5G core network and third-party applications or AFs, NEF enables the external application administrators to customize the network for providing innovative services to their end-users. The applications communicate through NEF to access the internal data of the 5G core network.

Note:

The performance and capacity of the NEF system may vary based on the call model, feature or interface configuration, and underlying CNE/OCI and hardware environment.

NEF performs the following functions:

  • Facilitates robust and secure exposure of network services, such as voice, data connectivity, charging, subscriber data, IoT, and so on to trusted third-party applications or AFs
  • Provides programmable environment access of 5G network to both internal and external application administrators through a set of northbound RESTful APIs
  • Enables AF to securely provide information to 3GPP network to authenticate, authorize, and assist in throttling the AF
  • Translates the information received from the AF to the internal 3GPP NFs, and vice versa
  • Provides support to expose information collected from other 3GPP NFs to the AF
  • Monitors User Equipment (UEs) related events present in the 5G system and makes the event information available for external exposure. For example, monitoring of user location and services.

NEF interacts with different applications and the 5G core network. It performs the above functions through the following services:

  • NEF 5GC Agent
  • NEF CAPIF Core Function (CCF) Client
  • NEF Expiry Auditor
  • NEF Monitoring Events
  • NEF Quality of Service
  • NEF Traffic Influence
  • NEF API Router
  • NEF APD Manager
  • NEF Diameter Gateway
  • CAPIF AF Manager
  • CAPIF API Manager
  • CAPIF Event Manager
  • Device Trigger
  • MSISDNless MO SMS

For a detailed description of each service, see NEF Architecture.

NEF Availability

Oracle Communications Cloud Native Core (CNC) NEF availability is dependent on many factors. NEF applications are designed to achieve 99.999% availability, according to the applicable Telecommunications Industry Association TL9000 standards, with the following deployment requirements:
  • Deploy on a Cloud Native Environment with at least 99.999% Availability.
  • Deploy with n + k application redundancy, where k is greater than or equal to one.
  • Maintain production software within n-3 software releases, where n is the current general availability release.
  • Apply bug fixes, critical patches, and configuration recommendations provided by Oracle promptly.
  • Maintain fault recovery procedures external to the applications for the reconstruction of lost or altered files, data, programs, or Cloud Native environment.
  • Install, configure, operate, and maintain NEF as per Oracle’s applicable installation, operation, administration, and maintenance specifications.
  • Maintain an active support contract and provide access to the deployed NEF and your personnel to assist Oracle in addressing any outage.
NEF availability is measured for each calendar year and is calculated as follows:

Table 1-1 Measuring NEF Availability

Availability Description
Planned Product Availability (Product available time in each month) less (Excluded Time (defined below) in each month).
Actual Product Availability (Planned Product Availability) less (any Unscheduled Outage)
Product Availability Level (Actual Product Availability across all Production instances divided by Planned Product Availability across all Production instances) x 100

Note:

Excluded Time means:
  • Scheduled maintenance time.
  • Lack of power or backhaul connectivity, except to the extent that such lack of backhaul connectivity was caused directly by the CNC NF.
  • Hardware failure.
  • Issues arising out of configuration errors or omissions.
  • Failures caused by third-party equipment or software not provided by Oracle.
  • Occurrence of any event under Force Majeure.
  • Any time associated with failure to maintain the recommended architecture and redundancy model requirements above.

1.2 References

Following are the reference documents: