CAPIF Node AF Registration via NEF Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G telecommunications networks, there is no defined process for application functions (AFs) to publish binding information with network exposure functions (NEFs) for alternate selection during overload or failure scenarios, limiting the ability of NEFs to use NRF discovery procedures for alternate routing of AFs, especially those outside the operator's trust domain.
Innovation Solution
Implementing a Common Application Programming Interface (API) Framework (CAPIF) node that receives a registration trigger message from an AF, determines its validity, generates a custom NF registration message, and sends it to an NF Repository Function (NRF) to register AFs, enabling NEFs to discover and use alternate AF instances for notification during failures or routing scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If 3GPP standards permit NEF to publish binding information to consumer NFs, then NEF can provide alternate routing capability, but the standards fail to define a process for AF instance to publish binding information with NEF for alternate selection
Solution Approach 1:
The patent introduces an intermediary mechanism where the NEF acts as a mediator between the AF and the NRF. The NEF receives binding information from the AF, validates it, and then publishes it to the NRF on behalf of the AF. This intermediary approach enables AFs to publish binding information without requiring direct NRF integration, thereby resolving the complexity of defining new registration processes while maintaining alternate routing capability.
2Reliability
If AF instances are registered with NRF for alternate selection, then high availability is improved, but the process is not defined in 3GPP standards for AFs outside operator's trust domain
Solution Approach 1:
The patent implements a universal registration mechanism that works for both AFs within and outside the operator's trust domain. The NEF serves multiple functions: it receives binding information from any AF, validates the information according to operator policies, and publishes it to the NRF. This multi-functional approach enables AFs outside the operator's domain to be registered for alternate selection while maintaining standard compliance through the existing NEF-NRF interface.
3Adaptability or versatility
If NEF pushes binding information to NF service set or NF set, then alternate NEF selection is enabled, but the same mechanism does not exist for AF instances
Solution Approach 1:
The patent applies preliminary action by having the NEF receive and validate binding information from the AF before publishing it to the NRF. This preliminary validation step ensures that only appropriate binding information is published, preventing information loss or incorrect routing. The NEF performs this preparatory action in advance, enabling subsequent alternate NF selection to work correctly for AF instances.
Data Source
AI summary
Methods, systems, and computer readable media for registering application functions (AFs) using common application programming interface (API) framework (CAPIF) are disclosed. One example method for registering AFs using CAPIF comprises: at a CAPIF node comprising at least one processor: receiving, from an AF, a registration trigger message comprising information about the AF; determining that the registration trigger message is valid; generating a custom NF registration message using the information about the AF; and sending the custom NF registration message to an NF repository function (NRF).