Edge Device Discovery via IP-Based Location Inversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-access edge computing (MEC), user equipment (UE) currently needs to provide location information to identify an optimal MEC device, consuming computing resources and increasing latency, and requires frequent configuration changes based on network location, which is cumbersome and resource-intensive.
Innovation Solution
The system identifies an edge device without requiring UE location information by assigning an IP address and using a far cloud component to determine an optimal edge device, preserving computing resources and reducing latency, and determines a UE usage type to select between cloud DNS and edge DNS for network address retrieval, minimizing reconfigurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If UE provides location information to identify optimal MEC device, then edge device identification is achieved, but computing resources of UE are consumed and latency increases
Solution Approach 1:
Instead of having the UE query its own location information (traditional approach), the network component queries the UE's IP address to obtain location information. This inversion of the query direction eliminates the need for UE to access its own location data, reducing UE computing resource consumption and latency while achieving the same edge device identification goal.
2Measurement precision
If UE provides location information to identify optimal MEC device, then edge device identification is achieved, but computing resources of network are consumed
Solution Approach 1:
The system leverages the UE's IP address, which already contains location information, to enable the network to identify the optimal MEC device. This self-service approach uses existing data (IP address) that automatically reflects the UE's location, eliminating the need for separate location information requests and reducing network computing resource consumption.
3Adaptability or versatility
If UE is configured based on network location, then service access is enabled, but configuration rechanges are cumbersome and resource-intensive
Solution Approach 1:
The patent extracts the location information directly from the UE's IP address, which already encodes network location data. By using this extracted information, the system enables adaptive service access without requiring complex configuration changes, as the IP address naturally reflects the current network location and can be used directly for service routing.
Data Source
AI summary
A system may receive registration information regarding a user equipment (UE). The system may determine a UE usage type for the UE from a plurality of UE usage types. The plurality of UE usage types includes a first UE usage type associated with accessing first services using a cloud domain name system (DNS) and a second UE usage type associated with accessing second services using an edge DNS. The system may receive a notification indicating that the UE is requesting access to a service and identify an edge device for providing access to the service. The system may obtain information identifying the UE usage type of the UE based on UE identification information of the UE. The system may provide, to the UE, DNS information regarding using the cloud DNS or the edge DNS to obtain a network address of the edge device.