LOCATION-BASED SERVICES

• US 20170178415A1
• Filed: 12/29/2016
• Published: 06/22/2017
• Est. Priority Date: 08/22/2008
• Status: Active Grant

• Current Assignee: Titan Intelligence Technology Limited
• Original Assignee: Telit Automotive Solutions Nv (TUS International Ltd.)
• Inventors: PEETERS, Michael, DEBAST, Claude, FROIDCOEUR, Tim
• Granted Patent: US 10,621,793 B2
• Time in Patent Office: Days
• CPC Class Codes: G01C 21/30 Map- or contour-matching
• CPC Class Codes: G01S 19/42 Determining position
• CPC Class Codes: G06Q 20/145 Payments according to the detected use or quantity
• CPC Class Codes: G07B 15/02 taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems G07B15/06 takes precedence; taximeters G07B13/00; parking meters per se G07F17/24; car rental systems per se G07B15/00
• CPC Class Codes: G07B 15/06 Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
• CPC Class Codes: H04L 63/1458 Denial of Service

Abstract

A location tracking unit for use with a location based service system is presented. The location tracking unit comprises: a navigation receiver adapted to implement a location tracking function; data processing means adapted to determine an occupied location according to a first location matching process, the first location matching process using navigation data from the navigation receiver and a first set of geographic data; and data processing means adapted to verify the integrity of the first location matching process based on a second location matching process using navigation data and a second set of geographic data.

Claims

1-15. -15. (canceled)

16. A location tracking unit configured for use with a location based service system comprising:

a first data processor configured to determine an occupied location according to a first location matching process, the first location matching process using navigation data from a navigation receiver and a first set of geographic data; and

a second data processor configured to verify integrity of the first location matching process based on a second location matching process using the navigation data and a second set of geographic data.

17. The location tracking unit of claim 16, wherein the first data processor is a host controller and the second data processor is a secure controller.

18. The location tracking unit of claim 16, wherein the second data processor executes the second location matching process as a mirror to the first location matching process undertaken in the first data processor to check whether or not the results of the first and second location matching processes match.

19. The location tracking unit of claim 16, wherein the second data processor is configured to verify the integrity of the first location matching process by verifying the continuity of road sections output by the first location matching process.

20. The location tracking unit of claim 16, wherein the second data processor is configured to verify the integrity of the first location matching process by checking whether or not distances between coordinates of the navigation data and road sections onto which these coordinates are mapped is below a threshold distance.

21. The location tracking unit of claim 20, wherein the distances between spherical coordinates are corrected by applying a corrective proportional factor before computing the distances.

22. The location tracking unit of claim 20, wherein a road section is represented as a straight line joining two distinct locations, wherein a coordinate of the navigation data is considered to be correctly mapped onto a road section if the distance between the coordinate and the straight line representing the road section is below a threshold distance.

23. The location tracking unit of claim 20, wherein a road section is represented as a plurality of splines, and wherein the first data processor is configured to compute a position on a spline that is nearest to the coordinate of the navigation data and forward to the second data processor a parameter value of the spline position;

and the second data processor is configured to compute the position on the spline using the parameter value and verify whether a distance between the coordinate submitted by the navigation receiver and the spline position is below a threshold distance.

24. The location tracking unit of claim 20, wherein a road section is represented as a polygon, wherein a coordinate of the navigation data is considered to be correctly mapped onto a road section if the coordinate is within a polygon surrounding the road section.

25. The location tracking unit of claim 20, wherein a road sections is represented as a series of overlapping circles or ellipses, wherein a coordinate of the navigation data is considered to be correctly mapped onto a road section if the coordinate is inside at least one of the circles or ellipses associated with the road section.

26. The location tracking unit of claim 20, wherein a road section is represented as a series of overlapping squares, rectangles or rhombuses, wherein a coordinate of the navigation data is considered to be correctly mapped onto a road section if the coordinate is inside at least one of the squares, rectangles or rhombuses associated with the road section.

27. The location tracking unit of claim 16, wherein the second data processor is further configured to perform statistics to determine if a mismatch between the first and second location matching processes is due to a fraud attempt or to reception conditions.

28. The location tracking unit of claim 27, wherein the second data processor maintains a trip average percentage of successful verification, which triggers a fraud notification if the percentage is below a threshold value.

29. The location tracking unit of claim 27, wherein the second data processor maintains a moving percentage of successful verifications over a number of submitted verification requests, which triggers a fraud notification if the percentage is below a threshold value.

30. The location tracking unit of claim 16, wherein the second data processor is further configured to verify integrity by using reliability information.

31. The location tracking unit of claim 30, wherein the threshold distance is increased in zones of typically bad reception and decreased in zones of typically good reception.

32. The location tracking unit of claim 30, wherein a reliability factor for each road section will moderate the effect of a failed verification on a success percentage.

33. The location tracking unit of claim 16, wherein the second data processor is further configured to maintain statistics related to signal interruptions, wherein an above threshold interruption causes the second data processor to trigger a fraud notification.

34. The location tracking unit of claim 16, wherein the second data processor is further configured to counter a denial-of-service attack in which an attacker falsely indicates that a coordinate of the navigation data is not on a tolled road section.

35. The location tracking unit of claim 34, wherein the second data processor is configured to verify that a distance between two subsequent navigational coordinates and a delay between two navigational timestamps are both below a maximum value.

36. The location tracking unit of claim 34, wherein the location tracking unit is configured to store a secure database in which all un-tolled zones are covered by toll free zones.

37. The location tracking unit of claim 34, wherein the second data processor is configured to verify that that each navigational coordinate is associated with a tolled zone or a toll-free zone.

38. The location tracking unit of claim 16, further comprising a database configured to store the second set of geographic data inside a secure controller.

39. The location tracking unit of claim 16, further comprising a database configured to store the second set of geographic data according to an encryption algorithm inside a host controller.

40. The location tracking unit of claim 39, wherein the database splits each data record into a pair of insecure and secure parts, wherein the insecure part comprises information used to perform the first location matching process, and the secure part comprises information used to verify the first location matching process.

41. The location tracking unit of claim 39, wherein the first data processor is configured to further provide to the second data processor signed verification parameters, and the second data processor is configured to first verify the validity of the signature on each verification parameter before using the verification parameters to verify the first location matching process.

42. A method of implementing a location tracking function in a location tracking unit, the method comprising:

determining, in a first data processor of the location tracking unit, an occupied location according to a first location matching process, the first location matching process using navigation data from a navigation receiver and a first set of geographic data; and

verifying, in a second data processor of the location tracking unit, integrity of the first location matching process based on a second location matching process using the navigation data and a second set of geographic data.