MEC Platform Data Routing via NSH Tag Bypassing Core DNS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile edge computing (MEC) platforms face inefficiencies in data processing due to reliance on domain name system (DNS) resolution, which leads to increased load, slow packet resolution, and potential security risks, especially when handling large business volumes or multiple service requests.
Innovation Solution
The method involves encapsulating a network service header (NSH) tag in data packets to selectively route them to corresponding MEC platforms for processing, bypassing core network DNS and enabling direct forwarding, thereby reducing latency and improving efficiency by allowing flexible selection of MEC platforms for data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If DNS resolution is used in the core network for data packet routing, then data packets can be routed to MEC platforms, but the processing speed decreases and latency increases
Solution Approach 1:
The patent extracts the DNS resolution function from the core network and relocates it to the edge network. Edge nodes perform local DNS resolution for data packets, eliminating the need for core network DNS queries. This extraction resolves the contradiction by enabling fast local resolution (improving speed) while avoiding core network latency (reducing time loss).
Solution Approach 2:
The patent implements preliminary DNS resolution at edge nodes before data packets reach the core network. By pre-resolving domain names at the edge and caching results, the system prepares routing information in advance, eliminating the need for real-time core network DNS queries and thus improving processing speed while reducing latency.
2Productivity
If DNS resolution is performed in the core network, then all data packets can be routed, but the core network load increases
Solution Approach 1:
The patent segments the DNS resolution function from the core network and distributes it to multiple edge nodes throughout the network. Each edge node independently handles DNS resolution for its local area, dividing the overall DNS resolution load across many distributed nodes rather than concentrating it all in the core network, thus reducing core network load while maintaining processing capacity.
Solution Approach 2:
The patent introduces edge nodes as intermediary components between terminals and the core network. These intermediaries perform DNS resolution locally, acting as mediators that handle routing decisions without requiring core network involvement for every data packet, thereby reducing core network load while maintaining overall data processing capacity.
3Reliability
If traditional DNS resolution is used, then data packets can be routed to MEC platforms, but security risks such as DNS hijacking increase
Solution Approach 1:
The patent extracts the DNS resolution process from the traditional core network path and relocates it to distributed edge nodes. This extraction removes the centralization vulnerability that enables DNS hijacking attacks, as each edge node independently resolves domain names locally without relying on centralized DNS infrastructure that could be compromised, thus improving reliability while reducing security risks.
Solution Approach 2:
The patent enables edge nodes to perform self-service DNS resolution independently without requiring queries to external DNS servers. Each edge node maintains its own resolution capabilities and caches, allowing it to autonomously resolve domain names for local data packets, thereby eliminating dependency on external DNS infrastructure that could be subject to hijacking attacks while maintaining reliable routing.
Data Source
AI summary
A data processing method based on a mobile edge computing (MEC) platform includes receiving a target data packet transmitted by a terminal, determining whether the target data packet includes a network service header (NSH) tag, and when determining that the target data packet includes the NSH tag, transmitting the target data packet to a target MEC platform corresponding to the NSH tag for data processing.