MEC Middleware Platform Onboarding via Edge Service Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing multi-access edge computing (MEC) environments face complexity and resource inefficiency in onboarding new applications, requiring multiple interactions between computing devices and platforms, leading to redundant communications and excessive resource consumption.

Innovation Solution

A MEC middleware platform is introduced to provide a uniform process for onboarding applications by assigning edge service identifiers (ESIDs) and host identifiers, enabling automatic configuration and authentication, thus reducing the need for redundant communications and optimizing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a uniform onboarding process is implemented, then device complexity and communication overhead are reduced, but the system must introduce a new middleware platform component

Engineering Contradiction:
Improveonboarding process complexityVSAvoidautomatic configuration and authentication
Core Design Contradiction:
Device complexityVSExtent of automation

Solution Approach 1:

The patent introduces a middleware platform as an intermediary component between user devices and the MEC environment. This middleware handles the complex onboarding processes, automatic configuration, and authentication tasks centrally, thereby reducing the complexity burden on individual devices while maintaining high automation levels. The middleware acts as a mediator that simplifies the interaction between devices and the MEC system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple interactions and communications are required for onboarding, then authentication and configuration can be thorough, but resource consumption increases

Engineering Contradiction:
Improveauthentication and configuration reliabilityVSAvoidcomputing and network resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple separate onboarding interactions, authentication steps, and configuration processes into a single unified onboarding flow managed by the middleware platform. By combining these previously separate operations into one coordinated process, the system maintains thorough authentication and configuration reliability while reducing the total resource consumption associated with multiple sequential interactions.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If redundant communications are performed during onboarding, then system security and verification are enhanced, but network resource usage increases

Engineering Contradiction:
Improvesystem security and verificationVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts the redundant communication and verification tasks from the distributed device-level processes and consolidates them into centralized authentication and verification operations performed by the middleware platform. This extraction eliminates unnecessary redundant communications at the device level while preserving the essential security and verification functions, thereby reducing network resource consumption without compromising system security.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11909845B2Methods and systems for managing applications of a multi-access edge computing environment
Publication Date: 2024.02.20 VERIZON PATENT & LICENSING INC
  • US11909845B2 patent drawing
  • US11909845B2 patent drawing
  • US11909845B2 patent drawing

AI summary

Examples herein involve a multi-access edge computing (MEC) environment. An example process may include receiving a tenant application that is to be hosted in a MEC environment. The MEC environment may be situated between a user device and an external platform. The process may include assigning an edge service identifier (ESID) to the tenant application. The ESID may be used to indicate that a message, associated with the user device, involves the tenant application. The process may include assigning a host identifier to the tenant application. The host identifier may be used to indicate that report data, associated with execution of the tenant application within the MEC environment, is to be provided to the external platform. The process may include routing communications associated with the tenant application using the ESID and the host identifier.