Program, non-transitory computer-readable storage medium, and device

The dynamic location tracking system addresses ETA inaccuracies by adjusting location data sharing frequency based on proximity to dead zones and directional ambiguity, ensuring accurate arrival predictions while conserving resources.

JP7584469B2Active Publication Date: 2024-11-15RAKUTEN GROUP INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2022081710
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-05-24
Filing Date
2022-05-18
Publication Date
2024-11-15
Estimated Expiration
2042-05-18

AI Technical Summary

Technical Problem

Determining an accurate estimated time of arrival (ETA) is challenging when mobile devices pass through geographic areas with wireless communication loss (dead zones) and have insufficient location data to determine heading, leading to inaccurate route predictions.

Method used

A dynamic location tracking system that adjusts the frequency of location data sharing based on proximity to dead zones and directional ambiguity, using triggers to increase sampling rates when necessary to conserve power and resources.

Benefits of technology

The system accurately estimates arrival times by minimizing power consumption and reducing complexity, even in areas with communication loss or directional uncertainty.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584469000001
    Figure 0007584469000001
  • Figure 0007584469000002
    Figure 0007584469000002
  • Figure 0007584469000003
    Figure 0007584469000003
Patent Text Reader

Abstract

To provide a device sharing location data by increasing spacing when it is determined to move within a reference distance toward a geographical area having a history of wireless communication loss or to the geographical area.SOLUTION: Exemplary methods, apparatuses, and systems read location data representing a current location of a mobile device. The location data for the mobile device is taken at a first sampling rate. Upon determining that the location data indicates that the mobile device is approaching a geographic area having a history of wireless communication loss, the mobile device is triggered to increase location data sampling from the first sampling rate to a second sampling rate.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates generally to tracking the location of a device, and more particularly to a device that shares location data at increasing intervals when determined to be moving toward or within a reference distance of a geographic area where wireless communication loss has occurred in the past. Additionally, the present disclosure relates to a device that shares location data at increasing intervals when current location data is insufficient to determine a heading direction. [Background technology]

[0002] Services involving delivery and pickup of people or goods can provide users with information about expected and / or impending arrivals through location tracking. For example, a mobile device can transmit location data to another device to facilitate tracking of the expected arrival of a person or goods.

[0003] The present disclosure will become more fully understood from the following detailed description and the accompanying drawings of various embodiments of the present disclosure, which are for purposes of illustration and understanding only and should not be construed as limiting the disclosure to specific embodiments. [Brief description of the drawings]

[0004] [Figure 1] 1 illustrates an example of a dynamic location tracking system in block diagram form. [Diagram 2] An example is provided for triggering dynamic tracking of a user device based on geographic areas that have previously experienced wireless communication loss. [Diagram 3] 1 is a flow chart illustrating an example method for estimating arrival by dynamically tracking a user device over a geographic area that has previously experienced wireless communication loss. [Figure 4] An example is shown of triggering dynamic tracking of a user device when current location data is insufficient to determine heading. [Diagram 5]1 is a flow chart illustrating an example method for estimating arrival by dynamic tracking of a user device when current location data is insufficient to determine heading. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] Aspects of the present disclosure relate to tracking location data and determining an estimated time of arrival (ETA). For example, services involving delivery and pickup of people or goods rely on location tracking to provide users with an indication of an estimated and / or imminent arrival. Mobile devices, such as mobile phones, can send location data to a server to facilitate tracking of the expected arrival of a person or thing. However, determining the estimated time of arrival can be difficult when the mobile device passes through a geographic area that has experienced wireless communication loss (a "dead zone") that prevents the mobile device from sending location data to a server.

[0006] Additionally, determining an estimated time of arrival can be complicated by insufficient location data to indicate a direction of travel. For example, a mobile device may not be traveling on the most direct route to the location for which the system is attempting to estimate a time of arrival. Detours, intermediate destinations, or other deviations from the most direct route can significantly change the expected arrival or imminent arrival prediction. Thus, when location data is insufficient to determine if a mobile device is traveling in a particular direction, it is difficult to obtain an accurate estimated time of arrival.

[0007] The embodiments described herein address the above-mentioned problems and others by tracking location data at a dynamic frequency based on the location of the mobile device in relation to blind zones or directional ambiguity. For example, the host system receives location data at a limited interval by default to minimize power usage and / or processing resources. The host system sends one or more messages to the mobile device to trigger an increase in the rate at which the mobile device shares location data with the host system. For example, the mobile device is triggered to send location data more frequently when the mobile device is within a reference distance to a blind zone or when the mobile device's current location data is insufficient to determine the mobile device's heading. As a result, the system can minimize tracking of the user device's location to conserve user device power when a relatively low location sharing frequency is sufficient, and increase the rate at which the mobile device shares location data when navigating blind zones with reduced complexity and / or directional ambiguity.

[0008] 1 illustrates an example dynamic location tracking system 100 in block diagram form. The dynamic location tracking system includes a mobile device 105, a host system 110, and a third party device 115 connected to one or more networks 120. For example, the mobile device 105 sends location data to the host system 110 at a dynamic frequency. The host system 110 sends one or more messages to the mobile device 105 to trigger a change in the frequency at which the mobile device 105 sends location data. The host system 110 also provides an estimate of the arrival of the mobile device 105 to the third party device 115.

[0009] The mobile device 105 includes a processor 125 coupled to a memory 130. As used herein, "coupled to" or "coupled with" generally refers to a connection between components, which may be electrical, optical, magnetic, etc., and may be an indirect communication connection or a direct communication connection (e.g., with no intervening components), whether wired or wireless. The mobile device 105 uses the processor 125 and memory 130 to perform one or more processes involved in the dynamic location tracking described herein.

[0010] Processor 125 represents one or more general-purpose processing devices, such as a microprocessor, a central processing unit, and the like. More specifically, processor 125 is a processing device that may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or a combination of instruction sets. Processor 125 may also be one or more special-purpose processing devices, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, and the like. Processor 125 is configured to execute instructions to perform the operations discussed herein.

[0011] Memory 130 may include non-volatile memory, volatile memory, or a combination thereof. Memory 130 is an example of a machine-readable storage medium (also known as a computer-readable storage medium) on which one or more sets of instructions or software embodying any one or more of the methodologies or functions described herein are stored. For example, location data controller 135 may be implemented as a set of instructions or a set of software that manages dynamic location tracking, as described in more detail below. In one embodiment, location data controller 135 updates the sampling rate of location data (e.g., the rate at which mobile device 105 sends location data to host system 110) in response to one or more triggers, as described below. Additionally, memory 130 may store trigger messages and / or data received from host system 110 (e.g., location data sampling rate, location of dead zone, location of dead zone threshold, reference distance from dead zone, etc.).

[0012] The mobile device 105 determines its location using a geographic location receiver 140 (e.g., a Global Positioning System (GPS)), Assisted GPS (A-GPS), cellular tower data (e.g., nearest tower, triangulation, etc.), wireless network data (e.g., a list of known Wi-Fi network connections in a geographic region), or a combination thereof. For example, the mobile device 105 may determine that it is within or outside a reference distance to a blind zone, a location of directional ambiguity, or a pick-up location, drop-off location, based on latitude and longitude values ​​determined by the geographic location receiver 140 and / or latitude and longitude values ​​associated with wireless network signals received by the mobile device 105.

[0013] The mobile device 105 may include additional components not shown, such as a network interface device for communicating over the network 120. For example, the mobile device may include one or more wireless transceivers, such as a Wi-Fi transceiver, a Bluetooth transceiver, a wireless cellular transceiver (e.g., 3G, 4G, 5G, etc.), or another radio protocol transceiver for connecting the mobile device 105 to another device, external component, or network and receiving instructions, data, etc. Additionally, one or more buses may be used to interconnect the various components of the mobile device 105.

[0014] Host system 110 includes a processor 145 coupled to a memory 150. Similar to the description of processor 125 above, processor 145 represents one or more general-purpose processing devices, such as a microprocessor, a central processing unit, etc. Additionally, memory 150 may include non-volatile memory, volatile memory, or a combination thereof.

[0015] Memory 150 is another example of a computer-readable storage medium on which one or more sets of instructions or software embodying any one or more of the methodologies or functions described herein are stored. For example, arrival prediction engine 155 and blind zone tracker 160 can each be implemented as a set of instructions or a set of software that manages dynamic location tracking and arrival estimation of mobile device 105, as described in more detail below.

[0016] The arrival prediction engine 155 determines an estimated arrival time for the mobile device 105 to reach the destination. For example, the arrival prediction engine 155 may determine (or estimate) the route that the mobile device 105 will travel to reach the destination, the distance along the route, the speed limits along the route, the traffic patterns along the route, etc. to estimate the arrival time. In one embodiment, the arrival prediction engine reads or uses data of the history of previous trips made by the mobile device stored in the trip history database 165 to determine, for example, the most likely route, traffic patterns, etc. In one embodiment, the arrival prediction engine 155 sends one or more messages to the mobile device 105 to trigger the mobile device 105 (to change settings on the mobile device 105) to share location data more or less frequently, as described in more detail below.

[0017] The dead zone tracker 160 determines geographical areas where there has been a past wireless communication loss. For example, the dead zone tracker 160 may create a heat map of the locations shared with the host 110 and determine that "cold" spots on the heat map (locations on the map that have not received a threshold amount of location data) correspond to areas where there has been a past wireless communication loss. In one embodiment, the dead zone tracker 160 considers cold spots that coincide with a path (e.g., roads, highways, railroads, etc.) taken by a mobile device to be areas where there has been a past wireless communication loss.

[0018] In another embodiment, the blind zone tracker 160 uses the movement history database 165 to detect when location data was expected but not received based on the frequency of location data sharing by the mobile device. In one embodiment, the arrival prediction engine 155 creates a logged movement history database 165 of shared locations received with a timestamp and / or timestamps of when location data was expected but not received. The blind zone tracker 160 can estimate the location or area where location data was expected but not received based on the frequency with which location data was shared along the route before and after the "missed" location and the locations before and after the missed location. In one embodiment, the blind zone tracker 160 associates missed locations of different movements in the movement history database 165. For example, the blind zone tracker 160 can group different missed locations into a single geographical area or blind zone if they are within a reference distance of each other. When the number of missed locations in a geographical area reaches a reference number, the blind zone tracker 160 designates the area as a blind zone. In one embodiment, the blind zone tracker 160 further uses traffic patterns, speed limits, and other data along the route to estimate the location or extent of the blind zones. The blind zone tracker 160 stores the defined blind zones, for example, in the travel history database 165.

[0019] Additionally, the blind zone tracker 160 can use the movement history database 165 to detect when a location or a location's ETA is inconsistent with the respective location or ETA of one or more other locations in the movement. For example, if a location or a location's ETA changes at a rate equal to or greater than a criterion (amount of change or rate of change), the blind zone tracker 160 can determine that the shared location data is incorrect. Inaccurate location data can be the result of, for example, urban canyons or other physical factors that may cause poor reception of GPS signals. In one embodiment, the blind zone tracker 160 designates areas associated with inaccurate or otherwise unreliable location data as blind zones as well.

[0020] The host system 110 may also include additional components not shown, such as a network interface device for communicating over the network 120, and one or more APIs that enable communication between the mobile devices 105 and the host system 110 and / or between the third party devices 115 and the host system 110. Additionally, one or more buses may be used to interconnect the various components of the host system 110.

[0021] The third party device 115 includes a processor 170 coupled to a memory 175. Similar to the description of the processor 125 above, the processor 170 represents one or more general-purpose processing devices, such as a microprocessor, a central processing unit, etc. Additionally, the memory 175 may include non-volatile memory, volatile memory, or a combination thereof.

[0022] Memory 175 is another example of a computer readable storage medium on which one or more sets of instructions or software embodying any one or more of the methodologies or functions described herein are stored. For example, arrival alert application 180 can be implemented as a set of instructions or software for receiving messages from host system 110 regarding an estimated arrival of mobile device 105. In one embodiment, arrival alert application 180 uses the messages from host system 110 to generate an imminent arrival alert of mobile device 105 at a destination.

[0023] Similar to the mobile device 105 and the host system 110, the third party device 115 may also include additional components not shown, such as a network interface device for communicating over the network 120, another bus, etc.

[0024] In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the present embodiments, and thus the techniques are not limited to any specific combination of hardware circuitry and software or to any particular source for the instructions executed by processor 125, processor 145, and / or processor 170.

[0025] FIG. 2 illustrates an example of triggering dynamic tracking of a user device based on geographical areas where there has been wireless communication loss in the past. In this example, the mobile device 105 is in or part of an automobile traveling along a route 205 to a destination 210. In one embodiment, the arrival prediction engine 155 uses input from the mobile device 105 and / or the third party device 115 to determine the location of the destination 210. For example, the arrival prediction engine 155 uses an input address or latitude and longitude where the mobile device 105 will pick up or drop off someone or something. In one embodiment, the third party device 115 is placed at the destination 210, and the third party device 115 uses a geographic location receiver to determine and share the location of the destination 210. The arrival prediction engine 155 can further use the location data shared by the mobile device 105 to determine the route 205 between the mobile device 105 and the destination 210.

[0026] As described above, the blind zone tracker 160 determines and stores geographical areas that have previously experienced wireless communication loss. In this example, the blind zone tracker 160 detects and stores a blind zone 215. Additionally, the arrival prediction engine 155 determines that the route 205 passes through the blind zone 215. For example, when determining the route 205, the arrival prediction engine 155 may detect whether any location along the route 205 is within a blind zone determined and stored by the blind zone tracker 160.

[0027] In one embodiment, the host system 110 sets a reference distance around the blind zone to act as a trigger for dynamic tracking of the user device. For example, the blind zone threshold 220 represents an area around the blind zone 215 where the sampling rate of the location data of the mobile device 105 is increased. In one embodiment, the host system 110 sends a message to the mobile device 105 to trigger an increase in the sampling rate of the location data. For example, in response to the arrival prediction engine 155 determining that the route 205 passes through the blind zone 215, the host system 110 can request an increase in the location data sampling rate when it receives location data indicating that the mobile device 105 is within the blind zone threshold 220, or the host system 110 can send the blind zone threshold 220 data to the mobile device 105, and the mobile device 105 can detect when it is within the blind zone threshold 220 and trigger the increase. In one embodiment, the arrival prediction engine 155 uses traffic patterns, speed limits, and other data from the movement history database 165 along or similar to the route 205 to determine the size and / or location of the dead zone threshold. For example, the arrival prediction engine 155 may set a larger threshold for routes with faster traffic speeds, such as freeways, and a smaller threshold for routes with slower traffic speeds, such as residential roads. As a result, the threshold provides sufficient distance to trigger increased location sampling before the mobile device enters the dead zone, while avoiding premature increases that could lead to oversampling of the location data and corresponding resource drain (e.g., battery life) of the mobile device.

[0028] Although the dead zone threshold 220 is shown as a circle, other boundaries may be used to facilitate triggering a change in the dynamic tracking of the mobile device 105. For example, the dead zone threshold 220 may be implemented as a combination of boundary roads, or any shape defined by latitude and longitude points.

[0029] In one embodiment, the mobile device 105 does not attempt to transmit location data to the host system 110 when it has no or poor connectivity to a cellular or other data network (e.g., within a dead zone 215). The mobile device 105 may obtain location data, for example, via a GPS signal, but may not communicate the location data efficiently (or at all) with the host system 110. Attempting to transmit location data in such a situation may unnecessarily drain the battery life of the mobile device 105. Thus, the mobile device may use a minimum network connectivity criterion (e.g., based on a signal strength value and / or communication protocol) as a trigger for sharing location data with the host system 110. For example, an increased sampling rate of the location data may cause the mobile device 105 to test data connectivity more frequently to determine if the network connection signal strength is weak or an older generation protocol (e.g., third generation or 3G). If the mobile device 105 determines that the network connection is poor or disconnected, the mobile device 105 does not attempt to transmit location data and waits to retry as dictated by the current sampling rate.

[0030] 3 is a flow chart illustrating an example method 300 of estimating arrival by dynamic tracking of user devices having geographical areas that have had historical wireless communication loss. Method 300 may be performed by processing logic that may include hardware (e.g., a processing device, circuitry, dedicated logic, programmable logic, microcode, device hardware, integrated circuits, etc.), software (e.g., instructions operating or executed on a processing device), or a combination thereof. In some embodiments, method 300 is performed by location data controller 135, arrival prediction engine 155, or a combination thereof. For purposes of illustrating the example, method 300 is described below as being performed by a processing device.

[0031] At step 305, the processing device sets location data sampling to a first rate. The first location data sampling rate can be set to conserve resources until triggered to sample more frequently. The mobile device 105 can share location data periodically and / or based on changes in location. In one embodiment, the mobile device 105 reads or otherwise obtains data indicative of the mobile device 105's current location (e.g., GPS coordinates) at a first rate and shares updated location information less frequently at intervals of one minute or more (e.g., five minutes) or when the mobile device 105's location has changed by a significant amount (e.g., 500 meters). As described above, the mobile device 105 will not attempt to transmit location data to the host system 110 if the mobile device 105's network connectivity does not meet criteria (e.g., signal strength and / or generation protocol).

[0032] In one embodiment, the host system 110 sends one or more messages including a reference distance from the location to the mobile device 105 to trigger a change in the dynamic location data sampling rate. For example, the host system 110 can send the latitude and longitude values ​​of the destination 210 and a reference distance to be used (e.g., as a radius) from the latitude and longitude values ​​as a reference distance from the destination 210. When outside the destination threshold, the mobile device 105 can use a less frequent sampling rate (e.g., a first rate) and when within the destination threshold, increase sampling to a more frequent rate (e.g., a second rate). For example, the reference distance from the destination 210 can be about 800 meters.

[0033] Additionally, the host system 110 can transmit latitude and longitude values ​​of the blind zone 215, or a reference distance from an equivalent location (e.g., blind zone threshold 220) that are used to trigger dynamic changes in the sampling rate, as described below. In some embodiments, the host system 110 receives location data from the mobile device 105 and transmits instructions to change the sampling rate in response to the host system 110 detecting that the mobile device 105 has crossed or otherwise met a threshold.

[0034] In one embodiment, the reference distance(s) is / are dependent on the density of businesses, residences, and / or locations proximate to the destination 210 and / or blind zone 215. A smaller reference distance may be more appropriate for denser areas as a result of the user being more likely to be near the destination 210 and / or blind zone 215 other than following or completing the route 205. As a result of using a smaller reference distance(s), users in denser areas may still be afforded some privacy in their location data and may conserve processing and battery resources when location tracking is less useful.

[0035] In step 310, the processing device determines whether the location data indicates that the mobile device is approaching a blind zone. In one embodiment, the mobile device 105 determines its location (e.g., using the geographic location receiver 140) and compares the determined location to the blind zone threshold 220. In another embodiment, the host system 110 determines the location data received from the mobile device 105 and compares the location to the blind zone threshold 220. If the location data indicates that the mobile device is not currently approaching a blind zone (e.g., the location of the mobile device 105 remains outside the blind zone threshold 220), the method 300 proceeds to step 315. If the location data indicates that the mobile device is approaching a blind zone (e.g., the location of the mobile device 105 is within the blind zone threshold 220), the method 300 proceeds to step 323.

[0036] At step 315, the processing device determines whether another trigger has occurred to change the sampling rate of the location data. For example, the processing device compares the location data to another criterion (e.g., a reference distance from the destination 210). Similar to step 310, the mobile device 105 or the host system 110 may compare the location data to one or more criteria. If another trigger has occurred (e.g., the location of the mobile device 105 is within a threshold of the destination 210), the method 300 proceeds to step 320. If another trigger has not occurred, the method 300 returns to step 310 and the mobile device 105 continues to sample and share the location data less frequently (at the first rate).

[0037] At step 320, the processing device updates the sampling rate of the location data in response to other triggers. For example, if the location data indicates that the mobile device 105 is within a destination threshold, the mobile device 105 updates the data sampling rate and transmits the location data to the host system 110 more frequently (e.g., at a second rate).

[0038] In one embodiment, the third party device 115 uses the location data to determine when the mobile device 105 is approaching the destination 210. For example, the destination criteria (or another criterion) can trigger the host system 110 to share location data from the mobile device 105 with the third party device 115 or otherwise notify the third party device 115 that the mobile device 105 is approaching the destination 210.

[0039] In step 323, the processing device determines whether the location data indicates that the ETA for the mobile device to arrive at the destination meets the time criteria. For example, the arrival prediction engine 155 can use one or more of the current speed along or similar to the route 205, traffic patterns, speed limits, and other data from the travel history database 165 to calculate a current ETA for the mobile device to reach the destination 210. If the current ETA exceeds the reference time value, the processing device can determine that the ETA does not meet the time criteria, the sampling rate is not updated to compensate for the blind zone, and the method 300 returns to step 310. If the current ETA is less than or equal to the reference time value, the processing device can determine that the ETA meets the time criteria, and the method 300 proceeds to step 325.

[0040] In step 325, the processing device updates the sampling rate of the location data in response to determining that the location data indicates that the mobile device is approaching a blind zone. For example, if the location data indicates that the mobile device 105 is within the blind zone threshold 220, the mobile device 105 updates the sampling rate of the location data and transmits the location data to the host system 110 more frequently (e.g., at the second rate). In one embodiment, the mobile device 105 updates the sampling rate of the location data in response to detecting that its location data indicates that it is approaching a blind zone. In another embodiment, the mobile device 105 updates the sampling rate of the location data when the host system 110 detects that the location data from the mobile device 105 indicates that the mobile device 105 is approaching a blind zone and the host system 110 instructs the mobile device 105 to increase the sampling rate of the location data. In one embodiment, the mobile device 105 uses the second rate to share updated location information more frequently than once a second (e.g., every second) and / or based on a detectable change in the location of the mobile device 105. As a result, the host system 110 can compensate for loss of communication within the dead zone 215, more accurately estimate the time the mobile device 105 will arrive at the destination 210, and / or determine whether the mobile device 105 is proceeding along the route 205 or detouring. Again, as described above, if the network connectivity of the mobile device 105 does not meet the criteria (e.g., signal strength and / or generating protocol), the mobile device 105 will not attempt to transmit location data to the host system 110.

[0041] In step 330, the processing device determines whether the location data indicates that the mobile device is leaving the blind zone. In one embodiment, the mobile device 105 determines its location (e.g., using the geographic location receiver 140) and compares the determined location to the blind zone threshold 220. In another embodiment, the host system 110 determines the location data received from the mobile device 105 and compares the location to the blind zone threshold 220. If the location data indicates that the mobile device is not currently leaving the blind zone (e.g., the location of the mobile device 105 remains within the blind zone threshold 220), the method 300 proceeds to step 340. If the location data indicates that the mobile device is leaving the blind zone (e.g., the location of the mobile device 105 is outside the blind zone threshold 220), the method 300 proceeds to step 335.

[0042] In step 335, the processing device updates the sampling rate of the location data in response to determining that the location data indicates that the mobile device is leaving the blind zone. For example, if the location data indicates that the mobile device 105 is outside the blind zone threshold 220, the mobile device 105 updates the sampling rate of the location data and sends the location data less frequently (e.g., at a first rate) to the host system 110. In one embodiment, the mobile device 105 updates the sampling rate of the location data in response to detecting that its location data indicates leaving the blind zone. In another embodiment, the mobile device 105 updates the sampling rate of the location data in response to the host system 110 detecting that the location data from the mobile device 105 indicates that the mobile device 105 is leaving the blind zone and the host system 110 instructs the mobile device 105 to reduce the sampling rate of the location data.

[0043] In response to determining at step 340 that the location data indicates that the mobile device is not currently leaving the dead zone, the processing device determines whether the location data indicates that the mobile device is stationary. For example, if a reference number of location data samples indicates that the mobile device 105 has not moved beyond a tolerance or other reference distance from a previous position, the mobile device 105 may consider itself stationary. In another embodiment, the mobile device 105 may use another input, such as an accelerometer, to determine whether it is stationary. If the processing device determines whether the location data indicates that the mobile device is stationary, the method 300 proceeds to step 345. If the processing device determines whether the location data does not indicate that the mobile device is stationary, the method 300 returns to step 330. In another embodiment, the method 300 omits steps 340-355 and returns to step 330 when the location data indicates that the mobile device is not currently leaving the dead zone.

[0044] In response to detecting that the mobile device is stationary, the processing device reduces the sampling rate of the location data or the rate at which it attempts to transmit location data to the host server, at step 345. For example, if the user of the mobile device 105 stops at a location within the blind zone 215, the mobile device 105 may conserve processing resources by reporting its stationary location to the host system 110 less frequently, or simply not reporting or attempting to report it.

[0045] In step 350, the processing device determines whether the location data indicates that the mobile device remains stationary. For example, the mobile device 105 can continue sampling the location data (while minimizing or without reporting the location data to the host system 110), or the mobile device 105 can sample the location data in response to a detected change in location detected based on another component, such as an accelerometer. If the processing device determines whether the location data indicates that the mobile device is still stationary, the method 300 returns to step 350 and continues to wait until the mobile device begins to move again. If the processing device determines whether the location data does not indicate that the mobile device is stationary, the method 300 proceeds to step 355.

[0046] In response to detecting that the mobile device is no longer stationary at step 355, the processing device triggers an increase in the sampling rate back to the increased rate (e.g., the second sampling rate). The method 300 returns to step 330 to detect when or if the mobile device has left the blind zone.

[0047] FIG. 4 illustrates an example of triggering dynamic tracking of a user device when current location data is insufficient to determine a heading direction. Similar to the description of FIG. 2, the arrival prediction engine 155 uses the input address or latitude and longitude. One or more mobile devices pick up or drop off someone or something at the destination, respectively. The arrival prediction engine 155 can use the location data shared by each mobile device to determine a route between the mobile device and its destination and determine the ETA of the mobile device to the destination. However, the mobile device A410 is inside or part of a car that has entered the intersection of two roads. While the arrival prediction engine 155 can determine the shortest, recommended, or most likely route for the mobile device A410 to proceed to the destination (based on the previous location), the user can change such route and make other stops, such as by going straight by mistake. The arrival prediction engine 115 updates the ETA of the mobile device A410 with each or at least a portion of the current location of the mobile device A410 as the mobile device A410 moves, and notifies a third party, for example, when the mobile device A410 is approaching or arriving at a destination. For example, the current location of the mobile device A410 corresponds to a path that can be part of continuing in the same traveling direction that the mobile device A410 has been traveling (e.g., continuing along the current road), and a path that includes turning in either direction (e.g., to another road). Each of these three possible directions corresponds to a path that may have a significantly different estimated time of arrival at the destination. In response to detecting this directional ambiguity, the arrival prediction engine 155 can trigger an increase in the sampling rate of the mobile device A410's position data so that the ambiguity of the traveling direction of the mobile device A410 can be resolved and the ETA of the mobile device A410 can be accurately updated.

[0048] The location of the mobile device B420 represents another location of directional ambiguity. The mobile device B420 is in or part of a car located between two lanes that allow traffic in both directions. For example, a car entering a road from a private road may not have a prior location indicating the direction of travel, leading to the mobile device sharing a location where it is unclear whether it is in one direction lane or the other direction lane. In response to detecting this directional ambiguity, the arrival prediction engine 155 may trigger an increase in the sampling rate of the location data of the mobile device B420 so that the ambiguity of the heading of the mobile device B420 can be resolved and the ETA of the mobile device B420 can be accurately updated. Dynamic tracking of a mobile device with directional ambiguity is further described with reference to FIG. 5.

[0049] In one embodiment, the host system 110 sets a reference distance around the location of the directional ambiguity to serve as a trigger for dynamic tracking of the user device. For example, the arrival prediction engine 155 can set a reference distance around the intersection in a manner similar to the blind zone threshold described above. In one embodiment, the arrival prediction engine 155 or the mobile device determines that the mobile device is in a directional ambiguity location (or within a reference distance to such a location) based on the current location, location data of the mobile device. In another embodiment, the arrival prediction engine 155 or the mobile device determines that the mobile device is in a directional ambiguity location (or within a reference distance to such a location) based on the current location, location data of the mobile device, including a tolerance for the location information. For example, the accuracy of the positioning system may be subject to a tolerance of several feet or meters. The mobile device A 410 is shown as having a tolerance for location information 430. An overlap between the tolerance for location information 430 and the intersection or other location of the directional ambiguity can serve as a trigger for dynamic tracking of the mobile device A 410. Similarly, mobile device B 420 is shown as having a location information tolerance 440, which can be used to trigger dynamic tracking of mobile device B 420 when the location information tolerance 440 overlaps with a location of directional ambiguity. FIG. 5 is a flow chart illustrating an example method of estimating arrival using dynamic tracking of a user device when current location data is insufficient to determine a heading direction. Method 500 can be performed by processing logic, which can include hardware (e.g., a processing device, circuitry, dedicated logic, programmable logic, microcode, device hardware, integrated circuits, etc.), software (e.g., instructions operating or executed on a processing device), or a combination thereof. In some embodiments, method 500 is performed by position data controller 135, arrival prediction engine 155, or a combination thereof. To illustrate the example, method 500 is described below as being performed by a processing device.

[0050] At step 505, the processing device sets the sampling of location data at a first rate. Similar to the description of method 300 above, the first location data sampling rate can be set to conserve resources until more frequent sampling is triggered. The mobile device 105 can share location data periodically and / or based on changes in location. In one embodiment, the mobile device 105 shares updated location information at the first rate at intervals of one minute or more (e.g., five minutes) or less frequently when the location of the mobile device 105 has changed by a significant amount (e.g., 500 meters).

[0051] In step 510, the processing device determines whether the position data indicates that the mobile device is in a directionally ambiguous position. For example, the processing device determines whether the current or recent position of the mobile device is in a position that is insufficient to detect the direction of travel of the mobile device. In one embodiment, the processing device determines that the position data is insufficient to detect the direction of travel when the position data is within a reference distance of an intersection, as shown for mobile device A 410.

[0052] In another embodiment, the processing device determines that the position data is insufficient to detect a direction of travel when the position data is within a reference distance of each of multiple lanes of a road that is open to traffic in both directions, as shown for mobile device B420. For example, if the mobile device's position or the mobile device's position tolerance overlaps two lanes with different traffic directions, the processing device determines that the position data is a position with ambiguous direction. In some embodiments, the processing device uses multiple subsequent position samples to resolve the ambiguity. For example, on a narrow two-lane road, the direction at one position may be ambiguous because the traffic directions of each lane are opposite, but when multiple positions are considered, the processing device can determine that the mobile device is traveling in one direction or the other.

[0053] In yet another embodiment, the processing device determines that the position data is insufficient to detect a direction of travel if the position data of subsequent position samples does not match the direction of travel of the road lane. For example, as the mobile device enters a road from a driveway, subsequent positions may show the mobile device moving in a direction perpendicular or nearly perpendicular to the direction of travel of the lane in which the mobile device's most recent position is located, as shown for mobile device B 420.

[0054] If the location data indicates that the location data is sufficient to detect the heading of the mobile device, method 500 proceeds to step 515. If the location data indicates that the location data is insufficient to detect the heading of the mobile device, method 500 proceeds to step 525.

[0055] At step 515, the processing device determines whether another trigger has occurred to change the sampling rate of the location data, similar to the description of step 315 above. At step 520, the processing device updates the sampling rate of the location data in response to the other trigger, similar to the description of step 315 above.

[0056] In step 525, the processing device triggers an increase in location sampling to a second rate in response to the determination of the directional ambiguity. For example, the mobile device 105 updates the location data sampling rate and transmits the location data to the host system 110 more frequently (e.g., at the second rate) at intervals of one second or more (e.g., every second) and / or based on any detectable change in the location of the mobile device 105. As a result, the host system 110 can resolve the directional ambiguity more quickly and update the ETA of the mobile device accordingly. In one embodiment, similar to the description of step 323 above, the processing device triggers an increase in the location sampling rate if the location data indicates that the ETA of the mobile device arriving at the destination meets the time criteria and does not trigger an increase if the ETA of the mobile device arriving at the destination does not meet the time criteria. Also, as described above, if the network connection of the mobile device 105 does not meet the criteria (e.g., signal strength and / or generating protocol), the mobile device 105 does not attempt to transmit the location data to the host system 110.

[0057] At step 530, the processing device determines whether the heading of the mobile device has been resolved. For example, using the second rate, the mobile device 105 determines its current location (e.g., using the geographic location receiver 140) and determines whether two or more subsequent locations (e.g., the current location and the location that triggered the heading ambiguity) match the heading of the lane of the road along which the mobile device 105 is traveling. If the heading of the mobile device has been resolved, the method 500 proceeds to step 535. If the heading of the mobile device has not been resolved, the method 500 proceeds to step 540.

[0058] In step 535, the processing device updates the sampling rate of the position data in response to determining that the position data indicates that the directional ambiguity has been resolved. For example, if the position data indicates that the mobile device 105 is moving in a direction consistent with expected traffic in a lane of a road, the mobile device 105 updates the sampling rate of the position data and sends the position data less frequently (e.g., at a first rate) to the host system 110. In one embodiment, the mobile device 105 updates the sampling rate of the position data in response to detecting that its position data resolves the directional ambiguity. In another embodiment, the mobile device 105 updates the sampling rate of the position data in response to the host system 110 detecting the resolution of the directional ambiguity and the host system 110 instructing the mobile device 105 to reduce the sampling rate of the position data. The method 500 may return to step 510 and proceed as described above.

[0059] At step 540, the processing device determines whether the location data indicates that the mobile device is stationary. For example, if a reference number of location data samples indicates that the mobile device 105 has not moved beyond a tolerance or other reference distance from a previous position, the mobile device 105 may consider itself stationary. In another embodiment, the mobile device 105 may use another input, such as an accelerometer, to determine whether it is stationary. If the processing device determines whether the location data indicates that the mobile device is stationary, the method 500 proceeds to step 545. If the processing device determines whether the location data does not indicate that the mobile device is stationary, the method 500 returns to step 530. In another embodiment, the method 500 omits steps 540-555 and returns to step 530 when the location data indicates that the mobile device has not currently left the blind zone.

[0060] In response to detecting that the mobile device is stationary, the processing device reduces the sampling rate of the location data or the rate at which it attempts to transmit location data to the host server, at step 545. For example, if a user of the mobile device 105 is stopped in a parking lot, at an intersection, in traffic, etc., the mobile device 105 may conserve processing resources by reporting its stationary location to the host system 110 less frequently, or simply not reporting or attempting to report.

[0061] At step 550, the processing device determines whether the location data indicates that the mobile device remains stationary. For example, the mobile device 105 can continue sampling the location data (while minimizing or without reporting the location data to the host system 110), or the mobile device 105 can sample the location data in response to a change in location detected based on another component, such as an accelerometer. If the processing device determines whether the location data indicates that the mobile device is still stationary, the method 500 returns to step 550 and continues to wait until the mobile device begins to move again. If the processing device determines whether the location data does not indicate that the mobile device is stationary, the method 500 proceeds to step 555.

[0062] In response to detecting that the mobile device is no longer stationary, the processing device triggers an increase in the sampling rate back to the increased rate (e.g., the second sampling rate) at step 555. Method 500 returns to step 530 to detect whether and when the heading of the mobile device has been resolved.

[0063] In the foregoing specification, the invention has been described with reference to certain exemplary embodiments thereof. Various embodiments and aspects of the invention are described with reference to the details discussed herein, and the accompanying drawings illustrate various embodiments. The above description and drawings are illustrative of the invention and should not be construed as limiting the invention. References herein to "one embodiment," "embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or feature, but not all embodiments may necessarily include the particular feature, structure, or feature. Moreover, such phrases do not necessarily refer to the same embodiment. Moreover, if a particular feature, structure, or feature is described in connection with one embodiment, such feature, structure, or feature may be implemented in connection with other embodiments, whether or not explicitly described. Blocks with dashed borders (e.g., big dash, small dash, dot dash, dot) may be used herein to describe any operations that add additional features to an embodiment of the invention. However, such notations should not be interpreted to mean that these are the only optional or optional operations and / or that blocks with solid borders are not optional in a particular embodiment of the invention. Numerous specific details are set forth in order to provide a thorough understanding of various embodiments of the invention, but in certain instances, well-known or conventional details are not set forth in order to provide a concise description of the embodiments of the invention.

[0064] It will be apparent that various modifications may be made thereto without departing from the broader spirit and scope of the present invention, as set forth in the following claims. For example, the methods described herein may be performed with fewer or more functions / operations, or the functions / operations may be performed in a different order. Further, the methods described herein may be repeated or performed in parallel with each other, or with different embodiments of the same or similar methods.

Claims

1. obtaining location data of a mobile device located in or part of a vehicle, the location data being obtained at a first sampling rate; determining that the location data is insufficient to detect a direction of travel along a lane of traffic around the mobile device; triggering an increase in sampling of the position data from the first sampling rate to a second sampling rate when it is determined that the position data is insufficient to detect a direction of travel along a lane traffic direction around the mobile device; detecting a travel direction along a traffic lane direction around the mobile device from the position data of the mobile device obtained at the second sampling rate, estimating a route to a destination of the mobile device based on the travel direction, and calculating an estimated time of arrival of the mobile device at the destination based on the route; A program that causes a computer to execute the following.

2. 2. The program of claim 1, wherein determining that the position data of the mobile device obtained at the first sampling rate is insufficient to detect a direction of travel along a traffic lane direction around the mobile device comprises determining that the position of the mobile device obtained at the first sampling rate meets a reference distance from an intersection of a plurality of routes.

3. 2. The program of claim 1, wherein determining that the position data of the mobile device obtained at the first sampling rate is insufficient to detect a direction of travel along a traffic direction of lanes surrounding the mobile device comprises determining that the position of the mobile device obtained at the first sampling rate is within a reference distance from two lanes of a road having different traffic directions.

4. obtaining subsequent location data of the mobile device; determining that the subsequent location data is sufficient to detect a direction of travel along a lane of traffic around the mobile device; triggering a decrease in sampling of position data from the second sampling rate to the first sampling rate when it is determined that the subsequent position data is sufficient to detect a direction of travel along a lane traffic direction around the mobile device; The program according to claim 1 , further comprising:

5. 5. The method of claim 4, wherein determining that the subsequent location data is sufficient to detect a direction of travel along a lane traffic direction surrounding the mobile device comprises determining that the location of the mobile device does not meet a reference distance from an intersection of a plurality of routes.

6. 5. The program of claim 4, wherein determining that the subsequent position data is sufficient to detect a direction of travel of the mobile device along a surrounding lane traffic direction comprises determining that the position of the mobile device indicates a direction of travel along a surrounding lane traffic direction relative to the position of the mobile device obtained at the first sampling rate.

7. The program product of claim 1 , further comprising causing the mobile device to suspend sampling at the second sampling rate when the mobile device is detected to be stationary.

8. When executed by a processing device, the processing device obtaining location data of a mobile device located in or part of a vehicle, the location data being obtained at a first sampling rate; determining that the location data is insufficient to detect a direction of travel along a lane of traffic around the mobile device; triggering an increase in sampling of the position data from the first sampling rate to a second sampling rate when it is determined that the position data is insufficient to detect a direction of travel along a lane traffic direction around the mobile device; detecting a travel direction along a traffic lane direction around the mobile device from the position data of the mobile device obtained at the second sampling rate, estimating a route to a destination of the mobile device based on the travel direction, and calculating an estimated time of arrival of the mobile device at the destination based on the route; A non-transitory computer-readable storage medium having instructions for executing the method.

9. 9. The non-transitory computer-readable storage medium of claim 8, wherein determining that the position data of the mobile device obtained at the first sampling rate is insufficient to detect a direction of travel along a lane traffic direction around the mobile device includes determining that the position of the mobile device obtained at the first sampling rate meets a reference distance from an intersection of a plurality of routes.

10. 9. The non-transitory computer-readable storage medium of claim 8, wherein determining that the position data of the mobile device obtained at the first sampling rate is insufficient to detect a direction of travel along a lane traffic direction around the mobile device includes determining that the position of the mobile device obtained at the first sampling rate is within a reference distance from two lanes of a road having different traffic directions.

11. obtaining subsequent location data of the mobile device; determining that the subsequent location data is sufficient to detect a direction of travel along a lane of traffic around the mobile device; triggering a decrease in sampling of position data from the second sampling rate to the first sampling rate when it is determined that the subsequent position data is sufficient to detect a direction of travel along a lane traffic direction around the mobile device; The non-transitory computer-readable storage medium of claim 8 , further comprising the processing device further executing:

12. 12. The non-transitory computer-readable storage medium of claim 11, wherein determining that the subsequent location data is sufficient to detect a direction of travel along a lane traffic direction surrounding the mobile device includes determining that the location of the mobile device does not meet a criteria distance from an intersection of a plurality of routes.

13. 12. The non-transitory computer-readable storage medium of claim 11, wherein determining that the subsequent position data is sufficient to detect a direction of travel along a surrounding lane traffic direction of the mobile device comprises determining that the position of the mobile device indicates a direction of travel along a surrounding lane traffic direction relative to the position of the mobile device obtained at the first sampling rate.

14. 9. The non-transitory computer-readable storage medium of claim 8, wherein the processing device further performs the step of causing the mobile device to suspend sampling at the second sampling rate when the mobile device is detected to be stationary.

15. A processing device; a memory coupled to the processing device and storing instructions; An apparatus comprising: The instructions, when executed by the processing device, cause the apparatus to: obtaining location data of a mobile device located in or part of a vehicle, the location data being obtained at a first sampling rate; determining that the location data is insufficient to detect a direction of travel along a lane of traffic around the mobile device; triggering an increase in sampling of the position data from the first sampling rate to a second sampling rate when it is determined that the position data is insufficient to detect a direction of travel along a lane traffic direction around the mobile device; detecting a travel direction along a traffic lane direction around the mobile device from the position data of the mobile device obtained at the second sampling rate, estimating a route to a destination of the mobile device based on the travel direction, and calculating an estimated time of arrival of the mobile device at the destination based on the route; Execute the Device.

16. 16. The apparatus of claim 15, wherein determining that the position data of the mobile device obtained at the first sampling rate is insufficient to detect a direction of travel along a lane traffic direction surrounding the mobile device comprises determining that the position of the mobile device obtained at the first sampling rate meets a reference distance from an intersection of a plurality of routes.

17. 16. The apparatus of claim 15, wherein determining that the position data of the mobile device obtained at the first sampling rate is insufficient to detect a direction of travel along a lane traffic direction surrounding the mobile device comprises determining that the position of the mobile device obtained at the first sampling rate is within a reference distance from two lanes of a road having different traffic directions.

18. obtaining subsequent location data of the mobile device; determining that the subsequent location data is sufficient to detect a direction of travel along a lane of traffic around the mobile device; triggering a decrease in sampling of position data from the second sampling rate to the first sampling rate when it is determined that the subsequent position data is sufficient to detect a direction of travel along a lane traffic direction around the mobile device; The apparatus of claim 15 , wherein the processing device further performs the steps of:

19. 20. The apparatus of claim 18, wherein determining that the subsequent location data is sufficient to detect a direction of travel along a lane traffic direction surrounding the mobile device comprises determining that the location of the mobile device does not meet a criteria distance from an intersection of a plurality of routes.

20. 20. The apparatus of claim 18, wherein determining that the subsequent position data is sufficient for detecting a direction of travel along surrounding lane traffic for the mobile device comprises determining that the position of the mobile device indicates a direction of travel along surrounding lane traffic for the mobile device position obtained at the first sampling rate.

Citation Information

Patent Citations

  • Positioning device

    JP2000352519A

  • Navigation apparatus and program for the same

    JP2009281814A

  • Navigation device, navigation system, terminal device, navigation server, navigation method, and program

    JP2012233791A

  • Travelling direction estimation device, method and program

    JP2014224715A