A fault processing method and device, electronic equipment, storage medium and product

Abstract

Embodiments of the present application disclose a fault processing method and device, electronic equipment, storage medium and product. The method comprises: in the case of detecting that a target vehicle has a fault, obtaining first-level fault data of the target vehicle; wherein the first-level fault data comprises a target fault type and a fault timestamp of the target vehicle; transmitting the first-level fault data from a cloud server to an operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first-level fault data in the case that the first-level fault data is all valid data; wherein the valid data is data required by the operation and maintenance terminal to determine the fault diagnosis result. The technical scheme of the embodiments of the present application can ensure that an accurate fault diagnosis result can be obtained, improve the efficiency of determining the fault diagnosis result, and facilitate timely maintenance of the target vehicle.

Description

Technical Field

[0001] The present invention relates to the field of vehicle control technology, and in particular to a fault handling method, device, electronic device, storage medium and product. Background Technology

[0002] To improve vehicle safety, it is necessary to inspect the vehicle's operating status, diagnose any faults, and carry out timely and effective repairs.

[0003] In existing technologies, after a vehicle malfunctions, vehicle operating information is obtained through data embedding and uploaded to a cloud server. This information is then sent to the maintenance terminal by the cloud server, facilitating maintenance personnel to handle the malfunction and repair the vehicle.

[0004] However, in the process of realizing this invention, it was found that the prior art has at least the following technical problems: In practical applications, the fault scenarios are complex and the number of embedded points is constantly increasing, resulting in an increase in the amount of embedded point data. Uploading all the embedded point data to the cloud server takes a long time, and the operation and maintenance terminal cannot obtain the uploaded embedded point data in a timely manner, which affects the repair efficiency of vehicle faults. Summary of the Invention

[0005] This invention provides a fault handling method, apparatus, electronic device, storage medium, and product to improve the efficiency of determining fault diagnosis results and facilitate timely repair of the target vehicle.

[0006] According to one aspect of the present invention, a fault handling method is provided, comprising:

[0007] If a fault is detected in the target vehicle, the first-level fault data of the target vehicle is acquired; wherein, the first-level fault data includes the target fault type and fault timestamp of the target vehicle;

[0008] The Level 1 fault data is transmitted 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 Level 1 fault data if all the Level 1 fault data is valid.

[0009] The valid data refers to the data determined by the operation and maintenance terminal that is required to obtain the fault diagnosis result.

[0010] According to another aspect of the present invention, a fault handling apparatus is provided, the apparatus comprising:

[0011] The Level 1 Fault Data Acquisition Module is used to acquire Level 1 fault data of the target vehicle when a fault is detected in the target vehicle; wherein, the Level 1 fault data includes the target fault type and fault timestamp of the target vehicle;

[0012] a data transmission module configured to transmit the first fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first fault data when the first fault data is all valid data.

[0013] The valid data is data required by the operation and maintenance terminal to obtain the fault diagnosis result.

[0014] According to another aspect of the present application, an electronic device is provided, which comprises:

[0015] at least one processor; and

[0016] a memory in communication connection with 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 to enable the at least one processor to execute the fault processing method according to any one of the embodiments of the present application.

[0018] According to another aspect of the present application, a computer readable storage medium is provided, which stores computer instructions for enabling a processor to implement the fault processing method according to any one of the embodiments of the present application when executed by the processor.

[0019] According to another aspect of the present application, a computer program product is provided, which comprises a computer program for implementing the fault processing method according to any one of the embodiments of the present application when executed by a processor.

[0020] The technical scheme of the embodiment of the present application, in the case of detecting that the target vehicle has a fault, acquires first fault data of the target vehicle; wherein the first fault data comprises a target fault type and a fault timestamp of the target vehicle; transmits the first fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first fault data when the first fault data is all valid data; wherein the valid data is data required by the operation and maintenance terminal to obtain the fault diagnosis result. This embodiment only transmits the target fault type and the fault timestamp of the target vehicle to the cloud server, and then transmits the target fault type and the fault timestamp to the operation and maintenance terminal by the cloud server, thereby greatly reducing the amount of data transmitted and shortening the time consumed in the transmission process; and in the case that the first fault data is all valid data, the operation and maintenance terminal determines a fault diagnosis result based on the first fault data, thereby ensuring that an accurate fault diagnosis result can be obtained, improving the efficiency of determining the fault diagnosis result, and facilitating timely maintenance of the target vehicle.

[0021] It is to be understood that the details set forth herein do not limit the scope of the embodiments of the application to the specific embodiments described. Rather, the scope of the embodiments of the application is to be defined by the appended claims. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiments description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0023] Figure 1 is a flow chart of a fault processing method according to an embodiment of the present application;

[0024] Figure 2 is a flow chart of another fault processing method according to an embodiment of the present application;

[0025] Figure 3 is a structural schematic diagram of a fault processing device according to an embodiment of the present application;

[0026] Figure 4 is a structural schematic diagram of an electronic device implementing a fault processing method according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the technical personnel in the art better understand the present application scheme, the following will combine the drawings in the embodiments of the present application, and the technical solutions in the embodiments of the present application will be described clearly and completely. Obviously, the described embodiments are only a part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should belong to the scope of protection of the present application.

[0028] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "etc." and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily limit to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0029] It should be noted that in the technical solutions of the present disclosure, the collection, collection, updating, analysis, processing, use, transmission, storage, etc. of user personal information are in line with relevant laws and regulations, are used for legal purposes, and do not violate public order and good customs. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain user personal information security and network security.

[0030] Figure 1 A flowchart of a fault processing method according to an embodiment of the present application is shown. The embodiment can be applicable to the case of determining a fault diagnosis result for a fault occurring in a target vehicle. The method can be executed by a fault processing device, which can be implemented in the form of hardware and / or software.

[0031] As shown in Figure 1 , the method of the embodiment can specifically include:

[0032] S110, in the case of detecting that a fault occurs in a target vehicle, obtaining first-level fault data of the target vehicle.

[0033] The first-level fault data includes the target fault type and the fault timestamp of the target vehicle. For example, the target fault type can be represented by a fault code that occurs when the target vehicle fails.

[0034] In the embodiment, the controller of the target vehicle can be used to determine whether a fault occurs in the target vehicle. Specifically, the controller can detect each component of the target vehicle at regular intervals or in real time to determine whether a fault exists in the target vehicle. 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 communication between each component inside the target vehicle and the domain controller.

[0035] Specifically, in the case of detecting that a fault exists in the target vehicle, in order to diagnose and locate the existing fault, first-level fault data of the target vehicle can be obtained. It should be noted that the fault data can be divided into different levels according to its relevance 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. For example, the fault data with the highest relevance to the fault diagnosis process can be determined as first-level fault data.

[0036] S120, transmitting the first-level fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first-level fault data in the case that the first-level fault data is all valid data.

[0037] The effective data is data determined by the operation and maintenance terminal and required for obtaining a fault diagnosis result.

[0038] In this embodiment, the controller can send the first fault data to the cloud server, and the cloud server can send the received first fault data to the operation and maintenance terminal. Specifically, for different target fault types, the controller can use different sending methods to send the first fault data to the cloud server. For example, according to the risk degree corresponding to the fault type, the fault type can be divided into three levels: high, medium and low. For example, the brake fault can be a high level, and the sunroof fault can be a low level. When the target fault type is a high level, the first fault data is directly sent to the cloud server after the first fault data is obtained; when the target fault type is a low level, the obtained first fault data can be sent to the cloud server according to a pre-set sending time period. For example, the pre-set sending time period can be a night time period.

[0039] Optionally, the cloud server transmits the first fault data to the operation and maintenance terminal, including: sending the first 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 in the case that the operation and maintenance terminal feeds back a data acquisition request, transmitting the first fault data to the operation and maintenance terminal.

[0040] In this embodiment, after the first fault data is obtained, the first fault data can be directly sent to the cloud server. In order to enable the operation and maintenance personnel to discover the fault condition of the target vehicle in time, the cloud server can generate fault prompt information, and the target fault type corresponding to the level can be included in the fault prompt information. The cloud server sends the fault prompt information to the operation and maintenance terminal, so that the operation and maintenance terminal can discover the fault of the target vehicle in time and understand the level of the fault, so as to reasonably arrange the time to process the fault condition of the target vehicle.

[0041] Further, after receiving the fault prompt information, if the operation and maintenance terminal starts the fault processing operation of the target vehicle, a data acquisition request for acquiring the fault data of the target vehicle corresponding to the fault prompt information is generated, and the data acquisition request is fed back to the cloud server. After receiving the data acquisition request, the cloud server sends the determined first fault data to the operation and maintenance terminal, so as to ensure that the first fault data can be provided when the operation and maintenance personnel need the fault data, and avoid occupying the storage space of the operation and maintenance terminal when the operation and maintenance personnel do not need the first fault data.

[0042] The embodiment generates the fault prompt information and sends it to the operation and maintenance terminal before sending the first-level fault data to the operation and maintenance terminal. In the case that 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 the storage space of the operation and maintenance terminal is occupied as little as possible.

[0043] In a specific implementation, after the operation and maintenance terminal acquires the first-level fault data, the manner of determining that the first-level fault data is all valid data is as follows: the first-level fault data is displayed, and in response to a data confirmation operation on the first-level fault data, it is determined that the first-level fault data is all valid data. In the case that the first-level fault data is all valid data, the fault diagnosis result is determined based on the first-level fault data. The fault diagnosis result is used to reflect the component of the target vehicle that appears a fault and the fault reason. For example, the operation and maintenance terminal can determine the diagnosis result corresponding to the first-level fault data as the fault diagnosis result of the target vehicle based on a mapping relationship between the pre-stored fault data and the diagnosis result. Alternatively, the operation and maintenance terminal acquires input information as the fault diagnosis result of the target vehicle in response to an input trigger operation on the fault diagnosis result.

[0044] Further, the manner of determining that the first-level fault data is not all valid data is as follows: the first-level fault data is displayed, and in response to an acquisition trigger operation on the second-level fault data, it is determined that the first-level fault data is not all valid data. The second-level fault data is the remaining fault data of the target vehicle after the first-level fault data is removed.

[0045] The technical scheme of the embodiment of the application comprises the following steps: in the case that a fault of a target vehicle is detected, first-level fault data of the target vehicle is acquired; the first-level fault data comprises a target fault type and a fault timestamp of the target vehicle; the first-level fault data is transmitted from a cloud server to an operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first-level fault data in the case that the first-level fault data is all valid data; the valid data is data required by the operation and maintenance terminal to determine the fault diagnosis result. In the embodiment, only the target fault type and the fault timestamp of the target vehicle are transmitted to the cloud server, and then the target fault type and the fault timestamp are transmitted from the cloud server to the operation and maintenance terminal, so that the amount of data transmitted is greatly reduced, and the time consumed in the transmission process is short. In the case that 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, so as to ensure that an accurate fault diagnosis result can be obtained, improve the efficiency of determining the fault diagnosis result, and facilitate timely maintenance of the target vehicle.

[0046] Figure 2is a flowchart of another fault processing method according to an embodiment of the present application. After the first fault data is transmitted from the cloud server to the operation and maintenance terminal, the second fault data of the target vehicle is determined, and the second fault data is transmitted to the operation and maintenance terminal to determine the fault diagnosis result. Wherein, the same or corresponding terms as in the above embodiments are not repeated here. As shown in Figure 2 The method comprises:

[0047] S210, in the case of detecting that the target vehicle has a fault, obtaining first fault data of the target vehicle.

[0048] S220, transmitting the first 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 first fault data in the case that the first fault data is all valid data.

[0049] S230, in the case of receiving the feedback of the operation and maintenance terminal, determining the second fault data of the target vehicle, transmitting the second 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 first fault data and the second fault data.

[0050] Wherein, the second fault data is generated in the case that the first fault data is not all valid data.

[0051] In this embodiment, the operation and maintenance terminal generates a second fault data request in response to the operation of obtaining the second fault data, and sends the second fault data request to the cloud server, and the cloud server sends the second fault data request to the controller of the target vehicle. After receiving the second fault data request, the second fault data of the target vehicle is determined.

[0052] Optionally, the second fault data comprises at least one of target key variable data, target bus information and vehicle data freeze frame of the target vehicle. For example, the target key variable data can include temperature data, humidity data and power data, etc. The target bus information is used to reflect the information transmitted by the bus of the target vehicle; the vehicle data freeze frame is used to record the running state of the target vehicle when the target vehicle has a fault.

[0053] In specific implementation, after the controller of the target vehicle obtains the second fault data, the second fault data is transmitted to the cloud server, and the cloud server transmits the second fault data to the operation and maintenance terminal, and the operation and maintenance terminal determines the fault diagnosis result of the target vehicle based on the received first fault data and second fault data.

[0054] The embodiment obtains the secondary fault data and transmits the secondary fault data to the operation and maintenance terminal only when the reverse query request is received, so that the secondary fault data is not transmitted when the operation and maintenance terminal does not need the secondary fault data, and the workload of transmitting the fault data is reduced while ensuring that the fault diagnosis result of the target vehicle is completed.

[0055] In the embodiment, the secondary fault data of the target vehicle is determined by obtaining a correspondence relationship between a fault type of the target vehicle and to-be-acquired fault data, and determining, based on the correspondence relationship, the to-be-acquired fault data corresponding to the target fault type as the secondary fault data.

[0056] It should be noted that for different fault types, different fault data needs to be acquired when the fault diagnosis result of the fault type is determined. In order to avoid the acquired fault data not being the data required for diagnosing the fault type, the correspondence relationship between the fault type and the to-be-acquired fault data can be constructed in advance. The to-be-acquired fault data is the fault data required for diagnosing the fault type. For example, when the fault type is a battery fault, the to-be-acquired fault data corresponding to the fault type can include battery temperature, direct current-direct current converter working state, battery remaining capacity, and battery humidity.

[0057] In the embodiment, the to-be-acquired fault data corresponding to the target fault type can be determined as the secondary fault data based on the pre-constructed correspondence relationship between the fault type and the to-be-acquired fault data, the secondary fault data is acquired, and the secondary fault data is transmitted to the operation and maintenance terminal through the cloud server.

[0058] Optionally, the to-be-acquired fault data can be to-be-acquired key variable data, and the secondary fault data of the target vehicle can be determined by determining, based on a pre-constructed correspondence relationship between the fault type and the to-be-acquired key variable data, the to-be-acquired key variable data corresponding to the target fault type as target key variable data, acquiring the target key variable data, target bus information, and vehicle data frozen frame, and forming the secondary fault data.

[0059] In the embodiment, the target key variable data associated with the target fault type is determined based on the pre-constructed correspondence relationship, and the secondary fault data is formed by the target key variable data, target bus data, and vehicle data frozen frame, so that the comprehensiveness of the secondary fault data is ensured. In addition, since the data included in the secondary fault data is all data associated with the target fault type, transmission of unnecessary data is reduced, and the workload is reduced.

[0060] In the embodiment, the method further comprises: when the target vehicle is detected to have a fault, taking a current execution position of a log file of the target vehicle as a fault occurrence position, adding a flag bit at the fault occurrence position, and when the viewing request is received, transmitting the log file with the added flag bit to the operation and maintenance terminal.

[0061] The log file records a working running code in a working process of the target vehicle. When the target vehicle is detected to have a fault, the log file of the target vehicle is acquired, and a current execution position of the working running code in the log file is determined as a fault occurrence position. A flag bit is added at the fault occurrence position.

[0062] It should be noted that, in the case that the operation and maintenance terminal receives the first fault data and the second 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 running code in more detail, a viewing request can be sent to the controller of the target vehicle. After the controller of the target vehicle receives the viewing request, the log file with the added flag bit is transmitted to the operation and maintenance terminal, so that the operation and maintenance personnel can verify each other according to the fault time stamp in the first fault data and the flag bit in the log file, and analyze the fault of the target vehicle in detail.

[0063] Figure 3 FIG. 1 is a structural schematic diagram of a fault processing device according to an embodiment of the present application. The device is used to execute the fault processing method provided in any of the above embodiments. The device and the fault processing method of each of the above embodiments belong to the same inventive concept. Details not described in the embodiment of the fault processing device can be referred to the embodiment of the fault processing method. As shown in FIG. 1, the device comprises: Figure 3

[0064] The first fault data acquisition module 10 is configured to acquire first fault data of the target vehicle when the target vehicle is detected to have a fault. The first fault data comprises a target fault type and a fault time stamp of the target vehicle.

[0065] The data transmission module 11 is configured to transmit the first fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first fault data when the first fault data is all valid data.

[0066] The valid data is data required by the operation and maintenance terminal to determine the fault diagnosis result.

[0067] On the basis of any optional technical solution in the embodiments of the present application, optionally, the device further comprises:

[0068] ​The secondary fault data transmission module is configured to, after the primary fault data is transmitted from the cloud server to the operation and maintenance terminal, determine secondary fault data of the target vehicle in a case where a reverse query request fed back by the operation and maintenance terminal is received, and transmit the secondary fault data from the cloud server to the operation and maintenance terminal, so that the operation and maintenance terminal determines a 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 in a case where the primary fault data is not all valid data.

[0070] In any optional technical solution in the embodiments of the present application, optionally, the secondary fault data transmission module comprises:

[0071] The corresponding relationship acquisition unit is configured to acquire a corresponding relationship between a fault type of the target vehicle and the to-be-acquired fault data, which is constructed in advance.

[0072] The secondary fault data determination unit is configured to determine, based on the corresponding relationship, the to-be-acquired fault data corresponding to the target fault type as the secondary fault data.

[0073] In any optional technical solution in the embodiments of the present application, optionally, the method further comprises:

[0074] The flag bit adding module is configured to, when detecting that the target vehicle has a fault, take a current execution position of a log file of the target vehicle as a fault occurrence position, add a flag bit at the fault occurrence position, and transmit the log file with the added flag bit to the operation and maintenance terminal when receiving the query request.

[0075] In any optional technical solution in the embodiments of the present application, optionally, the data transmission module 11 comprises:

[0076] The data transmission unit is configured to send the primary fault data to the cloud server, so that the cloud server generates fault prompt information and sends the fault prompt information to the operation and maintenance terminal, and in a case where a data acquisition request fed back by the operation and maintenance terminal is received, transmit the primary fault data to the operation and maintenance terminal.

[0077] In any optional technical solution in the embodiments of the present application, optionally, the secondary fault data comprises at least one of target key variable data, target bus information and vehicle data frozen frames of the target vehicle.

[0078] The technical scheme of the embodiment of the present application, in the case of detecting that the target vehicle has a fault, acquires first fault data of the target vehicle; wherein the first fault data includes a target fault type and a fault timestamp of the target vehicle; the first fault data is transmitted from a cloud server to an operation and maintenance terminal, so that the operation and maintenance terminal determines a fault diagnosis result based on the first fault data in the case that the first fault data is all valid data; wherein the valid data is the data required by the operation and maintenance terminal to determine the fault diagnosis result. This embodiment only transmits the target fault type and the fault timestamp of the target vehicle to the cloud server, and then transmits the target fault type and the fault timestamp to the operation and maintenance terminal by the cloud server, thereby greatly reducing the amount of data transmission and shortening the time consumption in the transmission process; and in the case that the first fault data is all valid data, the operation and maintenance terminal determines the fault diagnosis result based on the first fault data, thereby ensuring that an accurate fault diagnosis result can be obtained, improving the efficiency of determining the fault diagnosis result, and facilitating timely maintenance of the target vehicle.

[0079] It is worth noting that in the above embodiment of the fault processing device, each unit and module included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding function can be realized; in addition, the specific name of each functional unit is only for the convenience of mutual differentiation, and does not limit the protection scope of the present application.

[0080] Figure 4 FIG. 1 is a structural schematic diagram of an electronic device for implementing the fault processing method according to the embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown in the figure, their connections and relationships, and their functions are merely examples, and are not intended to limit the implementation of the present application described and / or claimed herein.

[0081] As Figure 4As shown, the electronic device 20 includes at least one processor 21, and a memory, such as a read-only memory (ROM) 22, a random access memory (RAM) 23, etc., connected to the at least one processor 21 in communication. The memory stores computer programs executable by the at least one processor 21, and the processor 21 can perform various appropriate actions and processes according to the computer programs stored in the read-only memory (ROM) 22 or loaded from the storage unit 28 into the random access memory (RAM) 23. In the RAM 23, various programs and data required for the operation of the electronic device 20 can also be stored. The processor 21, the ROM 22, and the RAM 23 are connected to each other through a bus 24. An input / output (I / O) interface 25 is also connected to the bus 24.

[0082] Various 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, a speaker, etc., a storage unit 28, such as a magnetic 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 can be various general and / or special-purpose processing components having 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-purpose 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 performs various methods and processes described above, such as the fault handling method.

[0084] In some embodiments, the fault handling method can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 28. In some embodiments, part or all of the computer program can be loaded and / or installed onto 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 can be performed. Alternatively, in other embodiments, the processor 21 can be configured to perform the fault handling method by any other appropriate means, such as by means of firmware.

[0085] The various embodiments of the systems and techniques described above can be implemented in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a load programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0086] Computer programs used to implement the processes of the application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer program, when executed, can cause instructions defined in the flow charts and / or block diagrams to be implemented. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine as a standalone software package and partially on a remote machine or entirely on a remote machine or server.

[0087] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store computer programs for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable storage media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0088] To provide for interaction with a user, the systems and techniques described here can 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 a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0089] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can 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), blockchain network, and the Internet.

[0090] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. A server can 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 large management difficulty and weak business scalability in traditional physical host and VPS service.

[0091] The embodiments also provide a computer program product, comprising a computer program which, when executed by a processor, implements the fault processing method as provided by any of the embodiments of the present application.

[0092] The computer program code can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce the computer implemented process such that the

[0093] It should be understood that the various forms of flow shown in the figures are illustrative examples of implementing the steps of the application. Several of the steps have been expanded to show the various constituent database, application, and process steps used to implement the examples. Other steps have been simplified to more clearly and concisely illustrate main points. The ordering of steps is not essential. For example, some steps can be performed in an order different from that shown or can be performed concurrently. Further, in some instances, less than all the benefits of a particular step can be achieved and still be within the scope and spirit of the application. One of ordinary skill in the art will appreciate the various functions performed by the various units and elements of the figures and the executive, database, and communication steps in the claims as being equivalent to corresponding functions in other blocks and steps. For the sake of brevity and clarity, only the most significant, novel, and non- obvious aspects of the application are described.

[0094] The detailed description contained herein does not limit the scope of the application. One skilled in the art will recognize that the application can be practiced with modification and alteration, and that the application should be limited only by the scope of the appended claims. Furthermore, the disclosure is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the best practices of the application. The disclosure is not intended to be exhaustive or to show all possible forms of the application. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can be practiced with the application as disclosed herein.

Claims

1. A fault handling method, characterized in that, include: When a fault is detected in a target vehicle, the acquisition time of the first-level fault data is determined based on the severity level of the fault, and the first-level fault data of the target vehicle is acquired at the acquisition time; 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 can determine the fault diagnosis result based on the first-level fault data if all the first-level fault data is valid. The valid data refers to the data determined by the operation and maintenance terminal that is required to obtain the fault diagnosis result; After transmitting the Level 1 fault data from the cloud server to the operation and maintenance terminal, the method further includes: Upon receiving a reverse lookup request from the maintenance terminal, the system obtains the pre-built correspondence between the fault types of the target vehicle and the fault data to be acquired. Based on the correspondence, the fault data to be acquired corresponding to the target fault type is determined as secondary fault data. The secondary fault data is transmitted 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 and the secondary fault data. The reverse lookup request is a request for acquiring fault data generated when the primary fault data is not all of the valid data. The secondary fault data is the remaining fault data after removing the primary fault data when the target vehicle malfunctions, including at least one of the target vehicle's target key variable data, target bus information, and vehicle data freeze frame. When a fault is detected in the target vehicle, the current execution position of the target vehicle's log file is taken as the fault location, a flag is added to 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.

2. The method according to claim 1, characterized in that, The process of transmitting the Level 1 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 a fault prompt message and sends it to the operation and maintenance terminal. Upon receiving a data acquisition request from the operation and maintenance terminal, the first-level fault data is transmitted to the operation and maintenance terminal.

3. A fault handling device, characterized in that, include: The Level 1 Fault Data Acquisition Module is used to determine the acquisition time of Level 1 Fault Data based on the hazard level of the fault when a fault is detected in a target vehicle, and acquire the Level 1 Fault Data of the target vehicle at the acquisition time; wherein, the Level 1 Fault Data includes the target fault type and fault timestamp of the target vehicle. The data transmission module is used to transmit the first-level 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 first-level fault data if all the first-level fault data is valid. The valid data refers to the data determined by the operation and maintenance terminal that is required to obtain the fault diagnosis result; The device further includes: The secondary fault data transmission module is used to determine the secondary fault data of the target vehicle after receiving a reverse lookup request from the maintenance terminal after the primary fault data has been transmitted from the cloud server to the maintenance terminal, and then transmit the secondary fault data from the cloud server to the maintenance terminal so that the maintenance terminal can determine the fault diagnosis result based on the primary fault data and the secondary fault data. Wherein, the reverse lookup request is a request generated to obtain fault data when the first-level fault data is not all of the valid data, and the second-level fault data is the remaining fault data after removing the first-level fault data when the target vehicle malfunctions, including at least one of the target vehicle's target key variable data, target bus information, and vehicle data freeze frame. The secondary fault data transmission module includes: The correspondence acquisition unit is used to acquire the pre-constructed correspondence between the fault types of the target vehicle and the fault data to be acquired; The secondary fault data determination unit is used to determine, based on the correspondence, the fault data to be acquired corresponding to the target fault type as the secondary fault data; The flag addition module is used to add a flag at the current execution position of the target vehicle's log file as the fault location when a fault is detected in the target vehicle, and transmit the log file with the added flag to the operation and maintenance terminal when a viewing request is received.

4. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the fault handling method according to any one of claims 1-2.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the fault handling method according to any one of claims 1-2.

6. A computer program product comprising a computer program that, when executed by a processor, implements the fault handling method according to any one of claims 1-2.

Images