Member-Oriented Hybrid Cloud OS Architecture for Scalable Stateful Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud operating systems lack self-management capabilities, struggle with high availability and scalability, particularly in stateful member processing clusters, and inefficient routing and load balancing, especially with the enlargement of keyword scale.

Innovation Solution

A member-oriented hybrid cloud operating system architecture based on layer and object models, with a message-based communication method for asynchronous calling, read-write separation, and load balancing, enabling independent management of members and processing clusters, and a polygon queue structure for efficient routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single module architecture of traditional OS is applied to COS, then highly-efficient calling among COS modules is achieved, but the coupling is close, the structure is complicated, and the system is hard to extend

Engineering Contradiction:
Improvecalling efficiencyVSAvoidextensibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the cloud operating system into independent member units with standardized interfaces. Each member can be independently developed, deployed, and scaled, resolving the contradiction by dividing the monolithic system into modular components that maintain efficient internal communication while enabling external extensibility through standardized member interfaces.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If a layer architecture is applied to COS, then the organization structure and dependency relationship among various modules is clear, but the software stack layer is so deep that the core is too large, and the coupling degree among modules is still relatively high

Engineering Contradiction:
Improveorganization structureVSAvoiddistributed processing capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent transitions from a vertical layered architecture to a horizontal member-based architecture. Instead of stacking layers, the system organizes functionality into peer-level members that can be distributed across multiple processing nodes, reducing the depth of the software stack and enabling true distributed processing while maintaining clear organizational structure through member relationships.

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

3Adaptability or versatility

If existing cloud management architecture based on message queue is applied, then loosely coupled architecture is achieved, but there is no member-oriented design, cannot control the member life period, and modules need to consider scaling and high-available methods by themselves

Engineering Contradiction:
Improveloose couplingVSAvoiddevelopment and deployment burden
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms at the member level, where members automatically manage their own lifecycle (creation, activation, deactivation, deletion), scaling, and high-availability configurations through standardized interfaces. This eliminates the need for external coordination while maintaining loose coupling, as each member autonomously handles its own operational concerns.

Inventive Principle:
Principle #25Self-service

4Device complexity

If existing communication protocol based on unstateful assumption is applied to stateful member processing cluster, then simple protocol design is achieved, but cannot achieve high availability and high performance support for stateful members

Engineering Contradiction:
Improveprotocol complexityVSAvoidhigh availability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent changes the statefulness parameter of the communication protocol to support both stateful and unstateful members. By introducing state awareness into the protocol while maintaining backward compatibility, the system achieves high availability for stateful members through proper state management and failure recovery mechanisms, without significantly increasing protocol complexity.

Inventive Principle:
Principle #35Parameter changes

5Device complexity

If tree-based routing algorithm is applied to horizontal scaling processing cluster, then hierarchical routing structure is achieved, but the efficiency is influenced by the enlargement of the keyword scale

Engineering Contradiction:
Improverouting structureVSAvoidrouting efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements a dynamic routing mechanism that adapts to the scale of the processing cluster. The routing algorithm dynamically adjusts its strategy based on the number of members and the scale of keywords, transitioning between hierarchical and flat routing approaches as needed, thereby maintaining efficient routing performance regardless of cluster size while preserving a structured routing framework.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9307017B2Member-oriented hybrid cloud operating system architecture and communication method thereof
Publication Date: 2016.04.05 SHANGHAI INSPUR CLOUD COMPUTING SERVICE CO LTD
  • US9307017B2 patent drawing
  • US9307017B2 patent drawing
  • US9307017B2 patent drawing

AI summary

A member-oriented hybrid cloud operating system architecture and a communication method thereof are provided. A hybrid architecture is established based on layer, object and message models, and a member-oriented idea is applied to manage constituent members and a processing environment thereof. On this basis, high-efficient routing, read-write separation and load balancing are performed on a member processing cluster, satisfying the requirements of being open and compatible, loosely coupled and extensible of a cloud operating system, and solving the self-management problem, the horizontal scaling problem of members and the high-availability problem of stateful members of the existing cloud operating system.