Apparatus and method for managing a vehicle and device installed on a vehicle

Abstract

The present disclosure relates to an apparatus and method for managing a vehicle and a device installed on the vehicle. An apparatus for managing a vehicle includes a vehicle failure information manager configured to manage information related to a failure of the vehicle, and a vehicle repair information provider configured to provide information related to repairing the vehicle based on an analysis of the information related to the failure of the vehicle.

Description

[0001] Related applications

[0002] This application claims the benefit of Korean Patent Application No. 10-2022-0113400, filed on September 7, 2022, the entire disclosure of which is incorporated herein by reference for all purposes. Technical Field

[0003] The following description relates to equipment and methods for managing vehicles, as well as devices installed on vehicles, and more specifically, to equipment for increasing vehicle failure modes to improve customer service. Background Technology

[0004] Vehicles are prone to various problems while driving, but these problems are not easily reproducible, making them difficult to detect. Furthermore, when a replacement part is needed during repairs, there is the issue that if the corresponding part is not available at the center, the driver must visit the center again.

[0005] It is difficult to identify the cause of component failure, and there are often situations that lead to unnecessary costs.

[0006] Although much research is underway to address these issues, the following problem remains: these problems are difficult to solve using conventional methods. Summary of the Invention

[0007] This overview is provided to introduce, in a simplified form, some concepts that will be further elaborated in the detailed description below. This overview is not intended to identify key or essential features of the claimed subject matter, nor is it intended to help determine the scope of the claimed subject matter.

[0008] In one general aspect, an apparatus for managing vehicles includes: a vehicle fault information manager configured to manage information related to vehicle faults; and a vehicle maintenance information provider configured to provide information related to vehicle maintenance based on analysis of the fault-related information.

[0009] The device may further include a fault state save button operation information manager, configured to manage information regarding the operation of the fault state save button, which is configured to store the fault state of the vehicle.

[0010] When the fault status save button operation manager confirms the operation of the vehicle's fault status save button, the vehicle fault information manager can be further configured to receive information related to the vehicle's faults from the vehicle.

[0011] The vehicle maintenance information provider can be further configured to send vehicle maintenance-related information derived from big data analysis of information related to vehicle malfunctions to the vehicle or user terminal.

[0012] The vehicle maintenance information provider can be further configured to provide vehicle maintenance-related information based on the fault level.

[0013] In another general aspect, the device installed on the vehicle includes: a vehicle fault information transmitter configured to transmit information related to vehicle faults to a device for managing the vehicle; and a vehicle maintenance information receiver configured to receive vehicle maintenance-related information from the device for managing the vehicle based on analysis of the information related to vehicle faults.

[0014] The device may further include a fault state save button, configured to store the fault state of the vehicle.

[0015] When the fault status save button is pressed, the vehicle fault information transmitter can be further configured to send information related to the vehicle's fault to the device used to manage the vehicle.

[0016] The vehicle maintenance information receiver can be further configured to receive vehicle maintenance-related information derived from big data analysis using information related to vehicle malfunctions.

[0017] The vehicle maintenance information receiver can be further configured to receive vehicle maintenance-related information based on the fault level.

[0018] In another general aspect, a method for managing vehicles includes: managing information related to vehicle malfunctions; and providing information related to vehicle maintenance based on the analysis of the information related to vehicle malfunctions.

[0019] The method may further include managing information regarding the operation of a fault state save button, which is configured to store the fault state of the vehicle.

[0020] Managing information about the operation of the fault state save button may include confirming the operation of the vehicle's fault state save button, and managing information related to vehicle faults may include receiving information related to vehicle faults from the vehicle when the operation of the vehicle's fault state save button is confirmed.

[0021] Providing vehicle maintenance-related information may include sending vehicle maintenance-related information derived from big data analytics using vehicle malfunction-related information to the vehicle or user terminal.

[0022] Providing vehicle maintenance-related information may include providing vehicle maintenance-related information based on the fault level.

[0023] A non-volatile computer-readable storage medium storing instructions that, when executed by one or more processors, configure the one or more processors to perform the method according to any of the disclosed methods.

[0024] Other features and aspects will become apparent from the following detailed description, drawings and claims. Attached Figure Description

[0025] Figure 1 This is a block diagram of a device for managing vehicles according to an embodiment;

[0026] Figure 2 This is a flowchart of a method for managing vehicles according to an embodiment;

[0027] Figure 3 This is a flowchart of a method for managing vehicles according to an embodiment;

[0028] Figure 4 This is a flowchart of a method for remote diagnostics of a vehicle management system according to an embodiment; and

[0029] Figure 5 This is a block diagram of a device installed on a vehicle according to an embodiment.

[0030] Throughout the accompanying drawings and detailed description, the same reference numerals denote the same or similar elements. The drawings may not be to scale, and for clarity, illustration, and convenience, the relative dimensions, scale, and descriptions of the elements in the drawings may be enlarged. Detailed Implementation

[0031] The following detailed description is provided to assist the reader in gaining a comprehensive understanding of the methods, apparatus, and / or systems disclosed herein. However, various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will be apparent upon understanding the disclosure of this application. For example, the sequences of operations described herein are merely illustrative and are not limited to those set forth herein, but may be changed as will become apparent upon understanding the disclosure of this application, except for operations that must occur in a specific order. Furthermore, for the sake of clarity and conciseness, descriptions of features known upon understanding the disclosure of this application may be omitted.

[0032] The features described herein may be embodied in different forms and should not be construed as limited to the examples described herein. Rather, the examples described herein are provided merely to illustrate some of the many possible ways in which the methods, apparatus, and / or systems described herein will become apparent upon understanding the disclosure of this application.

[0033] Throughout the specification, when an element such as a layer, region, or substrate is described as being “on,” “connected to,” or “coupled to” another element, it may be directly “on,” “connected to,” or “coupled to” another element, or one or more other elements may be present in between. Conversely, when an element is described as being “directly on,” “directly connected to,” or “directly coupled to” another element, no other elements may be present in between.

[0034] As used herein, the term “and / or” includes any one or more of the associated listed items and any combination of any two or more.

[0035] Although terms such as “first,” “second,” and “third” may be used herein to describe various components, parts, regions, layers, or sections, these components, parts, regions, layers, or sections are not limited by these terms. Rather, these terms are used only to distinguish one component, part, region, layer, or section from another. Therefore, without departing from the teachings of the examples described herein, the first component, first part, first region, first layer, or first section mentioned in the examples may also be referred to as a second component, second part, second region, second layer, or second section.

[0036] For ease of description, spatial relative terms such as “above,” “upper,” “lower,” and “below” are used herein to describe the relationship between one element and another as shown in the figures. These spatial relative terms are intended to encompass different orientations of the apparatus in use or operation, other than those depicted in the figures. For example, if the apparatus in the figures is flipped, an element described as “above” or “upper” relative to another element would be “below” or “lower” relative to that element. Therefore, the term “above” encompasses both upper and lower orientations, depending on the spatial orientation of the apparatus. The apparatus may also be oriented in other ways (e.g., rotated 90 degrees or otherwise), and the spatial relative terms used herein should be interpreted accordingly.

[0037] The terminology used herein is for the purpose of describing various examples only and is not intended to limit this disclosure. The articles “a,” “an,” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. The terms “comprising,” “including,” and “having” specify the presence of the stated feature, number, operation, component, element, and / or combination thereof, but do not preclude the presence or addition of one or more other features, numbers, operations, components, elements, and / or combinations thereof.

[0038] Due to manufacturing techniques and / or tolerances, variations in the shapes shown in the accompanying drawings may occur. Therefore, the examples described herein are not limited to the specific shapes shown in the accompanying drawings, but include shape variations that occur during manufacturing.

[0039] The features of the examples described herein can be combined in various ways, as will become apparent upon understanding the disclosure of this application. Furthermore, although the examples described herein have multiple configurations, other configurations are possible, as will become apparent upon understanding the disclosure of this application.

[0040] Figure 1 This is a block diagram of a device for managing vehicles according to an embodiment.

[0041] According to an embodiment, the device for managing a vehicle may include a fault status save button operation information management unit 110, a vehicle fault information management unit (vehicle fault information manager) 120, and a vehicle maintenance information providing unit (vehicle maintenance information provider) 130.

[0042] The device for managing a vehicle, or the components thereof, may include at least some of a memory, a processor, a data transceiver, etc. The device for managing a vehicle, or the components thereof, may include at least some of a computing device, a database, a communication device, etc.

[0043] The various information used by the device for managing a vehicle, or the apparatus installed on a vehicle, as described below, may include at least some of all information or data that can be obtained from the vehicle. The various information used by the device for managing a vehicle, or the apparatus installed on a vehicle, as described below, may include at least some of all results, information, or data analyzed based on at least some of all information or data that can be obtained from or transmitted to another device via communication.

[0044] According to an embodiment, the fault status save button operation information management unit 110 can manage information about the operation of the fault status save button, which is configured to store the fault status of vehicle 101.

[0045] The vehicle fault information management unit 120 can manage information related to faults of vehicle 101.

[0046] The vehicle maintenance information providing unit 130 can provide vehicle maintenance-related information based on the analysis of information related to the faults of the vehicle 101.

[0047] According to an embodiment, in a device for managing vehicles, when the fault status save button operation information management unit 110 confirms the operation of the fault status save button of vehicle 101, the vehicle fault information management unit 120 can receive information related to the fault of vehicle 101 from vehicle 101.

[0048] According to an embodiment, the vehicle maintenance information providing unit 130 can send vehicle maintenance-related information derived from big data analysis of information related to vehicle 101's malfunctions to the vehicle 101 or a user terminal. The user terminal may include a portable device used by the user, driver, or passenger of the vehicle 101. The user terminal may include a smartphone, tablet PC, etc.

[0049] According to an embodiment, the vehicle maintenance information providing unit 130 can provide vehicle maintenance-related information based on the fault level. The vehicle maintenance information providing unit 130 can send vehicle maintenance-related information to the vehicle 101 or a user terminal based on the fault level.

[0050] Equipment used for vehicle management can effectively handle malfunctions that occur in vehicles, develop vehicles by generating or providing fault state storage patterns that make it easy to analyze big data, and increase convenience for customers as users.

[0051] Vehicle management equipment can increase user or customer satisfaction. It can easily identify fault modes, even without the user visiting a customer service center for clarification. Furthermore, it can examine faults by reproducing stored vehicle status data.

[0052] The equipment used to manage vehicles can send information about relevant failure modes in advance to devices set up in finished vehicles, customer service centers, etc., thereby ensuring components in advance and providing measurement or service so that simple faults can be self-repaired.

[0053] Equipment used to manage vehicles can confirm the same quality and cost. This equipment can also provide guidance to mechanics using big data and other technologies for similar faults, thereby delivering better repair quality and reducing costs.

[0054] The equipment used for vehicle management can ensure the reliability of business-to-business (B2B) vehicle malfunctions. The advantages of this vehicle management equipment include easy reporting of malfunctions by B2B vehicle users due to its convenience and consistency, further ensuring quality, and the ability to proactively diagnose malfunctions using over-the-air (OTA) services through fault pattern big data analysis.

[0055] Because the equipment used to manage vehicles is advantageous in collecting big data, and therefore it is easy to collect big data on vehicle malfunction status, it is very easy to pinpoint the time point when a specific malfunction occurs, and the problem in that specific malfunction also occurs in other services.

[0056] The device for managing vehicles can easily identify the time when a vehicle malfunction occurred using the vehicle's fault status save button, and also confirm the vehicle's status at that time, thus providing convenience for the user.

[0057] Equipment used for vehicle management can provide robust design guidelines for the future through big data analytics.

[0058] Figure 2 This is a flowchart of a method for managing vehicles according to an embodiment.

[0059] According to an embodiment, each operation of the method for managing a vehicle may be performed by at least some components of the device for managing a vehicle described above.

[0060] In step 201, the device for managing the vehicle can manage information about the operation of the fault state save button, which is configured to store the fault state of the vehicle.

[0061] In step 202, the device used to manage the vehicle can manage information related to vehicle malfunctions.

[0062] According to an embodiment, the device for managing the vehicle can confirm the operation of the vehicle's fault state save button, and when the operation of the vehicle's fault state save button is confirmed, it receives information related to the vehicle's fault from the vehicle or a device installed on the vehicle.

[0063] When the vehicle's fault status save button is activated, the vehicle or a device installed on the vehicle can store the status of the fault mode or information or data related to the fault mode, and additionally store certain specific values ​​besides the real-time stored status. The vehicle or the device installed on the vehicle can send at least some of the stored status, information, data, etc., to a device used for managing the vehicle.

[0064] Data stored in the vehicle or on-vehicle devices can include data based on on-board diagnostics (OBD) (e.g., engine / tire pressure, etc.). When operating in fault state storage mode, all information inside and outside the vehicle, along with OBD data, can be stored in real time. Information from sensors, cameras, or LiDAR in the vehicle can be stored continuously, and a microphone installed in the vehicle can be operated to store sounds from inside or outside the vehicle. At this time, the user can also describe and store the problem through the microphone. For example, a problem stored by the user could include "Problem A is currently occurring and occurs frequently in situation B," etc. (e.g., A and B can include different situations).

[0065] When selecting to store fault modes for the vehicle or a device installed in the vehicle, the storage time for the fault mode during normal operation can be set to a default value of approximately 10 minutes (e.g., the storage time or default value can be changed by the user). Even when the ignition is off, the fault mode can be stored for approximately 10 minutes. After 10 minutes, a notification or alert can be provided to the user via a user terminal or a device installed in the vehicle (e.g., terminating the storage of the fault mode without clicking or touching after confirming whether to continue storing the fault mode). Various storage scenarios can be configured when approximately 3 to 4 hours of storage space is available.

[0066] When selecting to store fault modes of a vehicle or a device installed on the vehicle, the information, data, or factors (inputs) stored may include all data (e.g., coolant temperature, engine / battery pressure, accelerator operating time, etc., which may be collected from the OBD (2)), sound recorded after operation of a microphone inside or outside the vehicle (with customer consent), information or data obtained from vehicle sensors (e.g., RADAR, LIDAR, ultrasonic sensor, or camera data), information or data collected from CAN / LIN communication (e.g., values ​​for communication with the electronic control unit, and component diagnostic data), information for navigation and audio, video, and navigation (AVN) (e.g., vehicle position, or information processed by AVN, etc.), information or data obtained from an inertial measurement unit (IMU), etc.

[0067] Vehicles or devices installed on vehicles may include storage media such as memory or storage units. Storage media may include data storage modules or data storage modules (such as onboard hard drives or SD cards). In the case of onboard hard drives or SD cards, the storage media is located in the cockpit and can be easily attached / removed by a mechanic or user. The storage media can be configured to be physically attachable / removable for rapid transfer of large amounts of data.

[0068] Information or data stored in the vehicle and devices installed on the vehicle may include numerical or code values, and includes encrypted data values ​​of at least some of the information described above in the specification.

[0069] In step 203, the equipment used to manage the vehicle can provide information related to vehicle maintenance based on the analysis of information related to vehicle malfunctions.

[0070] According to an embodiment, the device for managing vehicles can send vehicle maintenance-related information derived from big data analysis of information related to vehicle malfunctions to the vehicle or user terminal.

[0071] According to an embodiment, the equipment for managing vehicles can provide information related to vehicle maintenance based on the fault level.

[0072] Figure 3 This is a flowchart of a method for managing vehicles according to an embodiment.

[0073] In step 301, the device for managing the vehicle may also receive information about detecting vehicle anomalies from a device installed on the vehicle. The device installed on the vehicle can detect vehicle anomalies and send relevant information to the device for managing the vehicle. The device installed on the vehicle may use at least some components of the vehicle (e.g., output devices such as speakers or displays) to notify the vehicle user or user terminal of a malfunction.

[0074] In step 302, the device for managing the vehicle can receive at least some of all vehicle information. When a vehicle malfunctions, and the user identifies the malfunction (e.g., noise, vibration, abnormal operation, etc.), the device installed in the vehicle can store all vehicle information and press a button to change the current mode to a fault state storage mode (when the fault state save button is pressed), and send at least some of the vehicle information to the device for managing the vehicle. All vehicle information may include information about engine temperature, speed, AVN status, internal and external sounds recorded via the vehicle microphone, currently playing songs, operating components, etc. When vehicle operation is terminated or the user terminates the fault state storage mode, the device installed in the vehicle can primarily store and save relevant information or data.

[0075] In step 303, when a user visits the customer service center, the device for managing the vehicle can use the vehicle's or user terminal's location information, etc., to send at least some of the fault-related information from all vehicle information to a device located in the customer service center, etc. The device located in the customer service center, etc., may include at least some of a computing device and a communication device.

[0076] Users can wirelessly transmit information about stored faults to a device located at a point where the vehicle can be repaired using a device installed on the vehicle. Alternatively, users can directly access a customer service center or notify the relevant fault status via a user terminal, etc. Therefore, remote diagnostics is possible, and components can be provided in advance. The device located at a point where the vehicle can be repaired may include at least some of a computing device or a communication device.

[0077] In step 304, the device for managing the vehicle may receive vehicle maintenance-related information from devices arranged in customer service centers, devices located at the location of vehicles that can be repaired, user terminals, devices installed on the vehicle, etc.

[0078] In the customer service center, vehicles can be repaired based on corresponding fault modes. Repair information or vehicle repair-related information can be transmitted from the customer service center to the finished vehicle or to devices installed on the vehicle via devices located in the customer service center, etc. The equipment used to manage the vehicles or devices located in the customer service center, etc., may use or include databases or management agents, such as Oracle Enterprise Management Unit / Oracle Enterprise Manager (OEM).

[0079] In step 305 or 306, the device for managing the vehicle may perform big data analysis or data analysis of the vehicle's fault modes. The device for managing the vehicle may collect or receive data related to the vehicle's fault modes from devices located in customer service centers or installed on the vehicle, and analyze the received data.

[0080] The equipment used for vehicle management can notify or send best-practice maintenance methods derived from big data analytics to devices deployed in customer service centers, user terminals, etc. The equipment can also share information on parts purchasing services and repair methods for simple faults (parts replacement) with users through user terminals, etc.

[0081] In step 307, the device used to manage the vehicle can send relevant data or analysis results to the server of the design-related organization, etc., for the use of big data analysis results for the robust design of the vehicle.

[0082] In step 308, the device for managing the vehicle can notify the vehicle or a device installed on the vehicle of a malfunction or a malfunction that can be anticipated. The device for managing the vehicle can send information about malfunction predictions to the vehicle or the device installed on the vehicle. Advantageously, the device for managing the vehicle can use big data analytics to inform the user of better driving habits.

[0083] In step 311, when a user requests remote diagnostics via a user terminal, a device installed in the vehicle, or similar means, the equipment used to manage the vehicle can perform a preliminary diagnostic using the system of the remote support center. At this time, data related to the vehicle's fault status can first be sent to devices located in customer service centers, etc.

[0084] In step 312, the device used to manage the vehicle can analyze data and determine whether access to the customer service center is necessary. The device can also determine whether self-repair is feasible. The device can send a notification to the device installed in the vehicle, the user terminal, etc., indicating whether access to the center is necessary or whether self-repair is possible.

[0085] In step 313, when it is determined that the vehicle needs to access the customer service center, the device used to manage the vehicle can send reservation-related information or reservation request information to the device installed on the vehicle or the user terminal by interacting with the pre-reservation system.

[0086] In step 314, when it is determined that self-repair of the vehicle (such as simple replacement of vehicle parts) is possible for the user, the device for managing the vehicle may send the repair method to a device installed in the vehicle, a user terminal, etc. The device for managing the vehicle may provide information related to the repair method via a device installed in the vehicle or a user terminal using video (such as YouTube) or a component purchase service.

[0087] In step 315, when it is determined that wireless maintenance of the vehicle is feasible, the device used to manage the vehicle can provide updates to the device installed on the vehicle or the corresponding vehicle via wireless communication (such as OTA).

[0088] Figure 4 This is a flowchart of a method for remote diagnostics of a vehicle management system according to an embodiment.

[0089] In step 401, the device for managing the vehicle may use a database (e.g., an OEM or weight database, etc.) to manage at least some of the vehicle's information.

[0090] In step 402, the device for managing the vehicle can receive data on vehicle fault diagnosis from the vehicle in question or a device installed on the vehicle in question.

[0091] In step 403, the equipment used to manage the vehicle may use a fault diagnosis module or the like to perform data analysis on the vehicle's faults or information.

[0092] In step 404, step 407, or step 409, the equipment used to manage the vehicle can determine or identify the vehicle's fault level based on the data analysis results.

[0093] According to an embodiment, the fault level may include critical, major, minor, etc.

[0094] According to an embodiment, the fault level can be from level 1 to level N (N is a natural number greater than or equal to 2). The higher the level, the greater the severity of the fault, and the lower the level, the less severe the fault. In another example, the opposite is also possible.

[0095] In step 404, the equipment used to manage the vehicle can determine / determine the fault level as critical.

[0096] In step 405, the equipment used to manage the vehicle can provide an alarm service that strongly recommends vehicle repair when a fault level is determined or deemed critical, via a device installed in the vehicle or a user terminal. The equipment used to manage the vehicle can also provide appointment services to customers via the device installed in the vehicle or a user terminal.

[0097] In step 406, the device for managing the vehicle can restrict the operation of the vehicle as needed. For example, when the vehicle's battery temperature is uncontrollable, the device for managing the vehicle can provide services to restrict the operation of the vehicle through the vehicle or a device installed on the vehicle.

[0098] In step 407, the equipment used to manage the vehicle can determine or decide that the fault level is primary.

[0099] In step 408, when the fault level is determined or deemed major, the vehicle management equipment can provide an alert service to recommend vehicle maintenance. The vehicle management equipment can provide vehicle maintenance-related services through devices installed on the vehicle, user terminals, etc. The vehicle management equipment can also provide appointment services to customers through devices installed on the vehicle or user terminals.

[0100] In step 409, the equipment used to manage the vehicle can determine or decide that the fault level is minor.

[0101] In step 410, when the fault level is determined or decided to be minor and self-repair is determined or decided to be feasible, the equipment for managing the vehicle can provide services related to the self-repair method through devices installed on the vehicle, user terminals, etc. The equipment for managing the vehicle can send the self-repair method, etc., to devices installed on the vehicle, user terminals, etc.

[0102] In step 411, when the fault level is determined or deemed minor and identified as an error such as a communication signal malfunction, the vehicle management device can delete information related to the fault mode, such as the deletion of the fault mode determined by the OEM. The vehicle management device can provide error-related services through devices installed in the vehicle, user terminals, etc. The vehicle management device can send error resolution methods, etc., to devices installed in the vehicle, user terminals, etc.

[0103] In step 412, the device for managing the vehicle may perform OTA diagnostics when the vehicle completes self-healing (or when troubleshooting) and provide customer notifications to the user via devices installed on the vehicle, user terminals, etc. The device for managing the vehicle may provide diagnostics of peripheral or additional problems of the vehicle via devices installed on the vehicle, user terminals, etc.

[0104] Figure 5 This is a block diagram of a device installed on a vehicle according to an embodiment.

[0105] According to an embodiment, the device 500 installed on the vehicle may include a fault status save button 501, a vehicle fault information sending unit (vehicle fault information transmitter) 502, and a vehicle maintenance information receiving unit (vehicle maintenance information receiver) 503.

[0106] The device 500 installed on the vehicle or the components of the device 500 installed on the vehicle may include at least some of the following: vehicle, controller installed on the vehicle, memory, processor, data transmitter or receiver, button, display, touch screen, etc.

[0107] A device mounted on a vehicle can provide a method for operating the device, the method being performed by at least some components of the device mounted on the vehicle. The method for operating the device mounted on the vehicle may include at least some of the operations of the device mounted on the vehicle as described in the specification. Each operation of the method for operating the device mounted on the vehicle may include at least some of the operations of the device mounted on the vehicle as described in the specification. Furthermore, a user terminal can perform at least some of all the operations of the device mounted on the vehicle.

[0108] The fault status save button 501 may include a button mounted on at least a portion of the vehicle to store the vehicle's fault status. The button may be mechanical or electronic and may include a button displayed on the vehicle's display.

[0109] The button can be configured to allow users, as customers, to store fault modes in the vehicle's cockpit or similar location. The button can be located on the AVN (Automatic Vehicle Name) in ordinary vehicles, shared vehicles (e.g., purpose-built vehicles (PBVs)), etc. The button can be attached to or arranged on the vehicle at a location desired by the user.

[0110] The vehicle fault information sending unit 502 can send information related to vehicle faults to the equipment used for vehicle management.

[0111] The vehicle maintenance information receiving unit 503 can receive vehicle maintenance-related information from equipment used for vehicle management, based on the analysis of information related to vehicle malfunctions.

[0112] According to an embodiment, when the fault status save button 501 is operated, the vehicle fault information sending unit 502 can send information related to the vehicle fault to the device used to manage the vehicle.

[0113] According to an embodiment, the vehicle maintenance information receiving unit 503 can receive vehicle maintenance-related information derived from big data analysis using information related to vehicle malfunctions.

[0114] According to an embodiment, the vehicle maintenance information receiving unit 503 can receive vehicle maintenance-related information based on the fault level.

[0115] In this embodiment, the term "unit" refers to a software or hardware component such as a Field-Programmable Gate Array (FPGA) or Application-Specific Integrated Circuit (ASIC), and a "unit" performs certain functions. However, a "unit" is not limited to software or hardware. A "unit" may also be configured to reside on an addressable memory medium or may also be configured to reproduce one or more processors. Thus, as an example, a "unit" includes components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "units" can be coupled through a small number of components and "units," or further decoupled through additional components and "units." Furthermore, components and "units" may also be implemented as one or more CPUs in a playback device or a secure multimedia card.

[0116] Perform the operations described in this application Figures 1 to 5The fault status save button operation information management unit 110, vehicle fault information management unit 120, and vehicle maintenance information providing unit 130, device 500, fault status save button 501, vehicle fault information sending unit 502, and vehicle maintenance information receiving unit 503 are implemented by hardware components configured to perform the operations performed by hardware components as described in this application. Where appropriate, examples of hardware components that can be used to perform the operations described in this application include controllers, sensors, generators, drivers, memories, comparators, arithmetic logic units, adders, subtractors, multipliers, dividers, integrators, and any other electronic components configured to perform the operations described in this application. In other examples, one or more of the hardware components performing the operations described in this application are implemented by computing hardware (e.g., by one or more processors or computers). A processor or computer may be implemented by one or more processing elements, such as logic gate arrays, controllers and arithmetic logic units, digital signal processors, microcomputers, programmable logic controllers, field-programmable gate arrays, programmable logic arrays, microprocessors, or any other means or combination of means configured to respond to and execute instructions in a defined manner to achieve desired results. In one example, the processor or computer includes or is connected to one or more memories storing instructions or software executed by the processor or computer. Hardware components implemented by a processor or computer may execute instructions or software such as an operating system (OS) and one or more software applications running on the operating system to perform the operations described in this application. Hardware components may also access, manipulate, process, create, and store data in response to the execution of instructions or software. For simplicity, the singular terms “processor” or “computer” may be used in the description of the examples described in this application; however, in other examples, multiple processors or computers may be used, or a processor or computer may include multiple processing elements, or multiple types of processing elements, or both. For example, a single hardware component or two or more hardware components may be implemented by a single processor, or two or more processors, or a processor and a controller. One or more hardware components may be implemented by one or more processors, or processors and controllers, and one or more other hardware components may be implemented by one or more other processors, or another processor and another controller. One or more processors or processors and controllers may implement a single hardware component or two or more hardware components. Hardware components may have any one or more different processing configurations, examples of which include a single processor, a standalone processor, a parallel processor, Single Instruction Single Data (SISD) multiple processing, Single Instruction Multiple Data (SIMD) multiple processing, Multiple Instruction Single Data (MISD) multiple processing, and Multiple Instruction Multiple Data (MIMD) multiple processing.

[0117] Figures 1 to 5The methods for performing the operations described in this application, as shown, are executed by computing hardware (e.g., one or more processors or a computer implemented as described above), which executes instructions or software to perform the operations performed by the methods described in this application. For example, a single operation or two or more operations may be performed by a single processor, or two or more processors, or a processor and a controller. One or more operations may be performed by one or more processors, or a processor and a controller, and one or more other operations may be performed by one or more other processors, or another processor and another controller. One or more processors or a processor and a controller may perform a single operation or two or more operations.

[0118] Instructions or software that control computing hardware (e.g., one or more processors or computers) to implement hardware components and perform the methods described above can be written as computer programs, code segments, instructions, or any combination thereof to individually or collectively instruct or configure one or more processors or computers to operate as a machine or special-purpose computer to perform operations performed by the hardware components and methods described above. In one example, the instructions or software include machine code that is directly executed by one or more processors or computers, such as machine code generated by a compiler. In another example, the instructions or software include high-level code that is executed by one or more processors or computers using an interpreter. The instructions or software can be written using any programming language based on the block diagrams and flowcharts shown in the accompanying drawings and the corresponding descriptions in the specification, which disclose algorithms for performing operations performed by the hardware components and methods described above.

[0119] Instructions or software for controlling computing hardware (e.g., one or more processors or computers) to implement hardware components and perform the methods described above, and any associated data, data files, and data structures, may be recorded, stored, or fixed in or on one or more non-volatile computer-readable storage media. Examples of non-volatile computer-readable storage media include read-only memory (ROM), random access memory (RAM), flash memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid-state disk, and any other means configured to store instructions or software and any associated data, data files, and data structures in a non-volatile manner and provide instructions or software and any associated data, data files, and data structures to one or more processors or computers, such that one or more processors or computers can execute instructions. In one example, instructions or software, along with any associated data, data files, and data structures, are distributed across a network-coupled computer system, such that the instructions or software, along with any associated data, data files, and data structures, are stored, accessed, and executed in a distributed manner by one or more processors or computers.

[0120] While this disclosure includes specific examples, it will be apparent upon understanding this disclosure that various changes in form and detail may be made in these examples without departing from the spirit and scope of the claims and their equivalents. The examples described herein are to be considered descriptive in nature only and not for limiting purposes. The description of features or aspects in each example is to be applied to similar features or aspects in other examples. Suitable results may be achieved if the described techniques are performed in a different order, and / or if components in the described system, architecture, device, or circuit are combined in a different manner and / or if components in the described system, architecture, device, or circuit are replaced or supplemented by other components or their equivalents. Therefore, the scope of this disclosure is not limited by the detailed description but by the claims and their equivalents, and all variations within the scope of the claims and their equivalents should be construed as included in this disclosure.

Claims

1. A device for managing vehicles, the device comprising: A fault status save button is located inside the vehicle. One or more processors are configured as follows: Detect the operation of the fault status save button; The vehicle's fault information is stored in response to the detected operation; as well as The stored fault information is sent to the vehicle maintenance information provider. Wherein, the one or more processors are further configured to: In response to the detected operation of the fault state save button, enter the fault state storage mode; Set the storage time of the fault state storage mode to a predetermined storage time; When the fault state storage mode is operated, at least one of the following is stored in real time: on-board diagnostic OBD data, information or data obtained from vehicle sensors, cameras or LIDAR, information or data collected from CAN / LIN communication, and sound recorded by a microphone installed in the vehicle. The predetermined storage time continues to be stored after the operation of the fault state save button is detected, including even when the vehicle's ignition is turned off; and The vehicle maintenance information provider is configured to analyze at least some of the transmitted and stored fault information to generate vehicle-specific maintenance information, and to provide the generated maintenance information to the vehicle or user terminal.

2. The device according to claim 1, wherein, The vehicle maintenance information provider is further configured to provide information related to the maintenance of the vehicle based on the fault level.

3. A device installed on a vehicle, the device comprising: A fault status save button is located inside the vehicle. One or more processors are configured as follows: Detect the operation of the fault status save button; The vehicle's fault information is stored in response to the detected operation; as well as The stored fault information is sent to the vehicle fault information transmitter, which is configured to send information related to the fault of the vehicle to the device used to manage the vehicle; as well as A vehicle maintenance information receiver is configured to receive vehicle maintenance-related information from the device for managing the vehicle, based on analysis of information related to the vehicle's fault. Wherein, the one or more processors are further configured to: In response to the detected operation of the fault state save button, enter the fault state storage mode; Set the storage time of the fault state storage mode to a predetermined storage time; When the fault state storage mode is operated, at least one of the following is stored in real time: on-board diagnostic OBD data, information or data obtained from vehicle sensors, cameras or LIDAR, information or data collected from CAN / LIN communication, and sound recorded by a microphone installed in the vehicle. The predetermined storage time continues to be stored after the operation of the fault state save button is detected, including even when the vehicle's ignition is turned off; and The vehicle maintenance information provider is configured to analyze at least some of the transmitted and stored fault information to generate vehicle-specific maintenance information, and to provide the generated maintenance information to the vehicle or user terminal.

4. The apparatus according to claim 3, wherein, The vehicle maintenance information receiver is further configured to receive maintenance-related information for the vehicle based on the fault level.

5. A method for managing vehicles, the method comprising: The operation of the fault status save button located inside the vehicle is checked; In response to the detected operation of the fault status save button, the fault information of the vehicle is stored; as well as Based on the analysis of the stored fault information, maintenance information is provided for the vehicle. The method further includes, in response to the detected operation of the fault state save button: Enter fault state storage mode; Set the storage time of the fault state storage mode to a predetermined storage time; When the fault state storage mode is operated, at least one of the following is stored in real time: on-board diagnostic OBD data, information or data obtained from vehicle sensors, cameras, or LIDAR, information or data collected from CAN / LIN communication, and sound recorded by a microphone installed in the vehicle. After the fault state save button is pressed, the predetermined storage time continues to be stored, including even when the vehicle's ignition is turned off; and At least some of the stored fault information is sent to the vehicle maintenance information providing unit, which analyzes the sent fault information to generate the maintenance information and provides the maintenance information to the vehicle or user terminal.

6. The method according to claim 5, wherein, Providing the information related to the maintenance of the vehicle includes providing the information related to the maintenance of the vehicle according to the fault level.

7. A non-volatile computer-readable storage medium storing instructions that, when executed by one or more processors, configure the one or more processors to perform the method according to claim 5.

Images