Edge Server Service Sharing to Reduce Cloud Component Waste

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The deployment of multiple public service components on edge servers for cloud applications leads to resource wastage due to repeated deployment and inefficient utilization.

Innovation Solution

A cloud processing system with a central cluster and edge servers that share services, utilizing different communication channels for first-type and second-type data based on real-time requirements, allowing edge servers to invoke central cluster services independently, thereby avoiding repeated component deployment and enhancing resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If multiple public service components are deployed on each edge server to support cloud applications, then the operation experience of cloud application users is improved, but component resources are wasted due to repeated deployment

Engineering Contradiction:
Improveoperation experienceVSAvoidcomponent resource waste
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent merges multiple edge servers into a unified edge cluster that shares common public service components. Instead of deploying identical components on each edge server, the cluster consolidates these components into shared resources that can be accessed by all edge servers, thereby reducing resource duplication and waste while maintaining service quality.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal public service components that can serve multiple edge servers simultaneously. These components are designed with multi-functionality to handle requests from different edge servers and cloud applications, allowing a single component instance to perform multiple roles and serve various purposes across the cluster.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If different communication channels are used for first-type and second-type data, then data transmission efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedata transmission efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments data transmission into two distinct channels: a first communication channel for first-type data and a second communication channel for second-type data. This segmentation allows each channel to be optimized for its specific data type, improving transmission efficiency while maintaining manageable system complexity through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by tailoring the communication channel characteristics to the specific requirements of each data type. The first communication channel is optimized for first-type data with specific performance characteristics, while the second channel is optimized for second-type data, ensuring that each channel has the appropriate quality attributes for its intended purpose.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12452339B2Data processing method and system, related device, storage medium, and product for an edge server in cloud computing system
Publication Date: 2025.10.21 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US12452339B2 patent drawing
  • US12452339B2 patent drawing
  • US12452339B2 patent drawing

AI summary

The embodiments of this application disclose a data processing method performed by an edge server physically closest to a client of a target cloud application. After acquiring running data of the target cloud application from the client, the edge server determines a type of the running data. When the running data is first-type data, the edge server transmits the running data to the central cluster via a first communication channel between the edge server and the central cluster, the first communication channel being a channel matching a real-time requirement of the first-type data. But when the running data is second-type data, the edge server transmits the running data to the central cluster via a second communication channel, so that the central cluster responds to the second-type data with a service matching the second-type data.