System and method for defining areas of interest and modifying asset monitoring in relation thereto

Information

  • Patent Grant
  • 7999670
  • Patent Number
    7,999,670
  • Date Filed
    Monday, July 2, 2007
    17 years ago
  • Date Issued
    Tuesday, August 16, 2011
    13 years ago
Abstract
System and method for tracking assets comprises determining if an asset is inside a geofence area, using a first set of asset monitoring parameters to monitor operation of the asset, if the asset is inside the geofence area, and using a second set of asset monitoring parameters to monitor operation of the asset, if the asset is outside the geofence area. The invention further comprises a system and method for providing one or more competitors with an asset tracking device, wherein the asset tracking device allows each competitor's location to be monitored, defining one or more geofence areas on a racetrack, and detecting when the competitors enter a designated geofence area.
Description
TECHNICAL FIELD

The present invention relates generally to a system and method for monitoring vehicle and asset movement and, more particularly, to a system and method for defining areas and/or regions of interest for modifying asset monitoring parameters based upon location.


BACKGROUND

Geofences are used to define geographical areas so that vehicle location can be monitored with respect to those areas. A vehicle's location can be determined using a Global Positioning System (GPS) as is known. The vehicle's current location can be compared to a geofence area to determine if the vehicle is inside or outside the geofence area. A geofence is typically defined using a simple geographic shape, such as a circle, square or rectangle. For example, a circular geofence is defined by a central point and a radius is assigned to that point. All of the area within the radius around the central point is within the geofenced area. Areas having one or more irregularly shaped boundaries are not accurately represented by simple geometric shapes. There are many areas, such as neighborhoods, cities, towns, industrial parks, roads, and the like, that cannot be adequately or precisely defined using simple shapes such as circles or rectangles that are available in current geofence applications. To geofence these areas, a large geofence area that overlaps both the target area and some of the surrounding area is often used to geofence such irregularly shaped locations.


Alternatively, multiple overlapping geofence areas must be created, such as a series of overlapping circles or squares, to cover areas such as a road, highway, or a region or shape on a lake, ocean, or river with a geofence. To determine if vehicles are within the geofence area, there must be an evaluation against all of the individual geofenced areas instead of one comprehensive area. Similar to the large, overlapping geofence area discussed above, to ensure that all of the target area is covered, these smaller individual geofence areas typically overlap some locations that are not intended to be within the target geofence area. Accordingly, the accuracy of the geofence varies depending upon the shape of the target area and the available geofencing tools.


SUMMARY OF THE INVENTION

In one embodiment of the invention, a system and method for tracking assets comprises determining if an asset is inside a geofence area or zone of interest. If the asset is inside the area or zone, a first set of asset monitoring parameters is used to monitor the operation of the asset. If the asset is outside the area or zone, a second set of asset monitoring parameters is used to monitor operation of the asset. The asset may be a vehicle that is monitored using a vehicle monitoring system capable of detecting the vehicle's speed. For example, the vehicle monitoring system may use a first set of speed parameters when monitoring the vehicle, if the vehicle is inside the geofence area or zone of interest. The vehicle monitoring system may use a second set of speed parameters for monitoring the vehicle, if the vehicle is outside the geofence area or zone of interest. The first and second sets of speed parameters may be used to provide feedback to the driver upon detection of a speeding condition. The first and second sets of speed parameters may also be used to trigger messages to a supervisor, parent or other authority upon detection of a speeding condition.


The vehicle monitoring system may also or alternatively be capable of detecting acceleration forces acting on the vehicle. The vehicle monitoring system may use a first set of acceleration parameters to monitor the vehicle, if the vehicle is inside the geofence area or zone of interest; and the vehicle monitoring system may use a second set of acceleration parameters to monitor the vehicle, if the vehicle is outside the geofence area or zone of interest. The first and second sets of acceleration parameters may be used to provide feedback to the driver based upon vehicle acceleration measurements. The first and second sets of acceleration parameters may also be used to trigger messages to a supervisor, parent or other authority based upon vehicle acceleration measurements.


The zone of interest or geofence area may have any shape, such as a multi-sided shape defined by a geographic region, a circular shape defined by a radius around a selected point, a polygon, or an irregular polygon. A geofence area or zone of interest having an irregular polygon shape may be drawn by sequentially designating locations of vertices of the irregular polygon. Alternatively, the region may be established by a mathematical spline or other mathematical procedure by designating a series of points that will then define the region. In another embodiment, the area of interest or geofence may be drawn over a map and the locations of the vertices selected from points on the map.


In one embodiment of the invention, a system and method of tracking events in a race comprises providing one or more competitors with an asset tracking device. The asset tracking device allows each competitor's location to be monitored. One or more geofence areas or zones of interest are defined on a racetrack or other area. The system detects when the competitors enter a designated geofence area or zone of interest. The system and method may further detect when the competitors leave the designated area or zone. The competitors may be detected upon entering the designated area or zone without regard to whether the competitors stop in or pass through the designated area or zone. The designated area or zone may be a finish line or other section of a race track in which case the present invention may be used in an accounting function to track laps completed by competitors. The invention may be used to count a number of times each competitor enters the designated area or zone. The designated geofence area or zone of interest may be a pit area or a safety area, for example. The competitors may be motor-powered vehicles (e.g. cars, trucks, trains, planes, boats, etc), human-powered vehicles, electro-mechanical devices (e.g. robots, etc.), humans or animals.


In another embodiment, a system and method of determining if non-competitors are clear of a racetrack comprises providing one or more non-competitors with an asset tracking device. The asset tracking device allows each non-competitor's location to be monitored. One or more zones of interest or geofence areas off of the racetrack are designated. The system detects when the non-competitors are within one or more designated off-track areas or zones. The system and method may further detect when the non-competitors leave the one or more designated areas or zones and/or when the non-competitors are stopped in the one or more designated areas or zones. The designated off-track zones or areas may be a safety zone. The system and method may determine when all of the one or more non-competitors are within the designated area or zone and may indicate that the racetrack is clear of non-competitors. In this example, non-competitors may include emergency service vehicles or pace vehicles.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:



FIG. 1 is a block diagram of a system according to one embodiment of the invention;



FIG. 2 illustrates a zone of interest for use in one embodiment of the invention;



FIG. 3 illustrates another zone of interest for use in another embodiment of the invention;



FIG. 4 illustrates an area incorporating embodiments of the present invention;



FIG. 5A illustrates a detailed area incorporating embodiments of the present invention;



FIG. 5B illustrates a detailed area incorporating alternate embodiments of the present invention;



FIG. 6 illustrates a detailed area incorporating additional embodiments of the present invention;



FIG. 7 illustrates a detailed area incorporating additional embodiments of the present invention;



FIG. 8 illustrates a detailed area incorporating additional embodiments of the present invention;



FIG. 9 illustrates a detailed area incorporating additional embodiments of the present invention;



FIG. 10 is a flowchart illustrating one process for implementing the present invention;



FIG. 11 is a flowchart illustrating another process for implementing the present invention; and



FIG. 12 is a flowchart illustrating another process for implementing the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.


With reference now to FIG. 1, there is shown a vehicle 101 in which a vehicle monitoring device is installed. The monitoring device may be self contained, such as a single unit mounted on a windshield 105 or dashboard 106. Alternatively, the monitoring device may include multiple components, such as a processor or central unit mounted under a car seat 103 or in a trunk 104. Similarly, the monitoring device may have a self-contained antenna in the unit (105), or may be connected to remotely mounted antennas 107. The vehicle monitoring unit may be connected to an on-board diagnostic (OBD) system or data bus in the vehicle. Information and data associated with the operation of the vehicle may be collected from the OBD system, such as engine operating parameters, vehicle identification, seatbelt use, door position, etc. The OBD system may also be used to power the vehicle monitoring device. The vehicle monitoring system may also be coupled to other sensors or detectors that monitor engine performance and vehicle operation parameters. In one embodiment, the vehicle monitoring device is of the type described in U.S. patent application Ser. No. 11/755,556, filed on May 30, 2007, entitled “System and Method for Evaluating Driver Behavior,” the disclosure of which is hereby incorporated by reference herein in its entirety.


Information may be exchanged between the vehicle monitoring system and a central monitoring system or server in real-time or at intervals. For example, the vehicle operation parameters may be transmitted to server 109 via communication network 108, which may be a cellular, satellite, WiFi, Bluetooth, infrared, ultrasound, short wave, microwave or any other suitable network. Server 109 may process the parameters and/or store the data to database 110, which may be part of server 109 or a separate device located nearby or at a remote location. Users can access the data on server 109 and database 110 using terminal 111, which may be co-located with server 109 and database 110 or coupled via the Internet or other network connection. Is some embodiments, the data captured by the monitoring system in vehicle 101 may be transmitted via a hardwired communication connection, such as an Ethernet connection that is attached to vehicle 101 when the vehicle is within a service yard or at a base station. Alternatively, the data may be transferred via a flash memory, diskette, or other memory device that can be directly connected to server 109 or terminal 111. Data, such as driving performance or warning thresholds, may also be uploaded from the central server to the vehicle monitoring device in a similar manner.


The vehicle monitoring device uses one or more sets of parameters or thresholds while monitoring the vehicle. Each set of monitoring parameters define thresholds associated with the operation of the vehicle. For example, the vehicle monitoring device receives inputs related to vehicle speed, acceleration, and location and to driver behavior, such as seatbelt use and cell phone use. The monitoring parameters define thresholds or criteria for each of these inputs, such as maximum allowed vehicle speeds or accelerations or whether the driver is required to use seatbelts. The monitoring parameters also define what action to take if one of the thresholds or criteria is exceeded. For example, if the vehicle is speeding above a speed threshold, the monitoring parameters may define that the monitoring system should warn the driver and/or notify a supervisor regarding the speeding condition.


The monitoring parameters may also define a grace period or delay in which the user can self-correct the speeding condition. For example, if the driver is passing another vehicle, the monitoring system may detect a speeding condition, but may be configured to delay warning the driver for 30 seconds or some other length of time. If the driver corrects the speeding condition, such as by returning to a posted highway speed after passing the other vehicle, the delay may prevent a warning from being sent to the driver. Other delays may be used for alerts or notices to supervisors if speeding or other threshold violations are corrected within a specified time of the violation or from when the driver is warned by an in-vehicle warning light or message.


The vehicle monitoring system may use more than one set of monitoring parameters, criteria or thresholds. For example, two sets of speeding and acceleration criteria may be used by the vehicle monitoring system to adjust the operation of the vehicle monitoring system in two different locations. One set of criteria may allow the driver to exceed speed limits by 5 MPH without warning and may set the acceleration limitations higher to allow the driver to drive more aggressively in most cities. However, if one city is known to have speed traps or to write more tickets, the vehicle monitoring system may be configured to use a different, more restrictive set of monitoring criteria in that city. Using a geofence, the boundaries of the city with speed traps may be identified to the monitoring system. When the vehicle enters that geofenced area, the monitoring system may be configured to switch to the more restrictive monitoring criteria. Using the present invention, a geofence can be established around any location and a unique set of vehicle monitoring criteria can be configured for each geofence area. Any vehicle or driver parameters that are monitored by the vehicle monitoring system may be configured specifically for a particular area.



FIG. 2 illustrates one embodiment of the invention in which a vehicle monitoring system uses different sets of monitoring criteria or thresholds in different locations. Map 200 represents a geographic area, such as, for example, a metropolitan area or city. Zone of interest 201 has been defined with in the metropolitan area. Zone 201 is bounded by highways 21-24 in the example of FIG. 2. It will be understood that any geographic or other reference may be used to define a zone of interest, such as a state or interstate highway, main thoroughfare, side street, state/city/county line or other governmental boundary, building, parking lot, industrial complex, river, lake, shoreline, natural terrain feature, geographic coordinates (e.g. latitude/longitude), or the like. Zone of interest 201 is defined by boundary 202 in the illustrated example. Boundary 202 may be drawn as an overlay on map 200, for example, and may be represented by a series of points used to define segments of boundary line 202. Although only one zone of interest is illustrated in FIG. 2, it will be understood that any number of such zones may be defined for use with the present invention. Moreover, by defining zone of interest 201, area 203 also has been defined—i.e. as being outside of area 201.


In an embodiment of the invention, a vehicle monitoring system is configured to operate using a first set of parameters when a vehicle is within zone 201 and using a second set of parameters when the vehicle is in zone 203 (i.e. when it is outside of zone 201). The first parameters may define a restrictive set of operating criteria or thresholds to be used within zone 201, while the second set of parameters may define a “normal” set of operating criteria or thresholds to be used in other areas. For example, the vehicle may be a taxi or bus for which zone 201 is its assigned working area. The bus or taxi operating company may want to more strictly regulate, monitor or control vehicles within zone 201. Accordingly, the monitoring criteria and thresholds used within zone 201 may reflect that higher level of scrutiny. Within zone 201, the monitoring thresholds may be set to generate mentoring feedback or warnings to the driver if speeds in excess of a posted limit to any amount are detected. On the other hand, when operating outside of zone 201 (i.e. in area 203), the monitoring thresholds may allow for some excess speed, such as 10 MPH over posted speed limits, without generating mentoring feedback or a warning. In other embodiments, the monitoring criteria may provide a grace period to correct excess speeds outside zone 201, but require immediate correction within area 201.


In other embodiments, the operating parameters that are monitored may differ depending upon whether the vehicle is inside zone 201 or in zone 203. For example, if the monitored vehicle is a taxi or bus that is picking up passengers within zone 201, the monitoring system may be configured to record information associated with the passenger entry/exit from the vehicle. The monitoring system, upon detecting that it is within zone of interest 201, may be configured to record information each time a vehicle door is opened or each time the vehicle stops, such as recording video and/or audio of the passengers and driver or determining if a fare meter has started or stopped. When operating outside of zone 201, the monitoring system may be configured so that it does not record such information upon a vehicle door opening or at vehicle stops, if, for example, the vehicle is out-of-service or off duty when operating in area 203.


It will be understood that the present invention is not limited to the specific types of vehicles, geofences, or zones of interest that are used in the examples herein. The invention may be applied to vehicle monitoring systems in a large number of vehicles of different types. Geofenced areas or zones of interest may be defined around hospitals, schools, parks, or other public safety zones. A particular set of monitoring criteria may be established for these public safety zones so that drivers receive additional or more frequent mentoring feedback in these zones. For example, drivers in any type of vehicle may receive warnings immediately upon exceeding a posted speed limit while operating within these public safety zones, wherein their vehicle monitoring system may otherwise allow them some grace period when operating outside the public safety zones.


As noted above, a plurality of zones of interest, such as zone 201, may be created. A vehicle monitoring system may use a different set of criteria in each of the zones. Alternatively, the vehicle monitoring system may have a two or more predetermined sets of operating criteria and each zone may be linked to one or more of these sets of operating criteria. When the vehicle monitoring system determines that the vehicle has entered a new zone, it will then determine which set or sets of operating criteria or thresholds to apply in that zone.



FIG. 3 illustrates an alternative embodiment of the invention in which zone of interest 301 is defined on map 300 by boundary 302. Zone 301 includes roads 31-36 so that when a vehicle is operating on roads 31-36, the vehicle is considered to be in zone 301. The area outside of zone 301 is labeled as area 303. When the vehicle is operating on roads other than 31-36, such as when the vehicle is on roads 37-39, or is anywhere else outside of zone 301, the vehicle is in area 303. Zone 301 may represent, for example, an assigned or approved route. When the vehicle is operating in zone 301, such as on an assigned route, the vehicle monitoring system may use a first set of operating parameters. When the vehicle is operating in zone 303, or outside of zone 301, then the vehicle monitoring system may use a second set of operating parameters.


For example, a vehicle, such as a bus, street sweeper, garbage truck, or delivery truck, may be assigned to a particular route that is within zone 301. When the vehicle is on its route, a vehicle monitoring system may determine that it is within zone 301 using, for example, a current vehicle location from a GPS unit. While on the route and, therefore, within zone 301, the vehicle monitoring system will use an on-route set of vehicle monitoring parameters. In one embodiment, such on-route parameters may include specific requirements for vehicle speeds and accelerations, or limit or require the use of seatbelts, cellular telephones, turn signals, or other vehicle operations. When operating off of the assigned route and, therefore, outside of zone 301, the vehicle monitoring system may use a second set of parameters for zone 303. The second set of parameters may be more or less restrictive than the first set of parameters and/or may provide for monitoring of more or less parameters than the first set of parameters. For example, seatbelt use may be monitored in zone 301, but not in zone 303; and speed and acceleration criteria may generate mentoring feedback at lower thresholds in zone 301 than in zone 303.


It will be understood that multiple zones of interest or geofences for various routes may be used in addition to the single zone of interest or geofence illustrated in FIG. 3. Moreover, a single zone of interest or geofence may cover one or more routes or may cover partial routes. Additionally, a single route or partial route may be covered by one or more zones of interest or geofences. In other embodiments, zones of interest covering a route, such as zone 301, may be defined and used in the same system as zones of interest covering larger geographic areas, such as zone 201. For example, a vehicle monitoring system may have three sets of criteria, a first set for use inside zone 201, a second set for use in zone 301, and a third set for areas outside both zones 201 and 301. In the event that two geofences or zones of interest overlap in whole or in part so that a vehicle may be in an location that is linked to two different sets of monitoring parameters, criteria or thresholds, the vehicle monitoring system may be configured to select one set of monitoring parameters over the other. For example, referring to the zones illustrated in FIGS. 2 and 3, zone 301 overlaps zone 203 and, therefore, a vehicle monitoring system may have to select between criteria for zone 301 and criteria for zone 203. The vehicle monitoring system may be configured to select the more restrictive or the less restrictive monitoring parameters, criteria or thresholds. Alternatively, the vehicle monitoring system may be configured to select the group of monitoring parameters, criteria or thresholds that are established for the smaller zone or a more specifically defined zone, such as selecting criteria for zone 301 over criteria for zone 203.


In other embodiments of the present invention, the vehicle monitoring system may be used in a racing or competitive environment. Speedway 400 is illustrated in FIG. 4 having racetrack 401 and pit road 402. Infield 403 may be grass or paved, such as infield roads 404 which allow support vehicles to move around the speedway without interfering with vehicles on the racetrack. Racetrack 401 includes four turns designated generally as 41-44. A start/finish line 405 is used to identify the start and finish point for races. Although speedway 400 illustrates a motor vehicle racetrack, such as Phoenix International Raceway, it will be understood that the present invention can be used on any speedway or racetrack, including, for example, any paved, grass, turf, dirt, man-made or natural course. The present invention can also be used on land, sea, or in the air (and space). Moreover, the present invention may be used with any vehicle or animal competitors, including, for example, cars, trucks, motorcycles, trains, planes, boats, bicycles, carts, horses, dogs, and humans. It will be further understood that the present invention, although illustrated by examples from a racing environment, is useable in any other competitive or non-competitive environment or any public, private or government enterprise or business and, therefore, should not be considered to be limited by the exemplary embodiments discussed herein.


As is well known, during a race the competitors begin at the starting line 405 and travel around racetrack 401 one or more times depending upon the length of racetrack 401 and the length of the race. Typically, the race is equated to a number of laps, such as a 200 mile race that requires 100 laps on a two-mile racetrack. Each time a competitor passes start/finish line 405, another lap is counted. As the race progresses, some competitors may fall behind by one or more laps and, as a result, the counting of laps for individual competitors may become more difficult as the race progresses.



FIG. 5A is a detailed illustration of portion 406 of speedway 400 near start/finish line 405. In one embodiment of the invention, geofence 501 is created around start/finish line 405. Geofence 501 is a polygon that may be created, for example, by designating a latitude and longitude for points 51-54, which are the vertices of the polygon having sides 502a-d. It will be understood that the size of geofence 501 may be matched exactly to the size of start/finish line 405 or may be larger or smaller than finish line 405 as desired. The monitoring system may be configured to record when competitors having a monitoring device pass though geofence 501. The number of times that a competitor passes through geofence 501 may be tracked and the data can be used to determine lap counts, lap split times, elapsed race times, average speed, trajectory, and other data. An in-vehicle monitoring system may track the number of laps and the associated times and/or this information may be forwarded to a central server or database, such as server 109 or database 110 in FIG. 1. A central server that collects lap count data from each competitor may provide centralized race information to users, such as via terminal 111 or a network or Internet connection. This information would allow a race authority to determine, how far and how many laps each competitor had traveled at any time and how much farther each competitor had to go. The data could be stored for historical analysis, such as average lap speeds or to review lap times and competitor order for each lap.



FIG. 5B illustrates an alternate embodiment in which start/finish line 405 is covered by two geofences 503 and 504, which may be creates in the same manner as geofence 501. By establishing two geofences 503 and 504 to cover start/finish line 405, the monitoring system would be able to determine and record whether the competitor had passed the finish line while on racetrack 401 or on pit road 402. This would allow the system to automatically count laps and to automatically determine when a competitor made a pit stop. It will be understood that geofence 501, 503 and 504 may be further divided as needed to provide additional information. For example, geofence 504 may be divided into multiple sections along start/finish line 405 between inside 505 and wall 506, which would provide additional information such as whether the competitor passed the start/finish line on the inside, middle or outside section of racetrack 401.


It will be further understood that in other embodiments, a geofence area such as 501, 503 and 504 may be established anywhere on racetrack 401, such as in turns 41-44 or on backstretch 401b (FIG. 4). This would allow for the automatic collection of additional data, such as partial lap split times, relative speeds between competitors, and relative order between competitors, for example. The present invention may also be used to designate specific areas on racetrack 401, pit road 402, infield 403, or infield road 404 to determine if a competitor ever passed over that area. For example, a geofence area could be established on the inside of a turn to determine if any, or to count how many, competitors used that line on racetrack 401. Additionally, geofence zones may be established for each competitor's pit area so that a central server was notified each time a competitor stopped in their pit.


Using embodiments of the present invention, wherein the start/finish line, pit areas, and other portions of the track are designated with geofences, each vehicle monitoring device could report to the central server when it passes through and/or stops in a geofence area. The location reports from the competitors' monitoring system may include an “in-zone” message upon entering the geofence area and an “out-of-zone” message upon leaving the geofence area. If the vehicle monitoring system sees these two events happen quickly, then it may transmit a location report of a transient event or with a combined in-zone and out-of-zone information.


Table 1 is illustrates exemplary vehicle reports for a track in which geofences have been set up at the start/finish line, halfway through each turn, in the middle of the backstretch, at the pit road start/finish line, and at each competitor's pit. The geofenced zones on the track have been further divided into three zones from the inside of the track to the wall to determine if the competitor passes each zone low on the inside, in the middle, or high on the wall. Each time a competitor enters, passes through, or stops in a geofenced zone, a report is sent to a central server with location information. Table 1 illustrates the type of messages that could be received by the central server from each competitor.












TABLE 1






Competitor
Time
Report








1
12:05:31
Pass Pit Road Start/Finish Line



2
12:05:33
Pass Start/Finish Line—High



1
12:05:33
In Pit



3
12:05:34
Turn 4—Middle



2
12:05:37
Turn 1—Middle



3
12:05:38
Pass Start/Finish Line—Middle



3
12:05:42
Turn 1—Low



2
12:05:44
Turn 2—Middle



2
12:05:48
Backstretch—High



3
12:05:50
Turn 2—High



2
12:05:52
Turn 3—Middle



1
12:05:54
Out of Pit



3
12:05:57
Turn 3—Middle



2
12:05:58
Turn 4—Low



1
12:05:01
Turn 2—Low



3
12:05:01
Backstretch—High



2
12:05:02
Pass Start/Finish Line—High









Although the time shown in Table 1 is in hours:minutes:seconds, it will be understood that based upon the type of competition, further precision may be available, such as tenths, hundredths or thousandths of seconds at each point. Additionally, although only three competitors are shown in Table 1, it will be understood that the number of competitors that can be tracked the by present invention is unlimited.


Table 2 illustrates information available to a race authority based upon the geofence reports from the competitors. The information in Table 2 is available for as static information at specific times or may be dynamic information in which the display is updated with each competitor's location report. Cross referencing to the example above in Table 1, at time 12:05:50, a race authority could see the information illustrated in Table 2 based upon the competitors' most recent reports.















TABLE 2











Average







Last Lap
Lap


Com-

Track
Elapsed
Elapsed
Time/
Time/


petitor
Lap
Position
Time
Lap
Speed
Speed







1
52
Pit
48.53

27.9/132
26.9/132


2
52
Backstretch
48.53
14.5
27.8/132
27.8/132


3
52
Turn 2
48.53
12.1
28.5/133
27.5/132









Additional information may be included in the vehicle position reports, such as current speeds and accelerations as well as current engine parameters. This and other information may also be displayed in addition to or in place of the data in Table 2. Preferably, a database, such as database 110, coupled to the central server stores the received location reports for later recall and analysis. A race authority may select information of interest and configure a display, such as on terminal 111, so that the desired information is updated as it is received by the central server. Alternatively, the display may be updated at regular intervals, such as every 5, 10, 15 or 30 seconds depending upon the user's requirements. The information may also be made available to third parties, such as via an Internet website for free or by subscription so that race teams, the media, fans and other interested parties can access the information.


In addition to the competitors, other vehicles, animals and/or people, use racetrack 401, pit road 402 and infield roads 404. For example, pace cars may be used to lead cars around racetrack 401 before the race begins or emergency vehicles, such as ambulances, fire trucks, or wreckers may enter racetrack 401 to assist following a vehicle crash. Before the race can begin or continue after a crash, for example, it is important that racetrack 401 is clear of all vehicles, animals and/or people other than the competitors. Emergency vehicle staging areas or safety areas are designated in infield 403 and, when the race is in progress, all emergency vehicles are required to be in their assigned staging area. FIG. 6 is a detailed illustration of portion 407 near turn 2 of speedway 400. Safety area or staging area 601 provides a location for emergency vehicles to park that is clear of racetrack 401 and pit road 402 while remaining close to racetrack 401 in the event of a crash. Other staging areas in infield 403 or near turns 41, 43, or 44 may also be used in other configurations.


Currently, in NASCAR race events, for example, spotters are assigned to watch emergency vehicles. The spotters are used to prevent a race from commencing or continuing while non-competitors are still on racetrack 401. Before the competitors can begin racing, as indicated by a “green flag,” each spotter must visually confirm that his or her assigned emergency vehicle/s is/are within their assigned staging area, such as staging area 601, and report this information to a racetrack authority. Once all the spotters have reported that their assigned emergency vehicles are within the designated staging areas, the competitors are allowed to return to “green flag racing.”



FIG. 7 illustrates one embodiment of the invention in which geofence area 701 is defined to overlap staging area 601. Geofence area 701 is defined by segments 702a-702j that link vertices 70-79. Geofence area 701 may be formed using a drawing tool similar to the Microsoft® Paint polygon tool in which point 70 is selected as an origin using a pointer such as a mouse. Segment 702a is drawing by dragging the pointer to a new location and clicking the pointer to fix the location of point 71. Segments 702b-702i are formed the same way by dragging the pointer and clicking at points 72-79. The number of points or nodes must be at least 3 (sufficient to define a region rather than a line). The geofence area is finished by dragging the pointer to point 70 and clicking or double-clicking to form segment 702j. The geofence area may be created, for example, as an overlay to a mapping program, such as Google™ Maps that allows the user to view a map of an area, or a satellite picture of the area, or a combination of both.



FIG. 8 illustrates an alternative method for geofencing a staging area using a circular geofence 801. FIG. 9 illustrates another alternative method for geofencing a staging area using a rectangular geofence 901. As shown in FIGS. 8 and 9, using a standard circular or rectangular geofence does not allow one to accurately mark the desired geofence area for irregularly shaped areas. Areas 802-805 and 902-905, which are part of the desired staging area 601, are not adequately covered by the standard geofence techniques. Accordingly, it is preferred to use a geofence tool such as that illustrated in FIG. 7 wherein a multi-sided irregular polygon can be created to more accurately designate the desired area.


Table 3 illustrates one embodiment of the present invention, in which a track supervisor or race authority may determine whether each emergency vehicle, pace car, or other vehicle that may be authorized to be on the track during non-race conditions, such as under a “yellow flag” or caution. The vehicle monitoring system will report to the central server when the vehicle is in an assigned staging area. The central server will make that information available to users, for example, via a user terminal or a network or Internet connection. This allows a single individual to quickly determine if the racetrack is ready for the race to commence or continue. If, for example, vehicles 5 and 6, two wreckers, are still moving competitors off the racetrack following a crash and are not in their staging area, it will be quickly apparent from the emergency vehicle location report in Table 3. A vehicle that is out of the staging area may be designated as “not ready,” “out of area” or by some other characterization.











TABLE 3





Vehicle
Vehicle Type
Location

















1
Supervisor
Staging Area 1


2
Fire Truck
Staging Area 1


3
Fire Truck
Staging Area 1


4
Ambulance
Staging Area 1


5
Wrecker
NOT READY


6
Wrecker
NOT READY


7
Fire Truck
Staging Area 2


8
Fire Truck
Staging Area 2


9
Ambulance
Staging Area 2


10
Ambulance
Staging Area 2


11
Wrecker
Staging Area 2


12
Wrecker
Staging Area 2


13
Pace Car
Staging Area 2









In an alternative embodiment, racetrack 401, infield 403, the pit area and other areas in the speedway may be designated by geofence areas. This would allow additional information to be presented to the user. For example, if the wreckers 5 and 6 were not in the staging area, instead of merely noting that these vehicles were not ready, the monitoring system may notify a track authority as to their actual location, such as “on racetrack,” “in pit area,” or “infield area.” This additional information would allow the track authority to decide if the race should commence or continue. For example, a race would not resume with wreckers on the racetrack, but a restart may be acceptable if the vehicles were off the racetrack in the infield or pit area, but not yet in the staging area.



FIG. 10 is a flowchart illustrating one process for implementing the invention. In step 1001, an asset monitoring system determines if the asset is within a geofence area. The asset may be a vehicle that is tracked using a vehicle monitoring system. In step 1002, if the asset within the geofence area, then a first set of asset monitoring parameters are used to monitor the operation of the asset. In step 1003, if the asset is outside the geofence area, then a second set of monitoring parameters are used to monitor operation of the asset. Multiple geofence areas may be created each with its own set of monitoring parameters so that the asset monitoring system operates different in each geofenced area.



FIG. 11 is flowchart illustrating an alternative embodiment of the invention. In step 1101, one or more competitors are provided with an asset tracking device. The asset tracking device allows the location of each competitor to be monitored. In step 1102, one or more geofence areas on a racetrack are defined. In step 1103, it is determined whether the competitor has entered one of the geofenced areas.



FIG. 12 is a flowchart illustrating another embodiment of the invention. In step 1201 one or more non-competitors are provided with an asset tracking device. The asset tracking device allows the location of the non-competitor to be monitored. In step 1202, one or more geofence areas are defined off of a racetrack. In step 1203, it is determined whether the non-competitors are within the one or more off-track geofence areas.


Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims
  • 1. A method of tracking events in a race, comprising: receiving a geoposition from one or more competitors, each competitor using an asset tracking device that allows each competitor's location to be determined; and;based on the received geoposition from the competitors, determining when the competitors enter one or more geofence areas on a racetrack, the one or more geofence areas defined by a virtual perimeter.
  • 2. The method of claim 1, further comprising: determining when the competitors leave the designated geofence area.
  • 3. The method of claim 1, wherein the step of determining when the competitors enter the one or more geofence areas is performed without regard to whether the competitors stop in or pass through the designated geofence area.
  • 4. The method of claim 1, wherein one of the geofence areas defines a virtual perimeter coincident with the finish line.
  • 5. The method of claim 4, further comprising: counting a number of times each competitor enters the designated geofence area.
  • 6. The method of claim 1, wherein the one or more geofence areas includes a pit area.
  • 7. The method of claim 1, wherein the competitors are motor-powered vehicles.
  • 8. The method of claim 1, wherein the competitors are human-powered vehicles.
  • 9. The method of claim 1, wherein the competitors are electro-mechanical devices.
  • 10. The method of claim 1, wherein the competitors are selected from the group consisting of: bicycles, cars, trucks, planes, boats, trains, or robots.
  • 11. The method of claim 1, wherein the competitors are animals.
US Referenced Citations (429)
Number Name Date Kind
3714649 Brouwer et al. Jan 1973 A
3975708 Lusk Aug 1976 A
4369427 Drebinger et al. Jan 1983 A
4395624 Wartski Jul 1983 A
4419654 Funk Dec 1983 A
4458535 Juergens Jul 1984 A
4785280 Fubini Nov 1988 A
4823367 Kreutzfeld Apr 1989 A
4926417 Futami May 1990 A
4939652 Steiner Jul 1990 A
5032821 Domanico Jul 1991 A
5119504 Durboraw, III Jun 1992 A
5223844 Mansell et al. Jun 1993 A
5225842 Brown et al. Jul 1993 A
5305214 Komatsu Apr 1994 A
5309139 Austin May 1994 A
5311197 Sorden et al. May 1994 A
5325082 Rodriguez Jun 1994 A
5347260 Ginzel Sep 1994 A
5359528 Haendel Oct 1994 A
5365114 Tsurushima Nov 1994 A
5365451 Wang et al. Nov 1994 A
5394136 Lammers Feb 1995 A
5400018 Scholl Mar 1995 A
5414432 Penny, Jr. et al. May 1995 A
5422624 Smith Jun 1995 A
5424584 Matsuda Jun 1995 A
5430432 Camhi Jul 1995 A
5436612 Aduddell Jul 1995 A
5436837 Gerstung Jul 1995 A
5446659 Yamawaki Aug 1995 A
5453939 Hoffman Sep 1995 A
5457439 Kuhn Oct 1995 A
5475597 Buck Dec 1995 A
5485161 Vaughn Jan 1996 A
5499182 Ousborne Mar 1996 A
5511045 Sasaki et al. Apr 1996 A
5521579 Bernhard May 1996 A
5521580 Kaneko May 1996 A
5525960 McCall Jun 1996 A
5548273 Nicol Aug 1996 A
5581464 Woll Dec 1996 A
5586130 Doyle Dec 1996 A
5600558 Mearek Feb 1997 A
5612875 Haendel Mar 1997 A
5625337 Medawar Apr 1997 A
5638077 Martin Jun 1997 A
5642284 Parupalli Jun 1997 A
5648755 Yagihashi Jul 1997 A
5659289 Zonkoski Aug 1997 A
5689067 Klein Nov 1997 A
5708417 Tallman Jan 1998 A
5717374 Smith Feb 1998 A
5719771 Buck Feb 1998 A
5723768 Ammon Mar 1998 A
5737280 Kokubo Apr 1998 A
5740548 Hudgens Apr 1998 A
5742915 Stafford Apr 1998 A
5751245 Janky et al. May 1998 A
5764139 Nojima Jun 1998 A
5767767 Lima Jun 1998 A
5777580 Janky et al. Jul 1998 A
5795997 Gittins Aug 1998 A
5797134 McMillan et al. Aug 1998 A
5801618 Jenkins Sep 1998 A
5801948 Wood Sep 1998 A
5815071 Doyle Sep 1998 A
5825283 Camhi Oct 1998 A
5825284 Dunwoody Oct 1998 A
5844475 Horie Dec 1998 A
5847271 Poublon Dec 1998 A
5862500 Goodwin Jan 1999 A
5867093 Dodd Feb 1999 A
5877678 Donoho Mar 1999 A
5880674 Ufkes Mar 1999 A
5880958 Helms et al. Mar 1999 A
5883594 Lau Mar 1999 A
5892434 Carlson Apr 1999 A
5907277 Tokunaga May 1999 A
5914654 Smith Jun 1999 A
5918180 Dimino Jun 1999 A
5926087 Busch Jul 1999 A
5928291 Jenkins et al. Jul 1999 A
5945919 Trask Aug 1999 A
5949330 Hoffman Sep 1999 A
5949331 Schofield Sep 1999 A
5954781 Slepian Sep 1999 A
5955942 Slifkin Sep 1999 A
5957986 Coverdill Sep 1999 A
5964816 Kincaid Oct 1999 A
5969600 Tanguay Oct 1999 A
5974356 Doyle et al. Oct 1999 A
5978737 Pawlowski Nov 1999 A
5982278 Cuvelier Nov 1999 A
5987976 Sarangapani Nov 1999 A
5999125 Kurby Dec 1999 A
6002327 Boesch Dec 1999 A
6008724 Thompson Dec 1999 A
6018293 Smith Jan 2000 A
6026292 Coppinger et al. Feb 2000 A
6028508 Mason Feb 2000 A
6028510 Tamam Feb 2000 A
6037861 Ying Mar 2000 A
6037862 Ying Mar 2000 A
6038496 Dobler Mar 2000 A
6044315 Honeck Mar 2000 A
6059066 Lary May 2000 A
6064928 Wilson May 2000 A
6064970 McMillan et al. May 2000 A
6067008 Smith May 2000 A
6067009 Hozuka May 2000 A
6072388 Kyrtsos Jun 2000 A
6073007 Doyle Jun 2000 A
6075458 Ladner et al. Jun 2000 A
6078853 Ebner Jun 2000 A
6081188 Kutlucinar Jun 2000 A
6084870 Wooten et al. Jul 2000 A
6094149 Wilson Jul 2000 A
6098048 Dashefsky Aug 2000 A
6100792 Ogino Aug 2000 A
6104282 Fragoso Aug 2000 A
6108591 Segal et al. Aug 2000 A
6121922 Mohan Sep 2000 A
6124810 Segal et al. Sep 2000 A
6130608 McKeown Oct 2000 A
6131067 Girerd et al. Oct 2000 A
6133827 Alvey Oct 2000 A
6141610 Rothert Oct 2000 A
6147598 Murphy Nov 2000 A
6172602 Hasfjord Jan 2001 B1
6184784 Shibuya Feb 2001 B1
6185501 Smith Feb 2001 B1
6198995 Settles Mar 2001 B1
6204756 Senyk Mar 2001 B1
6204757 Evans Mar 2001 B1
6208240 Ledesma Mar 2001 B1
6212455 Weaver Apr 2001 B1
6216066 Goebel Apr 2001 B1
6222458 Harris Apr 2001 B1
6225898 Kamiya May 2001 B1
6227862 Harkness May 2001 B1
6229438 Kutlucinar May 2001 B1
6232873 Dilz May 2001 B1
6246933 Bague Jun 2001 B1
6247360 Anderson Jun 2001 B1
6249219 Perez Jun 2001 B1
6253129 Jenkins et al. Jun 2001 B1
6255892 Gartner Jul 2001 B1
6255939 Roth Jul 2001 B1
6262658 O'Connor Jul 2001 B1
6265989 Taylor Jul 2001 B1
6266588 McClellan Jul 2001 B1
6278361 Magiawala Aug 2001 B1
6285931 Hattori Sep 2001 B1
6289332 Menig Sep 2001 B2
6294988 Shomura Sep 2001 B1
6294989 Schofield Sep 2001 B1
6295492 Lang Sep 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6301533 Markow Oct 2001 B1
6308120 Good Oct 2001 B1
6308134 Croyle et al. Oct 2001 B1
6313742 Larson Nov 2001 B1
6320497 Fukumoto Nov 2001 B1
6331825 Ladner et al. Dec 2001 B1
6333686 Waltzer Dec 2001 B1
6337653 Buchler et al. Jan 2002 B1
6339739 Folke Jan 2002 B1
6344805 Yasui Feb 2002 B1
6351211 Bussard Feb 2002 B1
6356188 Meyers Mar 2002 B1
6356822 Diaz Mar 2002 B1
6356833 Jeon Mar 2002 B2
6359554 Skibinski Mar 2002 B1
6362730 Razavi Mar 2002 B2
6362734 McQuade Mar 2002 B1
6366199 Osborn Apr 2002 B1
6378959 Lesesky Apr 2002 B2
6389340 Rayner May 2002 B1
6393348 Ziegler May 2002 B1
6404329 Hsu Jun 2002 B1
6405112 Rayner Jun 2002 B1
6424268 Isonaga Jul 2002 B1
6427687 Kirk Aug 2002 B1
6430488 Goldman Aug 2002 B1
6433681 Foo Aug 2002 B1
6441732 Laitsaari Aug 2002 B1
6449540 Rayner Sep 2002 B1
6459367 Green Oct 2002 B1
6459369 Wang Oct 2002 B1
6459961 Obradovich Oct 2002 B1
6459969 Bates Oct 2002 B1
6462675 Humphrey Oct 2002 B1
6472979 Schofield Oct 2002 B2
6476763 Allen, Jr. Nov 2002 B2
6480106 Crombez Nov 2002 B1
6484035 Allen, Jr. Nov 2002 B2
6484091 Shibata Nov 2002 B2
6493650 Rodgers Dec 2002 B1
6512969 Wang Jan 2003 B1
6515596 Awada Feb 2003 B2
6519512 Haas Feb 2003 B1
6525672 Chainer Feb 2003 B2
6526341 Bird et al. Feb 2003 B1
6529159 Fan et al. Mar 2003 B1
6535116 Zhou Mar 2003 B1
6542074 Tharman Apr 2003 B1
6542794 Obradovich Apr 2003 B2
6549834 McClellan Apr 2003 B2
6552682 Fan Apr 2003 B1
6556905 Mittelsteadt Apr 2003 B1
6559769 Anthony May 2003 B2
6564126 Lin May 2003 B1
6567000 Slifkin May 2003 B2
6571168 Murphy May 2003 B1
6587759 Obradovich Jul 2003 B2
6594579 Lowrey Jul 2003 B1
6599243 Woltermann Jul 2003 B2
6600985 Weaver Jul 2003 B2
6604033 Banet Aug 2003 B1
6611740 Lowrey Aug 2003 B2
6611755 Coffee Aug 2003 B1
6629029 Giles Sep 2003 B1
6630884 Shanmugham Oct 2003 B1
6636790 Lightner Oct 2003 B1
6639512 Lee Oct 2003 B1
6643578 Levine Nov 2003 B2
6651001 Apsell Nov 2003 B2
6654682 Kane et al. Nov 2003 B2
6657540 Knapp Dec 2003 B2
6662013 Takiguchi et al. Dec 2003 B2
6664922 Fan Dec 2003 B1
6665613 Duvall Dec 2003 B2
6674362 Yoshioka Jan 2004 B2
6675085 Straub Jan 2004 B2
6677854 Dix Jan 2004 B2
6678612 Khawam Jan 2004 B1
6696932 Skibinski Feb 2004 B2
6703925 Steffel Mar 2004 B2
6710738 Allen, Jr. Mar 2004 B2
6718235 Borugian Apr 2004 B1
6718239 Rayner Apr 2004 B2
6727809 Smith Apr 2004 B1
6728605 Lash Apr 2004 B2
6732031 Lightner May 2004 B1
6732032 Banet May 2004 B1
6737962 Mayor May 2004 B2
6741169 Magiawala May 2004 B2
6741170 Alrabady May 2004 B2
6745153 White Jun 2004 B2
6748322 Fernandez Jun 2004 B1
6750761 Newman Jun 2004 B1
6750762 Porter Jun 2004 B1
6756916 Yanai Jun 2004 B2
6759952 Dunbridge Jul 2004 B2
6768448 Farmer Jul 2004 B2
6775602 Gordon Aug 2004 B2
6778068 Wolfe Aug 2004 B2
6778885 Agashe et al. Aug 2004 B2
6784793 Gagnon Aug 2004 B2
6784832 Knockeart et al. Aug 2004 B2
6788196 Ueda Sep 2004 B2
6788207 Wilkerson Sep 2004 B2
6792339 Basson Sep 2004 B2
6795017 Puranik et al. Sep 2004 B1
6798354 Schuessler Sep 2004 B2
6803854 Adams et al. Oct 2004 B1
6807481 Gastelum Oct 2004 B1
6813549 Good Nov 2004 B2
6819236 Kawai Nov 2004 B2
6832141 Skeen et al. Dec 2004 B2
6845314 Fosseen Jan 2005 B2
6845317 Craine Jan 2005 B2
6847872 Bodin Jan 2005 B2
6847873 Li Jan 2005 B1
6859039 Horie Feb 2005 B2
6859695 Klausner Feb 2005 B2
6865457 Mittelsteadt Mar 2005 B1
6867733 Sandhu et al. Mar 2005 B2
6868386 Henderson et al. Mar 2005 B1
6870469 Ueda Mar 2005 B2
6873253 Veziris Mar 2005 B2
6873261 Anthony Mar 2005 B2
6879894 Lightner Apr 2005 B1
6885293 Okumura Apr 2005 B2
6892131 Coffee May 2005 B2
6895332 King May 2005 B2
6909398 Knockeart et al. Jun 2005 B2
6914523 Munch Jul 2005 B2
6922133 Wolfe Jul 2005 B2
6922616 Obradovich Jul 2005 B2
6922622 Dulin Jul 2005 B2
6925425 Remboski Aug 2005 B2
6928348 Lightner Aug 2005 B1
6937162 Tokitsu Aug 2005 B2
6950013 Scaman Sep 2005 B2
6954140 Holler Oct 2005 B2
6958976 Kikkawa Oct 2005 B2
6968311 Knockeart et al. Nov 2005 B2
6970075 Cherouny Nov 2005 B2
6970783 Knockeart et al. Nov 2005 B2
6972669 Saito Dec 2005 B2
6980131 Taylor Dec 2005 B1
6981565 Gleacher Jan 2006 B2
6982636 Bennie Jan 2006 B1
6983200 Bodin Jan 2006 B2
6988033 Lowrey Jan 2006 B1
6989739 Li Jan 2006 B2
7002454 Gustafson Feb 2006 B1
7002579 Olson Feb 2006 B2
7005975 Lehner Feb 2006 B2
7006820 Parker et al. Feb 2006 B1
7019641 Lakshmanan Mar 2006 B1
7023321 Brillon et al. Apr 2006 B2
7023332 Saito Apr 2006 B2
7024318 Fischer Apr 2006 B2
7027808 Wesby Apr 2006 B2
7034705 Yoshioka Apr 2006 B2
7038578 Will May 2006 B2
7042347 Cherouny May 2006 B2
7047114 Rogers May 2006 B1
7049941 Rivera-Cintron May 2006 B2
7059689 Lesesky Jun 2006 B2
7069126 Bernard Jun 2006 B2
7069134 Williams Jun 2006 B2
7072753 Eberle Jul 2006 B2
7081811 Johnston Jul 2006 B2
7084755 Nord Aug 2006 B1
7088225 Yoshioka Aug 2006 B2
7089116 Smith Aug 2006 B2
7091880 Sorensen Aug 2006 B2
7098812 Hirota Aug 2006 B2
7099750 Miyazawa Aug 2006 B2
7099774 King Aug 2006 B2
7102496 Ernst Sep 2006 B1
7109853 Mattson Sep 2006 B1
7113081 Reichow Sep 2006 B1
7113107 Taylor Sep 2006 B2
7117075 Larschan et al. Oct 2006 B1
7119696 Borugian Oct 2006 B2
7124027 Ernst Oct 2006 B1
7124088 Bauer et al. Oct 2006 B2
7129825 Weber Oct 2006 B2
7132934 Allison Nov 2006 B2
7132937 Lu Nov 2006 B2
7132938 Suzuki Nov 2006 B2
7133755 Salman Nov 2006 B2
7135983 Filippov Nov 2006 B2
7138916 Schwartz Nov 2006 B2
7139661 Holze Nov 2006 B2
7145442 Wai Dec 2006 B1
7149206 Pruzan Dec 2006 B2
7161473 Hoshal Jan 2007 B2
7164986 Humphries Jan 2007 B2
7170390 Quiñones Jan 2007 B2
7170400 Cowelchuk Jan 2007 B2
7174243 Lightner Feb 2007 B1
7180407 Guo Feb 2007 B1
7180409 Brey Feb 2007 B2
7187271 Nagata Mar 2007 B2
7196629 Ruoss Mar 2007 B2
7216035 Hörtner May 2007 B2
7218211 Ho May 2007 B2
7222009 Hijikata May 2007 B2
7225065 Hunt May 2007 B1
7228211 Lowrey Jun 2007 B1
7233235 Pavlish Jun 2007 B2
7236862 Kanno Jun 2007 B2
7239948 Nimmo Jul 2007 B2
7256686 Koutsky Aug 2007 B2
7256700 Ruocco Aug 2007 B1
7256702 Isaacs Aug 2007 B2
7260497 Watabe Aug 2007 B2
RE39845 Hasfjord Sep 2007 E
7269530 Lin Sep 2007 B1
7271716 Nou Sep 2007 B2
7273172 Olsen Sep 2007 B2
7280046 Berg Oct 2007 B2
7283904 Benjamin Oct 2007 B2
7286917 Hawkins Oct 2007 B2
7286929 Staton Oct 2007 B2
7289024 Sumcad Oct 2007 B2
7289035 Nathan Oct 2007 B2
7292152 Torkkola Nov 2007 B2
7292159 Culpepper Nov 2007 B2
7298248 Finley Nov 2007 B2
7298249 Avery Nov 2007 B2
7301445 Moughler Nov 2007 B2
7317383 Ihara Jan 2008 B2
7317392 DuRocher Jan 2008 B2
7317927 Staton Jan 2008 B2
7319848 Obradovich Jan 2008 B2
7321294 Mizumaki Jan 2008 B2
7321825 Ranalli Jan 2008 B2
7323972 Nobusawa Jan 2008 B2
7323974 Schmid Jan 2008 B2
7323982 Staton Jan 2008 B2
7327239 Gallant Feb 2008 B2
7327258 Fast Feb 2008 B2
7333883 Geborek Feb 2008 B2
7339460 Lane Mar 2008 B2
7349782 Churchill Mar 2008 B2
7352081 Taurasi Apr 2008 B2
7355508 Mian Apr 2008 B2
7365639 Yuhara Apr 2008 B2
7366551 Hartley Apr 2008 B1
7375624 Hines May 2008 B2
7376499 Salman May 2008 B2
7378946 Lahr May 2008 B2
7378949 Chen May 2008 B2
7386394 Shulman Jun 2008 B2
20030055555 Knockeart et al. Mar 2003 A1
20040039504 Coffee et al. Feb 2004 A1
20040066330 Knockeart et al. Apr 2004 A1
20040077339 Martens Apr 2004 A1
20040083041 Skeen et al. Apr 2004 A1
20040142672 Stankewitz Jul 2004 A1
20050064835 Gusler Mar 2005 A1
20050091018 Craft Apr 2005 A1
20050096809 Skeen et al. May 2005 A1
20050137757 Phelan et al. Jun 2005 A1
20060087427 Le Apr 2006 A1
20060154687 McDowell Jul 2006 A1
20060234711 McArdle Oct 2006 A1
20070229234 Smith Oct 2007 A1
20070293206 Lund Dec 2007 A1
20080036587 Meinzen et al. Feb 2008 A1
20080064413 Breed Mar 2008 A1
20080255888 Berkobin Oct 2008 A1
Foreign Referenced Citations (4)
Number Date Country
2071931 Dec 1993 CA
2007235530 Sep 2007 JP
WO2005109369 Nov 2005 WO
WO2008109477 Sep 2008 WO
Related Publications (1)
Number Date Country
20090009321 A1 Jan 2009 US