Dynamic DNS Record Refresh for Mobile Edge Computing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile edge computing (MEC), the current DNS implementation fails to ensure service continuity and minimize delay when a terminal moves, leading to data loss and increased overheads due to inadequate handling of DNS address changes and edge server handovers.
Innovation Solution
A method and device for dynamically refreshing domain name address records based on location changes, using local and public DNS configurations to ensure continuous service by triggering domain name queries and updating DNS information accordingly, distinguishing between MEC and non-MEC applications, and actively managing DNS records to maintain low latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If edge cloud is deployed closer to RAN network element to minimize delay, then service delay is reduced, but service range of edge cloud decreases
Solution Approach 1:
The patent segments the service area into multiple edge cloud deployment locations along the terminal's movement path. Instead of one edge cloud serving a large area, multiple edge clouds are deployed at different locations (e.g., at different RAN network elements), each serving a smaller local area. This allows the system to maintain low latency by selecting the nearest edge cloud while collectively covering a larger service range through the segmentation of the overall service area.
Solution Approach 2:
The patent implements dynamic selection of edge cloud based on terminal location. The domain name address record is dynamically updated to point to the nearest or most appropriate edge cloud as the terminal moves. This dynamic adaptation allows the system to maintain minimal service delay by always connecting to the closest edge cloud, while the overall service range is extended through the ability to switch between multiple edge clouds at different locations.
2Reliability
If domain name address record is refreshed frequently to ensure service continuity during terminal movement, then service continuity is improved, but resource overheads increase
Solution Approach 1:
The patent performs preliminary action by pre-configuring multiple domain name address records corresponding to different edge cloud locations before the terminal actually moves. The network side prepares the DNS configuration in advance, so when terminal movement is detected or predicted, the domain name address can be quickly switched without requiring frequent real-time refreshing. This reduces resource overheads while maintaining service continuity.
Solution Approach 2:
The patent implements feedback mechanisms where the network side monitors terminal location and movement status, and based on this feedback, selectively refreshes or updates domain name address records. Instead of frequent unconditional refreshing, the system uses feedback from location changes to trigger domain name updates only when necessary, thereby ensuring service continuity while minimizing resource overheads associated with unnecessary DNS queries and updates.
3Area of stationary object
If service flow is migrated between edge servers during terminal handover, then service range is extended, but data loss or delay occurs
Solution Approach 1:
The patent applies beforehand cushioning by maintaining multiple domain name address records in advance corresponding to different edge cloud locations. Before terminal handover occurs, the system already has the necessary DNS configuration information ready. This pre-prepared cushion of alternative address records allows for smooth transition during handover without causing data loss or delay, as the new edge server address is already known and configured beforehand.
Data Source
AI summary
A domain name address obtaining method includes: in a case that a first condition is met, performing a related operation of refreshing a domain name address record to obtain an address of a second server. The second server is an edge server or public server used to exchange data with the first communications device, and the first condition includes: a first indication being received in a PDU session modification process. The first indication is used to instruct to trigger domain name address query; the domain name address record is a mapping relationship between a server domain name and a server address.