Fault processing method and device, electronic equipment, storage medium and product
By only transmitting first-level fault data of vehicle failure, the problem of long data transmission time after vehicle failure is solved, the fault diagnosis efficiency is improved, and the timeliness and accuracy of maintenance is ensured.
Patent Information
- Application Number
- CN202410892214.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-04
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2044-07-04
AI Technical Summary
In the prior art, after a vehicle fails, it is uploaded to the cloud server through a data buried point, resulting in an increase in the amount of data, a long transmission time, and affecting maintenance efficiency.
When a vehicle detects a fault, only the first-level fault data (including fault type and fault timestamp) are obtained and transmitted from the cloud server to the operation and maintenance terminal. The operation and maintenance terminal uses this data to diagnose faults.
It greatly reduces the amount and time of data transmission, improves the efficiency of fault diagnosis results, ensures accurate diagnosis results, and facilitates timely repairs.
Smart Images

Figure CN118938848A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the field of vehicle control technology, and in particular, to a fault handling method, device, electronic equipment, storage medium and product. Background Art
[0002] In order to improve the safety of the vehicle, it is necessary to detect the working status of the vehicle, diagnose the vehicle's faults, and perform effective repairs in a timely manner.
[0003] In the prior art, after a vehicle breaks down, the vehicle operating information is obtained through data embedding, and the vehicle operating information is uploaded to a cloud server, which then sends it to an operation and maintenance terminal, making it easier for operation and maintenance personnel to troubleshoot and repair the vehicle.
[0004] However, in the process of implementing the present invention, it was found that the prior art has at least the following technical problems: in actual applications, the fault scenarios are complex and the number of buried points continues to increase, resulting in an increase in the amount of buried point data obtained. It takes a long time to upload all the buried point data to the cloud server, and the operation and maintenance terminal cannot obtain the uploaded buried point data in time, affecting the repair efficiency of vehicle faults. Summary of the invention
[0005] The embodiments of the present invention provide a fault handling method, device, electronic device, storage medium and product to achieve the purpose of improving the efficiency of determining fault diagnosis results and facilitate timely maintenance of a target vehicle.
[0006] According to one aspect of the present invention, a fault handling method is provided, comprising:
[0007] When a fault is detected in a target vehicle, primary fault data of the target vehicle is obtained; wherein the primary fault data includes a target fault type and a fault timestamp of the target vehicle;
[0008] Transmitting the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data when the primary fault data is all valid data;
[0009] The valid data is the data required to obtain the fault diagnosis result determined by the operation and maintenance terminal.
[0010] According to another aspect of the present invention, a fault handling device is provided, the device comprising:
[0011] A primary fault data acquisition module, used to acquire primary fault data of the target vehicle when a fault is detected in the target vehicle; wherein the primary fault data includes a target fault type and a fault timestamp of the target vehicle;
[0012] A data transmission module, used for transmitting the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data when the primary fault data is all valid data;
[0013] The valid data is the data required to obtain the fault diagnosis result determined by the operation and maintenance terminal.
[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:
[0015] at least one processor; and
[0016] a memory communicatively connected to the at least one processor; wherein,
[0017] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the fault handling method described in any embodiment of the present invention.
[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the fault handling method described in any embodiment of the present invention when executed.
[0019] According to another aspect of the present invention, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the fault handling method according to any embodiment of the present invention is implemented.
[0020] The technical solution of the embodiment of the present invention is to obtain the first-level fault data of the target vehicle when a fault is detected in the target vehicle; wherein the first-level fault data includes the target fault type and fault timestamp of the target vehicle; the first-level fault data is transmitted from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the first-level fault data when the first-level fault data is all valid data; wherein the valid data is the data required for obtaining the fault diagnosis result determined by the operation and maintenance terminal. This embodiment only transmits the target fault type and fault timestamp of the target vehicle to the cloud server, and then the cloud server transmits the target fault type and fault timestamp to the operation and maintenance terminal, thereby greatly reducing the amount of data transmitted and the transmission process is time-consuming; and when the first-level fault data is all valid data, the operation and maintenance terminal determines the fault diagnosis result based on the first-level fault data, thereby ensuring that accurate fault diagnosis results can be obtained, while improving the efficiency of determining the fault diagnosis result, and facilitating timely repair of the target vehicle.
[0021] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0023] Figure 1 is a flowchart of a fault handling method provided according to an embodiment of the present invention;
[0024] Figure 2 is a flowchart of another fault handling method provided according to an embodiment of the present invention;
[0025] Figure 3 is a structural schematic diagram of a fault handling device provided according to an embodiment of the present invention;
[0026] Figure 4 It is a structural schematic diagram of an electronic device for implementing the fault handling method of an embodiment of the present invention. DETAILED DESCRIPTION
[0027] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.
[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "etc." and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0029] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution of this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information and network security.
[0030] Figure 1 This is a flow chart of a fault handling method provided according to an embodiment of the present invention. This embodiment is applicable to the case where a fault diagnosis result is determined for a fault occurring in a target vehicle. The method can be executed by a fault handling device, which can be implemented in the form of hardware and / or software.
[0031] like Figure 1 As shown, the method of this embodiment may specifically include:
[0032] S110. When a fault is detected in the target vehicle, primary fault data of the target vehicle is obtained.
[0033] The first-level fault data includes the target fault type and fault timestamp of the target vehicle. For example, the target fault type can be reflected by the fault code that appears when the target vehicle fails.
[0034] In this embodiment, the target vehicle controller can be used to determine whether the target vehicle has a fault. Specifically, the controller can detect the components of the target vehicle regularly or in real time to determine whether the target vehicle has a fault. In order to better store data, a domain controller with strong computing power and storage capacity can be used to obtain fault data. Specifically, a bus and a switch can be used to realize the communication between the components inside the target vehicle and the domain controller.
[0035] Specifically, when a fault is detected in the target vehicle, the primary fault data of the target vehicle may be obtained in order to diagnose and locate the existing fault. It should be noted that the fault data may be divided into different levels according to the relevance of the fault data to the fault diagnosis process. The higher the relevance, the more necessary the fault data is for the fault diagnosis process, and the lower the relevance, the less necessary the fault data is for the fault diagnosis process. Exemplarily, the fault data with the highest relevance to the fault diagnosis process may be determined as primary fault data.
[0036] S120. Transmitting the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data when the primary fault data is all valid data.
[0037] The valid data is the data required to obtain the fault diagnosis result determined by the operation and maintenance terminal.
[0038] In this embodiment, the controller may send the first-level fault data to the cloud server, and the cloud server may send the received first-level fault data to the operation and maintenance terminal. Specifically, for different target fault types, the controller may use different sending methods to send the first-level fault data to the cloud server. Exemplarily, the fault types may be divided into three levels: high, medium and low, according to the degree of danger corresponding to the fault type. For example, a brake fault may be a high level, and a roof window fault may be a low level. When the target fault type is a high level, after obtaining the first-level fault data, the first-level fault data is directly sent to the cloud server; when the target fault type is a low level, the obtained first-level fault data may be sent to the cloud server according to a pre-set sending time period. For example, the pre-set sending time period may be a night time period.
[0039] Optionally, the first-level fault data is transmitted from the cloud server to the operation and maintenance terminal, including: sending the first-level fault data to the cloud server so that the cloud server generates fault prompt information and sends it to the operation and maintenance terminal, and when receiving a data acquisition request feedback from the operation and maintenance terminal, transmitting the first-level fault data to the operation and maintenance terminal.
[0040] In this embodiment, after obtaining the primary fault data, the primary fault data can be directly sent to the cloud server. In order to enable the operation and maintenance personnel to find the fault of the target vehicle in time, the cloud server can generate fault prompt information, and the fault prompt information can include the level corresponding to the target fault type. The cloud server sends the fault prompt information to the operation and maintenance terminal, so that the operation and maintenance terminal can find the fault of the target vehicle in time and understand the level of the fault, so as to reasonably arrange time to deal with the fault of the target vehicle.
[0041] Furthermore, after receiving the fault prompt information, if the operation and maintenance terminal starts the fault handling operation on the target vehicle, it generates a data acquisition request corresponding to the fault prompt information for obtaining the fault data of the target vehicle, and feeds back the data acquisition request to the cloud server. After receiving the data acquisition request, the cloud server sends the determined first-level fault data to the operation and maintenance terminal, so as to ensure that the first-level fault data can be provided when the operation and maintenance personnel need the fault data, and avoid sending the first-level fault data to the operation and maintenance terminal when the operation and maintenance personnel do not need it, which leads to the occupation of the storage space of the operation and maintenance terminal.
[0042] Before sending the first-level fault data to the operation and maintenance terminal, this embodiment first generates fault prompt information and sends it to the operation and maintenance terminal. When the operation and maintenance terminal allows, that is, when the data acquisition request is fed back to the cloud server, the first-level fault data is sent to the operation and maintenance terminal, so as to ensure that the first-level fault data can be provided when the operation and maintenance personnel need the fault data, and occupy as little storage space of the operation and maintenance terminal as possible.
[0043] In a specific implementation, after the operation and maintenance terminal obtains the primary fault data, the method for determining that the primary fault data is all valid data is: displaying the primary fault data, and in response to a data confirmation operation on the primary fault data, determining that the primary fault data is all valid data. In the case that the primary fault data is all valid data, a fault diagnosis result is determined based on the primary fault data. Among them, the fault diagnosis result is used to reflect the faulty components and the cause of the fault of the target vehicle. Exemplarily, the operation and maintenance terminal can determine the diagnosis result corresponding to the primary fault data as the fault diagnosis result of the target vehicle based on the mapping relationship between the pre-stored fault data and the diagnosis result. Alternatively, the operation and maintenance terminal responds to an input trigger operation on the fault diagnosis result and uses the acquired input information as the fault diagnosis result of the target vehicle.
[0044] Further, the method of determining that the primary fault data is not all valid data is: displaying the primary fault data, and in response to a trigger operation for obtaining the secondary fault data, determining that the primary fault data is not all valid data. The secondary fault data is the remaining fault data after removing the primary fault data generated when the target vehicle fails.
[0045] The technical solution of the embodiment of the present invention is to obtain the first-level fault data of the target vehicle when a fault is detected in the target vehicle; wherein the first-level fault data includes the target fault type and fault timestamp of the target vehicle; the first-level fault data is transmitted from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the first-level fault data when the first-level fault data is all valid data; wherein the valid data is the data required for obtaining the fault diagnosis result determined by the operation and maintenance terminal. This embodiment only transmits the target fault type and fault timestamp of the target vehicle to the cloud server, and then the cloud server transmits the target fault type and fault timestamp to the operation and maintenance terminal, thereby greatly reducing the amount of data transmitted and the transmission process is time-consuming; and when the first-level fault data is all valid data, the operation and maintenance terminal determines the fault diagnosis result based on the first-level fault data, thereby ensuring that accurate fault diagnosis results can be obtained, while improving the efficiency of determining the fault diagnosis result, and facilitating timely repair of the target vehicle.
[0046] Figure 2is a flowchart of another fault handling method provided according to an embodiment of the present invention. In this embodiment, after the primary fault data is transmitted from the cloud server to the operation and maintenance terminal, the secondary fault data of the target vehicle is determined, and the secondary fault data is transmitted to the operation and maintenance terminal to determine the fault diagnosis result. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here. Figure 2 As shown, the method includes:
[0047] S210: When a fault is detected in the target vehicle, primary fault data of the target vehicle is obtained.
[0048] S220. Transmitting the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data when the primary fault data is all valid data.
[0049] S230. Upon receiving a reverse query request from the operation and maintenance terminal, determine the secondary fault data of the target vehicle, and transmit the secondary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data and the secondary fault data.
[0050] The reverse query request is a request for obtaining fault data generated when the first-level fault data is not all valid data.
[0051] In this embodiment, the operation and maintenance terminal responds to the trigger operation of obtaining the secondary fault data, determines that the primary fault data is not all valid data, generates a reverse query request for obtaining the secondary fault data, and sends the reverse query request to the cloud server, which sends the reverse query request to the controller of the target vehicle. After receiving the reverse query request, the secondary fault data of the target vehicle is determined.
[0052] Optionally, the secondary fault data includes at least one of target key variable data, target bus information and vehicle data freeze frame of the target vehicle. Exemplarily, the target key variable data may include temperature data, humidity data and power data, etc. The target bus information is used to reflect the bus transmission information of the target vehicle; the vehicle data freeze frame is used to record the operating status of the target vehicle when a fault occurs.
[0053] In a specific implementation, after the controller of the target vehicle obtains the secondary fault data, it sends the secondary fault data to the cloud server, and the cloud server transmits the secondary fault data to the operation and maintenance terminal. The operation and maintenance terminal determines the fault diagnosis result of the target vehicle based on the received primary fault data and secondary fault data.
[0054] In this embodiment, the secondary fault data is obtained and transmitted to the operation and maintenance terminal only when a reverse query request is received, thereby avoiding sending the secondary fault data when the operation and maintenance terminal does not need the secondary fault data. This ensures that the fault diagnosis result of the target vehicle can be completed, while helping to reduce the workload of transmitting fault data.
[0055] In this embodiment, determining the secondary fault data of the target vehicle includes: obtaining a pre-constructed correspondence between the fault type of the target vehicle and the fault data to be obtained; based on the correspondence, determining the fault data to be obtained corresponding to the target fault type as the secondary fault data.
[0056] It should be noted that for different fault types, when determining the fault diagnosis result corresponding to the fault type, different fault data need to be obtained. In order to avoid the situation where the acquired fault data is not the data required for diagnosing the fault type, the corresponding relationship between the fault type and the fault data to be obtained can be pre-built. Among them, the fault data to be obtained is the fault data that needs to be known when diagnosing the fault of the fault type. Exemplarily, when the fault type is a battery fault, the fault data to be obtained corresponding to the fault type may include battery temperature, DC-DC converter working status, battery remaining power and battery humidity, etc.
[0057] In this embodiment, based on the pre-constructed correspondence between the fault type and the fault data to be obtained, the fault data to be obtained corresponding to the target fault type can be determined as the secondary fault data, the secondary fault data can be obtained, and the secondary fault data can be sent to the operation and maintenance terminal through the cloud server.
[0058] Optionally, the fault data to be obtained may be the key variable data to be obtained, and the method for determining the secondary fault data of the target vehicle may be: based on the pre-constructed correspondence between the fault type and the key variable data to be obtained, determine the key variable data to be obtained corresponding to the target fault type as the target key variable data, and obtain the target key variable data, target bus information and vehicle data freeze frame to form the secondary fault data.
[0059] In this embodiment, the target key variable data associated with the target fault type is determined through the pre-constructed correspondence, and the target key variable data, target bus data and vehicle data freeze frame constitute the secondary fault data, thereby ensuring the comprehensiveness of the secondary fault data; at the same time, since the data contained in the secondary fault data are all data associated with the target fault type, it is beneficial to reduce the transmission of unnecessary data and reduce the workload.
[0060] In this embodiment, the method also includes: when a fault is detected in the target vehicle, the current execution position of the log file of the target vehicle is used as the fault location, a flag is added to the fault location, and when a viewing request is received, the log file with the added flag is transmitted to the operation and maintenance terminal.
[0061] The log file (log file) records the working code of the target vehicle during operation. When a fault is detected in the target vehicle, the log file of the target vehicle can be obtained, and the current execution position of the working code in the log file is determined as the fault location, and a flag is added at the fault location.
[0062] It should be noted that when the operation and maintenance terminal receives the primary fault data and the secondary fault data, if the fault diagnosis result of the target vehicle still cannot be determined, or if it is necessary to determine the error in the working code in more detail, a viewing request can be sent to the controller of the target vehicle. After receiving the viewing request, the controller of the target vehicle transmits the log file with the flag bit added to the operation and maintenance terminal, so that the operation and maintenance personnel can perform mutual verification based on the fault timestamp in the primary fault data and the flag bit in the log file, so as to facilitate detailed analysis of the fault of the target vehicle.
[0063] Figure 3 1 is a schematic diagram of the structure of a fault handling device provided according to an embodiment of the present invention, and the device is used to execute the fault handling method provided in any of the above embodiments. The device and the fault handling method of the above embodiments belong to the same inventive concept, and the details not described in detail in the embodiments of the fault handling device can refer to the embodiments of the above fault handling method. Figure 3 As shown, the device comprises:
[0064] The primary fault data acquisition module 10 is used to acquire the primary fault data of the target vehicle when a fault is detected in the target vehicle; wherein the primary fault data includes the target fault type and fault timestamp of the target vehicle;
[0065] The data transmission module 11 is used to transmit the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal can determine the fault diagnosis result based on the primary fault data when the primary fault data is all valid data;
[0066] The valid data is the data required to obtain the fault diagnosis result determined by the operation and maintenance terminal.
[0067] Based on any optional technical solution in the embodiments of the present invention, optionally, the device further includes:
[0068] A secondary fault data transmission module is used to determine the secondary fault data of the target vehicle after the primary fault data is transmitted from the cloud server to the operation and maintenance terminal, upon receiving a reverse query request fed back by the operation and maintenance terminal, and transmit the secondary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data and the secondary fault data;
[0069] The reverse query request is a request for obtaining fault data generated when the first-level fault data is not all valid data.
[0070] Based on any optional technical solution in the embodiments of the present invention, optionally, the secondary fault data transmission module includes:
[0071] A corresponding relationship acquisition unit, used to acquire a corresponding relationship between a pre-built fault type of a target vehicle and the fault data to be acquired;
[0072] The secondary fault data determination unit is used to determine the to-be-acquired fault data corresponding to the target fault type as the secondary fault data based on the corresponding relationship.
[0073] Based on any optional technical solution in the embodiments of the present invention, optionally, the following further includes:
[0074] The flag adding module is used to take the current execution position of the log file of the target vehicle as the fault location when a fault is detected in the target vehicle, add a flag at the fault location, and transmit the log file with the added flag to the operation and maintenance terminal when a viewing request is received.
[0075] Based on any optional technical solution in the embodiment of the present invention, optionally, the data transmission module 11 includes:
[0076] The data transmission unit is used to send the first-level fault data to the cloud server so that the cloud server generates fault prompt information and sends it to the operation and maintenance terminal. When receiving the data acquisition request fed back by the operation and maintenance terminal, the first-level fault data is transmitted to the operation and maintenance terminal.
[0077] Based on any optional technical solution in the embodiments of the present invention, optionally, the secondary fault data includes at least one of target key variable data of the target vehicle, target bus information and vehicle data freeze frame.
[0078] The technical solution of the embodiment of the present invention is to obtain the first-level fault data of the target vehicle when a fault is detected in the target vehicle; wherein the first-level fault data includes the target fault type and fault timestamp of the target vehicle; the first-level fault data is transmitted from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the first-level fault data when the first-level fault data is all valid data; wherein the valid data is the data required for obtaining the fault diagnosis result determined by the operation and maintenance terminal. This embodiment only transmits the target fault type and fault timestamp of the target vehicle to the cloud server, and then the cloud server transmits the target fault type and fault timestamp to the operation and maintenance terminal, thereby greatly reducing the amount of data transmitted and the transmission process is time-consuming; and when the first-level fault data is all valid data, the operation and maintenance terminal determines the fault diagnosis result based on the first-level fault data, thereby ensuring that accurate fault diagnosis results can be obtained, while improving the efficiency of determining the fault diagnosis result, and facilitating timely repair of the target vehicle.
[0079] It is worth noting that in the embodiment of the above-mentioned fault handling device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.
[0080] Figure 4 1 is a schematic diagram of the structure of an electronic device that implements the fault handling method of an embodiment of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0081] like Figure 4As shown, the electronic device 20 includes at least one processor 21, and a memory connected to the at least one processor 21, such as a read-only memory (ROM) 22, a random access memory (RAM) 23, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 21 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 22 or the computer program loaded from the storage unit 28 to the random access memory (RAM) 23. In RAM23, various programs and data required for the operation of the electronic device 20 can also be stored. The processor 21, ROM22 and RAM23 are connected to each other through a bus 24. An input / output (I / O) interface 25 is also connected to the bus 24.
[0082] A number of components in the electronic device 20 are connected to the I / O interface 25, including: an input unit 26, such as a keyboard, a mouse, etc.; an output unit 27, such as various types of displays, speakers, etc.; a storage unit 28, such as a disk, an optical disk, etc.; and a communication unit 29, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 29 allows the electronic device 20 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0083] The processor 21 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 21 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 21 executes the various methods and processes described above, such as a fault handling method.
[0084] In some embodiments, the fault handling method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 28. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 20 via the ROM 22 and / or the communication unit 29. When the computer program is loaded into the RAM 23 and executed by the processor 21, one or more steps of the fault handling method described above may be performed. Alternatively, in other embodiments, the processor 21 may be configured to perform the fault handling method in any other appropriate manner (e.g., by means of firmware).
[0085] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0086] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0087] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0088] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0089] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0090] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0091] This embodiment also provides a computer program product, including a computer program, which, when executed by a processor, implements the fault handling method provided in any embodiment of the present application.
[0092] In the process of implementation, the computer program product can be written in one or more programming languages or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).
[0093] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.
[0094] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A fault handling method, characterized in that: include: When a fault is detected in a target vehicle, primary fault data of the target vehicle is obtained; wherein the primary fault data includes a target fault type and a fault timestamp of the target vehicle; Transmitting the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data when the primary fault data is all valid data; The valid data is the data required to obtain the fault diagnosis result determined by the operation and maintenance terminal.
2. The method according to claim 1, characterized in that After the first-level fault data is transmitted from the cloud server to the operation and maintenance terminal, the method further includes: Upon receiving the reverse query request fed back by the operation and maintenance terminal, determining the secondary fault data of the target vehicle, and transmitting the secondary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data and the secondary fault data; The reverse query request is a request for obtaining fault data generated when the first-level fault data is not all of the valid data.
3. The method according to claim 2, characterized in that The determining of the secondary fault data of the target vehicle includes: Acquire a pre-built correspondence between the fault type of the target vehicle and the fault data to be acquired; Based on the corresponding relationship, the to-be-acquired fault data corresponding to the target fault type is determined as the secondary fault data.
4. The method according to claim 1, characterized in that Also includes: When a fault is detected in the target vehicle, the current execution position of the log file of the target vehicle is used as the fault location, a flag is added at the fault location, and when a viewing request is received, the log file with the flag added is transmitted to the operation and maintenance terminal.
5. The method according to claim 1, characterized in that The transmitting the primary fault data from the cloud server to the operation and maintenance terminal includes: The first-level fault data is sent to the cloud server so that the cloud server generates fault prompt information and sends it to the operation and maintenance terminal. When a data acquisition request feedback from the operation and maintenance terminal is received, the first-level fault data is transmitted to the operation and maintenance terminal.
6. The method according to claim 3, characterized in that The secondary fault data includes at least one of target key variable data, target bus information, and vehicle data freeze frame of the target vehicle.
7. A fault handling device, characterized in that: include: A primary fault data acquisition module, used to acquire primary fault data of the target vehicle when a fault is detected in the target vehicle; wherein the primary fault data includes a target fault type and a fault timestamp of the target vehicle; A data transmission module, used for transmitting the primary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines the fault diagnosis result based on the primary fault data when the primary fault data is all valid data; The valid data is the data required to obtain the fault diagnosis result determined by the operation and maintenance terminal.
8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the fault handling method according to any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the fault handling method according to any one of claims 1 to 6 when executed.
10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the fault handling method according to any one of claims 1 to 6 is implemented.
Citation Information
Patent Citations
Automobile diagnosis method and apparatus
CN106248398A
Cloud based vehicle fault diagnosis method, device and system
CN108303264A
Vehicle fault diagnosis method and device, vehicle and storage medium
CN112650201A
Vehicle fault diagnosis method and device and vehicle
CN114815771A
Remote fault diagnosis method and device for vehicle, vehicle and computer storage medium
CN115016445A
