System and method for dynamically monitoring status in location services

[0001] The present invention relates to the field of location based services, and more specifically to a system and method for dynamically monitoring status in location services.

[0002] Radiolocation of mobile devices developed in the last half of the 20^th century, notably with the deployment of the Global Positioning System (GPS). Mobile phone technology evolved in a similar time frame. By the turn of the century, US cellular carriers deployed location-determination technology in their networks in support of emergency (E9-1-1) services. Subsequently, with the widespread use of smart phones and other portable computing devices, numerous applications utilizing location have been made available for such uses as direction finding, tracking individuals, and matching persons with nearby businesses.

[0003] Traditionally, a company might monitor its resources, e.g., vehicles, through an expensive specialized tracking system. With location technology being integrated into employees' personal communication equipment (cell phones), the specialized tracking systems may no longer be needed. The employer can track the employees via their cell phones. However, it may be necessary or appropriate for the employer to only track the employee during work hours. A simple “9-to-5, Monday-through-Friday,” tracking limitation is not suitable for many workers who may have flexible hours, employees on vacation, etc.

[0004] The present invention solves this problem by enabling and disabling location tracking or reporting thereof, based on a dynamically monitored status, for example, when an employee is on the job and when the employee is on his or her own time.

[0005] In some embodiments, the present invention is a method for reporting a location of an asset. The method includes: receiving a location tracking request for the asset; dynamically determining a status of the asset; and allowing acquisition of the location of the asset based on the determined status. The method further includes: obtaining the location of the asset responsive to the received request and said allowing; and reporting the obtained location of the asset.

[0006] In some embodiments, the present invention is a system for reporting a location of an asset. The system includes: a reporting module for receiving a location tracking request for the asset; a status module for dynamically determining a status of the asset; and a tracking module for obtaining the location of the asset responsive to the determined status. The reporting module reports the location of the asset responsive to the received location tracking request.

[0007] In some embodiments, the present invention is a method for reporting a location of an asset. The method includes: receiving a first indication of a current state of the person, the current state being one of a plurality of predefined states, wherein the first indication is triggered by a first action of the person; storing information about the current state; determining a first permission based on the information about the current state, the first permission indicating a first level of allowed location reporting; and reporting the location of the person based on the first permission. The method may further include receiving a second indication of an updated current state of the person, the updated current state being one of the plurality of predefined states, wherein the second indication is triggered by a second action of the person; storing information about the updated current state; determining a second permission based on the information about the updated current state, the second permission indicating a second level of allowed location reporting; and reporting the location of the person based on the second permission.

[0012] In some embodiments, the present invention enables and/or disables location tracking of an asset or resource, or reporting thereof, based on a dynamically monitored status, for example, when an employee is on the job and/or when the employee is on his or her own time.

[0013] FIG. 1 illustrates an exemplary functional block diagram of a typical employee tracking system, according to the prior art. Data flows are indicated by arrowed lines. An employee 101 is monitored by a tracking module 102. The dotted line indicates a location determination, e.g., using the cellular network. The tracking module provides employee locations to a reporting module 103, which in turn make the locations available to an employer 104. An example of this is a cell phone tracking feature provided by a cellular carrier. In this example, the employer pays for the employee cell phone usage, and in turn has permission to monitor employee location while the employee is working. The details are controlled by a configuration module 105, which has information entered by the employer and possibly the employee. Configuration typically includes information such as employee name, mobile device identification, times for employee to be tracked, boundary areas for alerts, etc. The employee may or may not have access to aspects of the configuration.

[0014] FIG. 2 illustrates an example of a form used to enter some of the configuration information, according to the prior art. For a given account, the tracking can be made active (allowed) or inactive (disallowed) in the first line. In the second line, the hours of tracking are entered, here from 8 AM to 5 PM. In the third line, the days of tracking are entered, here weekdays only. Such a system does not easily account for such eventualities as the employee taking a sick day, or working a Saturday in place of a Friday, or employees with flexible schedules.

[0015] FIG. 3 shows an exemplary system diagram for tracking an asset, according to some embodiments of the present invention. The illustrated system may be applied to a more general set of tracked assets, beyond employees. An asset 301 is monitored by a tracking module 302. The tracking module provides the asset locations to a reporting module 303. The reporting module 303 reports the locations of the asset, based on conditions set by a user.

[0016] The reporting module 303 provides location of the asset or resource 301 to the monitor module 304, under control of a configuration (module) 305. The configuration includes information such as asset name, mobile device identification, boundary areas for alerts, etc. The times for asset to be tracked are supplemented or replaced by the combination of the status monitor module 306 and enablement module 307. The status monitor module, described in more detail below, determines the state of the asset at any given time. Based on the state, the enablement module 307 determines whether tracking is permitted and indicates to the reporting module whether location information may be delivered. Obtaining the location of the asset may depend on the configuration. Reporting the location of the asset may also depend on the enablement module, as well as the configuration.

[0017] In some embodiments, the status monitor module keeps track of the asset's status, for example, as a binary state: either “at work”/“on the clock” (allowing the asset to be tracked) or “off work”/“off the clock” (preventing the asset from being tracked). This may be implemented any number of ways. In some embodiments, the invention uses a device based on a traditional time clock, where employees (physically) clock in and clock out when arriving at, and leaving work. For people or assets that do not report to a central location each day, other methods, such as sending a text message or email, making a phone call, or logging in to a web portal may be available.

[0018] In some embodiments, the status monitor module has more complex permission states. A third state could indicate a person's or an asset's eligibility for tracking only with a positive response to an explicit request for permission to be located. So, in this case while a user has given permission to be located during a particular period of time, their consent may be granted by the user on a case-by-case basis based on the requestor of the location or their current status during the authorized timeframe, but automatically denied if outside the authorized timeframe.

[0019] In some embodiments, other sets of states allow the person or the asset to be tracked with varying degrees of accuracy depending on the location of the asset or the time of the location request. For example the person or the asset may be tracked by exact location while on the clock, tracked by neighborhood on lunch hour, and not tracked at all on the weekend. Also, the varying degrees of tracking accuracy might be determined by privacy concerns or cost, where less exact locations may be less expensive. A long haul delivery vehicle might need only the less expense/less accurate tracking while on the open road, but require more precise tracking near the terminus points.

[0020] The following examples show how a variety of trigger events can be used to set tracking status. A tracking status may be assigned to a person or vehicle entering a sensitive area such as a military base; a person or vehicle leaving a known area, such as a school or worksite; an emergency vehicle with its lights/siren engaged; a vehicle traveling at an excessive speed; and/or a container loaded onto a ship, which would not need to be tracked individually until later when it is unloaded from the ship.

[0021] The enablement module 307, which in some embodiments may not be distinct from the status monitor module, indicates the person or asset tracking permission to the reporting module. When not enabled, the reporting module 303 prevents location information from being delivered to the status monitor module, thus protecting the asset's privacy during non-work hours. However, depending on permissions, the reporting module could be configured to provide a person's location to other requestors, as in a family location scenario, regardless of the person's “at work” status.

[0022] FIG. 4 shows an exemplary logical flow of a reporting module, according to some embodiments of the present invention. As shown, the reporting module waits for a tracking request to be received 401, for example, from a status monitor module. When a request is received, the configuration is optionally checked 402, for example, to verify the status monitor module's credentials, verify the identity of the tracked person or asset, etc. If the configuration verification fails, no location is returned 407. If the configuration verification is successful, a status enablement check is performed 403. In this process, the enablement state determined by the status monitor module and enablement module is checked to see if tracking is currently allowed, and any associated constraints (e.g., low precision tracking only). If tracking is not allowed, no location is returned 407.

[0023] If tracking is allowed, then an attempt is made to locate the asset 405 via the tracking module. If the location is not available 405, no location is returned. If the location is available 405, the location is returned 406. The allowance of the tracking may be stored for a next tracking request of the person or the asset.

[0024] In some embodiments, a first indication of a current state of the person is received, the current state being one of a plurality of predefined states (e.g., “at work,” “off work”). The first indication is triggered by a first action of the person, such as clocking in to work as described earlier. The information about the current state (“at work” in this example) is then stored. Subsequently, a first permission is determined based on the information about the current state, the first permission indicating a first level of allowed location reporting (e.g., “full tracking allowed”). The location of the person is then reported based on the first permission. Later, a second indication of an updated current state of the person may be received, as when the person clock out of work. The updated current state (“off work”) is also one of the predefined states, and is also triggered by a second action of the person. The information about the updated current state is then stored, and a second permission is determined based on the information about the updated current state, the second permission indicating a second level of allowed location reporting (e.g., “no tracking allowed”). The location of the person is reported again, or in this example, denied, this time, based on the second permission.

[0025] It will be recognized by those skilled in the art that various modifications may be made to the illustrated and other embodiments of the invention described above, without departing from the broad inventive scope thereof. It will be understood therefore that the invention is not limited to the particular embodiments or arrangements disclosed, but is rather intended to cover any changes, adaptations or modifications which are within the scope of the invention, as defined by the appended claims.