Edge Microservice Life Cycle Management for Dynamic Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional microservice management approaches in edge computing environments suffer from long release cycles of static, monolithic application packages and often require rush releases for quality or security updates, leading to inefficient and inappropriate deployment of microservices.

Innovation Solution

A microservice management method and system that actively collects function metadata, identifies suitable microservices based on preference factors, and deploys them efficiently through cloud and edge orchestrators, ensuring appropriate installation, initialization, monitoring, and termination based on edge-specific metadata and API definitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional microservice management approaches use static, monolithic application packages, then deployment is simple, but release cycles are long and flexibility is reduced

Engineering Contradiction:

Improverelease cycle speedVSAvoidmicroservice management complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments monolithic application packages into individual microservices that can be independently managed, deployed, and scaled. Each microservice is identified and deployed based on specific function metadata and preference factors, allowing granular control over deployment cycles and reducing overall system complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically identifies and deploys microservices based on runtime conditions, function metadata, and preference factors rather than using static deployment packages. This dynamic approach enables faster release cycles by deploying only the necessary microservices needed for specific functions.

Inventive Principle:

Principle #15Dynamics

2Productivity

If all microservices are deployed to edge environments, then complete functionality is available, but resource usage increases and efficiency decreases

Engineering Contradiction:

Improveedge computing efficiencyVSAvoidnumber of deployed microservices

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by deploying microservices selectively to edge environments based on specific criteria. Each microservice evaluation considers edge-side metadata, hardware capabilities, and function-specific requirements to determine optimal deployment locations, ensuring only necessary microservices are deployed to each edge node.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

Instead of deploying complete microservice bundles to all edge environments, the system deploys only the partial set of microservices necessary for specific functions. This partial action approach reduces resource consumption while maintaining sufficient functionality for edge computing tasks.

Inventive Principle:

Principle #16Partial or excessive action

3Manufacturing precision

If microservices are deployed based on comprehensive metadata analysis, then deployment accuracy improves, but processing time increases

Engineering Contradiction:

Improvemicroservice deployment accuracyVSAvoiddeployment processing time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-collecting and organizing function metadata, edge-side metadata, and microservice metadata before deployment decisions are made. This preliminary preparation enables faster deployment processing while maintaining high accuracy through comprehensive metadata analysis.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent replaces manual or mechanical metadata analysis processes with automated computational methods. The system automatically compares function metadata with microservice metadata using computational algorithms, significantly reducing processing time while maintaining deployment accuracy.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12417134B2Life cycle management of run time services in edge computing environment

Publication Date: 2025.09.16 DELL PROD LP

AI summary

A microservice management method responds to receiving a function request, comprising a request for a particular function, by collecting function metadata for the particular function and sending the function request and the function metadata to a cloud side orchestrator. The function metadata include one or more prerequisite for an execution environment. Suitable microservices for the particular function are identified, in accordance with the function metadata. The identified microservices are sent to an edge side orchestrator that installs, initializes, and monitors these microservices and, responsive to detecting complete execution of the particular function, terminates one or more of the suitable microservices. The identification of suitable microservices may be based, at least in part, on one or more preference factors including a dependency factor, indicative of a historical dependency between the particular function and one or more microservices and a relevance factor indicative of whether a microservice edge-type microservice.