Patent Application
20210082207
The present disclosure is generally related to a system and method for collecting data regarding the operation of a vehicle. More specifically the present disclosure is directed to evaluating and resolving conditions associated with the vehicle.
Vehicles when they are produced today include computing devices that collect data regarding the performance of various systems within a vehicle. Modern vehicles also include an on board diagnostic computer bus (OBD) that service technicians may couple devices to such that fault codes and certain operational characteristics of a vehicle may be monitored. These monitoring systems within particular vehicles are not designed to be expanded after a vehicle is manufactured. New aftermarket sensors capable of monitoring the operation of a vehicle cannot by easily added to the vehicle. For example, if a vehicle is manufactured with an oil sensor, yet without tire pressure sensors, a control system of that vehicle could monitor oil pressure, yet could not monitor tire pressure. Drivers and owners of vehicles, therefore, could benefit by being able to add sensors to their vehicle that are coupled to a diagnostic computer bus to help monitor the performance of older vehicles. Furthermore, even older vehicles may not have a computer diagnostic bus or computer that monitors vehicle operational parameters at all. Some vehicles may have been manufactured with an on board diagnostic version 2 (OBD-II) bus, other vehicles may have been manufactured with an OBDI version 1 (OBD-I) bus, and yet other vehicles may not have been manufactured with a computer diagnostic bus at all. Vehicles that include an OBD bus also include connection ports that allow service technicians monitor the operation of a vehicle or when those technicians evaluate fault codes communicated over the OBD bus. To accomplish this, a service technician must connect a piece of test equipment to the OBD bus when the vehicle is operational.
Another issue with modern vehicles is that drivers or owners of those vehicles do not have access to diagnostic information communicated over a diagnostic computer bus of their vehicle. The only way that drivers or vehicle owners can access information on a vehicle diagnostic computer bus is to bring their vehicle into a service center and have a technician monitor the operation of their vehicle. Drivers and owners of vehicles, however could benefit from an ability to monitor data transmitted over a vehicles diagnostic computer bus when that vehicle is not at a service center. Furthermore, issues that affect the performance of a vehicle can sometimes be intermittent or only occur under specific or even mysterious conditions. Because of this, even when a vehicle owner brings their vehicle to a service center, a technician at the service center may not be able to identify or verify a problem reported by the vehicle owner.
Yet another issue regarding maintaining a vehicle is that when an operating condition arises with that vehicle, a driver may not be aware of service centers capable of resolving the issue according to the terms of a warranty or according to a preferred payment criteria.
What are needed are systems that allow vehicle drivers or owners to monitor operating characteristics of their vehicle continuously. What are also needed are systems that enable older vehicles without advanced communications equipment to be easily retrofitted with systems that will communicate vehicle operating data to an intelligent platform that will interpret collected data and provide appropriate recommendations to vehicle drivers and owners. Furthermore, vehicle owners and drivers would benefit from intelligent platforms that are aware of vehicle warranty requirements, user payment preferences, and other user preferences such that vehicles can be more easily maintained.
The presently claimed invention is directed to a method, a non-transitory computer-readable storage medium, and an apparatus that may monitor operations at a vehicle and that may provide recommendations to users of the vehicle. In one embodiment the presently claimed method may include identifying a first accessory at a vehicle that senses vehicle operational data and identifying a normal operational range of that operational data. The presently claimed method may also include the steps of receiving the sensed vehicle operational data from the first accessory, identifying that the sensed vehicle operational data is out of the normal operating range, and sending a recommendation that identifies a corrective action that would result in the vehicle operating within the normal operating range.
In a second embodiment, the presently claimed may be implemented as a non-transitory computer readable storage medium, where a processor executes instructions out of the memory to implement the presently claimed method. Here again the method may include the steps of identifying a first accessory at a vehicle that senses vehicle operational data and identifying a normal operational range of that operational data. The processor may also execute instructions out of the memory to receive the sensed vehicle operational data from the first accessory, identify that the sensed vehicle operational data of the first accessory is out of the normal operating range, and send a recommendation that identifies a corrective action that would result in the vehicle operating within the normal operating range.
A third embodiment of the presently claimed invention may be an apparatus that includes an interface that receives diagnostic data transmitted via a communication bus at a vehicle, a first accessory that senses vehicle operational data, a memory, and a processor that executes instructions out of the memory. This processor may execute instructions out of the memory to identify the first accessory at a vehicle that senses the vehicle operational data and identify a normal operational range of the sensed vehicle operational data of the first accessory. The sensed vehicle operational data may be received from the first accessory after which the processor may then identify that the sensed vehicle operational data of the first accessory is out of the normal operating range. The presently claimed apparatus may also include a communication interface that provides a recommendation that identifies a corrective action that would result in the sensed vehicle operational data of the first accessory being within the normal operating range.
Methods and apparatus consistent with the present disclosure may collect and organize vehicle data. This data may be associated with one or more accessories operational at the vehicle. Each of the accessories may be a factory installed accessory, be an after market accessory added to the vehicle, or combination thereof. Computing devices may be communicatively coupled to a diagnostic or data collection system of a vehicle. These computing devices may also be communicatively coupled to servers that store operational information at a database or may communicate with websites of accessory manufactures or service providers. Program applications operational on a computing device may be downloaded from a server such that functionality of an automated vehicle assistant may be upgraded or expanded. A vehicle assistant may monitor parameters of a vehicle and identify that a vehicle needs to be serviced when current vehicle operating conditions do not correspond to required or desired operational operating conditions.
The vehicle 105 of
Computer 135 of vehicle 105 is illustrated as including a central processing unit (CPU) and a memory. While illustrated separately from DVR 110, DVI 110 may include or incorporate the functions of computer 135.
Vehicle local applications (VLA) system 140 may include computer memory 150 on which one or more software modules, program applications, and database data may be stored. This memory 150 can be built into the vehicle 105 itself, be part of a device that is plugged into the OBD-II port on the vehicle 105 or may be a wireless device, such as a smartphone, that communicates with a device plugged into the OBD-II port on the vehicle. A VLA base software module may be initiated or operated whenever power is supplied to the vehicle 105 each of a set of sub-modules may include instructions executable by processor/CPU 145 to provide functionality to a user based on monitoring data transmitted via engine bus 120. Memory 150 of the vehicle location application system 140 of
Processor 145 may execute instructions of memory 150 when accessing any of the databases 155 of the VLA system 140 or when communicating with the vehicle applications network 160. VLA system 140 may communicate with the vehicle applications network 160 via the cloud or Internet 125. In certain instances, processor 145 may communicate with vehicle computer 135 using a direct communication link or a wireless communication interface at vehicle 105. In other instances, processor 145 may be part of computer 135 of vehicle 105.
The databases 155 of vehicle local application system 140 include a local servicing database, an e-wallet database, an accessory database, a local application database, and an operating parameters database. Each of the respective databases 155 may be referred to as a specific type of VLA database.
The local servicing database of databases 155 may store information about service stations, their capabilities, rates, hours, etc., for use by the VLA servicing software module stored in memory 150 of VLA system 140. A VLA e-wallet database may store account information utilized by the VLA e-wallet software module in memory 150 for making payments. Instructions of the VLA e-Wallet Module when executed by processor 145 may allow processor 145 to provide or authorize a payment to authorized payees (payment receivers).
The VLA accessories database of databases 155 may store information about accessories connected to vehicle 105, such as heads up displays, tire pressure sensors, engine sensors, etc. The execution of instructions of the accessory platform software module 114 stored in memory 150 may allow processor 145 to access accessory data (e.g. heads up display data or sensor data). The VLA local applications database may store program applications that were selected by the user to download from the network applications database 170 of vehicle applications network 160 for use in the vehicle 105.
The operating parameters database of databases 155 may store information related to operating characteristics of the vehicle 105. This data may include safe operating ranges for any measured vehicle parameter, such as coolant temp, oil pressure, etc. the operating parameters database may also store information relating to services that may be provided when measured values fall outside of a given operating range. For example, in an instance when the coolant temperature is above a certain threshold, a cooling system failure may be identified. The data stored within the operating parameters database may have been provided by the vehicle manufacturer.
Various devices illustrated in
The computer 165 at vehicle applications network 160 may include a processor/CPU and a memory of a server or series of servers, that may be communicatively coupled to the vehicle 105 or the vehicle location application system 140 via the cloud or Internet 125. Data stored in memory 150 or in databases 155 of the vehicle location application system may be updated with information from databases 170 of the vehicle applications network 160. As such available applications, service station information, and an inventory of all applications operational at the vehicle location application system 140 may be updated periodically updated when desired.
The network servicing database of databases 170 of the vehicle applications network 160 may store an inventory of service stations available to service vehicle 105. The network servicing database at the vehicle application network 160 may store information that identifies a larger set of service providers as compared to the local servicing database of the vehicle location application system 140. Service stations stored in a local servicing database may have been filtered to only include local service stations or to store only service stations that are authorized to service vehicle 105. The vehicle access network (VAN) Database of databases 170 may store information that identifies all users of a VLA system. As mentioned above the network application database may store all program applications that are available for download to the VLA system 140 of
The mobile device(s) 175 illustrated in
Either after step 250 or when determination step 240 identifies that a payment request has not been received, program flow may move to determination step 260 that may identify whether any mobile devices are present. When a mobile device is present, the hotspot software module may be initiated at step 270. The hotspot module may then review and filter program applications available from a network applications database based upon current operating characteristics of the vehicle. For example, an application that identifies local attractions may be accessed when a vehicle is stationary, action games for when the vehicle is on a winding road may be identified, or entertainment applications may be identified when the vehicle is cruising on a highway. Next, determination step 280 may identify whether power is still active at the vehicle. If power is still present, the operation of the base module returns to step 230. When determination step 280 identifies that the power is no longer active, operation of the base module may end at step 290 of
Determination step 325 may then identify whether data from a set of data streams are available, when no program flow may move to determination step 330. Determination step 330 may identify whether an accessory can function without the data stream data. When determination step identifies that all of the required data feeds are available, program flow may move to step 335. Data relating to the accessories may be added to the accessory database may be identified in step 335 of
When determination step 330 identifies that an accessory cannot function with missing data, program flow may move to step 340 where an error message may be generated. Program flow may also move to step 340 after step 335 in instances when any anomalies relating to data stored in the database are identified and an error message may be sent. Error messages may be sent to either a user mobile device, a vehicle display, or a third device used to bridge the engine and the devices. Determination step 345 may then identify whether more accessories need to be added to the accessories database, program flow may move back to step 320 where these other accessories may be queried. When determination step 345 identifies that no additional accessories are connected that have not already been queried, program flow may return to the base module, at step 350 of
When program flow moves to determination step 430, a condition indicated by the reading outside of operating parameters may be evaluated to see if the vehicle should be serviced. Determination step 430 may identify that servicing is not required when a tire pressure reading is low. In such an instance, a notification may be sent to the driver of the vehicle that identifies the operating condition, at step 435. That notification may then be displayed on connected mobile devices, provided via an audio message to the driver, and/or be displayed on a vehicle display. After step 435, program flow may move to step 465 where program operation returns to performing functions of the base software module of Memory 150.
When determination step 430 identifies that a service is recommended or required, program flow may move from determination step 430 to step 440 that may identify whether the service is covered by a warranty. After step 440, a local service provider database may be queried to identify a provider in step 445. This service provider database may be the local servicing database of databases 155 of
The system may automatically contact a top provider of the identified providers or may identify several providers in order to make an appointment for the necessary service at step 455 of
In instances when a vehicle is traveling on a long distance trip, information stored in a local servicing database may be updated as the vehicle moves from one locality to another. This may be accomplished by the processor 145 retrieving data from the network servicing database at the vehicle applications network 160 of
When determination step 515 identifies a mobile device, the engine bus is polled by the hotspot module at step 520 for the current operating characteristics of the vehicle. The hotspot module may then identify current operating conditions, such as identifying that the vehicle is parked with the engine off, that the vehicle is driving on a winding road at 40 mph, or that the vehicle is cruising on a highway at 70 mph, etc. Next in step 525, a network application database may be accessed or queried for applications that match the operating parameters. Here again this may identify applications related to identifying local attractions finder for a stationary vehicle, identifying a flying game for driving on a winding road, or identify a movie channel that may provide video data for passengers to watch when the vehicle is cruising on the highway. Next in step 530, a list of the applications available with those optimized for the current vehicle characteristics at the top of the list may be sent to the identified user mobile device(s).
After step 535, the user mobile device(s) may be polled for an application selection after which information related to a selected application may be downloaded in step 540. Next, in step 545 the mobile device(s) may be sent a prompt that identifies the availability of the application for execution on their devices and deliver it when requested. Operation of instructions of the hotspot module may allow information or entertainment to send sent or streamed to mobile devices in the vehicle. This data may be sent to the VLA system 140 of
Table 1 includes information that may be stored in a local servicing database, such as the local servicing database of the databases 155 of
Table 1 identifies several local service entities that can perform services. Table 1 includes a first service provider ABC Ford dealership that can provide warranty repair work. Table 1 also identifies non-warranty service shops of XYZ Transmission, Main Street Auto Body, and Downtown Brake. Each of these service providers are associated with a street address.
Table 2 illustrates data that may be stored in an e-Wallet Database. Note that table 2 stores payment method information (e.g. credit card numbers) that the a user has loaded into the system along with any authorized payees. For example, the user has loaded one credit card that may be used to make payments to the ABC Ford. Services provided by ABC Ford may be paid automatically based on the information stored in table 2. As such, credit card ending in digits 1234 may be billed for any work performed on the user's vehicle automatically. While credit card information is included in table 2, payments may be made by other means, by the use of NFC payments or electronic bank transfers, etc. Note that each of the different authorized payees of table 2 may be linked to different payment methods (e.g. credit cards, debit cards, or bank accounts).
Table 3 includes information of an accessories database. The information of table 3 may identify accessories and may identify whether data collected by those accessories are required to operate a vehicle. The data of table 3 may be the data stored in the accessory database of the databases 155 of
Note that table 3 identifies that data sensed by a tachometer and data sensed by a wheel speed sensor must be sent to a heads up display at a vehicle because they are identified as being “required.” Table 3 also identifies that data relating to tire pressure, a gyroscope, a coolant temperature, an oil temperature, a boost pressure, an MAF sensor, or an exhaust sensor may optionally be provided to the heads up display. The data of table 3 also identifies that the only required data that must be provided to the race camera is from the wheel speed sensor. Data feeds associated with the efficiency helper identify data from the tachometer, the wheel speed sensor, the MAF sensor, and the Exhaust sensor must be provided to the efficiency helper. Table 3 also identifies that data collected by the gyroscope, the coolant temperature sensor, the oil temperature sensor, and the boost pressure sensor are not applicable to the efficiency helper. The efficiency helper may be associated with an external computer or a program application that monitors how efficiently a vehicle is being driven and this computer or application may provide a driver with efficiency information via a user interface at a vehicle computer.
The components shown in
Mass storage device 730, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 710. Mass storage device 730 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 720.
Portable storage device 740 operates in conjunction with a portable non-volatile storage medium, such as a FLASH memory, compact disk or Digital video disc, to input and output data and code to and from the computer system 700 of
Input devices 760 provide a portion of a user interface. Input devices 760 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 700 as shown in
Display system 770 may include a liquid crystal display (LCD), a plasma display, an organic light-emitting diode (OLED) display, an electronic ink display, a projector-based display, a holographic display, or another suitable display device. Display system 770 receives textual and graphical information, and processes the information for output to the display device. The display system 770 may include multiple-touch touchscreen input capabilities, such as capacitive touch detection, resistive touch detection, surface acoustic wave touch detection, or infrared touch detection. Such touchscreen input capabilities may or may not allow for variable pressure or force detection.
Peripherals 780 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 780 may include a modem or a router.
Network interface 795 may include any form of computer interface of a computer, whether that be a wired network or a wireless interface. As such, network interface 795 may be an Ethernet network interface, a BlueTooth™ wireless interface, an 802.11 interface, or a cellular phone interface.
The components contained in the computer system 700 of
The present invention may be implemented in an application that may be operable using a variety of devices. Non-transitory computer-readable storage media refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile and volatile media such as optical or magnetic disks and dynamic memory, respectively. Common forms of non-transitory computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, RAM, PROM, EPROM, a FLASH EPROM, and any other memory chip or cartridge.
While various flow diagrams provided and described above may show a particular order of operations performed by certain embodiments of the invention, it should be understood that such order is exemplary (e.g., alternative embodiments can perform the operations in a different order, combine certain operations, overlap certain operations, etc.).
The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.
This application claims priority benefit to U.S. provisional patent application 62/879,981, filed Jul. 29, 2019 the disclosure of which is hereby incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62879981 | Jul 2019 | US |
