Vehicle computer fault monitoring method, device, electronic device and readable storage medium

Abstract

The present application provides a vehicle computer fault monitoring method, device, electronic device and readable storage medium. The method includes: obtaining the heartbeat data periodically reported by the vehicle cabin system of the current vehicle; in response to not receiving new heartbeat data within a set first time period, generating a data request instruction for requesting vehicle driving data, the data request instruction including the vehicle identification code of the current vehicle and the first generation time of the last heartbeat data; querying the vehicle driving data with a generation time later than the first generation time in the preset data warehouse according to the vehicle identification code to obtain a vehicle driving data set; if the vehicle driving data set is not empty, and the vehicle driving data in the vehicle driving data set increases over time, it is determined that the vehicle cabin system of the current vehicle has a vehicle computer fault. The technical solution of the present application can be used to promptly and proactively discover vehicle computer faults for after-sales maintenance.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a vehicle computer fault monitoring method, device, electronic device, and readable storage medium. Background Art

[0002] As cars become increasingly intelligent and software-based, the large screens in vehicle cockpits are carrying more and more functions, and problems like black screens and system freezes are becoming increasingly common. However, car manufacturers typically only discover computer malfunctions after receiving reports from vehicle users, resulting in delayed after-sales service.

[0003] How to proactively detect vehicle computer failures and provide timely after-sales repairs and services is a technical problem that urgently needs to be solved. Summary of the Invention

[0004] In view of this, embodiments of the present application provide a vehicle computer fault monitoring method, device, electronic device, and computer-readable storage medium to solve the problem of not being able to proactively detect vehicle computer faults in a timely manner.

[0005] In a first aspect of an embodiment of the present application, a vehicle-computer fault monitoring method is provided, the method comprising: obtaining heartbeat data periodically reported by a vehicle cabin system of a current vehicle; in response to not receiving new heartbeat data within a set first time period, generating a data request instruction for requesting vehicle driving data, the data request instruction including a vehicle identification code of the current vehicle and a first generation time of the last heartbeat data; querying a preset data warehouse for vehicle driving data whose generation time is later than the first generation time according to the vehicle identification code to obtain a vehicle driving data set, wherein the data warehouse stores vehicle driving data uploaded in real time by the vehicle cabin system and data acquisition equipment of the current vehicle; if the vehicle driving data set is not empty, and the vehicle driving data in the vehicle driving data set increases over time, it is determined that a vehicle-computer fault has occurred in the vehicle cabin system of the current vehicle.

[0006] According to a second aspect of an embodiment of the present application, a vehicle-machine fault monitoring device is provided, which includes: an acquisition module for acquiring heartbeat data periodically reported by a vehicle cabin system of a current vehicle; a generation module for generating a data request instruction for requesting vehicle driving data in response to not receiving new heartbeat data within a set first time period, the data request instruction including a vehicle identification code of the current vehicle and a first generation time of the last heartbeat data; a query module for querying a preset data warehouse for vehicle driving data whose generation time is later than the first generation time according to the vehicle identification code to obtain a vehicle driving data set, wherein the data warehouse stores vehicle driving data uploaded in real time by the vehicle cabin system and data acquisition equipment of the current vehicle; a determination module for determining that a vehicle-machine fault has occurred in the vehicle cabin system of the current vehicle if the vehicle driving data set is not empty and the vehicle driving data in the vehicle driving data set increases over time.

[0007] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0008] According to a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the steps of the above method are implemented.

[0009] The beneficial effects of the embodiments of the present application compared with the prior art include at least: the technical solution of the embodiments of the present application generates a data request instruction under the condition that no new heartbeat data is received within a first time period, so as to obtain a data set composed of vehicle driving data whose generation time is later than the first generation time, and determines that a vehicle computer fault occurs when the data set is not empty. Vehicle computer fault monitoring can be realized in the cloud, so that vehicle computer faults can be discovered in a timely and proactive manner, thereby improving the user experience of vehicle computer products. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0011] Figure 1 This is a flow chart of a vehicle computer fault monitoring method provided by an embodiment of the present application;

[0012] Figure 2 This is a flow chart of another vehicle computer fault monitoring method provided by an embodiment of the present application;

[0013] Figure 3 This is a structural diagram of a vehicle fault monitoring device provided by an embodiment of the present application;

[0014] Figure 4 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0015] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0016] The vehicle computer fault monitoring method and device according to the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0017] Figure 1 This is a flow chart of a vehicle fault monitoring method provided by an embodiment of the present application. The method provided by the embodiment of the present application can be executed by any electronic device with computer processing capabilities, such as a terminal or a server. For example, Figure 1 The vehicle computer fault monitoring method shown can be executed by a cloud server communicating with a vehicle client. The vehicle client can be referred to as the vehicle end. Figure 1 As shown, the vehicle computer fault monitoring method includes:

[0018] Step S101: obtaining the heartbeat data periodically reported by the vehicle cabin system of the current vehicle.

[0019] Specifically, the reporting period for periodic heartbeat data reporting can be set to 1 minute, but is not limited thereto. The vehicle cockpit system periodically sends heartbeat data to the cloud server to notify the cloud server of its life status. If the cloud server can periodically receive this heartbeat data, it can be determined that the vehicle cockpit system is in normal working order.

[0020] Step S102: In response to not receiving new heartbeat data within a set first time period, generating a data request instruction for requesting vehicle driving data, the data request instruction including the vehicle identification code of the current vehicle and the first generation time of the last heartbeat data.

[0021] Specifically, the first duration may be an integer multiple of the reporting period of the periodically reported heartbeat data. If the reporting period is 1 minute, the first duration may be N minutes, i.e., N times 1 minute, where N is a natural number greater than or equal to 2. If no new heartbeat data is received within the set first duration, it indicates that the vehicle computer may have a fault.

[0022] Step S103, according to the vehicle identification code, query the vehicle driving data with a generation time later than the first generation time in the preset data warehouse to obtain a vehicle driving data set, wherein the data warehouse stores the vehicle driving data uploaded in real time by the vehicle cabin system and data acquisition equipment of the current vehicle.

[0023] Specifically, vehicle driving data includes cockpit behavior data collected and uploaded by the vehicle cockpit system, and vehicle network control unit driving data collected and uploaded by the data acquisition device. Cockpit behavior data is used to represent the interaction data generated by the human-computer interaction between the user and the vehicle cockpit system. Vehicle network control unit driving data is the vehicle driving data generated by each TBOX (Telematics-BOX, vehicle network control unit) during vehicle driving. After generating a data request instruction requesting vehicle driving data, the vehicle driving data after the first generation time of the last heartbeat data is queried. Based on the obtained vehicle driving data set, it can be determined whether the vehicle computer has failed.

[0024] Step S104 : If the vehicle driving data set is not empty and the vehicle driving data in the vehicle driving data set increases over time, it is determined that a vehicle cabin system of the current vehicle has a vehicle computer failure.

[0025] Specifically, after obtaining the vehicle driving data set, the presence of a fault can be determined based on the vehicle driving data in the vehicle driving data set. If the vehicle driving data set is empty, this indicates that the vehicle cockpit system and data acquisition device are no longer uploading vehicle driving data in real time, and the vehicle is now in a normal power-off state. If the vehicle driving data set is not empty and the data in the vehicle driving data set is continuously increasing, this indicates that the vehicle cockpit system or data acquisition device is still uploading vehicle driving data in real time, and it can be determined that the vehicle is operating normally, but the vehicle computer has a fault.

[0026] The technical solution in this embodiment of the application enables cloud-based monitoring and analysis of vehicle computer status. Data collection and big data analysis can identify faults such as black screens. This allows for timely detection of vehicle computer problems without waiting for user reports or complaints, allowing for timely follow-up visits with users. The technical solution in this embodiment of the application can reduce the probability of user complaints and help enhance brand image.

[0027] Before step S102, a data warehouse for storing vehicle driving data is constructed; cockpit behavior data uploaded by the vehicle cockpit system of the current vehicle is received and stored in the data warehouse; driving data uploaded by the data acquisition device of the current vehicle is received and stored in the data warehouse.

[0028] Specifically, a big data platform and data analysis platform can be built on the cloud server. A data warehouse can be built on the cloud big data platform. The vehicle-side vehicle cockpit system can establish a cockpit system behavior data collection service, periodically reporting heartbeat messages to the cloud big data platform, with a reporting period of 1 minute. In addition, the vehicle-side vehicle cockpit system can also collect real-time cockpit interaction behavior logs (i.e., cockpit behavior data) of users and store them in the data warehouse. Furthermore, the vehicle-side data collection equipment can collect and upload vehicle driving data to the data warehouse in real time.

[0029] Before step S102, the real-time analysis and complex event processing engine of the open source stream processing framework are used to monitor the time interval between the heartbeat data of the vehicle cabin system; when the timing duration started after the first heartbeat data is monitored is equal to the first duration, it is determined that no new heartbeat data is received within the first duration.

[0030] Specifically, the cloud-based big data platform uses a real-time analysis engine and the Flink CEP (Complex Event Processing) model to monitor the maximum value of the interval between two heartbeat data of the vehicle's cockpit system. When the maximum interval exceeds N times of 1 minute, a data request instruction for the vehicle's driving data is sent to the message queue. The data request instruction carries the timestamp T1 of the last heartbeat data sent back by the vehicle and the timestamp T2 of the second heartbeat data in reverse order, as well as the vehicle identification code of the vehicle, which are passed to the message queue. Among them, Flink is an open source stream processing framework for distributed systems that requires computing resources to execute applications.

[0031] Furthermore, the cloud data analysis platform monitors the data request instructions in the message queue, and after receiving the data request instructions, queries the vehicle driving data greater than the timestamp T1 in the data warehouse through the vehicle identification code of the vehicle to obtain the vehicle driving data set.

[0032] In this embodiment of the present application, the data request instruction also includes the second generation time of the penultimate heartbeat data. After step S104, the data warehouse can also be queried for cockpit behavior data and vehicle network control unit driving data between the first generation time and the second generation time, and a vehicle computer fault record can be generated based on the cockpit behavior data and vehicle network control unit driving data.

[0033] Specifically, the cloud data analysis platform queries the data warehouse based on timestamps T1 and T2 to obtain the cockpit behavior data and TBOX driving data in the time period from T1 to T2, stores them in the designated directory of the data warehouse, and generates vehicle computer fault records based on the vehicle driving data in the designated directory.

[0034] Furthermore, after the vehicle computer fault record is generated, the vehicle computer fault record may be sent to a maintenance user and / or a vehicle user of the current vehicle.

[0035] Specifically, after the vehicle computer fault record is generated, a maintenance record can be formed to notify the after-sales department to proactively confirm with the user.

[0036] like Figure 2 As shown, a vehicle computer fault monitoring method according to an embodiment of the present application includes the following steps:

[0037] Step S201: The cloud big data platform builds a data warehouse.

[0038] In step S202, the vehicle-side cockpit system periodically reports heartbeat messages to the cloud big data platform, and simultaneously collects and uploads the user's cockpit interaction behavior logs to the data warehouse in real time. The vehicle-side cockpit system is the vehicle-side vehicle cockpit system.

[0039] In step S203, the vehicle-side driving data collection device uploads the driving data to the data warehouse in real time.

[0040] Step S204: When the cloud big data platform does not receive new heartbeat data within the set first time period, it generates a data request instruction for requesting vehicle driving data.

[0041] In step S205 , the cloud data analysis platform searches for vehicle driving data with a generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle driving data set.

[0042] In step S206, the cloud big data platform determines whether the vehicle driving data set is empty. If so, step S209 is executed; if not, step S207 is executed.

[0043] Step S207 : When the vehicle driving data in the vehicle driving data set increases over time, it is determined that a vehicle cabin system of the current vehicle has a vehicle computer failure.

[0044] Step S208: query the data warehouse for the cockpit behavior data and the vehicle network control unit driving data between the first generation time and the second generation time to generate a vehicle computer fault record.

[0045] Step S209: Determine whether the vehicle is powered off normally.

[0046] According to the vehicle computer fault monitoring method of the embodiment of the present application, a data request instruction is generated under the condition that no new heartbeat data is received within a first time period to obtain a data set consisting of vehicle driving data whose generation time is later than the first generation time, and when the data set is not empty, it is determined that a vehicle computer fault has occurred. Vehicle computer fault monitoring can be implemented in the cloud, so that vehicle computer faults can be discovered in a timely and proactive manner, thereby improving the user experience of vehicle computer products.

[0047] The following are embodiments of the apparatus of the present application, which can be used to implement the embodiments of the method of the present application. The vehicle fault monitoring apparatus described below and the vehicle fault monitoring method described above can be referenced in conjunction with each other. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

[0048] Figure 3 This is a schematic diagram of a vehicle fault monitoring device provided by an embodiment of the present application. Figure 3 As shown, the vehicle fault monitoring device in the embodiment of the present application includes:

[0049] The acquisition module 301 is used to obtain the heartbeat data periodically reported by the vehicle cabin system of the current vehicle.

[0050] Specifically, the reporting period for periodically reporting heartbeat data may be set to 1 minute, but is not limited thereto.

[0051] The generation module 302 is used to generate a data request instruction for requesting vehicle driving data in response to not receiving new heartbeat data within a set first time period. The data request instruction includes the vehicle identification code of the current vehicle and the first generation time of the last heartbeat data.

[0052] Specifically, the first duration may be an integer multiple of the reporting period of the periodically reported heartbeat data. If the reporting period is 1 minute, the first duration may be N minutes, i.e., N times 1 minute, where N is a natural number greater than or equal to 2. If no new heartbeat data is received within the set first duration, it indicates that the vehicle computer may have a fault.

[0053] The query module 303 is used to query the vehicle driving data with a generation time later than the first generation time in the preset data warehouse according to the vehicle identification code to obtain a vehicle driving data set, wherein the data warehouse stores the vehicle driving data uploaded in real time by the vehicle cabin system and data acquisition equipment of the current vehicle.

[0054] Specifically, vehicle driving data includes cockpit behavior data collected and uploaded by the vehicle cockpit system, and vehicle network control unit driving data collected and uploaded by the data acquisition device. The cockpit behavior data is used to represent the interaction data generated by the human-computer interaction between the user and the vehicle cockpit system. The vehicle network control unit driving data is the vehicle driving data generated by each TBOX during vehicle driving. After generating a data request instruction requesting vehicle driving data, the vehicle driving data after the first generation time of the last heartbeat data is queried. Based on the obtained vehicle driving data set, it can be determined whether the vehicle computer has failed.

[0055] The determination module 304 is configured to determine that a vehicle cabin system failure occurs in the current vehicle if the vehicle driving data set is not empty and the vehicle driving data in the vehicle driving data set increases over time.

[0056] Specifically, after obtaining the vehicle driving data set, the presence of a fault can be determined based on the vehicle driving data in the vehicle driving data set. If the vehicle driving data set is empty, this indicates that the vehicle cockpit system and data acquisition device are no longer uploading vehicle driving data in real time, and the vehicle is now in a normal power-off state. If the vehicle driving data set is not empty and the data in the vehicle driving data set is continuously increasing, this indicates that the vehicle cockpit system or data acquisition device is still uploading vehicle driving data in real time, and it can be determined that the vehicle is operating normally, but the vehicle computer has a fault.

[0057] The technical solution in this embodiment of the application enables cloud-based monitoring and analysis of vehicle computer status. Data collection and big data analysis can identify faults such as black screens. This allows for timely detection of vehicle computer problems without waiting for user reports or complaints, allowing for timely follow-up visits with users. The technical solution in this embodiment of the application can reduce the probability of user complaints and help enhance brand image.

[0058] The vehicle fault monitoring device in the embodiment of the present application may also include a storage module for constructing a data warehouse for storing vehicle driving data, receiving cabin behavior data uploaded by the vehicle cabin system of the current vehicle and storing it in the data warehouse, and receiving driving data uploaded by the data acquisition device of the current vehicle and storing it in the data warehouse.

[0059] Specifically, a big data platform and data analysis platform can be built on the cloud server. A data warehouse can be built on the cloud big data platform. The vehicle-side vehicle cockpit system can establish a cockpit system behavior data collection service, periodically reporting heartbeat messages to the cloud big data platform, with a reporting period of 1 minute. In addition, the vehicle-side vehicle cockpit system can also collect real-time cockpit interaction behavior logs (i.e., cockpit behavior data) of users and store them in the data warehouse. Furthermore, the vehicle-side data collection equipment can collect and upload vehicle driving data to the data warehouse in real time.

[0060] The vehicle fault monitoring device in the embodiment of the present application may also include a monitoring module for using the real-time analysis and complex event processing engine of the open source stream processing framework to monitor the time interval between the heartbeat data of the vehicle cabin system; when the timing duration started after the first heartbeat data is monitored is equal to the first duration, it is determined that no new heartbeat data has been received within the first duration.

[0061] Specifically, the cloud-based big data platform uses a real-time analysis engine and the Flink CEP (Complex Event Processing) model to monitor the maximum value of the interval between two heartbeat data of the vehicle's cockpit system. When the maximum interval exceeds N times of 1 minute, a data request instruction for the vehicle's driving data is sent to the message queue. The data request instruction carries the timestamp T1 of the last heartbeat data sent back by the vehicle and the timestamp T2 of the second heartbeat data in reverse order, as well as the vehicle identification code of the vehicle, which are passed to the message queue. Among them, Flink is an open source stream processing framework for distributed systems that requires computing resources to execute applications.

[0062] Furthermore, the cloud data analysis platform monitors the data request instructions in the message queue, and after receiving the data request instructions, queries the vehicle driving data greater than the timestamp T1 in the data warehouse through the vehicle identification code of the vehicle to obtain the vehicle driving data set.

[0063] In an embodiment of the present application, the data request instruction also includes the second generation time of the penultimate heartbeat data. The vehicle computer fault monitoring device in an embodiment of the present application may further include a recording module for querying the data warehouse for cabin behavior data and vehicle network control unit driving data between the first generation time and the second generation time, and generating a vehicle computer fault record based on the cabin behavior data and vehicle network control unit driving data.

[0064] Specifically, the cloud data analysis platform queries the data warehouse based on timestamps T1 and T2 to obtain the cockpit behavior data and TBOX driving data in the time period from T1 to T2, stores them in the designated directory of the data warehouse, and generates vehicle computer fault records based on the vehicle driving data in the designated directory.

[0065] Furthermore, after generating the vehicle computer fault record, the recording module may send the vehicle computer fault record to the maintenance user and / or the vehicle user of the current vehicle.

[0066] Specifically, after the vehicle computer fault record is generated, a maintenance record can be formed to notify the after-sales department to proactively confirm with the user.

[0067] Since the various functional modules of the vehicle fault monitoring device of the example embodiment of the present application correspond to the steps of the example embodiment of the vehicle fault monitoring method mentioned above, for details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the vehicle fault monitoring method mentioned above in the present application.

[0068] According to the vehicle computer fault monitoring device of the embodiment of the present application, a data request instruction is generated under the condition that no new heartbeat data is received within a first time period to obtain a data set composed of vehicle driving data whose generation time is later than the first generation time, and a vehicle computer fault is determined to have occurred when the data set is not empty. Vehicle computer fault monitoring can be implemented in the cloud, so that vehicle computer faults can be discovered in a timely and proactive manner, thereby improving the user experience of vehicle computer products.

[0069] Figure 4 Schematic diagram of the electronic device 4 provided in the embodiment of the present application. Figure 4 As shown, the electronic device 4 of this embodiment includes: a processor 401, a memory 402, and a computer program 403 stored in the memory 402 and executable by the processor 401. When the processor 401 executes the computer program 403, the steps of the above-described method embodiments are implemented. Alternatively, when the processor 401 executes the computer program 403, the functions of the modules in the above-described device embodiments are implemented.

[0070] The electronic device 4 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 4 may include but is not limited to a processor 401 and a memory 402. Those skilled in the art will appreciate that Figure 4 This is merely an example of the electronic device 4 and does not limit the electronic device 4 . The electronic device 4 may include more or fewer components than shown in the figure, or different components.

[0071] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0072] Memory 402 can be an internal storage unit of electronic device 4, such as a hard disk or memory of electronic device 4. Memory 402 can also be an external storage device of electronic device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card, etc. equipped on electronic device 4. Memory 402 can also include both an internal storage unit of electronic device 4 and an external storage device. Memory 402 is used to store computer programs and other programs and data required by the electronic device.

[0073] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0074] If the integrated module is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0075] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A vehicle computer fault monitoring method, characterized in that: The method comprises: Get the heartbeat data periodically reported by the vehicle cockpit system of the current vehicle; In response to not receiving new heartbeat data within a set first time period, generating a data request instruction for requesting vehicle driving data, the data request instruction including a vehicle identification code of the current vehicle and a first generation time of the last heartbeat data; querying a preset data warehouse for vehicle driving data generated later than the first generation time according to the vehicle identification code to obtain a vehicle driving data set, wherein the data warehouse stores the vehicle driving data uploaded in real time by a vehicle cabin system and a data acquisition device of the current vehicle; If the vehicle driving data set is not empty and the vehicle driving data in the vehicle driving data set increases over time, it is determined that a vehicle cabin system of the current vehicle has a vehicle computer failure; In which, the data request instruction also includes the second generation time of the penultimate heartbeat data; after determining that a vehicle computer failure occurs in the vehicle cabin system of the current vehicle, the method also includes: querying the cabin behavior data and the vehicle network control unit driving data between the first generation time and the second generation time in the data warehouse, and generating a vehicle computer failure record based on the cabin behavior data and the vehicle network control unit driving data.

2. The method according to claim 1, characterized in that After obtaining the vehicle travel data set, the method further includes: If the vehicle driving data set is empty, it is determined that the current vehicle is powered off normally.

3. The method according to claim 1, characterized in that After generating the vehicle computer fault record, the method further includes: The vehicle computer fault record is sent to a maintenance user and / or a vehicle user of the current vehicle.

4. The method according to claim 1, wherein Before generating a data request instruction for requesting vehicle driving data, the method further includes: Using a real-time analysis and complex event processing engine based on an open source stream processing framework to monitor the time interval between heartbeat data of the vehicle cabin system; When the timing duration that starts after the first heartbeat data is monitored is equal to the first duration, it is determined that no new heartbeat data is received within the first duration.

5. The method according to claim 1, wherein Before searching a preset data warehouse for vehicle travel data whose generation time is later than the first generation time according to the vehicle identification code, the method further includes: Build a data warehouse to store vehicle driving data; Receiving cockpit behavior data uploaded by the vehicle cockpit system of the current vehicle and storing the data in the data warehouse; Receive the driving data uploaded by the data acquisition device of the current vehicle and store it in the data warehouse.

6. The method according to claim 1, characterized in that The first duration is an integer multiple of a reporting period of the periodically reported heartbeat data.

7. A vehicle fault monitoring device, characterized in that: The device comprises: An acquisition module is used to obtain the heartbeat data periodically reported by the vehicle cabin system of the current vehicle; a generating module configured to generate, in response to not receiving new heartbeat data within a set first time period, a data request instruction for requesting vehicle driving data, the data request instruction including a vehicle identification code of the current vehicle and a first generation time of the last heartbeat data; a query module, configured to query a preset data warehouse for vehicle travel data generated later than the first generation time based on the vehicle identification code, to obtain a vehicle travel data set, wherein the data warehouse stores the vehicle travel data uploaded in real time by a vehicle cabin system and a data acquisition device of the current vehicle; a determination module, configured to determine that a vehicle cabin system of the current vehicle has a vehicle computer fault if the vehicle driving data set is not empty and the vehicle driving data in the vehicle driving data set increases over time; In which, the data request instruction also includes the second generation time of the penultimate heartbeat data; after determining that a vehicle-computer fault occurs in the vehicle cabin system of the current vehicle, the query module is also used to query the cabin behavior data and the vehicle network control unit driving data between the first generation time and the second generation time in the data warehouse, and the determination module is also used to generate a vehicle-computer fault record based on the cabin behavior data and the vehicle network control unit driving data.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images