U.S. patent application number 15/339716 was filed with the patent office on 2017-04-06 for system for managing vehicle information displayed on a plurality of vehicles.
This patent application is currently assigned to LFORMATION PTY LTD. The applicant listed for this patent is LFORMATION PTY LTD. Invention is credited to Paul Wilson.
Application Number | 20170098270 15/339716 |
Document ID | / |
Family ID | 48986345 |
Filed Date | 2017-04-06 |
United States Patent
Application |
20170098270 |
Kind Code |
A1 |
Wilson; Paul |
April 6, 2017 |
SYSTEM FOR MANAGING VEHICLE INFORMATION DISPLAYED ON A PLURALITY OF
VEHICLES
Abstract
A system for managing vehicle information displayed on a
plurality of vehicles, said system including a central computer
system and plurality of electronic display devices (EDD), each
being associated with one of said vehicles and each being in
electronic communication with the central computer system (CCS).
The CCS includes one or more computer processors; computer readable
data storage; and a CCS computer program stored on said data
storage, the CCS program being executable by the processors to
perform the steps of selecting a vehicle from said plurality of
vehicles; generating vehicle data representing information about
said vehicle; and sending said vehicle data to an associated one of
said EDDs. Each one of said EDDs includes one or more computer
processors; computer readable data storage; an EDD computer program
stored on said data storage; and a visual display unit, the EDD
program being executable by the processors to perform the steps of
receiving vehicle data from the CCS representing information about
an associated vehicle; and displaying said vehicle data
representing information about the associated vehicle on the visual
display unit.
Inventors: |
Wilson; Paul; (Victoria,
AU) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
LFORMATION PTY LTD |
Melbourne |
|
AU |
|
|
Assignee: |
LFORMATION PTY LTD
Melbourne
AU
|
Family ID: |
48986345 |
Appl. No.: |
15/339716 |
Filed: |
October 31, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14438166 |
Apr 23, 2015 |
9514482 |
|
|
PCT/AU2013/000812 |
Jul 23, 2013 |
|
|
|
15339716 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F 3/0482 20130101;
G06Q 30/0265 20130101; G06Q 50/26 20130101; G06F 3/03 20130101;
G06F 3/14 20130101; G06Q 10/0833 20130101; G06Q 30/0641 20130101;
G06Q 30/0266 20130101 |
International
Class: |
G06Q 30/06 20060101
G06Q030/06; G06F 3/14 20060101 G06F003/14 |
Foreign Application Data
Date |
Code |
Application Number |
Oct 23, 2012 |
AU |
2012904627 |
Claims
1. A system for managing vehicle information displayed on a
plurality of vehicles, said system including a central computer
system and plurality of electronic display devices (EDD), each
being associated with one of said vehicles and each being in
electronic communication with the central computer system (CCS),
wherein: said CCS includes one or more computer processors;
computer readable data storage; and a CCS computer program stored
on said data storage, the CCS program being executable by the
processors to perform the steps of: (a) selecting a vehicle from
said plurality of vehicles; (b) generating vehicle data
representing information about said vehicle; and (c) sending said
vehicle data to an associated one of said EDDs, and each one of
said EDDs includes one or more computer processors; computer
readable data storage; an EDD computer program stored on said data
storage; and a visual display unit, the EDD program being
executable by the processors to perform the steps of: (a) receiving
vehicle data from the CCS representing information about an
associated vehicle; and (b) displaying said vehicle data
representing information about the associated vehicle on the visual
display unit.
Description
RELATED APPLICATIONS
[0001] This application is a continuation of and claims priority to
U.S. application Ser. No. 14/438,166 filed Apr. 23, 2015, which is
a 371 national phase application of PCT/AU2013/000812, filed Jul.
23, 2013, which claims foreign priority to Australian patent
application serial no. 2012904627, filed Oct. 23, 2012, all of
which are incorporated herein in their entirety by this
reference.
[0002] This application is related to U.S. patent application
publication 2015/0269621, published Sep. 24, 2015, all of which is
incorporated by reference herein in its entirety.
TECHNICAL FIELD OF THE INVENTION
[0003] The present invention relates to a system for managing
vehicle information displayed on a plurality of vehicles.
BACKGROUND OF THE INVENTION
[0004] Regulations from various government organisations require
that specific vehicle information must be displayed to customers on
the right rear window of a car which is being offered for sale. For
example, a first type of form is used for vehicles that are subject
to statutory warrantee; less than 10 years old and less than
100,000 km travelled. Alternatively, another type of form is used
for vehicles not covered by statutory warrantee; over 10 years old
or more than 100,000 km travelled.
[0005] The information must be affixed to the rear, right-side
window (where possible) and typically includes: [0006] The last
owner of the motor car; [0007] The distance travelled by the motor
car entered by the motor car trader; [0008] The cash price of the
motor car; [0009] A statement that the cash price does not include
transfer fee or stamp duty; [0010] Car registration period; [0011]
Car built date, compliance date, Date car first registered; [0012]
Model number; [0013] Registration number; [0014] Engine number;
[0015] If RWC is provided; [0016] Statement informing the
prospective purchaser of the warrantee period and the cooling off
period; [0017] LMCT identification, name; [0018] Signature of the
Motorcar trader; and [0019] Space for the Purchaser to sign--upon
sale of the motor car.
[0020] Currently, car dealerships mount a printed piece of paper
(form) on the rear, right window of a vehicle. Any time vehicle
information requires updating, such as a change in the drive away
price or a change in the odometer reading, the dealer needs to
print and mount a new form. This can be very inconvenient for both
the dealership and the customer.
[0021] In addition to the above described difficulties, dealership
owners are also faced with difficulties in locating vehicles around
the lot. For example, a potential buyer may take a car for a test
drive picking up the car from one point and dropping it off at
another. The vehicle has changed positions on the lot and it may be
difficult to later locate.
[0022] Further, it is sometimes the case that a person taking a car
for a test drive may violate a traffic rule. In the case of a
speeding ticket, for example, the dealer may only learn of the
incident a week or two after the violation has occurred. In a busy
dealership, it can be a difficult process to track backwards to
positively identify who was driving the vehicle at the time when
the violation occurred.
[0023] It is generally desirable to overcome or ameliorate one or
more of the above mentioned difficulties, or at least provide a
useful alternative.
SUMMARY OF THE INVENTION
[0024] In accordance with one the invention, there is provided a
system for managing vehicle information displayed on a plurality of
vehicles, said system including a central computer system and
plurality of electronic display devices (EDD), each being
associated with one of said vehicles and each being in electronic
communication with the central computer system (CCS), wherein:
[0025] said CCS includes one or more computer processors; computer
readable data storage; and a CCS computer program stored on said
data storage, the CCS program being executable by the processors to
perform the steps of: [0026] (a) selecting a vehicle from said
plurality of vehicles; [0027] (b) generating vehicle data
representing information about said vehicle; and [0028] (c) sending
said vehicle data to an associated one of said EDDs, and [0029]
each one of said EDDs includes one or more computer processors;
computer readable data storage; an EDD computer program stored on
said data storage; and a visual display unit, the EDD program being
executable by the processors to perform the steps of: [0030] (a)
receiving vehicle data from the CCS representing information about
an associated vehicle; and [0031] (b) displaying said vehicle data
representing information about the associated vehicle on the visual
display unit.
[0032] Preferably, the CCS program being executable by the
processors to perform the steps of: [0033] (a) associating a
vehicle with an EDD by sending an association request to an EDD;
[0034] (b) receiving an association confirmation from said EDD; and
[0035] (c) recording said association in said data storage.
[0036] Preferably, the EDD program being executable by the
processors to perform the steps of: [0037] (a) receiving an
association request from the CCS; [0038] (b) sending an association
confirmation to the CCS; and [0039] (c) recording said association
in said data storage.
[0040] Preferably, the EDD program being executable by the
processors to perform the steps of: [0041] (a) recording log
information about the associated vehicle; and [0042] (b) sending
said log information to the CCS.
[0043] Preferably, the CCS program being executable by the
processors to perform the steps of: [0044] (d) receiving log
information from one of said EDDs; and [0045] (e) recording the log
information in said data storage.
[0046] In accordance with the invention, there is also provided a
central computer system (CCS) for managing vehicle information
displayed on electronic display devices (EDDs) displayed on a
plurality of vehicles, including one or more computer processors;
computer readable data storage; and a CCS computer program stored
on said data storage, the CCS program being executable by the
processors to perform the steps of: [0047] (a) selecting a vehicle
from said plurality of vehicles; [0048] (b) generating vehicle data
representing information about said vehicle; and [0049] (c) sending
said vehicle data to an associated one of said EDDs, and
[0050] Preferably, the CCS program being executable by the
processors to perform the steps of: [0051] (a) associating a
vehicle with an EDD by sending an association request to an EDD;
[0052] (b) receiving an association confirmation from said EDD; and
[0053] (c) recording said association in said data storage.
[0054] Preferably, the CCS program being executable by the
processors to perform the steps of: [0055] (a) receiving log
information from one of said EDDs; and [0056] (b) recording the log
information in said data storage.
[0057] In accordance with one the invention, there is also provided
a computer program for a central computer system (CCS) for managing
vehicle information displayed on electronic display devices (EDDs)
displayed on a plurality of vehicles, including one or more
computer processors; computer readable data storage; and a CCS
computer program stored on said data storage, the CCS program being
executable by the processors to perform the steps of: [0058] (a)
selecting a vehicle from said plurality of vehicles; [0059] (b)
generating vehicle data representing information about said
vehicle; and [0060] (c) sending said vehicle data to an associated
one of said EDDs, and
[0061] Preferably, the CCS program being executable by the
processors to perform the steps of: [0062] (a) associating a
vehicle with an EDD by sending an association request to an EDD;
[0063] (b) receiving an association confirmation from said EDD; and
[0064] (c) storing said association in said data storage.
[0065] Preferably, the CCS program being executable by the
processors to perform the steps of: [0066] (a) receiving log
information from one of said EDDs; and [0067] (b) recording the log
information in said data storage.
[0068] Preferably, the step of recording log information includes
the step of recording vehicle usage.
[0069] In accordance with one the invention, there is also provided
an electronic display device (EDD) for managing vehicle
information, including one or more computer processors; computer
readable data storage; an EDD computer program stored on said data
storage; and a visual display unit, the EDD program being
executable by the processors to perform the steps of: [0070] (a)
receiving vehicle data from a central computer system (CCS)
representing information about an associated vehicle; and [0071]
(b) displaying said vehicle data representing information about the
associated vehicle on the visual display unit.
[0072] Preferably, the EDD program being executable by the
processors to perform the steps of: [0073] (a) receiving an
association request from the CCS for an associated vehicle; [0074]
(b) sending an association confirmation to the CCS; and [0075] (c)
recording said association in said data storage.
[0076] Preferably, the EDD program being executable by the
processors to perform the steps of: [0077] (a) recording log
information about the associated vehicle; and [0078] (b) sending
said log information to the CCS.
[0079] Preferably, the step of recording log information includes
the step of recording vehicle usage.
[0080] In accordance with one the invention, there is also provided
a computer program for an electronic display device (EDD) for
managing vehicle information, including one or more computer
processors; computer readable data storage; an EDD computer program
stored on said data storage; and a visual display unit, the EDD
program being executable by the processors to perform the steps of:
[0081] (a) receiving vehicle data from a central computer system
(CCS) representing information about an associated vehicle; and
[0082] (b) displaying said vehicle data representing information
about the associated vehicle on the visual display unit.
[0083] Preferably, the EDD program being executable by the
processors to perform the steps of: [0084] (a) receiving an
association request from the CCS for an associated vehicle; [0085]
(b) sending an association confirmation to the CCS; and [0086] (c)
recording said association in said data storage.
[0087] Preferably, the EDD program being executable by the
processors to perform the steps of: [0088] (a) recording log
information about the associated vehicle; and [0089] (b) sending
said log information to the CCS.
BRIEF DESCRIPTION OF THE DRAWINGS
[0090] Preferred embodiments of the present invention are hereafter
described, by way of non-limiting example only, with reference to
the accompanying drawing in which:
[0091] FIG. 1 is a schematic diagram of a system for managing
vehicle information displayed on a plurality of vehicles;
[0092] FIG. 2 is a schematic diagram of a computer system for
implementing the system shown in FIG. 1;
[0093] FIG. 3 is a schematic diagram of an electronic display
device of the system shown in FIG. 1;
[0094] FIG. 4 is a functional block diagram of hardware components
of an exemplary embodiment of the computer system shown in FIG.
2;
[0095] FIGS. 5 and 6 are exemplary embodiments of an event driven
architecture of a software application of the computer system shown
in FIG. 2;
[0096] FIG. 7 is a functional block diagram of software components
of an exemplary embodiment of the electronic display device shown
in FIG. 3;
[0097] FIG. 8 is a flow diagram showing steps performed by the
computer system shown in FIG. 2;
[0098] FIG. 9 is a flow diagram showing steps performed by the
electronic display device shown in FIG. 3;
[0099] FIG. 10 is a flow diagram showing further steps performed by
the electronic display device shown in FIG. 3;
[0100] FIG. 11 is a flow diagram showing further steps performed by
the computer system shown in FIG. 2; and
[0101] FIGS. 12 to 37 are views displayed on the electronic display
device shown in FIG. 3 and/or the personal computer device shown in
FIG. 1.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION
[0102] The system 10 shown in FIG. 1 is used to manage vehicle
information displayed on a plurality of vehicles 18. The system 10
includes a central computer system (CCS) 12 and plurality of
electronic display devices (EDD) 14, each being associated with one
of the vehicles 18 and each being in electronic communication with
the CCS 12.
[0103] The EDDs 14 are adapted to be mounted on the
rear-drivers-side window of respective vehicles 18, and will
display all the vehicle information required by the car trader's
legislation, such as dealership LMCT, odometer reading and drive
away price.
[0104] Most of the information displayed on an EDD 14 during the
time that the vehicle is offered for sale is static for example
vehicle make, warrantee information and model registration numbers.
However some of the display information is subject to change such
as the offered sales prices and vehicle odometer mileage. The
system 10 provides a means to automatically update the non-static
information in response to vehicle 18 usage such as the number of
test drives and the amount of time that the vehicle has been on
offer in the car lot.
[0105] Once a car 18 has been sold, the device 14 may be reloaded
with information about other vehicles 18.
[0106] The system 10 also provides means for recording a location
of a vehicle 18 so that it can be located on the dealership.
Further, the system 10 provides means for recording driver
information and tracking vehicle 18 movement. As such, if a traffic
violation occurs, then the person driving the vehicle at the time
can be identified.
The System 10
[0107] The system 10 is provided by a central computer system (CCS)
12 that includes a server in communication with a database 16, as
shown in FIG. 2. The computer system 12 is able to communicate with
electronic display devices (EDDs) 14 coupled to vehicles 18 of the
system 10 over a communications network 20 using standard
communication protocols. The computer system 12 is also able to
communicate with user equipment 19 of the system 10 over a
communications network 20 using standard communication
protocols.
[0108] The user equipment 19 can be a variety of communications
devices such as personal computers; interactive televisions; hand
held computers etc. Hand held computers include products such as
iPhones, IPads, iPods and their android equivalents. The
communications network 20 preferably includes the Internet,
telecommunications networks and/or local area networks.
[0109] The components of the CCS 12 can be configured in a variety
of ways. The components can be implemented entirely by software to
be executed on standard computer server hardware, which may
comprise one hardware unit or different computer hardware units
distributed over various locations, some of which may require the
communications network 20 for communication. A number of the
components or parts thereof may also be implemented by application
specific integrated circuits (ASICs).
[0110] In the example shown in FIG. 2, the CCS 12 is a commercially
available server computer system based on a 32 bit or a 64 bit
Intel architecture, and the processes and/or methods executed or
performed by the CCS 12 are implemented in the form of programming
instructions of one or more software components or modules 22
stored on non-volatile (e.g., hard disk) computer-readable storage
(HDD) 24 associated with the computer system 12. At least parts of
the software modules 22 could alternatively be implemented as one
or more dedicated hardware components, such as application-specific
integrated circuits (ASICs) and/or field programmable gate arrays
(FPGAs).
[0111] The computer system 12 includes at least one or more of the
following standard, commercially available, computer components,
all interconnected by a bus 25: [0112] 1. random access memory
(RAM) 26; [0113] 2. at least one computer processor 28, and [0114]
3. external computer interfaces 30: [0115] a. a first universal
serial bus (USB) interface 30a for connection to EDDs; [0116] b. a
second universal serial bus (USB) interface 30b (at least one of
which is connected to one or more user-interface devices, such as a
keyboard, a pointing device (e.g., a mouse 32 or touchpad), [0117]
c. a network interface connector (NIC) 30c which connects the
computer system 12 to a data communications network 18 via the WIFI
modem 35; and [0118] d. a display adapter 30d, which is connected
to a display device 34 such as a liquid-crystal display (LCD) panel
device.
[0119] The computer system 12 includes a plurality of standard
software modules, including: [0120] 1. an operating system (OS) 36
(e.g., Linux or Microsoft Windows); [0121] 2. web server software
38 (e.g., Apache, available at http://www.apache.org); [0122] 3.
scripting language modules (e.g., personal home page or PHP,
available at http://www.php.net, or Microsoft ASP); and [0123] 4.
structured query language (SQL) modules 42 (e.g., MySQL, available
from http://www.mysql.com), which allow data to be stored in and
retrieved/accessed from an SQL database 16.
[0124] Together, the web server 38, scripting language 40, and SQL
modules 42 provide the computer system 12 with the general ability
to allow users of the Internet 20 with standard computing devices
19 equipped with standard web browser software to access the
computer system 12 and in particular to provide data to and receive
data from the database 16. It will be understood by those skilled
in the art that the specific functionality provided by the system
12 to such users is provided by scripts accessible by the web
server 38, including the one or more software modules 22
implementing the processes performed by the computer system 12, and
also any other scripts and supporting data 44, including markup
language (e.g., HTML, XML) scripts, PHP (or ASP), and/or CGI
scripts, image files, style sheets, and the like.
[0125] The boundaries between the modules and components in the
software modules 22 are exemplary, and alternative embodiments may
merge modules or impose an alternative decomposition of
functionality of modules. For example, the modules discussed herein
may be decomposed into submodules to be executed as multiple
computer processes, and, optionally, on multiple computers.
Moreover, alternative embodiments may combine multiple instances of
a particular module or submodule. Furthermore, the operations may
be combined or the functionality of the operations may be
distributed in additional operations in accordance with the
invention. Alternatively, such actions may be embodied in the
structure of circuitry that implements such functionality, such as
the micro-code of a complex instruction set computer (CISC),
firmware programmed into programmable or erasable/programmable
devices, the configuration of a field-programmable gate array
(FPGA), the design of a gate array or full-custom
application-specific integrated circuit (ASIC), or the like.
[0126] Each of the blocks of the flow diagrams of the processes of
the computer system 12 may be executed by a module (of software
modules 22) or a portion of a module. The processes may be embodied
in a machine-readable and/or computer-readable medium for
configuring a computer system to execute the method. The software
modules may be stored within and/or transmitted to a computer
system memory to configure the computer system to perform the
functions of the module.
[0127] The computer system 12 normally processes information
according to a program (a list of internally stored instructions
such as a particular application program and/or an operating
system) and produces resultant output information via input/output
(I/O) devices 30. A computer process typically includes an
executing (running) program or portion of a program, current
program values and state information, and the resources used by the
operating system to manage the execution of the process. A parent
process may spawn other, child processes to help perform the
overall functionality of the parent process. Because the parent
process specifically spawns the child processes to perform a
portion of the overall functionality of the parent process, the
functions performed by child processes (and grandchild processes,
etc.) may sometimes be described as being performed by the parent
process.
Preferred Embodiment of CCS 12
[0128] With reference to the exemplary embodiment shown in FIG. 4,
the architecture of the software for the CCS 12 is preferably event
driven, as depicted in FIG. 5 and FIG. 6. The CCS 12 is preferably
a program running on the server. It shall have a connection to a
radio interface 35 that will allow it to communicate wirelessly to
the local EDDs 14.
[0129] As shown in FIG. 4, the computer program for the CCS 12
operates in the following manner: [0130] a. a USB wireless driver
200 is in communication with a wireless stack 202; [0131] b. a
communications manager 206 is in communication with both the
wireless stack 202 and a display device host 204; [0132] c. an
alarm manager 208 receives input from the communications manager
206 and outputs data to a user display manager 210 and a logger
212; [0133] d. a command transaction manager 214 receives input
from the database manager 216, and is in communication with the
communications manager 206 and the display device proxy 218, the
command transaction manager also outputs data to the logger 212;
[0134] e. the display device proxy communicates with the display
device information database 220; [0135] f. the logger inputs data
into the vehicle log database 222 and the change log database 224;
[0136] i. a vehicle information manager 226 communicates with a
vehicle information database 228; and [0137] j. a user input
manager 230 receives input from a user 232, the user display
manager 210, the display device proxy 218 and the vehicle
information manager 226.
The Electronic Display Devices 14
[0138] The EDDs 14 can be a variety of communications devices such
as personal computers; interactive televisions; hand held computers
etc. Hand held computers include products such as iPhones, IPads,
iPods and their android equivalents. However, the EDDs 14 are
described, by way of non-limiting example, by way of device 14
shown in FIG. 3. The communications network 20 preferably includes
a wireless local area network that uses standard telecommunication
protocols. As shown, the EDDs 14 each include the following
components electrically connected by a bus 101: [0139] a. at least
one computer processor 100; [0140] b. Memory 102; [0141] c.
input/out put interface 104 including a universal serial bus (USB)
interface for connection to the CCS; [0142] d. a battery 106;
[0143] e. a solar panel 108 electrically coupled to the battery
106; [0144] f. user interface controls 110; [0145] g. digital
recording apparatus 112, such as a digital camera or a digital
scanner; [0146] h. a position sensing device, such as a Global
Positioning Receiver 114; [0147] i. an accelerometer 116; [0148] j.
a visual display unit 118, such as a liquid-crystal display (LCD)
panel device; and [0149] k. a 3G interface 120.
[0150] The implementation of the display 118 may be though
monochrome or colour LCD, or E-ink, or any other suitable device.
The user controls 110 preferably includes a gesture or touch screen
interface to allow interactions between the user and the display
118. The input/output interface preferably includes a wireless
interface. The wireless interface is preferably used to update or
reconfigure the vehicle data on the EDD 14. The position sensing
device 114 preferably allows recording movements of the vehicle 18,
including the distance, speed and duration of operation of the
vehicle.
[0151] The wireless I/O interface 104 and the 3G interface 120 are
used to provide additional networking and location information to
external systems. The accelerometer 116 is be used to detect
movement of the EDD 14.
[0152] The EDDs include a computer program stored in memory 102
which is capable of being executed by the one or more processors
100. The program includes the following software components:
1. Display Formatting 300 & Display Driver 302
[0153] These components operate to format the vehicle data to match
requirements for presentation of the data on the display 118. They
also handle difference between display types for Standard and
Extended Versions. The standard version will consist of a segmented
display, whereas the Extended version may be a graphical display,
which will allow more animated displays or advertising.
2. Gesture Driver 304
[0154] The gesture driver 304 drives the hardware that recognises
hand gestures from a customer viewing the EDD 14 and converts,
using the comm. and processing driver 306 these gestures into
commands to modify what is displayed (eg: display advertising, more
vehicle details.
3. Command Processing 306
[0155] Monitors the radio 308 and serial control 310 interface
connections and determines if the EDD 14 is communicating with one
of its associated CCS 12. It also handles commands from the CCS 12
for updating/accessing vehicle data and logging information.
4. Alarm Generation 312
[0156] Handles events from hardware (ie: movement detection 314,
GPS movement 316, Battery Level 318) and generate alarm message to
the CCS 12.
5. Movement Detection 314 & Position Logging 320
[0157] These modules 314, 320 determine if the vehicle or display
EDD 14 is moved. The movement of the EDD 14 results in an
indication message being generated and sent to the CCS 12. The EDD
14 will activate the GPS positioning device 114 and periodically
record the movement. It is anticipated that the wireless
communications to the CCS 12 may be lost when the vehicle is taken
for a test drive. When the EDD 14 is within the range of the CCS 12
the movement tracking information will be downloaded and stored in
the CCS 12 data base. The EDD 14 may calculate the distance
travelled and the information may be used to update the odometer
value displayed.
6. USB Slave Driver 310
[0158] Detects when the EDD 14 is connected to a CCS 12, confirms
that it is connected to its associated CCS 12. It will provide its
unique id and access to its vehicle and logging information. If not
connected to one of its associated CCS(s), access is limited to
reconfiguring the EDD 14, not reading the vehicle or log
information. Allow allocation to new CCS 12, which clears current
Vehicle and Logging information.
7. Wireless stack 322
[0159] Communications protocol stack appropriate to the wireless
communications hardware selected.
Use of the System 10
[0160] With reference to FIG. 8, a person can use the system 10 to
manage vehicle information of a plurality of cars on a caryard by
using his or her computer 19, for example, to accesses system's
login page published by the CCS 12 over the Internet 20. The CCS 12
generates, at step 500, the a login page (not shown) that includes
a text box for a user name and an associated text box for a user
password. The CSS 12 receives, at step 502, the user name and
password correct and compares them against an authorised list of
users. If the user name and password matches an authorised user
name and password, then the CCS 12 generates, at step 504, the
user's profile page (not shown).
[0161] The profile page includes the following function
buttons:
a. Add New Vehicle (not shown); b. Setup New EDD (not shown); c.
Modify EDD (not shown); and e. Where is Vehicle (not shown).
[0162] A detailed description of each one of these operations is
set out below.
a. Add New Vehicle (not Shown)
[0163] If the user wishes to add a new vehicle into the database
16, then he or she executes the "Add New Vehicle" function button.
On execution of this button, the CCS 12 generates, at step 506, a
graphical user interface (GUI) (not shown) that includes text boxes
for the user to input information about the vehicle. For example,
the GUI includes the following text boxes for the following
information about the vehicle: [0164] a. The last owner of the
motor car; [0165] b. The distance travelled by the motor car
entered by the motor car trader; [0166] c. The cash price of the
motor car; [0167] d. A statement that the cash price does not
include transfer fee or stamp duty; [0168] e. Car registration
period; [0169] f. Car built date, compliance date, Date car first
registered; [0170] g. Model number; [0171] h. Registration number;
[0172] i. Engine number; [0173] j. If RWC is provided, then a
statement informing the prospective purchaser of the warrantee
period and the cooling off period; [0174] k. LMCT identification,
name; [0175] l. Signature of the Motorcar trader;
[0176] The GUI preferably also includes the following fields:
[0177] a. Vehicle location; [0178] b. Number of test drives; and
[0179] c. Distance travelled during test drives; and [0180] d.
Customer details
[0181] The system 12 receives, at step 508, data entered into the
relevant text boxes by the user. Once the user has finished
entering data into the relevant text boxes, he or she executes the
"Submit" function button (not shown) and the CCS 12 creates, at
step 510, a new entry in the database 16 for the vehicle and
generates, at step 504, the user profile.
b. Setup New EDD (not Shown)
[0182] If the user wishes to set up an EDD 14 for a vehicle, then
he or she executes the "Setup New EDD" function button. On
execution of this button, the CCS 12 generates, at step 512, a
graphical user interface (GUI) (not shown) that includes a list of
vehicles that are currently in the database 16. The user can select
a vehicle from the list. The CCS 12 receives, at step 514, the
user's selection and prompts, at step 516, the user to turn on an
EDD 14. For example, the CCS 12 generates a message for display on
the user's terminal 19.
[0183] With reference to FIG. 9, when the EDD 14 is turned on, it
initialises, at step 600, the hardware and software in readiness
for association with a new vehicle 18. The EDD 14 then checks, at
step 602, the battery and waits for a connection event.
[0184] The CCS 12 then prompts the user to connect the EDD 14 to
the CCS 12 using a USB cable. Once the connection is detected by
the CCS 12, it sends, at step 518, a message to the EDD 14 to set
up a new vehicle and sends vehicle data representing information
about the vehicle.
[0185] The EDD 14 receives, at step 604, vehicle data from the CCS
and stores this data in the data storage 102. If an error occurred
during the receiving process, then the EDD 14 sends, at step 606,
an error message back to the CCS 12. Otherwise, the EDD 14 sends,
at step 608, a confirmation message back to the CCS 12 that the
data was received properly. The EDD 14 then, at step 610, displays
the vehicle data on the visual display unit 118.
[0186] The CCS 12 waits for confirmation from the EDD 14 that the
upload was successful and then generates, at step 504, the user
profile. The user can then disconnect the EDD 14 from the CCS 12,
take the EDD 14 over to the relevant vehicle 18 and connect it to
the right rear window. The EDD 14 will then display the relevant
vehicle information.
c. Modify EDD (not Shown)
[0187] If the user wishes to update the information about a vehicle
18 being displayed by an EDD 14, then he or she executes the
"Modify EDD" function button. On execution of this button, the CCS
12 generates, at step 520, a graphical user interface (GUI) (not
shown) that includes a list of vehicles 18 that are currently in
the database 16. The user can select a vehicle 18 from the list.
The CCS 12 receives, at step 522, the user's selection and
generates, at step 524, a GUI including editable data boxes of
information about the vehicle 18.
[0188] The CCS 12 receives, at step 526, user input into the
relevant data boxes and when the user executes the "Modify"
function button, the CCS 12: [0189] i. saves the changes into the
database 16; [0190] ii. establishes, at step 528, a connection with
the relevant EDD 14; and [0191] iii. sends, at step 530, the
modified information about the vehicle 18 to the relevant EDD
14.
[0192] The CCS 12 waits for confirmation that the transfer
successfully completed and then generates, at step 504, the user
profile.
e. Where is Vehicle (not Shown).
[0193] If the user wishes to locate a vehicle 18 on the caryard,
then he or she executes the "Where is Vehicle" function button. On
execution of this button, the CCS 12 generates, at step 532, a
graphical user interface (GUI) (not shown) that includes a list of
vehicles 18 that are currently in the database 16. The user can
select a vehicle 18 from the list. The CCS 12 receives, at step
534, the user's selection and retrieves, 536, vehicle location
information from the database 16. On receipt of this vehicle
location information, the CCS 12 generates, at step 538, a GUI
including a map including indicia showing the location of the
vehicle. For example, the CCS 12 takes a GPS location of the
vehicle stored in the database 16 and then uses Google Maps.TM. to
show the location of the vehicle 18.
The EDDs 14
[0194] With reference to FIG. 10, the EDD 14 is woken up by way of
any one of the following events: [0195] a. receipt of a radio
signal from the CCS 12; [0196] b. a timer flagging a change in
state; [0197] c. movement detected by an accelerometer 116; [0198]
d. detection of a USB connection to the EDD 14; and [0199] e. user
input by way of a user gesture, for example.
[0200] On detection of such an event, the EDD 14 initialises, at
step 700, the hardware after a sleep. The EDD 14 also checks, at
step 702, the life of the battery 106. If the event relates to a
USB connection event, then the EDD 14: [0201] a. disables, at step
704, the GPS receiver and stops the GPS logging; [0202] b. updates,
at step 706, the display 118 to show that the USB is connected;
[0203] c. processes, at step 708, the USB commands received from
the CCS 12; [0204] d. updates, at step 712, the vehicle information
stored in memory 102 and updates the display 118 with the new info;
[0205] e. the EDD 14 then checks the connection status of the USB
connection, if the connection has terminated, then the EDD 14
changes to sleep mode. Otherwise, the EDD 14 waits for the next
command from the CCS 12.
[0206] Alternatively, if the event detected by the EDD 14 is not a
USB connection event, then the EDD 14 determines whether the event
relates to an accelerometer event. If it does, then the EDD 14
enables, at step 712, the GPS receiver and starts GPS logging.
Alternatively, if it does not, then the EDD 14 disables, at step
714, the GPS receiver and stops the GPS logging.
[0207] In either case, if a radio event from the CCS 12 occurs,
then the EDD 14 determines if the radio event relates to a vehicle
18 information update. In the event that it does, the EDD 14, at
step 716, receives the updated information, stores the information,
and updates the display 118 with the new information. In either
case, the EDD 14 then transmits, at step 718, the current status to
the CCS 12.
[0208] Again, in either case, if the event relates to a user
gesture, then the EDD 14 processes, at step 720, the user input and
updates the display with the images that result from the user
input.
CCS 12 Polling
[0209] When operating, the CCS 12 executes a program for polling
the EDDs 14. With reference to FIG. 11, from start up, the CCS 12
performs the following operations in that regard: [0210] a. the CCS
12 initialises, at step 800, the hardware for the CCS 12; [0211] b.
requests, at step 802, a status of an EDD 14; [0212] c. receives,
at step 804, a status check back from an EDD 14; [0213] d. if the
status is not normal, then the CCS sends, at step 806, a message to
the CCS 12 administrator; [0214] e. otherwise, the CCS 12 requests,
at step 808, log information from the EDD 14; [0215] f. receives,
at step 810, from the EDD 14 log information; [0216] g. records, at
step 812, the log information in the database 16.
Additional Functionality
[0217] The CCS 12 also has the capacity to send additional
information to an EDD 14. For example, in following the steps shown
in FIG. 8 for modifying the EDD 114 information, the administrator
has the capacity to send additional information such as an
advertising sequence. On receipt of the additional information, the
EDD 14 periodically alternates between displaying the information
about the vehicle and the advertising sequence.
[0218] Alternatively, the user may use the user controls 110 to
prompt the EDD 14 either the display vehicle data only or the
advertising information only. Further the user may use the user
controls 110 to prompt the EDD 14 any additional information about
the vehicle 18.
[0219] The CCS 12 is preferably in electric communication with a
printer 800. The CCS 12 includes a program being executable by the
processors to perform the steps of: [0220] (a) selecting one of the
vehicles 18; [0221] (b) retrieving data representing information
about the vehicle 18 from the data storage 16; and [0222] (c)
sending said data representing information about the vehicle 18 to
the printer 800 to produce a printed document.
[0223] The printed document preferably includes one or more of the
following vehicle data: [0224] (a) vehicle make; [0225] (b) vehicle
warrantee information; [0226] (c) model number and registration
number; [0227] (d) offered sale prices; [0228] (e) vehicle odometer
readings; [0229] (f) dealership LMCT; [0230] (g) drive away price;
[0231] (h) the last owner of the motor car; [0232] (i) the distance
travelled by the motor car entered by the motor car trader; [0233]
(j) a statement that the cash price does not include transfer fee
or stamp duty; [0234] (k) car registration period; [0235] (l) car
built date, compliance date, date car first registered; [0236] (m)
engine number; [0237] (n) if RWC is provided; [0238] (o) statement
informing the prospective purchaser of the warrantee period and the
cooling off period; [0239] (p) signature of the Motorcar trader;
and [0240] (q) space for the Purchaser to sign--upon sale of the
motor car
Exemplary Use of an EDD 14
[0241] As above-mentioned, the system 10 provides means for
recording driver information and tracking vehicle 18 movement. A
sales person can use an EDD 14 to enter and record this
information. With reference to FIG. 10, this process may be
initiated by the sales person waving his or her hand over the EDD
14 which will detect the gesture and process, at step 720, the user
input. Alternatively, the sales person could use the user controls
110 to begin this process. In response to this, the EDD 14 will
generate a display (not shown) including a list of menu
options.
[0242] The user cal elect to access his or her profile on the
system 12 by selecting the "Login" menu option (not shown). In
response to this, the EDD 14 contacts the CCS 12 over the network
20, requests the login page, and displays it on the display 118. As
shown in FIG. 12, Login view 1000 includes text boxes 1002a, 1002b
for respectively receiving user login and password data. On
detection of the user executing the "Login" function button 1004,
the EDD 14 send the user name and password to the CCS 12 for
authorisation. If the user name and password is valid, the CCS 12
send the EED 14 back the user profile view 1006 shown in FIG. 13
for display. The profile 1006 includes an activity feed 1007 which
does not include any entries.
[0243] On selection of the menu button 1008 by the user, the drop
down list 1010 shown in FIG. 14 is displayed which includes the
following menu options: [0244] 1. Start test drive 1012; [0245] 2.
Loan car 1014; [0246] 3. Return car 1016; [0247] 4. Dealership
stats 1018; [0248] 5. personal stats 1020; [0249] 6. Dealership
settings 1022; [0250] 7. Profile settings 1024; [0251] 8. Help
1026; and [0252] 9. Logout 1028.
[0253] The operation of each one of these components of the system
10 is described below in further detail.
1. Test Drive
[0254] On selection of the "Start test drive" function button 1012,
the EDD 14 displays the car search view 1030 shown in FIG. 15 which
includes a list 1032 of vehicles 18 currently in stock for
selection by the user. In the example shown, no vehicles 18 are
listed. However, advantageously, the EDD 14 would show the vehicle
18 which it has been associated with as a pre-selected option.
Alternatively, the view 1030 includes a search text box 1034 and a
"New Car?" function button 1036. If this button 1036 is selected,
the EDD 14 displays the "Add Car" view shown in FIG. 16 which
allows the user to enter the following details of the new vehicle
into the system 12: [0255] 1. Rego 1040; [0256] 2. Stock #1042;
[0257] 3. VIN 1044; [0258] 4. Make 1046; [0259] 5. Model 1048;
[0260] 6. Year 1050; and [0261] 7. Colour 1052.
[0262] The EDD 14 records this information in the system 12 on
execution of the "Next" function button 1052.
[0263] In either case, once the vehicle 18 has been selected, the
EDD displays the Car Damage view 1056 shown in FIG. 17 which gives
the user the opportunity to report whether he or she can see any
damage on the vehicle. If no, then the user executes the "No"
function button 1058a and the EDD 14 displays the Driver Details
view 1060 shown in FIG. 19. Otherwise, if the "Yes" function button
is executed, then the EDD 14 displays the Damage Report view 1062
shown in FIG. 18 which includes a text box 1064 for entering a
description of the observed damage and an "Add Photos" function
button 1066 which allows the user to take one or more photos using
the apparatus 112 of observed damage and record this information.
Once this process is completed, the user executes the "Next" button
1068 and the EDD 14 displays the above-mentioned Driver Details
view 1060 shown in FIG. 19.
[0264] The Driver Details view 1060 includes the following text
boxes for recording driver information: [0265] 1. First Name 1070;
[0266] 2. Last Name 1072; [0267] 3. Email Address 1074; and [0268]
4. Phone Number 1076.
[0269] The view 1060 also includes function buttons 1078, 1080
which, when executed, respectively take photos using the apparatus
112 of front and back sides of the driver's license.
[0270] This information is recorded by the EDD 14 when the "Next"
function button 1082 is executed. The EDD 14 then displays the
Terms & Conditions view 1084 shown in FIG. 20 which includes a
contract 1086 for the driver to read. The driver accepts the
contract by executing the "Accept" function button 1088 and then
signing his or her name in the signature field 1090 of the
Signature view 1092 shown in FIG. 21. Once the signature has been
completed, the driver executes the "Accept" function button 1094
and the EDD 14 displays the Start test drive view 1096 shown in
FIG. 22. This view simply has a "Start" function button 1098 that
is used to start the test drive.
[0271] When the "Start" button is executed, the EDD 14 displays the
Test Drive in Progress view 1100 shown in FIG. 23. This view
includes the following information: [0272] 1. "Recording" indicator
1102; [0273] 2. Time elapsed 1104; [0274] 3. Distance travelled
1106; and [0275] 4. Average speed 1108.
[0276] The EDD 14 will also records the above mentioned logging
information about the associated vehicle 18 in the above described
manner. This logging information also includes vehicle
location.
[0277] The test drive is completed when the sales person executes
the "Finish Drive" function button 1110. The EDD 14 then again
displays the Car Damage view 1056 shown in FIG. 17 which gives the
user the opportunity to report whether he or she can see any damage
on the vehicle. If no, then the user executes the "No" function
button 1058a and the EDD 14 displays the Test Drive Completed view
1112 shown in FIG. 24.
[0278] Otherwise, if the "Yes" function button 1058b is executed,
then the EDD 14 displays the Damage Report view 1062 shown in FIG.
18 which includes a text box 1064 for entering a description of the
observed damage and an "Add Photos" function button 1066 which
allows the user to take one or more photos using the apparatus 112
of observed damage and record this information. Once this process
is completed, the user executes the "Next" button 1068 and the EDD
14 displays the Test Drive Completed view 1112 shown in FIG.
24.
[0279] The Test Drive Completed view 1112 includes the total
elapsed time of the test drive 1114; the total distance driven 1116
and the average speed 1118. The EED 14 also confirms that the
system 10 has sent the driver an e-mail with information about the
vehicle and a request for comment on the quality of the
service.
[0280] The Test Drive Completed view 1112 also include a "Home"
function button 1120 which, when executed, returns user to his or
her profile view 1006 as shown in FIG. 24. As can be seen, the
activity feed 1007 of the profile 1006 includes an entry 1122 for
the recent test drive for Brad Dunn.
2. Loan Car
[0281] A similar process is performed by the EDD 14 when user loans
a vehicle 18. For example, the user selects the "Loan Car" option
1014 from the menu 1008 and the EDD 144 steps through an analogous
process to that set out for test-driving a vehicle 18. For example,
the EDD 14 will perform the following steps: [0282] 1. display the
Car search View 1030 on the visual display unit 118 of the EED 14
and to allow the user to search for the relevant vehicle in the
above described manner; [0283] 2. display the Car Damage view 1056
on the display 118 so that the user can report any damage in the
above described manner; [0284] 3. display the Driver Details view
1060 to record the driver's details in the above described manner;
[0285] 4. display the Terms & Conditions view 1084 for loan
vehicles 18 on the display 118; [0286] 5. display the Signature
view 1092 for loan vehicles 18 on the display 118; [0287] 6.
display the Start Loan view 1126 on the display 118 shown in FIG.
26 and record the details of the loan when the "Start Loan"
function button 1128 is executed; and [0288] 7. display the user
profile view 1006, as shown in FIG. 27.
[0289] As can be seen, the activity feed 1007 of the profile 1006
includes an entry 1130 for the recent loan to Brad Dunn.
[0290] For step 1, the EED 14 preferably suggests the associated
vehicle 18 as a first option of the user.
3. Return Car
[0291] The user selects the "Return Loan Car" option 1016 from the
menu 1008 and the EDD 144 performs the following steps: [0292] 1.
display the Car search View 1132 shown in FIG. 28 on the visual
display unit 118 of the EED 14 and to allow the user to search for
the relevant vehicle in the above described manner; [0293] 2.
display the Car Damage view 1134 on the display 118 so that the
user can report any damage in the above described manner; and
[0294] 3. display the Loan Returned view 1136 informing the user
that the loan car has been successfully returned.
[0295] The Loan Return view 1136 includes a "Home" function button
1138 that returns the user to his or her profile view 1006.
[0296] With regard to step 1, the EED 14 preferably lists the
associated vehicle 18 as a first option to the user.
4. Dealership Stats
[0297] When the user selects the "Dealer Stats" option 1018 from
the menu 1008, the EED 14 displays the Dealer Statistics view 1140
shown in FIG. 31 that includes the following information for the
user: [0298] 1. Account active; [0299] 2. Trips completed; [0300]
3. Test drives completed; [0301] 4. Loans completed; [0302] 5.
kilometres travelled; [0303] 6. Average car rating; and [0304] 7.
Average sales person rating.
[0305] The user returns to the Profile view 1006 by selecting the
"Back" function button 1142.
5. Personal Stats
[0306] When the user selects the "Personal Stats" option 1020 from
the menu 1008, the EED 14 displays the Personal Statistics view
1144 shown in FIG. 32 that includes the following information for
the user: [0307] 1. Account active; [0308] 2. Trips completed;
[0309] 3. Test drives completed; [0310] 4. Loans completed; [0311]
5. kilometres travelled; [0312] 6. Average car rating; and [0313]
7. Average sales person rating.
[0314] The user returns to the Profile view 1006 by selecting the
"Back" function button 1146.
6. Dealer Settings
[0315] When the user selects the "Dealer Settings" option 1022 from
the menu 1008, the EED 14 displays the Dealer Settings view 1148
shown in FIG. 33 that includes the following function buttons:
[0316] 1. Invite Sales Person 1150; [0317] 2. Edit User 1152; and
[0318] 3. Trips Remaining 1154.
[0319] The EED 14 displays the Select User view 1156 shown in FIG.
34 when the Invite sales Person function button 1150 is selected.
The user can select a person from the list 1158 provided.
[0320] The user can edit another user's details by selecting the
"Edit User" function button 1150. On selection of this button 1150,
the EED 14 displays the Edit User view 1160 shown in FIG. 35. This
view includes the following data fields:
1. First Name 1162;
2. Last Name 1164; and
3. Mobile 1166.
[0321] The EED 14 updates the system 10 with the user's amended
information on execution of the "Update" function button 1168.
[0322] The Trips Remaining view 1170 shown in FIG. 36 is displayed
by the EED 14 when the "Trips Remaining" function button 1154 is
selected. The Trips Remaining view lists the associated plan type
and the trip credits.
7. Profile Settings
[0323] When the user selects the "Profile Settings" option 1024
from the menu 1008, the EED 14 displays the Profile Settings view
1172 shown in FIG. 37 that includes the following text boxes:
[0324] 1. First Name 1174; [0325] 2. Last Name 1176; and [0326] 3.
Mobile 1178.
[0327] The EED 14 updates the system 10 with the user's amended
information on execution of the "Update" function button 1180.
[0328] The user returns to the Profile view 1006 by selecting the
"Back" function button 1182.
Alternate Embodiment
[0329] The above-described exemplary use of the EDD 14 has been
made, by way of non-limiting example, with reference to the EDD 14
receiving views published by the CCS 12 and displaying them on a
display 118 for interaction with the user. As above-mentioned, the
EDD 14 is preferably a smart phone, such as an iPhone, that is
capable of interfacing with the CCS 12 to receive and display views
published by the CCS 12. However, the EDD 14 could alternatively
include an application program, stored thereon in computer readable
data storage 102, that generates the same views and displays them
on the display 118 for interaction with the user.
Personal Device 19
[0330] The above-described exemplary use of the EDD 14 could
alternatively be performed by a user with a personal device 19. In
this embodiment, the personal device 19 interacts with the CCS 12
in the above-described manner so as to receive views published by
the CCS 12 and to display them on a display for interaction with
the user. As above-mentioned, the user device 19 is preferably a
smart phone, such as an iPhone, that is capable of interfacing with
the CCS 12 to receive and display views published by the CCS
12.
[0331] The personal device 19 could alternatively include an
application program, stored thereon in computer readable data
storage, that generates the same views and displays them on the
display for interaction with the user.
[0332] Many modifications will be apparent to those skilled in the
art without departing from the scope of the present invention.
[0333] Throughout this specification, unless the context requires
otherwise, the word "comprise", and variations such as "comprises"
and "comprising", will be understood to imply the inclusion of a
stated integer or step or group of integers or steps but not the
exclusion of any other integer or step or group of integers or
steps.
[0334] The reference to any prior art in this specification is not,
and should not be taken as, an acknowledgment or any form of
suggestion that the prior art forms part of the common general
knowledge in Australia.
* * * * *
References