Wireless Edge Service Gateway IP Translation for Centralized Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The ETSI-defined MEC architecture forms a private and closed service management system, limiting the ability of an Internet service background system to effectively manage and control servers deployed in the architecture, affecting service access and requiring complex IP address assignment for service access layer functions.
Innovation Solution
Deploy service access layer functions and business processing servers in an edge data center, utilizing the low latency of the edge data center to improve service access capabilities, and employ a service scheduler in a central cloud for effective management and control of edge services by changing IP addresses between virtual and real addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If service access layer functions are deployed in edge data center, then service access capability is improved, but IP address management complexity increases
Solution Approach 1:
The patent introduces a service gateway as an intermediary component deployed in the edge data center. This service gateway acts as a mediator between terminal devices and business servers, handling IP address translation and service routing. By placing this intermediary at the edge, the system achieves fast service access while the gateway itself manages the complexity of IP address translation, shielding terminal devices from this complexity.
Solution Approach 2:
The patent introduces a new network dimension by deploying service gateways in edge data centers, creating a multi-layered network architecture. This edge layer operates alongside the traditional core network, providing local service access while maintaining connection to central cloud services. This dimensional addition allows simultaneous achievement of low-latency edge access and centralized management.
2Loss of time
If ETSI-defined MEC architecture is used, then local service processing is enabled, but service management control is reduced
Solution Approach 1:
The patent segments service management into two distinct parts: service execution at the edge and service management in the core network. Business servers deployed in edge data centers handle local service processing requests, achieving fast response times. Meanwhile, service gateway instances are managed by service schedulers in the central cloud, maintaining centralized control over service deployment, configuration, and lifecycle management.
Solution Approach 2:
The patent applies local quality by deploying service gateway instances specifically in edge data centers where they provide localized service access functionality. These edge-deployed gateways have the specific quality of being geographically close to users, providing low-latency access. Meanwhile, management control remains centralized in the core network, creating different functional qualities in different locations.
3Speed
If service gateway is deployed in edge data center, then service access speed is improved, but system architecture complexity increases
Solution Approach 1:
The patent designs the service gateway with multi-functionality to handle multiple tasks within a single component deployed at the edge. The service gateway simultaneously performs service request routing, IP address translation, service discovery, and connection management. This consolidation of multiple functions into one universal edge component achieves fast service access while avoiding the complexity of multiple separate systems.
Data Source
AI summary
A wireless communication method is provided. In the wireless communication method, a service request transmitted by a terminal device to a local server is received. A target address of the service request is changed from a first IP address to a second IP address. The first IP address is a virtual address of the local server. The second IP address is a real address of the local server in an edge data center. A service response transmitted by the local server to the terminal device for the service request is received. A source address of the service response is changed from the second IP address to the first IP address.