US20160330321A1 - House number normalization for master street address guide (msag) address matching - Google Patents

House number normalization for master street address guide (msag) address matching Download PDF

Info

Publication number
US20160330321A1
US20160330321A1 US15/217,095 US201615217095A US2016330321A1 US 20160330321 A1 US20160330321 A1 US 20160330321A1 US 201615217095 A US201615217095 A US 201615217095A US 2016330321 A1 US2016330321 A1 US 2016330321A1
Authority
US
United States
Prior art keywords
civic
address
msag
standard format
postal address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US15/217,095
Inventor
Gerhard Geldenbott
Gordon John Hines
Jeffrey Thomas Martin
Abe Backus
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
TeleCommunication Systems Inc
Original Assignee
TeleCommunication Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by TeleCommunication Systems Inc filed Critical TeleCommunication Systems Inc
Priority to US15/217,095 priority Critical patent/US20160330321A1/en
Publication of US20160330321A1 publication Critical patent/US20160330321A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/04—Special services or facilities for emergency applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/30—Determination of the location of a subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • This invention relates generally to long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to emergency call systems (e.g., E9-1-1) including wireless and Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call systems.
  • emergency call systems e.g., E9-1-1
  • IP Internet Protocol
  • VoIP Voice Over Internet Protocol
  • 9-1-1 is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel.
  • Enhanced 9-1-1 (E9-1-1) is defined by an emergency call being selectively routed to an appropriate PSAP, and enhanced information (callback number, name and location) is provided to the PSAP. This is accomplished through the use of the ANI.
  • the ANI may be the real phone number of the caller (in landline E911) or a pseudo-ANI called an ESRK (in cellular E911) or ESQK (in VoIP E911).
  • ESRK in cellular E911
  • ESQK in VoIP E911
  • This identifier allows the PSAP to retrieve location information such as the Master Street Address Guide (MSAG) valid address of the E9-1-1 caller's Civic/Postal Address.
  • the Master Street Address Guide (MSAG) represents a community provided local address master guide that permits the most accurate dispatch of emergency personnel to a “correct address.”
  • the “correct address” originates as the civic/postal address of an E9-1-1 emergency caller over a wireless and/or Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call system.
  • IP Internet Protocol
  • VoIP Voice Over Internet Protocol
  • the civic/postal address represents the caller's location at the time when the emergency call is placed. This civic/postal address needs to be associated with an appropriate corresponding MSAG address, which in most cases is required by the public safety answering point (PSAP).
  • PSAP public safety answering point
  • PSAP Public Service Answering Point
  • PSAP may be a local, fire or police department, an ambulance service or a regional office covering all services.
  • PSAP refers to either a public safety access point (PSAP), or to an Emergency Call Center (ECC), a VoIP term.
  • PSAP public safety access point
  • ECC Emergency Call Center
  • ALI landline automatic location identification
  • MSAG master street address guide
  • ESN emergency service number
  • GIS geographic information system
  • VoIP systems use proprietary technologies, usually based on GIS polygons, or based on pre-provisioning of the caller in the traditional landline ALI long before the need for an emergency call.
  • a “simple match” to find an MSAG-valid address refers to a simple lexicographic comparison of an input civic/postal address against the entries in an MSAG address store to find a positive match.
  • house numbers prove to be particularly hard to compare as in many cases house numbers contain digits and alpha-numeric characters in any random order. Given this fact, two house numbers that are not character-for-character identical may refer to the same house number as determined by a human observer.
  • the MSAG-valid address is required by most PSAPs, as it represents a community provided local address that allows accurate dispatch of emergency personnel to the correct address. But a challenge remains to provide a MSAG-valid address, particularly with respect to a real-time Voice Over Internet Protocol (VoIP) emergency call.
  • VoIP Voice Over Internet Protocol
  • a master street address guide (MSAG) address data store comprises a plurality of address entries, each entry comprising an address, a normalized low house number field, and a normalized high house number field.
  • a method of matching a civic/postal address associated with an emergency call with a master street address guide (MSAG) address table comprises normalizing the house number of an input civic/postal address associated with an emergency call to comprise an alphanumeric string having a fixed number of characters.
  • the normalized house number is provided for matching against normalized entries in the master street address guide (MSAG).
  • a MSAG address is selected from the MSAG address table in which the normalized house number falls lexicographically between the normalized low house number and the normalized high house number of the MSAG address.
  • a process of normalizing a house number portion of a civic/postal address and MSAG address range for use with an address database consists of converting each non-alphanumeric character in the house number portion to a space character. Consecutive space characters in the house number portion are replaced with a single space character. Leading and trailing spaces in the house number portion are removed. Each group of consecutive digits are located and padded with leading characters such that each digits group is of a fixed common length.
  • Normalization of the house number does not convert a house number to a valid house number, rather it converts house numbers to a standardized form for the purpose of lexicographical comparison.
  • FIG. 1 shows an exemplary MSAG data store including an MSAG address table including a plurality of entries, in accordance with the principles of the present invention.
  • FIG. 2 shows an exemplary process of normalizing house numbers from a civic/postal address and from MSAG addresses for use with respect to an MSAG Address data store, in accordance with the principles of the present invention.
  • FIG. 3 shows normalizing an input house number, then determined if the input house number is “normalized-between” a given entry's low house number and a high house number, in accordance with the principles of the present invention.
  • FIG. 4 shows sample house number normalizations, in accordance with the principles of the present invention.
  • FIG. 5 shows sample normalized house numbers inserted into respective entries of an exemplary MSAG address table in an MSAG Address data store, in accordance with the principles of the present invention.
  • the present invention provides a technique and apparatus to allow a determination of an MSAG-valid address by use of normalized house numbers included in address entries in an MSAG Address data store.
  • it provides a unique method to facilitate the simple match of an input civic/postal address against entries in a MSAG data store based on the use of a normalization of the house numbers.
  • the house number normalization allows for a simple lexicographic determination as to whether or not the input civic/postal house number falls with the range of house numbers in the MSAG data store.
  • the present invention provides a very high matching rate of a master street address guide (MSAG) address using unique house number normalization on both: (1) an input civic/postal address; and (2) the MSAG addresses stored in an MSAG address data store.
  • MSAG master street address guide
  • the inventive process and apparatus normalizes house number fields in an MSAG address data store in advance of matching, and then normalizes input house numbers from a civic/postal address associated with an emergency call.
  • the normalized numbers in the input civic/postal address associated with the emergency call are then lexicographically matched with normalized entries in an MSAG address data store to successfully perform simple MSAG matching on an input civic/postal address.
  • An otherwise conventional MSAG address data store contains address ranges.
  • the low and high MSAG house numbers are normalized and stored based on house number normalization rules established by the present invention.
  • the normalized house numbers stored in the MSAG address data store may be normalized before first being stored in the MSAG address data store; or may be converted and restored in a new format accommodating the normalized form of the house numbers.
  • an input civic/postal address house number associated with an emergency call is converted using the same house number normalization as that used on the entries already stored in the MSAG address data store, and then lexicographically matched against the address range in the MSAG address data store.
  • the conversion may be accomplished in a module associated with presenting a match inquiry to the MSAG address data store, or within the mobile device making the relevant emergency call, or anywhere there between.
  • the input civic/postal address has a high probability to successfully match against the MSAG address data store, in accordance with the principles of the present invention.
  • normalized house numbers are used on both the input civic/postal house number, as well as on the MSAG address low and high house numbers in the MSAG data store.
  • the normalized civic/postal input house number is then lexicographically compared against the normalized MSAG address low and high house numbers in the data store.
  • MSAG data store may contain more than just the MSAG address table suitable to support the relevant match technique used.
  • FIG. 1 shows an exemplary MSAG data store 100 including an MSAG address table 101 including a plurality of entries, in accordance with the principles of the present invention.
  • a suitable database referred to herein as an MSAG data store 100 , includes an MSAG Address table 101 .
  • the MSAG Address table 101 includes multiple entries, each of which includes an associated data field for each of an MSAGAddress_ID 102 , an MSAG Address 104 , an MSAG_LOW_HOUSE_NUM_NORM 106 , and an MSAG_HIGH_HOUSE_NUM_NORM 108 .
  • each entry in the MSAG Address table 101 is uniquely identified by the MSAGAdress_ID 102 data.
  • MSAG Address 104 field is shown in the disclosed embodiments as one field for reasons of simplicity, the MSAG Address 104 field in general preferably comprises several fields capable of documenting a street address.
  • each entry in the MSAG Address table 101 also comprises a NORMALIZED low house number MSAG_LOW_HOUSE_NUM_NORM 106 , and a NORMALIZED high house number MSAG_HIGH_HOUSE_NUM_NORM 108 .
  • FIG. 2 shows an exemplary process of normalizing house numbers extracted from a civic/postal address, and for use of normalizing MSAG Address data store house numbers, in accordance with the principles of the present invention.
  • FIG. 2 shows exemplary rules 400 to normalize a house number.
  • step 420 a house number is input.
  • step 401 the input house number is converted to a common case, e.g., all to upper case.
  • normalization might instead normalize all house numbers to lower case within the scope of the present invention.
  • each non-alphanumeric character (e.g. punctuation) is converted to a space character.
  • step 403 consecutive space characters are replaced with a single space character.
  • step 404 leading spaces and trailing spaces are removed.
  • step 405 every group of consecutive digits (not whitespace, not alphanumeric) are located.
  • each located group of digits is padded with leading zeros such that each digits group is exactly a common length, e.g., a preferred 10 digits in the disclosed embodiments.
  • FIG. 3 shows normalizing an input civic/postal house number, then determined if the input house number is “normalized-between” a given entry's low house number and a high house number, in accordance with the principles of the present invention.
  • step 501 an input civic/postal address house number is normalized using the rules shown in FIG. 2 .
  • the input civic/postal address including the now-normalized house number is compared to entries in the relevant MSAG Address data store to search for MSAG addresses where the input house number is “normalized-between” those MSAG address records. If the normalized input house number is lexicographically between the normalized low and normalized high house numbers of an MSAG address record, then the input house number is referred to as “normalized-between” the low and high house numbers of that MSAG record. Even though the original non-normalized input civic/postal house number might not be lexicographically between the original non-normalized high and low house number on that MSAG record, this ‘normalized-between’ step finds legitimate MSAG records that match the input civic/postal house number.
  • FIG. 4 and FIG. 5 illustrate the normalization process and determining whether or not a house number is “normalized-between” a low and high house number.
  • FIG. 4 showing sample house number normalizations 200 will be described in accordance with the principles of the present invention.
  • the input low and high house numbers are normalized preferably before being stored in the MSAG Address table.
  • the first example 202 in FIG. 4 shows how house numbers consisting only of digits are normalized using the rules enumerated above.
  • the civic/postal low and high (i.e., range) house numbers “1100” and “2200” are normalized into “0000001100” and “0000002200”, respectively.
  • the second example 204 shows house numbers starting with an alpha-numeric character (e.g., “N”).
  • the civic/postal low and high house numbers “N0340” and “N0900” are normalized into “N0000000340” and “N0000000900”, respectively.
  • the third example 206 depicts an example of normalization of house numbers with a trailing alpha-numeric character.
  • original civic/postal low and high house numbers “10G” and “40G” are normalized into “0000000010G” and “0000000040G”, respectively.
  • FIG. 5 shows sample normalized house numbers inserted into respective entries of an exemplary MSAG address table 300 in an MSAG Address data store, in accordance with the principles of the present invention.
  • the MSAG address table 300 includes sample civic/postal addresses and house number ranges (i.e., as defined by both low and high house numbers), as shown in the examples 202 , 204 and 206 in FIG. 4 .
  • the “MSAG Address” parameter shown in FIG. 5 still contains the original UN-normalized house number, whereas the parameters or fields described as “MSAG_LOW_HOUSE_NUMBER_NORM” and “MSAG_HIGH_HOUSE_NUMBER_NORM” contain the corresponding normalized values.
  • the normalized house numbers for the “MSAG Address” field in the first civic/postal address entry 302 is “1100-2200 2ih AVE NE Seattle Wash. 98115”, with the address range defined by the normalized values of “0000001100” and “0000002200”, respectively.
  • the “MSAG Address” field in the second civic/postal address entry 304 contains the original civic/postal address: “N0340-N0900 NE 55th St Seattle Wash. 98115”, from which the normalized address is determined and stored as a low and high house number, e.g., “N0000000340” and “N0000000900”.
  • the “MSAG Address” field contains the original the original civic/postal address: “10G-40G NE Park Rd Seattle Wash. 98115”, from which the normalized address is determined and stored as a low and high house number, e.g., “000000001OG” and “0000000040G”.
  • the present invention guarantees that a given civic/postal address with a non-trivial house number can be simply matched against an MSAG address in a MSAG Address data store.
  • the present invention has particular applicability with location based server vendors.

Abstract

A technique and apparatus to allow a determination of an MSAG-valid address by use of normalized house numbers included in address entries in an MSAG Address data store, to facilitate the simple match of an input civic/postal address against entries in a MSAG data store based on the use of a normalization of the house numbers. The house number normalization allows for an easy lexicographical determination as to whether or not the input civic/postal house number falls with the range of house numbers in the MSAG data store. The inventive process and apparatus pre-stores normalized house number fields in an MSAG address data store, and then normalizes house numbers in a civic/postal address associated with an emergency call. The normalized numbers in the input civic/postal address associated with the emergency call are then lexicographically matched with normalized entries in an MSAG address data store.

Description

  • This application is a continuation of U.S. patent application Ser. 12/232,484, filed on Sep. 18, 2008, which claims priority from U.S. Provisional Application No. 60/960,459, entitled “MSAG Simple Matching a Civic/Postal Address Using Unique Normalized House Number Fields”, to Geldenbott, Hines and Martin, filed Oct. 1, 2007; and also from U.S. Provisional Application No. 60/960,148, entitled “Optimal Selection of MSAG Address for Valid Civic/Postal Address”, to Geldenbott, filed Sep. 18, 2007, the entirety of both of which are expressly incorporated herein by reference.
    • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • This invention relates generally to long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to emergency call systems (e.g., E9-1-1) including wireless and Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call systems.
  • 2. Background of Related Art
  • 9-1-1 is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel. Enhanced 9-1-1 (E9-1-1) is defined by an emergency call being selectively routed to an appropriate PSAP, and enhanced information (callback number, name and location) is provided to the PSAP. This is accomplished through the use of the ANI. The ANI may be the real phone number of the caller (in landline E911) or a pseudo-ANI called an ESRK (in cellular E911) or ESQK (in VoIP E911). Regardless of the network type, a 9-1-1 service becomes E-9-1-1 when automatic number identification and automatic location information related to the call is provided to the 9-1-1 operator at the PSAP.
  • This identifier allows the PSAP to retrieve location information such as the Master Street Address Guide (MSAG) valid address of the E9-1-1 caller's Civic/Postal Address. The Master Street Address Guide (MSAG) represents a community provided local address master guide that permits the most accurate dispatch of emergency personnel to a “correct address.” The “correct address” originates as the civic/postal address of an E9-1-1 emergency caller over a wireless and/or Internet Protocol (IP) based Voice Over Internet Protocol (VoIP) emergency call system. The civic/postal address represents the caller's location at the time when the emergency call is placed. This civic/postal address needs to be associated with an appropriate corresponding MSAG address, which in most cases is required by the public safety answering point (PSAP).
  • A Public Service Answering Point (PSAP) is a dispatch office that receives 9-1-1 calls from the public. A PSAP may be a local, fire or police department, an ambulance service or a regional office covering all services. As used herein, the term “PSAP” refers to either a public safety access point (PSAP), or to an Emergency Call Center (ECC), a VoIP term.
  • Distributed emergency call systems in telecommunications are in general very complex computing systems. Emergency calls that originate from a VoIP network use well proven routing paradigms already used for cellular 911 calls, or for traditional landline 911 calls. These paradigms usually work well, because VoIP customers can usually be grouped into two categories: a mobile VoIP caller that resembles a cellular user, and a stationary VoIP user resembling landline usage.
  • Traditional landline systems use pre-provisioned, generally static subscriber addresses, where the landline automatic location identification (ALI) provisioning process insures a match to a master street address guide (MSAG) record, which contains an emergency service number (ESN) used to route emergency calls to a PSAP.
  • But determination of the location of a mobile device proves much, much more challenging. To determine location of a mobile device, some conventional cellular systems use separate triangulation technologies (or any of a number of other techniques) to find a latitude & longitude of an emergency caller. These systems then use a geographic information system (GIS) system to query for a pre-defined region (e.g., a PSAP polygon) that contains this location.
  • Of course, errors may occur in conventional systems when determining the location of a mobile user. But even though it's very possible that these queried PSAP polygons can lead to a different (i.e., wrong) neighboring PSAP than an equivalent address provisioned in a landline ALI, this discrepancy is conventionally accepted by PSAPs because the location itself is likely to be imprecise due to measurement errors—sometimes the location is off by hundreds of feet.
  • Conventional VoIP systems use proprietary technologies, usually based on GIS polygons, or based on pre-provisioning of the caller in the traditional landline ALI long before the need for an emergency call.
  • Thus, traditional landline paradigms provide the most accurate location for its static users, but require the caller's address to be pre-provisioned into a landline automatic location identifier (ALI). This pre-provisioning (often referred to as service order interface (SOI) loading) usually takes a few days between the caller notifying their service provider of their address change, and this change being reflected in the landline ALI. But during this window a 911 call might be made, and if so it would be routed using the “old” data still in the landline ALI. Even the fastest possible conventional landline ALI provisioning takes at least several hours.
  • Existing solutions include the NENA VoIP architecture for enhanced 9-1-1 services standard NENA 08-001. However, such conventional technologies are too complicated and not always practical. Moreover, conventional systems are disadvantageous because they are unable to handle the embedded geographic location to precisely route the caller to the correct PSAP using the “just-in-time” paradigm.
  • A “simple match” to find an MSAG-valid address refers to a simple lexicographic comparison of an input civic/postal address against the entries in an MSAG address store to find a positive match. The present inventors have appreciated that house numbers prove to be particularly hard to compare as in many cases house numbers contain digits and alpha-numeric characters in any random order. Given this fact, two house numbers that are not character-for-character identical may refer to the same house number as determined by a human observer.
  • Compounding this issue is the fact that otherwise conventional MSAG data stored in an otherwise conventional MSAG address data store is always given as range data including a low and high house number, e.g., “100-2000 Elm Street.” So with this, a simple match must successfully determine if a given input civic/postal house number falls within a stored MSAG address house number range.
  • The MSAG-valid address is required by most PSAPs, as it represents a community provided local address that allows accurate dispatch of emergency personnel to the correct address. But a challenge remains to provide a MSAG-valid address, particularly with respect to a real-time Voice Over Internet Protocol (VoIP) emergency call.
    • SUMMARY OF THE INVENTION
  • In accordance with the principles of the present invention, a master street address guide (MSAG) address data store comprises a plurality of address entries, each entry comprising an address, a normalized low house number field, and a normalized high house number field.
  • In accordance with another aspect of the invention, a method of matching a civic/postal address associated with an emergency call with a master street address guide (MSAG) address table comprises normalizing the house number of an input civic/postal address associated with an emergency call to comprise an alphanumeric string having a fixed number of characters. The normalized house number is provided for matching against normalized entries in the master street address guide (MSAG). A MSAG address is selected from the MSAG address table in which the normalized house number falls lexicographically between the normalized low house number and the normalized high house number of the MSAG address.
  • In yet other aspects of the invention, a process of normalizing a house number portion of a civic/postal address and MSAG address range for use with an address database. Normalizing consists of converting each non-alphanumeric character in the house number portion to a space character. Consecutive space characters in the house number portion are replaced with a single space character. Leading and trailing spaces in the house number portion are removed. Each group of consecutive digits are located and padded with leading characters such that each digits group is of a fixed common length.
  • Normalization of the house number does not convert a house number to a valid house number, rather it converts house numbers to a standardized form for the purpose of lexicographical comparison.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:
  • FIG. 1 shows an exemplary MSAG data store including an MSAG address table including a plurality of entries, in accordance with the principles of the present invention.
  • FIG. 2 shows an exemplary process of normalizing house numbers from a civic/postal address and from MSAG addresses for use with respect to an MSAG Address data store, in accordance with the principles of the present invention.
  • FIG. 3 shows normalizing an input house number, then determined if the input house number is “normalized-between” a given entry's low house number and a high house number, in accordance with the principles of the present invention.
  • FIG. 4 shows sample house number normalizations, in accordance with the principles of the present invention.
  • FIG. 5 shows sample normalized house numbers inserted into respective entries of an exemplary MSAG address table in an MSAG Address data store, in accordance with the principles of the present invention.
    •  DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
  • The present invention provides a technique and apparatus to allow a determination of an MSAG-valid address by use of normalized house numbers included in address entries in an MSAG Address data store. In particular, it provides a unique method to facilitate the simple match of an input civic/postal address against entries in a MSAG data store based on the use of a normalization of the house numbers. The house number normalization allows for a simple lexicographic determination as to whether or not the input civic/postal house number falls with the range of house numbers in the MSAG data store.
  • The present invention provides a very high matching rate of a master street address guide (MSAG) address using unique house number normalization on both: (1) an input civic/postal address; and (2) the MSAG addresses stored in an MSAG address data store. The inventive process and apparatus normalizes house number fields in an MSAG address data store in advance of matching, and then normalizes input house numbers from a civic/postal address associated with an emergency call. The normalized numbers in the input civic/postal address associated with the emergency call are then lexicographically matched with normalized entries in an MSAG address data store to successfully perform simple MSAG matching on an input civic/postal address.
  • An otherwise conventional MSAG address data store contains address ranges. According to the invention, the low and high MSAG house numbers are normalized and stored based on house number normalization rules established by the present invention. The normalized house numbers stored in the MSAG address data store may be normalized before first being stored in the MSAG address data store; or may be converted and restored in a new format accommodating the normalized form of the house numbers.
  • According to the invention, an input civic/postal address house number associated with an emergency call is converted using the same house number normalization as that used on the entries already stored in the MSAG address data store, and then lexicographically matched against the address range in the MSAG address data store. The conversion may be accomplished in a module associated with presenting a match inquiry to the MSAG address data store, or within the mobile device making the relevant emergency call, or anywhere there between. In this way, because of the normalization of the input house number, the input civic/postal address has a high probability to successfully match against the MSAG address data store, in accordance with the principles of the present invention.
  • With this invention, normalized house numbers are used on both the input civic/postal house number, as well as on the MSAG address low and high house numbers in the MSAG data store. The normalized civic/postal input house number is then lexicographically compared against the normalized MSAG address low and high house numbers in the data store.
  • While the disclosed embodiments utilize an MSAG address matching technique referred to as a Simple Match for which an MSAG Address table suffices, in practice the MSAG data store may contain more than just the MSAG address table suitable to support the relevant match technique used.
  • FIG. 1 shows an exemplary MSAG data store 100 including an MSAG address table 101 including a plurality of entries, in accordance with the principles of the present invention.
  • In particular, as shown in FIG. 1, a suitable database, referred to herein as an MSAG data store 100, includes an MSAG Address table 101. The MSAG Address table 101 includes multiple entries, each of which includes an associated data field for each of an MSAGAddress_ID 102, an MSAG Address 104, an MSAG_LOW_HOUSE_NUM_NORM 106, and an MSAG_HIGH_HOUSE_NUM_NORM 108.
  • Thus, each entry in the MSAG Address table 101 is uniquely identified by the MSAGAdress_ID 102 data.
  • Though the MSAG Address 104 field is shown in the disclosed embodiments as one field for reasons of simplicity, the MSAG Address 104 field in general preferably comprises several fields capable of documenting a street address.
  • According to the invention, each entry in the MSAG Address table 101 also comprises a NORMALIZED low house number MSAG_LOW_HOUSE_NUM_NORM 106, and a NORMALIZED high house number MSAG_HIGH_HOUSE_NUM_NORM 108.
  • FIG. 2 shows an exemplary process of normalizing house numbers extracted from a civic/postal address, and for use of normalizing MSAG Address data store house numbers, in accordance with the principles of the present invention. In particular, FIG. 2 shows exemplary rules 400 to normalize a house number.
  • In step 420, a house number is input.
  • In step 401, the input house number is converted to a common case, e.g., all to upper case. Of course, normalization might instead normalize all house numbers to lower case within the scope of the present invention.
  • In step 402, each non-alphanumeric character (e.g. punctuation) is converted to a space character.
  • In step 403, consecutive space characters are replaced with a single space character.
  • In step 404, leading spaces and trailing spaces are removed.
  • In step 405, every group of consecutive digits (not whitespace, not alphanumeric) are located.
  • In step 406, each located group of digits is padded with leading zeros such that each digits group is exactly a common length, e.g., a preferred 10 digits in the disclosed embodiments.
  • FIG. 3 shows normalizing an input civic/postal house number, then determined if the input house number is “normalized-between” a given entry's low house number and a high house number, in accordance with the principles of the present invention.
  • In particular, as shown in FIG. 3, in step 501 an input civic/postal address house number is normalized using the rules shown in FIG. 2.
  • In step 502, the input civic/postal address including the now-normalized house number is compared to entries in the relevant MSAG Address data store to search for MSAG addresses where the input house number is “normalized-between” those MSAG address records. If the normalized input house number is lexicographically between the normalized low and normalized high house numbers of an MSAG address record, then the input house number is referred to as “normalized-between” the low and high house numbers of that MSAG record. Even though the original non-normalized input civic/postal house number might not be lexicographically between the original non-normalized high and low house number on that MSAG record, this ‘normalized-between’ step finds legitimate MSAG records that match the input civic/postal house number.
  • FIG. 4 and FIG. 5 illustrate the normalization process and determining whether or not a house number is “normalized-between” a low and high house number. First, FIG. 4 showing sample house number normalizations 200 will be described in accordance with the principles of the present invention.
  • In particular, as shown in FIG. 4, the input low and high house numbers are normalized preferably before being stored in the MSAG Address table. The first example 202 in FIG. 4 shows how house numbers consisting only of digits are normalized using the rules enumerated above. In this example, the civic/postal low and high (i.e., range) house numbers “1100” and “2200” are normalized into “0000001100” and “0000002200”, respectively.
  • Similarly, the second example 204 shows house numbers starting with an alpha-numeric character (e.g., “N”). In the second example 204, the civic/postal low and high house numbers “N0340” and “N0900” are normalized into “N0000000340” and “N0000000900”, respectively.
  • The third example 206 depicts an example of normalization of house numbers with a trailing alpha-numeric character. In this example, original civic/postal low and high house numbers “10G” and “40G” are normalized into “0000000010G” and “0000000040G”, respectively.
  • More complex examples would work in the same fashion following the enumerated rules above, in accordance with the principles of the present invention.
  • FIG. 5 shows sample normalized house numbers inserted into respective entries of an exemplary MSAG address table 300 in an MSAG Address data store, in accordance with the principles of the present invention.
  • In particular, as shown in FIG. 5, the MSAG address table 300 includes sample civic/postal addresses and house number ranges (i.e., as defined by both low and high house numbers), as shown in the examples 202, 204 and 206 in FIG. 4.
  • It is important to point out that the “MSAG Address” parameter shown in FIG. 5 still contains the original UN-normalized house number, whereas the parameters or fields described as “MSAG_LOW_HOUSE_NUMBER_NORM” and “MSAG_HIGH_HOUSE_NUMBER_NORM” contain the corresponding normalized values. With that, the normalized house numbers for the “MSAG Address” field in the first civic/postal address entry 302 is “1100-2200 2ih AVE NE Seattle Wash. 98115”, with the address range defined by the normalized values of “0000001100” and “0000002200”, respectively.
  • Similarly, the “MSAG Address” field in the second civic/postal address entry 304 contains the original civic/postal address: “N0340-N0900 NE 55th St Seattle Wash. 98115”, from which the normalized address is determined and stored as a low and high house number, e.g., “N0000000340” and “N0000000900”.
  • Finally, in the third and last example civic/postal address entry 306, the “MSAG Address” field contains the original the original civic/postal address: “10G-40G NE Park Rd Seattle Wash. 98115”, from which the normalized address is determined and stored as a low and high house number, e.g., “000000001OG” and “0000000040G”.
  • Therefore, taking the very last example, for the sample civic/postal input address of “0035G NE Park Rd Seattle Wash. 98115” a simple match would be found with civic/postal address 306, in accordance with the principles of the present invention, since the normalized form of “0035G” is “0000000035G”, which lexicographically falls between the Normalized range of “000000001OG” and “0000000040G” of that civic/postal address entry 306.
  • Accordingly, using modules put in place to normalize not only the house number range in all entries put into an MSAG Address table, but also a suitable normalization module to perform the same normalization on an input civic/postal address to be matched to the entries in the MSAG Address table, the present invention guarantees that a given civic/postal address with a non-trivial house number can be simply matched against an MSAG address in a MSAG Address data store.
  • The present invention has particular applicability with location based server vendors.
  • While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims (1)

What is claimed is:
1. A method of directing an emergency call to an emergency terminal responsible for a civic/postal address received with the emergency call, comprising:
obtaining a plurality of USPS standard format civic/postal address ranges for build into a physical MSAG database;
converting an upper limit and a lower limit to each of said plurality of USPS standard format civic/postal address ranges to a non-USPS standard format;
storing said non-USPS standard format civic/postal address ranges into said physical MSAG database;
receiving an emergency call from a mobile device together with an associated USPS standard format civic/postal address;
converting said associated USPS standard format civic/postal address into said non-UPSP standard format, wherein said non-UPSP standard format comprises:
converting each non-alphanumeric character in a street number portion of said USPS standard format civic/postal address to instead comprise a space character,
replacing consecutive space characters in said street number portion of said USPS standard format civic/postal address with a single space character,
removing a leading space and a trailing space in said street number portion of said USPS standard format civic/postal address, and
padding each group of consecutive digits in said USPS standard format civic/postal address with at least one leading character such that a resultant street number portion of said non-USPS standard format civic/postal address is of a fixed common length;
lexicographically matching said converted, non-USPS standard format civic/postal address to a non-USPS standard format address range entry pre-stored in said physical MSAG database; and
directing said emergency call from said mobile device to a proper physical public safety answering point (PSAP) terminal responsible for said USPS standard format civic/postal address based on said lexicographically matched, converted, non-USPS standard format civic/postal address.
US15/217,095 2007-09-18 2016-07-22 House number normalization for master street address guide (msag) address matching Abandoned US20160330321A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/217,095 US20160330321A1 (en) 2007-09-18 2016-07-22 House number normalization for master street address guide (msag) address matching

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US96014807P 2007-09-18 2007-09-18
US96045907P 2007-10-01 2007-10-01
US12/232,484 US9413889B2 (en) 2007-09-18 2008-09-18 House number normalization for master street address guide (MSAG) address matching
US15/217,095 US20160330321A1 (en) 2007-09-18 2016-07-22 House number normalization for master street address guide (msag) address matching

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/232,484 Continuation US9413889B2 (en) 2007-09-18 2008-09-18 House number normalization for master street address guide (MSAG) address matching

Publications (1)

Publication Number Publication Date
US20160330321A1 true US20160330321A1 (en) 2016-11-10

Family

ID=40455678

Family Applications (3)

Application Number Title Priority Date Filing Date
US12/232,507 Abandoned US20090077077A1 (en) 2007-09-18 2008-09-18 Optimal selection of MSAG address for valid civic/postal address
US12/232,484 Active 2030-05-29 US9413889B2 (en) 2007-09-18 2008-09-18 House number normalization for master street address guide (MSAG) address matching
US15/217,095 Abandoned US20160330321A1 (en) 2007-09-18 2016-07-22 House number normalization for master street address guide (msag) address matching

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US12/232,507 Abandoned US20090077077A1 (en) 2007-09-18 2008-09-18 Optimal selection of MSAG address for valid civic/postal address
US12/232,484 Active 2030-05-29 US9413889B2 (en) 2007-09-18 2008-09-18 House number normalization for master street address guide (MSAG) address matching

Country Status (1)

Country Link
US (3) US20090077077A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090094270A1 (en) * 2007-10-08 2009-04-09 Alirez Baldomero J Method of building a validation database
US8208909B2 (en) * 2008-06-02 2012-06-26 West Corporation System, apparatus and method for availing a mobile call of address information
US8271525B2 (en) * 2009-10-09 2012-09-18 Verizon Patent And Licensing Inc. Apparatuses, methods and systems for a smart address parser
US8606798B2 (en) * 2011-03-17 2013-12-10 Mastercard International Incorporated Systems and methods for creating standardized street addresses from raw address data
US8929855B2 (en) * 2011-12-02 2015-01-06 Maple Acquisition Llc Enabling location determination of user device originating emergency service call
US10684753B2 (en) 2012-03-28 2020-06-16 The Travelers Indemnity Company Systems and methods for geospatial value subject analysis and management
US9953369B2 (en) 2012-03-28 2018-04-24 The Travelers Indemnity Company Systems and methods for certified location data collection, management, and utilization
US11188853B2 (en) 2019-09-30 2021-11-30 The Travelers Indemnity Company Systems and methods for artificial intelligence (AI) damage triage and dynamic resource allocation, routing, and scheduling

Family Cites Families (216)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US1103073A (en) 1912-07-18 1914-07-14 American Telephone & Telegraph Emergency signaling system for telephone toll-collecting apparatus.
US4445118A (en) * 1981-05-22 1984-04-24 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Navigation system and method
US4651156A (en) * 1982-02-08 1987-03-17 Mcgraw-Edison Co. Integrated radio location and communication system
US4494119A (en) * 1983-08-04 1985-01-15 122923 Canada Limited Distress radiolocation method and system
DE3639753A1 (en) 1986-11-21 1988-06-01 Inst Rundfunktechnik Gmbh METHOD FOR TRANSMITTING DIGITALIZED SOUND SIGNALS
US4891638A (en) * 1987-10-30 1990-01-02 Motorola, Inc. Nationwide display pager with location readout
US4868570A (en) * 1988-01-15 1989-09-19 Arthur D. Little, Inc. Method and system for storing and retrieving compressed data
US4891650A (en) * 1988-05-16 1990-01-02 Trackmobile Inc. Vehicle location system
US5055851A (en) 1988-05-16 1991-10-08 Trackmobile, Inc. Vehicle location system
US5014206A (en) * 1988-08-22 1991-05-07 Facilitech International Incorporated Tracking system
US4952928A (en) 1988-08-29 1990-08-28 B. I. Incorporated Adaptable electronic monitoring and identification system
US5043736B1 (en) 1990-07-27 1994-09-06 Cae Link Corp Cellular position location system
US5068656A (en) 1990-12-21 1991-11-26 Rockwell International Corporation System and method for monitoring and reporting out-of-route mileage for long haul trucks
US6253074B1 (en) * 1996-01-10 2001-06-26 Telefonaktiebolaget L/M Ericsson (Publ) Cellular telecommunications systems having selectively associatable usage parameters
US6134316A (en) 1996-10-18 2000-10-17 Telefonaktiebolaget Lm Ericsson Telecommunications network with relocateability of subscriber number
US6240294B1 (en) 1997-05-30 2001-05-29 Itt Manufacturing Enterprises, Inc. Mobile radio device having adaptive position transmitting capabilities
US6108533A (en) 1997-08-22 2000-08-22 Telefonaktiebolaget Lm Ericsson (Publ) Geographical database for radio system
US6032051A (en) * 1997-12-01 2000-02-29 Telefonaktiebolaget L/M Ericsson Wireless mobile comunication devices for group use
US6526026B1 (en) * 1997-12-10 2003-02-25 Intel Corporation Digit transmission over wireless communication link
FI106354B (en) * 1998-02-18 2001-01-15 Nokia Networks Oy A method for processing mobile station information
US6278701B1 (en) 1998-07-10 2001-08-21 Verizon Laboratories Inc. Capacity enhancement for multi-code CDMA with integrated services through quality of services and admission control
US6067045A (en) * 1998-09-01 2000-05-23 Hughes Electronics Corporation Communication network initialization apparatus and method for fast GPS-based positioning
US6360102B1 (en) * 1998-09-10 2002-03-19 Ericsson Inc. System and method for defining a subscriber location privacy profile
US20070121601A1 (en) * 1998-09-24 2007-05-31 Genesys Telecommunications Laboratories, Inc Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure
US6321092B1 (en) 1998-11-03 2001-11-20 Signal Soft Corporation Multiple input data management for wireless location-based applications
US20040198386A1 (en) 2002-01-16 2004-10-07 Dupray Dennis J. Applications for a wireless location gateway
US6397208B1 (en) * 1999-01-19 2002-05-28 Microsoft Corporation System and method for locating real estate in the context of points-of-interest
SE9900710L (en) 1999-02-25 2000-08-26 Ericsson Telefon Ab L M Method and device relating to communication networks for mobile phones
US6564261B1 (en) * 1999-05-10 2003-05-13 Telefonaktiebolaget Lm Ericsson (Publ) Distributed system to intelligently establish sessions between anonymous users over various networks
US6621810B1 (en) 1999-05-27 2003-09-16 Cisco Technology, Inc. Mobile IP intra-agent mobility
US20050026589A1 (en) * 1999-07-29 2005-02-03 Bryan Holland Remote locator system using A E911-enabled wireless system
US6529500B1 (en) * 1999-08-26 2003-03-04 Verizon Laboratories Inc. Unified messaging notification
US6795444B1 (en) 1999-10-26 2004-09-21 Telefonaktiebolaget L M Ericsson (Publ) System and method for providing wireless telephony over a packet-switched network
DE69941460D1 (en) 1999-11-23 2009-11-05 Nokia Corp PROCEDURE WHICH ALLOWS THE USER TO BE NOTIFIED ABOUT HIS / YOUR LOCALIZATION REQUIREMENTS
US7603411B1 (en) 1999-12-14 2009-10-13 Nortel Networks Limited Presence management system
US6940826B1 (en) 1999-12-30 2005-09-06 Nortel Networks Limited Apparatus and method for packet-based media communications
US6687360B2 (en) * 1999-12-30 2004-02-03 At&T Corp. Personal IP follow-me service
AU2629601A (en) 2000-01-07 2001-07-24 Informio, Inc. Methods and apparatus for an audio web retrieval telephone system
US6662014B1 (en) * 2000-02-04 2003-12-09 Sbc Properties, L.P. Location privacy manager for a wireless communication device and method therefor
US6876734B1 (en) * 2000-02-29 2005-04-05 Emeeting.Net, Inc. Internet-enabled conferencing system and method accommodating PSTN and IP traffic
US7623447B1 (en) 2000-04-10 2009-11-24 Nokia Corporation Telephony services in mobile IP networks
US7110773B1 (en) 2000-04-11 2006-09-19 Telecommunication Systems, Inc. Mobile activity status tracker
GB2361389B (en) 2000-04-15 2004-01-28 Ericsson Telefon Ab L M Telecommunications system
US6731940B1 (en) * 2000-04-28 2004-05-04 Trafficmaster Usa, Inc. Methods of using wireless geolocation to customize content and delivery of information to wireless communication devices
US7031268B1 (en) * 2000-05-17 2006-04-18 Cisco Technology, Inc. Call optimization in ad-hoc conference calls
US6737989B2 (en) 2000-05-17 2004-05-18 Omega Patents, L.L.C. Vehicle tracker including variable frequency transmission and related methods
US8060389B2 (en) 2000-06-07 2011-11-15 Apple Inc. System and method for anonymous location based services
US6539232B2 (en) 2000-06-10 2003-03-25 Telcontar Method and system for connecting mobile users based on degree of separation
US6694351B1 (en) * 2000-06-30 2004-02-17 Cisco Technology, Inc. Call optimization in meet-me conference calls
US6687504B1 (en) * 2000-07-28 2004-02-03 Telefonaktiebolaget L. M. Ericsson Method and apparatus for releasing location information of a mobile communications device
AU2001285161A1 (en) * 2000-08-21 2002-03-04 United States Postal Services Delivery point validation system
US6898633B1 (en) * 2000-10-04 2005-05-24 Microsoft Corporation Selecting a server to service client requests
US7246187B1 (en) 2000-11-28 2007-07-17 Emc Corporation Method and apparatus for controlling exclusive access to a shared resource in a data storage system
US6377793B1 (en) 2000-12-06 2002-04-23 Xybernaut Corporation System and method of accessing and recording messages at coordinate way points
US7016847B1 (en) 2000-12-08 2006-03-21 Ben Franklin Patent Holdings L.L.C. Open architecture for a voice user interface
US7110749B2 (en) 2000-12-19 2006-09-19 Bellsouth Intellectual Property Corporation Identity blocking service from a wireless service provider
US7085555B2 (en) 2000-12-19 2006-08-01 Bellsouth Intellectual Property Corporation Location blocking service from a web advertiser
US20020077897A1 (en) 2000-12-19 2002-06-20 Zellner Samuel N. Identity blocking service from a web advertiser
US7224978B2 (en) 2000-12-19 2007-05-29 Bellsouth Intellectual Property Corporation Location blocking service from a wireless service provider
FI112902B (en) 2000-12-28 2004-01-30 Nokia Corp A method for transmitting a location-dependent message, a messaging system, and a wireless communication device
US7099332B2 (en) 2000-12-29 2006-08-29 Telefonaktiebolaget Lm Ericsson (Publ) Emergency calling with a VoIP device in a VLAN environment
US6744858B1 (en) * 2001-01-26 2004-06-01 Telcontrol, Inc. System and method for supporting multiple call centers
US7012901B2 (en) 2001-02-28 2006-03-14 Cisco Systems, Inc. Devices, software and methods for generating aggregate comfort noise in teleconferencing over VoIP networks
KR100369803B1 (en) 2001-03-10 2003-02-05 삼성전자 주식회사 Packet voice call service method in wireless telecommunication network and network architecture therefor
US6594483B2 (en) 2001-05-15 2003-07-15 Nokia Corporation System and method for location based web services
FI113001B (en) 2001-05-28 2004-02-13 Nokia Corp A method and an arrangement for locating a terminal in a packet switched network and a terminal utilizing the method
US6427001B1 (en) 2001-06-07 2002-07-30 Bellsouth Intellectual Property Corporation System and method for notification of 911 telephone calls using a link monitoring system
US7161939B2 (en) * 2001-06-29 2007-01-09 Ip Unity Method and system for switching among independent packetized audio streams
US6594576B2 (en) * 2001-07-03 2003-07-15 At Road, Inc. Using location data to determine traffic information
US7075900B2 (en) * 2001-07-10 2006-07-11 D.B. Zwirn Finance, Llc Software based single agent multipoint conference capability
AU2002354975A1 (en) * 2001-07-16 2003-03-03 Wavemarket Inc. System for providing alert-based services to mobile stations in a wireless communications network
US6996087B2 (en) * 2001-07-31 2006-02-07 Lucent Technologies Inc. Communication system including an interworking mobile switching center for call termination
US20030044654A1 (en) * 2001-08-31 2003-03-06 Holt Laurence E. Extending external telephone calls as conference calls with other communicatively proximate wireless devices
ES2305114T3 (en) * 2001-10-17 2008-11-01 Spyder Navigations L.L.C. PROCEDURE TO INFORM A NETWORK OF THE AMOUNT OF DATA TO TRANSFER.
DE60238073D1 (en) * 2001-10-30 2010-12-02 Alexander C Lang ADVANCED CALLS USING A BRIEFING SERVICE
US6813264B2 (en) 2001-11-02 2004-11-02 Qualcomm, Incorporated System and method for routing voice over IP calls
US20030109245A1 (en) * 2001-11-05 2003-06-12 Mccalmont Patti L Routing of emergency calls based on geographic location of originating telephone end office
US6771742B2 (en) * 2001-11-05 2004-08-03 Intrado Inc. Geographic routing of emergency service call center emergency calls
EP1315389A1 (en) 2001-11-16 2003-05-28 Telefonaktiebolaget Lm Ericsson Method for the determination of a receiver for location information
US6909776B2 (en) 2001-12-19 2005-06-21 Bellsouth Intellectual Property Corporation Systems and methods for monitoring network-based voice messaging systems
US7853272B2 (en) * 2001-12-21 2010-12-14 Telecommunication Systems, Inc. Wireless network tour guide
US20030119528A1 (en) * 2001-12-26 2003-06-26 Boathouse Communication Partners, Llc System and method for an automated intermediary to broker remote transaction between parties based on actively managed private profile information
US7072667B2 (en) 2001-12-31 2006-07-04 Nokia Corporation Location information service for a cellular telecommunications network
US7200380B2 (en) * 2002-03-28 2007-04-03 Telecommunication Systems, Inc. Wireless telecommunications location based services scheme selection
US6922565B2 (en) 2002-03-28 2005-07-26 Telecommunication Systems, Inc. Public safety access point (PSAP) selection for E911 wireless callers in a GSM type system
US7426380B2 (en) 2002-03-28 2008-09-16 Telecommunication Systems, Inc. Location derived presence information
US7321773B2 (en) 2002-03-28 2008-01-22 Telecommunication Systems, Inc. Area watcher for wireless network
JP4199475B2 (en) 2002-04-11 2008-12-17 日本電気株式会社 Positioning gateway device, terminal location information request processing method and program
US6957068B2 (en) 2002-05-13 2005-10-18 Qualcomm, Incorporated Subscriber station with dynamic multi-mode service acquisition capability
US6580390B1 (en) * 2002-05-30 2003-06-17 General Motors Corporation Method and system for global positioning system mask angle optimization
US7136466B1 (en) 2002-05-30 2006-11-14 Bellsouth Intellectual Property Corporation DSL integrated call waiting
JP4064964B2 (en) * 2002-07-04 2008-03-19 ノキア コーポレイション Packet-switched conference call management method, server, and terminal device
JP4016787B2 (en) 2002-07-31 2007-12-05 日本電気株式会社 Positioning system in mobile communication network
GB0218028D0 (en) * 2002-08-02 2002-09-11 Nokia Corp Location services for mobile communication system
AU2003257054A1 (en) 2002-08-16 2004-03-03 Nuasis Corporation Escalated handling of non-realtime communications
US8032149B2 (en) * 2002-08-29 2011-10-04 Andrew Llc Tasking and reporting method and implementation for wireless appliance location systems
US6839417B2 (en) 2002-09-10 2005-01-04 Myriad Entertainment, Inc. Method and apparatus for improved conference call management
EP1567956A4 (en) * 2002-11-08 2007-12-05 Dun & Bradstreet Inc System and method for searching and matching databases
WO2004052483A1 (en) 2002-12-10 2004-06-24 Nokia Corporation Method and device for continuing an electronic multi-player game, in case of an absence of a player of said game
US20070238455A1 (en) 2006-04-07 2007-10-11 Yinjun Zhu Mobile based area event handling when currently visited network doe not cover area
US20040143852A1 (en) 2003-01-08 2004-07-22 Meyers Philip G. Systems and methods for massively multi-player online role playing games
US6985747B2 (en) * 2003-02-05 2006-01-10 Autodesk, Inc. Use of triggers and a location hypercube to enable push-based location applications
GB0303080D0 (en) 2003-02-11 2003-03-19 Mobix Holdings Ltd Conference call facility
JP4517578B2 (en) 2003-03-11 2010-08-04 株式会社日立製作所 Peer-to-peer communication apparatus and communication method
US7730014B2 (en) 2003-03-25 2010-06-01 Hartenstein Mark A Systems and methods for managing affiliations
US6963557B2 (en) 2003-03-29 2005-11-08 Intrado Inc. System and method for routing telephone calls involving internet protocol network
US7403939B1 (en) 2003-05-30 2008-07-22 Aol Llc Resolving queries based on automatic determination of requestor geographic location
US7450566B2 (en) * 2003-06-05 2008-11-11 Oracle International Corporation Apparatus and method for providing a unified telephony solution
EP1645154B1 (en) 2003-06-27 2010-03-17 Nortel Networks Limited Call routing and corresponding updating of routing information
JP4330628B2 (en) 2003-08-22 2009-09-16 ノキア コーポレイション Apparatus and associated method for facilitating mobile station location determination according to location-based applications
US7251312B2 (en) * 2003-09-06 2007-07-31 Intrado Inc. Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores
US20070019614A1 (en) * 2003-09-09 2007-01-25 Klaus Hoffmann Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user
US7330112B1 (en) 2003-09-09 2008-02-12 Emigh Aaron T Location-aware services
US7027564B2 (en) 2003-09-22 2006-04-11 Foundry Networks, Inc. System, method and apparatus for supporting E911 emergency services in a data communications network
US7412050B2 (en) * 2003-10-01 2008-08-12 Aol Llc, A Delaware Limited Liability Company Conference calls via an intelligent call waiting interface
US8069082B2 (en) * 2003-10-06 2011-11-29 Utbk, Inc. Methods and apparatuses to determine prices of communication leads
US7440442B2 (en) * 2003-10-21 2008-10-21 3Com Corporation IP-based enhanced emergency services using intelligent client devices
TWI220614B (en) * 2003-10-21 2004-08-21 Benq Corp Method and device for updating frame number and automatically generating frame boundary
WO2005040166A1 (en) * 2003-10-23 2005-05-06 F.Hoffmann-La Roche Ag Triaza-spiropiperidine derivatives for use as glyt-1 inhibitors in the treatment of neurological and neuropsychiatric disorders
US7113797B2 (en) * 2003-11-06 2006-09-26 International Business Machines Corporation System, method and program product for scheduling meetings
US7436785B1 (en) 2003-11-12 2008-10-14 Sprint Spectrum L.P. Method and system for location based subject matter teleconferencing
US7877275B2 (en) * 2003-11-13 2011-01-25 General Motors Llc System and method for maintaining and providing personal information in real time
US20050125493A1 (en) 2003-11-13 2005-06-09 Hemant Chaskar IP-based mechanism for location service systems, methods, and devices
US7860811B2 (en) 2004-11-04 2010-12-28 Manyworlds, Inc. Adaptive recommendation explanations
ES2300536T3 (en) * 2003-12-02 2008-06-16 Alcatel Lucent DISSEMINATION OF SERVICES BASED ON THE LOCATION OF A MOBILE TERMINAL IN A WIRELESS NETWORK.
US7424293B2 (en) 2003-12-02 2008-09-09 Telecommunication Systems, Inc. User plane location based service using message tunneling to support roaming
US6968044B2 (en) 2003-12-05 2005-11-22 Bellsouth Intellectual Property Corporation Telephone emergency response system and method
US7181447B2 (en) * 2003-12-08 2007-02-20 Iac Search And Media, Inc. Methods and systems for conceptually organizing and presenting information
US7260186B2 (en) 2004-03-23 2007-08-21 Telecommunication Systems, Inc. Solutions for voice over internet protocol (VoIP) 911 location services
US6940950B2 (en) * 2003-12-19 2005-09-06 Telecommunication Systems, Inc. Enhanced E911 location information using voice over internet protocol (VoIP)
US20080090546A1 (en) 2006-10-17 2008-04-17 Richard Dickinson Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging
EP1698153A4 (en) 2003-12-22 2008-10-15 Linqware Inc System and method for initiating a conference call
US7937066B2 (en) * 2003-12-22 2011-05-03 911Tracker, Inc. Emergency conference calling system
US7174153B2 (en) * 2003-12-23 2007-02-06 Gregory A Ehlers System and method for providing information to an operator of an emergency response vehicle
US20050265318A1 (en) 2004-01-08 2005-12-01 Nokia Corporation Apparatus, system, and method for rejecting a session establishment request
US7369530B2 (en) * 2004-01-30 2008-05-06 Scott Keagy Apparatus and method for interfacing packet-based phone services with emergency call centers
US20050169248A1 (en) 2004-02-04 2005-08-04 Nortel Networks Limited Method and apparatus for providing in-band location information in an emergency response network
US7386111B2 (en) 2004-02-10 2008-06-10 Vonage Network Inc. Method and apparatus for placing a long distance call based on a virtual phone number
US7177399B2 (en) * 2004-02-27 2007-02-13 Nortel Network Limited Determining the geographical location from which an emergency call originates in a packet-based communications network
US7130385B1 (en) * 2004-03-05 2006-10-31 Avaya Technology Corp. Advanced port-based E911 strategy for IP telephony
US7177398B2 (en) * 2004-03-13 2007-02-13 Intrado Inc. Bi-directional messaging for an emergency services network
US7123693B2 (en) 2004-03-13 2006-10-17 Intrado Inc. Method and apparatus for increasing the reliability of an emergency call communication network
US7983835B2 (en) 2004-11-03 2011-07-19 Lagassey Paul J Modular intelligent transportation system
KR101085633B1 (en) 2004-05-17 2011-11-22 삼성전자주식회사 Method and apparatus for selecting location-server of mobile terminal when roaming and method for locating mobile terminals using the same
WO2005115035A1 (en) * 2004-05-20 2005-12-01 Research In Motion Limited Handling an audio conference related to a text-based message
US8265587B2 (en) 2004-06-17 2012-09-11 West Corporation System and method for amending instructions for emergency auxiliary services following an emergency services request
US8903820B2 (en) 2004-06-23 2014-12-02 Nokia Corporation Method, system and computer program to enable querying of resources in a certain context by definition of SIP even package
US7764944B2 (en) 2004-06-24 2010-07-27 Alcatel-Lucent Usa Inc. Method of providing a unique call back number for wireless 9-1-1 calls
US7650142B2 (en) * 2004-07-08 2010-01-19 Nortel Networks Limited Method for setting up a conference call
US7260384B2 (en) 2004-07-29 2007-08-21 Sprint Spectrum L.P. Method and system for dynamic selection of voice mail system
US7840681B2 (en) * 2004-07-30 2010-11-23 International Business Machines Corporation Method and apparatus for integrating wearable devices within a SIP infrastructure
US7881233B2 (en) * 2004-09-01 2011-02-01 Cisco Technology, Inc. Techniques for planning a conference using location data
DE102004043337B4 (en) * 2004-09-08 2007-07-12 Daimlerchrysler Ag Transverse differential of a motor vehicle and its manufacturing process
US7787611B1 (en) 2004-09-17 2010-08-31 Cisco Technology, Inc. Packet telephony bridging server
US7333480B1 (en) * 2004-09-20 2008-02-19 Nortel Networks Limited Localization of call routing for TDM sets in an IP network
US20080214273A1 (en) 2004-09-21 2008-09-04 Snoddy Jon H System, method and handheld controller for multi-player gaming
US20060068753A1 (en) * 2004-09-22 2006-03-30 Jim Karpen Emergency call handling system
US7532713B2 (en) 2004-09-23 2009-05-12 Vapps Llc System and method for voice over internet protocol audio conferencing
US7573982B2 (en) 2004-10-12 2009-08-11 Bellsouth Intellectual Property Corporation Methods and systems for managing a call session
US20060079330A1 (en) * 2004-10-13 2006-04-13 Motorola, Inc. Method and apparatus utilizing dynamic visual characters to address communications
US7113128B1 (en) 2004-10-15 2006-09-26 Telecommunication Systems, Inc. Culled satellite ephemeris information for quick, accurate assisted locating satellite location determination for cell site antennas
US20060088152A1 (en) * 2004-10-21 2006-04-27 Lightbridge, Inc. Conference-call initiation
GB0424052D0 (en) * 2004-10-29 2004-12-01 Nortel Networks Ltd Improvements in or relating to internet protocol (IP) location, privacy and presence
US7505482B2 (en) * 2004-11-15 2009-03-17 At&T Intellectual Property I, L.P. Application services infrastructure for next generation networks
US20060117020A1 (en) 2004-12-01 2006-06-01 John Toebes Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device
US8027658B2 (en) 2004-12-10 2011-09-27 At&T Intellectual Property I, L.P. Enhanced emergency service provider
IL165817A0 (en) 2004-12-16 2006-01-15 Samsung Electronics U K Ltd Electronic music on hand portable and communication enabled devices
US7747258B2 (en) 2005-02-04 2010-06-29 Qualcomm Incorporated Method and apparatus for performing position determination with pre-session action
US20070041513A1 (en) * 2005-02-08 2007-02-22 Gende Michael F Emergency call identification, location and routing method and system
US7756253B2 (en) 2005-02-22 2010-07-13 At&T Intellectual Property Ii, Lp Methods and systems for providing foreign call back number compatibility for VoIP E9-1-1 calls
US7545916B2 (en) 2005-02-28 2009-06-09 At&T Intellectual Property I Methods of placing emergency calls using data networks
US20060258380A1 (en) 2005-05-16 2006-11-16 Kai Liebowitz Interactive opt-in-messaging
US8175570B2 (en) * 2005-05-26 2012-05-08 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8103242B2 (en) * 2005-05-26 2012-01-24 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US20060281437A1 (en) 2005-06-13 2006-12-14 Qwest Communications International Inc. Systems and methods for supporting E911 emergency services in a data communications network
US9154907B2 (en) 2005-06-21 2015-10-06 Qualcomm Incorporated Efficient periodic location reporting in a radio access network
US20070003024A1 (en) * 2005-06-22 2007-01-04 Cml Emergency Services Inc. Network emergency call taking system and method
US20060293024A1 (en) 2005-06-23 2006-12-28 Lucent Technologies Inc. Methods and apparatus for improved 911 support for VoIP service
US8600410B2 (en) * 2005-07-28 2013-12-03 Unwired Planet, Llc Wireless network with adaptive autonomous location push
US20070027997A1 (en) * 2005-07-29 2007-02-01 Cisco Technology, Inc. Technique for translating location information
US10178522B2 (en) * 2005-08-02 2019-01-08 Qualcomm Incorporated VoIP emergency call support
US20070036139A1 (en) * 2005-08-09 2007-02-15 Ashish Patel System and method for authenticating internetwork resource requests
US8160577B2 (en) * 2005-08-19 2012-04-17 Global Locate, Inc. Method and apparatus for providing intelligent deactivation of electronic devices in aircraft
US7245900B1 (en) 2005-08-24 2007-07-17 Sprint Spectrum L.P. Method and system for using basic service set identifiers (BSSIDs) for emergency services routing
US20070049288A1 (en) * 2005-08-24 2007-03-01 Lamprecht Leslie J Creating optimum temporal location trigger for multiple requests
US20070081635A1 (en) * 2005-09-29 2007-04-12 Marian Croak Method and apparatus for providing enhanced 911 for nomadic users
US8824454B2 (en) * 2005-10-24 2014-09-02 West Corporation Peering network for parameter-based routing of special number calls
US7711094B1 (en) * 2005-11-16 2010-05-04 Verizon Data Services Llc E911 location server
US8185128B2 (en) * 2005-11-30 2012-05-22 Qualcomm Incorporated Method and apparatus for supporting location services with roaming
US8355410B2 (en) * 2007-08-17 2013-01-15 At&T Intellectual Property I, L.P. Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol
US8185567B2 (en) 2006-01-02 2012-05-22 Telecommunication Systems, Inc. Location aware content using presence information data formation with location object (PIDF-LO)
US20070160036A1 (en) 2006-01-10 2007-07-12 Smith David M Method and system for servicing enhanced 911 calls
US8059789B2 (en) 2006-02-24 2011-11-15 Telecommunication Systems, Inc. Automatic location identification (ALI) emergency services pseudo key (ESPK)
US8958346B2 (en) 2006-03-02 2015-02-17 Tango Networks, Inc. Calling line/name identification of enterprise subscribers in mobile calls
US8208461B2 (en) 2006-04-04 2012-06-26 Telecommunication Systems, Inc. SS7 MAP/Lg+ to SIP based call signaling conversion gateway for wireless VoIP E911
US8358645B2 (en) 2006-04-14 2013-01-22 Cisco Technology, Inc. Determining a physical location of a VoIP endpoint device utilized to originate an emergency call
US7937067B2 (en) * 2006-05-16 2011-05-03 Red Sky Technologies, Inc. System and method for an emergency location information service (E-LIS)
US7495608B1 (en) * 2006-06-16 2009-02-24 Cellco Partnership Position determination using almanac for virtual base stations
US7940896B2 (en) * 2006-06-29 2011-05-10 Avaya Inc. Adaption of emergency calls to the emergency services network based on caller location
US8044778B2 (en) * 2007-07-12 2011-10-25 Henry Schein, Inc. Injection device and case with reporting ability
US8223717B2 (en) 2006-08-03 2012-07-17 Accuris Technologies Roaming gateway
US20080032703A1 (en) * 2006-08-07 2008-02-07 Microsoft Corporation Location based notification services
US20080059304A1 (en) * 2006-08-16 2008-03-06 Kimsey Robert S Method of active advertising and promotion in an online environment
US8774370B2 (en) * 2006-08-21 2014-07-08 Connexon Telecom Inc. System and method for delivering callback numbers for emergency calls in a VOIP system
US20080065775A1 (en) * 2006-09-13 2008-03-13 Cisco Technology, Inc. Location data-URL mechanism
US8411833B2 (en) * 2006-10-03 2013-04-02 Microsoft Corporation Call abuse prevention for pay-per-call services
US8503430B2 (en) * 2006-11-21 2013-08-06 Qualcomm Incorporated Dynamic operational mode management for a wireless terminal
US8333641B2 (en) * 2006-12-14 2012-12-18 Sullivan C Bart Wireless video game system and method
CA2612645C (en) 2006-12-22 2011-05-24 Bce Inc. Method and system for configuring information regarding processing of calls involving a party
US20080214202A1 (en) 2007-03-02 2008-09-04 General Instrument Corporation Method and Apparatus for Bluetooth Discoverability Using Region Estimation
US20090319180A1 (en) 2007-04-27 2009-12-24 Aaron Thomas Robinson Emergency responder geographic information system
WO2009061858A1 (en) * 2007-11-05 2009-05-14 T-Mobile Usa, Inc. Method and system for allowing incoming emergency communications on a disabled device
WO2009132669A1 (en) * 2008-04-30 2009-11-05 Telecom Italia S.P.A. Method and system for enabling a user to get information about entities of predefined categories
US8308570B2 (en) 2009-11-18 2012-11-13 Sony Computer Entertainment America Inc. Synchronizing mission progress in peer-to-peer cooperative games
US20110149953A1 (en) 2009-12-23 2011-06-23 William Helgeson Tracking results of a v2 query in voice over internet (VoIP) emergency call systems
US20130072308A1 (en) * 2011-09-15 2013-03-21 Qonqr, Llc Location-Based Multiplayer Game System and Method

Also Published As

Publication number Publication date
US20090077077A1 (en) 2009-03-19
US20090092232A1 (en) 2009-04-09
US9413889B2 (en) 2016-08-09

Similar Documents

Publication Publication Date Title
US20160330321A1 (en) House number normalization for master street address guide (msag) address matching
US8102972B2 (en) Emergency services selective router interface translator
US8718595B2 (en) Emergency data message router database
US8068587B2 (en) Nationwide table routing of voice over internet protocol (VOIP) emergency calls
US8305912B2 (en) Network and method providing an indication of network capabilities to a user for special number calls
US9390615B2 (en) Emergency alert for voice over internet protocol (VoIP)
US8880021B2 (en) System and method for updating location information of voice-over-internet protocol based devices for E911 services
US20050213565A1 (en) Method for routing an emergency call from a voice over internet protocol phone to a public safety answering point
US9185537B2 (en) Systems and methods for alternative routing of voice over IP originated emergency calls
US20160112843A1 (en) Mobile Automatic Location Identification (ALI) for First Responders
US20060109960A1 (en) System and method for unilateral verification of caller location information
US8830987B2 (en) IP-based call answering point selection and routing
US9178996B2 (en) Unique global identifier header for minimizing prank 911 calls
US9584661B2 (en) Extended efficient usage of emergency services keys
US20080065628A1 (en) Associating Metro Street Address Guide (MSAG) validated addresses with geographic map data
US20090089070A1 (en) System and Method for Validating and Processing Customer Entered Addresses
US20100046720A1 (en) Point-in-poly routing for voice over internet protocol (VoIP) emergency calls with embedded geographic location information
US8532266B2 (en) Efficient usage of emergency services keys

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION