Emergency Call Handling Profiles for VoIP Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional emergency call handling systems face difficulties in routing and processing emergency calls effectively, particularly in complex scenarios involving multiple switches and varying vendor proprietary parameters, which can lead to configuration challenges and reduced flexibility in handling different client and server types.

Innovation Solution

The implementation of emergency call handling profiles (ECHPs) that include extensive rule sets and parameters, allowing for dynamic acquisition, sharing, and execution of call processing rules based on geographic location or device attributes, enabling advanced processing capabilities such as notifications, audio alarms, and location handling, and supporting E-911 and NG-911 standards through SIP and PIDF-LO mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional emergency call handling systems route calls through multiple switches with proprietary parameters, then call routing capability is improved, but system complexity and configuration difficulty increase

Engineering Contradiction:
Improvecall routing capabilityVSAvoidsystem configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal call handling profile system that can be executed across multiple different switch types and vendor platforms. The profile contains standardized instructions that enable any compliant switch to perform the same emergency call processing functions, eliminating the need for proprietary configurations on each switch while maintaining routing capability across diverse network infrastructure.

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

Solution Approach 2:

The patent introduces an intermediary call handling profile that acts as a mediator between the calling party and the PSAP. This profile can be executed by any switch in the call path and contains the processing logic that would otherwise require complex proprietary configurations on each switch, thereby simplifying the overall system while maintaining routing versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If additional processing rules are added to switches for complementing E-911 and NG-911 systems, then emergency call processing capability is improved, but configuration difficulty becomes impossible

Engineering Contradiction:
Improveemergency call processing capabilityVSAvoidconfiguration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements self-service through automated profile distribution and execution. The call handling profile is automatically provided to switches in the call path and executed without manual configuration. The system self-configures by retrieving the profile from a database or receiving it with the call setup, eliminating the need for complex manual configuration while enabling advanced processing capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies preliminary action by pre-defining call handling profiles in a database before calls are routed. These profiles contain all necessary processing rules for complementing E-911 and NG-911 systems, and are automatically retrieved and executed during call setup, eliminating the need for complex real-time configuration while enabling advanced processing capabilities.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If ECHPs are delivered by value within call messages, then processing flexibility is improved, but message size and transmission overhead increase

Engineering Contradiction:
Improveprocessing flexibilityVSAvoidmessage size
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts the call handling profile from the call message itself and places it in a separate database. The message only contains a reference or identifier to the profile, significantly reducing message size while maintaining processing flexibility. The actual profile data is retrieved separately from the database during call processing.

Inventive Principle:
Principle #2Taking out (Extraction)

4Quantity of substance

If ECHPs are delivered by reference to a database, then message efficiency is improved, but system reliability decreases

Engineering Contradiction:
Improvemessage sizeVSAvoidsystem reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements beforehand cushioning by pre-validating and caching call handling profiles in the database before they are needed. The system ensures profile availability and integrity through prior preparation, and includes fallback mechanisms to handle database access failures, thereby maintaining reliability while using reference-based delivery to reduce message size.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS8811572B2Systems and methods for exchanging call routing policies for voice over IP calls
Publication Date: 2014.08.19 INTRADO LIFE & SAFETY INC
  • US8811572B2 patent drawing
  • US8811572B2 patent drawing
  • US8811572B2 patent drawing

AI summary

An emergency call handling system can provide emergency call routing and processing that compliments or modifies the routing and processing provided by conventional enhanced 911 (E-911) and next generation 911 (NG-911) systems. Both the routing and processing can be based on rule sets detailed in emergency call handling profiles (ECHPs). Any entity (e.g., SIP servers, switches, terminals, etc.) within the system can process and route the emergency call by executing the rule sets within the ECHPs associated with the call. The ECHPs are delivered to the entities within the system by value or by reference. A SIP server, e.g., may execute all or a subset of the rule set, and may communicate with an application server to execute other subsets of the rule set.