Power Preservation in GPS-Equipped Tracking Devices

Power can be preserved in a tracking device equipped with a GPS receiver and a transceiver by evaluating the proximity of the tracking device to a mobile device and enabling the GPS receiver and transceiver only in the event that the tracking device is out of the range of the mobile device. Once enabled, the location of the tracking device can be determined based on location information received from the GPS receiver. The determined location can be provided to a tracking system associated with the tracking device. The tracking system can then inform an owner of the tracking device of the determined location. Once the tracking device has been found, the GPS receiver and the transceiver can be disabled to save additional power.

BACKGROUND

This disclosure relates generally to tracking devices, and more specifically, to preserve power in a GPS-equipped tracking device.

Electronic tracking devices have created numerous ways for people to track the locations of people and/or objects. For example, a user can use GPS technology to track a device remotely or determine a location of the user. In another example, a user can attach a tracking device to an important object, such as keys or a wallet, and use the features of the tracking device to more quickly locate the object, (e.g., if it becomes lost).

However, traditional tracking devices and corresponding systems suffer from one or more disadvantages. For instance, a battery of the tracking device may be difficult to recharge or replace, thus limiting the lifespan of the tracking device to the length of time the battery can power the tracking device. Accordingly, there is a need to improve performance in order to reduce the power requirements of the tracking device, thereby extending the amount of time the battery can power the tracking device, and thus extending the lifespan of the tracking device itself.

SUMMARY

A tracking device includes a wireless transmitter and receiver and a GPS receiver, each of which can drain a battery of the tracking device when enabled. Thus, to preserve power, the wireless transmitter and receiver and the GPS receiver are enabled only when the tracking device is determined to be lost. The tracking device can be determined to be lost if a set of lost conditions are satisfied. In some embodiments, the set of lost conditions can be a factory default set of lost conditions, while in other embodiments, the set of lost conditions are user-selected or defined. After determining the tracking device is lost, a controller of the tracking device enables the wireless transmitter and receiver and the GPS receiver. The controller then determines a location of the tracking device from the GPS receiver and provides the determined location to a central tracking system via the wireless transmitter. The central tracking system can notify a user or owner of the tracking device that the tracking device is determined to be lost, and can provide the determined location to the user. When the tracking device is determined to no longer be lost, the wireless receiver and transmitter and the GPS receiver are deactivated.

DETAILED DESCRIPTION

Environment Overview

Embodiments described herein detail functionality associated with a tracking device. A user can attach a tracking device to or enclose the tracking device within an object, such as a wallet, keys, a car, a bike, a pet, or any other object that the user wants to track. The user can then use a mobile device (e.g., by way of a software application installed on the mobile device) or other device or service to track the tracking device and corresponding object. For example, the mobile device can perform a local search for a tracking device attached to a near-by object. However, in situations where the user is unable to locate the tracking device using their own mobile device (e.g., if the tracking device is beyond a distance within which the mobile device and the tracking device can communicate), the user can leverage the capabilities of a community of users of a tracking device system.

In particular, a tracking system (also referred to herein as a “cloud server” or simply “server”) can maintain user profiles associated with a plurality of users of the tracking device system. The tracking system can associate each user within the system with one or more tracking devices associated the user (e.g., tracking devices that the user has purchased and is using to track objects owned by the user). If the user's object becomes lost or stolen, the user can send an indication that the tracking device is lost to the tracking system, which is in communication with one or more mobile devices associated with the community of users in communication with the system. The tracking system can set a flag indicating the tracking device is lost. When one of a community of mobile devices that are scanning for nearby tracking devices and providing updated locations to the tracking system identifies a flagged tracking device, the tracking system can associate the received location with the flagged tracking device, and relay the location to a user of the tracking device, thereby enabling the user to locate the lost tracking device.

FIG. 1illustrates an example tracking system environment in which a tracking device can operate, according to one embodiment. The environment ofFIG. 1includes a tracking system100communicatively coupled to a mobile device102associated with the user103via a first network108. The tracking system100is also communicatively coupled to a plurality of community mobile devices104athrough104n(collectively referred to herein as “community mobile devices104”) associated with a plurality of users105athrough105nof the tracking system100(collectively referred to herein as “community users105”) via the first network108. As will be explained in more detail below, the tracking system100can allow the user103to manage and/or locate a tracking device106associated with the user103. In some embodiments, the tracking system100leverages the capabilities of community mobile devices104to locate the tracking device106if the location of the tracking device is unknown to the user103and beyond the capabilities of mobile device102to track. In some configurations, the user103may own and register multiple tracking devices106. AlthoughFIG. 1illustrates a particular arrangement of the tracking system100, mobile device102, community mobile devices104, and tracking device106, various additional arrangements are possible.

In some configurations, the user103may be part of the community of users105. Further, one or more users105may own and register one or more tracking devices106. Thus, any one of the users within the community of users105can communicate with tracking system100and leverage the capabilities of the community of users105in addition to the user103to locate a tracking device106that has been lost.

The tracking system100, mobile device102, and plurality of community mobile devices104may communicate using any communication platforms and technologies suitable for transporting data and/or communication signals, including known communication technologies, devices, media, and protocols supportive of remote data communications.

In certain embodiments, the tracking system100, mobile device102, and community mobile devices104may communicate via a network108, which may include one or more networks, including, but not limited to, wireless networks (e.g., wireless communication networks), mobile telephone networks (e.g., cellular telephone networks), closed communication networks, open communication networks, satellite networks, navigation networks, broadband networks, narrowband networks, the Internet, local area networks, and any other networks capable of carrying data and/or communications signals between the tracking system100, mobile device102, and community mobile devices104. The mobile device102and community of mobile devices104may also be in communication with a tracking device106via a second network110. The second network110may be a similar or different type of network as the first network108. In some embodiments, the second network110comprises a wireless network with a limited communication range, such as a Bluetooth or Bluetooth Low Energy (BLE) wireless network. In some configurations, the second network110is a point-to-point network including the tracking device106and one or more mobile devices that fall within a proximity of the tracking device106. In such embodiments, the mobile device102and community mobile devices104may only be able to communicate with the tracking device106if they are within a close proximity to the tracking device, though in other embodiments, the tracking device can use long-distance communication functionality (for instance, a GSM transceiver) to communicate with either a mobile device102/104or the tracking system100at any distance. In some configurations, the mobile device102and one or more community mobile devices104may each be associated with multiple tracking devices associated with various users.

As mentioned above,FIG. 1illustrates the mobile device102associated with the user103. The mobile device102can be configured to perform one or more functions described herein with respect to locating tracking devices (e.g., tracking device106). For example, the mobile device102can receive input from the user103representative of information about the user103and information about a tracking device106. The mobile device102may then provide the received user information, tracking device information, and/or information about the mobile device102to the tracking system100. Accordingly, the tracking system100is able to associate the mobile device102, the user103, and/or the tracking device106with one another. In some embodiments, the mobile device102can communicate with the tracking device106and provide information regarding the location of the tracking device to the user103. For example, the mobile device102can detect a communication signal from the tracking device106(e.g., by way of second network110) as well as a strength of the communication signal or other measure of proximity to determine an approximate distance between the mobile device102and the tracking device106. The mobile device102can then provide this information to the user103(e.g., by way of one or more graphical user interfaces) to assist the user103to locate the tracking device106. Accordingly, the user103can use the mobile device102to track and locate the tracking device106and a corresponding object associated with the tracking device106. If the mobile device102is located beyond the immediate range of communication with the tracking device106(e.g., beyond the second network110), the mobile device102can be configured to send an indication that a tracking device106is lost to the tracking system100, requesting assistance in finding the tracking device. The mobile device102can send an indication of a lost device in response to a command from the user103. For example, once the user103has determined that the tracking device106is lost, the user can provide user input to the mobile device102(e.g., by way of a graphical user interface), requesting that the mobile device102send an indication that the tracking device106is lost to the tracking system100. In some examples, the lost indication can include information identifying the user103(e.g., name, username, authentication information), information associated with the mobile device102(e.g., a mobile phone number), information associated with the tracking device (e.g., a unique tracking device identifier), or a location of the user (e.g., a GPS location of the mobile device102at the time the request is sent).

The tracking system100can be configured to provide a number of features and services associated with the tracking and management of a plurality of tracking devices and/or users associated with the tracking devices. For example, the tracking system100can manage information and/or user profiles associated with user103and community users105. In particular, the tracking system100can manage information associated with the tracking device106and/or other tracking devices associated with the user103and/or the community users105.

As mentioned above, the tracking system100can receive an indication that the tracking device106is lost from the mobile device102. The tracking system100can then process the indication in order to help the user103find the tracking device106. For example, the tracking system100can leverage the capabilities of the community mobile devices104to help find the tracking device106. In particular, the tracking system100may set a flag for a tracking device106to indicate that the tracking device106lost and monitor communications received from the community mobile devices104indicating the location of one or more tracking devices106within proximity of the community mobile devices104. The tracking system100can determine whether a specific location is associated with the lost tracking device106and provide any location updates associated with the tracking device106to the mobile device102. In one example, the tracking system may receive constant updates of tracking device106locations regardless of whether a tracking device106is lost and provide a most recent updated location of the tracking device106in response to receiving an indication that the tracking device106is lost.

In some configurations, the tracking system100can send a location request associated with the tracking device106to each of the community mobile devices104. The location request can include any instructions and/or information necessary for the community mobile devices106to find the tracking device102. For example, the location request can include a unique identifier associated with the tracking device106that can be used by the community mobile devices104to identify the tracking device106. Accordingly, if one of the community mobile devices104detects a communication from the tracking device106(e.g., if the community mobile device104is within range or moves within range of the communication capabilities of the tracking device106and receives a signal from the tracking device106including or associated with the unique identifier associated with the tracking device106), the community mobile device104can inform the tracking system100. Using the information received from the community mobile devices104, the tracking system100can inform the user (e.g., by way of the mobile device102) of a potential location of the tracking device106.

As shown inFIG. 1and as mentioned above, the tracking system100can communicate with a plurality of community mobile devices104associated with corresponding community users105. For example, an implementation may include a first community mobile device104aassociated with a first community user105a, a second community mobile device104bassociated with a second community user105b, and additional communication mobile devices associated with additional community users up to an nth community mobile device104nassociated with an nth community user105n. The community mobile devices104may also include functionality that enables each community mobile device104to identify a tracking device106within a proximity of the community mobile device104. In one example, a first community mobile device104awithin proximity of a tracking device106can communicate with the tracking device106, identify the tracking device106(e.g., using a unique identifier associated with the tracking device106), and/or detect a location associated with the tracking device106(e.g., a location of the first mobile community device104aat the time of the communication with the tracking device106). This information can be used to provide updated locations and/or respond to a location request from the tracking system100regarding the tracking device106. In some embodiments, the steps performed by the first community mobile device104acan be hidden from the first community user105a. Accordingly, the first community mobile device104acan assist in locating the tracking device106without bother and without the knowledge of the first community user105a.

As mentioned above, the tracking system100can assist a user103in locating a tracking device106. The tracking device may be a chip, tile, tag, or other device for housing circuitry and that may be attached to or enclosed within an object such as a wallet, keys, purse, car, or other object that the user103may track. Additionally, the tracking device106may include a speaker for emitting a sound and/or a transmitter for broadcasting a beacon. In one configuration, the tracking device106may periodically transmit a beacon signal that may be detected using a nearby mobile device102and/or community mobile device104. In some configurations, the tracking device106broadcasts a beacon at regular intervals (e.g., one second intervals) that may be detected from a nearby mobile device (e.g., community mobile device104). The strength of the signal emitted from the tracking device106may be used to determine a degree of proximity to the mobile device102or community mobile device104that detects the signal. For example, a higher strength signal would indicate a close proximity between the tracking device106and the mobile device102and a lower strength signal would indicate a more remote proximity between the tracking device106and the mobile device102, though in some embodiments, the tracking device106can intentionally vary the transmission strength of the beacon signal. In some cases, the strength of signal or absence of a signal may be used to indicate that a tracking device106is lost.

System Overview

FIG. 2illustrates an example tracking system for use in a tracking system environment, according to one embodiment. As shown, the tracking system100may include, but is not limited to, an association manager204, a tracking device location manager206, a tracking device power manager207, and a data manager208, each of which may be in communication with one another using any suitable communication technologies. It will be recognized that although managers204-208are shown to be separate inFIG. 2, any of the managers204-208may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment.

The association manager204may be configured to receive, transmit, obtain, and/or update information about a user103and/or information about one or more specific tracking devices (e.g., tracking device106). In some configurations, the association manager204may associate information associated with a user103with information associated with a tracking device106. For example, user information and tracking information may be obtained by way of a mobile device102, and the association manager204may be used to link the user information and tracking information. The association between user103and tracking device106may be used for authentication purposes, or for storing user information, tracking device information, permissions, or other information about a user103and/or tracking device106in a database.

The tracking system100also includes a tracking device location manager206. The tracking device location manager206may receive and process an indication that the tracking device106is lost from a mobile device (e.g., mobile device102or community mobile devices104). For example, the tracking system100may receive a lost indication from a mobile device102indicating that the tracking device106is lost. The tracking device location manager206may set a flag on a database (e.g., tracker database212) indicating that the tracking device106is lost. The tracking device location manager206may also query a database to determine tracking information corresponding to the associated user103and/or tracking device106. The tracking system100may obtain tracking device information and provide the tracking device information or other information associated with the tracking device106to a plurality of community mobile devices104to be on alert for the lost or unavailable tracking device106.

The tracking device location manager206may also receive a location from one or more community mobile devices104that detect the tracking device106, for instance in response to the community mobile device receiving a beacon signal transmitted by the tracking device106, without the tracking device106having been previously marked as lost. In such embodiments, a user corresponding to the mobile device102can request a most recent location associated with the tracking device from the tracking system100, and the location manager206can provide the location received from the community mobile device for display by the mobile device102. In some embodiments, the location manager206provides the location of the tracking device106received from a community mobile device either automatically (for instance if the tracking device106is marked as lost) or at the request of a user of the mobile device102(for instance, via an application on the mobile device102). The location manager206can provide a location of a tracking device106to a mobile device102via a text message, push notification, application notification, automated voice message, or any other suitable form of communication.

The tracking device location manager206may further manage providing indications about whether a tracking device106is lost or no longer lost. For example, as discussed above, the tracking device location manager206may provide a location request to the community of mobile devices104indicating that a tracking device106is lost. Additionally, upon location of the tracking device106by the user103or by one of the community of users105, the tracking device location manager206may provide an indication to the user103, community user105, or tracking system100that the tracking device106has been found, thus removing any flags associated with a tracking device and/or canceling any location request previously provided to the community of users105. For example, where a user103sends an indication that the tracking device106is lost to the tracking system100and later finds the tracking device106, the mobile device102may provide an indication to the tracking system100that the tracking device106has been found. In response, the tracking device location manager206may remove a flag indicating that the tracking device106is lost and/or provide an updated indication to the community of users105that the tracking device106has been found, thus canceling any instructions associated with the previously provided location request. In some configurations, the notification that the tracking device106has been found may be provided automatically upon the mobile device102detecting the tracking device106within a proximity of the mobile device102. Alternatively, the notification that the tracking device106has been found may be provided by the user103via user input on the mobile device102. In another example, a known user (e.g., a friend or family member) with whom the tracking device106has been shared may provide an indication that the tracking device106has been found.

The tracking system100additionally includes a tracking device power manager207. The tracking device power manager207can store and manage power settings for a tracking device106provided by the user103, for instance via user input on the mobile device102. The power settings may include parameters related to the enabling or disabling of various components of the tracking device106, such as a GPS receiver (or “GPS unit” hereinafter) and a wireless transmitter and receiver.

The tracking system100additionally includes a data manager208. The data manager208may store and manage information associated with users, mobile devices, tracking devices, permissions, location requests, and other data that may be stored and/or maintained in a database related to performing location services of tracking devices. As shown, the data manager208may include, but is not limited to, a user database210, a tracker database212, permissions data214, and location request data216. It will be recognized that although databases and data within the data manager208are shown to be separate inFIG. 2, any of the user database210, tracker database212, permissions data214, and location request data216may be combined in a single database or manager, or divided into more databases or managers as may serve a particular embodiment.

The data manager208may include the user database210. The user database210may be used to store data related to various users. For example, the user database210may include data about the user103as well as data about each user105in a community of users105. The community of users105may include any user that has provided user information to the tracking system100via a mobile device102,104or other electronic device. The user information may be associated with one or more respective tracking devices106, or may be stored without an association to a particular tracking device. For example, a community user105may provide user information and permit performance of tracking functions on the community mobile device104without owning or being associated with a tracking device106. The user database210may also include information about one or more mobile devices or other electronic devices associated with a particular user.

The data manager208may also include a tracker database212. The tracker database212may be used to store data related to tracking devices. For example, the tracker database212may include tracking data for any tracking device106that has been registered with the tracking system100. Tracking data may include unique tracker identifications (IDs) associated with individual tracking devices106. Tracker IDs may be associated with a respective user103. Tracker IDs may also be associated with multiple users. Additionally, the tracker database212may include any flags or other indications associated with whether a specific tracking device106has been indicated as lost and whether any incoming communications with regard to that tracking device106should be processed based on the presence of a flag associated with the tracking device106.

The data manager208may further include permissions data214and location request data216. Permissions data214may include levels of permissions associated with a particular user103and/or tracking device106. For example, permissions data214may include additional users that have been indicated as sharing a tracking device106, or who have been given permission to locate or receive a location of a tracking device106. Location request data216may include information related to a location request or a lost indication received from the user103via a mobile device102.

FIG. 3illustrates an example user mobile device for use in a tracking system environment, according to one embodiment. As shown, the mobile device102may include, but is not limited to, a user interface manager302, a location request manager304, a database manager306, and a tracking manager308, each of which may be in communication with one another using any suitable communication technologies. It will be recognized that although managers302-308are shown to be separate inFIG. 3, any of the managers302-308may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment.

As will be explained in more detail below, the mobile device102includes the user interface manager302. The user interface manager302may facilitate providing the user103access to data on a tracking system100and/or providing data to the tracking system100. Further, the user interface manager302provides a user interface by which the user103may communicate with tracking system100and/or tracking device106via mobile device102. For example, the user interface manager302can facilitate the providing of power settings to the tracking device106for power management on the tracking device106by the user103.

The mobile device102may also include a location request manager304. The location request manager304may receive and process a request input to the mobile device102to send an indication that a tracking device106is lost to a tracking system100. For example, the user103may provide an indication that a tracking device106is lost, unreachable, or otherwise unavailable from the mobile device102via the user interface manager302, and the location request manager304may process the lost indication and provide any necessary data to the tracking system100for processing and relaying a location request to other users105over a network108. In some configurations, an indication that a tracking device106is lost is provided via user input. Alternatively, the indication may be transmitted automatically in response to the mobile device102determining that a tracking device106is lost.

In addition, the location request manager304can request a location of the tracking device106without the tracking device106being identified as lost. For instance, a user can access a tracking device location feature of an application running on the mobile device102(for example, via the user interface manager302), and the location request manager304can request a most recent location of the tracking device106from the tracking system100. The location request manager304can receive the most recent location from the tracking system100, and can display the most recent location via the user interface manager302.

The mobile device102may also include a database manager306. The database manager306may maintain data related to the user103, tracking device106, permissions, or other data that may be used for locating a tracking device106and/or providing a request to a tracking system100for locating one or more tracking devices106associated with the user103. Further, the database manager306may maintain any information that may be accessed using any other manager on the mobile device102.

The mobile device102may further include a tracking manager308. The tracking manager308may include a tracking application (e.g., a software application) for communicating with and locating a tracking device106associated with the user103. For example, the tracking manager308may be one configuration of a tracking application installed on the mobile device102that provides the functionality for locating a tracking device106and/or requesting location of a tracking device106using a tracking system100and/or a plurality of community mobile devices104. As shown, the tracking manager308may include, but is not limited to, a Bluetooth Low Energy (BLE) manager310, a persistence manager312, a local files manager314, a motion manager316, a secure storage manager318, a settings manager320, a location manager322, a network manager324, a notification manager326, a sound manager328, a friends manager330, a photo manager332, an authentication manager334, and a device manager336. Thus, the tracking manager308may perform any of the functions associated with managers310-338, described in additional detail below.

The BLE manager310may be used to manage communication with one or more tracking devices106. The persistence manager312may be used to store logical schema information that is relevant to the tracking manager308. The local files manager314may be responsible for managing all files that are input or output from the mobile device102. The motion manager316may be responsible for all motion management required by the tracking manager308. The secure storage manager318may be responsible for storage of secure data, including information such as passwords and private data that would be accessed through this sub-system. The settings manager320may be responsible for managing settings used by the tracking manager308. Such settings may be user controlled (e.g., user settings) or defined by the tracking manager308for internal use (e.g., application settings) by a mobile device102and/or the tracking system100. The location manager322may be responsible for all location tracking done by the tracking manager308. For example, the location manager322may manage access to the location services of the mobile device102and works in conjunction with other managers to persist data. The network manager324may be responsible for all Internet communications from the tracking manager308. For example, the network manager324may mediate all Internet API calls for the tracking manager308. The notification manager326may be responsible for managing local and push notifications required by the tracking manager308. The sound manager328may be responsible for playback of audio cues by the tracking manager308. The friends manager330may be responsible for managing access to contacts and the user's social graph. The photo manager332may be responsible for capturing and managing photos used by the tracking manager308. The authentication manager334may be responsible for handling the authentication (e.g., sign in or login) of users. The authentication manager334may also include registration (e.g., sign up) functionality. The authentication manager334further coordinates with other managers to achieve registration functionality. The device manager336may be responsible for managing the devices discovered by the tracking manager308. The device manager336may further store and/or maintain the logic for algorithms related to device discovery and update.

FIG. 4illustrates an example community mobile device for use in a tracking system environment, according to one embodiment. As shown, the community mobile device104may include, but is not limited to, a user interface manager402, a tracking device manager404, a database manager406, and a tracking manager408, each of which may be in communication with one another using any suitable communication technologies. The user interface manager402, database manager406, and tracking manager408illustrated inFIG. 4may include similar features and functionality as the user interface manager302, database manager306, and tracking manager308described above in connection withFIG. 3. It will be recognized that although managers402-408are shown to be separate inFIG. 4, any of the managers402-408may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment.

The community mobile device104may include a tracking device manager404. The tracking device manager404may facilitate scanning for nearby tracking devices106. In some configurations, the tracking device manager404can continuously or periodically scan (e.g., once per second) for nearby tracking devices106. The tracking device manager404may determine whether to provide an updated location of the nearby tracking device106to the tracking system100. In some configurations, the tracking device manager404provides a location of a nearby tracking device106automatically. Alternatively, the tracking device manager404may determine whether the location of the tracking device106has been recently updated, and may determine whether to provide an updated location based on the last time a location of the tracking device106has been updated (e.g., by the community mobile device104). For example, where the community mobile device104has provided a recent update of the location of a tracking device106, the tracking device manager404may decide to wait a predetermined period of time (e.g., 5 minutes) before providing an updated location of the same tracking device106.

In one configuration, the tracking device manager404may receive and process a location request or other information relayed to the community mobile device104by the tracking system100. For example, the tracking device manager404may receive an indication of a tracking device106that has been indicated as lost, and provide a location of the tracking device106if it comes within proximity of the community mobile device104. In some configurations, the community mobile device104is constantly scanning nearby areas to determine if there is a tracking device106within a proximity of the community mobile device104. Therefore, where a tracking device106that matches information provided by the tracking system100(e.g., from the location request) comes within proximity of the community mobile device104, the tracking device manager404may generate and transmit a response to the location request to the tracking system100, which may be provided to the user103associated with the tracking device106. Further, generating and transmitting the response to the tracking request may be conditioned on the status of the tracking device106being flagged as lost by the mobile device102and/or the tracking system100.

The tracking device manager404may additionally provide other information to the tracking system100in response to receiving the tracking request. For example, in addition to providing a location of the community mobile device104, the tracking device manager may provide a signal strength associated with the location to indicate a level of proximity to the location of the community mobile device104provided to the user103. For example, if a signal strength is high, the location provided to the user103is likely to be more accurate than a location accompanied by a low signal strength. This may provide additional information that the user103may find useful in determining the precise location of tracking device106.

As described above, the tracking device manager404may determine whether to send a location within the proximity of the tracking device106to the tracking system100. The determination of whether to send a location to the tracking system100may be based on a variety of factors. For example, a tracking device manager404may determine to send a location of the tracking device106to a tracking system100based on whether the detected tracking device106has been indicated as lost or if a tracking request has been provided to the community mobile device104for the particular tracking device106. In some configurations, the community mobile device104may send an update of a location of a tracking device106even if the tracking device106is not associated with a current tracking request or if the tracking device106is not indicated as lost. For example, where the location of a tracking device106has not been updated for a predetermined period of time, the community mobile device104may provide an update of a tracking device location to the tracking system100, regardless of whether a tracking request has been received.

In some configurations, the community mobile device104may include additional features. For example, the community mobile device104may allow a tracking system100to snap and download a photo using photo functionality of the community mobile device104. In some configurations, this may be an opt-in feature by which a community user105permits a tracking system100to take a snap-shot and possibly provide a visual image of an area within a proximity of the tracking device106.

FIG. 5illustrates an example tracking device for use in a tracking system environment, according to one embodiment. The tracking device106ofFIG. 5includes an interface502, a transceiver504, a controller506, one or more sensors508, and a GPS unit510. The transceiver504is a hardware circuit capable of both transmitting and receiving signals. It should be noted that in other embodiments, the tracking device106includes fewer, additional, or different components than those illustrated inFIG. 5.

The interface502provides a communicative interface between the tracking device106and one or more other devices, such as a mobile device102. For instance, the interface502can instruct the transceiver504to output beacon signals as described above (for example, periodically or in response to a triggering event, such as a detected movement of the tracking device106). The interface502can, in response to the receiving of signals by the transceiver504from, for instance, the mobile device102, manage a pairing protocol to establish a communicative connection between the tracking device106and the mobile device102. As noted above, the transceiver504can include a BLE receiver and transmitter, though in other embodiments, the transceiver504enables communications via other suitable wireless connection protocols (such as WiFi, Global System for Mobile Communications or “GSM”, LTE, and the like). It should be noted that while various examples herein describe the transceiver504as a GSM receiver and transmitter, this is done for the purposes of brevity, and it should be emphasized that the transceiver504can communicate over any other wireless communication protocol according to the embodiments described herein.

The controller506is a hardware chip that configures the tracking device106to perform one or more functions or to operate in one or operating modes or states. For instance, the controller506can configure the interval at which the transceiver broadcasts beacon signals, can authorize or prevent particular devices from pairing with the tracking device106based on information received from the devices and permissions stored at the tracking device, can increase or decrease the transmission strength of signals broadcasted by the transceiver, can configure the interface to emit a ringtone or flash an LED light, can enable or disable various tracking device sensors, can enable or disable a tracking device GPS unit, can enable or disable communicative functionality of the tracking device106(such as a GSM transmitter and receiver), can configure the tracking device into a sleep mode or awake mode, can configure the tracking device into a power preservation mode, and the like. The controller506can configure the tracking device to perform functions or to operate in a particular operating mode based on information or signals received from a device paired with or attempting to pair with the tracking device106, based on an operating state or connection state of the tracking device106, based on user-selected settings, based on information stored at the tracking device106, based on a detected location of the tracking device106, based on historical behavior of the tracking device106(such as a previous length of time the tracking device was configured to operate in a particular mode), based on information received from the sensors508or the GPS unit510, or based on any other suitable criteria.

The controller506can configure the tracking device106to operate in one or more power preservation modes. Each power preservation mode is associated with a set of tracking device settings. For instance, the controller506can configure the tracking device106to operate according to factory default power saving mode that includes a set of tracking device settings pre-installed on the tracking device. Likewise, the controller506may receive a set of tracking device settings associated with a user-defined power preservation mode from a user103through the user interface manager302of a mobile device102.

The sensors508can include motion sensors (such as gyroscopes or accelerators), altimeters, orientation sensors, proximity sensors, light sensors, or any other suitable sensor configured to detect an environment of the tracking device106, a state of the tracking device106, a movement or location of the tracking device106, and the like. The sensors508are configured to provide information detected by the sensors to the controller506. The GPS unit510is configured to detect a location of the tracking device106based on received GPS signals, and is configured to provide detected locations to the controller506.

Power Preservation Overview

In some embodiments, a tracking device106includes a transceiver504and a GPS unit510, which can be power intensive and can drain the battery of the tracking device106if always enabled. As noted above, the tracking device106can include any of a number of types of transceivers that operate and can be controlled according to the principles described herein, but the remainder of the description herein will be limited to embodiments in which the transceiver504is a GSM transceiver for the purposes of simplicity. Thus, to preserve battery power, the tracking device106can be configured to operate in a power saving mode in which the GSM transceiver and GPS unit510are disabled, and when the tracking device106is identified as lost, the tracking device106can be configured to operate in lost device mode by enabling the GSM transceiver and GPS unit.

The tracking device106may be identified as lost if certain lost conditions are met. These lost conditions may be factory default lost conditions or user-selected lost conditions. If the tracking device106is configured to operate in a power saving mode and is determined to be lost, the controller506can configure the tracking device106to operate in a lost device mode by enabling the GSM transceiver and GPS unit510on the tracking device106. The controller506then determines an updated location for the tracking device106from location information received via the GPS unit510. The controller506can provide the determined location to the tracking system100or the mobile device102via the GSM transceiver, along with an indication that the tracking device106is determined to be lost. The tracking system100can notify the user103that the tracking device106is lost, and can provide the determined location to the user (for instance via the mobile device102).

The controller506can subsequently disable the GPS unit and the GSM transceiver. For instance, the controller506can disable the GPS unit and the GSM transceiver in response to one or more of: determining that the tracking device106is no longer lost (e.g., in response to the tracking device106coupling to or receiving a signal from the mobile device106, or otherwise determining that the mobile device102or user103are within a threshold proximity distance of the tracking device106), in response to an instruction received from the tracking system100or the mobile device102via the GSM transceiver, in response to the passage of a threshold amount of time, or in response to any other suitable condition.

In some embodiments, lost conditions can be based on a time duration parameter describing a duration of time that a tracking device106is located outside a communicative transmission range of an access point before it is determined to be lost (e.g., the tracking device is determined to be lost if the tracking device hasn't received a signal from a mobile device or other wireless device for a particular duration of time). Examples of access points can include the user's mobile device102, a community mobile device105, or any other wireless device associated with the tracking device106, the user103, or the tracking system100. For example, the user103may set the time duration parameter for a tracking device106attached to a pet to 30 seconds. In such an example, the controller506determines that the tracking device106(and thus the pet) is lost if the tracking device106is located outside of the transmission range of the user's mobile device for more than 30 seconds. In another example, the user103may set a time duration parameter to 15 minutes if the tracking device106is attached to a set of keys. The time duration parameter may be a factory default time duration parameter or may be set by the user in the power settings for power management of the tracking device106.

In some embodiments, lost conditions may be based on a motion threshold parameter describing a threshold amount of motion a tracking device106can move without receiving a communication from a mobile device or other device associated with the tracking device before it is determined to be lost. In some embodiments, lost conditions can be based on a time of day (e.g., if a tracking device detects large amounts of motion during particular or user-selected times of day that the motion isn't expected, the tracking device can be determined to be lost), based on a day of the week, based on a last-determined location (e.g., if a tracking device was last determined to be located at a user's home, and the tracking device hasn't received a communication from the user since the user left for work, the tracking device may not be determined to be lost), based on an amount of remaining battery power available to the tracking device, or any other suitable conditions.

When the tracking device106is configured to operate in a power saving mode, the tracking device can be configured based on settings in addition to disabling the GPS unit and GSM transceiver until the tracking device is determined to be lost. For example, such additional power saving mode settings can include a frequency or interval that the controller506receives location information via the GPS unit, a frequency or interval that the controller enables the GPS unit, a frequency or interval that the controller communicates using the GSM transceiver, a frequency or interval that the controller provides location information to the tracking system100via the GSM transceiver, a frequency or interval that the controller enables the GSM unit, a duration for which the GPS unit and/or the GSM transceiver are enabled when the controller enables the GPS unit or GSM transceiver, and the like.

In one embodiment, after determining the tracking device106is lost, the controller506may check to see if a wifi network is available before turning on the GSM transceiver and GPS unit510. In the event that a wifi network is available, the controller506can enable a wifi transceiver of the tracking device106and the GPS unit, can determine a location of the tracking device via information received via the GPS unit, and can transmit the determined location via the wifi network.

FIGS. 6A, 6B, and 6Cillustrate an example of power preservation in a tracking device equipped with a GPS unit, according to one embodiment. InFIG. 6A, the tracking device601configured to operate in a power preservation mode is within a transmission range605of the community mobile device104iof community user105i. In this embodiment, the GPS unit of tracking device601is turned off. InFIG. 6B, the tracking device601is outside the transmission range605of the mobile device104iof community user105i. However, the tracking device601has been outside of this transmission range for less than 30 seconds, the time duration parameter set in the power settings of the power preservation mode of the tracking device601. Thus, the tracking device601is not determined to be lost and the GPS unit remains disabled. InFIG. 6C, the tracking device601is outside the transmission range605of the community mobile device104iof community user105ifor more than 30 seconds. Thus, the tracking device601is determined to be lost, and the tracking device601is configured to operate in a lost device mode. In the lost device mode, the GPS unit of the tracking device is enabled, and the location of the tracking device is determined based on location information received from the GPS unit. Additionally, the GSM transceiver of the tracking device601is enabled, and the determined location of the tracking device is transmitted to the tracking system100or to the mobile device102of the owner of the tracking device.

FIG. 7Aillustrates an example process for preserving power in a tracking device equipped with a GPS unit, according to one embodiment. The tracking system receives710a location via a GSM network from the tracking device. The tracking device is configured with a GPS unit that, upon a determination that the tracking device is lost, is enabled and location information is received from the GPS unit and provided to the tracking system. The tracking system updates712a stored current location of the tracking device with the received location of the tracking device. The tracking system notifies714the user that the tracking device may be lost and provides714the user with the updated location of the tracking device.

In some embodiments, tracking device instructions are received716from the user. For example, the user can provide an indication that the tracking device is no longer lost. In response, the tracking system can provide718configuration instructions based on the received tracking device instructions. For example, in response to an instruction from the user that the tracking device is no longer lost, the tracking system can instruct the tracking device to configure itself in a power saving mode (e.g., by disabling the GPS unit and the GSM unit of the tracking device). Likewise, in some embodiments, the tracking device is configured to enable the GPS unit, determine the location of the tracking device, enable the GSM unit, and communicate the determined location periodically (e.g., every 30 seconds). In such embodiments, the tracking system can provide instructions to the tracking device to repeat the location determination and providing cycle over a longer period (e.g., every 60 seconds).

FIG. 7Billustrates an example process for preserving power in a tracking device equipped with a GPS unit, according to one embodiment. The tracking device determines722that a set of lost conditions are satisfied. An example lost condition is failing to receive a communication from a mobile device for a predetermined amount of time. The tracking device enables724a GSM transceiver and a GPS unit of tracking device in response to determining that the lost conditions are satisfied (and thus determining that the tracking device is lost). The tracking device determines726the location of the tracking device via the GPS unit. The tracking device sends728the location of the tracking device via GSM transceiver to the tracking system, which is configured to provide the location of the tracking device to an owner of the tracking device.

In response to determining730that the tracking device is no longer lost, the tracking device disables732the GSM transceiver and the GPS unit. The determination that the tracking device is no longer lost may be based on the tracking device receiving a communication from a mobile device (and thus being within the transmission range of the mobile device), or receiving an indication from the owner of the tracking device (for instance, through the tracking system) that the tracking device is no longer lost. For example, the user may find the tracking device and bring the user's mobile device within proximity of the tracking device, or the user may find the tracking device without the user's mobile device being within proximity of the tracking device or in operation, and the user may notify the tracking system by other means that the tracking device has been found. In a third example, the tracking device motion sensors may indicate that the tracking device has not moved since the previous time the tracking device provided its location to the tracking system via the GSM transceiver, and thus the tracking device disables the GSM transceiver and the GPS unit.

Additional Considerations

Any of the devices or systems described herein can be implemented by one or more computing devices. A computing device can include a processor, a memory, a storage device, an I/O interface, and a communication interface, which may be communicatively coupled by way of communication infrastructure. Additional or alternative components may be used in other embodiments. In particular embodiments, a processor includes hardware for executing computer program instructions by retrieving the instructions from an internal register, an internal cache, or other memory or storage device, and decoding and executing them. The memory can be used for storing data or instructions for execution by the processor. The memory can be any suitable storage mechanism, such as RAM, ROM, flash memory, solid state memory, and the like. The storage device can store data or computer instructions, and can include a hard disk drive, flash memory, an optical disc, or any other suitable storage device. The I/O interface allows a user to interact with the computing device, and can include a mouse, keypad, keyboard, touch screen interface, and the like. The communication interface can include hardware, software, or a combination of both, and can provide one or more interfaces for communication with other devices or entities.