NWDAF-ONAP Integration for UPF Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The separation between Open Network Automation Platform (ONAP) and Fifth Generation Core (5GC) networks leads to decoupled automation loops, resulting in non-optimal decision-making due to lack of visibility and correlation of data across domains, affecting UPF selection, traffic routing, and Life Cycle Management (LCM) of network resources.
Innovation Solution
Implementing a Network Data Analytics Function (NWDAF) that provides UPF selection and traffic routing recommendations to the Session Management Function (SMF), leveraging user location, mobility patterns, application usage, and resource load information, and enabling interaction between ONAP and NWDAF for optimal deployment and onboarding of UPFs and Application Servers (ASs).
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If ONAP and 5GC networks operate separately with decoupled automation loops, then each domain maintains independent control and operational simplicity, but decision-making becomes non-optimal due to lack of visibility and correlation of data across domains
Solution Approach 1:
The patent introduces an intermediary mechanism that enables information exchange and correlation between the ONAP and 5GC domains. This intermediary allows the SMF to receive analytics information from NWDAF (which is influenced by ONAP) and use it for UPF selection and traffic routing decisions, thereby bridging the information gap without compromising the independent operational structure of either domain.
2Reliability
If analytics information is integrated across ONAP and 5GC domains, then decision-making optimality improves through better visibility and correlation, but system complexity increases due to additional interaction mechanisms
Solution Approach 1:
The patent segments the analytics information integration into modular components. The NWDAF is responsible for collecting and processing analytics information, the SMF is responsible for making decisions based on this information, and the interaction follows standardized service-based interfaces. This segmentation allows complex analytics integration to be broken down into manageable, independent functions that can be developed and maintained separately.
Solution Approach 2:
The patent employs universal service-based interfaces that enable multiple functions to interact through standardized mechanisms. The analytics information flow mechanism serves multiple purposes: UPF selection, traffic routing optimization, and resource management. This multi-functionality reduces the need for separate specialized interfaces for each interaction type, thereby managing complexity.
3Productivity
If UPF selection and traffic routing use integrated analytics from both ONAP and 5GC, then network automation and resource utilization improve, but the complexity of coordinating automation loops increases
Solution Approach 1:
The patent implements preliminary action by having the NWDAF pre-process and prepare analytics information before the SMF needs to make routing decisions. The analytics information is collected, processed, and made available in advance through the service-based interface, allowing the SMF to quickly access pre-computed insights without needing to coordinate complex real-time analytics generation during the decision-making process.
Data Source
AI summary
Methods and systems for Open Network Automation Platform (ONAP) Fifth Generation Core (5GC) interaction for analytics are provided. According to one aspect, a method, performed by a Front End node for receiving patterns extracted from events and current network status data in a telecommunications network, comprises: receiving, from a Session Management Function (SMF) a request for a User Plane Function (UPF) selection recommendation for a user; determining a list of applications associated with the user; sending, to a Data Collection, Analytics, and Events (DCAE) function of an ONAP, a request for a list of Application Server (AS) locations; receiving, from the DCAE function, the list of AS locations; selecting a UPF based on the user's mobility and application usage patterns; and sending, to the SMF, a recommendation identifying the selected UPF.