Edge Enabler Server API Interoperability for 5G MEC
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing mobile communication network is closed, making it difficult to utilize network information and services for external multi-access edge computing (MEC) applications and interoperating between systems, limiting the spread of 5G+ convergence service industry, which requires sharing network resources and supporting third-party service application programming interfaces (APIs) in the 5G MEC platform.
Innovation Solution
A method for enabling service APIs by performing EAS registration with an edge enabler server, publishing service APIs with key performance indicators (KPIs), discovering, and invoking these APIs, allowing network operators to provide a service platform that localizes service invocation traffic to the network edge, and utilizing a common API framework for interconnection and discovery across different edge application servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the mobile communication network maintains a closed structure, then network security and control are improved, but interoperability with external MEC applications and third-party service providers is worsened
Solution Approach 1:
The patent introduces an edge enabler server as an intermediary component that mediates between the closed mobile communication network and external MEC applications. This server enables third-party service providers to publish and expose service APIs within the network boundary, allowing controlled interoperability while maintaining the closed network structure for security. The intermediary facilitates service discovery, registration, and invocation without requiring external systems to directly access the core network.
Solution Approach 2:
The patent implements a universal service API framework that enables multiple types of services and applications to interoperate through standardized interfaces. By defining common service APIs that can be published, discovered, and invoked by various third-party providers, the system achieves multi-functionality and broad adaptability while maintaining a unified controlled environment within the closed network.
2Productivity
If service APIs are published and discovered through a centralized edge enabler server, then service management and resource sharing are improved, but system complexity increases
Solution Approach 1:
The patent implements self-service mechanisms where third-party service providers autonomously publish their service APIs to the edge enabler server without requiring manual configuration or intervention from network operators. Similarly, MEC applications can autonomously discover and subscribe to relevant services. This automation improves resource sharing efficiency while managing complexity through standardized self-service procedures rather than manual management.
Solution Approach 2:
The system incorporates feedback mechanisms where the edge enabler server maintains a registry of published service APIs and provides discovery information to requesting applications. This feedback loop enables efficient service matching and resource allocation while centralizing management functions that reduce overall system complexity despite the increased number of components.
3Loss of time
If service invocation traffic is localized to the network edge, then service latency is improved, but network infrastructure requirements increase
Solution Approach 1:
The patent applies local quality by deploying service invocation and processing functions at the network edge rather than centrally. By localizing traffic handling to edge locations, the system reduces latency for services requiring real-time processing. The edge enabler server and service APIs are deployed at appropriate network edges, enabling localized service discovery and invocation close to the data source or consumer.
Data Source
AI summary
Provided are a method of enablement of a service application programming interface (API) exposed by an edge application server (EAS) and a device for performing the same. A service API enablement method includes performing, by a first EAS, EAS registration with an edge enabler server (EES), performing, by a second EAS, EAS registration with the EES, transmitting, by the second EAS, a service API publish request to the EES in order to publish a service API of the second EAS, discovering, by the first EAS, a service API in the EES, and invoking, by the first EAS, the service API discovered in the EES and published by a second EAS, wherein the service API publish request may include a service key performance indicator (KPI).