On-Premise Server Cloud Configuration Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in reliably configuring servers with configuration data from cloud-based services, particularly in ensuring accurate implementation and management of configuration changes without requiring additional hardware or intermediaries, and in maintaining synchronization between the server and cloud-based service regarding configuration versions.

Innovation Solution

The system employs a stateless protocol for servers to poll cloud-based services at predetermined intervals, validate configuration changes, and commit updates, allowing for efficient and reliable configuration management without the need for additional hardware or intermediaries, and ensures both the server and cloud-based service have a consistent understanding of the current configuration version.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server polls the cloud-based service at a predetermined first interval, then the server can periodically check for configuration changes, but the polling frequency may be too low to respond quickly to new configuration changes

Engineering Contradiction:
Improveconfiguration update reliabilityVSAvoidtime to receive configuration updates
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies dynamics by transitioning from a static polling interval to a dynamic one. The server monitors for configuration change notifications from the cloud-based service, and when changes are detected, the server automatically reduces its polling interval to a second, faster interval. This allows the system to maintain reliable configuration updates while reducing time loss through adaptive polling frequency based on actual change activity.

Inventive Principle:
Principle #15Dynamics

2Reliability

If the server performs configuration validation before committing changes, then the reliability of configuration implementation is improved, but the complexity of the configuration management process increases

Engineering Contradiction:
Improveconfiguration implementation reliabilityVSAvoidconfiguration management process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback by having the server perform configuration validation and then provide feedback to the cloud-based service about the validation result. The server sends a service reply indicating whether the configuration validation was successful, allowing the cloud-based service to understand the server's capability to implement changes. This feedback mechanism improves reliability by ensuring changes are only committed if validated, while the automated nature of the process keeps complexity manageable.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If the cloud-based service pushes configuration changes to the server, then the server receives updates automatically, but the server cannot control when to poll or when changes are available

Engineering Contradiction:
Improveconfiguration update automationVSAvoidpolling and synchronization mechanism complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies self-service by having the server actively poll the cloud-based service to check for configuration changes rather than passively receiving pushes. The server initiates the communication, sends data packets containing its current configuration version information, and controls its own polling timing. This self-service approach simplifies the architecture by eliminating complex push mechanisms while maintaining automation through the server's autonomous polling and change detection capabilities.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If the server transitions from existing configuration version to proposed configuration version, then the server implements new features, but the risk of configuration errors and rollback needs increases

Engineering Contradiction:
Improveconfiguration update flexibilityVSAvoidconfiguration version transition reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements preliminary action by having the server perform configuration validation before actually transitioning from the existing configuration version to the proposed version. The server validates the proposed configuration changes against its current state and only proceeds with the transition if validation succeeds. This preliminary validation step ensures that the server is ready to accept and correctly implement the new configuration, reducing the risk of errors during version transitions while maintaining the flexibility to adopt new features.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10439873B2Reliably configure on-premise servers from the cloud
Publication Date: 2019.10.08 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10439873B2 patent drawing
  • US10439873B2 patent drawing
  • US10439873B2 patent drawing

AI summary

Optimizations are provided for reliably configuring an on-premise server using configuration data stored at a cloud-based service. An on-premise server polls the cloud-based service to determine whether any new configuration changes are available for the on-premise server to implement. In response to an indication that a new configuration change is available for the on-premise server, the on-premise server performs a validation to determine whether the new configuration change is committable by the on-premise server. Afterwards, the on-premise server receives the new configuration change and then attempts to commit to that new configuration change.