MEC Architecture with Class-Specific Tags for Mobility Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing MEC architectures face challenges in efficiently managing mobility and dynamic information services, particularly in 5G communication systems, due to the spatial separation of information sources, processing, and consumption, which leads to difficulties in discovering, storing, and forwarding data while maintaining edge processing resources and sink capabilities.

Innovation Solution

The proposed MEC architecture employs class-specific tags to separate DATA, APPLICATION, and USER objects, enabling flexible and efficient communication by dynamically tagging data classes and using these tags for pathfinding and object connections across spatially distributed network entities, thereby optimizing network usage and processing in dynamic environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If MEC architecture uses traditional cloud-based services for data processing, then centralized processing power is available, but network latency increases and responsiveness decreases

Engineering Contradiction:
Improvenetwork latencyVSAvoiddistributed architecture complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments the centralized cloud architecture into distributed edge nodes deployed at multiple locations. Each edge node independently processes data locally, eliminating the need for all data to traverse the entire network to reach a central cloud. This segmentation reduces latency while distributing computational burden across multiple simpler nodes rather than one complex centralized system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a spatial dimension to data processing by deploying edge nodes at geographically distributed locations. Instead of a single centralized processing point, data can be processed at multiple simultaneous locations across the network, effectively adding a spatial dimension to the architecture. This enables parallel processing and reduces the distance data must travel.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If MEC architecture implements dynamic mobility management, then service continuity is improved, but system complexity increases

Engineering Contradiction:
Improveservice continuityVSAvoidmobility management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a mobility management intermediary layer that coordinates between user equipment and multiple edge nodes. This intermediary handles the complexity of tracking user locations, managing handovers between nodes, and maintaining service continuity. By centralizing mobility management logic in this intermediary layer, the complexity is contained and managed systematically rather than being distributed throughout the entire network.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements feedback mechanisms where edge nodes continuously report their status and capabilities to the mobility management system. This feedback enables dynamic adaptation to network conditions, allowing the system to automatically select optimal edge nodes for users based on real-time factors like location, load, and availability, thereby maintaining service continuity through automated responses to changing conditions.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If MEC architecture separates DATA, APPLICATION, and USER objects spatially, then network flexibility is improved, but data discovery and connection difficulty increases

Engineering Contradiction:
Improvenetwork flexibilityVSAvoiddata discovery difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces a discovery and connection intermediary layer that mediates between spatially separated DATA, APPLICATION, and USER objects. This intermediary maintains a registry or index of available objects and their locations, enabling efficient discovery without requiring direct scanning of the entire distributed network. The intermediary simplifies the search process by pre-organizing information about available resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal discovery mechanism that can locate any type of object (DATA, APPLICATION, or USER) using a common interface and protocol. This universal approach allows the system to discover different object types through the same process, reducing the complexity of handling multiple discovery scenarios. The multi-functional discovery mechanism works consistently across all object types regardless of their specific characteristics or locations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3707881B1Multi-access edge computing (MEC) architecture and mobility framework
Publication Date: 2024.06.26 INTEL CORP
  • EP3707881B1 patent drawingFigure 1
  • EP3707881B1 patent drawingFigure 2
  • EP3707881B1 patent drawingFigure 3

AI summary

An architecture to allow the spatial separation of information sources, information processing, and information consumption using objects and tags, including in mobile / multi-access edge computing (MEC) communication environments, is disclosed. In an example, a request for information provided to a network entity (such as a MEC entity) results in the receipt of an object and a tag, as a device operates in an operational area of an information service. The object provides data for the information service, and the tag provides the metadata related to a context of the information service and the object from another entity, for another entity located within the operational area of the location service. The use of this object, including in the form of an application, data, or user object type, allows a transfer and use of data and context for the information service that is independent from the access network.