Emergency Communication Prioritization via Dynamic Labeling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Communication networks face challenges in maintaining the quality and connectivity of voice communications during emergency events due to excessive bandwidth usage, which can lead to poor quality or failure of critical emergency communications.

Innovation Solution

The system determines emergency events by analyzing communication metadata and generates a communication policy to prioritize emergency communications over non-emergency ones by using label data, ensuring that emergency communications are transmitted with higher quality and priority without requiring continuous resource dedication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the network capacity for handling voice communications is increased to maintain quality during emergency events, then the quality of emergency communications is improved, but the network resource allocation becomes inefficient during non-emergency periods

Engineering Contradiction:
Improvequality of emergency communicationsVSAvoidnetwork resource allocation efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The network dynamically adjusts resource allocation based on detected emergency conditions. During emergencies, the system increases bandwidth and priority handling for emergency communications. During non-emergency periods, resources are reduced to normal allocation levels, optimizing efficiency. This dynamic adaptation resolves the contradiction between maintaining high reliability during emergencies and preserving resource efficiency during normal operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes key network parameters such as bandwidth allocation, packet prioritization, and quality of service thresholds based on emergency detection. When an emergency is detected, parameters are adjusted to favor emergency communications. When no emergency exists, parameters return to standard configurations, preventing wasteful resource consumption while ensuring quality when needed.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If bandwidth allocation is increased for emergency communications during emergencies, then the connectivity of emergency communications is improved, but the bandwidth available for non-emergency communications is reduced

Engineering Contradiction:
Improveconnectivity of emergency communicationsVSAvoidbandwidth available for non-emergency communications
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

During emergency events, the system extracts and isolates emergency communications from the general traffic flow, dedicating specific bandwidth resources exclusively to these critical communications. This extraction ensures that emergency communications receive sufficient bandwidth without permanently reducing the total network capacity, allowing non-emergency communications to resume normal bandwidth access when emergencies subside.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The network segments traffic into emergency and non-emergency categories, applying different bandwidth allocation policies to each segment. Emergency communications are segmented into a high-priority class with guaranteed bandwidth during emergencies, while non-emergency communications are segmented into a standard class that receives remaining bandwidth. This segmentation resolves the contradiction by ensuring emergency connectivity without permanently sacrificing non-emergency bandwidth availability.

Inventive Principle:
Principle #1Segmentation

3Reliability

If the network prioritizes emergency communications over non-emergency ones, then the quality of emergency communications is maintained, but the handling capacity for non-emergency communications is reduced

Engineering Contradiction:
Improvequality of emergency communicationsVSAvoidhandling capacity for non-emergency communications
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The network implements periodic monitoring of traffic patterns and emergency conditions, adjusting prioritization levels in response to detected events. During non-emergency periods, normal handling capacity is maintained for all communications. When emergencies are detected, prioritization is periodically adjusted to favor emergency communications. This periodic adjustment ensures emergency quality maintenance without permanently reducing non-emergency handling capacity.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system applies partial prioritization to emergency communications rather than completely deprioritizing all other traffic. Emergency communications receive enhanced handling with higher priority queues and quality guarantees, while non-emergency communications continue to be handled with standard capacity. This partial action approach maintains emergency quality while preserving sufficient non-emergency handling capacity for normal operations.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9843914B1System for transiting emergency communications
Publication Date: 2017.12.12 AMAZON TECH INC
  • US9843914B1 patent drawing
  • US9843914B1 patent drawing
  • US9843914B1 patent drawing

AI summary

Described are techniques for determining an emergency event and associating label data with emergency communications to ensure that the emergency communications are provided with a greater quality and priority than non-emergency communications. When a quantity of communications associated with a network exceeds a threshold value, policy data may be generated and provided to network devices. The policy data may be configured to cause the network devices to transit communications associated with label data with high quality and connectivity. Correspondence between communications from the network and stored values indicative of emergency communications may be used to determine emergency communications from other data. Label data may be associated with the determined emergency communications to cause network devices to transit the communications in the manner indicated by the policy data.