Mobility Edge Interface for Low-Latency UE-to-UE Data Paths
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telecommunications networks face challenges in improving latency and reliability of data paths between controller devices and drones operating in close vicinity, particularly when using edge computing, due to network congestion and equipment degradations.
Innovation Solution
Implementing a mobility edge interface (MEI) that extends the instantiation of user plane functions (UPF) from core data centers to the UE level, allowing point-to-point wireless communication links between UEs, with localized management of data channel characteristics such as bandwidth and RF signal power, reducing reliance on the operator core network for data transport.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data paths are managed through the operator core network, then centralized control and authorization are maintained, but latency increases and reliability decreases due to network congestion and equipment degradations
Solution Approach 1:
The patent segments the data path management function by instantiating UPF instances at the UE level rather than relying solely on centralized core network functions. This allows local data sessions to be managed independently, reducing dependency on core network elements and enabling parallel processing of data paths, thereby decreasing latency while maintaining centralized authorization through the MEI manager.
Solution Approach 2:
The mobility edge interface (MEI) acts as an intermediary between centralized network functions and distributed UPF instances. The MEI manager maintains centralized control and authorization while allowing UPF instances to operate locally at UEs. This intermediary architecture enables reliable data path management with reduced latency by eliminating the need for all data to traverse the core network.
2Loss of time
If UPF instances are instantiated at UE level through mobility edge interface, then latency is reduced and local data path management is enabled, but device complexity increases
Solution Approach 1:
The patent applies universality by designing the mobility edge interface to support multiple data sessions and communication protocols simultaneously. The UPF instances can handle various data types and service requirements through a unified architecture, allowing a single implementation to serve multiple functions including data routing, session management, and quality of service control, thereby reducing overall system complexity despite the distributed nature of the architecture.
3Adaptability or versatility
If centralized core network controls data paths, then authorization and security are maintained, but adaptability to local communication needs is reduced
Solution Approach 1:
The patent implements dynamics by enabling the data path architecture to adapt between centralized and distributed modes based on operational needs. The MEI manager can dynamically authorize and manage UPF instances at UE levels, allowing the system to shift from centralized control to localized management as required. This dynamic capability provides high adaptability to local communication needs while maintaining centralized authorization through policy-based control.
Data Source
AI summary
Mobility edge network systems and methods are provided. In some embodiments, a mobility edge interface extends instantiation of a UPF and/or other network functions of the operator core network further from the traditional centralized network core, to a new edge that is launched and hosted at the UE level. The mobility edge interface may implement a mobility UPF instance that is launched by one or more applications executed on a primary UE and made accessible through a wireless communication link with a mobility edge RAN established by the primary UE. Through the mobility edge RAN and the mobility UPF instance, a secondary UE may establish a point-to-point wireless communication link (which may be a 3GPP link, or a non-3GPP link) and a user plane data path with the primary UE, in order to communicate data corresponding to a data session between the primary and secondary UE.