Multi-access Edge Computing Slice Communication via Platform Registry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Multi-access Edge Computing (MEC) systems face performance limitations when MEC slices need to communicate with each other, as data exchange requires traversal through the full operator's core network, resulting in high latency, especially in vehicular networks where vehicles connected to different communication service providers must communicate through remote V2X applications.
Innovation Solution
A method and system architecture that enable direct communication between MEC slices by establishing mutual access policies and configurations between MEC providers, allowing for direct slice-to-slice data exchange over shared physical platforms, leveraging novel interfaces and a platform registry for dynamic data exchange and service exposure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data exchange between MEC slices traverses through the full operator's core network, then network security and centralized control are maintained, but communication latency increases significantly
Solution Approach 1:
The patent segments the core network traversal path by introducing direct slice-to-slice communication interfaces at the edge. Instead of forcing all data exchanges through the centralized core network, the system creates dedicated communication channels between MEC slices that share the same physical platform, thereby reducing latency for inter-slice communication while maintaining core network security for external access.
Solution Approach 2:
The patent introduces a platform registry and mutual access policy mechanism as intermediaries to enable secure direct communication between MEC slices. These intermediaries facilitate authentication, authorization, and routing between slices without requiring core network traversal, thus reducing latency while maintaining security through policy-based control.
2Loss of time
If direct slice-to-slice communication is enabled, then communication latency is reduced, but system complexity increases due to mutual access policies and configurations
Solution Approach 1:
The patent creates a universal platform registry and mutual access policy framework that can be applied across multiple MEC slices and tenants. This multi-functional system handles authentication, authorization, routing, and configuration management in a unified manner, reducing the need for slice-specific complex configurations and simplifying the overall system architecture.
Solution Approach 2:
The patent enables MEC slices to perform self-configuration and self-authentication through automated discovery procedures and mutual access policies. The system automatically establishes communication channels between slices based on pre-configured policies, reducing the need for manual configuration and lowering operational complexity.
3Adaptability or versatility
If MEC providers become tenants of physical infrastructure provider, then resource allocation flexibility is improved, but access control and security management become more complex
Solution Approach 1:
The patent introduces the platform registry and mutual access policy mechanism as intermediaries between the physical infrastructure provider and multiple MEC provider tenants. This intermediary layer abstracts the complexity of access control and security management, providing a standardized interface for resource allocation and access authorization while maintaining security policies.
Solution Approach 2:
The patent uses parameter-based access control where mutual access policies define specific parameters (permissions, authentication methods, resource limits) that can be dynamically adjusted. This allows flexible resource allocation to different tenants while maintaining security through parameter-driven access control rather than hard-coded complex authorization logic.
Data Source
AI summary
A method performed by a first edge computing entity that is configured to provide supporting functions for serving an application includes performing retrieval and discovery procedures. The retrieval procedure is performed by: sending, to an edge entity configured for registration of one or more edge computing entities, a request to retrieve an address of a second edge computing entity that is configured to provide supporting functions for serving a further application; and receiving, from the edge entity, a response to the request to retrieve the address of the second edge computing entity including the address of the second edge computing entity. The discovery procedure is performed by: sending, to the second edge computing entity, a discovery request for discovering information for accessing the further application; and receiving, from the second edge computing entity, a discovery response including discovered information for accessing the further application.