Remote Server System Robustness via Segmentation and Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Intruder alarm security systems face robustness issues when the link or network between a system under control and a remote control system becomes unavailable or experiences insufficient bandwidth or latency, leading to potential security compromises.

Innovation Solution

Implementing solutions such as relocatable code movement, differential data exchange, user interface caching, alternate communication paths, and redundant server setups to ensure continuous system operation and security, including the use of interpreted languages like Lua or Python to execute code on different architectures without compilation, and providing physical security measures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system relies on continuous network connection to remote server, then centralized control and data synchronization are improved, but system robustness and availability deteriorate when network fails

Engineering Contradiction:
Improvesystem robustnessVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the control system into distributed components: local controllers at each site and a remote server. Each local controller can operate independently when network is unavailable, while the remote server provides centralized functions when connected. This segmentation allows the system to maintain robustness during network failures without requiring complete system redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-configuring local controllers with cached data, configuration files, and operational parameters stored locally. When the network is unavailable, these pre-stored resources enable the local controller to continue operating without immediate remote server intervention, thus maintaining system robustness during network disruptions.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If data is continuously synchronized between local system and remote server, then data consistency is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork bandwidth
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent extracts only the essential synchronization data for local operation and stores it locally in the local controller. Non-critical data and full configuration sets remain on the remote server. This extraction approach maintains data consistency for critical operations while significantly reducing the bandwidth required for continuous synchronization.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial synchronization by transmitting only changed or differential data between the local controller and remote server, rather than synchronizing complete data sets continuously. This partial action approach maintains adequate data consistency while minimizing network bandwidth consumption.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If complete system code is stored locally for offline operation, then system availability is improved, but local storage requirements and security risks increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidsecurity risks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts only the essential system code and configuration data required for basic local operation and stores it in the local controller. The complete system code and sensitive data remain on the secure remote server. This extraction enables offline operation for critical functions while minimizing security risks by reducing the attack surface from complete code replication.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies local quality by storing different types of data with different security requirements in different locations. Critical operational code is stored locally for availability, while sensitive configuration data and complete system images remain on the secure remote server. This differentiated approach balances availability needs with security requirements.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9985824B2Systems and methods for increasing robustness of a system with a remote server
Publication Date: 2018.05.29 RESIDEO USA LLC
  • US9985824B2 patent drawing
  • US9985824B2 patent drawing
  • US9985824B2 patent drawing

AI summary

Systems and methods for increasing robustness of a system with a remote server are provided. Some methods can include a first system remotely controlling a second system, detecting a failure in the first system or in a communication link between the first system and the second system, and temporarily removing control of the second system from the first system.