Service Management via Popularity-Based Local Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed systems face inefficiencies due to time-consuming remote invocations, which degrade response efficiency and require costly, inflexible manual analysis and deployment for service dependencies, limiting adaptability and increasing operational complexity.

Innovation Solution

A method and device for service management that detects the popularity of remote services and migrates them locally when a threshold is reached, using a popularity detection module and migration control module to optimize service deployment and reduce remote invocation time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If remote invocation is used for service interaction in distributed systems, then system flexibility and adaptability are improved, but response efficiency deteriorates due to significant time consumption

Engineering Contradiction:
Improvesystem flexibilityVSAvoidresponse time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-loading frequently used remote services into local memory before they are actually needed. The system detects service usage patterns and proactively caches service code and data locally, so that when the service is invoked, it can execute immediately without network latency. This resolves the contradiction by preparing services in advance based on predicted usage, maintaining flexibility while eliminating response time delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements local quality by creating different execution environments for different services based on their usage characteristics. Frequently accessed services are loaded locally with high-speed access, while less frequent services remain remote. This selective localization optimizes response time for critical services while maintaining system flexibility through continued remote access capability for other services.

Inventive Principle:
Principle #3Local quality

2Loss of time

If application analysis and physical concentration deployment are performed to reduce remote invocation time, then response efficiency is improved, but system flexibility and adaptability deteriorate

Engineering Contradiction:
Improveremote invocation timeVSAvoidsystem flexibility
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The patent applies dynamics by making the service deployment structure adaptive rather than static. Instead of permanently concentrating services based on initial analysis, the system continuously monitors service usage patterns and dynamically adjusts which services are loaded locally. When service dependencies or usage patterns change, the system automatically reconfigures the local-remote service architecture, maintaining both fast response times and system flexibility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements feedback mechanisms that continuously monitor service invocation patterns, performance metrics, and system state. This feedback information is used to automatically adjust service loading decisions, ensuring that services are concentrated locally only when it actually improves performance. The feedback loop prevents premature or incorrect service concentration, maintaining system flexibility while optimizing response efficiency based on actual runtime conditions.

Inventive Principle:
Principle #23Feedback

3Productivity

If manual application analysis and redeployment are performed for service dependency changes, then service performance is optimized, but operational cost and complexity increase

Engineering Contradiction:
Improveservice performanceVSAvoidoperational complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling the system to automatically analyze service dependencies, detect usage patterns, and perform optimization decisions without human intervention. The system monitors its own performance metrics, identifies services that would benefit from local loading, and automatically configures the service architecture. This eliminates the need for manual analysis and redeployment operations, reducing operational complexity while maintaining performance optimization.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical operations (human analysts examining service dependencies and performing redeployment) with automated computational mechanisms. The system uses algorithms to analyze service call patterns, calculate optimal loading strategies, and automatically configure service deployment. This substitution transforms a labor-intensive, error-prone manual process into an automated, scalable system that reduces operational complexity while improving service performance.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10635454B2Service management method and the device
Publication Date: 2020.04.28 ADVANCED NEW TECHNOLOGIES CO LTD
  • US10635454B2 patent drawing
  • US10635454B2 patent drawing

AI summary

The present invention provides a method and a device for service management, wherein the method comprises: detecting popularity of use of a remote target service by an application; and when the popularity reaches a first threshold value, loading the target service to the application locally. The present invention improves the response efficiency and adaptive capability of a distributed system.