CN116593171A - Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium - Google Patents

Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN116593171A
CN116593171A CN202310476741.6A CN202310476741A CN116593171A CN 116593171 A CN116593171 A CN 116593171A CN 202310476741 A CN202310476741 A CN 202310476741A CN 116593171 A CN116593171 A CN 116593171A
Authority
CN
China
Prior art keywords
vehicle
data
time
vehicle running
running data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310476741.6A
Other languages
Chinese (zh)
Inventor
何快洛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chongqing Selis Phoenix Intelligent Innovation Technology Co ltd
Original Assignee
Chengdu Seres Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chengdu Seres Technology Co Ltd filed Critical Chengdu Seres Technology Co Ltd
Priority to CN202310476741.6A priority Critical patent/CN116593171A/en
Publication of CN116593171A publication Critical patent/CN116593171A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
    • G01M17/00—Testing of vehicles
    • G01M17/007—Wheeled or endless-tracked vehicles
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The application provides a vehicle-mounted device fault monitoring method, a device, electronic equipment and a readable storage medium. The method comprises the following steps: acquiring heartbeat data periodically reported by a vehicle cabin system of a current vehicle; generating a data request instruction for requesting vehicle running data in response to the fact that new heartbeat data is not received within a set first duration, wherein the data request instruction comprises a vehicle identification code of a current vehicle and first generation time of last piece of heartbeat data; inquiring vehicle running data with the generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle running data set; if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set increases with time, determining that a vehicle cabin system of the current vehicle has a vehicle machine fault. By adopting the technical scheme of the application, the faults of the vehicle and the machine can be actively found in time so as to carry out after-sales maintenance.

Description

Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and apparatus for monitoring a vehicle-mounted device, an electronic device, and a readable storage medium.
Background
Along with the intelligent and software process of the automobile, the functions of the large screen of the automobile cabin are more and more, and the problems of black screen, dead halt and the like possibly occurring in the automobile cabin are gradually exposed. However, the vehicle manufacturer generally passively discovers the failure of the vehicle after receiving the failure report of the vehicle user, so that the after-sale of the vehicle is not timely enough.
How to actively discover the faults of the vehicle and machine in time and to carry out after-sales maintenance and service in time is a technical problem which needs to be solved currently.
Disclosure of Invention
In view of the above, the embodiments of the present application provide a method, an apparatus, an electronic device, and a computer readable storage medium for monitoring a vehicle-machine fault, so as to solve the problem that a vehicle-machine fault cannot be actively found in time.
In a first aspect of the embodiment of the present application, a method for monitoring a vehicle-mounted device fault is provided, where the method includes: acquiring heartbeat data periodically reported by a vehicle cabin system of a current vehicle; generating a data request instruction for requesting vehicle running data in response to the fact that new heartbeat data is not received within a set first duration, wherein the data request instruction comprises a vehicle identification code of a current vehicle and first generation time of last piece of heartbeat data; inquiring vehicle running data with the generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle running data set, wherein the data warehouse stores vehicle running data uploaded in real time by a vehicle cabin system and data acquisition equipment of a current vehicle; if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set increases with time, determining that a vehicle cabin system of the current vehicle has a vehicle machine fault.
In a second aspect of the embodiment of the present application, there is provided a vehicle-mounted device for monitoring a failure of a vehicle, the device comprising: the acquisition module is used for acquiring heartbeat data periodically reported by a vehicle cabin system of the current vehicle; the generation module is used for generating a data request instruction for requesting vehicle running data in response to the fact that new heartbeat data are not received within a set first duration, wherein the data request instruction comprises a vehicle identification code of a current vehicle and first generation time of the last piece of heartbeat data; the query module is used for querying vehicle running data with the generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle running data set, wherein the data warehouse stores vehicle running data uploaded by a vehicle cabin system and a data acquisition device of the current vehicle in real time; and the determining module is used for determining that the vehicle cabin system of the current vehicle has a vehicle machine fault if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set increases with time.
In a third aspect of the embodiments of the present application, there is provided an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above method when executing the computer program.
In a fourth aspect of the embodiments of the present application, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the above method.
Compared with the prior art, the embodiment of the application has the beneficial effects that: according to the technical scheme, the data request instruction is generated under the condition that new heartbeat data is not received within the first duration, so that the data set formed by the vehicle running data with the generation time later than the first generation time is obtained, the occurrence of the vehicle-to-vehicle fault is determined when the data set is not empty, the monitoring of the vehicle-to-vehicle fault can be realized at the cloud, and therefore the vehicle-to-vehicle fault can be timely and actively found, and the user experience of a vehicle-to-vehicle product is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a vehicle-mounted fault monitoring method provided by an embodiment of the application;
FIG. 2 is a schematic flow chart of another method for monitoring vehicle-mounted faults according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a fault monitoring device for a vehicle machine according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
The following describes in detail a vehicle-to-machine fault monitoring method and device according to an embodiment of the present application with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of a vehicle-mounted fault monitoring method according to an embodiment of the present application. The method provided by the embodiment of the application can be executed by any electronic device with computer processing capability, such as a terminal or a server. For example, the vehicle failure monitoring method as shown in fig. 1 may be performed by a cloud server in communication with a vehicle client. Wherein, the vehicle client may be simply referred to as a vehicle end. As shown in fig. 1, the vehicle-mounted fault monitoring method includes:
step S101, acquiring heartbeat data periodically reported by a vehicle cabin system of a current vehicle.
Specifically, the reporting period of periodically reporting the heartbeat data may be set to 1 minute, and is not limited thereto. The heartbeat data are periodically sent to the cloud server by the vehicle cabin system so as to inform the cloud server of the life state of the vehicle cabin system. If the cloud server can periodically receive the heartbeat data, it can be determined that the vehicle cabin system is in a normal working state.
Step S102, in response to the fact that the new heartbeat data is not received within the set first duration, a data request instruction for requesting the vehicle running data is generated, wherein the data request instruction comprises a vehicle identification code of the current vehicle and a first generation time of the last piece of heartbeat data.
Specifically, the first duration may be an integer multiple of a reporting period of the periodically reported heartbeat data. When the reporting period is 1 minute, the first duration may be N minutes, i.e., 1 minute N times, where N is a natural number and N is greater than or equal to 2. And (5) not receiving new heartbeat data in the set first time period, and indicating that the vehicle machine possibly fails.
Step S103, inquiring vehicle running data with the generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle running data set, wherein the data warehouse stores vehicle running data uploaded by a vehicle cabin system and a data acquisition device of the current vehicle in real time.
Specifically, the vehicle driving data comprises cabin behavior data collected and uploaded by a vehicle cabin system and vehicle networking control unit driving data collected and uploaded by data collecting equipment. The cabin behavior data are used for representing interaction data generated by man-machine interaction behavior between a user and a vehicle cabin system. The vehicle networking control unit driving data is vehicle driving data generated by each TBOX (Telematics-BOX) in the vehicle driving process. After a data request instruction for requesting the vehicle running data is generated, the vehicle running data after the first generation time of the last piece of heartbeat data is queried, and whether the vehicle machine of the vehicle determines that a fault occurs or not can be judged according to the obtained vehicle running data set.
Step S104, if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set increases with time, determining that the vehicle cabin system of the current vehicle has a vehicle machine fault.
Specifically, after the vehicle running data set is obtained, whether or not a failure occurs may be determined according to the vehicle running data conditions in the vehicle running data set. If the vehicle running data set is empty, the vehicle cabin system and the data acquisition equipment prove that the vehicle running data is not uploaded in real time any more, and the vehicle is in a normal power-down state. If the vehicle running data set is not empty and the data in the vehicle running data set is continuously increased, the vehicle cabin system or the data acquisition equipment is proved to be still uploading the vehicle running data in real time, and at the moment, the normal running of the vehicle can be determined, but the vehicle machine fails.
According to the technical scheme, monitoring analysis of the vehicle-mounted condition can be achieved at the cloud, faults such as the black screen of the vehicle-mounted condition can be found through data acquisition and big data analysis, and accordingly the vehicle-mounted problem can be found in time without waiting for user reporting and complaining, and return visit can be conducted on the user in time. By adopting the technical scheme provided by the embodiment of the application, the complaint probability of the user can be reduced, and the brand image can be improved.
Prior to step S102, a data warehouse storing vehicle travel data is constructed; receiving cabin behavior data uploaded by a vehicle cabin system of a current vehicle and storing the cabin behavior data into a data warehouse; and receiving driving data uploaded by the data acquisition equipment of the current vehicle and storing the driving data into a data warehouse.
Specifically, a big data platform and a data analysis platform can be constructed on a cloud server. A data warehouse can be constructed on the cloud big data platform. The vehicle cabin system at the vehicle end can construct cabin system behavior data acquisition service, and periodically report heartbeat messages to the cloud big data platform, wherein the reporting period can be 1 minute. In addition, the vehicle cabin system at the vehicle end can also collect cabin interaction behavior logs of the user, namely cabin behavior data, to the data warehouse in real time. In addition, the data acquisition equipment at the vehicle end can acquire and upload vehicle driving data to the data warehouse in real time.
Before step S102, monitoring a time interval between heartbeat data of a vehicle cabin system using a real-time analysis of an open source flow processing framework and a complex event processing engine; and when the timing duration of starting to time after the first heartbeat data is monitored is equal to the first duration, determining that new heartbeat data is not received in the first duration.
Specifically, the cloud big data platform monitors the maximum value of the interval between two pieces of heartbeat data of the vehicle cabin system using a real-time analysis engine and a flight CEP (Complex Event Processing ) model. When the maximum value interval exceeds N times of 1 minute, a data request instruction of the vehicle running data is sent to the message queue, wherein the data request instruction carries a time stamp T1 of the last heartbeat data returned by the vehicle at present and a time stamp T2 of the second heartbeat data in the reverse order, and the vehicle identification code of the vehicle is transmitted to the message queue. Wherein, the Flink is an open source stream processing framework of a distributed system, and requires computing resources to execute the application program.
Further, the cloud data analysis platform monitors a data request instruction in the message queue, and queries vehicle running data greater than a time stamp T1 in the data warehouse through a vehicle identification code of the vehicle after receiving the data request instruction, so as to obtain a vehicle running data set.
In an embodiment of the present application, the data request instruction further includes a second generation time of the penultimate heartbeat data. After step S104, the data warehouse may further query cabin behavior data and vehicle networking control unit driving data between the first generation time and the second generation time, and generate a vehicle-to-machine fault record according to the cabin behavior data and the vehicle networking control unit driving data.
Specifically, the cloud data analysis platform queries the data warehouse according to the time stamp T1 and the time stamp T2 to obtain cabin behavior data and TBOX driving data in the time period from T1 to T2, stores the cabin behavior data and the TBOX driving data in a designated directory of the data warehouse, and generates a vehicle-to-vehicle fault record according to the vehicle driving data in the designated directory.
Further, after the vehicle-to-machine fault record is generated, the vehicle-to-machine fault record may be sent to a maintenance user and/or a vehicle user of the current vehicle.
Specifically, after the vehicle-machine fault record is generated, a maintenance record can be formed to inform the after-sales department to actively confirm to the user.
As shown in fig. 2, the vehicle-mounted fault monitoring method according to an embodiment of the present application includes the following steps:
step S201, a cloud big data platform builds a data warehouse.
Step S202, a vehicle cabin system periodically reports heartbeat messages to a cloud big data platform, and simultaneously acquires and uploads cabin interaction behavior logs of users to a data warehouse in real time. The vehicle cabin system at the vehicle end is the vehicle cabin system at the vehicle end.
Step S203, the vehicle-end driving data acquisition equipment uploads driving data to the data warehouse in real time.
Step S204, when the cloud big data platform does not receive new heartbeat data within a set first duration, a data request instruction for requesting vehicle running data is generated.
In step S205, the cloud data analysis platform queries, according to the vehicle identification code, the vehicle running data with the generation time later than the first generation time in the preset data warehouse, and obtains a vehicle running data set.
Step S206, the cloud big data platform judges whether a vehicle running data set is empty or not. If yes, go to step S209, if no, go to step S207.
Step S207 determines that a vehicle cabin system of the current vehicle has a vehicle-machine failure when the vehicle travel data in the vehicle travel data set increases with time.
And step S208, inquiring cabin behavior data and vehicle-networking control unit driving data between the first generation time and the second generation time in the data warehouse, and generating a vehicle-machine fault record.
Step S209, determining that the vehicle is powered down normally.
According to the vehicle-mounted machine fault monitoring method, the data request instruction is generated under the condition that new heartbeat data is not received in the first duration, so that a data set formed by vehicle running data with the generation time being later than the first generation time is obtained, the occurrence of the vehicle-mounted machine fault is determined when the data set is not empty, and the vehicle-mounted machine fault monitoring can be realized at the cloud, so that the vehicle-mounted machine fault can be timely and actively discovered, and the user experience of a vehicle-mounted machine product is improved.
The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. The vehicle-machine fault monitoring device described below and the vehicle-machine fault monitoring method described above may be referred to correspondingly to 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.
Fig. 3 is a schematic diagram of a fault monitoring device for a vehicle machine according to an embodiment of the present application. As shown in fig. 3, the vehicle-mounted device for monitoring a vehicle fault in an embodiment of the present application includes:
the acquiring module 301 is configured to acquire heartbeat data periodically reported by a vehicle cabin system of a current vehicle.
Specifically, the reporting period of periodically reporting the heartbeat data may be set to 1 minute, and is not limited thereto.
The generating module 302 is configured to generate, in response to not receiving new heartbeat data within a set first duration, a data request instruction for requesting vehicle running data, where the data request instruction includes a vehicle identification code of a current vehicle and a first generation time of a last piece of heartbeat data.
Specifically, the first duration may be an integer multiple of a reporting period of the periodically reported heartbeat data. When the reporting period is 1 minute, the first duration may be N minutes, i.e., 1 minute N times, where N is a natural number and N is greater than or equal to 2. And (5) not receiving new heartbeat data in the set first time period, and indicating that the vehicle machine possibly fails.
And the query module 303 is configured to query, in a preset data warehouse, vehicle running data with a generation time later than the first generation time according to the vehicle identification code, and obtain a vehicle running data set, where the data warehouse stores vehicle running data uploaded in real time by a vehicle cabin system and a data acquisition device of a current vehicle.
Specifically, the vehicle driving data comprises cabin behavior data collected and uploaded by a vehicle cabin system and vehicle networking control unit driving data collected and uploaded by data collecting equipment. The cabin behavior data are used for representing interaction data generated by man-machine interaction behavior between a user and a vehicle cabin system. The vehicle networking control unit driving data are vehicle driving data generated by each TBOX in the vehicle driving process. After a data request instruction for requesting the vehicle running data is generated, the vehicle running data after the first generation time of the last piece of heartbeat data is queried, and whether the vehicle machine of the vehicle determines that a fault occurs or not can be judged according to the obtained vehicle running data set.
The determining module 304 is configured to determine that a vehicle cabin system of the current vehicle has a vehicle-to-vehicle failure if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set increases with time.
Specifically, after the vehicle running data set is obtained, whether or not a failure occurs may be determined according to the vehicle running data conditions in the vehicle running data set. If the vehicle running data set is empty, the vehicle cabin system and the data acquisition equipment prove that the vehicle running data is not uploaded in real time any more, and the vehicle is in a normal power-down state. If the vehicle running data set is not empty and the data in the vehicle running data set is continuously increased, the vehicle cabin system or the data acquisition equipment is proved to be still uploading the vehicle running data in real time, and at the moment, the normal running of the vehicle can be determined, but the vehicle machine fails.
According to the technical scheme, monitoring analysis of the vehicle-mounted condition can be achieved at the cloud, faults such as the black screen of the vehicle-mounted condition can be found through data acquisition and big data analysis, and accordingly the vehicle-mounted problem can be found in time without waiting for user reporting and complaining, and return visit can be conducted on the user in time. By adopting the technical scheme provided by the embodiment of the application, the complaint probability of the user can be reduced, and the brand image can be improved.
The vehicle-mounted fault monitoring device in the embodiment of the application can further comprise a storage module, wherein the storage module is used for constructing a data warehouse for storing vehicle running data, receiving cabin behavior data uploaded by a vehicle cabin system of a current vehicle and storing the cabin behavior data into the data warehouse, and receiving running data uploaded by data acquisition equipment of the current vehicle and storing the running data into the data warehouse.
Specifically, a big data platform and a data analysis platform can be constructed on a cloud server. A data warehouse can be constructed on the cloud big data platform. The vehicle cabin system at the vehicle end can construct cabin system behavior data acquisition service, and periodically report heartbeat messages to the cloud big data platform, wherein the reporting period can be 1 minute. In addition, the vehicle cabin system at the vehicle end can also collect cabin interaction behavior logs of the user, namely cabin behavior data, to the data warehouse in real time. In addition, the data acquisition equipment at the vehicle end can acquire and upload vehicle driving data to the data warehouse in real time.
The vehicle-mounted machine fault monitoring device in the embodiment of the application can also comprise a monitoring module, a control module and a control module, wherein the monitoring module is used for monitoring the time interval between heartbeat data of a vehicle cabin system by adopting a real-time analysis of an open source flow processing frame and a complex event processing engine; and when the timing duration of starting to time after the first heartbeat data is monitored is equal to the first duration, determining that new heartbeat data is not received in the first duration.
Specifically, the cloud big data platform monitors the maximum value of the interval between two pieces of heartbeat data of the vehicle cabin system using a real-time analysis engine and a flight CEP (Complex Event Processing ) model. When the maximum value interval exceeds N times of 1 minute, a data request instruction of the vehicle running data is sent to the message queue, wherein the data request instruction carries a time stamp T1 of the last heartbeat data returned by the vehicle at present and a time stamp T2 of the second heartbeat data in the reverse order, and the vehicle identification code of the vehicle is transmitted to the message queue. Wherein, the Flink is an open source stream processing framework of a distributed system, and requires computing resources to execute the application program.
Further, the cloud data analysis platform monitors a data request instruction in the message queue, and queries vehicle running data greater than a time stamp T1 in the data warehouse through a vehicle identification code of the vehicle after receiving the data request instruction, so as to obtain a vehicle running data set.
In an embodiment of the present application, the data request instruction further includes a second generation time of the penultimate heartbeat data. The vehicle-mounted fault monitoring device in the embodiment of the application can further comprise a recording module, wherein the recording module is used for inquiring cabin behavior data and vehicle-mounted control unit driving data between the first generation time and the second generation time in the data warehouse, and generating a vehicle-mounted fault record according to the cabin behavior data and the vehicle-mounted control unit driving data.
Specifically, the cloud data analysis platform queries the data warehouse according to the time stamp T1 and the time stamp T2 to obtain cabin behavior data and TBOX driving data in the time period from T1 to T2, stores the cabin behavior data and the TBOX driving data in a designated directory of the data warehouse, and generates a vehicle-to-vehicle fault record according to the vehicle driving data in the designated directory.
Further, after the vehicle-to-machine fault record is generated, the recording module may send the vehicle-to-machine fault record to a maintenance user and/or a vehicle user of the current vehicle.
Specifically, after the vehicle-machine fault record is generated, a maintenance record can be formed to inform the after-sales department to actively confirm to the user.
Since each functional module of the vehicle-to-machine fault monitoring device according to the exemplary embodiment of the present application corresponds to a step of the foregoing exemplary embodiment of the vehicle-to-machine fault monitoring method, for details not disclosed in the embodiment of the device of the present application, please refer to the foregoing embodiment of the vehicle-to-machine fault monitoring method according to the present application.
According to the vehicle-mounted machine fault monitoring device provided by the embodiment of the application, the data request instruction is generated under the condition that new heartbeat data is not received in the first time period, so that the data set formed by the vehicle running data with the generation time later than the first generation time is obtained, the occurrence of the vehicle-mounted machine fault is determined when the data set is not empty, and the vehicle-mounted machine fault monitoring can be realized at the cloud, so that the vehicle-mounted machine fault can be timely and actively discovered, and the user experience of a vehicle-mounted machine product is improved.
Fig. 4 is a schematic diagram of an electronic device 4 according to an embodiment of the present application. As shown in fig. 4, the electronic apparatus 4 of this embodiment includes: a processor 401, a memory 402 and a computer program 403 stored in the memory 402 and executable on the processor 401. The steps of the various method embodiments described above are implemented by processor 401 when executing computer program 403. Alternatively, the processor 401 may execute the computer program 403 to implement the functions of the modules in the above-described device embodiments.
The electronic device 4 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. The electronic device 4 may include, but is not limited to, a processor 401 and a memory 402. It will be appreciated by those skilled in the art that fig. 4 is merely an example of the electronic device 4 and is not limiting of the electronic device 4 and may include more or fewer components than shown, or different components.
The processor 401 may be a central processing unit (Central Processing Unit, CPU) or other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.
The memory 402 may be an internal storage unit of the electronic device 4, for example, a hard disk or a memory of the electronic device 4. The memory 402 may also be an external storage device of the electronic device 4, for example, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the electronic device 4. Memory 402 may also include both internal storage units and external storage devices of electronic device 4. The memory 402 is used to store computer programs and other programs and data required by the electronic device.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit.
The integrated modules, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. The computer program may comprise computer program code, which may be in source code form, object code form, executable file or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be appropriately increased or decreased according to the requirements of the jurisdiction's jurisdiction and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the jurisdiction and the patent practice.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (10)

1. A vehicle-to-machine fault monitoring method, the method comprising:
acquiring heartbeat data periodically reported by a vehicle cabin system of a current vehicle;
generating a data request instruction for requesting vehicle running data in response to the fact that new heartbeat data is not received within a set first duration, wherein the data request instruction comprises a vehicle identification code of the current vehicle and first generation time of the last piece of heartbeat data;
inquiring vehicle running data with the generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle running data set, wherein the data warehouse stores vehicle running data uploaded by a vehicle cabin system and data acquisition equipment of the current vehicle in real time;
and if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set is increased with time, determining that a vehicle cabin system of the current vehicle has a vehicle-to-machine fault.
2. The method of claim 1, wherein after obtaining the vehicle travel data set, the method further comprises:
and if the vehicle running data set is empty, determining that the current vehicle is powered down normally.
3. The method of claim 1, wherein the data request instruction further comprises a second generation time of a penultimate beat of heart data; after determining that the vehicle cabin system of the current vehicle has a vehicle-to-vehicle failure, the method further includes:
and inquiring cabin behavior data and vehicle-network control unit driving data between the first generation time and the second generation time in the data warehouse, and generating a vehicle-machine fault record according to the cabin behavior data and the vehicle-network control unit driving data.
4. The method of claim 1, wherein after generating the vehicle-to-machine fault record, the method further comprises:
and sending the vehicle-to-machine fault record to a maintenance user and/or a vehicle user of the current vehicle.
5. The method according to claim 1, wherein before generating the data request instruction requesting the vehicle running data, the method further comprises:
monitoring a time interval between heartbeat data of the vehicle cabin system by adopting real-time analysis of an open source stream processing framework and a complex event processing engine;
and when the timing duration of starting timing after the first heartbeat data is monitored is equal to the first duration, determining that new heartbeat data is not received in the first duration.
6. The method of claim 1, wherein prior to querying a preset data warehouse for vehicle travel data having a time of generation later than the first time of generation based on the vehicle identification code, the method further comprises:
constructing a data warehouse for storing vehicle driving data;
receiving cabin behavior data uploaded by a vehicle cabin system of the current vehicle and storing the cabin behavior data into the data warehouse;
and receiving the driving data uploaded by the data acquisition equipment of the current vehicle and storing the driving data into the data warehouse.
7. The method of claim 1, wherein the first duration is an integer multiple of a reporting period of the periodically reported heartbeat data.
8. A vehicle-to-machine fault monitoring device, the device comprising:
the acquisition module is used for acquiring heartbeat data periodically reported by a vehicle cabin system of the current vehicle;
the generation module is used for generating a data request instruction for requesting vehicle running data in response to the fact that new heartbeat data are not received within a set first duration, wherein the data request instruction comprises a vehicle identification code of the current vehicle and first generation time of last piece of heartbeat data;
the query module is used for querying vehicle running data with the generation time later than the first generation time in a preset data warehouse according to the vehicle identification code to obtain a vehicle running data set, wherein the data warehouse stores the vehicle running data uploaded by a vehicle cabin system and data acquisition equipment of the current vehicle in real time;
and the determining module is used for determining that the vehicle cabin system of the current vehicle has a vehicle machine fault if the vehicle running data set is not empty and the vehicle running data in the vehicle running data set increases with time.
9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method according to any one of claims 1 to 7.
CN202310476741.6A 2023-04-28 2023-04-28 Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium Pending CN116593171A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310476741.6A CN116593171A (en) 2023-04-28 2023-04-28 Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310476741.6A CN116593171A (en) 2023-04-28 2023-04-28 Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN116593171A true CN116593171A (en) 2023-08-15

Family

ID=87605466

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310476741.6A Pending CN116593171A (en) 2023-04-28 2023-04-28 Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN116593171A (en)

Similar Documents

Publication Publication Date Title
CN108512689B (en) Micro-service monitoring method and server
CN107888452B (en) 24-hour distributed website performance monitoring and real-time alarming method
CN111966289B (en) Partition optimization method and system based on Kafka cluster
WO2021164562A1 (en) Terminal behavior data obtaining method and apparatus, terminal behavior data sending method and apparatus, and network device
CN112783725B (en) Index collection method and device
CN113452486B (en) Vehicle information uploading method, device, equipment and storage medium
CN106357442A (en) Server cluster monitoring method and system
CN111049673A (en) Method and system for counting and monitoring API call in service gateway
WO2023109806A1 (en) Method and apparatus for processing active data for internet of things device, and storage medium
CN115001989A (en) Equipment early warning method, device, equipment and readable storage medium
CN110225113B (en) Service monitoring method and system
CN116593171A (en) Vehicle-mounted machine fault monitoring method and device, electronic equipment and readable storage medium
CN109831335B (en) Data monitoring method, monitoring terminal, storage medium and data monitoring system
CN113190583B (en) Data acquisition system, method, electronic equipment and storage medium
CN112533246B (en) Monitoring system and method for frequent network requests of intelligent equipment
CN110633191A (en) Method and system for monitoring service health degree of software system in real time
CN113965447B (en) Online cloud diagnosis method, device, system, equipment and storage medium
CN116010388A (en) Data verification method, data acquisition server and data verification system
CN115277355A (en) Method, device, equipment and medium for processing state code data of monitoring system
EP4044033A1 (en) Method and apparatus for acquiring data
CN112929191B (en) Service monitoring method, system, related equipment and device
CN108829563B (en) Alarm method and alarm device
CN110995839B (en) Method and device for analyzing performance of advertisement system and computer storage medium
CN110430093B (en) Data processing method and device and computer readable storage medium
CN114827126B (en) IPTVCDN user play log reporting method and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20240117

Address after: No. 13 Xingxiang Road, Zengjia Town, High tech Zone, Shapingba District, Chongqing, 400039

Applicant after: Chongqing Selis Phoenix Intelligent Innovation Technology Co.,Ltd.

Address before: 610095 No. 2901, floor 29, unit 1, building 1, No. 151, Tianfu Second Street, high tech Zone, China (Sichuan) pilot Free Trade Zone, Chengdu, Sichuan Province

Applicant before: Chengdu Thalys Technology Co.,Ltd.

TA01 Transfer of patent application right