SYSTEMS AND METHODS FOR PRESENTING VEHICLE STATUS INFORMATION

Systems and methods for presenting vehicle status information using a virtual vehicle in a virtual environment are disclosed. In one embodiment, a method of a method for presenting vehicle status information includes receiving vehicle data of a physical vehicle from one or more sources, wherein the vehicle data corresponds with one or more components of the physical vehicle, and causing for display a virtual vehicle within a virtual environment, wherein the virtual vehicle corresponds to the physical vehicle and an appearance of the virtual vehicle corresponds with the vehicle data of the one or more components of the physical vehicle.

TECHNICAL FIELD

The present specification relates to vehicle repairs and, more particularly, to systems and methods for presenting vehicle status information using a virtual vehicle in a virtual environment.

BACKGROUND

Vehicles, such as cars and trucks, often need to be repaired or otherwise serviced. As an example, a vehicle is moved to a maintenance bay where it is worked on by one or more technicians.

A pain-point of having a vehicle repaired for the owner of the vehicle is knowing the current status of the vehicle repair. An owner must either wait in a waiting room or wait for a phone call letting the owner know when the vehicle is completed. Vehicle repairs can be lengthy, and significant delays may occur. Owners may become antsy and agitated when there are delays and they do not know the status of their repair, or when the repair will be completed.

Accordingly, a need exists for alternative methods of presenting vehicle status information for vehicles undergoing repair.

SUMMARY

In one embodiment, a method of a method for presenting vehicle status information includes receiving vehicle data of a physical vehicle from one or more sources, wherein the vehicle data corresponds with one or more components of the physical vehicle, and causing for display a virtual vehicle within a virtual environment, wherein the virtual vehicle corresponds to the physical vehicle and an appearance of the virtual vehicle corresponds with the vehicle data of the one or more components of the physical vehicle.

In another embodiment, a system for presenting vehicle status information includes one or more processors, and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to receive vehicle data of a physical vehicle from one or more sources, wherein the vehicle data corresponds with one or more components of the physical vehicle, and cause for display a virtual vehicle within a virtual environment, wherein the virtual vehicle corresponds to the physical vehicle and an appearance of the virtual vehicle corresponds with the vehicle data of the one or more components of the physical vehicle.

DETAILED DESCRIPTION

The embodiments disclosed herein describe systems and methods for presenting vehicle status information regarding a vehicle under repair. More particularly, embodiments of the present disclosure generate a virtual vehicle that represents the physical vehicle under repair in a virtual environment that a user can view using a display device, such as, without limitation, a virtual reality headset. Data regarding the physical vehicle are used to indicate changes to components of the physical vehicle that are reflected in the virtual vehicle. In this manner, a user of the system is able to watch the progress of the repair of the vehicle. The user is able to move around the virtual vehicle, look under the hood, move under the virtual vehicle, sit in the virtual vehicle, or take other actions to watch and inspect the progress being made on the repair of the vehicle.

In some embodiments, a user may correspond with a virtual technician, which may be represented by an avatar that exists in the virtual environment. The avatar of the virtual technician may provide information regarding the vehicle repair to the user. The virtual technician may be an automated technician (i.e., a “bot”) or a representation of a real-life technician that is in a remote location. The avatar representing the virtual technician may switch between a bot and a real-life technician depending on the correspondence. For example, the avatar representing the virtual technician may start as a bot, and then transition to a real-life technician if the bot cannot answer questions presented by the user.

Various embodiments of systems and methods for presenting vehicle status information regarding a vehicle under repair are described in detail below.

Referring now toFIG.1, an example physical vehicle12in an example maintenance bay10is schematically illustrated. The physical vehicle12is in the maintenance bay10to receive repairs. In the illustrated example, the physical vehicle12is raised by a lift20that enables one or more technicians to work under the physical vehicle12, and perform tasks such as change or rotate tires. As shown inFIG.1, the physical vehicle12has its two wheels removed, thereby exposing left and right rear axle hubs14,15.

The owner of the physical vehicle12is not near the physical vehicle, and may in fact be at a remote location, such as at his or her home or work location. Therefore, the owner cannot be updated regarding the status of the repair, or to see how the repair is proceeding. As described in more detail below, sensors of the physical vehicle12, electronic control units of the physical vehicle12, cameras, data entered into a computing device by a technician, and any other data sources may provide information regarding the current state of the repair of the physical vehicle12. In the example ofFIG.1, rear tire pressure sensors (not shown) may be disconnected and not provide signals, which is indicative of the rear wheels being removed.

FIG.2illustrates an example user30experiencing a virtual vehicle12′ in a virtual environment10′. The user30utilizes a display device to experience the virtual vehicle12′ and the virtual environment10′. In the illustrated example, the display device is a virtual reality headset124. Any virtual reality headset124may be utilized. Other display devices include, but are not limited to augmented reality glasses or mobile devices operable to provide a virtual reality experience.

The virtual reality headset124renders the virtual vehicle12′ in a virtual environment10′. The virtual vehicle12′ is a virtual representation of the physical vehicle12that is being repaired. Thus, the virtual vehicle12′ may look the same as the physical vehicle12. Thus, the virtual vehicle12′ is the same make, model and year as the physical vehicle12. In other embodiments, the virtual vehicle12′ may be a generic representation of the physical vehicle12. However, a closer representation of the virtual vehicle12′ to the physical vehicle12may provide better information regarding the current status of the repair.

In the illustrated example, the virtual environment10′ includes a virtual lift20′ because the physical vehicle12is raised by the lift20. The state and condition of the virtual vehicle12′ reflects the state and condition of the physical vehicle12. Because the rear tires are removed from the physical vehicle12, the rear tires are removed from the virtual vehicle12′, thereby exposing first and second axle hubs14′,15′. As other examples, if the physical vehicle12is having its spark plugs replaced, the virtual vehicle12′ will be rendered such that the spark plugs are removed. If the physical vehicle12is having body work done, the virtual vehicle12′ will reflect the work, such as a front fender removed, or dents removed.

The user is able to move within the virtual environment10′ to view and inspect the virtual vehicle12′ from many different vantage points in a manner as if the user were in the maintenance bay walking around the physical vehicle12. In embodiments, the user may walk around the virtual vehicle12′, go under the virtual vehicle12′, fly over the virtual vehicle12′, sit in the virtual vehicle12′, among others. In this manner, the user can inspect the virtual vehicle12′ and monitor the repair process.

In some embodiments, one or more icons, texts, or other graphical elements may indicate the overall progress of the repair.FIG.2illustrates a non-limiting progress bar33as a progress icon that provides a visual indication of the progress of the repair. The progress bar33may float within the virtual environment10, or be provided in a menu area of the display (not shown). The progress bar33may be turned on or off. It should be understood that other information may also be displayed, such as text indicating what has been done and what still needs to be done.

In some embodiments, the user30has the option to communicate with a virtual technician35. The virtual technician35may be represented by an avatar, such as the avatar shown inFIG.2. In other embodiments, the virtual technician35may communicate with the user30by audio only without an avatar, or by use of a chat box. Other communication channels between the virtual technician35and the user30may be provided.

The virtual technician35can provide the user30with additional information regarding the status of the repair of the physical vehicle12, such as what still needs to be done and what has been done. The user30can ask questions of the virtual technician35. The avatar of the virtual technician35may give the user30a tour of the virtual vehicle12′ and explain what is going to be repaired and how it is going to be repaired.

The virtual technician35may be automated (i.e., a bot) or a real-life person in a remote location (e.g., a call center). In some embodiments, the virtual technician35transitions between a bot and a real-life person depending on the situation. For example, the virtual technician35may start out as a bot by providing general information about the repair, such as what will be done, how long the repair will take, and the like. For more detailed information, such as information in response to a user question, the bot may be replaced by a real-life person. The user30may or may not notice that a transition between bot and real-life person had occurred. Display and use of the virtual technician35may be optional, for example.

As stated above, the status of the physical vehicle12is reflected by the virtual vehicle12′. Thus, any changes to the physical vehicle12are represented by the virtual vehicle12′. The changes to the physical vehicle12are indicated by data from one or more sources of data. Thus, the vehicle data corresponds to components of the physical vehicle12(e.g., a door sensor corresponds with the door vehicle component). Referring now toFIG.3, various sources of data are illustrated. The physical vehicle12has many sensors16that produce data depending on current conditions.FIG.3illustrates four sensors16; however, it should be understood that many additional sensors may be provided and that four are provided for illustrative purposes. The sensors16may be any type of sensor, such as a door sensor, a trunk sensor, a hood sensor, a tire pressure sensor, a speedometer sensor, a tachometer sensor, a passenger detection sensor, a seatbelt sensor, among others. These sensors16provide signals representing data to the one or more processors of the physical vehicle12, such as a vehicle electronic control unit18. The data from the various sensors16may be read through the electronic control unit18, for example. This data may be provided wirelessly, or read through a diagnostic port19of the physical vehicle by a diagnostic device. Thus, sensor data of the physical vehicle12may be read and received by the system generating the virtual vehicle12′ such that the virtual vehicle12′ reflects the state of the physical vehicle12.

Other sources of data indicating the status of the physical vehicle12may include one or more cameras102having a field of view of the physical vehicle12. The one or more cameras102may be disposed all around the physical vehicle12such that a 360-degree view of the physical vehicle12may be captured. Cameras102underneath and inside of the physical vehicle12may also be provided. It should be understood that in other embodiments, no cameras are provided, or only one camera102is provided. As a non-limiting example, a technician may place a single camera102proximate the physical vehicle12such that the camera102has a field of view of the physical vehicle12where the work will be performed (e.g., body work to the hood would have a single camera102focused on the hood).

The data sources may also include information entered into a computing device104by one or more technicians or other personnel. For example, as tasks of the repair are completed, a technician may record the completed tasks by entering information into the computing device104. As a non-limiting example, the computing device104may display a graphical user interface displaying a list of tasks. A technician may select the tasks as they are completed to mark them done. This information can be provided to the system displaying the virtual vehicle12′ such that the status of the virtual vehicle12′ is updated and reflects the current state of the physical vehicle12. Thus, any data source may be used to ensure that the virtual vehicle12′ reflects the physical vehicle12.

Referring now toFIG.4, a flowchart110illustrating a non-limiting method of presenting vehicle status information to a user is provided. At block111, vehicle data is received by a computing device. This vehicle data may come from one or more sources, such as electronic control unit data that is gathered from physical vehicle sensors16, one or more cameras102, and data entered into a computing device104by a technician. Other sources for the vehicle data may also be utilized.

At block112, a virtual vehicle12′ that represents the physical vehicle12is rendered in a virtual environment10′. The virtual vehicle12′ and the virtual environment10′ may be viewed by a user by way of a display device, such as a virtual reality headset124. The user may explore the virtual environment10′ and the virtual vehicle12′ using virtual reality headset124and any other virtual reality hardware. For example, the user may have an avatar that navigates the virtual environment10′ to view the current status of the virtual vehicle12′ and thus her physical vehicle12.

At block113it is decided whether or not there has been a vehicle data update during the repair session. If there is, the workflow moves back to block111where the new data is received and then the virtual vehicle12′ rendering is updated at block112. If there is no update, the workflow moves to block114where it is determined whether or not service has been completed. If service has not been completed, then the process moves back to block112where the virtual vehicle12′ is continued to be rendered. If service has been completed at block114, then the process moves to block115where the process ends and the repair session is completed. At block115a summary of the work may be displayed, as well as a note indicating that the vehicle is ready to be picked up. In some embodiments, the user may continue to be able to view the virtual vehicle12′ that is rendered even after service has been completed.

Embodiments of the present disclosure may be implemented by a computing device, and may be embodied as computer-readable instructions stored on a non-transitory memory device. Referring now toFIG.5, an example system for providing a virtual environment for rendering a virtual vehicle for monitoring a status of a physical vehicle under repair as a computing device130is schematically illustrated. The example computing device130provides a system for providing a virtual environment for rendering a virtual vehicle for monitoring a status of a physical vehicle under repair, and/or a non-transitory computer usable medium having computer readable program code for providing a virtual environment for rendering a virtual vehicle for monitoring a status of a physical vehicle under repair embodied as hardware, software, and/or firmware, according to embodiments shown and described herein. While in some embodiments, the computing device130may be configured as a general purpose computer with the requisite hardware, software, and/or firmware, in some embodiments, the computing device130may be configured as a special purpose computer designed specifically for performing the functionality described herein. It should be understood that the software, hardware, and/or firmware components depicted inFIG.5may also be provided in other computing devices external to the computing device130(e.g., data storage devices, remote server computing devices, and the like).

As also illustrated inFIG.5, the computing device130(or other additional computing devices) may include a processor145, input/output hardware146, network interface hardware147, a data storage component148(which may include recorded vehicle data149A (e.g., data regarding the current state of the physical vehicle under repair), repair data149B (e.g., data relating to the repair of the vehicle being undertaken), and any other data149C for performing the functionalities described herein), and a non-transitory memory component140. The memory component140may be configured as volatile and/or nonvolatile computer readable medium and, as such, may include random access memory (including SRAM, DRAM, and/or other types of random access memory), flash memory, registers, compact discs (CD), digital versatile discs (DVD), and/or other types of storage components.

Additionally, the memory component140may be configured to store operating logic141, data collecting logic142for collecting data regarding work being performed, virtual vehicle and virtual environment logic143for generating the virtual vehicle and virtual environment, and virtual technician logic144for generating a virtual technician, as described herein (each of which may be embodied as computer readable program code, firmware, or hardware, as an example). It should be understood that the data storage component148may reside local to and/or remote from the computing device130, and may be configured to store one or more pieces of data for access by the computing device130and/or other components.

A local interface150is also included inFIG.5and may be implemented as a bus or other interface to facilitate communication among the components of the computing device130.

The processor145may include any processing component configured to receive and execute computer readable code instructions (such as from the data storage component148and/or memory component140). The input/output hardware146may include virtual reality headset, graphics display device, keyboard, mouse, printer, camera, microphone, speaker, touch-screen, and/or other device for receiving, sending, and/or presenting data. The network interface hardware147may include any wired or wireless networking hardware, such as a modem, LAN port, wireless fidelity (Wi-Fi) card, WiMax card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices. The network interface hardware147may communicate via the Internet to receive vehicle data122provided from one or more sources as well as communicate with a display device, such as virtual reality headset124to display the virtual vehicle and virtual environment.

Included in the memory component140may be the operating logic141, data collection logic142, virtual vehicle and virtual environment logic143, and virtual technician logic144. The operating logic141may include an operating system and/or other software for managing components of the computing device130. The operating logic141may also include computer readable program code for displaying the graphical user interface used by the user to view and experience a virtual environment. Similarly, the data collection logic142may reside in the memory component140and may be configured to receive and store vehicle data122from one or more sources of vehicle data. The virtual vehicle and virtual environment logic143also may reside in the memory component140and may be configured to render the virtual vehicle and virtual environment for display on a virtual reality headset124. The virtual technician logic144includes logic to generate a virtual technician and establish a communication channel between the user and the virtual technician.

The components illustrated inFIG.5are merely exemplary and are not intended to limit the scope of this disclosure. More specifically, while the components inFIG.5are illustrated as residing within the computing device130, this is a non-limiting example. In some embodiments, one or more of the components may reside external to the computing device130.

It should now be understood that embodiments of the present disclosure are directed to systems and methods for presenting vehicle status information about a vehicle that is under repair. Vehicle data regarding the vehicle under repair is received and stored. The vehicle data includes information regarding any vehicle components that are being repaired. Embodiments use the vehicle data to render a virtual vehicle that reflects the current state of the vehicle under repair. The virtual vehicle is rendered in a virtual environment that can be explored by a user. The user can see vehicle repair updates to her vehicle and therefore have an understanding regarding the current status of the repair and how much more time is needed before the repair is completed. In some embodiments, a virtual technician is displayed that can provide information regarding the vehicle and the repair. The user can ask the virtual technician questions about the repair to get additional information.