cMEC-to-eMEC Service Export Through Remote Proxy Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in efficiently exporting services generated at constrained multi-access edge computing (cMEC) applications to edge MEC (eMEC) applications, particularly in negotiating and managing transport protocols across different MEC platforms.
Innovation Solution
The implementation of a remote service proxy application (RSPA) that facilitates the exposure of services between cMEC and eMEC, enabling the negotiation and registration of services through interfaces like Mpp-rspa, allowing for the use of remote transports and managing service-related messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If services are exported from cMEC to eMEC through remote transports, then service accessibility and versatility are improved, but device complexity and protocol negotiation overhead increase
Solution Approach 1:
The patent introduces a remote service proxy application (RSPA) as an intermediary component that mediates between cMEC and eMEC platforms. The RSPA handles service registration, discovery, and communication protocol negotiation automatically, reducing the complexity burden on the core service export mechanism while enabling versatile cross-platform service access.
Solution Approach 2:
The service export functionality is segmented into distinct components: the RSPA layer for protocol negotiation and registration, the service proxy layer for service exposure, and the underlying transport layer. This segmentation allows each component to be optimized independently and simplifies the overall system by distributing complexity across manageable modules.
2Adaptability or versatility
If multiple transport protocols are supported for remote services, then adaptability is improved, but communication overhead and processing time increase
Solution Approach 1:
The system dynamically selects and negotiates the most appropriate transport protocol between cMEC and eMEC based on real-time conditions such as network availability, service requirements, and device capabilities. This dynamic adaptation allows the system to optimize communication efficiency for each specific scenario rather than using a fixed protocol set.
Solution Approach 2:
The RSPA performs preliminary protocol negotiation and service registration before actual service communication begins. By establishing the communication framework and selecting transport protocols in advance, the system reduces runtime overhead and enables faster service activation once the connection is needed.
Data Source
AI summary
A device may be provided. The device may comprise a processor, it may be determined that a first remote service proxy application (RSPA) that may be associated with the device. A first message may be received from a multi-access edge computing (MEC) node that may be associated with a second remote service proxy application (RSPA). The first message may indicate a transport protocol. A second message may be received from the MEC node using the transport protocol. The second message may indicate a service associated with the second RSPA. A third message may be sent to an MEC platform to register the service associated with the second RSPA as a local service that may be associated with the first RSPA.