Distributed Edge Cloud Fabric for Lower Bandwidth Waste

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing hierarchical client-server architecture in cloud computing is inefficient due to bandwidth wastage, energy consumption, and security vulnerabilities, with central cloud resources being a bottleneck and exposing user data to risks.

Innovation Solution

Decentralize cloud computing by enabling any computing device to act as a cloud server, forming a larger 'edge cloud fabric' that processes data locally and communicates directly with other edge devices, reducing reliance on central servers and enhancing data privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is sent from hundreds of billions of client devices to tens of millions of centralized cloud servers, then cloud hosting services can be provided, but bandwidth is wasted and energy consumption increases

Engineering Contradiction:
Improvecloud hosting service capabilityVSAvoidbandwidth waste and energy consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments the centralized cloud computing system into distributed edge computing nodes. Instead of all data flowing to central servers, computing tasks are divided and executed locally at edge devices (routers, set-top boxes, client devices), reducing the volume of data transmitted over the network and minimizing bandwidth waste while maintaining cloud hosting capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimensional approach by adding edge computing layers between clients and central clouds, creating a multi-dimensional architecture. This allows data processing to occur at multiple levels (edge, fog, cloud) rather than forcing all traffic through a single centralized dimension, thereby reducing energy consumption while preserving service capability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If cloud resources are designed for easy access to millions of developers and application service providers, then service accessibility is improved, but vulnerabilities and security holes increase

Engineering Contradiction:
Improveservice accessibilityVSAvoidvulnerabilities and security risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements local quality by allowing different security policies and access controls at different edge nodes. Each edge device can enforce localized security measures tailored to its specific context, while still providing easy access to services. This distributed security approach reduces vulnerabilities compared to uniform centralized access control.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces edge devices as intermediaries between clients and central cloud resources. These intermediaries can filter, validate, and secure communications, acting as a buffer that maintains service accessibility while reducing security risks by preventing direct exposure of central cloud resources to millions of developers.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If a hierarchical client-server architecture is used with servers in data centers, then application deployment is rapid and low-cost, but central cloud resources become a bottleneck for future growth

Engineering Contradiction:
Improveapplication deployment efficiencyVSAvoidsystem scalability and growth capability
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent transforms the static hierarchical architecture into a dynamic system where edge devices can dynamically assume server roles. Computing resources are not fixed in central data centers but can be activated anywhere in the network based on demand, allowing the system to scale flexibly without being constrained by central resource bottlenecks while maintaining deployment efficiency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent makes edge devices universal by enabling them to perform multiple functions: acting as clients, servers, or both simultaneously. This multi-functionality allows the same device to provide cloud services locally while also consuming services, eliminating the need for dedicated central servers and enabling scalable growth without proportionally increasing central infrastructure.

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

4Productivity

If data is stored and hosted on third party cloud servers, then cloud service functionality is provided, but data privacy and security are exposed to risks

Engineering Contradiction:
Improvecloud service functionalityVSAvoiddata privacy and security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent enables data owners to self-host services on their own edge devices rather than relying entirely on third-party cloud providers. Users can run their own instances of applications and store data locally, maintaining full control over their data privacy and security while still accessing cloud service functionality when needed through the edge cloud network.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12407574B2Method and system for distributed edge cloud computing
Publication Date: 2025.09.02 MIMIK TECH CANADA INC
  • US12407574B2 patent drawing
  • US12407574B2 patent drawing
  • US12407574B2 patent drawing

AI summary

Embodiments of an edge cloud computing device are disclosed. In an embodiment, the edge cloud computing device includes an edge node activation module configured to receive a request from an application running in the edge cloud computing device and determine a type of one or more microservices required to service the received request. The edge node activation module is configured to process the request locally in the edge cloud computing device when the determined type corresponds to one or more microservices locally hosted in the edge cloud computing device.