MEC Service Profile Caching for Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mobile edge computing (MEC) systems, handling user service profile information efficiently is challenging due to latency issues when retrieving data from core networks, and transferring all user service profile data to MEC servers requires significant storage and communication resources, becoming inefficient as the number of mobile terminals and applications increases.

Innovation Solution

A method is implemented where a network element in the core network receives application status change messages from MEC servers, detects location updates from user equipment, and obtains service profile data to generate and provide an MEC service policy to the MEC server, including priority and trigger parameters, thereby optimizing service provisioning and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service profile data is retrieved from the core network for each user request, then data accuracy is maintained, but latency increases

Engineering Contradiction:
Improvedata accuracyVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent caches service profile data at the MEC server in advance, before it is actually needed. When a user requests a service, the profile data is already available locally at the MEC server, eliminating the need for real-time retrieval from the core network. This preliminary caching action resolves the contradiction by providing accurate data (maintained through update mechanisms) without the latency of on-demand retrieval.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a caching mechanism as an intermediary layer between the core network and the MEC server. This cache stores service profile data locally, acting as a mediator that provides data quickly without requiring direct communication with the core network for each request. The intermediary cache resolves the latency issue while maintaining data accuracy through selective updates from the core network.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If all user service profile data is transferred to the MEC server, then service provisioning speed improves, but storage and communication resources are significantly consumed

Engineering Contradiction:
Improveservice provisioning speedVSAvoidstorage and communication resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary service profile data from the complete user profile stored in the core network. Instead of transferring all user service profile data to the MEC server, the system selectively retrieves and caches only the specific profile information needed for current service delivery. This extraction principle resolves the contradiction by improving service provisioning speed while minimizing storage and communication resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements local quality by caching service profile data specifically at the MEC server where it is needed for service delivery, rather than universally distributing all user data to all MEC servers. Each MEC server maintains only the profile data relevant to its local user base and service requirements. This localized approach improves service provisioning speed for local users while reducing overall storage and communication resource consumption across the network.

Inventive Principle:
Principle #3Local quality

3Loss of time

If service profiles are cached at the MEC server, then latency is reduced, but data may become outdated

Engineering Contradiction:
ImprovelatencyVSAvoiddata currency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the MEC server monitors service profile data usage and selectively updates cached data from the core network based on actual service delivery needs. When a user requests a service, the system checks if the cached profile data is current or needs updating. This feedback-driven update approach maintains data currency while minimizing unnecessary communication with the core network, thus resolving the contradiction between low latency and data accuracy.

Inventive Principle:
Principle #23Feedback

4Productivity

If service profile data is obtained dynamically based on location updates, then resource efficiency improves, but system complexity increases

Engineering Contradiction:
Improveresource efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-fetching and caching service profile data at the MEC server before actual service delivery, triggered by location updates or service requests. This preliminary caching reduces the need for dynamic data retrieval during service delivery, improving resource efficiency. The system complexity is managed by implementing this pre-fetching logic at controlled points in the network architecture, specifically at the MEC server where location and service information is already available.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3744069B1Method and apparatus for handling user service profile information in a communications network implementing mobile edge computing (MEC)
Publication Date: 2022.10.19 NOKIA SOLUTIONS & NETWORKS OY
  • EP3744069B1 patent drawingFigure 1A
  • EP3744069B1 patent drawingFigure 1B~1C
  • EP3744069B1 patent drawingFigure 2~3

AI summary

A method of handling user service profile information in a communications network, the communications network including a core network (CN) and a radio access network (RAN), includes receiving, at a first network element located in the CN, a first application status change message from a first mobile edge computing (MEC) server located in the RAN, the first application status change message indicating one or more applications currently running on the first MEC server; detecting a location update message received at the CN from a UE attached to the RAN; and in response to detecting the location update message, obtaining service profile data of the UE for at least one service corresponding to at least one of the one or more applications, and providing the obtained service profile data to the first MEC server.