Incident Area Network Sub-System Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Public safety agencies face disruptions in communication services during incident response due to handovers between network sub-systems, as portable communications devices may lose connection to localized and global application instances, leading to service interruptions.

Innovation Solution

A system and method for forming an incident area network that includes synchronization between sub-systems, using a network core, domain name servers, global and localized application instances, and network address translators to maintain session continuity by transmitting global network addresses and synchronizing application instances across sub-systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If network sub-systems are connected to form an incident area network, then communication coverage is expanded, but service continuity is disrupted during handovers

Engineering Contradiction:
Improvecommunication coverageVSAvoidservice continuity
Core Design Contradiction:
Area of stationary objectVSReliability

Solution Approach 1:

The system performs preliminary synchronization between network sub-systems before handovers occur. Domain name servers exchange global network addresses and localized application instances are synchronized in advance, so that when a device moves between sub-systems, the connection information is already prepared and service continuity is maintained without interruption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Domain name servers act as intermediaries between network sub-systems, exchanging connection information and global network addresses. This intermediary mechanism enables different sub-systems to share necessary data about application instances and network configurations, facilitating seamless handovers while maintaining service continuity across the expanded communication coverage area.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If localized application instances are deployed in each sub-system, then service accessibility is improved, but connection loss occurs during handovers

Engineering Contradiction:
Improveservice accessibilityVSAvoidconnection stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements both localized application instances (for sub-system-specific services) and global application instances (for services accessible across all sub-systems). Domain name servers manage both types, allowing devices to access appropriate services regardless of which sub-system they are currently connected to, while maintaining stable connections through synchronized address information during handovers.

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

Solution Approach 2:

Domain name servers continuously synchronize connection information between sub-systems, providing feedback about global network addresses and localized application instances. This feedback mechanism ensures that when devices handover between sub-systems, the necessary connection data is updated and available, preventing connection loss while maintaining access to both localized and global services.

Inventive Principle:
Principle #23Feedback

3Reliability

If global network addresses are transmitted between sub-systems, then application instance accessibility is maintained, but network complexity increases

Engineering Contradiction:
Improveapplication accessibilityVSAvoidnetwork configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Domain name servers automatically perform the synchronization of global network addresses and connection information between sub-systems without requiring manual configuration or complex network setup. The system self-manages the exchange and maintenance of address information, reducing the operational complexity of managing multi-sub-system networks while ensuring reliable application instance accessibility.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10009801B1Systems and methods for forming an incident area network
Publication Date: 2018.06.26 MOTOROLA SOLUTIONS INC
  • US10009801B1 patent drawing
  • US10009801B1 patent drawing
  • US10009801B1 patent drawing

AI summary

A system and method for forming an incident area network including a first sub-system and a second sub-system. The method includes detecting, with an electronic processor of the first sub-system, a network connection to the second sub-system. The method includes initiating a sub-system synchronization process. The process includes including transmitting, from a first domain name server of the first sub-system to a second domain name server of the second sub-system, a first global network address for a first global application instance of the first sub-system, and a first name corresponding to the first global network address. The process includes transmitting, from a first network address translator of the first sub-system to a second network address translator of the second sub-system, the first global network address. The process includes synchronizing a first localized application instance of the first sub-system, with a second localized application instance of the second sub-system.