Height-Floor Cross Referenced Database for Emergency Call Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current emergency services call routing systems, such as Next Generation 9-1-1, do not account for elevation or height in determining the appropriate Public Safety Answering Point (PSAP) for emergency responses, limiting the precision of first responder identification and call routing.

Innovation Solution

A Height-Floor Cross Referenced Database (H-FCRD) is integrated with the Emergency Call Routing Function (ECRF) to cross-reference elevation or height with specific buildings or floors, enabling more precise call routing and responder determination by using geodetic or civic location information that includes sub-addressing data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional two-dimensional call routing based on base civic address or latitude/longitude is used, then call routing simplicity is maintained, but location precision and responder identification accuracy deteriorate due to lack of elevation information

Engineering Contradiction:
Improvelocation precisionVSAvoidcall routing system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent transitions from two-dimensional call routing (latitude/longitude or base address) to three-dimensional routing by incorporating elevation data. The ECRF system now processes X/Y/Z coordinates instead of just X/Y, enabling precise vertical location identification. This dimensional expansion allows the system to distinguish between different floors and elevations, significantly improving location precision without fundamentally changing the routing architecture.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The system pre-provisions elevation data and building floor information in databases before call routing operations. The ECRF system has pre-configured knowledge of elevation-to-floor mappings, allowing it to immediately translate incoming elevation data into meaningful location information without requiring complex real-time calculations. This preliminary preparation enables the system to handle three-dimensional routing efficiently.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If elevation data collection and processing is implemented, then responder identification accuracy improves, but data processing complexity and infrastructure requirements worsen

Engineering Contradiction:
Improveresponder identification accuracyVSAvoiddata processing infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the H-FCRD database and ECRF processing logic) that mediates between raw elevation data from service providers and the call routing decision-making process. This intermediary translates elevation meters into building-specific floor information using pre-configured mappings, making the data usable without requiring complex analysis infrastructure at PSAPs or service provider systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system extracts and separates elevation data processing from the core call routing function. By dedicating specific databases (H-FCRD) and processing steps to handle elevation information independently, the system can process three-dimensional location data without overwhelming the primary routing infrastructure. This extraction allows elevation processing to be added incrementally without redesigning the entire system.

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If cross-floor-height reference databases are integrated, then call routing precision for multi-story buildings improves, but database complexity and maintenance requirements worsen

Engineering Contradiction:
Improvevertical location precisionVSAvoiddatabase structure complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments location data into distinct components: horizontal coordinates (X/Y), vertical coordinates (Z/elevation), and building-specific attributes (floor mappings). The H-FCRD database is structured to store these segments separately, with elevation-to-floor mappings organized by building identifier. This segmentation allows the system to process only the relevant vertical information needed for routing decisions without managing overly complex integrated datasets.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11388575B2Height-floor indexing for call routing and responder determination
Publication Date: 2022.07.12 911 DATAMASTER INC
  • US11388575B2 patent drawing
  • US11388575B2 patent drawing
  • US11388575B2 patent drawing

AI summary

A method to automatically alter the ECRF route determination for call delivery to a PSAP, and better identify the appropriate responders for incidents where significant elevation or height of the caller's location is involved. A pre-provisioned database for elevation and height consideration is provided either as part of or integrated with the ECRF based on the use of this additional sub-addressing data (building, height, etc.), and cross referenced to a pre-provisioned elevation or height associated with each specific building or floor. The routing of requests for emergency services through the use of either service provider delivered geodetic or civic location is provided. Emergency services routing and responder determination is based on both sub-addressing information in combination with a cross reference database of vertical height identifiers by accessing a pre-populated database of this cross-reference information.