Governments, including state and federal governments, have traditionally funded public infrastructure projects from tax revenue derived from fuel taxes. States may tax fuel purchased not only by in-state drivers, but also by drivers that travel through the state. With the development and availability of hybrid and electric cars on the market, governments will need to consider new ways of deriving tax revenue to fund public infrastructure. Therefore, any invention which provides information related to calculating and collecting transportation taxes would be useful.
For a detailed description of exemplary embodiments, reference will now be made to the accompanying drawings in which:
Certain terms are used throughout the following description and claims to refer to particular system components. As one skilled in the art will appreciate, different companies may refer to a component and/or method by different names. This document does not intended to distinguish between components and/or methods that differ in name but not in function.
In the following discussion and in the claims, the terms “including” and “comprising” are used in an open-ended fashion, and thus should be interpreted to mean “including, but not limited to . . . .” Also, the term “couple” or “couples” is intended to mean either an indirect or direct connection. Thus, if a first device couples to a second device that connection may be through a direct connection or through an indirect connection via other devices and connections.
“Remote” shall mean one kilometer or more.
“Political Boundary” shall mean the geographic boundary of a political entity or legal jurisdiction.
The following discussion is directed to various embodiments of the invention. Although one or more of these embodiments may be preferred, the embodiments disclosed should not be interpreted, or otherwise used, as limiting the scope of the disclosure, including the claims. In addition, one skilled in the art will understand that the following description has broad application, and the discussion of any embodiment is meant only to be exemplary of that embodiment, and not intended to intimate that the scope of the disclosure, including the claims, is limited to that embodiment.
Various embodiments are directed to configuring and creating a geo-fence boundary corresponding to the size and shape of a political boundary once a vehicle is detected as having crossed into the area defined by the political boundary, as well as collecting data related to the movement of the vehicle within the geo-fence boundary. The specification first turns to an illustrative system.
The operations center 100 may further comprise a mapping module 110 coupled to the processor 102. In accordance with at least some embodiments, the mapping module 110 is a stand-alone computer system executing software to perform a mapping function associated with the location of the vehicle 120 and any geo-fence boundaries that may be established. In yet still other embodiments, the mapping module 110 may be a computer program or program package that operates or executes on the processor 102.
In order to communicate with the vehicle 120, the operations center may further comprise a network interface 108 communicatively coupled to the processor 102. By way of the network interface, the processor 102, and any programs executing thereon, may communicate with vehicle 120, such as by wireless network 112. Wireless network 112 is illustrative of any suitable communications network, such as a cellular network, a pager network, or other mechanism for transmitting information between the operations center 100 and the vehicle 120.
In accordance with at least some embodiments, the operations center 100 is remotely located from the vehicle 120. In some cases, the operations center 100 and vehicle 120 may be located within the same city or state. In other cases, the operations center 100 may be many hundreds or thousands of miles from vehicle 120, and thus the illustrative wireless network 112 may span several different types of communication networks.
Still referring to
The specification now turns to a high level description of detecting a vehicle is located within a political boundary and automatically establishing a geo-fence boundary corresponding to the political boundary. In particular,
Referring still to
Operations Center Establishment of the Geo-Fence
In some cases, mapping module 110 of the remote operations center 100 may play a role in establishing the geo-fence when vehicle 120 crosses into a political boundary. In particular, the mapping module may periodically receive information from the vehicle regarding vehicle location. In the example of
Vehicle Establishment of the Geo-Fence
In yet still other cases, systems within the vehicle 120 establish the geo-fence. In order to discuss embodiments of the vehicle establishing the geo-fence boundaries, the discussion turns briefly to a more detailed description of the monitoring system 124. In particular,
Regardless of how the geo-fence boundary is established, once the geo-fence boundary is established, in accordance with various embodiments data regarding movement of the vehicle 120 within the political boundary is collected. Thus, the specification now turns to example systems of collecting data regarding movement of the vehicle.
Tracking Mileage by Way of GPS and Vehicle
The GPS receiver 402, in addition to assisting with determining the location of the vehicle with respect to various political boundaries, in some cases also plays a role in collecting data regarding movement of the vehicle. For example, in some embodiments the GPS receiver 402 alone may track mileage driven by the vehicle 120 while the vehicle resides within the political jurisdiction. In yet still other cases, the GPS receiver 402 may work with the computer system 126 to track mileage driven. For example, the computer system 126 may receive periodic or continuous location information from the GPS receiver, and may use the information to calculate updated locations of the vehicle, and thus determine the amount of miles traveled between updates.
Tracking Mileage by Way of GPS and Operations Center
In yet still other embodiments, operations center 100 may be responsible for tracking mileage driven within a political boundary. For example, GPS receiver 402 and computer system 126 may periodically send indications of vehicle location to the operations center by way of the wireless network 112. In some embodiments, the periodic sending could be time-based (e.g., the GPS receiver 402 and computer system 126 send an indication of location every minute when the vehicle is in motion, or every ten minutes). In yet still other cases, the periodic sending could be location-based (e.g., the GPS receiver 402 and computer system 126 send an indication of location every mile, ten, miles, or 100 miles when the vehicle is in motion). Thus, the processor 102 of the operations center 100 may track the mileage driven by the vehicle based on data collected by devices associated with the vehicle; the data directly or indirectly indicates mileage driven. In yet still another embodiment, the GPS receiver 402 and computer system 126 may send an indication of location of the vehicle 120 only during the times the vehicle's ignition system is engaged (e.g., the motor is running). Thus, in this embodiment, miles are being tracked by the GPS receiver if the vehicle is being driven, and not if the vehicle is otherwise moving due to means other than driving (e.g., being towed or other transportation method). Moreover, in some cases the operations center 100 may track the mileage in spite of the fact the devices associated with the vehicle have the capability (e.g., to avoid tampering). Determining the amount of mileage traveled is not limited the GPS system, and other methods of determining mileage traveled are possible.
Determining Mileage from Odometer/Vehicle
Still referring to
Determining Mileage from Odometer/Operations Center
In yet still other embodiments, collecting data regarding vehicle movement may be performed by the operations center 100 receiving information from odometer 404. In particular, in some cases the operations center may receive periodic or continuous updates regarding the odometer 404 indication, the updates sent from the vehicle 120 by way of wireless network 112. In these example embodiments, the processor 102 of the operations center 100 may calculate the miles driven by vehicle 122 based on the updates received from odometer 404.
Storing and Accessing Data
Regardless of the method by which mileage driven by vehicle 120 is determined, collected, and transmitted, the data collected corresponding to the mileage driven is eventually provided to external agent 118, such as a representative of the political boundary in which the vehicle is located or has just departed. The representative of the political boundary in
Still considering cases where the indication of mileage driven is determined by devices of the vehicle 120 without assistance of the operations center, in another embodiment mileage data collected may be stored on a removable storage device coupled to computer 126 such as: a USB flash drive; CompactFlash card; or Secure Digital card. At some point after data has been collected on the removable storage device, an external agent may remove the removable storage device in order to manually extract the data stored in memory.
In yet another embodiment, vehicle 120 may have the ability to directly transmit data, either continuously or periodically, such as by wireless network interface 122 through wireless network 112. However, in other cases, data collected by vehicle 120 may be transmitted by way of a wireless transmission through the wireless network 112 to the operations center 100 before being sent an external agent 118.
Now consider the situation where the operations center 100 is responsible for mileage data collection. In particular, in one embodiment data collected corresponding to the mileage driven may be stored in memory coupled to processor 102. Extracting the data stored in memory coupled to processor 102 may be accomplished by communicatively coupling a computer system directly to the processor 102 (e.g., a universal serial bus (USB) connection, FireWire connection, RS-232 connection, RS-485 connection, IEEE 802.11 compliant wireless connection, BLUETOOTH wireless connection).
Still considering cases where the indication of mileage driven is determined by the operations center 100, in another embodiment mileage data collected may be stored on a removable storage device coupled to processor 100, such as: a USB flash drive; CompactFlash card; or Secure Digital card. At some point after data has been collected on the removable storage device, an external agent may remove the removable storage device in order to manually extract the data stored in memory.
In yet another embodiment, the data center 100 may directly transmit data, either continuously or periodically to the external agent. Directly transmitting the data may be through the wireless network 112, but in other cases may involve transmission without using the wireless network 112, such as by way of the Internet.
In cases where the data is stored and then later sent to the external agent, and regardless of whether the storage is in the operations center 100 or the vehicle 120, the data may be sent periodically, such as at five miles intervals, 50 mile intervals, or 100 mile intervals. In yet another embodiment, odometer readings may be stored or sent at the time the vehicle enters a political boundary, and again when the vehicle departs a political boundary.
Referring now to
In some embodiments, the operations center can be configured to receive periodic transmissions from the on-board device even when there is no active data collection, so that if the on-board device is disabled or inoperative, the lack of transmissions can cause an alert to be issued to indicate tampering with the device, such as by attempting to alter the amount of miles driven by turning off the device, or by physically altering the collected mileage value.
Now the specification turns to the preconfiguration and specification of the geo-fence boundary. In particular, the size and shape of any geo-fence boundary that may be created responsive to a vehicle entering a political boundary may be initially preconfigured by a system administrator or an external agent before a vehicle is sold, rented, or otherwise turned over to a driver (e.g., prior to the vehicle being driven). The geo-fence boundary may be preconfigured as a region corresponding to the size and shape of a political boundary. In one embodiment, the geo-fence boundary may correspond to the size and shape of a state. In another embodiment, the geo-fence boundary may correspond to the size and shape of a county. In yet another embodiment, the geo-fence boundary may correspond to the size and shape of a country.
The method of establishing a geo-fence boundary and collecting mileage data will now be discussed in more detail.
From the description provided herein, those skilled in the art are readily able to combine software created as described with appropriate general-purpose or special-purpose computer hardware to create a computer system and/or computer sub-components in accordance with the various embodiments, to create a computer system and/or computer sub-components for carrying out the methods of the various embodiments and/or to create a non-transitory computer-readable medium (i.e., not a carrier wave) that stores a software program to implement the method aspects of the various embodiments.
References to “one embodiment,” “an embodiment,” “some embodiments,” “various embodiments”, or the like indicate that a particular element or characteristic is included in at least one embodiment of the invention. Although the phrases may appear in various places, the phrases do not necessarily refer to the same embodiment.
The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. For example, while the various embodiments have been described in terms of a vehicle is traveling within a state. This context, however, shall not be read as a limitation as to the scope of one or more of the embodiments described—the same techniques may be used for other automatic geo-fence establishing, vehicle movement detection, and data calculation. It is intended that the following claims be interpreted to embrace all such variations and modifications.
This application is a continuation-in-part of U.S. patent application Ser. No. 13/364,662 for “AUTOMATED GEO-FENCE BOUNDARY CONFIGURATION AND ACTIVATION,” filed Feb. 2, 2012, which was a continuation of U.S. patent application Ser. No. 13/215,732 filed Aug. 23, 2011 (now U.S. Pat. No. 8,164,431), which was a continuation of U.S. patent application Ser. No. 12/333,904 filed Dec. 12, 2008 (now U.S. Pat. No. 8,018,329). All related applications are incorporated herein by reference as if reproduced in full below.
Number | Name | Date | Kind |
---|---|---|---|
4335370 | Scalley et al. | Jun 1982 | A |
4592443 | Simon | Jun 1986 | A |
4624578 | Green | Nov 1986 | A |
4688026 | Scribner et al. | Aug 1987 | A |
4700296 | Palmer, Jr. et al. | Oct 1987 | A |
4738333 | Collier et al. | Apr 1988 | A |
4800590 | Vaughan | Jan 1989 | A |
5014206 | Scribner et al. | May 1991 | A |
5132968 | Cephus | Jul 1992 | A |
5228083 | Lozowick et al. | Jul 1993 | A |
5426415 | Prachar et al. | Jun 1995 | A |
5490200 | Snyder et al. | Feb 1996 | A |
5495531 | Smiedt | Feb 1996 | A |
5510780 | Norris et al. | Apr 1996 | A |
5619573 | Brinkmeyer et al. | Apr 1997 | A |
5673318 | Bellare et al. | Sep 1997 | A |
5708712 | Brinkmeyer et al. | Jan 1998 | A |
5775290 | Staerzi et al. | Jul 1998 | A |
5797134 | McMillan et al. | Aug 1998 | A |
5818725 | McNamara et al. | Oct 1998 | A |
5819869 | Horton | Oct 1998 | A |
5898391 | Jefferies et al. | Apr 1999 | A |
5917405 | Joao | Jun 1999 | A |
5970143 | Schneier et al. | Oct 1999 | A |
6025774 | Forbes | Feb 2000 | A |
6026922 | Horton | Feb 2000 | A |
6032258 | Godoroja et al. | Feb 2000 | A |
6064970 | McMillan et al. | May 2000 | A |
6088143 | Bang | Jul 2000 | A |
6130621 | Weiss | Oct 2000 | A |
6157317 | Walker | Dec 2000 | A |
6185307 | Johnson, Jr. | Feb 2001 | B1 |
6195648 | Simon et al. | Feb 2001 | B1 |
6249217 | Forbes | Jun 2001 | B1 |
6278936 | Jones | Aug 2001 | B1 |
6353776 | Rohrl et al. | Mar 2002 | B1 |
6370649 | Angelo et al. | Apr 2002 | B1 |
6380848 | Weigl et al. | Apr 2002 | B1 |
6401204 | Euchner et al. | Jun 2002 | B1 |
6429773 | Schuyler | Aug 2002 | B1 |
6489897 | Simon | Dec 2002 | B2 |
6587739 | Abrams et al. | Jul 2003 | B1 |
6601175 | Arnold et al. | Jul 2003 | B1 |
6611201 | Bishop et al. | Aug 2003 | B1 |
6611686 | Smith et al. | Aug 2003 | B1 |
6615186 | Kolls | Sep 2003 | B1 |
6665613 | Duvall | Dec 2003 | B2 |
6714859 | Jones | Mar 2004 | B2 |
6717527 | Simon | Apr 2004 | B2 |
6741927 | Jones | May 2004 | B2 |
6804606 | Jones | Oct 2004 | B2 |
6812829 | Flick | Nov 2004 | B1 |
6816089 | Flick | Nov 2004 | B2 |
6816090 | Teckchandani et al. | Nov 2004 | B2 |
6828692 | Simon | Dec 2004 | B2 |
6868386 | Henderson et al. | Mar 2005 | B1 |
6870467 | Simon | Mar 2005 | B2 |
6873824 | Flick | Mar 2005 | B2 |
6888495 | Flick | May 2005 | B2 |
6917853 | Chirnomas | Jul 2005 | B2 |
6924750 | Flick | Aug 2005 | B2 |
6950807 | Brock | Sep 2005 | B2 |
6952645 | Jones | Oct 2005 | B1 |
6961001 | Chang et al. | Nov 2005 | B1 |
6972667 | Flick | Dec 2005 | B2 |
6985583 | Brainard et al. | Jan 2006 | B1 |
6993658 | Engberg et al. | Jan 2006 | B1 |
7005960 | Flick | Feb 2006 | B2 |
7015830 | Flick | Mar 2006 | B2 |
7020798 | Meng et al. | Mar 2006 | B2 |
7031826 | Flick | Apr 2006 | B2 |
7031835 | Flick | Apr 2006 | B2 |
7039811 | Ito | May 2006 | B2 |
7053823 | Cervinka et al. | May 2006 | B2 |
7061137 | Flick | Jun 2006 | B2 |
7091822 | Flick et al. | Aug 2006 | B2 |
7103368 | Teshima | Sep 2006 | B2 |
7123128 | Mullet et al. | Oct 2006 | B2 |
7124088 | Bauer et al. | Oct 2006 | B2 |
7133685 | Hose et al. | Nov 2006 | B2 |
7149623 | Flick | Dec 2006 | B2 |
7205679 | Flick | Apr 2007 | B2 |
7224083 | Flick | May 2007 | B2 |
7266507 | Simon et al. | Sep 2007 | B2 |
7299890 | Mobley | Nov 2007 | B2 |
7323982 | Staton et al. | Jan 2008 | B2 |
7327250 | Harvey | Feb 2008 | B2 |
7379805 | Olsen, III et al. | May 2008 | B2 |
7389916 | Chirnomas | Jun 2008 | B2 |
7561102 | Duvall | Jul 2009 | B2 |
7823681 | Crespo et al. | Nov 2010 | B2 |
7873455 | Arshad et al. | Jan 2011 | B2 |
7877269 | Bauer et al. | Jan 2011 | B2 |
7930211 | Crolley | Apr 2011 | B2 |
8018329 | Morgan et al. | Sep 2011 | B2 |
8095394 | Nowak et al. | Jan 2012 | B2 |
8140358 | Ling et al. | Mar 2012 | B1 |
8217772 | Morgan et al. | Jul 2012 | B2 |
8370027 | Pettersson et al. | Feb 2013 | B2 |
20010040503 | Bishop | Nov 2001 | A1 |
20020019055 | Brown | Feb 2002 | A1 |
20020193926 | Katagishi et al. | Dec 2002 | A1 |
20030036823 | Mahvi | Feb 2003 | A1 |
20030151501 | Teckchandani et al. | Aug 2003 | A1 |
20030191583 | Uhlmann et al. | Oct 2003 | A1 |
20040088345 | Zellner et al. | May 2004 | A1 |
20040153362 | Bauer et al. | Aug 2004 | A1 |
20040176978 | Simon et al. | Sep 2004 | A1 |
20040177034 | Simon et al. | Sep 2004 | A1 |
20040203974 | Seibel et al. | Oct 2004 | A1 |
20040204795 | Harvey et al. | Oct 2004 | A1 |
20040239510 | Karsten | Dec 2004 | A1 |
20050017855 | Harvey | Jan 2005 | A1 |
20050033483 | Simon et al. | Feb 2005 | A1 |
20050134438 | Simon | Jun 2005 | A1 |
20050162016 | Simon | Jul 2005 | A1 |
20050270178 | Ioli | Dec 2005 | A1 |
20060059109 | Grimes | Mar 2006 | A1 |
20060108417 | Simon | May 2006 | A1 |
20060111822 | Simon | May 2006 | A1 |
20060122748 | Nou | Jun 2006 | A1 |
20060136314 | Simon | Jun 2006 | A1 |
20070010922 | Buckley | Jan 2007 | A1 |
20070176771 | Doyle | Aug 2007 | A1 |
20070185728 | Schwarz et al. | Aug 2007 | A1 |
20070194881 | Schwarz et al. | Aug 2007 | A1 |
20080114541 | Shintani et al. | May 2008 | A1 |
20080162034 | Breen | Jul 2008 | A1 |
20080221743 | Schwarz et al. | Sep 2008 | A1 |
20090043409 | Ota | Feb 2009 | A1 |
20090182216 | Roushey, III et al. | Jul 2009 | A1 |
20100148947 | Morgan et al. | Jun 2010 | A1 |
20100268402 | Schwarz et al. | Oct 2010 | A1 |
20110050407 | Schoenfeld et al. | Mar 2011 | A1 |
20110057800 | Sofer | Mar 2011 | A1 |
20110063138 | Berkobin et al. | Mar 2011 | A1 |
20110084820 | Walter et al. | Apr 2011 | A1 |
20110153143 | O'Neil et al. | Jun 2011 | A1 |
20120133530 | Morgan et al. | May 2012 | A1 |
Number | Date | Country |
---|---|---|
1557807 | Jul 2005 | EP |
9616845 | Jun 1996 | WO |
2007092272 | Aug 2007 | WO |
2007092287 | Aug 2007 | WO |
2010068438 | Jun 2010 | WO |
Entry |
---|
US 5,699,633, 12/1997, Roser (withdrawn). |
Schwarz et al. Office Action dated Aug. 21, 2009; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, p. 18. |
Schwarz et al., Response to Office Action dated Aug. 21, 2009; filed Jan. 21, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 36 p. |
Schwarz et al., Final Office Action dated May 4, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 19 p. |
Schwarz et al., RCE and Response to Final Office Action dated May 4, 2010, filed Jul. 12, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 40 p. |
Schwarz et al., Office Action dated Oct. 26, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 16 p. |
Schwarz et al., Response to Office Action dated Oct. 26, 2010, filed Feb. 21, 2011; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 27 p. |
Schwarz et al., Final Office Action dated Apr. 28, 2011; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 17 p. |
Schwarz et al., Preliminary Amendment filed Mar. 16, 2007; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 28 p. |
Schwarz et al., Office Action dated Jul. 22, 2009; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 22 p. |
Schwarz et al., Office Action dated May 14, 2010; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 13 p. |
Schwarz et al., Response to Office Action dated May 14, 2010, filed Jul. 12, 2010; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 50 p. |
Schwarz et al., Office Action dated Oct. 15, 2010; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 13 p. |
Schwarz et al., Response to Office Action dated Oct. 15, 2010 filed Feb. 15, 2011; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 36 p. |
Schwarz et al., Final Office Action dated May 26, 2011; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 16 p. |
Gordon*Howard Associates, Inc., International Search Report and Written Opinion of the International Searching Authority dated Nov. 29, 2007 in PCT Patent Application No. PCT/US07/02816, 6 p. |
Gordon*Howard Associates, Inc., International Search Report and Written Opinion of the International Searching Authority dated Dec. 4, 2007 in PCT Patent Application No. PCT/US07/02840, 6 p. |
On Time Payment Protection Systems, printed Jan. 2, 2004 from www.ontime-pps.com/how.html. |
Aircept Products, printed Jan. 2, 2004 from www.aircept.com/products.html. |
How PayTeck Works, printed Jan. 2, 2004 from www.payteck.cc/aboutpayteck.html. |
Article: “Pager Lets You Locate Your Car, Unlock and Start It”, published Dec. 10, 1997 in USA Today. |
Article: “Electronic Keys Keep Tabs on Late Payers”, published Sep. 22, 1997 in Nonprime Auto News. |
Article: “PASSTEC Device Safely Prevents Vehicles from Starting”, published Jul. 19, 1999 in Used Car News. |
Payment Clock Disabler advertisement, published, May 18, 1998. |
Secure Your Credit & Secure Your Investment (Pay Teck advertisement), printed Jan. 2, 2004 from www.payteck.cc. |
iMetrik Company Information, printed Dec. 21, 2006 from imetrik.com. |
About C-CHIP Technologies, printed Dec. 21, 2006 from www.c-chip.com. |
Hi-Tech tools to solve traditional problems, printed Dec. 21, 2006 from www.c-chip.com. |
C-CHIP Technologies Products: Credit Chip 100, Credit Chip 100C, Credit Chip 200, printed Dec. 21, 2006 from www.c-chip.com. |
The Credit Chip 100, printed Dec. 21, 2006 from www.c-chip.com. |
PCT Search Report, International Application No. PCT/US2013/049090, mailed Sep. 27, 2013. |
Number | Date | Country | |
---|---|---|---|
20120303256 A1 | Nov 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13215732 | Aug 2011 | US |
Child | 13364662 | US | |
Parent | 12333904 | Dec 2008 | US |
Child | 13215732 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13364662 | Feb 2012 | US |
Child | 13545745 | US |