Routing Code-Based Incident Notification System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems require manual updating and storage of responder contact information for each object, which is inefficient and prone to errors.

Innovation Solution

A system that uses object-identification data to obtain a routing code, which is then used to retrieve a routing destination from a data store, allowing incident messages to be routed to designated responders without the need for individual object-based contact information storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual updating and storage of responder contact information is performed for each object, then accuracy of notification delivery is maintained, but system complexity and error-proneness increase

Engineering Contradiction:
Improvenotification delivery accuracyVSAvoidcontact information management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a routing code as an intermediary element that mediates between the object identification and the responder contact information. Instead of storing contact information directly associated with each object, the system uses routing codes as a intermediary layer that maps objects to responders through a centralized routing table, thereby reducing complexity while maintaining accuracy

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy of the routing information in the form of routing codes that are independent of the actual object storage. The routing codes serve as replicated identifiers that point to responder contact information in a centralized location, eliminating the need to maintain and update contact information at every object level while ensuring accurate notification delivery

Inventive Principle:
Principle #26Copying

2Ease of operation

If individual object-based contact information storage is used, then notification routing is straightforward, but manual updates and storage operations become time-consuming

Engineering Contradiction:
Improvenotification routing simplicityVSAvoidcontact information update time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges the routing functionality into a centralized routing table that consolidates all object-to-responder mappings in a single location. This unified routing mechanism allows the system to route notifications by looking up routing codes in the centralized table rather than performing individual object-based lookups, thereby simplifying operations and reducing update time

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The routing code serves multiple functions: it identifies the object, provides the key for routing table lookup, and enables notification delivery to the appropriate responder. This multi-functional design eliminates the need for separate contact information storage at each object level, making the system more efficient and reducing the time required for manual updates

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

Data Source

PatentUS8645970B1Method to route notifications to designated responder
Publication Date: 2014.02.04 T MOBILE INNOVATIONS LLC
  • US8645970B1 patent drawing
  • US8645970B1 patent drawing
  • US8645970B1 patent drawing

AI summary

A method for looking up routing information for a person or program assigned to respond to an incident messages is explained herein. The method includes recognizing a routing code that was appended to either the object name or description. The routing code is recognized by a program that looks up the responders contact information in a table that correlates routing codes with designated responder information.