HK1129144A - Mobile tracking - Google Patents

Description

Motion tracking

Technical Field

The present disclosure relates generally to wireless communication devices, and in particular, to wireless communication devices having a Global Positioning System (GPS) receiver or other such position determination capability.

Background

Some wireless communication devices have a Global Positioning System (GPS) chipset (or external Bluetooth (r)) that is capable of communicating with a wireless device^TMAccessories) that convert radio frequency signals received from orbiting GPS satellites into real time coordinates of longitude and latitude, typically accurate to within a few meters of the actual current location of the device. This current location (i.e., coordinates of longitude and latitude) may then be wirelessly transmitted to a recipient with another wireless communication device (or to any other networked computing device via a cellular base station and the internet), allowing the recipient to use any of a number of available mapping applicationsOne, e.g. BlackBerry Maps^TM、Google Maps^TMOr TeleNav^TMTo map the coordinates. Sending the GPS determined current location from one mobile device to another can enable two mobile users to rendezvous, or alternatively allow one mobile user to follow the other mobile user. This "two-party voluntary" tracking is described, for example, in PCT publication WO2006/108071 (XONE corporation) entitled "Location Sharing and tracking Using Mobile Phones or Other Wireless Devices". In a similar manner, the GPS tracking device to be attached to the target vehicle is hidden from the knowledge and consent of the target. These hidden devices only provide static location updates automatically (i.e., periodically) or upon remote request. See, for example, U.S. patent application publication 2007/0139223(Bedenko) entitled "Vehicle Tracking System" and U.S. patent application publication 2007/0099626(Lawrence et al) entitled "Tracking System and method".

Considering this ("two-party voluntary") scenario, a first mobile user wants a second mobile user to follow him. The first mobile user may periodically send their GPS coordinates to the second mobile user, allowing the second mobile user to map the static location data using a mapping application. However, due to the time lag in generating, transmitting and drawing the position data map, by the time the second mobile user sees the first mobile user's "current" position, the position is no longer "current". This problem is particularly apparent when the second mobile user follows the first mobile user at a high speed, such as in their respective cars or other vehicles, in which case the time lag between updates makes it difficult to follow the first mobile user. This problem is further exacerbated in densely populated urban areas where the density of roads makes it less clear which route or routes need to be taken in order to reach the most recently received location update of the first mobile user. While it is conceivable that one solution would require more frequent location updates, this would undesirably burden the onboard processors of both the sender and recipient's devices, let alone using the higher-valued wireless bandwidth with the extra over-the-air transmission. Therefore, there is a great need for improvements in this prior art to facilitate the tracking of one mobile user to another.

Disclosure of Invention

In general, the present technology preferably provides a method, wireless communication device, and computer program product that enable tracking of a wireless communication device. In its primary application, such techniques may enable a user of a first wireless communication device to track or follow a second wireless communication device by receiving not only current location data representing the current location of the second wireless communication device, but also one or more of speed data, time data or path data indicating the speed of the device, the time corresponding to the current location and the path (or route) taken by the device from its previously transmitted location to its current location, respectively.

Preferably, therefore, one aspect of the present technology is a method of tracking wireless communication devices using other computing devices. The method may comprise the steps of: obtaining current location data of a first wireless communication device; obtaining one or more of speed data, time data and path data of the first wireless communication device; and transmitting at least one of the speed data, the time data and the path data together with the current location data from the wireless communication device to the other computing device to enable tracking of the wireless communication device using the computing device. In one primary implementation, the computing device may be a second wireless communication device to track the second wireless communication device using the first wireless communication device.

Another aspect of the technology may be a computer program product comprising code adapted to perform the steps of the above method when the computer program product is loaded into a memory and executed on a processor of a wireless communication device. Alternatively, the code may be loaded onto a server adapted to receive raw device data from a first mobile device, process the data to create useful route tracking information (e.g., waypoints), and then send the information (the processed data) to a second mobile device.

Yet another aspect of the technology can be a wireless communication device for generating and transmitting data to enable tracking of the device. The apparatus may have: a GPS chipset for receiving GPS signals and for generating current location data indicative of a current location of the device; a memory operatively connected to the processor for storing and executing an application configured to obtain one or more of speed data, time data, and path data for the device; and a radio frequency transmitter for transmitting the current position data in addition to at least one of the speed data, time data and path data.

Yet another aspect of the technology may be a computing device for tracking a mobile device. The computing device may have: a communication port for receiving current location data representing a current location of the mobile device in addition to at least one of speed data, time data, and path data associated with the mobile device; a memory, operatively connected to the processor, for storing and executing a mapping application for generating a map having a current location mapped thereon; and a display for displaying the map in addition to one or more of the speed data, time data and path data.

Drawings

Further features and advantages of the present technology will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, in which:

fig. 1 is a flowchart outlining the steps of a method of generating and transmitting speed, time and path data to enable a first wireless communication device to track a second wireless communication device;

FIG. 2 is a block diagram of key components of a GPS-enabled wireless communication device on which the present techniques may be implemented;

FIG. 3 is a high level system diagram depicting the operation of the present tracking technique;

FIG. 4 depicts a common scenario, given by way of example only, in which a first mobile user would utilize the present tracking technology to enable a second mobile user, who has been left behind at a traffic light, to follow the first mobile user;

FIG. 5 depicts a problem that arises in the example scenario of FIG. 4, where a second mobile user attempts to guess which path to take is the correct route to follow the first mobile user when only current location updates are periodically provided to the second mobile user;

FIG. 6 depicts how the method of generating and sending speed, time and path data enables a second mobile user to determine the correct route to a first mobile user;

FIG. 7 depicts an example of a mapping application displayed on a wireless communication device tracking a mobile user of another mobile user;

FIG. 8 depicts an example of an options page within a "tracking manager" module or application in which a user of a tracking device may configure various settings and preferences associated with tracking functionality; and

FIG. 9 depicts an example of an options page within a "follow-me manager" module or application in which a user of a device to be followed may configure various settings and preferences associated with tracking functionality.

It may be noted that throughout the drawings, like reference numerals are used to identify like features.

Detailed Description

The details and particularity of these aspects of the present technology will now be described, by way of example, with reference to the accompanying drawings.

Fig. 1 is a flowchart outlining the steps of a method of generating and transmitting speed, time and path data to enable a first wireless communication device to track a second wireless communication device. In an initial step 10, tracking of one device to another device is initiated. Here, this will be understood as initiating or activating a "follow me" mode. Activating the "follow-me" mode may be performed by the first device or by the second device, and may be performed manually or automatically. Automatic triggering of the tracking mode may be performed using a proximity detection subsystem that detects when one device has moved away from another device with which it is paired. Can use Bluetooth^TMProximity detection to enable such detection. When a Bluetooth^TMWhen a device is far from its paired device, then the connection is lost, so this can be used to automatically trigger activation of the track/follow-me mode.

As shown in the flow chart of fig. 1, once the track/follow-me mode has been activated, the first wireless communication device (the "leading" device, i.e., the mobile device to be followed) obtains current location data representing the current location (place) of the device at step 12. An onboard GPS chipset receiver can be used, or Bluetooth can be provided externally^TMA GPS puck is enabled to obtain current position data. GPS signals from a plurality of GPS satellites orbiting provide a position fix accurate to within a few meters. Assisted GPS technology and assisted GPS technology may also be used to improve Time To First Fix (TTFF). Position data may also be obtained or supplemented using radiolocation techniques including triangulation of base station signals and time of arrival calculations, but these techniques have lower accuracy than GPS, which provides sufficient accuracy for road-based navigation.

As further described in fig. 1, the method also requires a step 14 for determining the type of additional data to be obtained and transmitted. In other words, in addition to generating and transmitting the current position data, one or more of speed data, time data, and path data are also obtained and transmitted. As shown in FIG. 1, seven options (16-28) are given in FIG. 1: option 16: obtaining all data types (i.e., speed, time, and path data); option 18: obtaining only speed and time data; option 20: obtaining only speed and path data; option 22: obtaining only time and path data; option 24: obtaining only speed data; option 26: obtaining only time data; and option 28: only the path data is obtained. In other words, the "tracking data" includes not only GPS location data, but also one or more of velocity data, time data, and path data. The tracking data may also include orientation (direction of movement). Once this "trace data" is obtained, it is sent to another device (i.e. the device following/tracing the leading device) at step 30. For consistency of naming, the first mobile user is the operator of the leading device and the second mobile user is the operator of the tracking/following device. After the trace data has been sent, an evaluation is made whether to continue the trace, step 32. If no further tracking is required (i.e., if the first mobile user or the second mobile user has disabled the tracking functionality), then operation is stopped at step 34. If further tracking is to be continued, new (updated) position, velocity, time and path data is obtained and transmitted by repeating steps 12-30. The characteristics and attributes of the speed, time and path data will be described in more detail below with respect to fig. 3. As will be explained below, these additional tracking data facilitate performing tasks of tracking or following another mobile device. Due to the time lag between static current location data points, it is sometimes difficult to determine which path to take to follow the leading device. In addition to providing current location data, providing speed, time and path data provides a second mobile user (i.e., a follower or tracker) with a better overall description of the first mobile user's travel. This makes it easier for the second mobile user not only to retrace the first mobile user's exact path, but also (possibly) to predict or anticipate in which direction the second mobile device is heading.

The method steps described above may be implemented as coded instructions in a computer program product. In other words, the computer program product is a computer readable medium having software code recorded thereon for performing the above-mentioned steps when the computer program product is loaded into a memory and executed on a microprocessor of a wireless communication device.

Preferably, the novel method is implemented on a wireless communication device, such as Czech research Inc(or in other wireless handsets, cellular phones, wireless enabled laptops, or wireless enabled PDAs).

Fig. 2 is a block diagram depicting certain key components of the wireless communication device 100. It should be clearly understood that this figure is intentionally simplified to show only certain components, and of course, that the device 100 includes other components than those shown in fig. 2. As is well known in the art, the device 100 includes a microprocessor 102 (or simply "processor") that interacts with memory in the form of RAM 104 and flash memory 106. Device 100 includes an RF transceiver 108 for wirelessly communicating with one or more base stations 200. The device 100 includes a GPS receiver chipset 110 for receiving GPS radio signals transmitted from one or more orbiting GPS satellites 300. In terms of input/output devices or user interfaces, device 100 typically includes a display 112 (e.g., a small LCD screen), a thumbwheel and/or trackball 114, a keyboard 116, a USB 118 or serial port for connecting to peripheral devices, a speaker 120, and a microphone 122. Thus, the processor and memory enable the mapping application (along with other software applications) to run on the wireless device. The mapping application may interact with the GPS receiver 110 by mapping the GPS location coordinates to graphically display the current location of the device.

FIG. 3 is a high-level system diagram describing the operation of the present tracking technique. In this figure, two GPS-enabled wireless communication devices 100 communicate with each other via a base station 200, or via separate base stations (if the two devices are further apart). In any case, the devices are connected to each other via a wireless network that enables transmission and reception of data packets. Further, as shown in fig. 3, the wireless communication device 100 receives GPS signals from a plurality of GPS satellites 300. The lead device "mobile device 1" (associated with the first mobile user) obtains current location data, velocity data, time data and path data (or a subset thereof) via the base station 200 (and its wireless network) and sends it to the device of the second mobile user ("mobile device 2"). The mobile device 2 receives the current location data, velocity data, time data and path data (or a subset thereof) and then presents these "tracking data" graphically and/or audibly to the second mobile user.

For example, as will be shown by the example in fig. 7 below, the second wireless communication device may use the superimposed velocity and time information of the first mobile user to plot the current location and path on a map. Alternatively or additionally, the tracking data may be presented audibly, such as in the form of an audible report (e.g., "the followed opponent is at a turn of the first street and embankment, travelling eastward over the first street at 50 km/hour), and/or as instructions for each turn to navigate the same path as the first mobile user took. In addition to receiving this tracking data, the second mobile device also receives its own GPS signal and converts it to its own GPS position fix. Its own current location may be plotted on a map to show relative location. Alternatively or additionally, its own current location fix may be used by the navigation software to reroute the second mobile user to a different path to catch up with the first mobile user. In other words, navigation software may be used to determine a more optimal route to the most recently received current location of the first mobile user, and this option is presented to the second mobile user, who may choose to follow exactly the path taken by the first mobile user, or to take the suggested "more optimal" route to catch up with the first mobile user.

For purposes of this specification, "speed data" refers toData relating to the speed, velocity or travel rate of the followed device. The velocity data may be an average velocity determined using the rate of change of position over time (determined by GPS). Alternatively, the speed data may be instantaneous speed obtained using a speed sensor/transducer embedded in or connected to the device. As another alternative, the device may receive speed data wirelessly (e.g., via bluetooth)^TMReceived from a vehicle speed sensor). The velocity data may include velocity as a scalar quantity (magnitude only), or may include a velocity vector (both velocity and direction). In the case where path data is also provided, no velocity vector is required because the direction is already known from the path data. The speed data helps the recipient (second mobile user) to know how fast the first mobile user is traveling and thus whether he should consider faster traveling to catch up with the first mobile user.

For the purposes of this specification, "time data" refers to data relating to: the actual time of day of the first mobile device when it is at a particular location, or the time elapsed since the last fix, or the time elapsed between the fix and receipt of tracking data by the second mobile user. In other words, the time data accompanying the GPS positioning gives an important context to the position data by telling the recipient (second mobile user) that the first mobile user is located at the particular location at the particular time. Providing a location alone is little indicative because the recipient may not have good knowledge of when the first mobile user is at the location. In other words, the time data allows the recipient to know how outdated or stale the definition is in fact.

For the purposes of this specification, "path data" refers to data relating to a path or route that has been taken by the first mobile device. This may be provided as a path segment (only the portion of the path that the device has traveled since the last time the definition was obtained) or as an accumulated path showing the entire path that the device has traveled since the trace was initiated. Alternatively, the receiving device may store all path data, but only display the accumulated path data that fits within the bounding box at the selected map scale. The path data may comprise a continuous list of all street names and highway numbers which, together with the directions taken along each of them, define the path taken by the leading device, constituting navigation instructions for the recipient. Alternatively, the path data may be vector data, allowing the recipient device to be able to render a path map in which the path is highlighted using one of any number of standard mapping applications. Alternatively, the leading device may generate a bitmap showing the highlighted route/path and send it to the recipient device for immediate viewing on the screen. Alternatively, the efficiency of such tracking or following methods may be improved by simplifying the path data to reduce the amount of data generated and transmitted without unduly sacrificing travel path fidelity. Techniques such as the Douglas Peuker line reduction algorithm may be used to reduce the number of points needed to describe a path (e.g., by removing common points along a straight line).

It will be appreciated that since the destination point of each path segment of the path data corresponds to each location, the path data effectively contains current location data. The route data is presented graphically highlighted route on the map (with optional navigation instructions presented graphically or audibly). Thus, the current location is used to define the end point or destination of the path. The second mobile device (the follower device) may optionally present the destination of the path (as defined by the GPS fix) as a destination street address (e.g., 123 main street) and/or as longitude and latitude coordinates.

In another embodiment, the second mobile device may also optionally present the distance to the first mobile device. This distance may be in the form of an actual road distance in kilometers (or miles) or meters (or yards). Alternatively, the distance may be presented in terms of a straight-line distance (distance that is a "straight line") in combination with a compass heading (e.g., "northeast" or 045 degrees). In addition to, or as an alternative to, distanceAn estimated time to the first mobile user's current location may be provided, or a rendezvous time (the time required to catch up with the first mobile user, or to reach within a specified range of the first user, such as triggering Bluetooth, may be presented^TMRange of proximity detection). Thus, in this variation of this embodiment, a "trip computer" module may be provided on the device as a software application to calculate various distances, compass bearings and times.

Fig. 4 depicts a general scenario, given by way of example only, in which a first mobile user ("mobile user 1") would utilize the present tracking technology to enable a second mobile user ("mobile user 2") (that has been left behind at a traffic light) to follow the first mobile user. The present technique is particularly applicable to mobile users traveling in road vehicles, where the speed involved, the amount of traffic on the road, the interference of traffic lights and the number of routing options are prone to losing track of the followed vehicle. Although a car is described as an example, the situation described in relation to this and the following figures is equally applicable to other road vehicles (e.g. trucks, vans, buses, motorcycles, scooters), or off-road vehicles (e.g. snowmobiles, all terrain vehicles), or vessels (e.g. steamers, yachts, sails, personal watercraft, jet skis), or to cyclists, or even to mobile users who are merely walking on foot.

Fig. 5 depicts the problem that arises in the scenario of fig. 4, where the second mobile user ("mobile user 2") tries to guess which is to follow the correct route to be taken by the first mobile user ("mobile user 1") when only periodically providing current location updates to the second mobile user. In this example scenario, the car associated with mobile user 1 is no longer within the line of sight of the car associated with mobile user 2 (which had been left behind earlier at the traffic light). Thus, the occupant of the car associated with the mobile user 2 does not necessarily know which route to take (to illustrate, presuming that the occupant of the car associated with the mobile user 2 does not know the correct route to take to reach the lake park).

Fig. 6 depicts how the method of generating and sending speed, time and path data allows a second mobile user ("mobile user 2") to determine the correct route to a first mobile user ("mobile user 1"). In this example (again provided only to illustrate the use of the present technique), mobile user 2 is provided by mobile user 1 at a discrete point with three data transfers to allow mobile user 2 to follow mobile user 1. At time T1, when mobile subscriber 1 leaves the south of highway 206 (206S) to bridge street, mobile subscriber 1 sends his current location and his speed, time and path to mobile subscriber 2. For example, the path data may be a pre-generated bitmap (or vector path data allowing a map to be presented), showing a segment of highway 17, followed by exiting to highway 206S. Navigation instructions for each turn may also be provided in graphical or audible form. At time T2, when mobile user 1 turns onto the bridge, another transfer of tracking data is sent, again providing an update of mobile user 1's current location and its updated speed, time and path data. Again, at time T3, mobile user 1 sends the updated location, velocity, time, and path data to mobile user 2. The three data transfers provide mobile subscriber 2 with sufficient information to allow mobile subscriber 2 to be able to properly navigate out onto highway 206S, properly steer onto the bridge street, and properly then follow the bridge across the lake to the park, which is the intended destination of mobile subscriber 1.

FIG. 7 depicts an example of a mapping application displayed on a wireless communication device of a mobile user who is tracking another mobile user. The application interface 350 is provided merely as an example to illustrate one way of presenting the tracking data. It is readily appreciated that other interfaces (i.e. having different "look and feel") are of course possible which present data in other ways. Similarly, the interface may present more data or less data than shown in this example. In addition to the graphical representation of the tracking data, audible reports may be used to supplement or replace certain aspects of the tracking data, such as navigation for each turn using text-to-speech, with vocalization reading street names, audibly reporting speed, time and location data in addition to being displayed on the screen.

As depicted by the example interface 350 shown in fig. 7, the current location of the tracker (the second mobile user) is shown by a car icon 360 (although the user may select other icons to suit the environment). The car icon 370 represents the GPS position fix for the first mobile user time T1 that the second mobile user is tracking once the track/follow-me mode is enabled. Sending the first set of tracking data packets to the second mobile user reporting, for example: at time T1, which is 12:05 pm, the first mobile user is traveling eastward on the first street at 50 km/h. A second transmission is sent a moment later to update the current location, speed, time and path. The car icon 380 represents the location updated at time T2, which in this example is after 5 minutes of 12:10 pm (although it should be understood that the update may be provided more frequently, e.g., once per minute) or less frequently, as configured by the user. In suburban environments, where routing options are less, users may wish to conserve device resources for other uses or applications, and thus may provide less frequent updates. In densely populated urban areas, the number of route choices is higher, and thus the likelihood of getting lost is higher, so more frequent updates may of course be useful. The frequency of updates may also be managed or adjusted based on the state of the leading user (first mobile user) and the distance between the first mobile user and the second mobile user (follower). For example, if the leading user (first mobile user) (a) stops; (b) traveling at high speed in a constant direction; or (c) a greater distance from the following vehicle (requiring feedback from the tracker/second mobile user), the updates may be sent less frequently. Sending updates less frequently reduces the burden on the mobile device and the wireless link. It should also be noted that if the path data is sent in larger segments, the path data can be more easily compressed. The rate of travel (i.e., speed) of the leading user (first mobile user) may also be an important factor for determining whether there is a delay effect in generating, transmitting, receiving, and displaying the path data. In other words, if there is a large or significant delay ("latency") in providing path data to the tracker, the method will take this latency or delay into account by predicting or predicting where the first mobile user (the leading user) is likely to be at, or where the leading user is heading, the moment the path data is actually displayed on the second mobile user's device screen.

Still referring to the example of fig. 7, the second data transfer report is, for example: at time T2, which is 12:10 pm, the second mobile user is traveling eastward on the third street at 40 km/h. This path data would provide the route as shown between car icons 370 and 380, i.e., the route traversed between times T1 and T2. Written instructions and/or audible instructions will provide navigation for each turn, e.g., "go east on the first street, turn north on the bank street (left), turn east on the third street (right), go through highway 1".

Still referring to the example shown in fig. 7, a third update is provided to the second mobile user by sending the updated tracking data at time T3, the location of this time tracking data being represented by car icon 390. At time T3, 12:15 pm (still after 5 minutes), the first mobile user travels eastward on the fourth street at 30 km/h. The route data updates the route to that shown between the car icons 380 and 390 and optionally provides navigation instructions in written or audible form, e.g., "turn south (right) on the oak street, turn east (left) on the second street, turn north (left) on the maple street, turn east (right) on the fourth street)". These path, velocity and time data facilitate the second mobile user completing the task of following the first mobile user through city streets. As described above, rather than blindly following the exact path taken by the first mobile user, the application may optionally calculate an alternative route (e.g., to the east on the first street, and to the left on the alder street). In summary, the selection between the precise route and the alternative route is presented to the second mobile user, or the user may configure the device to automatically provide either the precise route or the alternative route (where the alternative route is shorter).

FIG. 8 depicts an example of an options page 400 within a "tracking manager" module or application in which a user of a tracking device (a second mobile user) may configure various settings and preferences associated with a tracking function. For example, the options page 400 allows a user to activate or deactivate the tracking function, determine what types of data to display and in what particular form. The user may also specify the frequency with which update requests are sent to devices belonging to the followed first mobile user. The user may also specify whether he prefers to receive a pre-generated bitmap (i.e., a bitmap generated by the first mobile user on his device) or whether he prefers to receive raw data, which is then mapped by the receiving device. An optional path log may be provided to allow the user to review or revisit all navigation instructions acquired while following the first mobile user along the various path segments. An optional "draw now" function generates a map in which the path is highlighted or otherwise emphasized.

In one embodiment, a breadcrumb (breadcrumbs) path (comprised of waypoints or path segments) may also be stored (along with optional reverse navigation instructions) to allow the user to be able to retrace his path to return to the starting point where tracking is to begin. This set of breadcrumb functions and/or reverse path instructions is particularly useful in the following situations: the second mobile user has followed the first mobile user through an unfamiliar location and then wishes to return to the point where the follow begins alone (without guidance). For example, consider the following scenario: the second mobile user has followed the first mobile user through unfamiliar terrain to the cabin and then wishes to go home alone after dark. The user activates the breadcrumb function to get a route home without worrying about trying to navigate unfamiliar roads in the dark. The breadcrumb function may also include a stored travel time to inform the user how long the user has taken to travel between waypoints while following the first mobile user. The breadcrumb function may also optionally provide (audibly or graphically) the distance and travel speed of each path segment between waypoints. This helps the user know at what speed he is reasonably traveling (when the speed limit may not be easily visible), and how many kilometers or miles he has to travel to the next waypoint. The breadcrumb function may also optionally recalculate the travel time to the next waypoint based on the actual speed of movement on the return leg of the voyage (which may be different from the travel speed of the first leg of the voyage). Another breadcrumbs function that may be implemented, in addition to the turn-around step for each turn, is an off-road breadcrumbs function that may be used in situations where the leading user (the first mobile user) is not traveling on a road known to the navigation software, in which case breadcrumbs or waypoints are defined at specific locations to allow the tracking party to follow the same path taken by the leading user. This applies, for example, to off-road vehicles, all-terrain vehicles, boats, airplanes, helicopters, or pedestrians or hikers who wish to follow the leading user without reference to a specifically defined road.

In a variation of this embodiment, the device may be configured to record audible input from the user (via a microphone on the device), thereby allowing the user to annotate on the personally defined waypoint. The recorded waypoint annotations may be stored in association with the actual GPS fix (or a location interpolated between adjacent fixes based on travel time and travel speed). When the user turns back their route, the waypoint annotation is audibly played via the device speaker to alert the user to a landmark or waypoint of interest to their person. For example, when passing a particular gas station, the user may record: "we are turning around at a bright orange gas station near McDonald's work". The recording operation may be voice activated (hands-free) or triggered by speaking a predetermined specified word or phrase that the voice recognition software on the device is able to recognize (e.g., "record waypoint annotations"). When the user returns, the waypoint annotations are played through the speaker to alert the user that the user thinks that it is a meaningful particular waypoint.

FIG. 9 depicts an example of an options page 500 within a "follow-me manager" module or applicationThe user of the device to be followed may configure various settings and preferences associated with the tracking function therein. The follow-me manager allows the user of the followed device (the first mobile user) to manually initiate the follow-me mode, based on bluetooth^TMProximity detection (Bluetooth)^TMLoss of connection) automatically triggers the follow-me mode or disables the follow-me mode (refuses to receive trace data). Other options are also possible, such as caching the trace data and asking the second mobile user if he would like to accept the trace data, if the second device answers in a positive way, the first device enters the follow-me mode. Without using bluetooth^TMLoss of connection to trigger follow-me mode, bluetooth may also be used^TMThe proximity detection incoming signal indicates availability to enter the follow-me mode. Having Bluetooth when the device is set to "discoverable" mode^TMThe functional device sends an indication that it is ready and available for use with another bluetooth^TMSignal that the device is "paired". For example, if the first and second mobile users plan to meet so that one can follow the other, both users put their devices into "discoverable" mode so that when they come within a suitable range, e.g., for class I bluetooth^TMThe device is about 100 meters, or alternatively, the two devices are allowed to pair when within 10 meters for a class II device. Furthermore, although due to the limited range (100m), Bluetooth may be used^TMConnected (for class I devices) to enable some or all of the data exchange, but preferably relying on a wireless link. In another variation, the device may use bluetooth^TMThe link is then switched to a cellular channel (the "normal" radio link) when the device-to-device range is near its maximum.

Further, as shown by way of example in fig. 9, the user may configure the follow-me manager to actively generate and send data (active mode), or to await a data request from a follow-up device (passive mode). The user of the followed device may accept either generating a bitmap based on the request (which burdens the followed device), or sending only the raw data (which shifts the computational burden to the device being followed).

As further shown in fig. 9, the follow-me manager may allow the user to specify whether the current location data, speed data, time data, and path data are allowed to be generated and transmitted. For speed data, the first mobile user may specify whether to send speed only or speed plus direction (speed vector). Finally, as also shown by way of example only in fig. 9, the first mobile user may adjust the allowed update frequency. Frequent updates are advantageous to the followed party (i.e. provide the most tracking data), but are also the most expensive in terms of data charges and air transfer time and processing resource consumption of the device. On the other hand, infrequent transmissions consume less resources, enabling the processor and RAM of the device to be idle to process other applications. This feature adjusts the content that the first mobile user is willing to distribute. In fact, the actual frequency of transmission may be determined based on what the first mobile user is willing to provide and what the second mobile user is requesting, or may be determined based on various parameters as described above, i.e., the rate of travel, the distance between mobile users, etc.

In another embodiment, the frequency of the update may be based on a feedback loop that requires feedback from the follower. For example, a first mobile device (the leading user) does not send a complete set of route data representing all of the route information between its respective locations, and instead, a more efficient method of sending data may include packaging the route data and sending a small batch or packet of route information to a follower (the second mobile user) with only one waypoint marker at a time. When the follower reaches the waypoint marker, the follower's device signals to the lead user that more data is needed. The waypoint markers may be set a certain distance (or equivalent time) forward of the endpoint of the current segment of route data so that the follower does not run out of route data before more route data can be provided. In other words, when the follower reaches the waypoint marker, the follower device signals the leader device that the next piece of line information is needed. As a corollary benefit, the leading user receives an acknowledgement: the follower has reached the waypoint marker and is thus "correctly tracked". This provides the leading user with a finer sense of the follower's current location, allowing the user to optionally adjust to the line, speed, etc. to accommodate the follower. Requesting more data from the lead device can be accomplished in a manner very similar to a "more" request made in the received email, i.e. using only a single bit (marker) to indicate that the waypoint has been reached, thus requiring more data to describe or delineate the next segment along the route.

Although one follower and one preamble device are assumed above, this technique may also be used to multicast trace data to more than one follower. This is the case when a first mobile user wishes to direct a group of friends, all in different cars, to his cabin.

It should also be understood that the follower may also be a static (non-moving) follower, i.e., a user of a stationary computing device that is merely visually following, or visually tracking, the motion of the leading user. While the computing device is preferably a wireless communication device, the computing device may also be a desktop computer, laptop computer, or other such computing device having a processor, memory, and a communication port for receiving real-time tracking data. Even for stationary computing devices, the communication port may be wireless or wired.

The present novel technology has been described with reference to specific embodiments and configurations, which are intended to be exemplary only. Accordingly, the scope of patenting sought by the applicant should be limited only by the following claims.

Claims (20)

1. A method of tracking a wireless communication device using other computing devices, the method comprising the steps of:

obtaining current location data of a first wireless communication device;

obtaining one or more of speed data, time data and path data of the first wireless communication device; and

at least one of one or more of speed data, time data and path data is transmitted with the current location data from the first wireless communication device to the other computing device to enable tracking of the first wireless communication device using the other computing device.

2. The method of claim 1, wherein the other computing device is a second wireless communication device.

3. The method of claim 2, comprising: speed data, time data, and path data are obtained and transmitted to the second wireless communication device in addition to the current location data.

4. The method of claim 2, comprising: only the velocity data is obtained and the velocity data is transmitted to the second wireless communication device in addition to the current position data.

5. The method of claim 2, comprising: only the time data is obtained and transmitted to the second wireless communication device in addition to the current location data.

6. The method of claim 2, comprising: only the path data is obtained and transmitted to the second wireless communication device in addition to the current location data.

7. The method of claim 2, comprising: only the speed data and the time data are obtained and transmitted to the second wireless communication device in addition to the current position data.

8. The method of claim 2, comprising: only the speed data and the path data are obtained and transmitted to the second wireless communication device in addition to the current position data.

9. The method of claim 2, comprising: only the time data and the path data are obtained and transmitted to the second wireless communication device in addition to the current position data.

10. The method of claim 2, further comprising the steps of: preference data is received from the second wireless communication device indicating which one or more of speed data, time data and path data the first wireless communication device is to transmit to the second wireless communication device.

11. A computer program product comprising code adapted to cause a wireless communication device to perform the steps of the method according to any of claims 1 to 10 when the code is loaded into a memory and executed on a processor of the wireless communication device.

12. A wireless communication device for generating and transmitting data to enable other computing devices to track the wireless communication device, the wireless communication device comprising:

a Global Positioning System (GPS) chipset for receiving GPS signals and generating current location data indicative of a current location of the wireless communication device;

a memory operatively connected to the processor for storing and executing an application configured to obtain one or more of speed data, time data, and path data of the wireless communication device; and

a radio frequency transmitter for transmitting the current location data to the other computing device in addition to the at least one of the speed data, time data, and path data to the other computing device.

13. The wireless communication device of claim 12, wherein the application is further configured to: generating path data by identifying a street name or highway number corresponding to a current location of the wireless communication device.

14. The wireless communication device of claim 12 or 13, wherein the application is further configured to: the speed data is generated by determining the instantaneous speed of the wireless communication device when the current location is obtained.

15. The wireless communication device of any of claims 12-14, wherein the application is further configured to: time data is generated by determining the time at which the current location is obtained.

16. The wireless communication device of claim 13, wherein the application is further configured to: the path data is generated by determining all street names or highway numbers between the current location of the wireless communication device and a predetermined location of the wireless communication device.

17. A computing device for tracking wireless communication devices, the computing device comprising:

a communication port for receiving current location data representing a current location of the wireless communication device in addition to at least one of speed data, time data, and path data associated with the wireless communication device;

a memory, operatively connected to the processor, for storing and executing a mapping application for generating a map with a current location mapped; and

a display for displaying the map in addition to one or more of the speed data, time data and path data.

18. The computing device of claim 17, further comprising: means for transmitting preference data to the wireless communication device, the preference data indicating which one or more of the speed data, time data and path data the wireless communication device is to transmit to the computing device.

19. The computing device of claim 17 or 18, wherein the drawing application is further configured to: the computing device is enabled to specify which of the speed data, the time data, and the path data is to be displayed.

20. The computing device of any of claims 17-19, wherein the drawing application is further configured to: an audible report is provided to the user via a speaker on the computing device, the audible report being generated based on one or more of the speed data, the time data, and the path data.