Data Plane Gateway Architecture for Low-Overhead Wireless Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges with communication overhead due to tunnel headers added to and removed from protocol data units, and maintaining end-to-end performance is difficult when data processing services are managed outside the system.
Innovation Solution
The implementation of data plane architecture that includes data plane gateways (DP GWs) for mapping and processing protocol data units (PDUs) with service-based interfaces, enabling native data processing within the communication system and optimizing tunnel headers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If tunnel headers are added to and removed from protocol data units to support data communication, then data connectivity is enabled, but communication overhead increases
Solution Approach 1:
The patent extracts and removes unnecessary tunnel headers from protocol data units at the data plane gateway. By identifying and eliminating redundant header information while preserving essential routing data, the system reduces communication overhead and packet size, directly addressing the contradiction between maintaining connectivity and reducing overhead.
Solution Approach 2:
The patent changes the parameter of tunnel header composition by dynamically adjusting which header fields are included or removed based on routing requirements. This parameter optimization allows the system to maintain sufficient routing information while minimizing overhead, resolving the contradiction between reliable connectivity and energy-efficient communication.
2Adaptability or versatility
If data processing services are managed outside the wireless communication system, then service flexibility is improved, but end-to-end performance assurance becomes difficult
Solution Approach 1:
The patent introduces a data plane gateway as an intermediary component within the wireless communication system that bridges external data processing services and the core network. This gateway enables service flexibility by allowing external services to be accessed while simultaneously providing performance assurance through controlled packet handling, routing optimization, and quality of service management at the gateway interface.
Solution Approach 2:
The data plane gateway performs multiple functions including packet routing, header optimization, service processing, and performance monitoring. By consolidating these diverse functions in a single gateway component, the system achieves both service flexibility and end-to-end performance assurance, resolving the contradiction between adaptability and reliability.
3Adaptability or versatility
If protocol data units are processed through multiple network entities with tunnel encapsulation, then routing capability is enhanced, but data rate decreases and delay increases
Solution Approach 1:
The patent removes redundant tunnel headers and encapsulation layers at the data plane gateway, reducing packet size and minimizing processing steps. This extraction of unnecessary overhead directly increases data rate and reduces transmission delay while preserving essential routing information needed for multi-entity navigation.
Solution Approach 2:
The gateway implements optimized routing that allows packets to skip unnecessary processing stages and tunnel hops by directly routing through the gateway. This skipping mechanism reduces the number of intermediate processing steps, thereby increasing speed and reducing delay while maintaining routing capability.
Data Source
AI summary
The disclosure provides for systems and methods for data plane architecture of a wireless communication system. According to an aspect a method is provided. The method may include receiving, by at least one DP GW from a caller, a request based on a first service-based interface format of the caller. The request may indicate one or more of: a procedure to be performed by a callee and a parameter of the procedure. The method may further include sending, by the at least one DP GW to the callee, a second request based on a second service-based interface format of the callee, the second request indicating one or more of: the procedure and the one or more parameters of the procedure.