MEC Information Discovery Across Operator Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The deployment of Mobile Edge Computing (MEC) on a radio access network limits its service scope and user coverage, making it difficult to satisfy the requirements of third-party applications that need coordination across multiple MECs.
Innovation Solution
Implement a method for MEC information discovery using a Common API Framework (CAPIF) and network elements like CCF, AEF, and NRF to enable API sharing and MEC registration, allowing third-party applications to discover and utilize suitable MECs across different domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If MEC is deployed on a radio access network to reduce data transmission delay, then response speed is improved, but service scope and user coverage are limited
Solution Approach 1:
The patent segments the MEC service architecture into multiple distributed MEC instances across different radio access networks. Each MEC instance operates independently within its local RAN domain, enabling services to be distributed rather than centralized in a single location, thus expanding overall service coverage while maintaining low latency for local users.
Solution Approach 2:
The patent introduces an intermediary discovery mechanism (including discovery messages, registration procedures with network functions, and API exposure frameworks) that enables different MEC instances to find and coordinate with each other. This intermediary layer allows MEC services to extend beyond their local RAN boundaries while preserving the low-latency advantage of edge deployment.
2Loss of time
If MEC service scope is limited to access network scope, then data transmission delay is reduced, but third-party application requirements cannot be satisfied
Solution Approach 1:
The patent implements a universal discovery and coordination framework that enables MEC instances to serve multiple purposes: local low-latency services, cross-domain third-party applications, and inter-MEC coordination. The standardized API exposure mechanism and discovery procedures allow a single MEC instance to adapt to various service requirements without sacrificing its edge computing advantages.
Solution Approach 2:
The patent adds a new dimension to MEC operation by enabling vertical integration across multiple RAN domains through the discovery mechanism. While horizontal service delivery remains local (maintaining low latency), the vertical dimension allows third-party applications to orchestrate services across multiple MEC instances, effectively expanding capability without increasing transmission delay for local operations.
3Reliability
If MEC is deployed close to RAN to improve response speed, then user service quality is enhanced, but service coverage area is restricted
Solution Approach 1:
The patent merges multiple MEC instances from different RAN domains into a coordinated service ecosystem. Through the discovery mechanism and standardized interfaces, these geographically distributed MEC instances function as a unified service platform, maintaining high reliability for local users while collectively expanding service coverage area through inter-MEC collaboration.
Data Source
Figure 1(a)
Figure 1(b)
Figure 2
AI summary
This application discloses a MEC information obtaining method and apparatus. The method includes: receiving, by a first network element, target reference information from a second network element; and sending, by the first network element, to the second network element, information about a MEC corresponding to the target reference information. According to the foregoing method, a MEC discovery process is implemented, so that the second network element can communicate with the MEC based on the obtained information about the MEC, to use a capability of the MEC to implement a service requirement that cannot be satisfied by the second network element. Further, the information about the MEC obtained by the second network element and the second network element may belong to different domains, for example, belong to different operators, so that a solution of invoking the MEC across operators is implemented, and a requirement that a third-party application can provide a service for users of different operators is satisfied.