Breathing Apparatus Network Nodes for Master Failover Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication techniques in emergency response incidents face challenges with maintaining connectivity and managing multiple pieces of equipment over large areas, leading to potential equipment failure and increased complexity.

Innovation Solution

A system comprising a decentralized network of network nodes and breathing apparatus (BA) that allows for adaptable and robust communication, with automatic reselection of a master node if the current one becomes inactive, ensuring continuous connectivity through a distributed network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single master node is used to manage all breathing apparatus in the network, then the system structure is simple and easy to manage, but the communication range is limited and the system reliability decreases when the master node fails

Engineering Contradiction:
Improvesystem reliabilityVSAvoidnetwork structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network is segmented into multiple independent master nodes, each managing a subset of breathing apparatus. This segmentation allows the system to maintain functionality even if one master node fails, as other master nodes continue to operate independently. The segmentation principle directly addresses the reliability issue by distributing the master node function across multiple entities rather than relying on a single point of failure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes the operational parameters of network nodes based on their state. When a master node becomes inactive, the system changes the status of support nodes to become new master nodes, altering the network topology parameters. This parameter change enables the system to adapt to failures and maintain reliability without requiring complete system reconfiguration.

Inventive Principle:
Principle #35Parameter changes

2Area of stationary object

If multiple support nodes are deployed to extend communication range, then the effective range for BA communication increases, but the device complexity and difficulty of managing the network increases

Engineering Contradiction:
Improvecommunication rangeVSAvoidnetwork management complexity
Core Design Contradiction:
Area of stationary objectVSDevice complexity

Solution Approach 1:

Support nodes automatically perform the function of master nodes when needed, without requiring manual intervention. When a master node fails, support nodes self-organize and take over master node responsibilities automatically. This self-service mechanism reduces the complexity of network management by eliminating the need for manual reconfiguration when nodes are added or fail.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Network nodes are designed with universal functionality, capable of operating as either master nodes or support nodes depending on system needs. This multi-functionality allows the same hardware to serve different roles, reducing the need for specialized equipment and simplifying network management. Nodes can dynamically transition between roles based on system conditions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If the system automatically selects a new master node when the current one fails, then the system reliability and continuity of communication is improved, but the complexity of the node selection mechanism increases

Engineering Contradiction:
Improvecommunication continuityVSAvoidnode selection mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-designating support nodes that can become master nodes if needed. Rather than selecting a new master node from scratch when a failure occurs, the system has already prepared potential candidates in advance. This preliminary action reduces the complexity of the selection mechanism during actual failure events, as the choice is already narrowed to pre-identified support nodes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where nodes continuously monitor the status of master nodes and automatically trigger reconfiguration when failures are detected. This feedback loop ensures communication continuity by automatically initiating the master node selection process when needed, reducing manual intervention while maintaining system reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4697298A1Communication handling
Publication Date: 2026.02.18 DRAGER SAFETY AG & CO KAAA
  • EP4697298A1 patent drawingFigure 1
  • EP4697298A1 patent drawingFigure 2
  • EP4697298A1 patent drawingFigure 3

AI summary

There is provided a system for handling communications in a network. The system comprises a plurality of network nodes (202, 204, 206), and a plurality of breathing apparatus (208, 210, 212) of the network. Each network node of the plurality of network nodes (202, 204, 206) is configured as an access point for the network. Each breathing apparatus of the plurality of breathing apparatus (208, 210, 212) is configured to establish a connection to a single corresponding network node of the plurality of network nodes (202, 204, 206). The plurality of network nodes (202, 204, 206) comprises a master node (202) and one or more support nodes (204, 206). The master node (202) is configured to establish a connection to each support node of the one or more support nodes (204, 206). Each support node of the one or more support nodes (204, 206) is configured to initiate transmission of first information indicative of one or more corresponding breathing apparatus towards the master node (202). The system is configured to, if a first master node enters an inactive state, select, based on second information indicative of the one or more support nodes (204, 206), a first support node to be configured as a second master node.