Navigation system with user generated content mechanism and method of operation thereof

• US 8,306,729 B2
• Filed: 10/13/2009
• Issued: 11/06/2012
• Est. Priority Date: 10/13/2009
• Status: Active Grant

• Current Assignee: TeleNav Incorporated
• Original Assignee: TeleNav Incorporated
• Inventors: Liu, Winston Yonglong
• Primary Examiner(s): Tran, Dalena
• Application Number:
  US12/578,158
• Publication Number:
  US 20110087427A1
• Time in Patent Office: 1,120 Days
• Field of Search: 701/400, 701/408, 701/425, 380/30, 715/810, 717/168, 717172-174
• US Class Current: 701/400
• CPC Class Codes: G01C 21/20 Instruments for performing navigational calculations G01C21/24, G01C21/26 take precedence
• CPC Class Codes: G01C 21/3679 Retrieval, searching and output of POI information, e.g. hotels, restaurants, shops, filling stations, parking facilities G01C21/3611 takes precedence

Abstract

A method of operation of a navigation system includes: receiving a change request with a proposed change for an item; verifying a validity of the change request based on a confidence level meeting or exceeding a change threshold; and updating a target element of the item based on the validity of the proposed change for avoiding an incorrect update to the target element for displaying on a device.

Claims

1. A method of operation of a navigation system comprising:

receiving a change request with a proposed change for an item;

verifying a validity of the change request based on a confidence level meeting or exceeding a change threshold with a control unit;

updating a target element of the item based on the validity of the proposed change for avoiding an incorrect update to the target element for displaying on a device; and

wherein;

verifying the validity of the change request includes calculating the confidence level based on the number of times the change request matches an entry on a change candidate list of the item to correlate with multiple potential modifications.

2. The method as claimed in claim 1 wherein receiving a change request includes selecting the item for the change request from an item list.

3. The method as claimed in claim 1 wherein verifying the validity of the change request based on the confidence level includes calculating the confidence level based on a user'"'"'s status.

4. The method as claimed in claim 1 wherein verifying the validity the change request based on the change confidence level includes calculating the confidence level based on a time interval between the change request and a change candidate entry meeting or being below a time interval threshold.

5. A method of operation of a navigation system comprising:

receiving a change request with proposed change for an item;

verifying a validity of the change request matching a change candidate entry in a change candidate list based on a confidence level meeting or exceeding a change threshold with a control unit;

updating a target element of the item based on the validity of the proposed change for avoiding an incorrect update to the target element for displaying on a device; and

wherein;

verifying the validity of the change request includes calculating the confidence level based on the number of times the change request matches an entry on a change candidate list of the item to correlate with multiple potential modifications.

6. The method as claimed in claim 5 wherein verifying the validity of the change request includes varying the change threshold based on a change request type to differentiate between potential modifications requiring more correlation between multiple changes.

7. The method as claimed in claim 5 further comprising matching the change request to the change candidate entry including:

matching a proposed change name to a change candidate name; and

matching a proposed change value to a change candidate value.

8. The method as claimed in claim 5 further comprising matching the change request to the change candidate entry includes identifying the change request as a change candidate entry based on the proposed change name not previously existing in the change candidate list.

9. The method as claimed in claim 5 further comprising matching the change request to the target element of the item includes matching the proposed change name to the target element name based on the exact match of the proposed change name and the target element name.

10. A navigation system comprising:

a controller interface for receiving a change request;

a verify change request module, coupled to the controller interface, for verifying the change request of an item based on the validity of the proposed change for avoiding an incorrect update to the target element;

an update item module, coupled to the controller interface, for updating the target element of the item based on the validity of the proposed change for avoiding an incorrect update to the target element; and

wherein;

the verify change request module is for calculating the confidence level based on the number of times the change request matches an entry on a change candidate list of the item to correlate with multiple potential modifications.

11. The system as claimed in claim 10 wherein the controller interface is for receiving a change request based on selecting the item for the change request for an item list.

12. The system as claimed in claim 10 wherein the verify change request module is for calculating the confidence level based on the user'"'"'s status.

13. The system as claimed in claim 10 wherein the verify change request module is for calculating a change confidence level based on a time interval between a change request and a change candidate entry below a time interval threshold.

14. The system as claimed in claim 10 further comprising a match change candidate module, coupled to the controller interface, for matching the change request to the change candidate entry of the change candidate list.

15. The system as claimed in claim 14 wherein the match change candidate module for verifying the validity of the change request includes varying the change threshold based on the change request type to differentiate between changes requiring more correlation between multiple changes.

16. The system as claimed in claim 14 wherein the match change candidate module for matching the change request to the change candidate entry includes:

matching a proposed change name to a change candidate name; and

matching a proposed change value to a change candidate value.

17. The system as claimed in claim 14 wherein the match change candidate module is for identifying the change request as a change candidate entry based on the proposed change name not previously existing in the change candidate list.

18. The system as claimed in claim 14 wherein the match change candidate module, coupled to the controller interface, for matching the change request to the target element of the item includes matching the proposed change name to the target element name based on the exact match of the proposed change name and the target element name.