Cloud Manager for Online Service Network Orchestration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing the deployment and operation of content management applications across multiple networks is a time-intensive and error-prone process for administrators, especially when dealing with large numbers of customers and distributed servers.

Innovation Solution

A cloud manager system that provides centralized coordination for network management, utilizing an idempotent and asynchronous API to handle requests for configuring, updating, and deploying assets across networks, including servers, virtual machines, and databases, while ensuring minimal downtime during upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If centralized coordination is implemented for network management, then management efficiency and consistency are improved, but system complexity increases

Engineering Contradiction:

Improvemanagement efficiencyVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud manager as an intermediary component that sits between administrators and the distributed network infrastructure. This cloud manager receives administration requests, translates them into appropriate actions, and coordinates execution across multiple networks and machines, thereby reducing the complexity burden on administrators while maintaining centralized control.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The management function is segmented into discrete, manageable components within the cloud manager system. Administration requests are broken down into specific operations (deployment, configuration, monitoring) that can be handled independently, allowing the system to manage complexity through modular organization while maintaining overall coordination.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If multiple networks are managed simultaneously, then service coverage and scalability are improved, but administration time and error rates increase

Engineering Contradiction:

Improveservice coverageVSAvoidadministration time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The cloud manager is designed as a universal management platform that can administer multiple different networks and machine types through a single interface. It provides multi-functional capabilities including deployment, configuration, updates, and monitoring across diverse infrastructure components, eliminating the need for separate management processes for each network.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements self-service capabilities where the cloud manager automatically executes management tasks across networks without requiring manual intervention for each operation. Administration requests trigger automated workflows that handle deployment, configuration, and monitoring tasks, significantly reducing administration time while maintaining consistent service coverage.

Inventive Principle:

Principle #25Self-service

3Reliability

If continuous service is maintained during upgrades, then availability is improved, but upgrade complexity and risk increase

Engineering Contradiction:

ImproveavailabilityVSAvoidupgrade complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The cloud manager performs preliminary actions by validating upgrade packages, preparing configuration changes, and pre-checking system compatibility before actual upgrades are executed. This advance preparation allows upgrades to be applied more quickly and with fewer disruptions, maintaining service availability while reducing the complexity of the upgrade process itself.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements beforehand cushioning by creating rollback mechanisms, preserving configuration states, and preparing contingency plans before upgrades are executed. If an upgrade fails or causes issues, the system can quickly revert to previous states, cushioning against the risks of continuous operation during upgrades and maintaining high availability.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If idempotent asynchronous API is used, then network reliability is improved, but response time and processing complexity increase

Engineering Contradiction:

Improvenetwork reliabilityVSAvoidresponse time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The cloud manager implements continuity of useful action by maintaining persistent connections and state information across asynchronous API calls. Rather than treating each request as isolated, the system continues useful actions from previous requests and maintains context, allowing faster response times while the idempotent design ensures network failures do not compromise reliability.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS8799453B2Managing networks and machines for an online service

Publication Date: 2014.08.05 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A cloud manager assists in deploying and managing networks for an online service. The cloud manager system receives requests to perform operations relating to configuring, updating and performing tasks in networks that are used in providing the online service. The management of the assets may comprise deploying machines, updating machines, removing machines, performing configuration changes on servers, Virtual Machines (VMs), as well as performing other tasks relating to the management. The cloud manager is configured to receive requests through an idempotent and asynchronous application programming interface (API) that can not rely on a reliable network.