Security Control Panel DNS Caching for IP Address Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security system control panels require reprogramming when the IP address of a central station receiver changes, leading to potential communication disruptions due to reliance on static IP addresses, which can be unreliable, especially during ISP changes or network re-routing.

Innovation Solution

Implementing a method that uses the Domain Name System (DNS) to initially look up the IP address of a central monitoring center, then caches this address for subsequent communications, treating it as static unless an acknowledgement failure occurs, thereby eliminating DNS as a point of failure and allowing continuous operation even if the IP address changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If control panels use static IP addresses to communicate with central stations, then communication stability is improved, but adaptability to IP address changes deteriorates

Engineering Contradiction:
Improvecommunication stabilityVSAvoidadaptability to IP address changes
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically switches between using cached static IP addresses for stable communication and querying DNS servers when communication failures occur. The control panel maintains a cached IP address for routine operations, ensuring communication stability, while implementing a failure detection mechanism that triggers DNS queries to obtain updated IP addresses, thus adapting to network changes without disrupting normal operations.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If control panels query DNS servers for IP address lookups, then adaptability to IP address changes is improved, but system reliability deteriorates due to DNS server availability

Engineering Contradiction:
Improveadaptability to IP address changesVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The control panel performs preliminary action by caching the IP address obtained from DNS lookup during installation or initial configuration. This cached IP address is then used for all subsequent communications without requiring repeated DNS queries. The system only queries the DNS server when communication failures are detected, thereby eliminating DNS servers as continuous points of failure while maintaining adaptability to IP address changes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The cached IP address acts as an intermediary between the control panel and the DNS server. Instead of directly depending on the DNS server for every communication, the system uses the cached IP address as a stable reference point. This intermediary mechanism isolates the system from DNS server unavailability while still allowing updates when necessary through failure-triggered DNS queries.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If control panels reprogram when IP address changes occur, then adaptability to IP address changes is improved, but loss of time and operational disruption increase

Engineering Contradiction:
Improveadaptability to IP address changesVSAvoidreprogramming time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The control panel performs self-service by automatically detecting communication failures and independently querying the DNS server to obtain updated IP addresses. When a communication failure is detected, the system automatically initiates a DNS lookup, retrieves the new IP address, and updates its communication parameters without requiring manual reprogramming by technicians. This self-service capability eliminates reprogramming time and operational disruptions while maintaining adaptability to network changes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2803183B1Using DNS for security system event reporting
Publication Date: 2017.07.05 ROBERT BOSCH GMBH
  • EP2803183B1 patent drawingFigure 1
  • EP2803183B1 patent drawingFigure 2

AI summary

A method of transmitting a message from a security system to a central station receiver includes receiving (202) at the security system an IP address associated with the central station receiver. An attempt is made to transmit (204) the message from the security system to the central station receiver by use of the IP address. In response to a failure to receive at the security system an acknowledgement from the central station receiver that the message was received, the security system is used (208) to query a Domain Name Server for a current IP address associated with the central station receiver. The query is dependent upon a domain name of the central station receiver. The current IP address associated with the central station receiver is received and used (212) to re-attempt the transmitting of the message from the security system to the central station receiver.