Light source fault processing method and device, electronic equipment and storage medium

Abstract

This application discloses a method, apparatus, electronic device, and storage medium for handling light source faults, belonging to the field of light source fault handling technology. The method includes: acquiring target operating data of a target light source device; generating a fault diagnosis result based on the target operating data using a fusion diagnostic model; and generating a repair plan based on the fault diagnosis result if the fault diagnosis result is verified. The light source fault handling method disclosed in this application aims to solve the problems of time-consuming and low success rates in light source repair.

Description

Technical Field

[0001] This application belongs to the field of light source fault handling technology, and particularly relates to a light source fault handling method, device, electronic device and storage medium. Background Technology

[0002] Laser-driven light sources, as core components of high-precision optoelectronic systems such as spectral analysis and precision measurement, are characterized by stable output power, high spectral purity, and fast response speed, and are widely used in scientific research, industrial testing, and medical fields. However, laser-driven light sources have complex structures, including optical components such as xenon lamps, lenses, and filters, electrical components such as drive circuits, and mechanical structural parts. During long-term use, they are prone to failure due to component aging, environmental interference, improper operation, and other factors, requiring timely maintenance.

[0003] Typically, the repair of laser-driven light sources relies heavily on the personal experience of senior technicians. The lack of standardized procedures for fault location and repair plan development leads to time-consuming repairs and a low success rate. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a method, apparatus, electronic device, and storage medium for handling light source faults, to solve the problems of time-consuming and low success rates in light source repair.

[0005] Firstly, this application provides a method for handling light source malfunctions, including: Acquire target operating data of the target light source device; Based on the fusion diagnostic model, fault diagnosis results are generated according to the target operating data; If the fault diagnosis results are verified, a maintenance plan is generated based on the fault diagnosis results.

[0006] According to the light source fault handling method of this application, target operating data of the target light source device is obtained; based on the fusion diagnostic model, fault diagnosis results are generated according to the target operating data; if the fault diagnosis results are verified, a maintenance plan is generated based on the fault diagnosis results. No manual experience is required. Based on the fusion diagnostic model, the fault diagnosis results of the target light source device are generated in a standardized manner, and a maintenance plan is further generated, which improves the speed of troubleshooting the cause of light source faults and improves the maintenance success rate.

[0007] According to one embodiment of this application, the fusion diagnostic model includes a fault feature library and a reliability assessment model; based on the fusion diagnostic model, fault diagnosis results are generated according to the target operating data, including: Based on the fault feature library, the predicted fault causes are determined according to the target operating data; the fault feature library includes several fault causes and the corresponding operating data for each fault cause, and the number of predicted fault causes is at least 2; The credibility of each predicted fault cause is evaluated based on the credibility assessment model, and a credibility score is obtained for each predicted fault cause. The fault diagnosis result is determined based on the confidence score of each estimated cause of the fault.

[0008] According to one embodiment of this application, a fault diagnosis result is determined based on the confidence score of each estimated fault cause, including: The predicted cause of failure with the highest confidence score among all predicted causes is determined as the failure diagnosis result.

[0009] According to one embodiment of this application, after generating fault diagnosis results based on the target operational data using a fusion diagnostic model, the method further includes: The fault diagnosis results are verified based on historical maintenance records; the historical maintenance records include several historical fault causes and the historical operating data corresponding to each historical fault cause.

[0010] According to one embodiment of this application, the verification of fault diagnosis results based on historical maintenance records includes: Identify the causes of historical faults in the maintenance records that are identical to the fault diagnosis results; Based on the similarity matching algorithm, the target similarity between the historical operating data corresponding to the historical fault causes and the target operating data is obtained; The verification result is determined based on the target similarity.

[0011] According to one embodiment of this application, if the fault diagnosis result is verified to be successful, a maintenance plan is generated based on the fault diagnosis result, including: If the fault diagnosis results are verified, search the fault repair solution library for the corresponding repair solution.

[0012] According to one embodiment of this application, after generating a maintenance plan based on the fault diagnosis results, if the fault diagnosis results are verified to be successful, the method further includes: Store the target operating data, fault diagnosis results, and maintenance plans in the historical maintenance archive.

[0013] Secondly, this application provides a light source fault handling device, comprising: The acquisition module is used to acquire the target operating data of the target light source device; The first generation module is used to generate fault diagnosis results based on the target operating data and the fusion diagnostic model. The second generation module is used to generate a maintenance plan based on the fault diagnosis results if the fault diagnosis results are verified.

[0014] According to the light source fault handling device of this application, the target operating data of the target light source equipment is obtained; based on the fusion diagnostic model, the fault diagnosis result is generated according to the target operating data; if the fault diagnosis result is verified, a maintenance plan is generated based on the fault diagnosis result. No human experience is required. Based on the fusion diagnostic model, the fault diagnosis result of the target light source equipment is generated in a standardized manner, and a maintenance plan is further generated, which improves the speed of troubleshooting the cause of light source faults and improves the maintenance success rate. Thirdly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the light source fault handling method described in the first aspect.

[0015] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the light source fault handling method described in the first aspect.

[0016] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the light source fault handling method described in the first aspect.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which: Figure 1 This is one of the flowcharts illustrating the light source fault handling method provided in the embodiments of this application; Figure 2 This is a second schematic flowchart of the light source fault handling method provided in the embodiments of this application; Figure 3 This is a schematic diagram of the structure of the light source fault handling device provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0020] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0021] The following description, in conjunction with the accompanying drawings, details the light source fault handling method, apparatus, electronic device, and storage medium provided in this application through specific embodiments and application scenarios.

[0022] Among them, the light source fault handling method can be applied to the terminal, and can be executed by the hardware or software in the terminal.

[0023] The terminal includes, but is not limited to, portable communication devices such as mobile phones or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that, in some embodiments, the terminal may not be a portable communication device, but rather a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0024] The following embodiments describe a terminal including a display and a touch-sensitive surface. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and joystick.

[0025] The light source fault handling method provided in this application embodiment can be executed by an electronic device or a functional module or entity in an electronic device that can implement the light source fault handling method. The electronic devices mentioned in this application embodiment include, but are not limited to, mobile phones, tablets, computers, cameras, and wearable devices. The light source fault handling method provided in this application embodiment will be described below using an electronic device as the execution subject.

[0026] like Figure 1 As shown, the light source fault handling method includes steps 110, 120 and 130.

[0027] Step 110: Obtain the target operating data of the target light source device.

[0028] In actual implementation, the target light source device can be a device that includes a laser-driven light source.

[0029] In some embodiments, the target operating data includes optical power, real-time current, real-time voltage, environmental parameters, and historical maintenance data. Environmental parameters include, but are not limited to, temperature and humidity.

[0030] In some embodiments, target operating data of the target light source device can be acquired when a fault is detected in the target light source device.

[0031] In some embodiments, a real-time image of the target light source can be acquired using an image acquisition device (e.g., a camera) of a mobile device to monitor for malfunctions in the target light source device. For example, if the real-time image indicates that the target light source device has no light output, a malfunction in the target light source device can be determined.

[0032] In some embodiments, optical power can be obtained based on a power sensor, real-time current can be obtained based on a current sensor, and real-time voltage can be obtained based on a voltage sensor.

[0033] Step 120: Based on the fusion diagnostic model, generate fault diagnosis results according to the target operating data.

[0034] In practice, the fusion diagnostic model can be used to determine the fault diagnosis results of the target light source equipment based on the target's operational data.

[0035] In some embodiments, the fusion diagnostic model can determine the preliminary cause of failure of the target light source device based on the target operating data, and then screen the preliminary cause of failure to determine the fault diagnosis result.

[0036] In some embodiments, after generating the fault diagnosis results, the generated fault diagnosis results can be verified to obtain the verification results.

[0037] Step 130: If the fault diagnosis results are verified, generate a maintenance plan based on the fault diagnosis results.

[0038] In some embodiments, if the fault diagnosis result is verified, the corresponding repair solution can be found in a pre-stored fault repair solution library.

[0039] In practice, the repair plan includes repair steps, required components, repair tools, operating procedures, and expected repair results.

[0040] In some embodiments, after a maintenance plan is generated, the target operating data, fault diagnosis results, and maintenance plan can be stored.

[0041] According to the light source fault handling method of this application embodiment, target operating data of the target light source device is obtained; based on the fusion diagnostic model, fault diagnosis results are generated according to the target operating data; if the fault diagnosis results are verified, a maintenance plan is generated based on the fault diagnosis results. No manual experience is required. Based on the fusion diagnostic model, the fault diagnosis results of the target light source device are generated in a standardized manner, and a maintenance plan is further generated, which improves the speed of troubleshooting the cause of light source faults and improves the maintenance success rate.

[0042] In some embodiments, the fusion diagnostic model includes a fault feature library and a reliability assessment model; based on the fault feature library, the predicted fault causes are determined according to the target operating data; the fault feature library includes several fault causes and the operating data corresponding to each fault cause, and the number of predicted fault causes is at least 2; based on the reliability assessment model, the reliability of each predicted fault cause is assessed to obtain a reliability score for each predicted fault cause; based on the reliability score of each predicted fault cause, the fault diagnosis result is determined.

[0043] In actual implementation, the fault feature database can be a two-dimensional data table or any theoretically feasible form; this application does not impose specific restrictions on it. The fault feature database includes fault causes such as optical faults (e.g., xenon lamp aging, filter contamination, etc.), electrical faults (e.g., drive circuit faults, etc.), and mechanical faults (e.g., lens displacement, loose housing, etc.), as well as the corresponding operating data for each fault cause.

[0044] In some embodiments, after acquiring the target operating data, the optical power, real-time current, real-time voltage, and environmental parameters in the target operating data can be compared one by one with the operating data corresponding to each fault cause in the fault feature database. If the optical power, real-time current, real-time voltage, and environmental parameters in the target operating data are the same as those in the operating data in the fault feature database, the fault cause corresponding to that operating data is determined as the estimated fault cause. For example, based on the comparison with the contents recorded in the fault feature database, the estimated fault causes corresponding to an optical power of 0mW and abnormal real-time current include drive circuit failure, power module failure, and laser diode burnout.

[0045] In practice, the credibility assessment model can be based on a neural network algorithm.

[0046] In some embodiments, after obtaining multiple estimated fault causes, a credibility assessment can be performed on each estimated fault cause based on a credibility assessment model to obtain a credibility score for each estimated fault cause. For example, based on the credibility assessment model, the credibility score for "drive circuit failure" is determined to be 90%, the credibility score for "power module failure" is 8%, and the credibility score for "laser diode burnout" is 2%.

[0047] In some embodiments, the predicted fault cause with the highest confidence score among all predicted fault causes can be determined as the fault diagnosis result.

[0048] According to the light source fault handling method of this application embodiment, the following steps are taken: First, target operating data of the target light source device is acquired. Second, based on a fault feature library, the estimated fault cause is determined according to the target operating data. The fault feature library includes several fault causes and corresponding operating data for each fault cause, with at least two estimated fault causes. Third, a credibility assessment is performed on each estimated fault cause using a credibility evaluation model to obtain a credibility score for each estimated fault cause. Fourth, a fault diagnosis result is determined based on the credibility score of each estimated fault cause. Fifth, if the fault diagnosis result is verified, a maintenance plan is generated based on the fault diagnosis result. This method eliminates the need for manual experience, standardizes the generation of fault diagnosis results for the target light source device based on a fusion diagnosis model, and further generates a maintenance plan, thereby improving the speed of troubleshooting light source faults and increasing the maintenance success rate.

[0049] In some embodiments, after generating fault diagnosis results based on the target operating data using the fusion diagnostic model, the fault diagnosis results can be verified based on historical maintenance records; the historical maintenance records include several historical fault causes and historical operating data corresponding to each historical fault cause.

[0050] In practice, the historical fault causes and the corresponding historical operating data in the historical maintenance records can come from the same light source equipment or from different light source equipment.

[0051] In some embodiments, the historical fault causes that are the same as the fault diagnosis results can be found in the historical maintenance records, and the fault diagnosis results can be verified based on the historical operating data corresponding to the historical fault causes to obtain the verification results.

[0052] According to the light source fault handling method of this application embodiment, the target operating data of the target light source device is obtained; based on the fusion diagnostic model, a fault diagnosis result is generated according to the target operating data; the fault diagnosis result is verified based on historical maintenance records; if the fault diagnosis result is verified, a maintenance plan is generated based on the fault diagnosis result. Without the need for manual experience, the fault diagnosis result of the target light source device is generated in a standardized manner based on the fusion diagnostic model, and a maintenance plan is further generated, which improves the speed of troubleshooting the cause of light source faults and improves the maintenance success rate.

[0053] In some embodiments, the historical fault causes that are the same as the fault diagnosis results in the historical maintenance records are identified; and the target similarity between the historical operating data corresponding to the historical fault causes and the target operating data is obtained based on a similarity matching algorithm. The verification result is determined based on the target similarity.

[0054] In actual implementation, the similarity matching algorithm can be any theoretically feasible similarity algorithm, such as the cosine similarity algorithm. This application does not make any specific restrictions on it.

[0055] In some embodiments, a similarity score can be obtained between historical operating data corresponding to historical fault causes and target operating data based on a similarity matching algorithm, and the similarity score can be used as the target similarity between historical operating data corresponding to historical fault causes and fault diagnosis results.

[0056] In some embodiments, the fault diagnosis result can be deemed verified if the target similarity is greater than or equal to a similarity threshold. The similarity threshold can be a preset value, such as 60%.

[0057] In some embodiments, if the fault diagnosis result is verified, a repair solution corresponding to the fault diagnosis result is searched in the fault repair solution library.

[0058] In actual implementation, the fault repair solution library can include several historical fault causes and the corresponding historical repair solutions for each historical fault cause.

[0059] In some embodiments, if the fault diagnosis result is verified, a historical fault cause identical to the fault diagnosis result can be searched in the fault repair solution library, and the historical repair solution corresponding to that historical fault cause can be identified as the repair solution corresponding to the fault diagnosis result. For example, the repair solution may include the following: ① Repair steps (power off → disassemble the casing → check the drive circuit → re-plug the interface → tighten the interface screws → power-on test); ② Repair tools (Phillips screwdriver, multimeter); ③ Requirements (no need to replace parts, if the interface is damaged, the drive circuit interface needs to be adapted); ④ Operating procedures (handle the interface gently when plugging and unplugging, and tighten the screws with a pre-tightening force of 0.5N). m); ⑤ Safety precautions (Wait 5 minutes after power off before operating to avoid static electricity damaging components).

[0060] According to the light source fault handling method of this application embodiment, target operating data of the target light source device is obtained; based on the fusion diagnostic model, fault diagnosis results are generated according to the target operating data; if the fault diagnosis results are verified, a repair plan corresponding to the fault diagnosis results is searched in the fault repair plan library. Without human experience, the fault diagnosis results of the target light source device are generated in a standardized manner based on the fusion diagnostic model, and a repair plan is further generated, which improves the speed of troubleshooting the cause of light source faults and improves the repair success rate.

[0061] In some embodiments, after the fault diagnosis results are verified and a maintenance plan is generated based on the fault diagnosis results, the target operating data, fault diagnosis results, and maintenance plan can be stored in the historical maintenance archive.

[0062] In practice, historical maintenance records can be stored on a cloud server.

[0063] To better understand the light source fault handling method provided in the embodiments of this application, further explanation is provided below. It should be understood that the following discussion is merely exemplary.

[0064] This application provides a method for handling light source malfunctions, and the specific steps are as follows: Figure 2 As shown: Step 210: Obtain the target operation data of the target light source device.

[0065] In actual implementation, the target light source device can be a device that includes a laser-driven light source.

[0066] In some embodiments, the target operating data includes optical power, real-time current, real-time voltage, environmental parameters, and historical maintenance data. Environmental parameters include, but are not limited to, temperature and humidity.

[0067] In some embodiments, target operating data of the target light source device can be acquired when a fault is detected in the target light source device.

[0068] In some embodiments, a real-time image of the target light source can be acquired using an image acquisition device (e.g., a camera) of a mobile device to monitor for malfunctions in the target light source device. For example, if the real-time image indicates that the target light source device has no light output, a malfunction in the target light source device can be determined.

[0069] In some embodiments, optical power can be obtained based on a power sensor, real-time current can be obtained based on a current sensor, and real-time voltage can be obtained based on a voltage sensor.

[0070] Step 220: Based on the fault feature library, determine the estimated fault causes according to the target operating data; the fault feature library includes several fault causes and the operating data corresponding to each fault cause, and the number of estimated fault causes is at least 2; perform a credibility assessment on each estimated fault cause based on the credibility assessment model, and obtain the credibility score of each estimated fault cause; determine the fault diagnosis result based on the credibility score of each estimated fault cause.

[0071] In actual implementation, the fault feature database can be a two-dimensional data table or any theoretically feasible form; this application does not impose specific restrictions on it. The fault feature database includes fault causes such as optical faults (e.g., xenon lamp aging, filter contamination, etc.), electrical faults (e.g., drive circuit faults, etc.), and mechanical faults (e.g., lens displacement, loose housing, etc.), as well as the corresponding operating data for each fault cause.

[0072] In some embodiments, after acquiring the target operating data, the optical power, real-time current, real-time voltage, and environmental parameters in the target operating data can be compared one by one with the operating data corresponding to each fault cause in the fault feature database. If the optical power, real-time current, real-time voltage, and environmental parameters in the target operating data are the same as those in the operating data in the fault feature database, the fault cause corresponding to that operating data is determined as the estimated fault cause. For example, based on the comparison with the contents recorded in the fault feature database, the estimated fault causes corresponding to an optical power of 0mW and abnormal real-time current include drive circuit failure, power module failure, and laser diode burnout.

[0073] In practice, the credibility assessment model can be based on a neural network algorithm.

[0074] In some embodiments, after obtaining multiple estimated fault causes, a credibility assessment can be performed on each estimated fault cause based on a credibility assessment model to obtain a credibility score for each estimated fault cause. For example, based on the credibility assessment model, the credibility score for "drive circuit failure" is determined to be 90%, the credibility score for "power module failure" is 8%, and the credibility score for "laser diode burnout" is 2%.

[0075] In some embodiments, the predicted fault cause with the highest confidence score among all predicted fault causes can be determined as the fault diagnosis result.

[0076] Step 230: Verify the fault diagnosis results based on historical maintenance records; historical maintenance records include several historical fault causes and historical operating data corresponding to each historical fault cause.

[0077] In practice, the historical fault causes and the corresponding historical operating data in the historical maintenance records can come from the same light source equipment or from different light source equipment.

[0078] In some embodiments, the historical fault causes that are the same as the fault diagnosis results can be found in the historical maintenance records, and the fault diagnosis results can be verified based on the historical operating data corresponding to the historical fault causes to obtain the verification results.

[0079] In some embodiments, the historical fault causes that are the same as the fault diagnosis results in the historical maintenance records are identified; and the target similarity between the historical operating data corresponding to the historical fault causes and the target operating data is obtained based on a similarity matching algorithm. The verification result is determined based on the target similarity.

[0080] In actual implementation, the similarity matching algorithm can be any theoretically feasible similarity algorithm, such as the cosine similarity algorithm. This application does not make any specific restrictions on it.

[0081] In some embodiments, a similarity score can be obtained between historical operating data corresponding to historical fault causes and target operating data based on a similarity matching algorithm, and the similarity score can be used as the target similarity between historical operating data corresponding to historical fault causes and fault diagnosis results.

[0082] In some embodiments, the fault diagnosis result can be deemed verified if the target similarity is greater than or equal to a similarity threshold. The similarity threshold can be a preset value, such as 60%.

[0083] Step 240: If the fault diagnosis result is verified, search for the corresponding repair solution in the fault repair solution library.

[0084] In actual implementation, the fault repair solution library can include several historical fault causes and the corresponding historical repair solutions for each historical fault cause.

[0085] In some embodiments, if the fault diagnosis result is verified, a historical fault cause identical to the fault diagnosis result can be searched in the fault repair solution library, and the historical repair solution corresponding to that historical fault cause can be identified as the repair solution corresponding to the fault diagnosis result. For example, the repair solution may include the following: ① Repair steps (power off → disassemble the casing → check the drive circuit → re-plug the interface → tighten the interface screws → power-on test); ② Repair tools (Phillips screwdriver, multimeter); ③ Requirements (no need to replace parts, if the interface is damaged, the drive circuit interface needs to be adapted); ④ Operating procedures (handle the interface gently when plugging and unplugging, and tighten the screws with a pre-tightening force of 0.5N). m); ⑤ Safety precautions (Wait 5 minutes after power off before operating to avoid static electricity damaging components).

[0086] Step 250: Store the target operating data, fault diagnosis results, and maintenance plan in the historical maintenance archive.

[0087] In practice, historical maintenance records can be stored on a cloud server.

[0088] This application also provides a light source fault handling device.

[0089] like Figure 3 As shown, the light source fault handling device 300 includes: an acquisition module 310, a first generation module 320, and a second generation module 330.

[0090] The acquisition module 310 is used to acquire the target operation data of the target light source device; The first generation module 320 is used to generate fault diagnosis results based on the target operating data and the fusion diagnostic model. The second generation module 330 is used to generate a maintenance plan based on the fault diagnosis results if the fault diagnosis results are verified.

[0091] According to the light source fault handling device of this application embodiment, first motion monitoring data and second motion monitoring data for a target area are acquired; the first motion monitoring data is data acquired based on the integrated radar-visual device, and the second motion monitoring data is data acquired by the visual monitoring device; based on the global coordinate system of the target area, a projection operation is performed on the first motion monitoring data and the second motion monitoring data to generate a target motion trajectory, so as to project the first motion monitoring data acquired by the integrated radar-visual device and the second motion monitoring data acquired by the visual monitoring device onto the pre-set global coordinate system of the target area, thereby obtaining a continuous and complete motion trajectory of each moving target detected in the multiple first motion monitoring data and second motion monitoring data in the target area.

[0092] In some embodiments, the fusion diagnostic model includes a fault feature library and a reliability assessment model; the first generation module 320 includes: The first determining unit is used to determine the estimated cause of failure based on the fault feature library and the target operating data; the fault feature library includes several fault causes and the operating data corresponding to each fault cause, and the number of estimated fault causes is at least 2; The first acquisition unit is used to perform a credibility assessment on each predicted fault cause based on the credibility assessment model, and to obtain a credibility score for each predicted fault cause. The second determining unit is used to determine the fault diagnosis result based on the confidence score of each estimated fault cause.

[0093] In some embodiments, the second determining unit is used for: The predicted cause of failure with the highest confidence score among all predicted causes is determined as the failure diagnosis result.

[0094] In some embodiments, the light source fault handling device 300 further includes: The verification module is used to verify the fault diagnosis results based on historical maintenance records; the historical maintenance records include several historical fault causes and the historical operating data corresponding to each historical fault cause.

[0095] In some embodiments, the verification module includes: The third determining unit is used to determine the cause of historical faults that are the same as the fault diagnosis results in the historical maintenance records; The second acquisition unit is used to acquire the target similarity between historical operating data corresponding to historical fault causes and target operating data based on a similarity matching algorithm. The fourth determining unit is used to determine the verification result based on the target similarity.

[0096] In some embodiments, the second generation module 330 includes: The search unit is used to search for the corresponding repair solution in the fault repair solution library if the fault diagnosis result is verified.

[0097] In some embodiments, the light source fault handling device 300 further includes: The storage module is used to store target operating data, fault diagnosis results, and maintenance plans into historical maintenance files.

[0098] The light source fault handling device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0099] The light source fault handling device in this application embodiment can be a device with an operating system. This operating system can be a Microsoft (Windows) operating system, an Android operating system, an iOS operating system, or other possible operating systems; this application embodiment does not specifically limit it.

[0100] The light source fault handling device 300 provided in this application embodiment can achieve... Figures 1 to 2 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0101] In some embodiments, such as Figure 4 As shown, this application embodiment also provides an electronic device 400, including a processor 401, a memory 402, and a computer program stored in the memory 402 and executable on the processor 401. When the program is executed by the processor 401, it implements the various processes of the above-described light source fault handling method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0102] It should be noted that the computer equipment in this application embodiment includes the mobile electronic equipment and non-mobile electronic equipment described above.

[0103] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described light source fault handling method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0104] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0105] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described light source fault handling method.

[0106] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0107] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described light source fault handling method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0108] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0109] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0111] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0112] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0113] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A method for handling light source malfunctions, characterized in that, include: Acquire target operating data of the target light source device; Based on the fusion diagnostic model, fault diagnosis results are generated according to the target operating data; If the fault diagnosis results are verified, a maintenance plan is generated based on the fault diagnosis results.

2. The light source fault handling method according to claim 1, characterized in that, The fusion diagnostic model includes a fault feature library and a reliability assessment model; the generation of fault diagnosis results based on the fusion diagnostic model and the target operational data includes: Based on the fault feature library, the estimated fault causes are determined according to the target operating data; the fault feature library includes several fault causes and operating data corresponding to each fault cause, and the number of estimated fault causes is at least 2; The credibility of each of the predicted fault causes is evaluated based on the credibility assessment model, and a credibility score is obtained for each of the predicted fault causes. The fault diagnosis result is determined based on the confidence score of each of the predicted causes of the fault.

3. The light source fault handling method according to claim 2, characterized in that, The determination of the fault diagnosis result based on the confidence score for each of the estimated causes of the fault includes: The predicted fault cause with the highest confidence score among all the predicted fault causes is determined as the fault diagnosis result.

4. The light source fault handling method according to claim 1, characterized in that, After generating fault diagnosis results based on the target operational data using the fusion diagnostic model, the method further includes: The fault diagnosis results are verified based on historical maintenance records; the historical maintenance records include several historical fault causes and historical operating data corresponding to each historical fault cause.

5. The light source fault handling method according to claim 4, characterized in that, Based on historical maintenance records, the fault diagnosis results are verified, including: Identify the cause of the historical fault in the historical maintenance file that is identical to the fault diagnosis result; Based on a similarity matching algorithm, the target similarity between the historical operating data corresponding to the historical fault cause and the target operating data is obtained; The verification result is determined based on the target similarity.

6. The light source fault handling method according to claim 1, characterized in that, If the fault diagnosis result is verified, the step of generating a maintenance plan based on the fault diagnosis result includes: If the fault diagnosis result is verified, the corresponding repair solution in the fault repair solution library is searched.

7. The light source fault handling method according to claim 1, characterized in that, If the fault diagnosis result is verified to be successful, after generating a maintenance plan based on the fault diagnosis result, the method further includes: The target operating data, the fault diagnosis results, and the maintenance plan are stored in the historical maintenance archive.

8. A light source fault handling device, characterized in that, include: The acquisition module is used to acquire the target operating data of the target light source device; The first generation module is used to generate fault diagnosis results based on the target operating data according to the fusion diagnostic model; The second generation module is used to generate a maintenance plan based on the fault diagnosis results if the fault diagnosis results are verified to be successful.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the light source fault handling method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the light source failure handling method according to any one of claims 1-7.

Images