Data processing method and apparatus, device, and storage medium
By dynamically loading device diagnostic rules and matching them with visual rule components and device operating parameters, the problem of insufficient flexibility in device diagnostics in existing technologies is solved, thereby improving the flexibility and accuracy of device diagnostics.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHENZHEN TCL NEW-TECH CO LTD
- Filing Date
- 2026-03-13
- Publication Date
- 2026-07-03
AI Technical Summary
Existing equipment diagnostic methods embed diagnostic rules in a hard-coded manner, resulting in poor flexibility and an inability to quickly adapt to changes in equipment operating status or new fault types.
The system assembles and loads diagnostic rules using a visual rule component, and performs real-time matching and diagnosis using device operating parameters and target diagnostic rules. It supports the dynamic adjustment and loading of diagnostic rules without stopping device operation.
It improves the flexibility and accuracy of equipment diagnostics, enabling real-time monitoring and rapid response to equipment operating status.
Smart Images

Figure CN122331979A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and more specifically to a data processing method, apparatus, device, and storage medium. Background Technology
[0002] Currently, with the rapid development of modern industrial production and technologies such as the Internet of Things (IoT), an increasing number of equipment clusters (such as production equipment clusters and IoT device combinations) require real-time monitoring and intelligent diagnostics during production operations to ensure the continuity of equipment production or operation and improve processing efficiency. However, existing equipment diagnostic methods embed diagnostic rules into programs using hard-coding. When it is necessary to adjust the rules to adapt to changes in equipment operating status or new fault types, it is necessary to stop the equipment operation to recompile and deploy the program. This results in poor equipment diagnostic flexibility and an inability to quickly adapt to changes in equipment operating status or new fault types. Summary of the Invention
[0003] This application provides a data processing method, apparatus, device, and storage medium, aiming to solve the technical problem of poor diagnostic flexibility in existing equipment monitoring and intelligent diagnosis.
[0004] On one hand, embodiments of this application provide a data processing method, which includes the following steps: Respond to device diagnostic requests and obtain the device operating parameters of the corresponding target device; Based on the device operating parameters and the loaded diagnostic rules, rule matching is performed to obtain the target diagnostic rule. The loaded diagnostic rule is a device diagnostic rule that is dynamically loaded after being assembled by a visual rule component. The target device is diagnosed using the target diagnostic rules and the device operating parameters to obtain the device diagnostic results.
[0005] In one possible implementation of this application, before performing rule matching based on the device operating parameters and the loaded diagnostic rules to obtain the target diagnostic rule, the method further includes: Display the visual rules component in the preset display interface; In response to component interaction events for any one or more visual rule components, determine the target rule component associated with the component interaction event in the visual rule components; Based on the component interaction events and the target rule component, load diagnostic rules are generated.
[0006] In one possible implementation of this application, the step of generating loading diagnostic rules based on the component interaction events and the target rule component includes: The target rule components are combined according to the component interaction events to obtain the initial diagnostic rules; The initial diagnostic rules are syntax-validated using a preset rule expression to obtain the rule validation result; The initial diagnostic rule whose rule verification result is the first verification result is input into the preset rule database for loading, thereby obtaining the loaded diagnostic rule.
[0007] In one possible implementation of this application, the step of performing rule matching based on the device operating parameters and loading diagnostic rules to obtain the target diagnostic rule includes: Obtain dynamically loaded diagnostic rules from the preset rule database and determine the rule parameter fields corresponding to each of the loaded diagnostic rules; The target diagnostic rule is obtained by matching the device operating parameters and the rule parameter fields.
[0008] In one possible implementation of this application, the step of performing rule matching based on the device operating parameters and the rule parameter field to obtain the target diagnostic rule includes: The operating parameters of the equipment are converted to obtain the converted equipment parameters; The conversion device parameters and the rule parameter fields are matched to obtain the parameter matching result; The loading diagnostic rule corresponding to the rule parameter field whose parameter matching result is the first matching result is determined as the target diagnostic rule.
[0009] In one possible implementation of this application, the step of performing device diagnosis on the target device using the target diagnostic rules and the device operating parameters to obtain the device diagnosis result includes: The target diagnostic rules are parsed using a rule parser to obtain the target execution code; The target device is diagnosed using the target execution code and the device operating parameters to obtain the device diagnosis results.
[0010] In one possible implementation of this application, the device diagnostic result includes a first diagnostic result and a second diagnostic result; the first diagnostic result is a device diagnostic result indicating that the target device is operating abnormally; the second diagnostic result is a device diagnostic result indicating that the target device is operating normally. The step of performing device diagnosis on the target device using the target executable code and the device operating parameters to obtain device diagnosis results includes: The target execution code is used to run the conversion device parameters corresponding to the device operating parameters to obtain the code execution result; If the code execution result satisfies the fault diagnosis condition corresponding to the target diagnosis rule, then the first diagnosis result is output; If the code execution result does not meet the fault diagnosis conditions corresponding to the target diagnosis rule, then the second diagnosis result is output.
[0011] On the other hand, this application provides a data processing apparatus, the data processing apparatus comprising: The information acquisition module is configured to respond to device diagnostic requests and acquire the device operating parameters of the corresponding target device. The rule matching module is configured to perform rule matching based on the device operating parameters and loaded diagnostic rules to obtain target diagnostic rules. The loaded diagnostic rules are device diagnostic rules that are dynamically loaded after being assembled by a visual rule component. The data processing module is configured to perform device diagnosis on the target device using the target diagnosis rules and the device operating parameters, and obtain device diagnosis results.
[0012] On the other hand, this application also provides a data processing device, the data processing device comprising: One or more processors; Memory; and One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps of the data processing method.
[0013] On the other hand, this application also provides a computer-readable storage medium having a computer program stored thereon, the computer program being loaded by a processor to perform the steps in the data processing method.
[0014] This application obtains the operating parameters of the target device in response to a device diagnostic request; performs rule matching based on the operating parameters and loaded diagnostic rules to obtain target diagnostic rules, which are dynamically loaded device diagnostic rules assembled by a visual rule component; and performs device diagnostics on the target device using the target diagnostic rules and the operating parameters to obtain device diagnostic results. This achieves real-time acquisition of the operating parameters of the target device to be diagnosed, and matches these parameters with dynamically loaded diagnostic rules to obtain the target diagnostic rules associated with the operating parameters. Furthermore, it enables dynamic adjustment (e.g., modification and addition) of diagnostic rules during the diagnostic process, and their dynamic loading and matching with the operating parameters improves the flexibility and accuracy of device diagnostics. Attached Figure Description
[0015] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0016] Figure 1 This is a schematic diagram illustrating a scenario of the data processing method in an embodiment of this application. Figure 2 This is a flowchart illustrating one embodiment of the data processing method in this application. Figure 3a A schematic diagram of a scenario of one embodiment of a visualization rule component in the data processing method provided in this application; Figure 3b This is a schematic diagram illustrating a scenario of loading diagnostic rules in the data processing method provided in this application. Figure 4 A flowchart illustrating an embodiment of the data processing method for generating loading diagnostic rules provided in this application; Figure 5 A schematic diagram of the structure of one embodiment of the data processing apparatus provided in this application; Figure 6 This is a schematic diagram of the structure of one embodiment of the data processing device provided in this application. Detailed Implementation
[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0018] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.
[0019] In this application, the term "exemplary" is used to mean "serving as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.
[0020] Currently, with the rapid development of modern industrial production and technologies such as the Internet of Things (IoT), an increasing number of equipment clusters (such as production equipment clusters and IoT device combinations) require real-time monitoring and intelligent diagnostics during production operations to ensure the continuity of equipment production or operation and improve processing efficiency. However, existing equipment diagnostic methods embed diagnostic rules into programs using hard-coding. When it is necessary to adjust the rules to adapt to changes in equipment operating status or new fault types, it is necessary to stop the equipment operation to recompile and deploy the program. This results in poor equipment diagnostic flexibility and an inability to quickly adapt to changes in equipment operating status or new fault types.
[0021] Based on this, this application proposes a data processing method, apparatus, device, and computer-readable storage medium to solve the technical problem of poor diagnostic flexibility in the prior art when performing equipment monitoring and intelligent diagnosis.
[0022] The data processing method in this embodiment of the invention is applied to a data processing device, which is disposed in a data processing equipment. The data processing equipment is provided with one or more processors, a memory, and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the data processing method. The data processing equipment can be a smart terminal, such as a mobile phone, tablet computer, network device, and smart computer. Optionally, the data processing equipment can also be a server or a service cluster composed of multiple servers.
[0023] like Figure 1 As shown, Figure 1 This is a schematic diagram of a data processing method according to an embodiment of the present application. The data processing scenario in this embodiment includes a data processing device 100 (which integrates a data processing unit) and a target device 200. The data processing device 100 has a computer-readable storage medium corresponding to the data processing method running to execute the steps of the data processing method. The target device 200 is an operating device that is communicatively connected to the data processing device 100 for device diagnostics.
[0024] Understandable Figure 1 The data processing device in the data processing method scenario shown, or the device included in the data processing device, does not constitute a limitation on the embodiments of the present invention. That is, the number or type of data processing device in the data processing method scenario, or the number or type of device included in each device, does not affect the overall implementation of the technical solution in the embodiments of the present invention, and can all be considered as equivalent substitutions or derivatives of the technical solutions claimed in the embodiments of the present invention.
[0025] In this embodiment of the invention, the data processing device 100 is mainly used to: respond to device diagnostic requests and obtain the device operating parameters of the corresponding target device; Based on the device operating parameters and the loaded diagnostic rules, rule matching is performed to obtain the target diagnostic rule. The loaded diagnostic rule is a device diagnostic rule that is dynamically loaded after being assembled by a visual rule component. The target device is diagnosed using the target diagnostic rules and the device operating parameters to obtain the device diagnostic results.
[0026] The data processing device 100 in this embodiment of the invention can be an independent data processing device, such as a mobile phone, tablet computer, network device, server and smart computer, or a data processing network or data processing cluster composed of multiple data processing devices.
[0027] This application provides a data processing method, apparatus, device, and computer-readable storage medium, which will be described in detail below.
[0028] It will be understood by those skilled in the art that Figure 1 The application environment shown is only one application scenario related to the solution of this application and does not constitute a limitation on the application scenario of this application. Other application environments may include more than one application scenario. Figure 1 The number of data processing devices shown, or the data processing network connections, for example Figure 1 Only one data processing device is shown in the figure. It is understood that the scenario of this data processing method may also include one or more data processing devices, which are not specifically limited here. The data processing device 100 may also include a memory for storing device operating parameters and other data.
[0029] It should be noted that, Figure 1 The schematic diagram of the data processing method shown is merely an example. The scenarios of the data processing method described in the embodiments of the present invention are intended to more clearly illustrate the technical solutions of the embodiments of the present invention and do not constitute a limitation on the technical solutions provided in the embodiments of the present invention.
[0030] Based on the scenarios described above, various embodiments of the data processing method disclosed in this invention are proposed.
[0031] like Figure 2 As shown, Figure 2 This is a flowchart illustrating one embodiment of the data processing method in this application. The data processing method includes the following steps 201 to 203: 201. Respond to the device diagnostic request and obtain the device operating parameters of the corresponding target device; The data processing method in this embodiment is applied to a data processing device. The type and number of data processing devices are not specifically limited. That is, the data processing device can be one or more intelligent terminals or servers used for real-time monitoring and device diagnosis of at least one or more target devices. In a specific embodiment, the data processing device is an intelligent computer.
[0032] Optionally, the target device refers to a smart terminal that is communicating with the data processing device and is currently running. Optionally, the target device can be any one or more of industrial production equipment, IoT devices, and other smart devices. The data processing device can perform real-time monitoring and intelligent diagnostics on the target device to promptly detect operational anomalies and then perform timely repairs, thereby ensuring operational continuity and improving production efficiency. Optionally, real-time monitoring of the target device refers to the process by which the data processing device collects the target device's operating parameters intermittently or periodically during the communication connection with the target device. Device diagnostics of the target device refers to the process by which the data processing device uses the target device's operating parameters and dynamically loaded diagnostic rules within the data processing device to determine whether the target device is operating normally.
[0033] Optionally, a device diagnostic request is a request event that drives the data processing device to collect device operating parameters and perform device diagnostics on a specified target device. Optionally, the triggering method for this device diagnostic request is not specifically limited here; that is, the device diagnostic request can be actively triggered by the user. For example, the user can click the device diagnostic button on the corresponding settings page of the data processing device to actively trigger a device diagnostic request for the target device. Furthermore, the device diagnostic request can also be automatically triggered by the data processing device. For example, if a timed diagnostic process is set up in the device processing device, the device diagnostic request can be triggered periodically using the timed diagnostic process.
[0034] Optionally, equipment operating parameters refer to multi-dimensional index parameters reflecting the operating status of the target equipment during operation and / or production. Optionally, in one specific embodiment, equipment operating parameters can be expressed as different index parameters depending on the different equipment types and / or operating types of the target equipment. For example, equipment operating parameters can be any one or more of multi-dimensional parameter indicators such as temperature, pressure, operating mode, and rotational speed. Optionally, in other embodiments, the equipment operating parameters can also be other IoT device operating parameters not listed here, or other equipment operating parameters; this embodiment does not specifically limit them.
[0035] Optionally, after receiving a device diagnostic request, the data processing device also collects the device operating parameters of the target device corresponding to the diagnostic request. That is, the data processing device parses the diagnostic request, obtains the device identifier carried in the request, identifies the operating device corresponding to the device identifier as the target device, and obtains the device operating parameters reported by the target device through a message middleware. During operation, the target device can collect specified device operating parameters through sensors and transmit these parameters to the message middleware via a message transmission protocol. The message middleware then transmits the parameters to the data stream processing platform of the data processing device, which in turn sends them to the device diagnostic framework module for processing. Optionally, in one specific embodiment, the sensor can be a sensor component corresponding to the device operating parameters, such as one or more sensors including a temperature sensor, a pressure sensor, and a speed sensor. The message middleware is a middleware component used to receive the device operating parameters reported by the target device and upload them to the data processing device. Optionally, in one specific embodiment, the message middleware can be an EMQ (Erlang MQTT Broker) middleware or other middleware. The message transmission protocol can be MQTT (Message Queuing Telemetry Transport).
[0036] 202. Based on the device operating parameters and loading diagnostic rules, perform rule matching to obtain the target diagnostic rule; Optionally, after obtaining the device operating parameters of the target device, the data processing device also performs rule matching based on the device operating parameters and the loaded diagnostic rules to obtain the target diagnostic rules for the target device to be diagnosed.
[0037] Optionally, the loaded diagnostic rules are dynamically loaded device diagnostic rules assembled from visual rule components, used to perform device diagnostics on a specified target device. That is, the data processing device pre-displays at least one or more visual rule components in a preset display interface on the front end, and responds to user interaction events with any one or more visual components. The visual rule component selected by the interaction event is identified as the target rule component associated with that interaction event. The target rule components are then combined and loaded through the corresponding interactive operation of that interaction event, resulting in loaded diagnostic rules used to detect the operating parameters of the specified device to achieve device diagnostics.
[0038] Optionally, the visual rule component is a visual component displayed on a preset display interface, containing partial rule information and capable of being combined with other visual rule components. This partial rule information includes runtime parameter fields, parameter values, and diagnostic condition fields used to compose diagnostic rules. Optionally, in a specific embodiment, the visual rule component is a blockly component carrying partial or complete rule information such as runtime parameter fields, parameter values, and diagnostic condition fields.
[0039] Optional, such as Figure 3a As shown, Figure 3a This is a schematic diagram of a scenario representing one embodiment of a visualization rule component in the data processing method provided in this application. Figure 3a In the illustrated embodiment, the visualization rule component includes a working mode component, an outlet water temperature component, a duration component, a parameter value component, an AND condition component, a ≥ diagnostic condition, a = diagnostic condition, parameter value 4, and parameter value 30, etc.
[0040] Optionally, the component interaction event is an interaction event used to combine selected visual rule components into a complete diagnostic rule. Optionally, in a specific embodiment, the component interaction event is an operation event in which the user combines any visual rule component through interactive methods such as dragging and combining.
[0041] Optionally, in one specific embodiment, after the data processing device generates loading diagnostic rules through component interaction events and target rule components, it stores the loading diagnostic rules in a preset rule database and dynamically loads the loading diagnostic rules. This enables dynamic configuration operations such as adding, modifying, deleting, and querying diagnostic rules in real time without restarting the operating system, thereby improving the flexibility of device diagnostics. Optionally, in one specific embodiment, the preset rule database is a MongoDB database. Figure 3b As shown, Figure 3b This is a schematic diagram illustrating a scenario of loading diagnostic rules in the data processing method provided in this application. For example... Figure 3b As shown, Figure 3b The document demonstrates a specific example of a load diagnostic rule generated by the target rule component. This load diagnostic rule specifies that the average outlet water temperature of the device in heating mode over 30 seconds must be greater than or equal to 30 degrees Celsius.
[0042] Optionally, after responding to the device diagnostic request and obtaining the device operating parameters of the target device, the data processing device also performs rule matching based on the device operating parameters and the loaded diagnostic rules to obtain the target diagnostic rules used to perform device diagnostics on the device operating parameters.
[0043] Optionally, the target diagnostic rule is a diagnostic rule related to the equipment operating parameters, used to perform equipment diagnosis on the target equipment using the equipment operating parameters.
[0044] Optionally, the data processing device accesses a preset rule database, obtains dynamically loaded diagnostic rules from the database, and determines the rule parameter fields corresponding to each diagnostic rule. That is, the data processing device parses each diagnostic rule to obtain the rule parameter fields contained within it. These rule parameter fields are the parameter fields corresponding to the operating parameters to be diagnosed in the diagnostic rule. Optionally, in a specific embodiment, these rule parameter fields can be parameter fields representing any device operating parameter, such as operating mode fields, outlet water temperature fields, operating pressure fields, and operating speed fields.
[0045] Optionally, after obtaining the rule parameter fields of each loaded diagnostic rule, the data processing device also performs rule matching based on the device's operating parameters and the rule parameter fields to obtain the target diagnostic rule. That is, the data processing device matches the obtained device operating parameters with the rule parameter fields, thereby identifying the loaded diagnostic rule whose rule parameter fields are the same as the device operating parameters as the target diagnostic rule.
[0046] Optionally, after reading the device operating parameters through the data stream transmission framework corresponding to the preset data processing framework, the data processing device further performs data transformation on the device operating parameters to obtain transformed device parameters that conform to the data processing framework. That is, the data processing device converts the device operating parameters into a data structure within the data processing framework to obtain the transformed device parameters. Optionally, in a specific embodiment, the data processing framework is the FLink framework, and the data stream transmission framework is the Kafka Connector framework.
[0047] Optionally, after obtaining the conversion device parameters, the data processing device performs parameter matching between the conversion device parameters and the rule parameter field to obtain a parameter matching result. This parameter matching result indicates whether the corresponding operating parameters of the conversion device parameters and the rule parameter field are the same. Specifically, the parameter matching result includes a first matching result indicating that the corresponding operating parameters of the conversion device parameters and the rule parameter field are the same, and a second matching result indicating that the corresponding operating parameters of the conversion device parameters and the rule parameter field are different.
[0048] Optionally, if the data processing device determines that the parameter matching result is the first matching result, that is, the running parameters corresponding to the conversion device parameters and the rule parameter fields are the same, then the loading diagnostic rule corresponding to the rule parameter field where the parameter matching result is the first matching result is determined as the target diagnostic rule.
[0049] 203. Perform equipment diagnosis on the target equipment using the target diagnosis rules and the equipment operating parameters to obtain equipment diagnosis results.
[0050] Optionally, after determining the target diagnostic rules, the data processing device also performs device diagnostics on the target device using the target diagnostic rules and device operating parameters to obtain device diagnostic results. That is, the data processing framework in the data processing device periodically pulls the target diagnostic rules from the preset rule database, parses the target diagnostic rules and / or other diagnostic rules through the rule parser, and dynamically loads them into the device diagnostic task, generating corresponding device diagnostic results using the target diagnostic rules and device operating parameters.
[0051] Optionally, after acquiring the target diagnostic rule, the data processing device reads the target execution code corresponding to the target diagnostic rule, and uses the target execution code and the device's operating parameters to perform device diagnosis on the target device, obtaining a device diagnostic result. That is, the data processing device uses a rule parser to parse the target diagnostic rule, obtains the target execution code, and uses the target execution code to run the device's operating parameters to perform device diagnosis, obtaining a device diagnostic result corresponding to the device's operating parameters. This device diagnostic result is a diagnostic result indicating whether the target device is operating normally. The device diagnostic result includes a first diagnostic result and a second diagnostic result; the first diagnostic result indicates that the target device is operating abnormally; the second diagnostic result indicates that the target device is operating normally.
[0052] That is, the data processing device uses the target execution code to run the transformation device parameters corresponding to the device's operating parameters, and obtains the code execution result. The code execution result is the calculation result obtained by the data processing device executing the target execution code.
[0053] Optionally, if the code execution result meets the fault diagnosis condition corresponding to the target diagnostic rule, a first diagnostic result is output. This fault diagnosis condition is a condition for determining whether the operating parameters of the target device are normal. For example, in a specific embodiment, the fault diagnosis condition is that the average outlet water temperature is greater than or equal to 30 degrees Celsius. If the code execution result shows that the average outlet water temperature is greater than or equal to 30 degrees Celsius, then the code execution result is determined to meet the fault diagnosis condition. Optionally, the fault diagnosis result can also be set to different forms according to different target diagnostic rules.
[0054] Optionally, if the code execution result does not meet the fault diagnosis conditions corresponding to the target diagnosis rule, a second diagnosis result will be output.
[0055] Optionally, after obtaining the device diagnostic results, the data processing device will also send the device diagnostic results to the downstream server through a data stream transmission framework, whereby the downstream server will handle the fault and store the data. Optionally, in one specific embodiment, the downstream server can be a cloud server (such as an SLS server).
[0056] In this embodiment, the data processing device obtains the device operating parameters of the corresponding target device by responding to a device diagnostic request; it performs rule matching based on the device operating parameters and loaded diagnostic rules to obtain target diagnostic rules, which are dynamically loaded device diagnostic rules assembled by a visual rule component; and it uses the target diagnostic rules and the device operating parameters to perform device diagnostics on the target device to obtain device diagnostic results. This achieves real-time acquisition of the device operating parameters of the target device to be diagnosed, and matches the device operating parameters with dynamically loaded diagnostic rules to obtain the target diagnostic rules associated with the device operating parameters. Then, it uses the target diagnostic rules and the device operating parameters to perform device diagnostics on the target device. This allows for dynamic adjustment (e.g., modification and addition) of diagnostic rules during the device diagnostic process, and their dynamic loading and matching with device operating parameters for device diagnostics, thereby improving the flexibility and accuracy of device diagnostics.
[0057] like Figure 4 As shown, Figure 4 This is a flowchart illustrating an embodiment of the data processing method for generating loading diagnostic rules provided in this application. Specifically, in this embodiment, the data processing method further includes steps 301 to 303: 301. Combine the target rule components according to the component interaction events to obtain the initial diagnostic rules; 302. Perform syntax validation on the initial diagnostic rule using a preset rule expression to obtain the rule validation result; 303. Input the initial diagnostic rule whose rule verification result is the first verification result into the preset rule database for loading to obtain the loaded diagnostic rule.
[0058] Based on the above embodiments, in this embodiment, after obtaining the device operating parameters of the target device, the data processing device also performs rule matching based on the device operating parameters and the loaded diagnostic rules, thereby obtaining the target diagnostic rules for the target device to be diagnosed.
[0059] Optionally, after the data processing device displays the visual rule components on the preset interface and receives component interaction events to determine the target rule component to be assembled into a diagnostic rule, it further combines the target rule component according to the component interaction events to obtain an initial diagnostic rule. This combination of visual rule components according to component interaction events can involve dragging and combining the visual rule components according to operations within the component interaction events to obtain the initial diagnostic rule. This initial diagnostic rule is a set of visual rule components obtained by combining at least one visual rule component. In one specific embodiment, the initial diagnostic rule is a diagnostic rule in JSON format obtained by combining various visual rule components.
[0060] Optionally, after obtaining the initial diagnostic rule, the data processing device performs syntax validation on the initial diagnostic rule using a preset rule expression to obtain a rule validation result. The rule validation result is the verification result determining whether the initial diagnostic rule is compliant. Compliance of the initial diagnostic rule refers to whether the initial diagnostic rule can effectively diagnose the target device. Optionally, the rule validation result includes a first validation result and a second validation result. The first validation result indicates that the initial diagnostic rule is a compliant diagnostic rule. The second validation result indicates that the initial diagnostic rule is a non-compliant diagnostic rule.
[0061] That is, after obtaining the initial diagnostic rule, the data processing device uses a preset rule expression to perform syntax validation on the initial diagnostic rule, determining whether the syntax of the initial diagnostic rule is valid, thereby determining whether the initial diagnostic rule is compliant and valid. Optionally, in one specific embodiment, the preset expression is a regular expression. Optionally, in other embodiments, the data processing device also presets a first diagnostic threshold and a second diagnostic threshold. The first diagnostic threshold is used to limit the minimum value of the parameter in the initial diagnostic rule. The second diagnostic threshold is used to limit the maximum value of the parameter in the initial diagnostic rule. The data processing device also uses the first and second diagnostic thresholds to check the parameter values of the initial diagnostic rule, thereby determining the rule validation result corresponding to the initial diagnostic rule whose parameter value is between the first and second diagnostic thresholds as the first validation result. The rule validation result corresponding to the initial diagnostic rule whose parameter value is less than the first diagnostic threshold or greater than the second diagnostic threshold is determined as the second validation result.
[0062] Optionally, after obtaining the rule verification result corresponding to the initial diagnostic rule, the data processing device inputs the initial diagnostic rule whose rule verification result is the first verification result into the preset rule database for loading, thereby obtaining the loaded diagnostic rule.
[0063] To better implement the data processing method in the embodiments of this application, based on the data processing method, the embodiments of this application also provide a data processing apparatus, such as... Figure 5 As shown, Figure 5 This is a schematic diagram of one embodiment of the data processing apparatus provided in this application. Specifically, the data processing apparatus 400 includes: The information acquisition module 401 is configured to respond to device diagnostic requests and acquire the device operating parameters of the corresponding target device. The rule matching module 402 is configured to perform rule matching based on the device operating parameters and loaded diagnostic rules to obtain target diagnostic rules. The loaded diagnostic rules are device diagnostic rules that are dynamically loaded after being assembled by a visual rule component. The data processing module 403 is configured to perform device diagnosis on the target device using the target diagnosis rules and the device operating parameters, and obtain device diagnosis results.
[0064] In one possible implementation of this embodiment, before the data processing device performs rule matching based on the device operating parameters and loaded diagnostic rules to obtain the target diagnostic rule, it further includes: Display the visual rules component in the preset display interface; In response to component interaction events for any one or more visual rule components, determine the target rule component associated with the component interaction event in the visual rule components; Based on the component interaction events and the target rule component, load diagnostic rules are generated.
[0065] In one possible implementation of this embodiment, the data processing device generates loading diagnostic rules based on the component interaction events and the target rule component, including: The target rule components are combined according to the component interaction events to obtain the initial diagnostic rules; The initial diagnostic rules are syntax-validated using a preset rule expression to obtain the rule validation result; The initial diagnostic rule whose rule verification result is the first verification result is input into the preset rule database for loading, thereby obtaining the loaded diagnostic rule.
[0066] In one possible implementation of this embodiment, the data processing device performs rule matching based on the device operating parameters and loaded diagnostic rules to obtain target diagnostic rules, including: Obtain dynamically loaded diagnostic rules from the preset rule database and determine the rule parameter fields corresponding to each of the loaded diagnostic rules; The target diagnostic rule is obtained by matching the device operating parameters and the rule parameter fields.
[0067] In one possible implementation of this embodiment, the data processing device performs rule matching based on the device operating parameters and the rule parameter fields to obtain target diagnostic rules, including: The operating parameters of the equipment are converted to obtain the converted equipment parameters; The conversion device parameters and the rule parameter fields are matched to obtain the parameter matching result; The loading diagnostic rule corresponding to the rule parameter field whose parameter matching result is the first matching result is determined as the target diagnostic rule.
[0068] In one possible implementation of this embodiment, the data processing device uses the target diagnostic rules and the device operating parameters to perform device diagnostics on the target device, obtaining device diagnostic results, including: The target diagnostic rules are parsed using a rule parser to obtain the target execution code; The target device is diagnosed using the target execution code and the device operating parameters to obtain the device diagnosis results.
[0069] In one possible implementation of this embodiment, the device diagnostic results in the data processing device include a first diagnostic result and a second diagnostic result; the first diagnostic result is a device diagnostic result indicating that the target device is operating abnormally; the second diagnostic result is a device diagnostic result indicating that the target device is operating normally. The data processing device uses the target executable code and the device operating parameters to perform device diagnosis on the target device, and obtains device diagnosis results, including: The target execution code is used to run the conversion device parameters corresponding to the device operating parameters to obtain the code execution result; If the code execution result satisfies the fault diagnosis condition corresponding to the target diagnosis rule, then the first diagnosis result is output; If the code execution result does not meet the fault diagnosis conditions corresponding to the target diagnosis rule, then the second diagnosis result is output.
[0070] In this embodiment, the data processing device obtains the device operating parameters of the corresponding target device in response to a device diagnostic request; performs rule matching based on the device operating parameters and loaded diagnostic rules to obtain target diagnostic rules, which are dynamically loaded device diagnostic rules assembled by a visual rule component; and performs device diagnostics on the target device using the target diagnostic rules and the device operating parameters to obtain device diagnostic results. This achieves real-time acquisition of the device operating parameters of the target device to be diagnosed, and performs rule matching between the device operating parameters and dynamically loaded diagnostic rules to obtain the target diagnostic rules associated with the device operating parameters. Furthermore, it utilizes the target diagnostic rules and device operating parameters to perform device diagnostics on the target device. This allows for dynamic adjustment (e.g., modification and addition) of diagnostic rules during the device diagnostic process, and their dynamic loading and matching with device operating parameters for device diagnostics, thereby improving the flexibility and accuracy of device diagnostics.
[0071] This invention also provides a data processing device, such as... Figure 6 As shown, Figure 6 This is a schematic diagram of one embodiment of the data processing device provided in this application.
[0072] The data processing device integrates any of the data processing apparatuses provided in the embodiments of the present invention, and the data processing device includes: One or more processors; Memory; and One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor of the steps in the data processing method described in any of the embodiments of the above data processing method.
[0073] Specifically, a data processing device may include components such as a processor 501 with one or more processing cores, a memory 502 with one or more computer-readable storage media, a power supply 503, and an input unit 504. Those skilled in the art will understand that... Figure 6 The data processing device structure shown does not constitute a limitation on the data processing device. It may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein: The processor 501 is the control center of the data processing device. It connects various parts of the data processing device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 502, and by calling data stored in the memory 502, it performs various functions of the data processing device and processes data, thereby providing overall monitoring of the data processing device. Optionally, the processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 501.
[0074] The memory 502 can be used to store software programs and modules. The processor 501 executes various functional applications and data processing by running the software programs and modules stored in the memory 502. The memory 502 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the data processing device, etc. In addition, the memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.
[0075] The data processing device also includes a power supply 503 that supplies power to the various components. Preferably, the power supply 503 can be logically connected to the processor 501 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 503 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0076] The data processing device may also include an input unit 504, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
[0077] Although not shown, the data processing device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 501 in the data processing device loads the executable files corresponding to the processes of one or more application programs into the memory 502 according to the following instructions, and the processor 501 runs the application programs stored in the memory 502 to realize various functions, as follows: Respond to device diagnostic requests and obtain the device operating parameters of the corresponding target device; Based on the device operating parameters and the loaded diagnostic rules, rule matching is performed to obtain the target diagnostic rule. The loaded diagnostic rule is a device diagnostic rule that is dynamically loaded after being assembled by a visual rule component. The target device is diagnosed using the target diagnostic rules and the device operating parameters to obtain the device diagnostic results.
[0078] Therefore, embodiments of the present invention provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk, etc. A computer program is stored thereon, which is loaded by a processor to execute the steps of any of the data processing methods provided in the embodiments of the present invention. For example, the computer program loaded by the processor can execute the following steps: Respond to device diagnostic requests and obtain the device operating parameters of the corresponding target device; Based on the device operating parameters and the loaded diagnostic rules, rule matching is performed to obtain the target diagnostic rule. The loaded diagnostic rule is a device diagnostic rule that is dynamically loaded after being assembled by a visual rule component. The target device is diagnosed using the target diagnostic rules and the device operating parameters to obtain the device diagnostic results.
[0079] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the detailed descriptions of other embodiments above, which will not be repeated here.
[0080] In practice, each of the above units or structures can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units or structures, please refer to the previous method embodiments, which will not be repeated here.
[0081] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0082] The above provides a detailed description of a data processing method provided by the embodiments of this application. Specific embodiments have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.
Claims
1. A data processing method, characterized in that, The data processing method includes: Respond to device diagnostic requests and obtain the device operating parameters of the corresponding target device; Based on the device operating parameters and the loaded diagnostic rules, rule matching is performed to obtain the target diagnostic rule. The loaded diagnostic rule is a device diagnostic rule that is dynamically loaded after being assembled by a visual rule component. The target device is diagnosed using the target diagnostic rules and the device operating parameters to obtain the device diagnostic results.
2. The data processing method according to claim 1, characterized in that, Before performing rule matching based on the device operating parameters and loaded diagnostic rules to obtain the target diagnostic rule, the process further includes: Display the visual rules component in the preset display interface; In response to component interaction events for any one or more visual rule components, determine the target rule component associated with the component interaction event in the visual rule components; Based on the component interaction events and the target rule component, load diagnostic rules are generated.
3. The data processing method according to claim 2, characterized in that, The step of generating loading diagnostic rules based on the component interaction events and the target rule component includes: The target rule components are combined according to the component interaction events to obtain the initial diagnostic rules; The initial diagnostic rules are syntax-validated using a preset rule expression to obtain the rule validation result; The initial diagnostic rule whose rule verification result is the first verification result is input into the preset rule database for loading, thereby obtaining the loaded diagnostic rule.
4. The data processing method according to claim 1, characterized in that, The step of performing rule matching based on the device operating parameters and loaded diagnostic rules to obtain the target diagnostic rule includes: Obtain dynamically loaded diagnostic rules from the preset rule database and determine the rule parameter fields corresponding to each of the loaded diagnostic rules; The target diagnostic rule is obtained by matching the device operating parameters and the rule parameter fields.
5. The data processing method according to claim 4, characterized in that, The step of performing rule matching based on the device operating parameters and the rule parameter fields to obtain the target diagnostic rule includes: The operating parameters of the equipment are converted to obtain the converted equipment parameters; The conversion device parameters and the rule parameter fields are matched to obtain the parameter matching result; The loading diagnostic rule corresponding to the rule parameter field whose parameter matching result is the first matching result is determined as the target diagnostic rule.
6. The data processing method according to claim 1, characterized in that, The process of performing equipment diagnosis on the target equipment using the target diagnostic rules and the equipment operating parameters to obtain equipment diagnosis results includes: The target diagnostic rules are parsed using a rule parser to obtain the target execution code; The target device is diagnosed using the target execution code and the device operating parameters to obtain the device diagnosis results.
7. The data processing method according to claim 6, characterized in that, The equipment diagnostic results include a first diagnostic result and a second diagnostic result; the first diagnostic result is a diagnostic result indicating that the target equipment is operating abnormally; the second diagnostic result is a diagnostic result indicating that the target equipment is operating normally. The step of performing device diagnosis on the target device using the target executable code and the device operating parameters to obtain device diagnosis results includes: The target execution code is used to run the conversion device parameters corresponding to the device operating parameters to obtain the code execution result; If the code execution result satisfies the fault diagnosis condition corresponding to the target diagnosis rule, then the first diagnosis result is output; If the code execution result does not meet the fault diagnosis conditions corresponding to the target diagnosis rule, then the second diagnosis result is output.
8. A data processing apparatus, characterized in that, The data processing device includes: The information acquisition module is configured to respond to device diagnostic requests and acquire the device operating parameters of the corresponding target device. The rule matching module is configured to perform rule matching based on the device operating parameters and loaded diagnostic rules to obtain target diagnostic rules. The loaded diagnostic rules are device diagnostic rules that are dynamically loaded after being assembled by a visual rule component. The data processing module is configured to perform device diagnosis on the target device using the target diagnosis rules and the device operating parameters, and obtain device diagnosis results.
9. A data processing device, characterized in that, The data processing device includes: One or more processors; Memory; and One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps of the data processing method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, It stores a computer program, which is loaded by a processor to execute the steps of the data processing method according to any one of claims 1 to 7.