A data processing method, a DCS system, an electronic device, and a storage medium

Abstract

The application provides a data processing method, a DCS system, an electronic device and a storage medium, when a data proxy service detects a data request input by an external device, a corresponding diagnostic point table is determined from a point table service based on the data request, the diagnostic point table of the point table service is constructed based on system configuration of a certain system by a diagnostic point table generator; a diagnostic data reference service acquires the diagnostic point table determined by the data proxy service, and analyzes the data request by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information, so as to query a diagnostic subsystem, acquire diagnostic data corresponding to the data request, and output to the external device through the data proxy service. The diagnostic point table of the corresponding system is constructed based on the system configuration of the certain system, so that the diagnostic point table has high readability, the external device can find the diagnostic point table through the device address information and the diagnostic point information, and data in the diagnostic subsystem can be quickly queried.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a data processing method, a DCS system, an electronic device and a storage medium. BACKGROUND

[0002] The diagnostic subsystem is an important component of the DCS system, and the running state of the whole system can be monitored through the diagnostic subsystem.

[0003] Since the diagnostic subsystem is relatively closed in design, only the data is displayed externally through the diagnostic picture, and other subsystems of the DCS cannot efficiently and conveniently obtain the data of the diagnostic subsystem. SUMMARY

[0004] Therefore, the embodiments of the present application provide a data processing method, a DCS system, an electronic device and a storage medium to solve the problem that the data of the diagnostic subsystem cannot be efficiently and conveniently obtained in the prior art.

[0005] To achieve the above object, the embodiments of the present application provide the following technical solutions.

[0006] The first aspect of the embodiments of the present application shows a data processing method applied to a DCS system, wherein the DCS system comprises a diagnostic point table generator, a point table service, a diagnostic subsystem, a data agent service and a diagnostic data reference service, the diagnostic point table generator is connected with the diagnostic subsystem and the point table service respectively, the data agent service is connected with an external device and the diagnostic data reference service respectively, the diagnostic data reference service is connected with the point table service, and the method comprises the following steps:

[0007] When the data agent service detects a data request input by the external device, the data agent service determines a corresponding diagnostic point table from the point table service based on the data request, and the diagnostic point table of the point table service is constructed by the diagnostic point table generator based on the system configuration of a certain system;

[0008] The diagnostic data reference service acquires the diagnostic point table determined by the data agent service, and analyzes the data request by using the corresponding diagnostic point table of the data request to obtain device address information and diagnostic point information;

[0009] The diagnostic data reference service queries the diagnostic subsystem based on the device address information and the diagnostic point information, acquires diagnostic data corresponding to the data request, and outputs the diagnostic data to the external device through the data agent service.

[0010] Optionally, the data agent service determines the corresponding diagnostic point table from the point table service based on the data request, comprising:

[0011] The data proxy service determines system information corresponding to required acquisition data based on the data request;

[0012] The data proxy service selects corresponding diagnostic point table from the point table service by using the system information.

[0013] Optionally, the process of constructing a diagnostic point table based on system configuration of a system comprises:

[0014] The diagnostic point table generator triggers diagnostic point table creation when detecting start of a system;

[0015] Acquire system configuration data of the system;

[0016] Input the system configuration data into a multi-level creation model, so that the multi-level creation model processes the system configuration data to determine corresponding diagnostic point table.

[0017] Input system information of the system and corresponding diagnostic point table into a point table service for storage.

[0018] Optionally, inputting the system configuration data into a multi-level creation model so that the multi-level creation model processes the system configuration data to determine corresponding diagnostic point table comprises:

[0019] The multi-level creation model splits the system configuration data to obtain system configuration nodes of different levels;

[0020] Call corresponding level processing thread to process system configuration nodes of corresponding level to construct diagnostic point field of each system configuration node;

[0021] Construct corresponding diagnostic point table based on the diagnostic point field of each system configuration node.

[0022] Optionally, calling corresponding level processing thread to process system configuration nodes of corresponding level to construct diagnostic point field of each system configuration node comprises:

[0023] Execute corresponding level processing thread for each level system configuration node;

[0024] Determine whether diagnostic point information exists according to the keyword corresponding to the system configuration node;

[0025] If so, use domain address and station address corresponding to the system configuration node as diagnostic address;

[0026] Combine the role, diagnostic address and diagnostic point information corresponding to the keyword to obtain diagnostic point field of the system configuration node.

[0027] Optionally, the diagnostic data reference service acquires the diagnostic point table determined by the data agent service, and parses the data request by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information, including:

[0028] The diagnostic data reference service acquires the diagnostic point table determined by the data agent service;

[0029] It is determined whether the diagnostic point field corresponding to the data request exists in the diagnostic point table;

[0030] Device address information and diagnostic point information are determined based on the diagnostic point field corresponding to the data request in the diagnostic point table.

[0031] The second aspect of the embodiment of the application shows a DCS system, which comprises a diagnostic point table generator, a point table service, a diagnostic subsystem, a data agent service and a diagnostic data reference service, the diagnostic point table generator is connected with the diagnostic subsystem and the point table service respectively, the data agent service is connected with an external device and the diagnostic data reference service respectively, and the diagnostic data reference service is connected with the point table service;

[0032] The data agent service is configured to determine the diagnostic point table corresponding to the data request from the point table service based on the data request if the data request input by the external device is detected, and the diagnostic point table of the point table service is constructed by the diagnostic point table generator based on the system configuration of a certain system;

[0033] The diagnostic data reference service is configured to acquire the diagnostic point table determined by the data agent service, and parse the data request by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information; and query the diagnostic subsystem based on the device address information and diagnostic point information, acquire diagnostic data corresponding to the data request, and output the diagnostic data to the external device through the data agent service.

[0034] Optionally, the diagnostic point table generator is specifically configured to:

[0035] Detect the start of a certain system, and trigger diagnostic point table creation;

[0036] Acquire system configuration data of the system;

[0037] Input the system configuration data into a multi-level creation model, so that the multi-level creation model processes the system configuration data to determine the corresponding diagnostic point table.

[0038] Input system information of the system and the corresponding diagnostic point table into the point table service for storage.

[0039] The third aspect of the embodiments of the present application shows an electronic device for running a program, wherein the program performs the data processing method shown in the first aspect of the embodiments of the present application when running.

[0040] The fourth aspect of the embodiments of the present application shows a storage medium comprising a program, wherein the device where the storage medium is located performs the data processing method shown in the first aspect of the embodiments of the present application when the program runs.

[0041] Based on the data processing method, the DCS system, the electronic device and the storage medium provided in the embodiments of the present application, the DCS system comprises a diagnostic point table generator, a point table service, a diagnostic subsystem, a data agent service and a diagnostic data reference service, the diagnostic point table generator is connected with the diagnostic subsystem and the point table service respectively, the data agent service is connected with an external device and the diagnostic data reference service respectively, the diagnostic data reference service is connected with the point table service, and the method comprises the following steps: when the data agent service detects a data request input by the external device, the data agent service determines a corresponding diagnostic point table from the point table service based on the data request, the diagnostic point table of the point table service is constructed by the diagnostic point table generator based on the system configuration of a certain system; the diagnostic data reference service acquires the diagnostic point table determined by the data agent service, and analyzes the data request by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information; and the diagnostic data reference service queries the diagnostic subsystem based on the device address information and the diagnostic point information, acquires diagnostic data corresponding to the data request, and outputs the diagnostic data to the external device through the data agent service. In the embodiments of the present application, the diagnostic point table of a certain system is constructed based on the system configuration of the system, so that the diagnostic point table has high readability. Moreover, the constructed diagnostic point table is a soft point table, so that system resources are not occupied. When the data request input by the external device is detected, the corresponding diagnostic point table is queried based on the data request, and the data request is analyzed by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information; and then the diagnostic subsystem is queried based on the device address information and the diagnostic point information, so that the external device can quickly query the data in the diagnostic subsystem by using the device address information and the diagnostic point information. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments or the prior art description will be briefly introduced as follows. Obviously, the drawings in the following description are only embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative effort on the basis of the provided drawings.

[0043] Figure 1 The architecture diagram of the DCS system shown in the embodiment of the present application is shown in the figure;

[0044] Figure 2 The flow diagram of the data processing method shown in the embodiment of the present application is shown in the figure;

[0045] Figure 3 The multi-level creation model shown in the embodiment of the present application is shown in the figure;

[0046] Figure 4 The architecture diagram of the diagnostic point table shown in the embodiment of the present application is shown in the figure;

[0047] Figure 5 The diagnostic data reference shown in the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.

[0049] The terms "first", "second", "third", "fourth" and the like (if any) in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to the process, method, product or device.

[0050] It should be noted that the description of "first", "second" and the like in the present application is only for the purpose of description, and cannot be understood as indicating or implying the relative importance of the indicated technical features or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first", "second" can explicitly or implicitly include at least one of the features. In addition, the technical solutions of various embodiments can be combined with each other, but must be based on the realization of a person skilled in the art, when the combination of technical solutions appears to be contradictory or unachievable, it should be considered that the combination of technical solutions does not exist, nor within the scope of protection required by the present application.

[0051] In this application, the terms "comprise", "contain" or any other variant thereof are intended to cover non-exclusive inclusions, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or device. Without more limitations, the element defined by the statement "comprises a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0052] Referring to Figure 1 The schematic diagram of the architecture of the DCS system shown in the embodiment of the present application.

[0053] The DCS system comprises a diagnostic point table generator 10, a point table service 20, a diagnostic subsystem 30, a data agent service 40, and a diagnostic data reference service 50;

[0054] The diagnostic point table generator 10 is connected with the diagnostic subsystem 30 and the point table service 20 respectively;

[0055] The data agent service 40 is connected with the external device 60 and the diagnostic data reference service 50 respectively, and the diagnostic data reference service 50 is connected with the point table service 20;

[0056] The point table service 20 is connected with the DCS system, i.e. with each subsystem thereunder.

[0057] The process of data processing based on the architecture shown in the embodiment of the present application comprises:

[0058] The data agent service 40 is configured to determine the corresponding diagnostic point table from the point table service 20 based on the data request if the data request input by the external device 60 is detected, and the diagnostic point table of the point table service 20 is constructed by the diagnostic point table generator 10 based on the system configuration of a certain system.

[0059] Specifically, the data agent service 40 detects in real time whether a data request sent by the external device such as other subsystems of the DCS or third-party systems is received, and determines the corresponding diagnostic point table from the point table service 20 based on the data request if the data request is received.

[0060] The diagnostic data reference service 50 is configured to acquire the diagnostic point table determined by the data agent service 40, parse the data request by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information, query the diagnostic subsystem 30 based on the device address information and the diagnostic point information, acquire diagnostic data corresponding to the data request, and output the diagnostic data to the external device 60 through the data agent service 40.

[0061] Optionally, the data agent service 40 determines the diagnostic point table corresponding to the data request from the point table service 20 based on the data request, and the determination includes:

[0062] The data agent service 40 determines system information corresponding to the data to be acquired based on the data request, and selects the diagnostic point table corresponding to the system information from the point table service 20 by using the system information.

[0063] Specifically, the data agent service 40 acquires system information corresponding to the data to be acquired from the data request, and traverses the point table service 20 to determine the diagnostic point table corresponding to the system information by using the system information.

[0064] It should be noted that the system information includes system identification id and other information capable of identifying the system.

[0065] Optionally, the diagnostic point table generator 10 is specifically configured to:

[0066] When detecting that a system is started, triggering the creation of a diagnostic point table, acquiring system configuration data of the system, inputting the system configuration data into a multi-level creation model, so that the multi-level creation model processes the system configuration data to determine the diagnostic point table corresponding to the system, and inputting system information of the system and the diagnostic point table corresponding to the system into the point table service 20 for storage.

[0067] Specifically, for each system, the diagnostic point table generator 10 automatically creates a diagnostic point table corresponding to the system when detecting that a system is started, acquires system configuration data of the system, so that the multi-level creation model processes the system configuration data to determine the diagnostic point table corresponding to the system.

[0068] It should be noted that the system refers to a system under a DCS system.

[0069] It should be noted that the system configuration data includes the association relationship of devices constituting the system, components under the devices, and sub-components under the components, and other components.

[0070] Further, it should be noted that the devices, the components under the devices, and the sub-components under the components, and other components are all system configuration nodes.

[0071] That is, the next level of association of the component is a subcomponent connected to or disposed within the component; conversely, the upper level of association of the subcomponent is the corresponding component.

[0072] The multi-level creation model is constructed by a main thread, a first-level hierarchical processing thread, a second-level hierarchical processing thread, and an N-level hierarchical processing thread.

[0073] N is a positive integer greater than or equal to 2.

[0074] Optionally, the diagnostic point table generator 10 inputs the system configuration data into the multi-level creation model, so that the multi-level creation model processes the system configuration data to determine a corresponding diagnostic point table, including:

[0075] The diagnostic point table generator 10 calls the multi-level creation model to split the system configuration data to obtain system configuration nodes of different levels; calls a corresponding hierarchical processing thread to process system configuration nodes of a corresponding level to construct a diagnostic point field of each system configuration node; and constructs a corresponding diagnostic point table based on the diagnostic point field of each system configuration node.

[0076] Specifically, after the diagnostic point table generator 10 calls the main thread of the multi-level creation model to load the system configuration, for each system configuration node in the system configuration data, it is first determined whether the system configuration node has an association relationship, if it is determined that the system configuration node does not have a corresponding upper level association relationship but has a corresponding lower level association relationship, it is determined to be a first level system configuration node; if it is determined that the system configuration node has a corresponding upper level association relationship and a corresponding lower level association relationship, the level X of the upper level association system is determined, and the system configuration node is determined to be an X+1 level system configuration node, and so on, until the level of each system configuration node is determined. A corresponding hierarchical processing thread processes system configuration nodes of a corresponding level to construct a diagnostic point field of each system configuration node.

[0077] Optionally, the diagnostic point table generator 10 calls a corresponding hierarchical processing thread to process system configuration nodes of a corresponding level to construct a diagnostic point field of each system configuration node, including:

[0078] For each level system configuration node, a corresponding hierarchical processing thread is executed; it is determined whether the system configuration node has diagnosable point information according to a keyword corresponding to the system configuration node; if so, the domain address and station address corresponding to the system configuration node are taken as diagnostic addresses; and the role, diagnostic address, and diagnostic point information corresponding to the keyword are combined to obtain a diagnostic point field of the system configuration node.

[0079] Specifically, first, the diagnostic point table generator 10 calls each hierarchical processing thread in parallel for each hierarchical system configuration node, so that a first hierarchical processing thread processes a first system configuration node, a second hierarchical processing thread processes a second system configuration node, and so on, and an Nth hierarchical processing thread processes an Nth system configuration node.

[0080] Next, the keyword corresponding to the system configuration node is extracted, the correspondence between the pre-set keyword and the diagnostic point information is queried, and it is determined whether there is diagnostic point information corresponding to the keyword corresponding to the system configuration node. If there is, it means that the system configuration node can have diagnostic point information. The domain address and station address corresponding to the hierarchical system configuration node in the system are obtained, and the domain address and station address are taken as the diagnostic address of the system configuration node.

[0081] Finally, the keyword corresponding to the role in the system configuration node is searched for, and the diagnostic point information corresponding to the role is obtained. For example, the diagnostic point information corresponding to the role operation node includes CPU load and CPU load alarm state. Then, the role, diagnostic address, and diagnostic point information are combined to obtain the diagnostic point field of the system configuration node.

[0082] It should be noted that each role has corresponding diagnostic point information, which is set in advance according to multiple experiments or experience.

[0083] It should be noted that the diagnostic point information refers to the detailed position of the diagnostic point.

[0084] The diagnostic point is a suspicious point that may cause system abnormalities. Generally, CPU load, CPU load alarm state, data service state, running state, network state, address conflict, and the like are suspicious points that may cause system bottlenecks.

[0085] The diagnostic point position of each system configuration node includes role_diagnostic address_diagnostic point information, such as: NODE_domain address_station address_diagnostic point information.

[0086] Optionally, the diagnostic data reference service 50 obtains the diagnostic point table determined by the data agent service, and uses the diagnostic point table corresponding to the data request to analyze the data request, to obtain device address information and diagnostic point information, including:

[0087] The diagnostic data reference service 50 obtains the diagnostic point table determined by the data agent service 40, searches for whether there is a diagnostic point field corresponding to the data request in the diagnostic point table, and determines the device address information and diagnostic point information based on the diagnostic point field corresponding to the data request in the diagnostic point table.

[0088] Specifically, the diagnostic data reference service 50 acquires the diagnostic point table determined by the data agent service 40; determines whether there is a role corresponding to the diagnostic point table by using the keyword in the data request, if there is, further determines whether there is the same diagnostic point information as the specific request data in the diagnostic point field corresponding to the role in the diagnostic point table according to the specific request data in the data request, if there is, acquires the diagnostic point field corresponding to the data request from the diagnostic point table;

[0089] Then, the corresponding device address information and diagnostic point information are acquired from the diagnostic point field.

[0090] In the embodiment of the application, the diagnostic point table corresponding to a system is constructed based on the system configuration of the system, so that the diagnostic point table has high readability. The constructed diagnostic point table is a soft point table, so that system resources are not occupied. When the data request input by the external device is detected, the corresponding diagnostic point table is queried based on the data request, and the data request is analyzed by using the diagnostic point table corresponding to the data request, to obtain device address information and diagnostic point information. Then, the diagnostic subsystem is queried based on the device address information and diagnostic point information, to acquire diagnostic data corresponding to the data request, and the diagnostic data is output to the external device by the data agent service. The external device can quickly query the data in the diagnostic subsystem by using the device address information and diagnostic point information.

[0091] Referring to Figure 2 The flowchart of the data processing method shown in the embodiment of the application comprises the following steps:

[0092] Step S201: The data agent service determines whether the data request input by the external device is received, if yes, step S202 is performed, if not, the step S201 is continued to be performed.

[0093] In the process of implementing the step S201, the data agent service detects in real time whether the data request sent by the external device such as the DCS other subsystem or the third party system is received, if yes, the step S202 is performed, if not, the step S201 is continued to be performed.

[0094] Step S202: The data agent service determines the corresponding diagnostic point table from the point table service based on the data request.

[0095] The diagnostic point table of the point table service is constructed by the diagnostic point table generator based on the system configuration of a system.

[0096] It should be noted that the process of implementing the step S202 comprises the following steps:

[0097] Step S11: The data proxy service determines the system information corresponding to the required data based on the data request;

[0098] In the process of implementing step S11, the data proxy service obtains the system information corresponding to the required data from the data request;

[0099] It should be noted that the system information includes system identification id and other information that can identify the system.

[0100] Step S12: The data proxy service selects the corresponding diagnostic point table from the point table service using the system information;

[0101] In the process of implementing step S12, the data proxy service traverses the point table service using the system information to determine the diagnostic point table corresponding to the system information.

[0102] It should be noted that the process of constructing a diagnostic point table based on the system configuration of the DCS system includes the following steps:

[0103] Step S21: The diagnostic point table generator detects the start of a system and triggers the creation of a diagnostic point table;

[0104] It should be noted that the system refers to the system under the DCS system.

[0105] In the process of implementing step S21, for each system, such as system 1, system 2,..., system 3, the diagnostic point table generator detects the start of a system and automatically creates the diagnostic point table corresponding to the system.

[0106] Step S22: Obtain the system configuration data of the system;

[0107] It should be noted that the system configuration data includes the association relationship of the devices that constitute the system, the components under the devices, and the subcomponents under the components, etc.

[0108] Further, it should be noted that the devices, the components under the devices, and the subcomponents under the components, etc. are all system configuration nodes.

[0109] That is, the next level of association of a component is the subcomponent connected to or set in the component; conversely, the next level of association of a subcomponent is the corresponding component.

[0110] Step S23: Input the system configuration data into a multi-level creation model to process the system configuration data and determine the corresponding diagnostic point table.

[0111] The multi-level creation model is constructed by a main thread, a first-level hierarchical processing thread, a second-level hierarchical processing thread, and an Nth-level hierarchical processing thread.

[0112] N is a positive integer greater than or equal to 2.

[0113] It should be noted that the process of implementing step S23 includes the following steps:

[0114] Step S31: The multi-level creation model splits the system configuration data to obtain system configuration nodes of different levels.

[0115] In the process of implementing step S31, after the main thread of the multi-level creation model loads the system configuration, for each system configuration node in the system configuration data, it is first determined whether the system configuration node has an association relationship. If it is determined that there is no corresponding upper-level association relationship but there is a corresponding lower-level association relationship, the system configuration node is regarded as a first-level system configuration node. If it is determined that there is a corresponding upper-level association relationship and a corresponding lower-level association relationship, the level X of the upper-level association system is determined, and the system configuration node is regarded as an X+1-level system configuration node. This process is repeated until the level of each system configuration node is determined.

[0116] Step S32: The multi-level creation model calls the corresponding hierarchical processing thread to process the system configuration nodes of the corresponding level to construct the diagnostic point field of each system configuration node.

[0117] It should be noted that in the process of implementing step S32, the following steps are included:

[0118] Step S41: For each level system configuration node, the corresponding hierarchical processing thread is executed.

[0119] In the process of implementing step S31, for each level system configuration node, the multi-level creation model calls each level processing thread for parallel execution, so that the first-level hierarchical processing thread processes the first-level system configuration node, the second-level hierarchical processing thread processes the second-level system configuration node, and so on, and the Nth-level hierarchical processing thread processes the Nth-level system configuration node, as shown in Figure 3 .

[0120] N is a positive integer greater than or equal to 2.

[0121] Step S42: According to the keyword corresponding to the system configuration node, it is determined whether there is diagnostic point information that can exist. If there is, step S43 is executed. If there is not, it means that the current system configuration node does not have diagnostic point information, that is, the system configuration node does not affect the system exception.

[0122] In the implementation of step S42, the keyword corresponding to the system configuration node is extracted, the correspondence between the pre-set keyword and the diagnostic point information is queried, and it is determined whether there is diagnostic point information corresponding to the keyword corresponding to the system configuration node. If there is, it means that the system configuration node may have diagnostic point information, and step S43 is executed; if not, it means that the current system configuration node does not have diagnostic point information, that is, the system configuration node will not affect the system exception.

[0123] It should be noted that the process of the correspondence between the pre-set keyword and the diagnostic point information includes:

[0124] The historical keywords of the system configuration node and the system historical diagnostic point information are experimented multiple times to determine the correspondence between different keywords and diagnostic point information, and are stored.

[0125] Step S43: taking the domain address and station address corresponding to the system configuration node as the diagnostic address;

[0126] In the implementation of step S43, the domain address and station address corresponding to the hierarchical system configuration node in the system are obtained, and the domain address and station address are taken as the diagnostic address of the system configuration node.

[0127] Step S44: combining the role corresponding to the keyword, the diagnostic address and the diagnostic point information to obtain the diagnostic point field of the system configuration node.

[0128] It should be noted that each role has different keywords, and the keywords owned by each role are pre-set through multiple experiments.

[0129] In the implementation of step S44, the role corresponding to the keyword in the system configuration node is first found, and the diagnostic point information corresponding to the role is obtained, for example, the diagnostic point information corresponding to the role operation node includes CPU load and CPU load alarm state; then, the role, the diagnostic address and the diagnostic point information are combined to obtain the diagnostic point field of the system configuration node.

[0130] It should be noted that each role has corresponding diagnostic point information, which is pre-set according to multiple experiments or experience.

[0131] It should be noted that the diagnostic point information refers to the detailed location of the diagnostic point.

[0132] The diagnostic point is a suspicious point that may cause system exception. Generally, CPU load, CPU load alarm state, data service state, running state, network state, address conflict and the like are suspicious points that may cause system bottleneck.

[0133] The diagnosis point position of each system configuration node comprises role_diagnosis_address_diagnosis point information, such as: NODE_domain address_station address_diagnosis point information.

[0134] Optionally, the structure of the diagnosis point table can be as shown in Table (1).

[0135] Table (1):

[0136]

[0137] As can be seen from Table (1), the structure of the diagnosis point table comprises a role operation node NODE, a role server SVR, a role controller CON, a role data forwarding card COM, a role IO card IOM_, and a role IO card channel CHN, each of which is used for a different keyword.

[0138] It should be noted that the diagnosis information corresponding to the same role of different systems is the same, and the diagnosis information of different roles is different.

[0139] It should be noted that the processing procedure of each level processing thread for the system configuration node of the corresponding level is the same, and based on this, the procedure of the two-level processing thread for the two-level system configuration node is taken as an example for description.

[0140] Specifically, for each two-level system configuration node, the two-level processing thread is executed to determine whether the diagnosis point information corresponding to the keyword of the two-level system configuration node exists, if it exists, the domain address and the station address corresponding to the two-level system configuration node are taken as the corresponding diagnosis address, and then the role, the diagnosis address and the diagnosis point information corresponding to the keyword are combined to obtain the diagnosis point field of the two-level configuration node.

[0141] If it does not exist, it means that the current two-level system configuration node does not have diagnosis point information, that is, the two-level system configuration node will not affect the system exception.

[0142] Step S33: The multi-level creation model constructs the corresponding diagnosis point table based on the diagnosis point field of each system configuration node.

[0143] In the process of implementing step S33, each level processing thread in the multi-level creation model constructs the corresponding diagnosis point table based on the diagnosis point position of the corresponding level obtained by itself.

[0144] Step S24: The system information of the system and the corresponding diagnosis point table are input into the point table service for storage.

[0145] The diagnostic point table is not stored in the disk, but is stored outside the disk of the corresponding system, because the diagnostic point table is a soft point table, that is, the point table service is arranged outside the disk, and a certain storage memory is built in for storing the correspondence between the system information of different systems and the corresponding diagnostic point table.

[0146] In step S203, the diagnostic data reference service acquires the diagnostic point table determined by the data agent service, and parses the data request by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information.

[0147] It should be noted that the process of implementing step S203 includes the following steps:

[0148] In step S51, the diagnostic data reference service acquires the diagnostic point table determined by the data agent service.

[0149] Optionally, the data agent service sends the diagnostic point table corresponding to the data request to the diagnostic data reference service, so that the diagnostic data reference service references.

[0150] In step S52, it is determined whether the diagnostic point field corresponding to the data request exists in the diagnostic point table. If the diagnostic point field exists, step S53 is performed; if the diagnostic point field does not exist, step S54 is performed.

[0151] In the process of implementing step S52, it is determined whether the role corresponding to the diagnostic point table exists in the data request by using the keyword in the data request. If the role exists, it is further determined whether the diagnostic point information same as the specific request data exists in the diagnostic point field corresponding to the role in the diagnostic point table according to the specific request data in the data request. If the diagnostic point information exists, step S53 is performed; if the diagnostic point information does not exist, the data request is marked, so that the corresponding diagnostic point table is optimized based on the data request subsequently.

[0152] In step S53, the device address information and the diagnostic point information are determined based on the diagnostic point field corresponding to the data request in the diagnostic point table.

[0153] In the process of implementing step S53, the diagnostic point field corresponding to the data request is acquired from the diagnostic point table. For example, the diagnostic point field can be NODE_001_129_CPU, that is, the CPU load condition of the operation node at address 0.129.

[0154] Then, the device address information corresponding to the diagnostic point field, that is, the diagnostic address 001_129, and the diagnostic point information, that is, the CPU in the diagnostic point field, are acquired.

[0155] Optionally, the diagnostic subsystem stores a diagnostic data block for each diagnostic point, and each data block is uniquely indexed according to device address information;

[0156] Step S54: Query the preset regular point table to determine the table data address corresponding to the data request, and query the system database using the table data address to obtain the corresponding data;

[0157] It should be noted that the regular point table refers to the regular data of the system, such as basic data.

[0158] In the process of implementing step S54, first, the system information corresponding to the data to be obtained is determined through step S31; then the system information is used to select the corresponding regular point table from the point table service, and the data address corresponding to the data request in the regular point table is queried, so as to traverse the system database based on the table data address to obtain the corresponding data.

[0159] The construction process of the regular point table is that the multi-level creation model splits the system configuration data to obtain system configuration nodes of different levels; a corresponding level processing thread is called to process the system configuration nodes of the corresponding level to construct the data address of each system configuration node; and the corresponding regular point table is constructed based on the data address of each system configuration node.

[0160] It should be noted that the regular point table is composed of roles and data addresses, and the implementation process can be the same as the creation process of the diagnostic point table, and can be referred to each other.

[0161] It should be noted that the specific process of implementing steps S51 to S54 can be achieved by referring to the attached drawings. Figure 4 It is explained that the corresponding diagnostic point table is constructed by the diagnostic point table generator, and the regular point table is also constructed.

[0162] Step S204: The diagnostic data reference service queries the diagnostic subsystem based on the device address information and the diagnostic point information to obtain the diagnostic data corresponding to the data request, and outputs the diagnostic data to the external device through the data proxy service.

[0163] In the process of implementing step S204, the diagnostic data reference service quickly maps the diagnostic data block in the diagnostic subsystem through the device address, and obtains the in-block offset of the diagnostic data block through the diagnostic point information, so as to quickly obtain the diagnostic data, as shown in Figure 5

[0164] ​In the embodiment of the present application, the diagnostic point table of a certain system is constructed based on the system configuration of the system, so that the diagnostic point table has high readability. The constructed diagnostic point table is a soft point table, so that no system resource is occupied. When the data request input by the external device is detected, the corresponding diagnostic point table is queried based on the data request, and the data request is parsed by using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information. Then, the diagnostic subsystem is queried based on the device address information and the diagnostic point information, the diagnostic data corresponding to the data request is acquired, and the diagnostic data is output to the external device through the data proxy service. The external device can quickly query the data in the diagnostic subsystem through the device address information and the diagnostic point information.

[0165] The embodiment of the present application provides an electronic device, the electronic device comprises a processor and a memory, the memory is used for storing data processing program code and data, and the processor is used for calling program instructions in the memory to execute steps shown in the data processing method in the above embodiment.

[0166] The embodiment of the present application provides a storage medium, the storage medium comprises the electronic device provided by the embodiment of the present application, and the electronic device is used for executing the data processing method disclosed by the embodiment of the present application.

[0167] Each embodiment in the specification is described in a progressive manner, and the same and similar parts of each embodiment can be referred to each other. Each embodiment mainly describes the difference from other embodiments. Especially, the system or the system embodiment is basically similar to the method embodiment, so the description is relatively simple, and the related parts can be referred to the part of the method embodiment. The system and the system embodiment described above are only schematic, the units described as separate components can be or can not be physically separated, and the components displayed as units can be or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to the actual needs, some or all of the modules can be selected to achieve the purpose of the embodiment scheme. Those skilled in the art can understand and implement without creative labor.

[0168] Those skilled in the art will further realize that the mechanisms of the various examples described herein are capable of being implemented using any number of combinations of the described features. Accordingly, these examples are not limited to the mechanisms described herein, but rather, the intent is to cover all modifications and alternatives equivalent thereto. The preceding description of the examples is illustrative, and not restrictive. Many other examples will be apparent to those of skill in the art upon reviewing the above description. The scope of the examples should, therefore, be determined not with reference to the above description, but instead should be given to the appended claims, along with their full scope of equivalents.

[0169] The above description of disclosed examples is intended to be illustrative, and not restrictive. Many other examples will be apparent to those of skill in the art upon reviewing the above description. The scope of the examples should, therefore, be determined not with reference to the above description, but instead should be given to the appended claims, along with their full scope of equivalents.

Claims

1. A data processing method, characterized in that, The method is applied to a DCS system, which includes a diagnostic point table generator, a point table service, a diagnostic subsystem, a data proxy service, and a diagnostic data reference service. The diagnostic point table generator is connected to the diagnostic subsystem and the point table service, respectively. The data proxy service is connected to external devices and the diagnostic data reference service, respectively. The diagnostic data reference service is connected to the point table service. The method includes: If the data proxy service detects a data request input by the external device, the data proxy service determines the corresponding diagnostic point table from the point table service based on the data request. The diagnostic point table of the point table service is constructed by the diagnostic point table generator based on the system configuration of a certain system. The diagnostic data reference service obtains the diagnostic point table determined by the data proxy service, and uses the diagnostic point table corresponding to the data request to parse the data request to obtain device address information and diagnostic point information; The diagnostic data referencing service queries the diagnostic subsystem based on the device address information and diagnostic point information to obtain the diagnostic data corresponding to the data request, and outputs it to the external device through the data proxy service. The process by which the diagnostic point table generator constructs a diagnostic point table based on the system configuration of a certain system includes: When the diagnostic point table generator detects that a system has started, it triggers the creation of the diagnostic point table. Obtain the system configuration data of the system; The system configuration data is input into the multi-level creation model so that the multi-level creation model can process the system configuration data and determine the corresponding diagnostic point table; The system information of the system and the corresponding diagnostic point table are stored in the point table service.

2. The method according to claim 1, characterized in that, The data proxy service determines the corresponding diagnostic point table from the point table service based on the data request, including: The data proxy service determines the system information corresponding to the data to be obtained based on the data request; The data proxy service uses the system information to select the corresponding diagnostic point table from the point table service.

3. The method according to claim 1, characterized in that, The system configuration data is input into a multi-level creation model so that the multi-level creation model can process the system configuration data and determine the corresponding diagnostic point table, including: The multi-level creation model splits the system configuration data to obtain system configuration nodes at different levels; The corresponding level processing thread is invoked to process the corresponding level system configuration node in order to construct the diagnostic point field for each system configuration node; A corresponding diagnostic point table is constructed based on the diagnostic point field of each system configuration node.

4. The method according to claim 3, characterized in that, The corresponding level processing thread is invoked to process the corresponding level's system configuration node, in order to construct the diagnostic point fields for each system configuration node, including: For each system configuration node at each level, execute the corresponding level processing thread; Determine whether diagnostic point information can exist based on the keywords corresponding to the system configuration nodes; If present, the domain address and station address corresponding to the system configuration node will be used as the diagnostic address; The diagnostic point field of the system configuration node is obtained by combining the role, diagnostic address, and diagnostic point information corresponding to the keyword.

5. The method according to claim 1, characterized in that, The diagnostic data referencing service obtains the diagnostic point table determined by the data proxy service, and uses the diagnostic point table corresponding to the data request to parse the data request to obtain device address information and diagnostic point information, including: The diagnostic data referencing service obtains the diagnostic point table determined by the data proxy service; Check if the diagnostic point table contains a diagnostic point field corresponding to the data request; The device address information and diagnostic point information are determined based on the diagnostic point field corresponding to the data request in the diagnostic point table.

6. A DCS system, characterized in that, The DCS system includes a diagnostic point table generator, a point table service, a diagnostic subsystem, a data proxy service, and a diagnostic data reference service. The diagnostic point table generator is connected to the diagnostic subsystem and the point table service, respectively. The data proxy service is connected to external devices and the diagnostic data reference service, respectively. The diagnostic data reference service is connected to the point table service. The data proxy service is used to determine the corresponding diagnostic point table from the point table service based on the data request when a data request input from the external device is detected. The diagnostic point table of the point table service is constructed by the diagnostic point table generator based on the system configuration of a certain system. The diagnostic data referencing service is used to obtain the diagnostic point table determined by the data proxy service, and to parse the data request using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information; based on the device address information and diagnostic point information, the service queries the diagnostic subsystem to obtain the diagnostic data corresponding to the data request, and outputs it to the external device through the data proxy service. Specifically, the diagnostic point table generator, which constructs a diagnostic point table based on the system configuration of a certain system, is used for: When a system startup is detected, the creation of the diagnostic point table is triggered. Obtain the system configuration data of the system; The system configuration data is input into the multi-level creation model so that the multi-level creation model can process the system configuration data and determine the corresponding diagnostic point table; The system information of the system and the corresponding diagnostic point table are stored in the point table service.

7. An electronic device, characterized in that, The electronic device is used to run a program, wherein the program executes the data processing method as described in any one of claims 1-5.

8. A storage medium, characterized in that, The storage medium includes a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to perform the data processing method as described in any one of claims 1-5.

Images