IP Library Granted Patent US 12,566,077
Granted Patent B2
US 12,566,077 · App. 18/147,572 · Granted Mar 3, 2026

Method and apparatus for device probe point data object determinations and validations

Inventors: Swetha Bose Nutakki (Khajaguda, IN); Nandhi Prabhu Mohan (Naperville, IL); Corinne Bradley (Chicago, IL); Arnold Sheynman (Northbrook, IL)
Assignee: HERE GLOBAL B.V.
G01C21/3841G08G1/01
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,566,077
App. No.
18/147,572
Granted
Mar 3, 2026
Kind
B2
Abstract

A method, apparatus and computer program product are provided to determine one or more probe point data objects and/or validate one or more probe point data objects for use with determination of traffic conditions. A determined probe point data object may be determined and/or updated with one or more probe point data objects which exclude any probe point data objects determined to correspond to an off-road location. A validated probe point data object may additionally or alternatively be determined using one or more first validation sequence check operations and using one or more second validation sequence check operations. The determined probe point data object and/or validated probe point data object may be used to determine one or more traffic conditions, and as a result, traffic condition determinations may be determined more accurately and efficiently.

Claims (54)

1 . A method for probe point validation, the method comprising:

receiving, from a mobile device, two or more sequential probe point data objects corresponding to a unique device identifier, wherein the mobile device comprises a mobile phone, an in-vehicle navigation system, or an advanced driving assistance system (ADAS);

determining whether the two or more sequential probe point data objects are valid based on one or more first validation sequence check operations;

responsive to determining that the two or more sequential probe point data objects are valid based on the one or more first validation sequence check operations, determining whether the two or more sequential probe point data objects are valid based on one or more second validation sequence check operations;

responsive to determining that the two or more sequential probe point data objects are valid based on the one or more second validation sequence check operations, generating a validated probe point set data object comprising the two or more sequential probe point data objects;

determining one or more traffic conditions for one or more road segments based at least in part on the validated probe point set data object; and

using, by a computing entity, the one or more traffic conditions that are determined for at least one of a determination of a navigational route, an estimation of a time of arrival or event planning for a road segment,

wherein the one or more first validation sequence check operations and the one or more second validation sequence check operations are configured to determine whether a quality of the two or more sequential probe point data objects will affect the accuracy of determining the one or more traffic conditions for the one or more road segments.

2 . The method of claim 1 , wherein:

the two or more sequential probe point data objects are not validated by the one or more first validation sequence check operations in an instance the two or more sequential probe point data objects comprise the same timestamp.

3 . The method of claim 1 , wherein the two or more sequential probe point data objects are not validated by the first validation sequence check operation in an instance the two or more sequential probe point data objects comprise the same set of coordinates.

4 . The method of claim 1 , wherein the two or more sequential probe point data objects are not validated by the first validation sequence check operation in an instance the two or more sequential probe point data objects comprise zero value speeds.

5 . The method of claim 1 , the method further comprising determining an absolute device speed difference for each of the two or more sequential probe point data objects based at least in part on corresponding device speeds for the two or more sequential probe point data objects.

6 . The method of claim 5 , wherein the two or more sequential probe point data objects are not validated by the second validation sequence check operation in an instance the absolute device speed difference fails to satisfy one or more device speed difference threshold values.

7 . The method of claim 5 , the method further comprising:

determining an estimated device speed based at least in part on the set of coordinates for the two or more sequential probe point data objects; and

determining an estimated device speed difference based at least in part on the absolute device speed and the estimated device speed.

8 . The method of claim 7 , wherein the two or more sequential probe point data objects are not validated by the second validation sequence check operation in an instance the estimated device speed difference fails to satisfy one or more estimated device speed difference threshold values.

9 . The method of claim 1 , wherein each probe point data object comprises one or more of a timestamp at which the probe point data object was generated by the device, a set of coordinates, a device speed, and a device heading value.

10 . The method of claim 1 , wherein the one or more first validation sequence check operations comprise:

determining whether the two or more sequential probe point data objects are associated with a same timestamp value,

determining whether the two or more sequential probe point data objects comprise a same set of coordinates, or

determining whether the two or more sequential probe point data objects comprise a zero value for device speed.

11 . The method of claim 1 , wherein the one or more second validation sequence check operations comprise:

determining an absolute device speed difference for respective ones of the two or more sequential probe point data objects based at least in part on corresponding device speeds for the two or more sequential probe point data objects, and

determining whether the absolute device speed difference satisfies one or more device speed difference threshold values.

12 . An apparatus comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:

receive, from a mobile device, two or more sequential probe point data objects corresponding to a unique device identifier, wherein the mobile device comprises a mobile phone, an in-vehicle navigation system, or an advanced driving assistance system (ADAS);

determine whether the two or more sequential probe point data objects are valid based on one or more first validation sequence check operations;

responsive to determining that the two or more sequential probe point data objects are valid based on the one or more first validation sequence check operations, determine whether the two or more sequential probe point data objects are valid based on one or more second validation sequence check operations;

responsive to determining that the two or more sequential probe point data objects are valid based on the one or more second validation sequence check operations, generate a validated probe point set data object comprising the two or more sequential probe point data objects;

determine one or more traffic conditions for one or more road segments based at least in part on the validated probe point set data object; and

use, by a computing entity, the one or more traffic conditions that are determined for at least one of a determination of a navigational route, an estimation of a time of arrival or event planning for a road segment,

wherein the one or more first validation sequence check operations and the one or more second validation sequence check operations are configured to determine whether a quality of the two or more sequential probe point data objects will affect the accuracy of determining the one or more traffic conditions for the one or more road segments.

13 . The apparatus of claim 12 , wherein the two or more sequential probe point data objects are not validated by the first validation sequence check operation in an instance the two or more sequential probe point data objects comprise the same set of coordinates.

14 . The apparatus of claim 12 , wherein the two or more sequential probe point data objects are not validated by the first validation sequence check operation in an instance the two or more sequential probe point data objects comprise zero value speeds.

15 . The apparatus of claim 12 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to determine an absolute device speed difference for each of the two or more sequential probe point data objects based at least in part on corresponding device speeds for the two or more sequential probe point data objects.

16 . The apparatus of claim 15 , wherein the two or more sequential probe point data objects are not validated by the second validation sequence check operation in an instance the absolute device speed difference fails to satisfy one or more device speed difference threshold values.

17 . The apparatus of claim 12 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:

determine an estimated device speed based at least in part on the set of coordinates for the two or more sequential probe point data objects; and

determine an estimated device speed difference based at least in part on the absolute device speed and the estimated device speed.

18 . The apparatus of claim 17 , wherein the two or more sequential probe point data objects are not validated by the second validation sequence check operation in an instance the estimated device speed difference fails to satisfy one or more estimated device speed difference threshold values.

19 . The apparatus of claim 12 , wherein each probe point data object comprises one or more of a timestamp at which the probe point data object was generated by the device, a set of coordinates, a device speed, or a device heading value.

20 . A computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code portions stored therein, the computer-executable program code portions comprising program code instructions configured to:

receive, from a mobile device, two or more sequential probe point data objects corresponding to a unique device identifier, wherein the mobile device comprises a mobile phone, an in-vehicle navigation system, or an advanced driving assistance system (ADAS);

determine whether the two or more sequential probe point data objects are valid based on one or more first validation sequence check operations;

responsive to determining that the two or more sequential probe point data objects are valid based on the one or more first validation sequence check operations, determine whether the two or more sequential probe point data objects are valid based on one or more second validation sequence check operations;

responsive to determining that the two or more sequential probe point data objects are valid based on the one or more second validation sequence check operations, generate a validated probe point set data object comprising the two or more sequential probe point data objects;

determine one or more traffic conditions for one or more road segments based at least in part on the validated probe point set data object; and

use, by a computing entity, the one or more traffic conditions that are determined for at least one of a determination of a navigational route, an estimation of a time of arrival or event planning for a road segment,

wherein the one or more first validation sequence check operations and the one or more second validation sequence check operations are configured to determine whether a quality of the two or more sequential probe point data objects will affect the accuracy of determining the one or more traffic conditions for the one or more road segments.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2022
From: NUTAKKI, SWETHA BOSE; MOHAN, NANDHI PRABHU; BRADLEY, CORINNE; SHEYNMAN, ARNOLD
To: HERE GLOBAL B.V.
Reel/Frame 062228/0218 →
Priority Claims (1)
IN 202111061612 · Dec 29, 2021 · national
Continuity (1)
Related Publication 20230204382A1 · Jun 29, 2023
References Cited (60)
US 6760770B1 · Kageyama · 2004 [cited by examiner]
US 8217777B2 · Sekiyama · 2012 [cited by examiner]
US 8284995B2 · Diaz et al. · 2012 [cited by applicant]
US 10397089B2 · Dorum · 2019 [cited by examiner]
US 10515542B2 · Littlejohn · 2019 [cited by applicant]
US 10838954B1 · Santos · 2020 [cited by examiner]
US 10983877B1 · Hoffman · 2021 [cited by examiner]
US 10996061B2 · Stajner et al. · 2021 [cited by applicant]
US 12174032B2 · Fowe · 2024 [cited by examiner]
US 12184528B2 · Chowdhury · 2024 [cited by examiner]
US 20110072002A1 · Kirkby et al. · 2011 [cited by applicant]
US 20110112760A1 · Serbanescu · 2011 [cited by examiner]
US 20110137907A1 · Ikenoue · 2011 [cited by examiner]
US 20120004845A1 · Kmiecik et al. · 2012 [cited by applicant]
US 20140005940A1 · Suzuki · 2014 [cited by examiner]
US 20140372022A1 · Witmer · 2014 [cited by applicant]
US 20150006069A1 · Kwon et al. · 2015 [cited by applicant]
US 20150018011A1 · Mendelson · 2015 [cited by examiner]
US 20150160020A1 · van Hemert · 2015 [cited by examiner]
US 20150300837A1 · Hisano · 2015 [cited by examiner]
US 20160021093A1 · Vinckier · 2016 [cited by applicant]
US 20160148429A1 · Groppa · 2016 [cited by examiner]
US 20160284212A1 · Tatourian et al. · 2016 [cited by applicant]
US 20160379485A1 · Anastassov · 2016 [cited by examiner]
US 20170314934A1 · Averbuch · 2017 [cited by examiner]
US 20180066957A1 · Stroila · 2018 [cited by examiner]
US 20180121483A1 · Giurgiu et al. · 2018 [cited by applicant]
US 20180143998A1 · Prahladka · 2018 [cited by examiner]
US 20180158369A1 · Al Darwesh · 2018 [cited by examiner]
US 20180173222A1 · Tseng · 2018 [cited by examiner]
US 20180276988A1 · Littlejohn · 2018 [cited by applicant]
US 20180299272A1 · Salowitz · 2018 [cited by examiner]
US 20190170530A1 · Martyniv · 2019 [cited by examiner]
US 20190235251A1 · Amano · 2019 [cited by examiner]
US 20190310100A1 · Yang · 2019 [cited by applicant]
US 20190313210A1 · Ohkawa · 2019 [cited by examiner]
US 20200326201A1 · Nara · 2020 [cited by examiner]
US 20210020034A1 · Lorenz · 2021 [cited by examiner]
US 20210082285A1 · Bieger · 2021 [cited by examiner]
US 20210095971A1 · Mao et al. · 2021 [cited by applicant]
US 20210180985A1 · Yokota et al. · 2021 [cited by applicant]
US 20210370933A1 · Zhang · 2021 [cited by examiner]
US 20220057216A1 · Zhang · 2022 [cited by examiner]
US 20220078171A1 · Borak · 2022 [cited by examiner]
US 20220130054A1 · Okano · 2022 [cited by examiner]
US 20220180099A1 · Yadav · 2022 [cited by examiner]
US 20220182412A1 · Borak · 2022 [cited by examiner]
US 20220246028A1 · White · 2022 [cited by examiner]
US 20220290995A1 · Zhang · 2022 [cited by examiner]
US 20220358400A1 · Zheng · 2022 [cited by examiner]
US 20220417718A1 · Yoshida · 2022 [cited by examiner]
US 20230204381A1 · Nutakki et al. · 2023 [cited by applicant]
US 20230221136A1 · Rodrigues · 2023 [cited by examiner]
US 20230229457A1 · Chivukula · 2023 [cited by examiner]
US 20230304819A1 · Nishijima · 2023 [cited by examiner]
CN 111653091A · 2020 [cited by examiner]
JP 6672077B2 · 2020 [cited by applicant]
Examination Report for Indian Application No. 202111061612 dated Mar. 18, 2024, 6 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 18/147,538 dated Jan. 14, 2025. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/147,538 dated Aug. 4, 2025. [cited by applicant]