N3IWF Control and User Plane Separation via E10 Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing non-3rd generation partnership project (3GPP) interworking functions (N3IWF) do not adopt control and user plane separation (CUPS) architecture, missing out on benefits like enhanced scalability and higher capacity per session, and rely on heavy proprietary interfaces like PFCP over UDP, which is inefficient for N3IWF.
Innovation Solution
Introducing CUPS architecture by splitting N3IWF into N3IWF-control plane (N3IWF-C) and N3IWF-user plane (N3IWF-U) with a new E10 interface using E10 application protocol (E10AP) over stream control transmission protocol (SCTP), enabling services like interface management, bear management, and load management between N3IWF-C and N3IWF-U.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If CUPS architecture is adopted by N3IWF, then scalability and capacity per session are improved, but device complexity increases due to separation into N3IWF-C and N3IWF-U
Solution Approach 1:
The N3IWF is segmented into two independent functional units: N3IWF-C (control plane) and N3IWF-U (user plane). This segmentation allows independent scaling and deployment of control and user plane functions, improving capacity per session while maintaining manageable complexity through functional separation.
Solution Approach 2:
The control plane (N3IWF-C) is designed to be universal and can control multiple user plane instances (N3IWF-U). This multi-functionality allows a single control plane to manage numerous user plane functions, improving scalability without proportionally increasing control plane complexity.
2Adaptability or versatility
If proprietary interface PFCP over UDP is used, then interface functionality is sufficient, but protocol overhead and processing burden are excessive for N3IWF
Solution Approach 1:
The heavy PFCP protocol is extracted and replaced with a lighter custom binary protocol for the E10 interface. This extraction removes unnecessary overhead while retaining essential control and user plane functionality, reducing processing burden on N3IWF nodes.
Solution Approach 2:
The protocol parameters are changed from PFCP's complex structure to a simplified binary format with reduced header overhead and streamlined message structures. This parameter change maintains functional capability while significantly reducing processing requirements.
3Productivity
If N3IWF is split into N3IWF-C and N3IWF-U, then scalability is improved, but interface management complexity increases
Solution Approach 1:
The interface management is segmented into distinct functional areas: control plane signaling (E10-C), user plane forwarding (E10-U), and management plane operations. This segmentation simplifies interface management by providing clear separation of concerns and dedicated protocols for each functional area.
Solution Approach 2:
A standardized E10 interface specification acts as an intermediary between N3IWF-C and N3IWF-U, defining clear message formats, state machines, and interaction protocols. This intermediary layer abstracts the complexity of inter-plane communication and provides a manageable interface for implementation.
Data Source
AI summary
A method for controlling an execution (signalling) of a non-3rd generation partnership project (3GPP) interworking function (N3IWF) is provided. The method includes splitting a signalling of a N3IWF into a control plane signalling and a user plane signalling, where the control plane signalling is handled by an N3IWF-C device and the user plane signalling is handled by an N3IWF-U device. Further, the method includes adding the E10 interface between the N3IWF-C device and the N3IWF-U device. Further, the method includes monitoring the E10 interface, whereas the E10 interface includes an E10AP. The N3IWF-C device and the N3IWF-U device enables a plurality of services between the N3IWF-C device and the N3IWF-U device. The plurality of services includes an interface management service, a bear management service, a trace management service, and a load management service.