MEC Platform Deployment via Characteristic Root Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-access edge computing (MEC) platform deployment methods face challenges such as increased delay due to large forwarding routing tables and high operational costs associated with limited equipment room space, particularly when carriers exclusively build MEC platforms.
Innovation Solution
A MEC platform deployment method that utilizes a characteristic root apparatus to initiate an authentication process with a cloud server, automatically install MEC platform components, and execute edge policies or implement service governance, facilitating plug-and-play deployment and co-building of MEC platforms by multiple parties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the carrier centrally builds a MEC node for a plurality of users, then the MEC node is reused by the plurality of users, but the delay for a forwarding routing table lookup increases and services of the plurality of users are affected once the MEC node is changed
Solution Approach 1:
The patent divides the centralized MEC node into distributed MEC nodes deployed at different network edges. Each MEC node serves a specific user group locally, eliminating the single point of congestion. This segmentation reduces forwarding routing table lookup delay by distributing the routing burden across multiple nodes while maintaining adaptability through the virtualized nature of the MEC platforms.
2Adaptability or versatility
If the carrier builds different MEC nodes for different vendors, then the carrier cannot deploy more servers due to limited equipment room space on a live network, but the carrier needs to invest a large amount of money to build a new site, resulting in increased operation costs
Solution Approach 1:
The patent implements a universal MEC platform architecture that can be deployed on existing carrier infrastructure (servers, storage, network elements) without requiring dedicated hardware for each vendor. The virtualized MEC nodes can run on any standard server, enabling multi-vendor deployment within existing equipment room space. This universality eliminates the need for expensive new site construction while maintaining the ability to support multiple vendors simultaneously.
3Reliability
If the carrier exclusively builds the MEC platform, then the carrier has full control, but the carrier needs to cooperate with third parties to extend edge computing to third-party network environments
Solution Approach 1:
The patent introduces a centralized management platform as an intermediary between the carrier and third-party vendors. This management platform maintains carrier control over the overall MEC system while enabling third-party vendors to deploy their own virtualized MEC nodes. The intermediary coordinates authentication, resource allocation, and communication between carrier and vendor nodes, allowing extended edge computing to third-party networks while preserving carrier authority.
4Ease of operation
If manual configuration is used for MEC platform deployment, then the deployment process is complex, but automated deployment is not yet implemented
Solution Approach 1:
The patent implements self-service deployment where the centralized management platform automatically authenticates third-party servers, allocates resources, and deploys virtualized MEC nodes without manual configuration. The system automatically generates authentication credentials, provisions network resources, and configures routing tables based on pre-defined templates. This automation dramatically simplifies the deployment process while maintaining security through automatic authentication mechanisms.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A MEC platform deployment method is provided, relates to the field of communications technologies, and is used to fast deploy a MEC platform. The method includes: A server initiates an authentication process to a cloud server by using a characteristic root apparatus, where a digital certificate of a user and first authentication information are prestored in the characteristic root apparatus; after the authentication succeeds, the server installs a MEC platform component, where the MEC platform component includes LUPF software and/or APP agent software; then, the server executes an edge policy by using the LUPF software, where the edge policy includes a traffic routing policy and/or a charging policy; and/or the server implements service governance on a local application by using the APP agent software. The technical solutions of this application are applicable to a deployment process of a MEC platform.