TWIF CUPS Architecture via E13 Interface Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current 3GPP standards for Trusted WLAN Interworking Function (TWIF) are monolithic, lacking Control and User Plane Separation (CUPS) architecture, which is essential for efficient operation in 5G networks, and require a new interface (E13) between TWIF-C and TWIF-U entities to manage control and user plane signaling effectively.
Innovation Solution
Implementing a CUPS architecture by splitting the TWIF into TWIF-C and TWIF-U entities and introducing an E13 interface between them, utilizing the E13 Application Protocol (E13AP) running on transport protocols like SCTP, TCP, or UDP to manage control and user plane functionalities independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the TWIF is kept as a monolithic structure following current 3GPP standards, then the device complexity is reduced and ease of manufacture is improved, but the adaptability to 5G networks and operational efficiency deteriorate due to lack of CUPS architecture
Solution Approach 1:
The TWIF is segmented into two independent entities: TWIF-C (Control plane) and TWIF-U (User plane). This segmentation enables the TWIF to adopt the CUPS architecture required by 5G networks, improving adaptability while managing complexity through functional separation rather than monolithic design.
2Productivity
If the TWIF is split into TWIF-C and TWIF-U entities with a new E13 interface, then the operational efficiency and bearer management capability are improved, but the device complexity and interface management overhead increase
Solution Approach 1:
The TWIF is divided into TWIF-C for control plane functions and TWIF-U for user plane functions, with a dedicated E13 interface between them. This segmentation improves operational efficiency by allowing independent optimization of control and data paths, while the standardized E13 interface manages the complexity of inter-entity communication.
3Ease of operation
If a new E13 interface with E13AP protocol is introduced between TWIF-C and TWIF-U, then the bearer management and interface management capabilities are enhanced, but the ease of operation and implementation difficulty increase
Solution Approach 1:
The E13 interface with E13AP protocol acts as an intermediary standardized communication channel between TWIF-C and TWIF-U. This intermediary provides structured procedures for bearer management and interface management, enhancing operational capability while the standardized protocol framework manages implementation complexity.
Data Source
AI summary
A method is provided. The method performed by a trusted wireless local area network (WLAN) Interworking Function (TWIF) control plane (TWIF-C) entity in a trusted WLAN access network, comprises communicating with a TWIF user plane (TWIF-U) entity through a E13 interface. Each of the TWIF-C entity and the TWIF-U entity is communicated with a trusted WLAN access point (TWAP) in the trusted WLAN access network connected to a user equipment (UE).


