U.S. patent application number 14/996457 was filed with the patent office on 2016-05-12 for methods and systems of selectively enabling a vehicle by way of a portable wireless device.
This patent application is currently assigned to GORDON*HOWARD ASSOCIATES, INC.. The applicant listed for this patent is GORDON*HOWARD ASSOCIATES, INC.. Invention is credited to Chris Aron, Franco Chirico, Jeffrey H. Frank, James C. Graves, JR., Debra A. Jones, Mary Sue Karlin, Christopher M. Macheca, Gerald A. Morgan, Corey Pelland, Stanley G. Schwarz.
Application Number | 20160132053 14/996457 |
Document ID | / |
Family ID | 46829121 |
Filed Date | 2016-05-12 |
United States Patent
Application |
20160132053 |
Kind Code |
A1 |
Schwarz; Stanley G. ; et
al. |
May 12, 2016 |
METHODS AND SYSTEMS OF SELECTIVELY ENABLING A VEHICLE BY WAY OF A
PORTABLE WIRELESS DEVICE
Abstract
A system. The system includes a processor, a memory coupled to
the processor, a first wireless communication circuit coupled to
the processor. The first wireless communication circuit is
configured to receive, from an operations center remotely located
with respect to a vehicle, a message comprising an alert concerning
a payment event. The system also includes a second wireless
communication circuit, distinct from the first wireless
communication circuit, coupled to the processor. The second
wireless communication circuit is configured to relay the alert to
a wireless device. The memory stores a program that, when executed
by the processor, causes the processor to: disable the vehicle
responsive to a first command from the operations center, the first
command received across the first wireless communication circuit
using a first communication protocol, disable the vehicle
responsive to a second command from the operations center, the
second command relayed through the wireless device across the
second wireless communication circuit using a second communication
protocol, and disable the vehicle when the wireless device is not
communicatively coupled to the onboard device.
Inventors: |
Schwarz; Stanley G.;
(Indialantic, FL) ; Frank; Jeffrey H.; (Littleton,
CO) ; Macheca; Christopher M.; (Centennial, CO)
; Morgan; Gerald A.; (Littleton, CO) ; Chirico;
Franco; (Highlands Ranch, CO) ; Aron; Chris;
(Denver, CO) ; Karlin; Mary Sue; (Denver, CO)
; Pelland; Corey; (Gurnee, IL) ; Jones; Debra
A.; (Schaumburg, IL) ; Graves, JR.; James C.;
(St. Charles, IL) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
GORDON*HOWARD ASSOCIATES, INC. |
Littleton |
CO |
US |
|
|
Assignee: |
GORDON*HOWARD ASSOCIATES,
INC.
Littleton
CO
|
Family ID: |
46829121 |
Appl. No.: |
14/996457 |
Filed: |
January 15, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14644259 |
Mar 11, 2015 |
|
|
|
14996457 |
|
|
|
|
13229398 |
Sep 9, 2011 |
9026267 |
|
|
14644259 |
|
|
|
|
12826513 |
Jun 29, 2010 |
|
|
|
13229398 |
|
|
|
|
11684186 |
Mar 9, 2007 |
|
|
|
12826513 |
|
|
|
|
Current U.S.
Class: |
701/2 |
Current CPC
Class: |
B60R 25/04 20130101;
G05D 1/0022 20130101; H04L 63/083 20130101; H04W 12/06 20130101;
G06Q 20/127 20130101; H04W 4/70 20180201; G06Q 30/06 20130101; G06Q
20/10 20130101 |
International
Class: |
G05D 1/00 20060101
G05D001/00; G06Q 20/12 20060101 G06Q020/12; H04W 12/06 20060101
H04W012/06; H04L 29/06 20060101 H04L029/06; H04W 4/00 20060101
H04W004/00; G06Q 20/10 20060101 G06Q020/10 |
Claims
1. A system comprising: a processor; a memory coupled to the
processor; a first wireless communication circuit coupled to the
processor, the first wireless communication circuit configured to
receive, from an operations center remotely located with respect to
a vehicle, a message comprising an alert concerning a payment
event; a second wireless communication circuit, distinct from the
first wireless communication circuit, coupled to the processor, the
second wireless communication circuit configured to relay the alert
to a wireless device; and the memory storing a program that, when
executed by the processor, causes the processor to: disable the
vehicle responsive to a first command from the operations center,
the first command received across the first wireless communication
circuit using a first communication protocol disable the vehicle
responsive to a second command from the operations center, the
second command relayed through the wireless device across the
second wireless communication circuit using a second communication
protocol; and disable the vehicle when the wireless device is not
communicatively coupled to the onboard device.
2. The system of claim 1, wherein the second wireless communication
protocol comprises a Bluetooth network protocol.
3. The system of claim 1, wherein the second wireless communication
protocol comprises a ZigBee network protocol.
4. A system comprising: a wireless device configured to communicate
with other devices by way of a wireless communication network; and
an onboard device located on a vehicle, the onboard device
comprising: a processor; a memory coupled to the processor; a first
wireless communications circuit coupled to the processor, the first
wireless communication circuit configured to receive, from an
operations center remotely located with respect to the vehicle, a
message comprising an alert concerning a payment event; a second
wireless communication circuit, first wireless communication
circuit coupled to the processor, the second wireless communication
circuit configured to relay the alert to the wireless device via
the wireless network; and the memory storing a program that, when
executed by the processor, causes the processor to: disable the
vehicle responsive to a first command from the operations center,
the first command received across the first wireless communication
circuit; disable the vehicle responsive to a second command from
the operations center, the second command relayed through the
wireless device across the second wireless communication circuit;
and disable the vehicle when the wireless device is not
communicatively coupled to the onboard device.
5. The system of claim 4, wherein the wireless device is configured
to communicate with the operations center using a short message
service (SMS) communication channel.
6. The system of claim 4, wherein the wireless device is configured
to communicate with the operations center using a voice
communication channel.
7. The system of claim 4, wherein the wireless device is configured
to communicate with the operations center using an email
communication channel.
8. The system of claim 4, wherein the wireless device comprises at
least one selected from the group consisting of: a mobile
telephone; a handheld computer; a laptop computer; and a personal
digital assistant.
9. The system of claim 4, wherein the wireless device comprises a
component communicatively coupled to at least one selected from the
group consisting of: a navigation system installed in the vehicle,
a communications network operating in the vehicle, an engine
control module, a transmission control module, and a control module
for controlling a component of the vehicle.
10. The system of claim 9, wherein the wireless device is
controllable via input components associated with the navigation
system, and wherein the navigation system displays output related
to operation of the wireless device.
11. The system of claim 4, wherein the wireless device is
configured to receive user entry of a password.
12. The system of claim 11, wherein the wireless device is
configured to transmit the entered password to the operations
center for validation.
13. The system of claim 11, wherein the wireless device is
configured to transmit the entered password to the onboard device
for validation.
14. The system of claim 13, wherein the onboard device is
configured to validate the entered password.
15. The system of claim 13, wherein the onboard device is
configured to relay the entered password to the operations center
for validation.
16. The system of claim 11, wherein the processor disables the
vehicle responsive to a predetermined number of unsuccessful
password entry attempts.
17. The system of claim 4, wherein the wireless device is
configured to communicate with the operations center via a wireless
telephone network.
18. The system of claim 4, wherein the onboard device is configured
to transmit messages to the wireless device via the personal area
network, and wherein the wireless device is configured to output
messages to a user.
19. The system of claim 17, wherein the messages comprise
text-based alerts.
20. The system of claim 4, wherein the wireless device is
configured to receive input from a user specifying operational
preferences, and wherein the onboard device is configured to
receive specified operational preferences from the wireless device
and configured to reconfigure its operation in response to the
received specified operational preferences.
21. The system of claim 4 wherein the alert concerning a payment
event comprises an extension of an operability period for the
vehicle.
22. The system of claim 16 wherein, upon validation of the
password, the alert concerning a payment event comprises an
extension of an operability period for the vehicle.
23. The system of claim 15 wherein, upon validation of the
password, the alert concerning a payment event comprises a command
causing enabling operation of the vehicle.
24. The system of claim 4 wherein the wireless device is further
configured to enter a service mode on receiving a service
password.
25. A method for relaying an alert concerning a trigger event to a
user, comprising: at an operations center, detecting a trigger
event; transmitting a message from the operations center to a
device located onboard a vehicle, the message comprising an alert
concerning the trigger event, the onboard device being adapted to
selectively disable the vehicle; at the onboard device, relaying
the alert to a wireless device via a wireless network, the wireless
device being portable and movable with respect to the vehicle;
outputting, at the wireless device, an indication of the alert to
notify a user of the trigger event; and wherein the onboard device
is configured to disable the vehicle when the wireless device is
not communicatively coupled to the onboard device.
26. The method of claim 25, wherein the trigger event comprises a
non-payment event.
27. The method of claim 25, wherein the trigger event comprises a
payment event.
28. The method of claim 26, wherein relaying the alert comprises
transmitting a message comprises transmitting a message comprising
the alert via the wireless network.
29. The method of claim 25, further comprising disabling the
vehicle in response to the message from the operations center.
30. The method of claim 25, further comprising enabling the vehicle
in response to the message from the operations center.
31. The method of claim 25, wherein the trigger event comprises a
payment event, the method further comprising: at the wireless
device, prompting the user for payment input; and responsive to
failing to receiving input indicating payment, disabling the
vehicle.
32. The method of claim 25, wherein outputting an indication of the
alert comprises outputting at least one of a text message, beep,
and voice message.
33. The method of claim 25, further comprising: prompting the user
to contact the operations center; and responsive to the user
accepting the prompt, initiating wireless communication between the
wireless device and the operations center.
34. The method of claim 33, wherein initiating wireless
communication between the wireless device and the operations center
comprises initiating voice communication.
35. The method of claim 33, wherein initiating wireless
communication between the wireless device and the operations center
comprises initiating at least one selected from the group
consisting of: SMS communication; and e-mail communication.
36. A method for relaying an alert concerning a trigger event to a
user, comprising: at an operations center, detecting a trigger
event; transmitting a message from the operations center to a
wireless device, the message comprising an alert concerning the
trigger event, the wireless device being portable and movable with
respect to the vehicle; at the wireless device, relaying the alert,
via a wireless network, to a device located onboard a vehicle, the
onboard device being adapted to selectively disable the vehicle;
outputting, at the wireless device, an indication of the alert to
notify a user of the trigger event; and wherein the onboard device
is configured to disable the vehicle when the wireless device is
not communicatively coupled to the onboard device.
37. The method of claim 36, wherein the trigger event comprises a
nonpayment event.
38. The method of claim 36, wherein the trigger event comprises a
payment event.
39. The method of claim 36, further comprising disabling the
vehicle in response to the message from the operations center.
40. The method of claim 36, further comprising enabling the vehicle
in response to the message from the operations center.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of application Ser. No.
14/644,259 filed Mar. 11, 2015 titled "Methods and Systems of
Selectively Enabling a Vehicle by Way of a Portable Wireless
Device" which was a divisional of application Ser. No. 13/229,398
filed Sep. 9, 2011, titled "Methods and Systems of Selectively
Enabling a Vehicle by Way of a Portable Wireless Device" (now U.S.
Pat. No. 9,026,267). Application Ser. No. 13/229,398 was a
continuation-in-part of application Ser. No. 12/826,513, filed Jun.
29, 2010, now abandoned, titled "Onboard Starter-Interrupt Device
Incorporating Wireless Personal Area Network." Application Ser. No.
12/826,513 was a divisional of application Ser. No. 11/684,186
filed Mar. 9, 2007, now abandoned, titled "Onboard
Starter-Interrupt Device Incorporating Wireless Personal Area
Network.". All the applications noted are incorporated by reference
herein as if reproduced in full below.
FIELD OF THE INVENTION
[0002] The present invention relates to the use of a wireless
Personal Area Network (PAN), such as a Bluetooth network, in the
context of a payment enforcement system that disables, alerts, and
locates a vehicle in response to a missed payment or other
event.
BACKGROUND AND DESCRIPTION OF RELATED ART
[0003] Individuals with low credit scores have difficulty financing
purchases, such as purchases of automobiles. To the extent such
individuals can find companies to finance automobile purchases,
many times the financing is through a "buy here, pay here"
automobile dealer where the purchaser makes payments directly at
the automobile dealer's location. In many cases, the automobile
purchased includes an after-market onboard device, installed by the
automobile dealer, which enables the dealer to disable the vehicle
in the event payments are not made, or not timely made. In some
cases, the onboard device has the ability to determine the location
of the automobile and send location information to a data
center.
[0004] Thus, the onboard device of the related-art is a fairly
sophisticated device, which includes electronics for: receiving
Global Positioning System (GPS) signals; calculating location;
communicating with a data center over a wireless communication
network (such as cellular telephone network); and disabling the
automobile to which the onboard device is affixed. Of course, the
functionality drives up the cost per unit, and the communication
functionality further carries wireless communication network access
charges.
[0005] Any advance which reduces the product cost, or reduces
operational costs, of the onboard device would provide a
competitive advantage in the marketplace.
[0006] Lenders have various mechanisms for enforcing payment of
debt obligations, particularly those obligations that arise from
the sale of goods or property on credit. For example, mortgagees
can foreclose on real property if a mortgagor defaults. Vehicle
finance companies can repossess a vehicle in the event the owner
fails to make timely payment.
[0007] In some cases, foreclosure payment schedule enforcement
mechanisms are expensive and/or cumbersome to implement.
Accordingly, lenders often refuse to extend credit when the
likelihood of default exceeds some amount, because of the expense
or impracticality of repossessing or otherwise enforcing payment
obligations. In particular, potential buyers with poor credit
history may be denied credit when attempting to purchase a vehicle
or other item because of the relatively high likelihood of default.
In addition, payments on less expensive items such as appliances,
computers, and the like are often difficult to enforce because
repossession is far too expensive in relation to the value of the
item itself, and because the item loses much of its value once it
is used.
[0008] Payment enforcement systems exist whereby a vehicle (or
other purchased property) is equipped with a device capable of
disabling the vehicle in the event of non-payment. Whenever the
purchaser/owner makes a timely payment, he or she is given a
password to enter on a keypad installed in the vehicle. Entry of
the password enables the vehicle for some limited period of time
(usually until the next payment due date, plus some grace period).
Failure to enter the password causes the vehicle to be disabled,
for example by interrupting the starter circuitry. Usually, the
owner is given some warning of impending disablement, and may also
be provided with a limited number of emergency starts whereby the
vehicle can be used a few times even if a code has not been
entered. In some variations, the password is transmitted wirelessly
to the vehicle so that the owner need not enter it manually.
[0009] Such systems, available for example from PassTime USA of
Littleton, Colo., are effective in reducing the incidence of
delinquency and default. However, widespread implementation and use
of such systems is hindered by significant barriers and costs. For
example, many such systems require installation of a dedicated
onboard device (also referred to interchangeably as a vehicle
control device or payment enforcement device) with which the
vehicle owner interacts in order to enter passwords, see alerts and
notifications, and the like. Such devices can be costly to install
and maintain; furthermore, a vehicle owner may resent having such a
device because of the stigma associated with having such a visible
and prominent indication of the owner's poor credit. The device may
also be confusing to operate, difficult to update, and can take up
valuable space inside the vehicle.
[0010] In addition, it is often useful for vehicle owners to have
available to them a direct communication channel to the lender.
Without such a communication channel, errors may occur which cause
a vehicle to be mistakenly disabled because a lender did not
receive (or thought it did not receive) timely payment. Owners may
have explanations for tardiness in payment, or may wish to obtain
extensions because of valid extenuating circumstances. A direct
communication channel to lenders facilitates such advantages.
[0011] In addition, lenders often want to know where the vehicle
is, particularly in cases of default. Such information would be
useful in reducing the cost of repossession. Furthermore, providing
such information to lenders can reduce the likelihood of default,
particularly if the owner of the vehicle is informed of the fact
that location information is being made available to lenders.
[0012] What is needed, therefore, is a payment enforcement system
that avoids the need for a visible apparatus to be installed in the
vehicle. What is further needed is a device that allows user entry
of passwords and further facilitates direct communication with
lenders, without requiring a visible apparatus.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] For a detailed description of exemplary embodiments,
reference will now be made to the accompanying drawings in
which:
[0014] FIG. 1 shows a system in accordance with at least some
embodiments;
[0015] FIG. 2 shows an electrical block diagram of a portable
wireless device in accordance with at least some embodiments;
[0016] FIG. 3 shows an automobile with a docking station in
accordance with at least some embodiments;
[0017] FIG. 4 shows a method in accordance with at least some
embodiments;
[0018] FIG. 5 shows a method in accordance with at least some
embodiments; and
[0019] FIG. 6 shows a method in accordance with at least some
embodiments.
[0020] FIG. 7 depicts an overall architecture for an embodiment of
the invention.
[0021] FIG. 8A is a flow diagram depicting an example of a method
of alerting a vehicle owner of a nonpayment event according to an
embodiment of the present invention.
[0022] FIG. 8B is a flow diagram depicting an example of a method
of alerting a vehicle owner of a payment event according to an
embodiment of the present invention.
[0023] FIG. 8C is a flow diagram depicting an example of a method
of sending a disablement message to an onboard device via a
wireless device according to an embodiment of the present
invention.
[0024] FIG. 8D is a flow diagram depicting an example of a method
of sending an enablement message to an onboard device via a
wireless device according to an embodiment of the present
invention.
[0025] FIG. 8E is a flow diagram depicting an example of a method
of receiving payment via a wireless device in response to a payment
due event according to an embodiment of the present invention.
[0026] FIG. 8F is a flow diagram depicting an example of a method
of receiving payment via a wireless device according to an
embodiment of the present invention.
[0027] FIGS. 9A and 9B are flow diagrams depicting examples of
methods of enabling direct communication between a vehicle owner
and an operations center according to an embodiment of the present
invention.
[0028] FIGS. 10A and 10B are flow diagrams depicting examples of
methods of enabling password entry on a wireless device for
validation at an operations center according to an embodiment of
the present invention.
[0029] FIG. 10C is a flow diagram depicting an example of a method
of enabling password entry on a wireless device for validation at
the wireless device according to an embodiment of the present
invention.
[0030] FIG. 10D is a flow diagram depicting an example of a method
of enabling password entry on a wireless device for validation at
an onboard device according to an embodiment of the present
invention.
[0031] FIG. 11 is a flow diagram depicting an example of a method
of enabling adjustment of preferences and options for an onboard
device via a user interface presented at a wireless device
according to an embodiment of the present invention.
[0032] FIG. 12 is a block diagram depicting a hardware architecture
according to one embodiment of the present invention.
[0033] FIGS. 13A through 13C are screen shots showing examples of a
cell phone based user interface according to one embodiment of the
present invention.
NOTATION AND NOMENCLATURE
[0034] 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 by different names. This document does not intend to
distinguish between components that differ in name but not
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.
[0035] "Affixed" with respect to an onboard device and a vehicle
shall mean that the onboard device is mechanically and electrically
coupled to the vehicle such that the onboard device is not
physically accessible by an occupant properly seated in the
vehicle.
[0036] "Portable wireless device" shall mean a handheld device that
has the ability to execute third party applications, communicate
over a wireless data network, and is not affixed to the vehicle.
The fact that a portable wireless device may dock with a docking
station while in a vehicle shall not obviate the portable
status.
[0037] "Proximate", in reference to a portable wireless device and
a vehicle, shall mean coupled to the vehicle, within the vehicle,
or within two meters of the vehicle.
[0038] "Remote" or "remotely", relative to a device or vehicle,
shall mean a distance of greater than one kilometer.
DETAILED DESCRIPTION
[0039] 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 or 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 or
claims is limited to that embodiment.
[0040] The various embodiments are directed to systems and methods
of using a portable wireless device, such as the smart phone of the
driver, as the primary element in providing location and
communication services related to selectively locating and
disabling of a vehicle, such as an automobile. By having a
significant portion of the functionality implemented on a portable
wireless device of a person within the automobile, both the cost of
the onboard device, as well as the data transmission costs
associated with location and/or disablement, are significantly
reduced. In most cases the cost of the onboard device is borne by
the consumer purchasing the car, and thus the cost to the consumer
may be likewise reduced. FIG. 1 shows a system in accordance with
at least some embodiments. In particular, major components of the
system comprise data center 100, a portable wireless device 102, a
wireless data network 104, and an onboard device 106. Each will be
discussed in turn.
[0041] The data center 100 may comprise one or more computer
systems executing software instructions. In some cases, the one or
more computer systems of the data center may all be located at a
single location; however, in other cases the computer systems of
the data center may be remotely located from one another, yet
functioning as a data center. In a particular embodiment, one or
more computer systems of the data center may be "cloud" computer
systems provided under contract from a cloud computing service
provider, thus the physical location of the computer systems may
not be precisely known to the data center operator, or may change
daily or even hourly depending on the amount of computing resources
used.
[0042] In the illustration of FIG. 1, an onboard device 106 is
affixed to an automobile 108. Affixed with respect to an onboard
device 108 and an automobile shall mean that the onboard device 108
is mechanically and electrically coupled to the automobile such
that the onboard device 108 is not physically accessible by an
occupant properly seated in the vehicle. In many cases, the onboard
device 106 may reside under or within the dashboard of the
automobile. In other cases, the onboard device 106 may be at any
suitable location within the automobile, such as in an electrical
compartment under the hood, or within the luggage compartment. In a
particular embodiment, the onboard device 106 both mechanically and
electrically couples to the automobile 108 by way of a connector
110. That is, connector 110 may provide mechanical support that
holds the onboard device 106 in place, and by way of the connector
110 the onboard device 106 may electrically couple to other
components of the automobile 108, such as the onboard computer or
starter solenoid. The connector 110 may be an onboard diagnostic
(OBD) version two (hereafter just OBD-II) port. Coupling the
onboard device 106 to the illustrative OBD-II port thus gives the
onboard device 106 the ability to communicate with one or more
computer systems of the automobile 108. In other cases, the
connector 110 is a specialty connector within the automobile, such
as the starter solenoid relay connector, or fuel pump relay
connector.
[0043] The onboard device 106 illustrated in FIG. 1 comprises a
processor 112 coupled to a memory 114 by way of a bus 116. The
memory 114 stores programs executed by the processor 112, and in
some cases may be the working the working memory for the processor
112. For example, the memory 114 may be random access memory (RAM)
(e.g., dynamic random access memory (DRAM), flash memory),
programmable read-only memory (PROM), or combinations. While FIG. 1
shows the processor 112 and memory 114 as separate components, in
other cases the processor and memory are an integrated component,
such as microcontroller. The processor 112 may communicate with
sub-systems of the automobile over the connector 110.
[0044] The onboard device 106 further comprises a wireless
communication system 118 coupled to the processor 112. By way of
the wireless communication system 118, programs of the processor
112 may wirelessly communicate with other devices (i.e., radio
frequency communication by way of electromagnetic waves propagating
through air), as discussed more below. The wireless communication
system 118 may take many forms, but has a limited distance over
which communication may take place--a short range communication
network. In particular, the range of the wireless communication
system 118 need not extend beyond the passenger compartment of the
automobile, but because the passenger compartment of an automobile
has windows and doors, the range may extend beyond the automobile
for a relatively short distance (e.g., two meters). The protocol
over which the wireless communication system 118 communicates may
likewise take many forms. In one embodiment, the wireless
communication system 118 implements a Bluetooth communication
protocol. Another example is a ZIGBEE.RTM. brand network protocol,
where the ZIGBEE.RTM. trademark is owned by Zigbee Alliance.
Regardless of the type of protocol and range implemented by the
wireless communication system 118, when the onboard device 106 is
installed and remotely located from the data center 100 the
wireless communication system 118 cannot communicate with the data
center 100 without an intervening device in the form of the
portable wireless device 102.
[0045] Portable wireless device 102 is a handheld device that has
the ability to execute third party applications, communicate over a
wireless data network 104, communicate over the short range
communication network (i.e., communicate with the wireless
communication system 118 when in range), and is not affixed to the
automobile. In some cases, the portable wireless device 102 also
places and receives cellular telephone calls. Thus, in some
embodiments, the portable wireless device 102 is a "smart phone"
possessed by an owner or occupant of the automobile. In most cases,
the portable wireless device 102 will be carried by an owner or
occupant of the automobile 108, and thus will be out of
communication range with the onboard device 106 at times when the
owner or occupant is not proximate to the automobile. However, when
the owner or occupant approaches the automobile, or is within the
automobile, the portable wireless device 102 may establish
communication with the onboard device 106.
[0046] FIG. 2 shows an electrical block diagram of a portable
wireless device 102 in accordance with at least some embodiments.
In particular, the portable wireless device 102 comprises a
processor 200, memory 204, graphics controller 206, display device
208, global positioning system (GPS) receiver 210, cellular
phone/data transceiver 212, short range communication transceiver
214, and battery 216. The processor 200 is coupled to memory 204,
such as by a bus 202. The memory 204 stores programs executed by
the processor 200, and in some cases may be the working the working
memory for the processor 200. In some cases, the memory 204 may be
random access memory (RAM) (e.g., dynamic random access memory
(DRAM), flash memory). The memory 204 may store programs used by
the portable wireless device for operation, such as a mobile
operating system (e.g., iOS.TM. brand mobile operating system from
Apple, Inc., or the ANDROID.TM. brand mobile operating system from
Google, Inc.) and original equipment manufacturer (OEM) installed
programs (e.g., applications to implement placing and receiving
cellular phone calls, or messaging services).
[0047] A person who carries the portable wireless device 102 may
interface with the various programs executed on the device 102 by
way of display device 208. The display device 208 may be any
display device upon which text and/or images may be formed, such as
a liquid crystal display (LCD). In some cases, the display device
is controlled by graphics controller 206, but in other cases the
graphics controller functionality may be implemented within the
processor 200. Though not specifically shown in FIG. 2, the display
device may be overlaid with a transparent touch sensitive device
such that the portable wireless device implements "touch screen"
functionality.
[0048] The illustrative portable wireless device 102 further
comprises a GPS receiver 210. The GPS receiver 210 receives signals
from an array of GPS satellites orbiting the earth, and based on
timing associated with arrival of those signals, a position can be
determined. In some cases, the GPS receiver 210 has sufficient
functionality to calculate position, and thus the data passed to
processor 200 may be a direct indication of position. In other
cases, the functionality to determine position may be shared
between the GPS receiver 210 and software executing on the
processor 200. That is, the GPS receiver 210 may receive the
plurality of GPS signals and pass the information to a program on
the processor 200, which program may then make the determination as
to location of the portable wireless device 102.
[0049] Still referring to FIG. 2, the portable wireless device
further comprises a cellular phone/data transceiver 212, over which
voice and data transmission may take place. The transceiver 212
thus implements a wireless communication system and/or protocol
(i.e., radio frequency communication by way of electromagnetic
waves propagating through air). Any suitable communication protocol
may be implemented by the transceiver 212, such as Global System
for Mobile Communications (GSM) compliant protocol, a General
Packet Radio Service (GPRS) compliant protocol, or a Personal
Communications Service (PCS) compliant system. While it is
contemplated that in most cases the transceiver 212 will employ
both voice and data communications, in some embodiments only a data
communication system is implemented (e.g., an IPAD.TM. brand
product available from Apple, Inc.). That is, in some cases the
portable wireless device 102 does not provide voice services.
[0050] Still referring to FIG. 2, illustrative portable wireless
device 102 further comprises a short range communication
transceiver 214. By way of the short range communication
transceiver 214, programs executed by the processor 200 may
communicate with other devices, such as the onboard device 106. The
short range communication transceiver 214 may take many forms, but
has a limited distance over which communication may take place. In
a particular embodiment, the transceiver 214 is a wireless
transceiver (i.e., radio frequency communication by way of
electromagnetic waves propagating through air), and need not have a
range larger than the passenger compartment of the automobile 108
to which the onboard device 106 is affixed. Because the passenger
compartment of an automobile has windows and doors, the portable
wireless device 102 may establish communication when in close
proximity to the automobile 108 (e.g., within two meters). The
protocol over which the short range communication transceiver 214
communicates may take many forms, but will be compatible with the
protocol of the wireless communication system 118 of the onboard
device 106. Thus, the short range communication transceiver 214 may
implement any suitable system, such as a Bluetooth communication
protocol, or a ZIGBEE.RTM. brand communication protocol.
[0051] Returning again to FIG. 1, in order for the onboard device
106 to have the ability to reliably establish communication with
the data center 100, in accordance with various embodiments the
portable wireless device 102 is considered a "key" to the car. That
is, in one embodiment onboard device 106 is configured to disable
the automobile 108 at any time the portable wireless device 102 is
not communicatively coupled to the onboard device 106 by way of the
wireless communication system 118, and the onboard device 106 is
configured to enable the automobile 108 at any time the portable
wireless device 102 is communicatively coupled to the onboard
device 106 by way of the wireless communication system 118.
[0052] Disabling and enabling of the automobile 108 based on
proximity of the portable wireless device 102 may take many forms.
In some embodiments, the onboard device 106 is mechanically and
electrically coupled to connector 110 in the form of the OBD-II
port as discussed above. When connected to the OBD-II port, the
onboard device 106 may communicate with one or more computer
systems of the automobile 108, and thus may disable the automobile
by any suitable technique, such as disabling the ability to crank
the engine, disabling the spark ignition system, disabling the fuel
system, or a combination. An onboard device 106 configured to
couple to the OBD-II port may also have the ability to read or
determine data associated with the vehicle, such as determining the
identity of the vehicle (e.g., by reading the VIN number).
[0053] In other embodiments, the onboard device 106 may be a relay
replacement device. For example, a starter relay is a device within
an automobile that, when activated, provides electrical current to
the solenoid of the starter. The onboard device 106 in the form a
starter relay replacement device may thus act as an operational
starter relay when the portable wireless device 102 is
communicatively coupled, but in the event communication is lost
with the portable wireless device 102 the onboard device 106 may
not provide current to the solenoid in spite of a command to do so.
Thus, connector 110 may be a relay connector. In yet still other
cases, the onboard device 106 may be a relay replacement device for
any system that could disable the vehicle (e.g., either prevents
the motor from starting, or prevents the motor from continuing to
operate).
[0054] The portable wireless device 102 and onboard device 106 also
enable further functionality regarding the data center 100. In
particular, the data center 100 (e.g., at the behest of a lien
holder on the automobile) may periodically need to determine the
location of the automobile 108 (e.g., to ensure the automobile has
not been moved out of state). In accordance with the various
embodiments, location services are based on the portable wireless
device 102. That is, in accordance with at least some embodiments
determining the location of the automobile 108 may involve the data
center 100 communicating with the portable wireless device 102 by
way of the wireless data network 104. It is noted that reference to
communication with the portable wireless device 102 by way of the
wireless data network 104 shall not be read to require that the
data center 100 wirelessly couple to the data network 104. The
communication by the data center 100 to the portable wireless
device 102 may thus request an indication of location. The portable
wireless device 102, in turn, may establish whether the device 102
is communicatively coupled to the onboard device 106. If the
portable wireless device 102 is not communicatively coupled to the
onboard device 106, the portable wireless device 102 may notify the
data center 100, and/or wait until communication is established
with the onboard device 106.
[0055] Assuming the portable wireless device is or becomes
communicatively coupled with the onboard device 106, the wireless
device 102 then activates its GPS receiver 210 to receive signals
from a plurality of GPS satellites (illustrated by satellite 130)
and determine location. Once a location is established, the
location information is sent to the data center 100 over the
wireless data network 104. Thus, location of the automobile may be
determined in spite of the fact the onboard device 106 does not
have the capability to determine location.
[0056] In yet still further embodiments, the data center 100 may
periodically need to disable the automobile 108. For example, in
the event a payment is missed, or some other contractual obligation
is breached (e.g., automobile moved to a non-approved location) the
automobile 108 may be disabled. As with the location services, in
accordance with the various embodiments disablement services are
based on the portable wireless device 102. That is, in accordance
with at least some embodiments disabling the automobile 108 may
involve the data center 100 communicating with the portable
wireless device 104 by way of the wireless data network 104. The
portable wireless device 102, in turn, may establish whether the
device 102 is communicatively coupled to the onboard device 106. If
the portable wireless device 102 is not communicatively coupled to
the onboard device 106, the portable wireless device 102 may notify
the data center 100, and/or wait until communication is established
with the onboard device 106.
[0057] Assuming the portable wireless device is or becomes
communicatively coupled with the onboard device 106, the portable
wireless device 102 then sends a command to the onboard device 106.
The onboard device, in turn, disables the automobile. Thus, the
automobile may be disabled in spite of the fact the onboard device
106 does not have the capability to communicate with the data
center 100 over the wireless data network 104.
[0058] In accordance with yet still further embodiments, the data
center 100 may periodically need to communicate with the owner or
occupant of the automobile 108. For example, in the event a payment
due date is approaching, or the automobile is approaching a
contractual boundary, the data center 100 may send a message to the
owner or occupant. In accordance with at least some embodiments,
sending a message by the data center 100 may involve the data
center 100 communicating with the portable wireless device 102 by
way of the wireless data network 104. The portable wireless device
102, in turn, may display the message on the display device 208.
The message may take many forms. In some cases the message is text
message (e.g., short messaging service (SMS) text communication).
In yet still other embodiments, the message may take the form of
series of TCP/IP packets exchanged between a program executing on
the portable wireless device 102 and the computer systems of the
data center 100.
[0059] The various embodiments discussed to this point have been
based on embodiments where the portable wireless device 102
wirelessly couples to the onboard device 106. However, in yet still
further embodiments the portable wireless device may couple to a
docking station within the automobile, and further communicatively
couple with the onboard device 106 by way of one or more
conductors. FIG. 3 shows a block diagram of further embodiments
that utilize a docking station. In particular, FIG. 3 shows a
docking station 300 mechanically coupled to the automobile 108. The
docking station may take many forms depending on the nature of the
portable wireless device 102. For example, for a portable wireless
device 102 in the form of an IPHONE.TM. brand product (produced by
Apple, Inc. of Cupertino, Calif.), the docking station 300 may
comprise the proprietary IPHONE.TM. connector along with one or
more mechanism to physically hold the IPHONE.TM.. Thus, the docking
station 300 may both mechanically couple the portable wireless
device 102 to the automobile, and electrically couple the portable
wireless device 102 to the onboard device 106. In some cases, one
or more conductors 302 may couple between the docking station 300
and the onboard device 106, thus establishing a communication
network. The conductors may be either electrical or optical
conductors. It is noted again, however, that coupling the portable
wireless device 102 to a docking station 300 when the device 102 is
within the automobile shall not, for purposes of the claims,
obviate the portable status of the device 102.
[0060] FIG. 4 shows a method in accordance with at least some
embodiments, some of which may be implemented in software executed
at the data center and/or the portable wireless device. In
particular, the method starts (block 400) and comprises: enabling a
vehicle when a portable wireless device is communicatively coupled
to an onboard device by way of a first communication network, the
enabling by the onboard device coupled to the vehicle (block 402);
sending an indication of location of the vehicle to a data center
(block 404); and disabling the vehicle when the portable wireless
device is no longer communicatively coupled to the onboard device
(block 412). The sending (again block 404) may comprise: receiving
global positioning system (GPS) signals by the portable wireless
device, the portable wireless device operatively coupled to a
second communication network (block 406); establishing that the
portable wireless device is proximate to the vehicle, the
establishing by the portable wireless device (block 408); and
sending an indication of location to the data center, the sending
by the portable wireless device by way of the second communication
network (block 410). Thereafter, the method ends (block 414).
[0061] FIG. 5 shows a method in accordance with at least some
embodiments, some of which may be implemented in software executed
at the data center and/or the portable wireless device. In
particular, the method starts (block 500) and comprises disabling
the vehicle during periods of time when the portable wireless
device is proximate the vehicle (block 502). In some cases, the
disabling is by: sending a message from the data center to the
portable wireless device (block 504); sending a command to the
onboard device by the portable wireless device, the sending the
command responsive to the message from the data center (block 506);
and disabling the vehicle by the onboard device responsive to the
command (block 508). Thereafter, the method ends (block 510).
[0062] FIG. 6 shows a method in accordance with at least some
embodiments, some of which may be implemented in software executed
at the data center and/or the portable wireless device. In
particular, the method starts (block 600) and comprises:
establishing a first communication between a portable wireless
device proximate a vehicle and an onboard device affixed to the
vehicle, the first communication by way of a first communication
network (block 602); establishing a second communication between
the portable wireless device and a data center remotely located
from the portable wireless device and the vehicle, the second
communication by way of a second communication network distinct
form the first communication network (block 604); receiving a
message by the portable wireless device from the data center, the
message received over the second communication network (block 606);
enabling the vehicle responsive to the message indicating
enablement, the enabling by the portable wireless device sending a
command to the onboard device over the first communication network
(block 608); and disabling the vehicle responsive to the message
indicating disablement, the disabling by the portable wireless
device sending a command to the onboard device over the first
communication network (block 610). Thereafter, the method ends
(block 612).
[0063] In still other embodiments, the present invention uses a
Personal Area Network (PAN) to facilitate communication between a
wireless device (such as a cellular telephone or personal digital
assistant (PDA)) and a payment enforcement device installed on a
vehicle. The PAN can be implemented using, for example, the
well-known Bluetooth protocol.
[0064] The onboard payment enforcement device includes starter
interrupt circuitry capable of disabling the vehicle by, for
example, cutting power to the vehicle's starting system. The
onboard payment enforcement device communicates with an operations
center to receive instructions from the operations center; these
instructions can cause the onboard device to disable or enable the
vehicle. The instructions can also cause the onboard device to
transmit alerts and other notifications via the PAN for display on
the owner's wireless device.
[0065] In one embodiment, the owner can communicate directly with
personnel at the operations center via the wireless device. Such
communication can include SMS, voice, email, and the like. The PAN
provides an infrastructure by which the owner's wireless device
transmits messages and communications between the wireless device
and the onboard device; a separate communication channel exists
between the onboard device and the operations center. Thus, a voice
communication can be easily established from the owner's wireless
device to the operations center, allowing the owner to talk
directly to a live human being at the operations center and thereby
clear up any errors, request extensions, and the like. In addition,
the owner can enter passwords on, for example, a keypad on the
wireless device; such passwords are transmitted via the PAN to the
onboard device and then relayed to the operations center via a
wireless carrier.
[0066] In another embodiment, the owner's wireless device is itself
used as the communication channel with the operations center. In
this variation, the onboard device does not establish its own
wireless channel to the operations center, but instead
transmits/receives control messages to/from the wireless device
(via the PAN), and causes the wireless device to interact
wirelessly with the operations center. The communication channel
can include data, voice, or both. In this variation the vehicle
cannot receive commands from the operations center if the owner
does not bring his/her cell phone to the vehicle at least
periodically; therefore, fail-safe schemes can be put in place such
that unless periodic contact is made with the operations center,
the onboard device causes the vehicle to be disabled.
[0067] According to the techniques of the present invention, an
improved onboard starter-interrupt device incorporates a wireless
Personal Area Network (PAN) using a protocol such as Bluetooth in
implementing a payment enforcement scheme. Owner interaction with
the onboard starter-interrupt device takes place via a cell phone
or other PAN-enabled device; where appropriate, the onboard device
facilitates communication between the owner and an operations
center via the PAN and via the onboard device's own wireless modem
or other communication mechanism.
[0068] In one aspect, a payment schedule can be configured. If the
vehicle owner fails to make payment by a certain date, the
operations center can send a message to the onboard device to
output alerts, disable the vehicle, provide location information,
or any combination thereof in any desired sequence. Disablement
alerts and warnings can be communicated to the owner via the PAN,
so that alerts appear on the owner's own wireless device. An owner
can also directly communicate with the operations center, for
example via voice, text, email, or the like, via the PAN.
[0069] By combining vehicle disablement technology with a personal
area network such as a Bluetooth-enabled network, the present
invention provides an improved system and method for enforcing
payment schedules and reducing the likelihood and cost of default.
Such a system and method provides distinct advantages over prior
art schemes, including: avoiding the need for a visible keypad or
other user input device installed in the vehicle; ability to
provide a direct communication channel, including voice
communication; ability to interface with existing communication
devices, such as a BlueTooth-enabled cell phone.
[0070] Enforcement of payment schedules in a centralized, flexible
manner is described in related co-pending U.S. patent application
Ser. No. 11/349,523 for "ENFORCING PAYMENT SCHEDULES", filed Feb.
7, 2006, the disclosure of which is incorporated herein by
reference. As described therein, various types of events can be
configured via software running at an operations center. Upon
occurrence of a specified event, a message is sent to an onboard
device located remotely with respect to the operations center, such
as one installed in a vehicle or other product. The onboard device
(also referred to interchangeably as a vehicle control device or a
payment enforcement device) is configured so that it can disable
the vehicle (for example by disabling the starter circuitry) upon
receipt of the message from the operations center. In
implementations involving products other than vehicles, other
mechanisms for disabling the product (such as cutting off power to
the product) can be used. The remotely located device can be
instructed to allow a certain number of emergency uses, or to
accept an override password that re-enables use of the vehicle.
[0071] In one embodiment, the onboard device or vehicle control
device includes functionality for interfacing with a personal area
network (PAN), for example using the well-known Bluetooth protocol.
Although the description provided herein sets forth the invention
in terms of a Bluetooth-enabled system, one skilled in the art will
recognize that other protocols and operational schemes can be used
in connection with the present invention, without departing from
the essential characteristics of the present invention. For
example, the present invention can be implemented using the ZigBee
protocol.
[0072] In one embodiment, the present invention includes or
interfaces with location tracking functionality as described in
related to U.S. patent application Ser. No. 11/539,292 for
"STARTER-INTERRUPT DEVICE INCORPORATING GLOBAL POSITIONING SYSTEM
FUNCTIONALITY", attorney docket number GH004, filed Oct. 6, 2006,
the disclosure of which is incorporated herein by reference. One
skilled in the art will recognize that the present invention can be
implemented with or without such location tracking
functionality.
[0073] For illustrative purposes, the description provided herein
sets forth the invention in the context of vehicles. However, one
skilled in the art will recognize that the invention can be used in
connection with any product.
[0074] For purposes of the following description, "vehicle owner",
"owner", and "user" are synonymous and can refer to any individual
who is interacting with wireless device 7152 and/or onboard device
7111.
[0075] According to one embodiment, the present invention is
implemented as a software application running at an operations
center. The software application detects relevant events such as
nonpayment and communication requests from owners, and generates
messages in response to the events. These messages are received by
remotely located devices installed in vehicles or other products.
Upon receiving a message, the remotely located device takes one or
more appropriate action(s), including for example: opening a
communication channel with the owner of the vehicle, disabling the
vehicle, transmitting its current location, outputting alerts, or
the like. As described in more detail below, the present invention
operates in connection with a PAN so that a Bluetooth-enabled
cellular telephone (or other similar wireless device) can be used
for entry of passwords, display of alerts, voice communication with
the operations center, and text or email-based communication with
the operations center. The present invention thus avoids the need
for a keypad unit to be installed in the vehicle, and further
provides additional functionality that allows owners to directly
communicate with lenders and thereby avoid unnecessary or
unintentional vehicle disablement. Further advantages will become
apparent in the course of the following description.
[0076] Referring now to FIG. 7, there is shown a block diagram
depicting an overall architecture for an embodiment of the
invention. Referring now also to FIG. 12, there is shown a block
diagram depicting a hardware architecture for wireless device 7152
and onboard device 7111.
[0077] Software 7102 runs at operations center 7101. In one
embodiment, operations center 7101 is situated at some central
location and is operated by or on behalf of a lender, seller, or
loan service company. Appropriate communications infrastructure,
such as Internet, wireless, and/or telecommunications connectivity
is provided, so as to allow operations center 7101 to communicate
with other elements of the overall system.
[0078] Onboard device 7111 is located in vehicle 7109 and includes
a processor, such as PIC processor 71105, which implements onboard
functionality. Onboard device 7111 also includes host or cellular
baseband processor 12602 for facilitating wireless communication on
a cellular network such as provided by wireless carrier 7119. PIC
processor 71105 interfaces with wireless modem 7120 for sending and
receiving messages. Software running on PIC processor 71105
controls enablement and disablement of vehicle starter circuitry
7112. In one embodiment, PIC processor 71105 is communicatively
coupled to vehicle starter circuitry 7112 to facilitate such
disablement when needed. In other embodiments, a starter interrupt
module 12604 is provided. In other embodiments, PIC processor 71105
is coupled to other vehicle circuitry such as a Controller Area
Network (CAN) bus, on-board diagnostic (OBD) port, or the like, so
that it can affect operation of vehicle 7109 by disabling,
curtailing, or limiting certain features and functions of vehicle
7109 as appropriate. For example, under certain conditions, vehicle
speed and/or vehicle functionality may be limited in response to a
nonpayment event. Device 7111 also includes memory 12603, such as
RAM, to enable it to store preferences, configurations, schedules,
and the like. In one embodiment, device 7111 also includes an
input/output component 12605 such as a keypad, display, alert
system, and the like, also in other embodiments some input
components are not needed because wireless device 7152 acts as an
input device.
[0079] PAN interface 7151 facilitates operation with Personal Area
Network (PAN) 7600, which may be for example a network operating in
accordance with the Bluetooth protocol, the ZigBee protocol, or any
other well-known protocol for implementing a PAN. In one
embodiment, for example, PAN interface 7151 is a Bluetooth
interface that permits onboard device 7111 to communicate with a
wireless device 7152 that is similarly Bluetooth-enabled. Examples
of such a wireless device 7152 include a cell phone, personal
digital assistant (PDA), handheld computer, and the like. Device
152 can be a conventional cellular telephone that is capable of
calling any number, or it can be a specialized cell phone that can
only be used to communicate with the seller (or lender).
[0080] In one embodiment, wireless device 7152 includes
input/output components 12605 including for example an output
device such as a screen, an audio output device such as a speaker,
and an input device such as a keypad, touch-sensitive screen,
keyboard, buttons, rockers, rolling switches, and/or any
combination thereof, as is well known in the art of cellular
telephones, PDAs and the like. Wireless device 7152 also includes a
PAN interface 12601 for facilitating communication with PAN 7600,
host or cellular baseband processor 12602 for facilitating wireless
communication on a cellular network, and memory 12603 such as
RAM.
[0081] Wireless device 7152 may be a hand-held device, or it may be
installed in vehicle 7109. In one embodiment, wireless device 7152
is implemented as part of a navigation system such as a portable or
in-car GPS-enabled navigation device with BlueTooth functionality.
In another embodiment, wireless device 7152 communicates with any
or of the vehicle's communications network (vehicle bus), engine
control module (ECM), transmission control module (TCM), and the
like. By communicating with such components, wireless device 7152
is able to interact with various components of vehicle 7109.
[0082] In one embodiment, onboard device 7111 transmits messages,
via PAN 7600, to wireless device 7152 for display to owner 7110;
for example, an alert may appear on device 152 to indicate to the
owner 7110 that vehicle 7109 will be disabled in three days if
payment is not received. PAN interface 7151 also provides a
mechanism by which voice communication with owner 7110 can be
facilitated via wireless device 7152. For example, if owner 7110
wishes to communicate directly with an administrator 104 at
operations center 7101, owner 7110 can activate a command on
wireless device 7152 that enables such communication to take place
via PAN.
[0083] As described in more detail below, wireless device 7152 can
be also used as an input device for entry of passwords and the
like. The owner can also enter a pass code on the wireless device's
152 keypad; wireless device 7152 then communicates with onboard
device 7111 to enable use of vehicle 7109 and/or to send messages
7107A to operations center 7101 indicating that a pass code has
been entered. Validation of the pass code can take place at
wireless device 7152, or at onboard device 7111, or at operations
center 7101.
[0084] As described in more detail below, wireless device 7152 can
also receive messages via BlueTooth from device 7111. For example,
status updates, prompts, warnings, and the like, can be displayed
on a display screen of wireless device 7152 in response to
receiving particular messages from device 7111. In one embodiment,
device 7111 sends such messages to wireless device 7152 in response
to receiving certain types of messages 7107A from operations center
7101. In one embodiment, device 7111 sends such messages when it
detects the presence or proximity of device 152, or when owner 7110
attempts to start vehicle 7109. Messages sent in this manner can be
presented to the owner 7110 via SMS, voicemail, or any other
communication means.
[0085] Owner 7110 can also use SMS, voice, or other means to send
messages to operations center 7101, for example to send payment
information or the like. In one embodiment, such messages are sent
to device 7111 using BlueTooth and then relayed to operations
center 7101. In one embodiment, data communications are enabled by
first issuing AT commands, as are well known in the field of modem
communication, in order to set up the connection between wireless
device 7152 and wireless modem 7120 in device 7111 over PAN 7600.
AT commands can also be used to transfer data between devices 111
and 152.
[0086] In one embodiment, voice communication is implemented using
a direct communication path between wireless device 7152 and
operations center 7101 over a conventional wireless network,
without using PAN 7600 as an intermediary. By using conventional
wireless telephony methodology, the system can operate with
off-the-shelf wireless devices such as cell phones and PDAs. If
appropriate, onboard device 7111 can provide a telephone number to
wireless device 7152 via PAN, so as to tell owner 7110 what number
to dial when trying to reach operations center 7101, or to enable
automatic dialing.
[0087] In another embodiment, wireless device 7152 can be a custom
device that enables voice communication to operations center 7101
using onboard device 7111 as an intermediary. In this embodiment
onboard device 7111 operates essentially as a cell phone and
wireless device 7152 is equivalent to a Bluetooth headset or
similar device.
[0088] Alternatively, wireless device 7152 can send/receive
messages directly to/from operations center 7101 for example via
SMS or other wireless protocols. Wireless device 7152 can then
relay appropriate messages to onboard device 7111 via PAN 7600. In
such an embodiment, device 152 acts as an intermediary for messages
being sent from operations center 7101 to onboard device 7111.
[0089] In one embodiment, device 152 can also include RF
functionality, a card-swiper, or the like (not shown). Data
collected using such input methods can be sent to device 7111 via
PAN 7600. For example, if the owner 7110 swipes a credit card for
payment purposes, device 152 can relay the credit card information
to device 7111 and/or to operations center 7101 to enable continued
operation of vehicle 7109.
[0090] Wireless device 7152 can also be used for programming and
setting preferences on onboard device 7111. For example, in one
embodiment, a service mode is available for use by an administrator
or other representative of operations center 7101 or lender. A
service password may be required before entering such a service
mode. While in the service mode, the administrator can specify
warning periods, alert parameters, and other settings using a user
interface on device 152. Device 152 communicates with device 7111
via PAN 7600 to cause such settings to be implemented on onboard
device 7111. In one embodiment, the vehicle owner 7110 can specify
user preferences in a similar manner, although without having to
enter a service password.
[0091] System administrator 7104 interacts with software 7102 via
user interface 7103, which allows system administrator 7104 to
specify options, schedules, alert conditions, and the like, and
also allows system administrator 7104 to view reports, monitor
system operations, and the like. System administrator 7104 may be
located at or near operations center 7101, or may be remotely
located, in which case interactions with software 7102 may take
place over a computer network such as the Internet, virtual private
network, or the like, according to techniques that are well known
to those of skill in the art.
[0092] Technology trigger 7121 provides messages 107C specifying
events that have occurred. Technology trigger 7121 can be any
source of information that is relevant to the payment schedule
enforcement mechanism of the present invention. For example,
technology trigger 7121 may be a data stream providing information
from a payment system, so that upon receipt of messages 107C from
technology trigger 77121, software causes payment schedule 7105
and/or other information to be updated.
[0093] Event logic 7115 specifies what actions should be taken in
response to such messages 107C. For example, technology trigger
7121 can inform software 7102 that a payment has been received, or
that a payment has been missed, or that some other event has taken
place. Event logic 7115 tells software 7102 what to do in response
to such events.
[0094] Payment schedule 7105 for a particular debtor is stored, for
example, in a database or other data store at operations center
7101 or at some other location. Software 7102 enforces payment
schedule 7105 by sending appropriate messages according to event
logic 7115, on-demand needs, or local override. Software 7102 is
communicatively coupled with accounting systems (not shown) or
other sources of data that inform software 7102 when a payment is
late or when other relevant events take place that require messages
7107A, 7107B to be sent.
[0095] In one embodiment, software 7102 also includes data
management module 7117, which maintains customer information,
financial controls, verification data to ensure authenticity of
messages 7107A from vehicles 109, and the like. Such information
can be stored in database 7118, which in one embodiment is
implemented as a SQL server database. Data management module 7117
can also maintain payment schedules 105, and can specify changes to
event logic 7115, under the control of user interface 7103.
[0096] In one embodiment, software 7102 invokes middleware 7106 to
send messages 7107A, via wireless carrier 7119, to modem 120
associated with device 7111 at vehicle 7109. In one embodiment,
middleware 7106 can also be used for sending messages 7107B to
external agent 7108, although in other embodiments messages 7107B
are sent directly by software 7102. For example, middleware 7106
can communicate with a cellular network via Internet Protocol;
messages are then sent via the cellular network using a GSM or
other protocol to modem 120 in vehicle 7109. External agent 7108
can receive information regarding vehicle 7109 by other means, for
example by receiving email messages from operations center 7101, or
by logging onto a web site run by operations center 7101.
[0097] In one embodiment, messages are sent using an Access Point
Name (APN) associated with a wireless carrier 7119 communicating
via a GPRS protocol. Any other network or protocol can be used,
including for example GSM, CMDA, or the like. The APN enables
sending and/or receiving messages to external agent 7108 and/or
wireless modem 7120 on onboard device 7111. Middleware 7106
provides an interface by which software 7102 can communicate with
many different types of devices, systems, computers, vehicles,
nodes, and the like, via a variety of protocols, to provide mobile
device control and data acquisition functionality. Essentially,
middleware 7106 acts a protocol translation module between software
7102 and whatever entities software 7102 communicates with. For
example, for certain devices 111, Internet Protocol (IP) may be an
appropriate communication medium, whereas cell or pager messages
may be the appropriate mechanism for other devices 111. Examples of
other communication protocols that can be used include GPRS, SMS
Edge, Java, SQL and the like. In one embodiment, the present
invention is implemented using mobile device middleware available
from Intellimatics of Coppell, Tex. Standard ODBC protocols can be
used to communicate with Intellimatics databases (via standard SQL
commands, a SQL Server database, and UDP, SMS, and/or TCP/IP
messaging protocols).
[0098] Event management middleware 7106 sends messages 7107A to
remotely located device 7111 installed in vehicle 7109. In one
embodiment, modem 120 in device 7111 receives such messages 7107A.
Messages 7107A instruct device 7111 to perform various operations,
such as disabling vehicle starter circuitry 7112 in order to
prevent operation of vehicle 7109, outputting alerts or other
information to owner 7110 via PAN 7600 and wireless device 7152, or
the like.
[0099] In addition to sending messages 7107A and/or 7107B, in one
embodiment, middleware 7106 can also receive messages. For example,
middleware 7106 may receive acknowledgement messages from device
7111 and/or agent 108 to confirm receipt of messages 7107A and/or
7107B. In an alternative embodiment, middleware 7106 can be
omitted, and software 7102 communicates directly with device 7111
via wireless carrier 7119 to exchange such information.
[0100] Although the present invention is described in connection
with an embodiment using middleware 7106, one skilled in the art
will recognize that other embodiments are possible. In particular,
middleware 7106 can be omitted, so that software 7102 communicates
directly with onboard device 7111 and/or external agent 7108, as
appropriate.
[0101] The following description sets forth a number of methods of
operation according to various embodiments of the present
invention. One skilled in the art will recognize that other methods
of operation can also be implemented without departing from the
essential characteristics of the present invention.
[0102] Referring now to FIG. 8A, there is shown a flowchart
depicting an example of a method of alerting a vehicle owner of a
nonpayment event according to an embodiment of the present
invention. A nonpayment event is detected 8201. (Alternatively, the
method of FIG. 2 can be performed in response to other types of
events such as geo-fence violations described in the
above-referenced related patent application.) In response to the
event, operations center 7101 transmits message 107A to onboard
device 7111. In one embodiment, message 107A is transmitted by
middleware 7106 across wireless carrier 7119 to wireless modem 7120
at device 7111.
[0103] Message 107A can be of any form or type. In one embodiment,
message 107A indicates that an alert should be displayed to vehicle
owner 7110; for example, in response to a nonpayment event it may
be desirable to alert vehicle owner 7110 that he or she has five
days to make payment before vehicle 7109 will be disabled.
[0104] According to the techniques of the present invention,
wireless device 7152 is used for displaying or otherwise
communicating such alerts to vehicle owner 7110. Thus, device 7111
relays 8203 the message to wireless device 7152 via PAN 7600, and
device 152 outputs 8204 the appropriate alert. For example, device
152 may display a text message, or may sound a beep, or may play a
voice message specifying the details of the alert. Furthermore, as
described below, wireless device 7152 may display an option that
allows owner 7110 to initiate direct contact with an administrator
104 at operations center 7101. Should owner 7110 activate this
option, voice communication (or other communication such as Short
Message Service (SMS), push-to-talk, or email) is enabled via PAN
7600 and, in turn, via wireless carrier 7119 to operations center
7101.
[0105] If appropriate, device 7111 also disables 8205 vehicle 7109;
such action may be appropriate, for example, if owner 7110 has
previously been warned of the payment delinquency and has been
given ample opportunity to cure the problem. In one embodiment,
device 7111 disables 8205 vehicle 7109 by interacting with vehicle
starter circuitry 7112. In other embodiments, other techniques are
used such as for example sending messages via the vehicle's 109 CAN
bus.
[0106] As indicated above, the system of the present invention can
be used with products other than vehicles as well, in which case
device 7111 might be located in or attached to whatever product is
subject to being remotely disabled according to the methods
provided herein. In such embodiments, device 7111 is configured and
situated so that it is capable of disabling the subject product
when it receives a message instructing it to do so. For example,
device 7111 can be configured to be able to shut off a power source
(such as 110-volt AC) to an appliance or other product.
[0107] In one embodiment, device 7111 receives communications from
middleware 7106 via the same physical medium as is used to power
the product (such as AC power lines). Such an arrangement prevents
owner 7110 (or some other individual) from disabling communications
with middleware 7106 without also cutting off power to the product.
Such an embodiment may be effective for payment enforcement on
appliances that run on AC power.
[0108] Device 7111 can include additional components to enhance
functionality. In one embodiment, device 7111 includes a WiFi
repeater to enable communication with vehicle 7109 or other
products. The repeater is capable of enabling and/or disabling
certain actions within the vehicle such as fuel, ignition, or other
components. Device 7111 can communicate with middleware 7106 using
any wireless or wired communication channel, including for example
Internet, cellular, radio, GSM, pager, or the like. In one
embodiment, device 7111 periodically polls middleware 7106 for
messages; alternatively, device 7111 is passive and only responds
when middleware 7106 sends messages. In one embodiment, device 7111
has an IP address so that it can be directly addressed via the
Internet protocol.
[0109] Messages 7107A and 7107B may be encoded using any known
encoding scheme or protocol. In one embodiment, messages 7107A and
7107B are password-protected and/or encrypted to reduce the
possibility of interception and/or tampering.
[0110] Referring now to FIG. 8B, there is shown a flowchart
depicting an example of a method of alerting a vehicle owner of a
payment event according to an embodiment of the present invention.
The method of FIG. 8B is similar to that of FIG. 8A, although it is
performed in response to a payment event (such as an indication
that payment has been received). In response to detection 8207 of
such an event, message 8202 is transmitted to onboard device 7111
and relayed 8203 to wireless device 7152 via PAN 7600. Device 152
outputs 8204 an alert informing the owner 7110 that payment has
been received and that continued operation of vehicle 7109 is
therefore enabled. Optionally, receipt of the message at onboard
device 7111 causes device 7111 to enable 8208 operation of vehicle
7109.
[0111] Referring now to FIG. 8C, there is shown a flowchart
depicting an example of a method of sending a disablement message
to onboard device 7111 via wireless device 7152 according to an
embodiment of the present invention. Here, upon detection 8201 of a
nonpayment event, operations center 7101 transmits 8209 a message
directly to wireless device 7152 using a wireless carrier or
equivalent. Wireless device 7152 then relays a message 8210 to
onboard device 7111 via PAN 7600, instructing device 7111 to
disable vehicle 7109. In effect, then, wireless device 7152
effectively forms part of the communications conduit between
operations center 7101 and onboard device 7111. Wireless device
7152 also outputs 8204 an alert or other message to owner 7110.
Device 7111 disables 8205 vehicle 7109.
[0112] In one embodiment, when wireless device 7152 outputs 8204
the alert, vehicle owner 7110 is given an opportunity to respond,
to provide payment information, or to communicate directly with
operations center 7101 for example via voice communications. In
this way, vehicle owner 7110 is given an opportunity to convince
operations center 7101 to cancel or reverse the disablement of
vehicle 7109.
[0113] Referring now to FIG. 8D, there is shown a flowchart
depicting an example of a method of sending an enablement message
to onboard device 7111 via wireless device 7152 according to an
embodiment of the present invention. The method of FIG. 8D is
similar to that shown in FIG. 8C, except that an enablement message
is being sent in response to a payment event. Upon detection 8207
of a payment event, operations center 7101 transmits 8209 a message
directly to wireless device 7152 using a wireless carrier or
equivalent. Wireless device 7152 then relays a message 8210 to
onboard device 7111 via PAN 7600, instructing device 7111 to enable
vehicle 7109 (if vehicle 7109 has previously been disabled).
Alternatively, the message to device 7111 can specify an extension
of an operability period for vehicle 7109, for example in an
environment where a "fail-safe" system has been implemented that
results in automatic disablement unless periodic extensions are
received. Wireless device 7152 also outputs 8204 an alert or other
message to owner 7110 indicating that the payment event has been
processed and acknowledged. Device 7111 performs the appropriate
action 8208 to enable vehicle 7109, if required.
[0114] Referring now to FIG. 8E, there is shown a flow diagram
depicting an example of a method of receiving payment via wireless
device 7152 in response to a payment due event according to an
embodiment of the present invention.
[0115] Operations center 7101 detects 8211 a payment due event, and
transmits 8209 a message to wireless device 7152 requesting
payment. Alternatively, the message can be sent to onboard device
7111 which relays it to wireless device 7152. Alternatively,
wireless device 7152 can be equipped to periodically request
payment on its own without receiving communication from operations
center 7101.
[0116] Wireless device 7152 prompts 8251 owner 7110 for payment.
Owner 7110 may reply by entering a credit card number, or bank
account number, or by other means. Alternatively, owner 7110 may
swipe a credit card at a swiper device (not shown) connected to
wireless device 7152 or to onboard device 7111. Alternatively,
owner 7110 may wave an RF-enabled key fob at an RF detector (not
shown) connected to wireless device 7152 or to onboard device 7111.
In any case, if user input or response is received 8212 indicating
payment, wireless device 7152 transmits 8213 payment information to
operations center 7101. Alternatively, payment information can be
transmitted to onboard device 7111 via PAN 7600 and relayed to
operations center 7101. Wireless device 7152 sends a message 8214
to onboard device 7111 to enable vehicle 7109 operation.
Alternatively, the message to device 7111 can specify an extension
of an operability period for vehicle 7109, for example in an
environment where a "fail-safe" system has been implemented that
results in automatic disablement unless periodic extensions are
received.
[0117] If, in 8212, no user input or response indicating payment is
received, wireless device 7152 transmits 8215 non-payment
information to operations center 7101. Alternatively, payment
information can be transmitted to onboard device 7111 via PAN 7600
and relayed to operations center 7101. Wireless device 7152 sends a
message 8216 to onboard device 7111 to disable vehicle 7109
operation.
[0118] Referring now to FIG. 8F, there is shown a flow diagram
depicting an example of a method of receiving payment via wireless
device 7152 according to an embodiment of the present invention.
Owner 7110 provides 8231 user input at wireless device 7152 to
indicate payment, for example by entering a credit card number, or
bank account number, or by other means. Alternatively, owner 7110
may swipe a credit card at a swiper device (not shown) connected to
wireless device 7152 or to onboard device 7111. Alternatively,
owner 7110 may wave an RF-enabled key fob at an RF detector (not
shown) connected to wireless device 7152 or to onboard device 7111.
Wireless device 7152 transmits 8232 payment information to
operations center 7101. Alternatively, payment information can be
transmitted to onboard device 7111 via PAN 7600 and relayed to
operations center 7101. Wireless device 7152 sends a message 8233
to onboard device 7111 to enable vehicle 7109 operation.
Alternatively, the message to device 7111 can specify an extension
of an operability period for vehicle 7109, for example in an
environment where a "fail-safe" system has been implemented that
results in automatic disablement unless periodic extensions are
received.
[0119] Referring now to FIG. 9A, there is shown a method of
enabling direct communication between a vehicle owner and an
operations center according to an embodiment of the present
invention. Wireless device 7152 can be used for initiating direct
communication between operations center 7101 and owner 7110, at the
behest of either party. In one embodiment, vehicle owner 7110 or
other user may request direct communication with operations center
7101 to alert operations center 7101 as to an impending payment
delay, absence, or other information. Alternatively, an
administrator 104 at operations center 7101 may wish to contact
owner 7110, in order to check on status of a payment, expired
credit card information, or other concerns, or the communication
may be initiated automatically in response to some triggering
event.
[0120] In either case, direct communication is initiated 9311, for
example using a conventional cellular network. The communication
mechanism can include any or all of voice, SMS, email, or the like.
As part of the communication, if appropriate, operations center
7101 can send 9312 a message to wireless device 7152 to re-enable
or disable vehicle 7109; wireless device 7152 relays 9313 such a
message to onboard device 7111, which in turn re-enables or
disables 9315 vehicle 7109. For example, if, in the course of
communicating with operations center 7101, owner 7110 initiates a
payment process for example by authorizing a bank account debit, it
may be appropriate to re-enable vehicle 7109 after a previous
disablement.
[0121] FIG. 9B depicts a method similar to that shown in FIG. 9A.
However, in FIG. 9B, operations center 7101 sends 9314 a
re-enablement or disablement message directly to onboard device
9314 (for example via wireless carrier 7119); onboard device 9314
in turn re-enables or disables 9315 vehicle 7109.
[0122] In one embodiment, owner 7110 can initiate communication
with an emergency services provider or roadside assistance provider
via wireless device 7152.
[0123] In an alternative embodiment, in response to a request to
initiate communication 9311, device 7111 initiates wireless
communication with wireless device 7152 via PAN 7600, and further
initiates communication with operations center 7101 via wireless
modem 7120 and wireless carrier 7119. Device 7111 thus functions as
an intermediary in facilitating communication between wireless
device 7152 and operations center 7101.
[0124] In one embodiment, the communication between owner 7110 and
operations center 7101 is a live voice communication that is
enabled using known Bluetooth protocols. In other embodiments,
other communication means are implemented such as text (SMS)
messaging, email messages, GSM, MMS, ZigBee, and/or the like.
[0125] Referring now to FIG. 10A, there is shown a flow diagram
depicting an example of a method of enabling password entry on
wireless device 7152 for validation at operations center 7101
according to an embodiment of the present invention. In embodiments
where vehicle owner 7110 is given a password that enables continued
use of vehicle 7109, a keypad or other input component of wireless
device 7152 can be used to receive such password. Accordingly, the
method begins with user input 10401 of the password at wireless
device 7152. The password may be encrypted at wireless device 7152
for greater security. The password is then transmitted 402 to
onboard device 7111 via PAN 7600. Onboard device 7111 forwards
10403 the password via wireless carrier 7119 to operations center
7101. At operations center 7101, the password is validated 10406.
If the password is in fact valid, operations center 7101 transmits
a message (either directly to onboard device 7111 or via wireless
device 7152) causing vehicle 7109 operation to be re-enabled or
enabled 10404. Alternatively, the message can specify that an
operability period for vehicle 7109 should be extended for some
period of time, for example in an environment where a "fail-safe"
mode of operation is in place. If the password is not valid,
operations center 7101 can optionally transmit a message to
wireless device 7152 to prompt the owner 7110 to re-enter the
password; alternatively, or after some number of failed attempts,
operations center transmits a message (either directly to onboard
device 7111 or via wireless device 7152) causing vehicle 7109
operation to be disabled 10404. In an environment where a
"fail-safe" mode of operation is in place, no message need be sent,
as the operability period for vehicle 7109 will expire of its own
accord, at which point device 7111 automatically disables vehicle
7109 until it receives instructions to the contrary.
[0126] FIG. 10B depicts a method similar to that of FIG. 10A,
except that the password is transmitted directly from wireless
device 7152 to operations center 7101 (for example via a cellular
telephone network), without being relayed through onboard device
7111. Any known technique can be used for such transmission,
voice/DTMF tones, SMS, email, or the like.
[0127] Referring now to FIG. 10C, there is shown a flow diagram
depicting an example of a method of enabling password entry on
wireless device 7152 for validation at wireless device 7152
according to an embodiment of the present invention. The user, such
as owner 7110, inputs 10406 the password at wireless device 7152.
Wireless device 7152 validates 10407 the entered password using
validation software or other component(s) that allow it to
determine whether the entered password is valid. If wireless device
7152 determines 10408 that the entered password is valid, wireless
device 7152 transmits 10409 a message to operations center 7101
indicating that a valid password has been entered; this
transmission 10409 can take place directly, or via PAN 7600 and
onboard device 7111. In one embodiment the password itself is not
sent, so as to minimize the possibility of interception. Also,
wireless device 7152 can display a message to owner 7110 to
indicate that the entered password is valid. Operations center 7101
transmits a message (either directly to onboard device 7111 or via
wireless device 7152) causing vehicle 7109 operation to be
re-enabled or enabled 10413. Alternatively, the message can specify
that an operability period for vehicle 7109 should be extended for
some period of time, for example in an environment where a
"fail-safe" mode of operation is in place.
[0128] If wireless device 7152 determines 10408 that password is
not valid, it displays 10410 a message to owner 7110 to indicate
that the entered password is not valid, and determines 10412
whether a maximum number of password entry attempts have been made.
If the maximum number has not been reached, wireless device 7152
prompts 10411 the owner 7110 to re-enter the password. If the
maximum number of attempts has been made, in one embodiment
operations center transmits a message (either directly to onboard
device 7111 or via wireless device 7152) causing vehicle 7109
operation to be disabled 10414. In an environment where a
"fail-safe" mode of operation is in place, no message need be sent,
as the operability period for vehicle 7109 will expire of its own
accord, at which point device 7111 automatically disables vehicle
7109 until it receives instructions to the contrary. In one
embodiment, if the maximum number of attempts has been made,
operations center contacts 10415 the lender, seller, and/or an
administrator to inform them of the problem.
[0129] In one embodiment, device 152 is locked out after a maximum
number of unsuccessful password entry attempts have been made.
[0130] FIG. 10D depicts a method similar to that of FIG. 10C,
except that the password is transmitted 10402 to onboard device
7111 and validated 421 at onboard device 7111. In one embodiment,
the password is encrypted before being transmitted 10402. Onboard
device 7111 validates 421 password. The method then proceeds as
described above in connection with FIG. 10C.
[0131] Referring now to FIGS. 7A through 7C, there is shown a
series of screenshots depicting a user interface for password entry
on a cell phone or similar device according to one embodiment. In
FIG. 13A, screen 13700 is displayed, including prompt 13701 asking
the owner to enter a passcode (or password). The owner can enter
the password using the keypad of the cell phone or other device. In
one embodiment, the password is not displayed on screen 13700 for
security purposes.
[0132] In FIG. 13B, screen 13710 includes message 13702 indicating
that the entered password has been approved.
[0133] In FIG. 13C, screen 13720 includes message 13703 indicating
that the entered password has been denied. The owner is advised to
contact customer service. In one embodiment, the cell phone can
automatically dial customer service; a message such as "Dialing . .
. " can be added to screen 13720 to inform the owner that customer
service is being called.
[0134] One skilled in the art will recognize that the screen shots
depicted in FIGS. 7A through 7C are examples only, and that many
other layouts and arrangements are possible without departing from
the essential characteristics of the present invention.
[0135] Referring now to FIG. 11, there is shown a flow diagram
depicting an example of a method of enabling adjustment of
preferences and options for onboard device 7111 via a user
interface presented at wireless device 7152 according to an
embodiment of the present invention. Such a method can be initiated
by owner 7110, for example to set preferences, or it can be
initiated by an administrator on behalf of operations center 7101,
for example to set warning periods and other parameters for
operation of onboard device 7111.
[0136] At wireless device 7152, the administrator or other user
(such as owner 7110) initiates 11501 a command to adjust
preferences and/or options. If appropriate, a password or security
code is validated 11502 or a biometric validation mechanism is
invoked to ensure that the individual attempting to make the
adjustments is authorized to do so. A user interface is then opened
11503 that permits the individual to adjust the operation of
onboard device 7111. Once the individual confirms the changes, a
message is transmitted 11504 to onboard device 7111 to implement
the adjustments. In this manner, the keypad and/or other input
mechanisms of wireless device 7152 can be used as an interface for
controlling the operation of onboard device 7111.
[0137] In the specification, certain components of the invention
may be described in terms of algorithms and/or steps performed by a
software application. In many cases, such descriptions are intended
to set forth the invention using representations that are commonly
used among those of skill in the arts. Accordingly, any
descriptions that refer to algorithms, method steps, functional
components, and the like, shall be considered to encompass
electrical, magnetic, optical, and/or mechanical signals
representing such algorithms, method steps, functional components,
such signals being capable of being stored, transmitted, input,
output, and/or otherwise manipulated. Reference to these signals as
variables, bits, symbols, values, and the like may appear herein
and is not intended to limit the scope of the claimed invention in
any way.
[0138] All such terms, and any similar terms, are to be considered
labels only, and are intended to encompass any appropriate physical
quantities or other physical manifestations. Any particular naming
or labeling of the various modules, protocols, features, and the
like is intended to be illustrative; other names and labels can be
used.
[0139] In addition, various terms such as "processing",
"calculating", "determining", "transmitting", or the like, may be
used herein. Such terms are intended to refer to processes
performed by a software and/or hardware device such as a computer
system. Such terms refer to various types of manipulation and/or
transformation of physical and/or electronic components such as
registers and memories within the device. These physical and/or
electronic components typically represent data elements to be
transformed, transmitted, and/or output.
[0140] Furthermore, the invention can be implemented as a method,
system, computer program product, user interface, or any
combination thereof.
[0141] The present invention also relates to a system for
performing various steps and operations as described herein. This
system may be a specially-constructed device such as an electronic
device, or it may include one or more general-purpose computers
that can follow software instructions to perform the steps
described herein. Multiple computers can be networked to perform
such functions. Software instructions may be stored in any computer
readable storage medium, such as for example, magnetic or optical
disks, cards, memory, and the like.
[0142] The method steps, user interface layouts, displays, and
other components described herein can be implemented on any
computer, network, or other apparatus capable of performing the
functions described. No limitation as to operation on a particular
type of system or apparatus is implied. No particular programming
language is required; rather, any type of programming language can
be used to implement the present invention.
[0143] References to "one embodiment" or "an embodiment" indicate
that a particular element or characteristic is included in at least
one embodiment of the invention. Although the phrase "in one
embodiment" may appear in various places, these do not necessarily
refer to the same embodiment.
[0144] One skilled in the art will recognize that the invention can
be practiced according to many embodiments other than those
described herein, without departing from the essential
characteristics of the present invention. The particular
descriptions set forth above are intended to be illustrative
examples only, and are not intended to limit the scope of the
invention. For example, the onboard device 116, particularly in the
relay embodiments, may be just a relay operated at the behest of a
digital output of the wireless communication system 118, thus
omitting the processor 112 and memory 114. It is intended that the
following claims be interpreted to embrace all such variations and
modifications.
* * * * *