Mobility Management Entity Identifier Translation for MEC-RAN Control

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In Mobile Edge Computing (MEC) networks, there is a challenge in directly exchanging control messages between the MEC server and the Radio Access Network (RAN) node due to the lack of a common terminal identifier, which hinders efficient radio resource management and scheduling for radio terminals.

Innovation Solution

A network entity is configured to request and receive a second identifier from a mobility management entity or subscriber server, allowing direct communication with the RAN node using this identifier to facilitate control message exchange between the MEC server and the RAN node.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the MEC server uses its own terminal identifier system (IP address or application layer ID), then the MEC server can identify radio terminals for edge computing services, but the RAN node cannot directly recognize these identifiers for radio resource management

Engineering Contradiction:

ImproveMEC server's ability to identify radio terminalsVSAvoidRAN node's ability to manage radio resources

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces the MME as an intermediary entity that receives terminal identifiers from the MEC server and translates them into RAN node recognizable identifiers. The MME acts as a mediator between the MEC server's identifier system and the RAN node's identifier system, enabling communication and coordination without requiring direct compatibility between the two systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the identifier translation function into a separate entity (MME) rather than requiring direct integration between the MEC server and RAN node. This segmentation allows each system to maintain its own identifier system while the MME handles the translation, reducing complexity and improving ease of operation.

Inventive Principle:

Principle #1Segmentation

2Device complexity

If the MEC server directly communicates with the RAN node using its identifier system, then control message exchange can be simplified, but the RAN node cannot properly manage radio resources due to identifier incompatibility

Engineering Contradiction:

Improvecontrol message exchange mechanismVSAvoidradio resource management effectiveness

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The MME serves as a necessary intermediary that ensures reliable radio resource management by translating identifiers before they reach the RAN node. This intermediary approach maintains reliability of resource management while still enabling control message exchange, as the MME processes and translates identifiers in the control messages.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent establishes a feedback mechanism where the MME receives identifiers from the MEC server, translates them, and provides the translated identifiers to the RAN node. This feedback loop ensures that the RAN node receives properly formatted identifiers for reliable resource management while maintaining the MEC server's original identifier system.

Inventive Principle:

Principle #23Feedback

3Ease of operation

If a common terminal identifier is implemented across MEC server and RAN node, then direct communication becomes possible, but the existing identifier systems of both entities must be changed

Engineering Contradiction:

Improvedirect communication capabilityVSAvoididentifier system modification

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

Rather than modifying the identifier systems of the MEC server or RAN node, the patent introduces the MME as an intermediary that handles identifier translation. This approach enables direct communication capability without requiring changes to the existing identifier systems of the core entities, thus avoiding the complexity of system modification.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The MME is designed to handle multiple identifier types and translation formats, making it a universal intermediary that can accommodate different identifier systems. This multi-functionality allows the MME to translate between various identifier formats without requiring changes to the original systems, enabling direct communication while preserving existing infrastructure.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11116029B2Mobility management entity, network entity, and method and computer readable medium therefor

Publication Date: 2021.09.07 NEC CORP

AI summary

A network entity (5) sends, to a mobility management entity (6) or a subscriber server (9), a request message in order to configure the mobility management entity (6) to report a second identifier to be used by a radio access network node (2) for identifying a radio terminal (1). Further, the network entity (5) receives the second identifier from the mobility management entity (6) directly or through the subscriber server (9) and communicates with the radio access network node (2) by using the second identifier. It is thus, for example, possible to allow an MEC server (or an MEC application hosted on the MEC server) and the radio access network (RAN) node to directly exchange therebetween control messages regarding a specific radio terminal.