Tracking results of a v2 query in voice over internet (VoIP) emergency call systems

• US 20110149953A1
• Filed: 12/22/2010
• Published: 06/23/2011
• Est. Priority Date: 12/23/2009
• Status: Abandoned Application

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: Helgeson, William, Geldenbott, Gerhard
• Application Number:
  US12/926,997
• Publication Number:
  US 20110149953A1
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 3/5116 for emergency applications

Abstract

A simplified method of encoding information needed to set the NENA 08-001 v2 Result code based on two essential factors that are stored in a data store at runtime. An ESRResponse header is built with two fields created as simple enumerated types: LocationSrc and RoutedOnAlgo. For each emergency call there is one entry in this data store. The first field of the ESRResponse header comprises one of five possible unique values, as does the second field.

Claims

1. A method of building an ESRResponse header including location and routing information, comprises:

a first field containing only one unique value indicating a source of location information; and

a second field indicating only one unique value indicating a source of routing to a responder.

2. The method of building an ESRResponse header including location and routing information according to claim 1, wherein:

said response header forms a v2 result code header in conformance with NENA i2 standards for VoIP emergency calls.

3. The method of building an ESRResponse header including location and routing information according to claim 1, wherein:

said first field comprises at least five possible predefined values.

4. The method of building an ESRResponse header including location and routing information according to claim 3, wherein said at least five possible predefined values of said first field comprise:

a first possible unique value indicating that no location information was obtained;

a second possible unique value indicating that said location was obtained from call signaling;

a third possible unique value indicating that said location relates to information from a subscriber obtained from a location information server (LIS);

a fourth possible unique value indicating that said location relates to information from a location profile obtained from a location information server (LIS); and

a fifth possible unique value indicating that said location relates to information from a custom location source.

5. The method of building an ESRResponse header including location and routing information according to claim 1, wherein:

said second field comprises at least five possible predefined values.

6. The method of building an ESRResponse header including location and routing information according to claim 5, wherein said at least five possible predefined values of said second field comprise:

a first possible unique value indicating that said routing to said emergency responder is carrier default routing;

a second possible unique value indicating that said routing to said emergency responder was calculated using only address without use of GIS;

a third possible unique value indicating that said routing to said emergency responder was calculated using GIS from a given position;

a fourth possible unique value indicating that said routing to said emergency responder was calculated using GIS from a geocoded full address; and

a fifth possible unique value indicating that said routing to said emergency responder was calculated using GIS from only city/state/Zip code.

wherein a fixed set of possible unique values of said second field condense information to complete routing of a given emergency call.

7. The method of building an ESRResponse header including location and routing information according to claim 4, wherein possible predefined values of said second field comprise:

a first possible unique value indicating that said routing to said emergency responder is carrier default routing;

a second possible unique value indicating that said routing to said emergency responder was calculated using only address without use of GIS;

a third possible unique value indicating that said routing to said emergency responder was calculated using GIS from a given position;

a fourth possible unique value indicating that said routing to said emergency responder was calculated using GIS from a geocoded full address; and

a fifth possible unique value indicating that said routing to said emergency responder was calculated using GIS from only city/state/Zip code.

wherein a fixed set of possible unique values of said second field condense information to complete routing of a given emergency call.

8. The method of building an ESRResponse header including location and routing information according to claim 1, wherein possible predefined values of said first field comprise:

a first possible unique value indicating that no location information was obtained;

a second possible unique value indicating that said location was obtained from call signaling;

a third possible unique value indicating that said location relates to information from a subscriber obtained from a location information server (LIS);

a fourth possible unique value indicating that said location relates to information from a location profile obtained from a location information server (LIS); and

a fifth possible unique value indicating that said location relates to information from a custom location source.

9. The method of building an ESRResponse header including location and routing information according to claim 8, wherein possible predefined values of said second field comprise:

a first possible unique value indicating that said routing to said emergency responder is carrier default routing;

a second possible unique value indicating that said routing to said emergency responder was calculated using only address without use of GIS;

a third possible unique value indicating that said routing to said emergency responder was calculated using GIS from a given position;

a fourth possible unique value indicating that said routing to said emergency responder was calculated using GIS from a geocoded full address; and

a fifth possible unique value indicating that said routing to said emergency responder was calculated using GIS from only city/state/Zip code.

wherein a fixed set of possible unique values of said second field condense information to complete routing of a given emergency call.

10. The method of building an ESRResponse header including location and routing information according to claim 1, wherein possible predefined values of said second field comprise:

a first possible unique value indicating that said routing to said emergency responder is carrier default routing;

a second possible unique value indicating that said routing to said emergency responder was calculated using only address without use of GIS;

a third possible unique value indicating that said routing to said emergency responder was calculated using GIS from a given position;

a fourth possible unique value indicating that said routing to said emergency responder was calculated using GIS from a geocoded full address; and

a fifth possible unique value indicating that said routing to said emergency responder was calculated using GIS from only city/state/Zip code.

wherein a fixed set of possible unique values of said second field condense information to complete routing of a given emergency call.