1. Field of the Invention
The present invention relates generally to wireless and long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to location based services, and most particularly to navigation using location based services.
2. Background of the Related Art
The demand for wireless communication services are ever increasing in response to a society that is becoming increasingly mobile. As a result, wireless devices, and in particular cell phones, have become ubiquitous with day-to-day life. A majority of people in the United States now own cell phones.
Location services are a more recent advanced feature made available for use with wireless devices, perhaps most notably to provide location of a cell phone. The general goal of location-based services is to automatically provide location-based information to a requesting application. The requesting application may be operating on the wireless device itself, or even on an external application running, e.g., on another device in the wireless or other network. Some exemplary applications that use location services include mapping applications that show interesting places in a vicinity of the wireless device's current global position, and navigation from a current location. Location based services are available for wireless devices such as personal digital assistants (PDAs) as well as for cell phones.
A geospatial entity object code (Geocode) is code that represents a geospatial coordinate measurement of an exact geographic location on (or above, or below) the earth. Many location-based applications on current wireless phones allow a user of the wireless phone to manually input a geocode location, and get in response a location based service, e.g., navigation to a desired destination.
A geocoded representation is derived from latitude, longitude, altitude, date, local time, global time, and other geospatial attributes, e.g., how the area is coded (number, letter, mixture of both, other); which part of the earth is covered (whole earth, land, water, a continent, a country); what kind of area or location is coded (country, county, airport, railstation, city); and/or whether an area or a point is coded.
In practice, a geocoded location may be entered by the name of the location. While entry of a location name is much more user-friendly than an all-natural numerical input relating to latitude, longitude, etc., it is subject to error when input by the user.
In particular, as shown in
The conventional system aims to shorten a user's need to enter all letters of a given location name. However, if the user doesn't know how to properly spell the location, particularly in the earliest letters in the location name, the conventional system will not be able to present the user with a small, focused list from which to choose a location. Moreover, if the user has misspelled any letter in the location name, conventional systems quite simply will in fact exclude, rather than include, the intended location name. Furthermore, even with the conventional system aimed at assisting a user to input a geocoded location correctly in the first place, the conventional system has no way of automatically correcting a mistaken geocode once it is entered by the user.
There is a need for an improved location input technique on a wireless phone.
In accordance with the principles of the invention, a method and apparatus for automatically correcting an input location including a typographical mistake comprises comparing an input location parameter to a plurality of possible location parameter matches. The plurality of possible location parameter matches are ranked based on edit distance between the input location parameter and the possible location parameter. A best ranked one of the plurality of possible location parameters is provided as a correction to the input location parameter.
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:
The invention relates to manual or semi-manual input of a geocode location. The present inventors have realized that a geocode location is subject to erroneous manual input by the user, particularly using the keypad of a typical wireless phone. If the user makes a mistake during manual input of a location name, the geocode will likely fail and an error message would be generated. This wastes network resources, not to mention the user's time.
Existing technology does not automatically fix spelling mistakes in geocode location input. Conventional systems may give a user locations matching the contiguous letters entered to that point by the user, but the user must spell the beginning few or more letters of the location correctly to narrow the field of possible choices for location, which may be presented to the user. However, the existing technology is disadvantageous because a user unsure of the spelling of the beginning of a given location's name may be unable to manually enter a location.
In particular, as shown in
Preferably the geocoded location manual input monitor 100, possible matches database 102, and/or possible match ranker based on edit distance module 104 are resident in the wireless device 100. However, any or all of these elements 100-104 may be alternatively located in a central location, e.g., in a server at the wireless base station in communication with the wireless device 100.
In accordance with the principles of the present invention, the geocoded location manual input monitor 100 looks for a best match for location input based on edit distance from possible matches in the possible matches database 102. Edit distance ranks correction options based on a ‘confidence factor’.
In accordance with the principles of the present invention, given a geocode location/address input, the geocoding indices are searched for close matches. All the ‘closely’ matching entries are evaluated for their closeness to the input, thereby giving a ‘confidence factor’ or score. If there is no perfect match, then we return a list of geocode options sorted by the score. The ‘closeness’ is derived by looking at the edit distance to go from the input to the matched address.
Edit distance is defined herein as the number of insertion/deletion/replacement operations to go from input location to the possible matched location. In one embodiment, an option list, or ‘pick list’, may be provided based on an edit distance scoring system. The edit distance scoring system is preferably based on a number of keystrokes difference between the input location name and the possible matched location name.
For example, a user might intend to input “Maine”, but instead incorrectly inputs “Main”. The edit distance between the input “Maine” and the possible match “Main”, “Main” vs the correct “Maine”, is 1 deletion, or 1 keystroke score.
Using the edit distance scoring system, there are three (3) types of keystroke mistakes: an insertion mistake, a deletion mistake, and a replacement of character mistake. In the disclosed embodiments all types of mistakes are ranked equally. It is within the principles of the invention to score the types of mistakes differently. A difference in the type of scoring may be determined empirically.
Automatic correction of an input location may be determined based on various elements of the input location name. For instance, a geocoded location may be input not by name (or in addition to name), but instead by another identifying parameter, e.g., on:
In particular, as shown in step 200 of
In step 202, the user's manual input is compared to the entries in the possible match database 102.
In step 204, entries in the possible match database 102 are ranked based on edit distance to what the user input.
In step 206, the best ranked match is selected, and presented as the input geocoded location. Preferably the ‘best’ ranked match is that which has the highest numerical ranking based on edit distance to entries in the possible matches database 102.
If the user input a correctly spelled location in the first place, the best ranked match, and the highest scoring match with no errors, would be the correct location.
The invention has particular applicability to use in cell phones and other wireless devices.
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.
The present application is a continuation of U.S. application. Ser. No. 11/797,819, entitled “Location Input Mistake Correction”, filed on May 8, 2007, now U.S. Pat. No. 8,370,339; which claims priority from U.S. Provisional Application No. 60/798,330, entitled “Location Input Mistake Correction” to Ahuja et al., filed May 8, 2006, the entirety of both of which are expressly incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5006837 | Bowers | Apr 1991 | A |
5200738 | Fumoto | Apr 1993 | A |
5263136 | DeAguiar | Nov 1993 | A |
5781200 | Lu | Jul 1998 | A |
5973700 | Taylor | Oct 1999 | A |
6104416 | McGuiness | Aug 2000 | A |
6144338 | Davies | Nov 2000 | A |
6262741 | Davies | Jul 2001 | B1 |
6434482 | Oshida | Aug 2002 | B1 |
6487495 | Gale | Nov 2002 | B1 |
6529143 | Mikkola | Mar 2003 | B2 |
6571169 | Miyaki | May 2003 | B2 |
6587782 | Nocek | Jul 2003 | B1 |
6714205 | Miyahita | Mar 2004 | B1 |
6734867 | Munshi | May 2004 | B1 |
6834229 | Rafiah et al. | Dec 2004 | B2 |
6904176 | Chui | Jun 2005 | B1 |
6912545 | Lundy et al. | Jun 2005 | B1 |
6940407 | Miranda-Knapp | Sep 2005 | B2 |
6947976 | Devitt et al. | Sep 2005 | B1 |
7190839 | Feather | Mar 2007 | B1 |
7385600 | Marion | Jun 2008 | B2 |
7840579 | Samuelson et al. | Nov 2010 | B2 |
20020067353 | Kenyon | Jun 2002 | A1 |
20030011623 | Dermer | Jan 2003 | A1 |
20030016804 | Sheha et al. | Jan 2003 | A1 |
20030034936 | Ernst | Feb 2003 | A1 |
20030137961 | Tsirtsis et al. | Jul 2003 | A1 |
20040135784 | Cohen | Jul 2004 | A1 |
20040158829 | Beresin | Aug 2004 | A1 |
20040185870 | Matsuda | Sep 2004 | A1 |
20040217980 | Radburn | Nov 2004 | A1 |
20050174333 | Robinson et al. | Aug 2005 | A1 |
20050270311 | Rasmussen | Dec 2005 | A1 |
20050288033 | McNew | Dec 2005 | A1 |
20050289141 | Baluja | Dec 2005 | A1 |
20060005114 | Williamson | Jan 2006 | A1 |
20060023626 | Krausz | Feb 2006 | A1 |
20060055693 | Sylthe | Mar 2006 | A1 |
20060058943 | Pascual et al. | Mar 2006 | A1 |
20060176283 | Suraqui | Aug 2006 | A1 |
20060224997 | Wong | Oct 2006 | A1 |
20060246922 | Gasbarro | Nov 2006 | A1 |
20060256130 | Gonzalez | Nov 2006 | A1 |
20070041513 | Gende | Feb 2007 | A1 |
20070072620 | Levitan | Mar 2007 | A1 |
20070149243 | Hwang | Jun 2007 | A1 |
20080104227 | Birnie et al. | May 2008 | A1 |
Number | Date | Country |
---|---|---|
PCTUS000023 | Jan 2000 | WO |
PCTUS05023244 | Jun 2005 | WO |
PCTCA05001512 | Oct 2005 | WO |
Entry |
---|
NENA Statement on VoIP E9-1-1 Implementation issues, National Emergency No. Association, Mar. 2006. |
Internal Search Report received in PCT/US2007/11027 dated Oct. 23, 2008. |
European Search Report received in European Appl. No. 07794624.2 dated Jun. 17, 2010. |
Internal Search Report received in PCT/US2007/10542 dated Nov. 26, 2008. |
Number | Date | Country | |
---|---|---|---|
20130151512 A1 | Jun 2013 | US |
Number | Date | Country | |
---|---|---|---|
60798330 | May 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11797819 | May 2007 | US |
Child | 13758701 | US |