NEF APIs and their Implementation

Course outline : The Network Exposure Function (NEF) is a key component of the 5G SA architecture. It enables external applications (AF - Application Function) to securely access the capabilities of the 5G SA mobile network through standardized interfaces. The APIs exposed by the NEF facilitate innovation, service customization, and monetization of network functionalities.

1. Network Exposure Function in the 5GS Network
1.1. NEF Functions
1.2. NEF Architecture
1.3. NEF versus SCEF
1.4. Combined NEF/SCEF
1.5. UE or UE Group Identities for Invoking NEF APIs
1.6. NEF API Families
1.6.1. Provisioning APIs
1.6.2. Policy and Charging APIs
1.6.3. Monitoring APIs
1.6.4. Non-IP Data Delivery APIs
1.6.5. Etc.
1.6.6. APIs Common to SCEF and NEF
1.6.7. NEF-Specific APIs

2. NEF APIs Exposed to External AFs
2.1. Event Monitoring API allowing the AF to subscribe to and be notified of state changes of a UE or a group of UEs (15 events are supported).
2.2. Device Triggering API allowing an AF to deliver a message to a UE or a group of UEs.
2.3. Background Data Transfer Policy Negotiation API allowing the AF to negotiate a data transfer policy for a group of devices.
2.4. Traffic Influence API allowing the AF to influence the selection of the UPF handling a UE’s traffic.
2.5. Network Configuration Parameter Provisioning API for configuring parameters related to IoT device power saving.
2.6. AF Session With QoS API allowing an AF to request QoS for a flow exchanged between the AF and a UE.
2.7. MSISDN-less Mobile Originated SMS API allowing a UE to send an SMS to an AF without having an MSISDN.
2.8. NIDD API allowing a device to exchange data with an AF through a Non-IP PDU session (i.e., unstructured).
2.9. Analytics Information Exposure API allowing an AF to obtain analytics data related to a given slice or to UEs (mobility data, connectivity data, etc.).
2.10. 5G LAN Parameter API allowing the AF to create, modify, and delete groups. This then enables invocation of NEF APIs for groups of devices.
2.11. SliceParamProvision API allowing the AF to configure parameters of a network slice instance.
2.12. UeAddress API allowing an AF to retrieve the IP address assigned to a UE.
2.13. UE ID Retrieval API allowing the AF to obtain the SUPI or GPSI of a UE from its public IPv4 address and port number or from an IPv6 address.
2.14. Service Specific Parameter Provisioning API allowing an AF to configure UE-related service data such as URSP.
2.15. Mobile Originated Location Request API allowing the NEF to notify the AF of the UE location provided by the GMLC.
2.16. AM Policy Authorization API allowing the AF to configure an AM policy applicable to a UE. This AM policy is relayed by the NEF to the PCF and from the PCF to the AMF so that the AMF can enforce it.
2.17. Other APIs

3. NEF APIs Exposed to Internal Network Functions (NFs)
3.1. NEF API used by the SMF for NIDD: Nnef_SMContext API
3.2. NEF API used by the SMSC for MSISDN-less SMS: Nnef_SMService API
3.3. NEF API used by the NWDAF or LMF to subscribe to UE state changes: Nnef_EventExposure API
3.4. NEF API used by the GMLC to obtain the UE SUPI from the GPSI or UE IP address: Nnef_UEId API

4. User Data Model Stored in the UDR and Manipulated by the NEF
4.1. Subscription Data
4.2. Policy Data
4.3. Structured Data for Exposure
4.4. Application Data
4.4.1. AccessAndMobilityData
4.4.2. PduSessionManagementData