Classifications

• • G—PHYSICS
  • G07—CHECKING-DEVICES
  • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
  • G07C5/00—Registering or indicating the working of vehicles
  • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
  • B60R25/00—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles
  • B60R25/10—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles actuating a signalling device
  • B60R25/102—Fittings or systems for preventing or indicating unauthorised use or theft of vehicles actuating a signalling device a signal being sent to a remote location, e.g. a radio signal being transmitted to a police station, a security company or the owner
• • G—PHYSICS
  • G07—CHECKING-DEVICES
  • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
  • G07C5/00—Registering or indicating the working of vehicles
  • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
  • G07C5/0841—Registering performance data
• • G—PHYSICS
  • G08—SIGNALLING
  • G08G—TRAFFIC CONTROL SYSTEMS
  • G08G1/00—Traffic control systems for road vehicles
  • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles

Definitions

• This disclosu re relates to vehicle monitoring systems and associated methods.
• a low amou nt of fuel can be a problem for a vehicle dealer in that the vehicle cannot be taken out for a test drive and may result in a lost sale.
• a vehicle which has too much fuel cannot be transported and delays will occu r while removing fuel. This can result in the vehicle not getting on the transport (rail, truck, or ship) on time.
• Another example is engine error codes. If a vehicle dealer is trying to sell a vehicle and the customer sees the check-engine error light come on, then the sale is likely to fail.
• At least some aspects of the disclosure to systems and methods which enable monitoring of statuses of various parameters of vehicles and reporting the statuses to one or more persons when appropriate to assist with management and servicing of the vehicles. Other aspects are described below.
• Fig. 1 is an illustrative representation of a vehicle monitoring system according to one embodiment.
• Fig. 2 is a block diagram of a computing device according to one embodiment.
• Fig. 3 is a flow chart of an implementation of use of the vehicle monitoring system according to one embodiment.
• Fig. 4 is a flow chart of a method performed by a monitoring device according to one embodiment.
• Fig. 5 is a flow chart of a method performed by an intermediary device according to one embodiment.
• Fig. 6 is a flow chart of a method performed by a management device according to one embodiment.
• Fig. 7 illustrates operations performed by processing circuitry with respect to execution of events according to one embodiment.
• Fig. 8 illustrates operations performed by processor circuitry with respect to vehicle issues which have not been addressed.
• At least some embodiments of the disclosure include apparatus and methods of monitoring objects.
• the apparatus and methods provide monitoring and tracking of a plurality of vehicles, such as automobiles upon a lot of a vehicle dealership. Other objects may be monitored and tracked in other implementations.
• Example described embodiments provide reliable and trustworthy systems and methods that a bank can believe will correctly report when a vehicle is on a vehicle lot.
• the device will not necessarily indicate when a device is not on a vehicle lot, but if the monitoring device does report that the vehicle is on the lot, then it can be trusted.
• the assu mption is that while the vehicle is on the lot, then the dealer is justified in continuing the loan and will not need to pay off the vehicle loan.
• Banks expect loans for vehicles which are no longer on the lots of the vehicle dealerships, or are otherwise no longer within the inventories of the vehicle dealerships to be paid off. Accordingly, banks may utilize the apparatus and methods of the disclosu re to determine whether the vehicle dealerships are properly following contractual obligations associated with the financing of vehicles which have been sold in one implementation.
• a plu rality of vehicle monitoring devices of a vehicle monitoring system communicate with respective vehicles being monitored and communicate information regarding the vehicles to a management device which may implement vehicle monitoring.
• the management device may provide information regarding the vehicles being monitored to banks as well as other desired parties, such as the vehicle dealerships themselves, in one embodiment.
• some embodiments of the disclosure may be used to provide other information regarding the vehicles being monitored. For example, information regarding the locations of the vehicles on the dealership lots may be provided as well as information indicating if a vehicle monitoring device has been removed from one vehicle and placed in another vehicle.
• FIG. 1 one example embodiment of a vehicle monitoring system 10 is shown.
• the example illustrated system includes a plurality of vehicle monitoring devices 14, one or more intermediary device 16 and a management device 1 8.
• intermediary device 1 6 may be omitted in some embodiments and the monitoring devices 14 may commu nicate directly with management device 1 8.
• the monitoring devices 14 are configured to monitor a plurality of vehicles 1 2, for example, within inventory of a vehicle dealership.
• the monitoring devices 14 may also be referred to as diagnostic devices.
• the monitoring devices 14 are configured to establish respective communications 1 3 with respective vehicles 12.
• the monitoring device 14 communicates with an on-board computer or other circuitry of the vehicle being monitored (e.g., the device 14 may be coupled with an OBD socket of vehicle 12).
• the monitoring device 14 may receive operational energy from the vehicle 1 2 as well.
• the monitoring devices 14 are configured to receive information regarding the vehicles 12 being monitored at a plu rality of moments in time (e.g., continuously) via communications 1 3 and are configu red to generate a plurality of messages including the information regarding the vehicles 12 being monitored and perhaps other data as described further below. Furthermore, the monitoring devices 14 may output the generated messages externally of the monitoring devices 14 via respective communications 1 5. As discussed below, the generated messages may also include timing data which may be used to validate the associated data included within the messages in example embodiments of the disclosure.
• the intermediary device 16 commu nicates with and receives the messages from the monitoring devices 14 via the commu nications 1 5.
• Some embodiments may include a plu rality of intermediary devices 1 6 which communicate with the monitoring devices 14, although only one intermediary device 1 6 is shown in Fig. 1 .
• the intermediary device 16 is a computing device such as a smart phone running an application, a notebook computer, a tablet computer, etc.
• the intermediary device 16 is configu red to receive the messages and data from the monitoring devices 14, including information regarding the vehicles 1 2 being monitored, and to output the received data and perhaps other data as described further below in a plurality of messages via communications 17.
• additional timing data may be added to the messages in one embodiment.
• the additional timing data may include timestamps of the dates and times the respective messages were received by the intermediary device 16.
• the management device 18 commu nicates with and receives the messages from the intermediary devices 1 6 via the communications 1 7 in the illustrated embodiment.
• the management device 18 may receive the messages directly from the monitoring devices 14 in other embodiments.
• the management device 18 is implemented as a server in one possible implementation.
• the management device 1 8 is configured to receive the messages and data from the intermediary devices 1 8 including information regarding the vehicles 1 2 being monitored and additional information.
• the management device 18 processes the received data of the messages and generates reports and alerts with respect to the vehicles or other objects being monitored.
• management device 1 8 is also configu red to generate timing data for the messages corresponding to moments in time when the respective messages are received by the management device 1 8.
• management device 18 may be configu red to monitor and manage vehicles on a plurality of different lots of different vehicle dealerships in one embodiment.
• the commu nications 13, 15, 17 may be implemented using an appropriate form for commu nicating data including wireless and/or wired communications.
• commu nications 1 3, 15, 17 may each be implemented using one or more of Bluetooth, WiFi, cellular, wired connections and/or other wireless communications.
• an example computing device 20 is shown according to one embodiment.
• One or more of the monitoring device 14, intermediary device 1 6 and management device 1 8 have the configu ration of the illustrated computed device 20 in example embodiments.
• computing device 20 includes a user interface 22, processing circuitry 24, storage circuitry 26, and commu nications circuitry 28.
• Other embodiments of computing device 20 are possible including more, less and/or alternative components or circuitry.
• User interface 22 is configu red to interact with a user including conveying data to a user (e.g., displaying visual images for observation by the user) as well as receiving inputs from the user, for example using one or more input device, keyboard, touchscreen, etc.
• processing circuitry 24 is arranged to process data, control data access and storage, issue commands, and control other desired operations.
• Processing circuitry 24 may comprise circuitry configured to implement desired programming provided by appropriate computer-readable storage media in at least one embodiment.
• the processing circuitry 24 may be implemented as one or more processor(s) and/or other structu re configu red to execute executable instructions including, for example, software and/or firmware instructions.
• Other example embodiments of processing circuitry 24 include hardware logic, PGA, FPGA, ASIC, state machines, and/or other structures alone or in combination with one or more processor(s). These examples of processing circuitry 24 are for illustration and other configurations are possible.
• Storage circuitry 26 is configured to store programming such as executable code or instructions (e.g., software and/or firmware), electronic data, databases, or other digital information and may include computer-readable storage media. At least some embodiments or aspects described herein may be implemented using programming stored within one or more computer-readable storage maxim m of storage circuitry 26 and configu red to control appropriate processing circuitry 24. In one embodiment, information regarding vehicles being monitored may be stored using storage circuitry 26.
• programming such as executable code or instructions (e.g., software and/or firmware), electronic data, databases, or other digital information and may include computer-readable storage media. At least some embodiments or aspects described herein may be implemented using programming stored within one or more computer-readable storage maxim m of storage circuitry 26 and configu red to control appropriate processing circuitry 24. In one embodiment, information regarding vehicles being monitored may be stored using storage circuitry 26.
• the computer-readable storage maxim m may be embodied in one or more articles of manufacture which can contain, store, or maintain programming, data and/or digital information for use by or in connection with an instruction execution system including processing circuitry 24 in one embodiment.
• computer-readable storage media may be non-transitory and include any one of physical media such as electronic, magnetic, optical, electromagnetic, infrared or semiconductor media.
• Some more specific examples of computer- readable storage media include, but are not limited to, a portable magnetic computer diskette, such as a floppy diskette, a zip disk, a hard drive, random access memory, read only memory, flash memory, cache memory, and/or other configurations capable of storing programming, data, or other digital information.
• Commu nications circuitry 28 is arranged to implement communications of computing system 1 0 with respect to external devices (not shown).
• commu nications circuitry 28 may be arranged to communicate information bi-directionally with respect to computing system 1 0 and include hardware for wired connections (e.g., network interface card (N IC), serial or parallel connections, USB port, Firewire interface), and/or circuitry for wireless connections (e.g., Bluetooth, Cellular, G PS, WiFi, etc.).
• wired connections e.g., network interface card (N IC), serial or parallel connections, USB port, Firewire interface
• wireless connections e.g., Bluetooth, Cellular, G PS, WiFi, etc.
• the vehicle monitoring system 1 0 uses an independent timing protocol or reference to synchronize the monitoring devices 14 and management device 18 in time and which may be utilized to assure that the generated information regarding the vehicles being monitored is valid and can be trusted.
• the independent timing protocol is independent in the sense that it is not based upon a calendar based timing system (e.g., date and time of day) in one arrangement.
• timing data or information of the independent timing protocol is internally generated within the vehicle monitoring system 1 0 without the use of any communications which originate external of the vehicle monitoring system 1 0, for example G PS signals.
• the use of timing data which is independent of a calendar based timing system provides a system 1 0 of increased security since the timing data is not readily apparent to those not aware of the independent timing protocol or reference being utilized.
• a monitoring device 14 is configu red to generate timing data of the independent timing protocol which is indicative of timing of the information regarding the vehicle (e.g., the timing data may be indicative of moments in time when the respective vehicle information is received from the vehicle).
• the timing data is used to synchronize the management device 18 with the monitoring device 14 and can be used to determine whether the vehicle information contained within the messages commu nicated from the monitoring device 14 is valid or has expired in one implementation.
• the timing data generated by the monitoring device 14 is a plurality of values of a timing variable at different moments in time.
• monitoring device 14 generates a first value of the timing variable that is thereafter incremented periodically to generate subsequent timing data (e.g., incremented values of the timing variable which are indicative of passages of time for the information regarding the vehicle contained within the respective messages from the first value of the timing variable) in accordance with parameters of the independent timing protocol.
• the parameters may define to increment the first (or updated) value of the timing variable by a known amou nt (e.g., one) according to a period (e.g., hou rly).
• the values of the timing variable at the different moments in time are the timing data within the messages which may be used as a rolling timestamp reference of the independent timing protocol in one implementation.
• the timing variable is an integer and the first value of the integer is randomly generated by the monitoring device 14 when the monitoring device 14 is powered-up (e.g., coupled with the OBD port of the vehicle).
• the monitoring device 14 may randomly generate a new first value of the timing variable each time the device 14 is powered-up from a powered-down state in one implementation.
• the first value of the timing variable may be generated by another device (e.g., management device 1 8) and communicated to the monitoring devices 14.
• the management device 1 8 is aware of the independent timing protocol (e.g., the frequency of updates to the value of the timing variable and the amou nt of each update) in one embodiment.
• the management device 1 8 may not receive all messages which are outputted by the monitoring device 14. However, once a message is received from the monitoring device 14, the management device 18 performs a registration process described below with respect to the monitoring device 14 and associated vehicle.
• the value of the timing variable contained within the first message which is received by the management device 18 from the monitoring device 14 may be used as an initial value of the timing variable which corresponds to or indicates an initial reference moment in time of the independent timing protocol. This initial reference moment in time may be used to generate subsequent timing data (e.g., updated values of the timing variable) which may be compared with timing data within subsequent messages which are received from the monitoring device 14.
• the monitoring device 14 and management device 18 may be considered to be synchronized with the independent timing protocol after management device 18 has received the initial value of the timing variable and which may be used as a registration value as described further below.
• the parameters of the independent timing protocol may be changed at different moments in time for additional secu rity of the timing data contained within the messages.
• different parameters of the independent timing protocol may be used for communications of the management device 18 with different monitoring devices 14 in one embodiment.
• the processing circuitry of the monitoring device 14 randomly generates the first value of the timing variable upon power-up and thereafter increments the value of the timing variable.
• different values of the timing variable are timing data which are included within different messages generated by the monitoring device 14 and are associated with different information regarding the vehicle which is received from the vehicle at a plu rality of moments in time.
• the timing data of a given message corresponds to and indicates the respective timing of the receipt of the information regarding the vehicle by the monitoring device 14 which is contained with the message, and which indicates the amount of time which has passed since the initial reference moment in time.
• the values of the timing variable included in the messages correspond to the moments in time when the information regarding the vehicle contained within the respective messages was received by the monitoring device 14.
• the messages including the timing data may be referred to as timestamped messages in one embodiment.
• the value of the timing variable when information regarding the vehicle is received may be associated with the respective information regarding the vehicle in an individual message. Thereafter, the value of the timing variable is incremented and the incremented value indicates the passage of time from the initial reference moment in time to the moment in time when subsequent information regarding the vehicle is received by the monitoring device 14. The incremented value of the timing variable may be associated with the subsequently received information regarding the vehicle in one of the subsequent messages in one embodiment.
• the monitoring device 14 is configu red to determine the first value of the timing variable after the monitoring device 14 is coupled with and establishes communications with the vehicle 12 via the OBD port in one example embodiment. For example, upon coupling with the OBD port of the vehicle 12, the monitoring device 14 receives power from the vehicle 12 and commu nicates with the vehicle 12, and as a result randomly generates the first value of the timing variable. As mentioned previously, one of the monitoring devices 14 implements commu nications 1 3 with respect to a vehicle being monitored, for example, via an OBD port or socket of the vehicle.
• processing circuitry of the monitoring device 14 executes software that queries the vehicle for vehicle information such as the vehicle’s unique vehicle identification nu mber (VIN) and then also receives and encrypts the following data into an encrypted data packet or message (e.g., a 31 -32 byte encrypted code) : (1 ) the queried VI N ; (2) the integer/incremented integer; (3) the monitoring device’s factory-assigned unique media access control (MAC) code; and (4) any other information regarding the vehicle, such as mileage, fuel level, etc.
• vehicle information such as the vehicle’s unique vehicle identification nu mber (VIN)
• VIN vehicle identification nu mber
• MAC factory-assigned unique media access control
• Encryption of the data in the messages adds additional protection to the data therein and increases the difficulty of re-engineering the operations of the system.
• the encrypted data may include the information regarding the vehicle contained within the message as well as the timing data (e.g., value of the timing variable) which indicates the timing of when the information regarding the vehicle was received by the monitoring device 14.
• the monitoring device 14 is configured to periodically and continuously, such as once a second, output the timestamped, encrypted messages via commu nications 1 5.
• the encryption of the data within the messages for example, including the timing data and the VIN of the vehicle, makes it more difficult for other parties to obtain and replicate the data, including the timing data. Without the timing data, it is more difficult for other parties to generate messages which will not be detected as being invalid as described further below.
• intermediary device 1 6 is moved throughout different geographical locations of a lot of the vehicle dealership.
• the intermediary device 16 is placed in a“scan” mode in one implementation to be able to receive the broadcast messages from the monitoring devices 14 of vehicles of the dealership as the intermediary device 1 6 is moved throughout the lot.
• the intermediary device 1 6 receives the messages which were broadcast from the monitoring devices 14, and executes its own software program that may add various data to the messages. For example, in one embodiment, timestamp data indicative of times and dates when the messages were received by the intermediary device 16 and location data (e.g., G PS, latitude, longitude) of the intermediary device 1 6 when the messages were received by the device 16 are added to the messages.
• location data e.g., G PS, latitude, longitude
• management device 18 may add timestamp data to the messages which is indicative of the times and dates when the messages are received by the management device 18 and the intermediary device 1 6 may or may not add its respective timestamp data to the messages.
• the intermediary device 16 comes into the transmission range of the monitoring device 14 and either automatically receives the broadcast messages from the monitoring device 14, or does a scan for devices emitting messages and discovers the broadcast messages. Following the addition of any data to the received messages, the intermediary device 1 6 outputs the timestamped, encrypted data messages (with any additional data) via commu nications 17 to management device 18. In one embodiment, the intermediary device 1 6 does not decrypt the data contained in the received messages, but rather adds additional data to the messages and outputs the messages externally of the intermediary device 1 6 via commu nications 17. In one embodiment, the intermediary device 1 6 is u naware of and cannot access encrypted data of the messages, such as the first timing data (e.g., values of the timing variable).
• the first timing data e.g., values of the timing variable
• the management device 18 receives the transmitted messages from the intermediary device 16 via commu nications 17 and executes a software program that decrypts the messages, and extracts and processes the data therein including the VIN, the MAC, the information regarding the vehicle being monitored, and the value of the timing variable in one embodiment.
• the data may be processed including comparing data within the messages with records of the vehicles being monitored in a database as discussed further below.
• the management device 18 may generate reports and alerts regarding the vehicles being monitored as a result of the processing of the data in the messages and the records in the database. Management device 18 may also add timestamp data to the messages which indicates the times and dates of receipt of the respective messages.
• the management device 18 stores or has access to a stored database with vehicle data records of the vehicles being monitored in one embodiment.
• the management device software searches the database to see if a record exists for the VIN pulled from a received message in one embodiment.
• the database may include a plu rality of records for a plurality of vehicles being monitored.
• the records may correspond to vehicles in an automobile dealer’s inventory which were purchased from a manufacturer using loaned fu nds from a bank or other financial institution.
• the disclosed systems and methods of monitoring vehicles may be used by the bank to verify that the automobiles which have not been sold (and the corresponding loans not paid off) are still on the dealer’s lot in one example application.
• the management device software program creates a“registration” or reference record for the VIN that includes all the data in the message.
• the record includes the initial value of the timing variable which was included in the first message which was received by the management device from the monitoring device as a base timestamp of the independent timing protocol, and to which timing data of subsequently-received messages is compared and which may be used to provide time synchronization of the management device 1 8 with the respective monitoring device 14 which generated the message.
• the initial value of the timing variable may also be referred to as the registration value of the timing variable and corresponds to an initial reference moment in time of the independent timing protocol. This completes the“registration” process for the monitoring device 14 and corresponding vehicle being monitored in the system. Accordingly, in one embodiment, the records of the vehicles being monitored are added to the database over time as messages are received by the management device 1 8.
• the initial value of the timing variable may not be the first value of the timing variable generated by the monitoring device 14. For example, one or more messages including different values of the timing variable may not be received by the management device 18, and accordingly, the initial value of the timing variable may be an updated value of the timing variable which has been updated from the first value.
• the management device software program performs a comparison of the data based on the VI N and stores any new data from the message into the vehicle data record of the respective vehicle in one embodiment.
• the management device 18 processes the data of the received message to determine whether the information regarding the vehicle being monitored and contained within the message is valid (as well as the other data included in the message) in the described embodiment. More specifically, in one embodiment, the processing circuitry of the management device 18 uses different timing data of the messages themselves to determine whether the data contained with the messages is valid.
• the processing circuitry of the management device 18 compares different timing data of the messages (e.g., timing data of the independent timing protocol and timing data of a calendar based timing system) to determine whether the messages and data are valid.
• the processing circuitry uses the first timing data (e.g., initial value of the timing variable and the updated value of the timing variable contained with the current message being processed) as well as the parameters of the independent timing protocol to calculate a first amou nt of time between the message transmitted by the monitoring device 14 (and received by the management device 18) containing the initial (registration) value of the timing variable and the current message being processed.
• the processing circuitry also uses the time and date timing data of the calendar based timing system which is associated with the message which contained the initial value of the timing variable and the cu rrent message being processed to calculate a second amou nt of time between the respective messages.
• the processing circuitry calculates the second amou nt of time using the time and date timestamp of the message which contained the initial value of the timing variable and the time and date timestamp of the current message.
• the first amount of time and second amount of time correspond to different calculations (using different timing protocols) of the passage of time from the initial reference moment in time to the moment in time associated with the current message being processed.
• the different timing protocols are independent from each other in one embodiment, for example, one protocol based upon a calendar while the other protocol is independent of the calendar.
• timing data which is processed is generated by a plu rality of different devices (e.g., monitoring device 14 as well as intermediary device 1 6 and/or management device 18) in one more specific embodiment.
• the first timing data contained with the messages generated by the monitoring device 14 is indicative of timing of the information regarding the vehicle (e.g., when the information regarding the vehicle was received by the monitoring device 14) and the second timing data is indicative of timing of the messages themselves, for example when the messages are received by the intermediary device 1 6 or management device 18.
• the management device 1 8 compares the calculated first and second amou nts of time to determine whether the message and data therein are valid.
• the software allows for a specified grace period of time and the compared amou nts of time are not expected to match exactly.
• the differences in time calculated using the different timing data are within the specified grace period of time (e.g., 2 hours or less difference)
• the message and data are determined to be valid.
• the message and data therein are determined to be invalid if the first and second amou nts of time differ by an amount greater than the grace period.
• the comparison of the different amounts of time determined according to the different timing protocols makes the corresponding data of the message expire in one embodiment.
• the message is valid and the data of the message is stored in the database and the VIN is verified which indicates that the vehicle is on the dealer’s lot. If the time periods do not match up, the software generates an alert of some kind in one embodiment. The alert is used to indicate that there may be an issue with the vehicle which corresponds to the VIN for further investigation in one embodiment.
• a display of the management device 1 8 may communicate the alert and an email or text alert may also be sent from the management device 1 8 to appropriate personnel. Any appropriate form for an alert may be used.
• the monitoring device 14 if the monitoring device 14 is u nplugged from the vehicle 12 for any reason or if the vehicle’s battery is drained and no power is provided to the monitoring device 14 from the vehicle 12, the monitoring device 14 is automatically cleared and needs to be re registered when it’s plugged back into either a new vehicle 1 2 or when the vehicle’s battery is charged and again supplying power to the monitoring device 14. All data is cleared in the monitoring device 14 including the obtained VIN, the value of the timing variable, the MAC, etc. when power is lost in one embodiment.
• the monitoring device 14 When a new power sou rce is supplied, the monitoring device 14 automatically re-generates a new random value of the timing variable, re-queries the on-board computer for the vehicle’s VI N, re-obtains its own MAC address, and begins generation and communication of messages in one arrangement.
• the monitoring device 14 When the monitoring device 14 loses power from the vehicle 12 for any reason, it stops broadcasting messages in one embodiment.
• the failure of the management device 18 to receive a message within a specified amou nt of time for a given record/vehicle is used in one embodiment to generate an alert for further investigation of the vehicle which corresponds to the record. For example, if the broadcast messages from a monitoring device 14 stop, but the system expects them to continue, such as the intermediary device 1 6 coming within range of where the vehicle 12 with the monitoring device 14 is expected to be, the software on the management device 1 8 generates an alert indicating the lack of receipt of a broadcast message from the particular monitoring device 14 so any necessary follow-up can be performed to locate the corresponding vehicle.
• messages from a given monitoring device 14 and based upon the same initial value of the timing variable must be continuously received within a given amou nt of time from previously- received messages from the same monitoring device 14, or otherwise an alert may be generated by the management device 18 and sent to appropriate personnel regarding the corresponding vehicle 12 of the monitoring device 14 for further investigation to determine whether the vehicle 12 is on the dealer’s lot or not.
• the amou nt of time in which the messages are to be received to avoid the generation of an alert may be varied for different implementations. For example, for more risky dealers, the amou nt of time may be less, such as every two days, while the amount of time may be longer, such as every six weeks, for other dealers.
• the vehicle monitoring system 1 0 may also provide additional information regarding the vehicles being monitored. For example, information regarding the locations of the vehicles on the dealership lots may be provided to the dealers on a continuous basis. Referring to Fig. 3, use of systems and methods of the disclosure for vehicle financing by banks is described in one example implementation. As a condition of a bank loan for a vehicle, the dealer agrees to the following conditions in one example:
• the vehicle dealer plugs the monitoring device into the vehicle soon (or immediately) after the loan is started. This will often be soon after the vehicle is dropped at the dealer lot by the factory.
• the vehicle is turned on sometime soon after installation of the monitoring device.
• the exact timing of tu rning on the vehicle is not important.
• the vehicle needs to be turned on at least once before the monitoring device can be detected in one embodiment.
• the monitoring device queries the vehicle for information as discussed previously and also generates the first value of the timing variable. Thereafter, following detection, the vehicle may be turned off and the monitoring device continues to receive operational energy from the vehicle after the vehicle is turned off in one embodiment.
• one or more employees of the vehicle dealership will run an application on their intermediary devices while they are walking the vehicle lots as already part of their jobs.
• the application runs in the background on their intermediary devices and does not require any input from the intermediary device operators in one embodiment. Except for manual vehicle verification discussed below in act A1 6, this example vehicle monitoring application does not require any more additional walking by the employees then is already being done throughout the work day. While vehicle monitoring may be accomplished using one intermediary device, all employees who routinely walk the lots or move vehicles, may have associated intermediary devices to provide improved results, such as more frequent updates with respect to the vehicles being monitored.
• the monitoring device when the vehicle is sold, then the monitoring device will be removed from the vehicle and kept by the dealer for use on a different vehicle later.
• the dealer benefits in having instant access to the last known location of the vehicle on his lot in one embodiment. This instant access of vehicle location may be provided to a dealer for a fee in one arrangement.
• Some of the benefits of the systems and methods of the disclosure to the bank include less expensive audits as a person may not be needed to do the audit or the person will not be spending as much time doing the audit. Nearly instant audits may be performed at an increased frequency (currently audits are done every 2 to 6 months in some arrangements). In addition, issues or problems regarding financed vehicles may be caught earlier. By doing audits more frequently, problems are caught sooner as well as cause the dealer to be more prompt and honest in dealing with the bank. In addition, loans to smaller dealers may become more practical which may open new markets for the bank (cu rrently small dealers in out-of-the-way locations can be prohibitively expensive to audit).
• Vehicle mileage information may be provided since the last time that the OBD was cleared which will help indicate to the bank whether excessive mileage has been added to the vehicle since the start of the loan.
• Information regarding fuel and battery levels of the vehicles may be provided to the dealer for use and information regarding the last time that the vehicle was started may be provided to the bank which helps establish the existence of the engine in the vehicle.
• information may be provided indicating if a vehicle monitoring device has been removed from one vehicle and placed in another vehicle (e.g., by recognizing the failure of the management device to receive a message from the initial vehicle as well as recognizing the receipt of the new messages from the same monitoring device which is coupled with the subsequent different vehicle).
• a flow chart of operations performed by a monitoring device are described according to one embodiment. Other embodiments are possible including more, less and/or alternative acts. The described acts are controlled using processing circuitry of the monitoring device in one embodiment.
• communications are established between a vehicle to be monitored and a monitoring device.
• the monitoring device may be coupled with the OBD port of the vehicle in one arrangement.
• the monitoring device obtains a first value of a timing variable of the independent timing protocol for time synchronization with other devices.
• the first value of the timing variable may be randomly generated and used for the initial message regarding the vehicle in one embodiment.
• the monitoring device periodically increments the value of the timing variable a known amou nt in accordance with the independent timing protocol, and additional messages after the initial message include the respective updated values of the timing variable which also correspond to the moments in time when the additional messages are generated in one embodiment.
• the monitoring device receives information regarding the vehicle being monitored as discussed above.
• the monitoring device generates a message including the first (or updated) value of the timing variable and the information regarding the vehicle.
• the data within the message is encrypted in one embodiment.
• the monitoring device commu nicates the generated message externally of the monitoring device.
• the process of Fig. 4 returns to act A32 and continuously generates and outputs additional messages with new data corresponding to the moments in time when the additional messages are generated and/or vehicle information is received from the vehicle being monitored.
• FIG. 5 a flow chart of operations performed by an intermediary device are described according to one embodiment. Other embodiments are possible including more, less and/or alternative acts. The described acts are controlled using processing circuitry of the intermediary device in one embodiment.
• An intermediary device in the vicinity of the monitoring device receives an outputted message from the monitoring device at an act A40.
• the intermediary device adds additional data to the message including a timestamp (e.g., date/time information and location data of the intermediary device from G PS when the message is received).
• a timestamp e.g., date/time information and location data of the intermediary device from G PS when the message is received.
• the intermediary device communicates the message with the additional data externally of the intermediary device.
• the method of Fig. 5 returns to act A40 and the intermediary device continues to monitor for the reception of additional messages from the monitoring device at act A40 which are processed as discussed above.
• a flow chart of operations performed by a management device are described according to one embodiment. Other embodiments are possible including more, less and/or alternative acts. The described acts are controlled using processing circuitry of the management device in one embodiment.
• the management device receives the message communicated by the intermediary device.
• the management device decrypts and extracts the data of the received message.
• the management device uses the VIN contained within the message to determine whether a record exists for the respective VIN.
• the process proceeds to an act A56 and a registration operation for the vehicle is performed including storing the data of the message including the value of the timing variable as the initial value of the timing variable which is used as an initial timing reference and synchronizes the management device in time with the monitoring device. Thereafter, the management device monitors for the receipt of additional messages.
• the management device determines whether the data and the message are valid at an act A60.
• the management device uses the timing data of the different timing protocols in order to validate the data and message.
• the management device may use the respective values of the timing variable and the date/time information of the message which contained the initial value of the timing variable and the currently processed message to calculate respective amounts of time which have passed since registration to determine whether the data and message are valid.
• the currently processed message includes first timing data in the form of the updated value of the timing variable which may be used with the initial value of the timing variable to calculate a period of time which has passed between the message which contained the initial value of the timing variable and the current message being processed according to the independent timing protocol.
• the message also includes second timing data in the form of the date/time timestamp (added to the message by the intermediary device or the management device) and the timestamp may be used with the timestamp of the initial message received from the monitoring device regarding the vehicle to calculate another period of time which has passed between the initial message and the current message. If the periods of time calculated using the first and second timing data are within a grace amount of time (e.g., within two hours), then the data is determined to be valid and is stored. Otherwise, the data is determined to be invalid.
• a grace amount of time e.g., within two hours
• the management device If the result of act A60 is negative, the management device generates and commu nicates an alert to appropriate personnel at an act A62 and which indicates that the data of the vehicle is invalid and further investigation of the vehicle may be performed. If the result of act A60 is affirmative or following act A62, the management device monitors for the receipt of additional messages regarding the vehicle from the monitoring device.
• the monitoring device may be unplugged from a vehicle (for example to allow a service/scanning device to be coupled with the vehicle using the OBD port). Thereafter, the monitoring device may again be plugged into the same vehicle following the service. In this situation, the new value of the timing variable received by the management device after the monitoring device was again plugged into the vehicle would not match the expected value of the timing variable before the monitoring device was unplugged. In one embodiment, the management device would generate an alert due to the mismatch of the value of the timing variable. In addition, the management device may use the received mismatched value of the timing variable as a new initial or registration value of the timing variable for use with respect to validating subsequently received messages.
• the monitoring devices 14 of the vehicle monitoring system 1 0 each include communications circuitry which can implement wired and/or wireless communications.
• the monitoring devices 14 can communicate with respective circuitry including computer systems of the vehicles 12 to receive vehicle information regarding the vehicles, and which may include status information regarding one or more parameters of the vehicles, such as battery state (e.g., voltage), fuel level, error codes, last time the vehicle was started and other information described below.
• battery state e.g., voltage
• fuel level e.g., fuel level
• error codes last time the vehicle was started and other information described below.
• the monitoring devices 14 can also include memory or other storage circuitry 26 to store digital information, such as executable code, and data received from the vehicles 12.
• the monitoring devices 14 can further include processing circuitry 24 configured to execute code, control commu nications with external devices including reception of messages from devices 14 and access or retrieval of vehicle information from the vehicles 1 2 and forwarding of the vehicle information to an intermediary device 1 6 and/or management device 18, control storage of the vehicle information using the storage circuitry of the devices 14, and implement communications with additional external devices via the communications circuitry 28.
• management device 18 monitors statuses of one or more parameters of the vehicles 12 being monitored to identify issues with respect to the vehicles 12, such as low battery voltage. Following the identification of vehicles with issues, the management device 18 performs additional operations including notifying different parties with respect to addressing or resolving the issues regarding the vehicles 1 2 in a timely manner. As discussed according to one example embodiment below, the management device 18 may initially notify a party responsible for addressing or resolving the issues within the vehicles 1 2 and subsequentially notify another party responsible for assuring that the identified issues of the vehicles 12 are addressed or resolved in a timely manner.
• the monitoring devices 14 commu nicate the vehicle information in one or more messages regarding a vehicle 1 2 being monitored to management device 1 8 which uses the received vehicle information to implement additional operations as discussed below.
• messages of the external communications including the vehicle information from the monitoring devices 14 to the management device 18 are reported periodically.
• the monitoring devices 14 are configu red to use any appropriate method of communications, including wired commu nications and/or wireless communications, such as Cellular, Wi-Fi and Bluetooth directly to management device 18 or via an intermediary device 1 6 described above.
• Management device 18 includes appropriate commu nications circuitry to receive the messages which include vehicle information from the monitoring devices, storage circuitry to store the vehicle information in one or more databases, and processing circuitry configu red to access and process the received vehicle information and implement example operations discussed below as a result of the processing.
• the processing circuitry of the management device 1 8 processes status information within the messages regarding parameters of the vehicles to identify various issues with respect to the vehicles 12.
• One example issue may be one or more vehicles 12 have a low battery voltage as mentioned above which needs to be addressed or resolved, for example by charging and/or replacing the batteries of the vehicles 12.
• the battery level status information e.g., voltages
• the processing circuitry may perform additional operations as a result of the processing of the status information including notifying one or more recipient parties via communications regarding issues with the vehicles 12 being monitored and which need to be addressed.
• management device 18 processes the vehicle information and may generate and send automated messages to specified people, for example via text or email, to indicate the issues or problems which need to be addressed for specific vehicles 12. After a predefined passage of time, if those specified people have not addressed the issues of the vehicles 1 2 and updated the resolution of the issues of the vehicles 12 in the management device 1 8, then another notification message is sent to a second specified person such as a manager to indicate that the initial person has not completed his/her work in addressing the issues with one or more of the vehicles 1 2.
• management device 18 receives messages, processes the vehicle information therein, and sends communications to appropriate recipient parties regarding issues of the vehicles 12 automatically in the absence of instruction from a user to the management device 18 to perform the functions.
• the monitoring devices 14 are coupled with respective vehicles 12 to be monitored.
• the monitoring device 14 is coupled with the OBDI I port of the vehicle 1 2 while the vehicle is left upon a lot an automobile dealer, or other premises where vehicles are being monitored.
• the monitoring device 14 queries the computer system of the vehicle 1 2 for various information at a plurality of different moments of time such as periodically while the vehicle 1 2 is on the vehicle lot.
• the monitoring device 14 includes a unique I D for identification and which may be 6 bytes of hexadecimal. In one illustrative example, the following information is gathered by the monitoring device 12 from the vehicle 12 :
• VIN 17 or 18 digit number which is compressed into a 1 3-byte number using encoding into a base-40 nu mbering system
• Engine Error Codes up to four engine error codes of 4-byte hexadecimals each
• Timing information When the vehicle was last turned on : 3-byte integer indicating the number of 4.6875 second increments since the device was first placed in the vehicle. This gives a maximum of 91 0 day span in this example.
• the monitoring device 14 accesses the vehicle information and operates as a beacon to broadcast the information periodically, such as every 750 milliseconds, via messages as shown in Fig. 1 .
• the intermediary device 16 is moved throughout a vehicle lot, receives vehicle information from the vehicles 12, and forwards the received vehicle information in messages to the management device 1 8 for processing and generation of notifications to appropriate personnel regarding the status of parameters of the vehicles 12 and indicating any issues thereof, such as a low battery level.
• the monitoring devices 14 commu nicate directly with the management device 18, for example, via the Internet, without use of intermediary device 16.
• a Bluetooth Low Energy (BLE) 32-byte packet is used to implement wireless commu nications 15 from the monitoring devices 14 in one embodiment.
• This commu nications technology has relatively low energy usage and is used to reduce or minimize drain of the vehicle’s battery which powers the monitoring device 14 in one embodiment.
• Other communications protocols may be used in other embodiments including ultra-low-power wireless protocols such as: ANT, Zigbee, RF4CE, I EEE 802.11 ah.
• other commu nications such as use of a mesh network may be utilized to commu nicate vehicle information from the monitoring devices 14.
• the vehicle information gathered from the vehicle 14 is sent in a plurality of 32-byte packets including a first packet type which contains the VIN of the vehicle along with the u nique identifier of the monitoring device 14 and a second packet type which contains the vehicle information regarding the vehicle, for example including status information of various parameters of the vehicles, such as battery voltage, fuel level, mileage, etc.
• the identification of the monitoring device 14 is increased to 16 bytes of hexadecimal and three packet types are used including :
• a third packet of additional vehicle information (e.g., battery voltage, fuel level, etc.) with up to a 1 6-byte monitoring device identifier
• the packets may be alternated when communicated from the monitoring device 14.
• the monitoring device 14 is configu red to communicate the packets with a predefined time period of delay (e.g., 750 milliseconds) therebetween to conserve the battery of the vehicle 1 2 being monitored.
• the management device 14 can also store information regarding the first time that the vehicle was placed on a dealer’s lot and monitor the length of time the vehicle remains on the dealer’s lot with respect to a threshold length of time.
• the monitoring devices 14 are configured as beacons to only transmit data and are incapable of processing communications received by the intermediary device 16 or management device 18. In other embodiments, monitoring devices 14 are configu red to output communications, for example including vehicle information, as well as receive and process inbou nd commu nications to the monitoring devices 14.
• management device 1 8 resides on a cloud service and implements one or more relational databases (e.g., Structu red Query Language - SQL) with respect to vehicle information which is received from the plurality of monitoring devices 14.
• relational databases e.g., Structu red Query Language - SQL
• Management device 18 maintains a vehicle information database including a record of vehicle information regarding each vehicle 1 2 being monitored including different statuses of different parameters of the vehicles in one embodiment.
• the following example information regarding parameters of the vehicles 1 2 may be stored in a respective record of the vehicle information database for each vehicle 12 :
• VIN of vehicle 1 7 or 18 digit alpha-numeric (uniquely identifies each vehicle)
• Engine Error Codes Coded, correlates to Engine Error Codes Database
• Last Ru ntime date and time of when vehicle was last turned on (format date)
• Company I D alpha-nu meric, correlate to the Company database (e.g., owner of the lot where the vehicles are stored)
• Last date/time vehicle was reported on : (e.g. “2018-06-14
• management device 1 8 also maintains an engine error codes database which includes the following information for each numerical error code which may be returned by the computer systems of vehicles 1 2 being monitored by the monitoring devices 14 :
• Website Webpage indicating problem and possible solution for the error code
• management device 1 8 monitors statuses of one or more parameters of the vehicles 12 being monitored to identify a plurality of issues with respect to the vehicles 1 2, such as low battery voltage, and to implement appropriate operations towards having the issues addressed or resolved.
• the management device 18 performs additional operations including initially notifying one party responsible for addressing the issues of identified vehicles 12 having the issues, and subsequentially notifying another party responsible for assu ring that the issues of the vehicles 12 are addressed or resolved in a timely manner if issues of the vehicles 1 2 remain after predefined or specified amounts of time.
• the management device 1 8 is configu red to execute a plurality of different events at a plu rality of moments in time to identify respective individual issues of the vehicles 12 which need to be addressed or resolved.
• the events include different sets of programming instructions, such as different scripts, which are individually executed by the processing circuitry during the execution of a respective event to identify a list of vehicles 12 having the respective issue in accordance with the specific event being executed.
• the status information regarding a respective parameter of the vehicles 12 is processed du ring the execution of the event to identify the list of the vehicles 12 having the issue of the respective event being executed.
• the programming instructions of the different events may be executed periodically as well as simultaneously or individually to identify the vehicles having the respective issues.
• management device 1 8 also maintains an event database including the events.
• the events each include programming instructions in the form of scripts in the described embodiment which the processing circuitry of the management device 1 8 executes to process the status information of the respective parameter (e.g., battery voltage) being monitored for the respective event and to identify the vehicles 1 2 having the respective issue being monitored du ring the execution of the event vehicles.
• a separate event is created for each parameter of the vehicles 12 being monitored.
• Example information for a low battery voltage event within the event database includes :
• Event I D alpha-numeric, unique I D of this event
• Event Title e.g.“Report Battery less than x volts”.
• Company I D alpha-numeric, correlate to the Company database
• time-span e.g. 24 hours, 3 days, 22 minutes
• DateTime e.g.“201 8-07-1 5 1 5:33”.
• Script Database script to check for issues of vehicles on a dealer’s lot and present within the vehicle information database (e.g. identify all vehicles in the vehicle information database having a battery voltage less than x volts)
• Service Person contact method e.g. email, text, phone call
• Service Person contact details e.g. someone@mail.com, 503- 555-1212
• Time period in which problem must be addressed defines moment in time in the future to address the issue determined by a specified time-span from present time (e.g. 24 hours, 3 days, 22 minutes)
• Service Manager contact method e.g. email, text, phone call
• Each of variables Value 1 - Value 4 above may be specified by the dealer or set to default levels (e.g., 1 1 Volts may be set as the default low battery voltage threshold).
• Last time vehicle has been ru n If this is off hours when the dealer is closed, then u nauthorized use of the vehicle may have occurred
• Vehicle driven off premises e.g., a geo-fence
• Vehicle has not been moved for too long Vehicles need to be slightly moved to stop flat-spots on tires and engines need to be run periodically.
• Management device 18 additionally maintains an event queue database which is used to monitor the correction of issues of the vehicles 12 being monitoring in one embodiment.
• the event queue database stores a plu rality of lists of vehicles having respective different issues which need to be addressed as a result of the processing of the status information.
• the event queue database stores the following information for each event:
• Event I D correlates to the event database (e.g., low battery voltage event)
• VIN List list of VINs of vehicles which had this issue or problem
• Expire Time time by which the issue of the event should be addressed or the manager will be informed (e.g. “2018-07-31 20 :00”)
• the management device 18 is sent the data packets from the monitoring device 14 or intermediary device 16 (if utilized).
• the received vehicle information within the data packets is stored in the vehicle information database of the management device 1 8 in one embodiment.
• Extra information regarding the vehicles 12 being monitored may be extrapolated from the vehicle information by the processing circuitry of the management device 1 8 as needed.
• Example extrapolated information includes “Change in Mileage From First date/time vehicle was reported” and“Time vehicle is on dealer lot.”
• Additional information gathered from the monitoring device 14 or intermediary device 1 6 may also be stored within the vehicle information database, such as location information which is indicative of the location of the vehicle 12 being monitored as detected by location circuitry (e.g., G PS) of the monitoring device 14 or intermediary device 1 6.
• location circuitry e.g., G PS
• status information regarding one or more parameters of the vehicles is processed to identify issues with respect to the vehicles. Thereafter, the processing circuitry of the management device 18 may perform one or more operations in attempts to address or resolve the identified issues of the vehicles 1 2.
• One example operation is generating and outputting a communication to a recipient party who is responsible for addressing or resolving the issues of the vehicles 1 2, such as specified mechanics or vehicle servicemen for attending to the issues.
• battery voltage status information of the vehicles may be processed by comparing the battery voltages of the vehicles 1 2 with a threshold and all vehicles 1 2 having a battery voltage less than the threshold may be identified and reported to service personnel or other appropriate recipient.
• the length of time in which the vehicle has been on a dealer’s lot may be compared with a threshold length of time and all vehicles 1 2 exceeding the threshold may be identified and reported to a sales manager or other appropriate recipient.
• An additional example operation is generating and outputting a commu nication to another recipient party who is responsible for assuring that the issues of the vehicles 12 have been addressed or resolved in a timely manner, such as a service manager of an automobile dealership. Additional example operations and details thereof which may be performed by management device 12 are described below.
• FIG. 7 one example method performed by processing circuitry of the management device 1 8 operating as an event handler with respect to execution of events with respect to vehicles 12 monitored by the monitoring devices 14, and implementing operations in response to the execution of the events is shown. Other methods are possible including more, less and/or alternative actions.
• the management device 14 periodically (e.g., every minute) the management device 14 checks its event database (Action 1 ) to identify individual events (e.g., low battery voltage, fuel level, etc.) which need to be executed during the present execution of the method of Fig. 7.
• Event database Action 1
• individual events e.g., low battery voltage, fuel level, etc.
• the sets of programming instructions for the respective events needing to be checked are loaded and executed by the processing circuitry.
• executing the low battery voltage event includes updating the“Next time to check this event” field at Action 2 to be the current time plus the time defined in“How often to check” of the event being executed to define when the low battery voltage event is to be next executed.
• the processing circuitry runs the database script for the low battery voltage event against each vehicle being monitored in the vehicle information database to identify those vehicles with a low battery voltage.
• the management device 18 monitors vehicles of a plurality of different entities, such as different automobile dealers, different automobile rental companies , etc. and the events can be executed against the vehicles in the vehicle information database which are associated with a single entity during the execution of the low battery voltage event and the low battery voltage event may be executed against vehicles in the vehicle information database which are associated with other entities during subsequent executions of the low battery voltage event.
• processing circuitry first identifies the list of vehicles in the records of the vehicle information database which belong to a given entity using the“Company I D” field of the vehicle records stored in the vehicle information database, and then the low battery voltage event is executed against the identified list of vehicles which belong to the entity to identify those with a low battery voltage.
• an appropriate commu nication (e.g., SMS, email, phone call, etc.) is generated and sent to the appropriate person indicated in the event using the Person Name who is responsible for addressing or resolving the issues regarding the vehicles (title, first & last name), Person contact method (e.g. email, text, phone call) and Person contact details set forth in the event.
• the communication includes an initial list of vehicles having the issue being monitored during the event execution of the event (e.g., low battery voltage).
• the commu nication may also include various additional information of the vehicles with an issue.
• the management device is configured to generate the communication to include information regarding an error code if the execution of an event detects the presence of an error code from one or more of the vehicles.
• the management device generates and stores an action item to be performed at a moment in time in the future to determine whether the corresponding issue of the vehicles has been addressed at an Action 5.
• a manager checkup entry or record is created in the event queue database. This entry includes the list of VINs of the vehicles identified in Action 3 as having low battery voltage and the moment in time in the futu re when the action item is to be performed.
• the moment in time in the future is an“Expire Time” which is set to the current time plus“Time period in which problem must be addressed” of the event.
• FIG. 8 additional details implemented by the management device 18 with respect to monitoring of the manager checkup entry or records within the event queue database are shown according to one embodiment.
• checking the event queue database includes for each record, determining if the record has a“Expire Time” later than now, and if so do nothing for the presently analyzed record and proceed to the next record. This process is repeated for each manager checkup entry or record u ntil a record is identified with an “Expire Time” which has passed in time.
• the manager checkup entry or record is deleted from the event queue database.
• the processing circuitry reads details resulting from the previous execution of the event from the event database using the event I D from the event queue database and which identifies the initial list of vehicles which had the issue being monitored by the respective event (e.g., initial list of vehicles with low battery voltage and which was commu nicated to the responsible service personnel).
• the script for the respective event (e.g., programming instructions for identifying vehicles with low battery voltage) identified by the Event I D is again executed against the initial list of vehicles which includes the vehicles which had a low battery voltage when the manager checkup entry or record was created du ring the execution of Fig. 7. Any vehicles which still report as true (e.g., those vehicles having a low battery voltage after the Expire Time) go into a new or updated vehicle list for the respective manager checkup entry or record being processed.
• the processing circuitry processes the initial list and new list of vehicles to identify the vehicles which are present in both lists (i.e., the intersection of the initial vehicle list of vehicles having low battery voltage when the entry or record was created during the execution of Fig. 7 and the new vehicle list of vehicles having low battery voltage during the execution of Fig. 8). This processing is performed by the processing circuitry to remove vehicles from the list which have had the respective issues addressed or resolved.
• the processing circuitry 1 8 If the intersection of vehicles is not empty, the processing circuitry 1 8 generates and outputs a commu nication to a recipient party who is responsible for assuring that the issues of the vehicles 12 have been addressed and as a result of the issue not having been addressed for at least one vehicle within the specified amou nt of time.
• the management device generates and sends the communication to the service manager at an Action 5 indicating the original message sent to the initially notified person(s), the time frame that was expected for the servicing of the vehicle to be completed, and identifiers of the vehicles (e.g., VINs) which are on the intersection list. This information informs the manager of vehicles 1 2 still requiring service to address one or more issue detected by the monitoring devices 14.
• Additional information that could be added to the messages sent to the initial service person and manager may include the locations of the vehicles having issues as well as the year, make, model, and color and any other useful information of the vehicles.
• the processing circuitry of the management device is configured to automatically generate and output the initial communication to the recipient party responsible for addressing or resolving issues of the vehicles in the absence of input from a hu man, to automatically generate, store and review action items in the absence of input from a hu man, and to automatically generate and output another communication to a recipient party responsible for assuring that the issues of the vehicles are timely addressed or resolved when issues of one or more vehicles have not been resolved in the absence of input from a human.
• the vehicles with low battery voltages or other issues are automatically reported to service personnel and managers according to one embodiment.
• the monitoring and reporting of vehicles with issues to service personnel and managers are automatic without intervention of a user in one implementation as discussed above.
• service personnel can then charge the batteries of the vehicles, start the vehicles without needing to jumpstart or perform other maintenance.
• the reason for the battery drain can also be addressed. For instance, the lights were left on or the key was left in the ignition of the vehicles.
• the service manager will receive messages indicating which of the vehicles on the lot need servicing and permit follow-up monitoring to verify that the servicing has addressed the issues with the vehicles in a timely manner. This results in a revenue stream for the dealer’s service department, and accordingly, sending messages on the health of the vehicles reduces cost, time, and generates revenue according to some aspects of the disclosure.
• aspects herein have been presented for guidance in construction and/or operation of illustrative embodiments of the disclosure. Applicant(s) hereof consider these described illustrative embodiments to also include, disclose and describe further inventive aspects in addition to those explicitly disclosed. For example, the additional inventive aspects may include less, more and/or alternative featu res than those described in the illustrative embodiments. In more specific examples, Applicants consider the disclosu re to include, disclose and describe methods which include less, more and/or alternative steps than those methods explicitly disclosed as well as apparatus which includes less, more and/or alternative structure than the explicitly disclosed structure.

Landscapes

• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Engineering & Computer Science (AREA)
• Mechanical Engineering (AREA)
• Traffic Control Systems (AREA)

Priority Applications (1)

Applications Claiming Priority (2)

Publications (2)

Family

ID=69164760

Family Applications (1)

Country Status (3)

Family Cites Families (8)

• 2019
  • 2019-07-16 DE DE19837133.8T patent/DE19837133T1/de active Pending
  • 2019-07-16 WO PCT/US2019/042075 patent/WO2020018588A1/en unknown
  • 2019-07-16 EP EP19837133.8A patent/EP3823864A4/de active Pending

Also Published As

Similar Documents

Legal Events