Source: https://patents.justia.com/patent/8775074
Timestamp: 2019-11-22 20:57:16
Document Index: 357445951

Matched Legal Cases: ['application No. 201010107813', 'Application No. 201010107831', 'Application No. 201010107846', 'Application No. 201010107866', 'Application No. 201010107813', 'Application No. 201010107887', 'Application No. 2010']

US Patent for Method and system for refreshing location code data Patent (Patent # 8,775,074 issued July 8, 2014) - Justia Patents Search
Justia Patents Updating Existing User Map DatabaseUS Patent for Method and system for refreshing location code data Patent (Patent # 8,775,074)
Jan 30, 2009 - Navteq B.V.
The present patent application is related to the copending patent applications filed on the same date, Ser. No. 12/362,734, entitled “METHOD AND SYSTEM FOR ASSESSING QUALITY OF LOCATION CONTENT,” Ser. No. 12/362,751, entitled “METHOD AND SYSTEM FOR MANAGING RELATIONSHIPS BETWEEN LOCATION IDENTIFIERS,” Ser. No. 12/362,786, entitled “METHOD FOR REPRESENTING LINEAR FEATURES IN A LOCATION CONTENT MANAGEMENT SYSTEM,” and Ser. No. 12/362,807, entitled “METHOD AND SYSTEM FOR EXCHANGING LOCATION CONTENT DATA IN DIFFERENT DATA FORMATS.”
FIG. 3 is a block diagram of an example location code change system 300 that may be used as the location code change system 106 depicted in FIG. 1. Other location code change system designs may also be used. The location code change system 300 includes a map change receiver 301, a map change requester 302, a request scheduler 303, a user interface 304, a map change processor 305, a change process metadata repository 306, a map change queue 307, a queue listener 308, a queue filter 309, a location code updater 310, a geocoder 311, a geocoder data store 312, a location code change receiver 313, and a location code change notifier 314. The location code change system 300 may have other components as well.
receiving a first message identifying a first map vendor and a map version of a first map database, wherein the first message includes map change data in a format associated with the first map database and specifies a removed road link and a new road link;
receiving a second message identifying a second map vendor and a map version of a second map database, wherein the second message includes map change data in a format associated with the second map database;
converting the format associated with the first map database and the format associated with the second map database to a common format;
determining whether the map change data affects a location code stored in a location code system, wherein the location code links geographic coordinates to content for the first map vendor and the second map vendor;
updating location code data associated with the location code based on the map change data by removing a reference to the removed road link and attaching the new road link to the location code; and
2. The method of claim 1, further comprising authenticating the first message to identify specifications for the first map vendor.
3. The method of claim 1, wherein determining whether the map change data of the first message affects the location code data includes examining the first map vendor, the map version of the first map database, and a map change type.
4. The method of claim 1, wherein uploading data for the location code includes performing a forward geocoding operation if the location code contains address information.
5. The method of claim 1, wherein updating location code data for the location code includes performing a reverse geocoding operation if the location code does not contain address information.
6. The method of claim 1, wherein updating data for the location code includes using the map change data to manipulate the location code data.
7. The method of claim 1, further comprising performing a map baseline shift if the location code data includes data for a number of map versions that exceeds a predetermined amount.
8. The method of claim 7, wherein the map baseline shift includes deleting the location code data for map version associated with an oldest date.
9. A location code change system used for refreshing location code data stored in a location code system, comprising:
a map change receiver operable to receive messages that include map change data, wherein the map change data identifies a first map vendor and a first map version associated with the map change data and a second map vendor and a second map version associated with the map change data;
a map change processor operable to transform the map change data obtained by the map change receiver into a common format compatible with the first map vendor and the second map vendor; and
a location code updater operable to identify location codes affected by the map change data using the common format and update the affected location codes, wherein the location codes link geographic locations to location content and the location code updater is configured to send a message to the location code system that includes updated location code data.
10. The system of claim 9, further comprising a map change requester operable to request the map change data.
11. The system of claim 10, further comprising a map change scheduler operable to signal the map change requester to request the map change data.
12. The system of claim 9, further comprising a map change queue that stores the transformed map change data prior to the location code updater identifying the affected location codes.
a geocoder operable to perform geocoding operations for the location code updater; and
a geocoder data store configured to store geocoding data used by the geocoder.
14. The system of claim 9, further comprising a location code change receiver that receives messages from the location code system that includes location code change data.
15. A data refresh system for updating location code data, comprising:
a map change system that receives a plurality of messages from the map system that includes map change data, wherein each of the plurality of messages identifies a map vendor and a version number, wherein the map change system formats the map change data to be compatible for a plurality of map vendor formats, wherein the map change system identifies an action based on the map vendor and the version number;
a location code change system that receives the formatted map change data from the map change system and updates location code data based on the formatted map change data, wherein the location code data links content to geographic locations; and
a location code system that receives updated location code data from the location code change system.
16. The system of claim 15, wherein the location code system sends messages to the location code change system that includes location code change data.
17. The system of claim 16, wherein the location code change system sends the location code change data to the map change system.
18. The system of claim 17, wherein the map change system sends the location code change data to the map system.
19. The method of claim 1, wherein the location code is configured to allow multiple map vendors to update the content.
6876921 April 5, 2005 Omi
6970782 November 29, 2005 Watanabe et al.
7281021 October 9, 2007 Shiota et al.
7373247 May 13, 2008 Park
7487114 February 3, 2009 Florance et al.
7564375 July 21, 2009 Brinton et al.
7584049 September 1, 2009 Nomura
7649838 January 19, 2010 Fishteyn et al.
7720596 May 18, 2010 Kobuya et al.
7805442 September 28, 2010 Joshi et al.
8065291 November 22, 2011 Knorr
20010051973 December 13, 2001 Green et al.
20020070934 June 13, 2002 Sakamoto et al.
20040030490 February 12, 2004 Hegedus et al.
20040044752 March 4, 2004 Hamaguchi et al.
20050060313 March 17, 2005 Naimat et al.
20050096849 May 5, 2005 Sorrells
20050149257 July 7, 2005 Linkohr
20050165743 July 28, 2005 Bharat et al.
20060149800 July 6, 2006 Egnor et al.
20060230452 October 12, 2006 Field
20070106455 May 10, 2007 Fuchs
20070146374 June 28, 2007 Riise et al.
20070239648 October 11, 2007 Thota
20070260628 November 8, 2007 Fuchs et al.
20070294031 December 20, 2007 Brinton et al.
20080214300 September 4, 2008 Williams et al.
20080228391 September 18, 2008 Sarkeshik
20080228392 September 18, 2008 Fuchs
20080256039 October 16, 2008 Chang et al.
20080256060 October 16, 2008 Chang et al.
20080319670 December 25, 2008 Yopp et al.
20090043498 February 12, 2009 Maethner
20090049038 February 19, 2009 Gross
20090070379 March 12, 2009 Rappaport
20090143984 June 4, 2009 Baudisch et al.
20100211307 August 19, 2010 Geelen
101154222 April 2008 CN
101319911 December 2008 CN
H10229577 August 1998 JP
H11224047 August 1999 JP
2001075967 March 2001 JP
2001134595 May 2001 JP
2001243595 September 2001 JP
2002041554 February 2002 JP
2002/333830 November 2002 JP
200233830 November 2002 JP
2004191419 July 2004 JP
2005025291 January 2005 JP
2005291872 October 2005 JP
2007089196 April 2007 JP
2007147567 June 2007 JP
2007193066 August 2007 JP
2008096706 April 2008 JP
2009003838 January 2009 JP
WO2006/074056 July 2006 WO
WO2006/105754 October 2006 WO
WO2007131044 November 2007 WO
WO2008/154571 December 2008 WO
European Search Report for EP10250102.0, dated Jul. 8, 2010.
European Search Report for EP 10250100.4-1236, dated Mar. 16, 2012.
Wubbahed.com, Importing Google Maps to your Nokia N95 (Jun. 29, 2007), http://wubbahed.com/2007/06/29/importing-mogle-maps-to-your-nokia-n95/.
European Search Report for EP 10250101.2 dated Jul. 6, 2010.
Priedhorsky, et al. “The Computational Geowiki: What, Why and How.” GroupLens Research, Department of Computer Science and Engineering, University of Minnesota. Paper presented at Computer Supported Cooperative Work Conference. 2008.
Chinese Office Action for related application No. 201010107813.2 mailed Dec. 19, 2012.
Chinese Office Action issued in Chinese Application No. 201010107831.0, mailed Jun. 20, 2013.
Chinese Office Action cited in CN Application No. 201010107846.7, mailed Sep. 2, 2013.
Chinese Office Action for related Chinese Application No. 201010107866.4, mailed Jan. 7, 2013.
Chinese Office Action in Chinese Application No. 201010107813.2, mailed Oct. 22, 2013.
European Search Report for European Application No. EP 13155460, mailed Oct. 30, 2013.
Chinese Office Action in Chinese Application No. 201010107887.6, mailed Apr. 2, 2013.
Chinese Office Action issued in Application No. CN201010107866.4, mailed Nov. 22, 2013.
Japanese Office Action issued in Application No. JP2010-034052, mailed Nov. 27, 2013.
Japanese Office Action issued in Application No. JP2010-034054, mailed Nov. 15, 2013.
Japanese Office Action for JP Application No. 2010-034053, mailed Oct. 23, 2013.
Patent number: 8775074
Patent Publication Number: 20100194605
Inventors: Vojislav Samsalovic (Chicago, IL), Paul M. Bouzide (Chicago, IL)
Application Number: 12/362,767
Current U.S. Class: Updating Existing User Map Database (701/450); Data Sent To User From Remote Location (701/451); Data Sent In Increments (701/452); Employing Map Database System (701/532); Map Display (340/995.1); Having Plural Maps (340/995.11); Transmission Of Map Data To Vehicle (340/995.12); Plural Version Management (717/170)
International Classification: G01C 21/12 (20060101); G08G 1/123 (20060101); G06F 9/44 (20060101);