Edge Integration Control for MEC Service Linkage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Multi-Access Edge Computing (MEC) standards limit service continuity and linkage between MEC services across different systems, restricting direct communication and hindering the maintenance of low latency and high-volume data transfer, which is essential for emerging applications like AR/VR and AI.

Innovation Solution

An edge integration control device with an information register and linkage controller that searches for and facilitates direct linkage between MEC services by acquiring and registering information from MEC Orchestrators, enabling communication between MEC systems and supporting linkage through a federation manager structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If indirect linkage through public cloud is used, then service linkage between different MEC systems is possible, but transmission latency increases and data transfer capacity decreases

Engineering Contradiction:

Improveservice linkage capabilityVSAvoidtransmission latency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces a service gateway as an intermediary component within the MEC system that enables direct service linkage between different MEC systems. The service gateway establishes direct communication channels between services in different MEC systems, eliminating the need for indirect cloud-based routing while maintaining standardized interfaces for interoperability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the MEC system architecture by introducing dedicated service gateway entities that handle inter-MEC communication separately from core MEC operations. This segmentation allows direct peer-to-peer service linkage while maintaining system modularity and standardized interfaces.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If indirect linkage through public cloud is used, then service linkage between different MEC systems is possible, but data transfer capacity is limited

Engineering Contradiction:

Improveservice linkage capabilityVSAvoiddata transfer capacity

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The service gateway acts as a local intermediary that enables high-capacity direct data transfer between MEC systems without routing through the public cloud. This maintains the ability to link services across different MEC systems while preserving full data transfer capacity through dedicated communication channels.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new communication dimension by establishing direct lateral connections between MEC systems through service gateways, rather than forcing all communication through the vertical cloud pathway. This creates parallel high-capacity data transfer routes.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

3Speed

If direct linkage between MEC services is implemented, then low latency and high-volume data transfer is maintained, but system complexity increases

Engineering Contradiction:

Improvedata transfer speedVSAvoidsystem complexity

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The service gateway is designed as a universal component that handles multiple functions including service registration, discovery, direct communication establishment, and standardized interface management. This multi-functionality reduces overall system complexity by consolidating inter-MEC operations into a single versatile entity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The service gateway performs preliminary actions by pre-establishing communication channels and registering services before actual data transfer occurs. This preparation work simplifies real-time operations and reduces the complexity of dynamic service linkage.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If service continuity through handover is implemented, then service continuity during terminal movement is ensured, but service linkage between different MEC systems is not supported

Engineering Contradiction:

Improveservice continuityVSAvoidservice linkage capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent merges the service continuity function with the service linkage function by integrating handover capabilities into the service gateway architecture. This allows the same infrastructure that ensures continuous service during terminal movement to also enable direct service linkage between different MEC systems.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The service gateway is designed to perform multiple functions simultaneously including both service continuity management through handover and service linkage establishment between different MEC systems, eliminating the need for separate specialized systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12132602B2Edge integration control device and method for searching for a MEC application based on linkage triggering

Publication Date: 2024.10.29 SK TELECOM CO LTD

AI summary

The present invention proposes a scheme for realizing a structure and a technology which can support direct linkage between services in an inter-MEC environment, the services being mounted in different MEC systems, respectively.