Load Balancer Automatic Recovery for Remote Management Authentication Failures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Remote management services face challenges in supporting automatic recovery, particularly in managing devices experiencing authentication failures, where existing systems lack efficient mechanisms to trigger bootstrap processes and synchronize credentials across devices and servers.

Innovation Solution

The implementation of a load balancer within the remote management service that recognizes authentication failures and triggers a bootstrap process by sending bootstrap information to managed devices, facilitating automatic recovery by maintaining error count information and determining when to initiate a bootstrap process based on a threshold of authentication failures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If remote management services use traditional authentication mechanisms, then device management can be performed, but authentication failures cannot be automatically recovered

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidrecovery automation
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The load balancer monitors authentication failures and uses this feedback to automatically trigger bootstrap processes. When authentication failures exceed a threshold, the system receives feedback about the failure state and automatically initiates recovery procedures, creating a closed-loop feedback mechanism that improves reliability without requiring manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-service recovery by automatically detecting authentication failures and initiating bootstrap processes without external intervention. The managed devices themselves are the ones that receive bootstrap information and retry authentication, enabling the system to heal itself automatically and improving both reliability and automation extent.

Inventive Principle:
Principle #25Self-service

2Reliability

If manual recovery processes are used for authentication failures, then recovery can be performed, but system complexity increases and scalability is limited

Engineering Contradiction:
Improverecovery capabilityVSAvoidrecovery process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system eliminates manual recovery operations by implementing automatic detection and recovery. The load balancer autonomously monitors authentication status, triggers bootstrap processes when failures occur, and manages the recovery lifecycle without human intervention, thereby reducing operational complexity while maintaining reliable recovery capability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system prepares for recovery by continuously monitoring authentication failure counts and maintaining threshold criteria. When authentication failures reach the predefined threshold, the bootstrap process is already ready to be triggered immediately, eliminating the need for complex manual recovery procedures and simplifying the overall recovery process.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If authentication failures are handled with traditional error handling, then errors are acknowledged, but continuous management of large-scale devices is disrupted

Engineering Contradiction:
Improveerror information handlingVSAvoidremote management productivity
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The load balancer implements feedback-driven error handling by monitoring authentication failure counts and using this information to automatically trigger recovery processes. This feedback mechanism ensures that error information is not just acknowledged but actively utilized to restore service, minimizing disruption to continuous management operations even in large-scale deployments.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system maintains continuous management productivity by automatically recovering from authentication failures without interrupting overall system operations. The bootstrap process is triggered seamlessly when failures occur, and managed devices are quickly returned to manageable state, ensuring that useful management actions continue uninterrupted even during error recovery.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10505787B2Automatic recovery in remote management services
Publication Date: 2019.12.10 NOKIA OF AMERICA CORP
  • US10505787B2 patent drawing
  • US10505787B2 patent drawing
  • US10505787B2 patent drawing

AI summary

The present disclosure generally discloses improvements in computer performance for supporting automatic recovery for a remote management service (RMS) based on an RMS automatic recovery capability. The RMS automatic recovery capability may be configured to support automatic recovery for an RMS by supporting automatic recovery for a managed device that is experiencing a device authentication failure. The RMS automatic recovery capability may be configured to support automatic recovery for an RMS based on configuration of a load balancer of the RMS to recognize an authentication failure of a managed device and to trigger the managed device to enter a bootstrap process based on recognition of the authentication failure of the managed device. The RMS automatic recovery capability may be configured to support automatic recovery for an RMS based on configuration of a managed device to initiate a bootstrap process based on an indication from a load balancer of the RMS.