Traffic Splitter for Mobile Network User Plane
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Evolved Packet Core (EPC) architecture in 5G networks is complex and inefficient for machine-type communication (MTC) scenarios, leading to high operational costs and latency due to its features designed for classic mobile broadband applications, which are not needed in MTC, and struggles with high-bandwidth traffic volumes.
Innovation Solution
A traffic splitter is introduced into the user plane of mobile communications networks to determine whether data packet flows should be processed through the EPC or Software Defined Network (SDN) paths based on packet information, allowing for offloading of CPU-intensive tasks to dedicated hardware and reducing complex data manipulation, thereby optimizing processing paths for low-latency and high-bandwidth requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the EPC architecture is used to process all data packet flows, then comprehensive mobile broadband functionality is provided, but operational costs and latency increase due to complex processing
Solution Approach 1:
The patent segments the data packet flow processing into two distinct paths: the EPC processing path for flows requiring complex mobile broadband functionality, and the SDN processing path for flows requiring only simple forwarding. This segmentation allows each path to be optimized for its specific purpose, reducing overall latency while maintaining comprehensive functionality.
Solution Approach 2:
The patent introduces dynamic flow classification that determines the processing path based on the specific requirements of each data packet flow. The system dynamically routes flows to the appropriate processing path based on real-time analysis of flow characteristics, enabling adaptive optimization of latency and functionality.
2Reliability
If the EPC architecture is used to process all data packet flows, then comprehensive mobile broadband functionality is provided, but operational costs increase due to CPU-intensive processing
Solution Approach 1:
The patent segments the processing workload between EPC and SDN paths, offloading CPU-intensive simple forwarding tasks from the EPC infrastructure to the SDN processing path. This reduces the computational burden on expensive EPC resources, lowering operational costs while maintaining comprehensive functionality through the EPC path when needed.
Solution Approach 2:
The patent introduces an intermediary flow classification mechanism that directs appropriate flows to the SDN processing path for efficient handling. This intermediary layer enables cost-effective processing by matching flow requirements with the most appropriate processing resource, reducing overall operational costs.
3Reliability
If the EPC architecture is used for high-bandwidth traffic, then comprehensive processing capability is maintained, but scalability is limited due to CPU core constraints
Solution Approach 1:
The patent segments high-bandwidth traffic into two categories: flows requiring complex EPC processing and flows requiring only simple forwarding. By routing simple forwarding flows through the SDN path, the system achieves linear scalability with bandwidth capacity, while the EPC path maintains comprehensive processing capability for flows that require it.
Solution Approach 2:
The patent creates a universal processing architecture where the SDN processing path can handle high-bandwidth simple forwarding traffic, while the EPC processing path provides comprehensive processing capability when needed. This multi-functional architecture enables the system to scale efficiently with bandwidth while maintaining full processing capability.
4Adaptability or versatility
If the EPC architecture is used for MTC scenarios, then full feature set is available, but device complexity and operational costs increase due to unnecessary features
Solution Approach 1:
The patent segments MTC traffic into flows requiring full EPC feature processing and flows requiring only simple forwarding. This segmentation allows the system to provide the full feature set when needed while avoiding the complexity overhead for simple MTC flows by handling them through the streamlined SDN path.
Solution Approach 2:
The patent applies local quality optimization by providing different processing treatments to different flows based on their specific requirements. MTC flows needing only simple forwarding receive streamlined SDN processing, while flows requiring MTC-specific features receive full EPC processing, optimizing the balance between feature availability and complexity.
Data Source
AI summary
The application relates to a method for operating a traffic splitter provided for a data packet flow flowing through the data plane. The data packet flow is received and it is determined whether the data packet flow should be transmitted through an Evolved Packet Core, EPC, processing path or through a Software Defined Network, SDN, processing path based on information provided in the data packets of the data packet flow and it is transmitted either through the EPC processing path or the SDN processing path based on the determination.