Data processing method, DCS system, electronic device and storage medium

Abstract

The invention provides a data processing method, a DCS system, an electronic device and a storage medium, if a data proxy service detects a data request input by an external device, a corresponding diagnosis point table is determined from a point table service based on the data request, and the diagnosis point table of the point table service is constructed by a diagnosis point table generator based on system configuration of a certain system; and the diagnosis data reference service obtains the diagnosis point table determined by the data proxy service, analyzes the data request by using the diagnosis point table corresponding to the data request to obtain equipment address information and diagnosis point information so as to query the diagnosis subsystem, obtain diagnosis data corresponding to the data request, and output the diagnosis data to the external equipment through the data proxy service. According to the method, the diagnosis point table of the corresponding system is constructed based on the system configuration of a certain system, so that the diagnosis point table has high readability, and the external equipment can search the diagnosis point table through the equipment address information and the diagnosis point information so as to quickly query the data in the diagnosis subsystem.

Description

Technical Field

[0001] The present invention 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 Art

[0002] The diagnostic subsystem is an important part of the distributed control system DCS system. Through this diagnostic subsystem, the operating status of the entire system can be monitored.

[0003] Since the diagnostic subsystem is relatively closed in design and only displays data through the diagnostic screen itself, other DCS subsystems cannot obtain the diagnostic subsystem data efficiently and conveniently. Summary of the invention

[0004] In view of this, an embodiment of the present invention provides a data processing method, a DCS system, an electronic device and a storage medium to solve the problem in the prior art that the diagnostic subsystem data cannot be obtained efficiently and conveniently.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] A first aspect of an embodiment of the present invention shows a data processing method, which is applied to a DCS system. 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 an external device and a diagnostic data reference service respectively, and the diagnostic data reference service is connected to the point table service. The method includes:

[0007] If the data proxy service detects a data request input by the external device, the data proxy service determines a corresponding diagnostic point table from the point table service based on the data request, wherein 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 obtains the diagnostic point table determined by the data proxy service, and parses the data request using the diagnostic point table corresponding to 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, obtains the diagnostic data corresponding to the data request, and outputs it to the external device through the data proxy service.

[0010] Optionally, the data proxy service determines a corresponding diagnosis point table from the point table service based on the data request, including:

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

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

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

[0014] When the diagnostic point table generator detects that a certain system is started, the diagnostic point table creation is triggered;

[0015] Obtaining system configuration data of the system;

[0016] The system configuration data is input into a multi-level creation model so that the multi-level creation model processes the system configuration data and determines a corresponding diagnosis point table.

[0017] The system information of the system and the corresponding diagnostic point table are input into the 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 and determines a corresponding diagnostic point table, including:

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

[0020] Calling a corresponding level processing thread to process a corresponding level system configuration node to construct a diagnosis point field of each system configuration node;

[0021] A corresponding diagnosis point table is constructed based on the diagnosis point field of each system configuration node.

[0022] Optionally, calling a corresponding level processing thread to process a corresponding level system configuration node to construct a diagnostic point field for each system configuration node, including:

[0023] For each level of system configuration nodes, execute the corresponding level processing threads;

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

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

[0026] The role, diagnosis address and diagnosis point information corresponding to the keyword are combined to obtain the diagnosis point field of the system configuration node.

[0027] Optionally, the diagnostic data reference service obtains the diagnostic point table determined by the data proxy service, and parses the data request 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 obtains the diagnostic point table determined by the data proxy service;

[0029] Find out whether there is a diagnosis point field corresponding to the data request in the diagnosis point table;

[0030] 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.

[0031] A second aspect of an embodiment of the present invention shows a DCS system, the DCS system comprising 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 an external device and the diagnostic data reference service respectively, and the diagnostic data reference service is connected to the point table service;

[0032] The data proxy service is used for, if a data request input by the external device is detected, the data proxy 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 being constructed by the diagnostic point table generator based on a system configuration of a certain system;

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

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

[0035] When a system is detected to be started, the creation of the diagnostic point table is triggered;

[0036] Obtaining system configuration data of the system;

[0037] The system configuration data is input into a multi-level creation model so that the multi-level creation model processes the system configuration data and determines a corresponding diagnosis point table.

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

[0039] A third aspect of an embodiment of the present invention shows an electronic device, which is used to run a program, wherein the program executes the data processing method shown in the first aspect of the embodiment of the present invention when it is run.

[0040] A fourth aspect of an embodiment of the present invention shows a storage medium, which includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the data processing method shown in the first aspect of the embodiment of the present invention.

[0041] Based on the above embodiment of the present invention, a data processing method, a DCS system, an electronic device and a storage medium are provided. 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 an external device and a diagnostic data reference service respectively, and 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 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; 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 reference service queries the diagnostic subsystem based on the device address information and the diagnostic point information, obtains diagnostic data corresponding to the data request, and outputs it to the external device through the data proxy service. In the embodiment of the present invention, a diagnostic point table of a corresponding system is first constructed based on the system configuration of a certain system, so that the diagnostic point table has high readability. And the constructed diagnostic point table is a soft point table, so that system resources do not need to be occupied. When a 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 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, so that the external device can quickly query the data in the diagnostic subsystem through the device address information and diagnostic point information. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0043] Figure 1 A schematic diagram of the architecture of a DCS system according to an embodiment of the present invention;

[0044] Figure 2 A schematic flow chart of a data processing method according to an embodiment of the present invention;

[0045] Figure 3 A schematic diagram of a multi-level creation model construction diagnosis point shown in an embodiment of the present invention;

[0046] Figure 4 A schematic diagram of a diagnostic point table architecture shown in an embodiment of the present invention;

[0047] Figure 5 This is a schematic diagram of diagnostic data reference according to an embodiment of the present invention. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0049] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0050] It should be noted that the descriptions of "first", "second", etc. in the present invention are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0051] In this application, the terms "comprises", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0052] See also Figure 1 , is a schematic diagram of the architecture of a DCS system shown in an embodiment of the present invention.

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

[0054] Wherein, the diagnostic point table generator 10 is connected to the diagnostic subsystem 30 and the point table service 20 respectively;

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

[0056] The point meter service 20 is connected to the DCS system, that is, to each subsystem under it.

[0057] The process of implementing data processing based on the architecture shown in the above embodiment of the present invention includes:

[0058] The data proxy service 40 is used for, if a data request input by the external device 60 is detected, the data proxy service 40 determines a corresponding diagnostic point table from the point table service 20 based on the data request, the diagnostic point table of the point table service 20 being constructed by the diagnostic point table generator 10 based on the system configuration of a certain system;

[0059] Specifically, the data proxy service 40 detects in real time whether a data request sent by an external device such as other DCS subsystems or a third-party system is received. If received, the corresponding diagnostic point table is determined from the point table service 20 based on the data request.

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

[0061] Optionally, the data proxy service 40 determines a corresponding diagnosis point table from the point table service 20 based on the data request, including:

[0062] The data proxy service 40 determines the system information corresponding to the data to be acquired based on the data request; the data proxy service 40 selects the corresponding diagnosis point table from the point table service 20 using the system information.

[0063] Specifically, the data proxy service 40 obtains the system information corresponding to the data to be obtained from the data request; and uses the system information to traverse the point table service 20 to determine the diagnosis point table corresponding to the system information.

[0064] It should be noted that the system information includes information that can identify the system, such as a system ID.

[0065] Optionally, the diagnostic point table generator 10 is specifically used for:

[0066] When a system is detected to be started, the creation of a diagnostic point table is triggered; the system configuration data of the system is obtained; the system configuration data is input into a multi-level creation model so that the multi-level creation model processes the system configuration data and determines a corresponding diagnostic point table. The system information of the system and the corresponding diagnostic point table are input into the point table service 20 for storage.

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

[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 devices constituting the system, the components under the devices, and the association relationship between the subcomponents under the components;

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

[0071] That is, the next-level association of a component is the subcomponent connected to it or set within the component; conversely, the previous-level association of a subcomponent is the corresponding component.

[0072] The multi-level creation model is constructed by a main thread, a first-level processing thread, a second-level processing thread, ... and an N-level 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 a multi-level creation model so that the multi-level creation model processes the system configuration data and determines 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 at different levels; calls the corresponding level processing thread to process the system configuration nodes at the corresponding level to construct the diagnostic point field of each system configuration node; and constructs the 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, first determine 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, it is used 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 used as a system configuration node of level X+1, and so on, until the level of each system configuration node is determined. The corresponding level processing thread processes the system configuration node of the corresponding level to construct the diagnostic point field of each system configuration node.

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

[0078] For each level of system configuration node, execute the corresponding level processing thread; determine whether the diagnostic point information exists based on the keyword corresponding to the system configuration node; if so, use the domain address and station address corresponding to the system configuration node as the diagnostic address; combine the role, diagnostic address and diagnostic point information corresponding to the keyword to obtain the diagnostic point field of the system configuration node.

[0079] Specifically, first, for each level of system configuration node, the diagnostic point table generator 10 calls each level of processing thread for parallel execution in the multi-level creation model, so that the first-level processing thread processes the first-level system configuration node, the second-level processing thread processes the second-level system configuration node, and so on, the N-level processing thread processes the N-level system configuration node.

[0080] Next, extract the keyword corresponding to the system configuration node, query the correspondence between the preset keyword and the diagnostic point information, determine whether there is diagnostic point information corresponding to the keyword corresponding to the system configuration node, if so, it means that the system configuration node may have diagnostic point information, obtain the domain address and station address corresponding to the hierarchical system configuration node in the system, and use the domain address and station address as the diagnostic address of the system configuration node;

[0081] Finally, first search for the role corresponding to the keyword in the system configuration node; and obtain the diagnostic point information corresponding to the role, for example, the diagnostic point information corresponding to the role operation node includes CPU load and CPU load alarm status; then, combine the role, diagnostic address and diagnostic point information 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 pre-set based on multiple experiments or experience.

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

[0084] Diagnostic points are suspicious points that may cause system abnormalities. They are generally CPU load, CPU load alarm status, data service status, operating status, network status, address conflicts, etc., which are all suspicious points that may cause system bottlenecks.

[0085] The diagnostic point location 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 proxy service, and parses the data request using the diagnostic point table corresponding to 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 proxy service 40; searches the diagnostic point table for a diagnostic point field corresponding to the data request; and determines 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 obtains the diagnostic point table determined by the data proxy service 40; determines whether there is a role corresponding to the diagnostic point table using the keyword in the data request; if so, further traverses the diagnostic point field corresponding to the role in the diagnostic point table according to the specific request data to determine whether there is the same diagnostic point information as the specific request data; if so, obtains the diagnostic point field corresponding to the data request from the diagnostic point table;

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

[0090] In an embodiment of the present invention, a diagnostic point table of a corresponding system is first constructed based on the system configuration of a certain system, so that the diagnostic point table has high readability. And the constructed diagnostic point table is a soft point table, so that system resources do not need to be occupied. When a 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 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, and the diagnostic data corresponding to the data request is obtained, and output to the external device through the data proxy service. This allows the external device to quickly query the data in the diagnostic subsystem through the device address information and diagnostic point information.

[0091] See also Figure 2 , is a flow chart of a data processing method shown in an embodiment of the present invention, the method comprising:

[0092] Step S201: The data proxy service determines whether a data request input from an external device is received. If received, step S202 is executed. If not, the process returns to step S201.

[0093] In the specific implementation of step S201, the data proxy service detects in real time whether a data request sent by external devices such as other DCS subsystems or third-party systems is received. If received, step S202 is executed; if not, step S201 is continued.

[0094] Step S202: the data proxy service determines a corresponding diagnosis point table from the point table service based on the data request.

[0095] Wherein, 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;

[0096] It should be noted that the specific implementation of step S202 includes the following steps:

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

[0098] In the specific implementation of step S11, the data proxy service obtains system information corresponding to the data to be obtained from the data request;

[0099] It should be noted that the system information includes information that can identify the system, such as a system ID.

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

[0101] In the specific implementation of step S12, the data proxy service uses the system information to traverse the point table service to determine the diagnosis point table corresponding to the system information.

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

[0103] Step S21: When the diagnostic point table generator detects that a certain system is started, the diagnostic point table creation is triggered;

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

[0105] In the process of implementing step S21, for each system, such as system 1, system 2, ... system 3, when the diagnostic point table generator detects that a certain system is started, it automatically creates a diagnostic point table corresponding to the system.

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

[0107] It should be noted that the system configuration data includes the devices constituting the system, the components under the devices, and the association relationship between the subcomponents under the components;

[0108] Furthermore, it should be noted that the device, the components under the device, and the sub-components under the components are all system configuration nodes.

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

[0110] Step S23: inputting the system configuration data into the multi-level creation model so that the multi-level creation model processes the system configuration data and determines a corresponding diagnosis point table.

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

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

[0113] It should be noted that the specific 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 at different levels;

[0115] In the process of specifically 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, it is used 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 used as a system configuration node of level X+1, and so on, until the level of each system configuration node is determined.

[0116] Step S32: the multi-level creation model calls the corresponding level processing thread to process the corresponding level system configuration node to construct the diagnosis point field of each system configuration node;

[0117] It should be noted that the specific implementation of step S32 includes the following steps:

[0118] Step S41: for each level of system configuration node, execute the corresponding level processing thread;

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

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

[0121] Step S42: Determine whether the diagnostic point information exists according to the keyword corresponding to the system configuration node. If yes, execute step S43. 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 abnormality.

[0122] In the process of implementing 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 so, 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 abnormality.

[0123] It should be noted that the process of presetting the correspondence between the keywords and the diagnostic point information includes:

[0124] Conduct multiple experiments on the historical keywords of the system configuration nodes and the historical diagnosis point information of the system to determine the corresponding relationship between different keywords and diagnosis point information and store them.

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

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

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

[0128] It should be noted that each character has different keywords, and the keywords for each character are set in advance after multiple experiments.

[0129] In the process of implementing step S44, first find the role corresponding to the keyword in the system configuration node; and obtain the diagnostic point information corresponding to the role. For example, the diagnostic point information corresponding to the role operation node includes CPU load and CPU load alarm status; then, combine the role, diagnostic address and diagnostic point information 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 based on multiple experiments or experience.

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

[0132] Diagnostic points are suspicious points that may cause system abnormalities. They are generally CPU load, CPU load alarm status, data service status, operating status, network status, address conflicts, etc., which are all suspicious points that may cause system bottlenecks.

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

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

[0135] Table (1):

[0136]

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

[0138] It should be noted that the diagnostic information corresponding to the same role in different systems is the same, but the diagnostic information corresponding to different roles is different.

[0139] It should be noted that the process of processing the system configuration node of the corresponding level by each level processing thread is the same. Based on this, the process of processing the level 2 system configuration node by the level 2 processing thread is taken as an example for description.

[0140] Specifically, for each secondary system configuration node, a secondary level processing thread is executed to determine whether the diagnostic point information may exist based on the keyword corresponding to the secondary system configuration node. If so, the domain address and station address corresponding to the secondary system configuration node are used as the corresponding diagnostic address. Then, the role, diagnostic address and diagnostic point information corresponding to the keyword are combined to obtain the diagnostic point field of the secondary configuration node.

[0141] If it does not exist, it means that the current secondary system configuration node does not have diagnostic point information, that is, the secondary system configuration node will not affect the system abnormality.

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

[0143] In the specific implementation of step S33, each level processing thread in the multi-level creation model constructs a corresponding diagnostic point table based on the diagnostic point positions of the corresponding level obtained by its own processing.

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

[0145] Among them, the diagnostic point table is not stored in the disk, but 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 set outside the disk and has a certain storage memory built in to store the system information of different systems and the corresponding relationship between the diagnostic point tables.

[0146] Step S203: the diagnostic data reference service obtains the diagnostic point table determined by the data proxy service, and parses the data request 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 specific implementation of step S203 includes the following steps:

[0148] Step S51: the diagnostic data reference service obtains the diagnostic point table determined by the data proxy service;

[0149] Optionally, the data proxy service sends the diagnostic point table corresponding to the data request to the diagnostic data reference service so that the diagnostic data reference service can reference it.

[0150] Step S52: Check whether there is a diagnostic point field corresponding to the data request in the diagnostic point table. If yes, execute step S53; if no, execute step S54;

[0151] In the specific implementation of step S52, the keyword in the data request is used to determine whether there is a role corresponding to the diagnostic point table. If so, the diagnostic point field corresponding to the role in the diagnostic point table is traversed according to the specific request data in the data request to determine whether there is the same diagnostic point information as the specific request data. If so, step S53 is executed. If not, the data request is marked so that the corresponding diagnostic point table is subsequently optimized based on the data request.

[0152] Step S53: Determine the device address information and the diagnostic point information based on the diagnostic point field corresponding to the data request in the diagnostic point table.

[0153] In the specific implementation of step S53, the diagnostic point field corresponding to the data request is obtained from the diagnostic point table. For example, the diagnostic point field may be NODE_001_129_CPU, ie, the CPU load condition of the operation node at address 0.129.

[0154] Next, the corresponding device address information, ie, the diagnostic address 001_129, and the diagnostic point information, ie, the CPU in the diagnostic point field, are obtained from the diagnostic point field.

[0155] Optionally, the diagnostic subsystem stores a diagnostic data block for each diagnostic point, and each data block creates unique index information based on the device address information;

[0156] Step S54: querying a preset regular point table to determine a table data address corresponding to the data request, and using the table data address to query a system database to obtain 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 determine the system information corresponding to the data to be obtained through step S31; then use the system information to select the corresponding regular point table from the point table service, and query the data address corresponding to the data request in the regular point table, 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 as follows: the multi-level creation model splits the system configuration data to obtain system configuration nodes of different levels; calls the corresponding level processing thread to process the corresponding level system configuration nodes to construct the data address of each system configuration node; and constructs the corresponding regular point table based on the data address of each system configuration node.

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

[0161] It should be noted that the specific process of implementing steps S51 to S54 can be seen in the attached Figure 4 To illustrate, a corresponding diagnostic point table is constructed by a diagnostic point table generator, and a conventional point table is constructed at the same time.

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

[0163] In the specific implementation of step S204, the diagnostic data reference service quickly maps the diagnostic data block in the diagnostic subsystem through the device address, and obtains the block offset of the diagnostic data block through the diagnostic point information, thereby quickly obtaining the diagnostic data. Figure 5 shown.

[0164] In an embodiment of the present invention, a diagnostic point table of a corresponding system is first constructed based on the system configuration of a certain system, so that the diagnostic point table has high readability. And the constructed diagnostic point table is a soft point table, so that system resources do not need to be occupied. When a 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 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, and the diagnostic data corresponding to the data request is obtained, and output to the external device through the data proxy service. This allows the external device to quickly query the data in the diagnostic subsystem through the device address information and diagnostic point information.

[0165] An embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory is used to store data processing program code and data, and the processor is used to call program instructions in the memory to execute the steps shown in the data processing method in the above embodiment.

[0166] An embodiment of the present invention provides a storage medium, which includes the electronic device provided by the above-mentioned embodiment of the present application, and the electronic device is used to execute the data processing method disclosed in the embodiment of the present application.

[0167] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0168] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0169] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A data processing method, characterized in that: Applied to a DCS system, 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 an external device and the diagnostic data reference service respectively, the diagnostic data reference service is connected to the point table service, and the method includes: If the data proxy service detects a data request input by the external device, the data proxy service determines a corresponding diagnostic point table from the point table service based on the data request, wherein 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 parses the data request using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information; The diagnostic data reference service queries the diagnostic subsystem based on the device address information and the diagnostic point information, obtains the diagnostic data corresponding to the data request, and outputs it to the external device through the data proxy service.

2. The method according to claim 1, characterized in that The data proxy service determines a corresponding diagnosis 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 acquired based on the data request; The data proxy service selects a corresponding diagnosis point table from the point table service using the system information.

3. The method according to claim 1, characterized in that The process of building a diagnostic point table based on the system configuration of a system includes: When the diagnostic point table generator detects that a certain system is started, the diagnostic point table creation is triggered; Obtaining 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 and determines a corresponding diagnostic point table; The system information of the system and the corresponding diagnostic point table are input into the point table service for storage.

4. The method according to claim 3, characterized in that: Inputting the system configuration data into a multi-level creation model so that the multi-level creation model processes the system configuration data and determines a corresponding diagnostic point table, including: The multi-level creation model splits the system configuration data to obtain system configuration nodes at different levels; Calling a corresponding level processing thread to process a corresponding level system configuration node to construct a diagnosis point field of each system configuration node; A corresponding diagnosis point table is constructed based on the diagnosis point field of each system configuration node.

5. The method according to claim 4, characterized in that Call the corresponding level processing thread to process the corresponding level system configuration node to construct the diagnostic point field of each system configuration node, including: For each level of system configuration nodes, execute the corresponding level processing threads; Determine whether the diagnostic point information exists according to the keyword corresponding to the system configuration node; If so, the domain address and station address corresponding to the system configuration node are used as the diagnostic address; The role, diagnosis address and diagnosis point information corresponding to the keyword are combined to obtain the diagnosis point field of the system configuration node.

6. The method according to claim 1, characterized in that The diagnostic data reference service obtains the diagnostic point table determined by the data proxy service, and parses the data request using the diagnostic point table corresponding to the data request to obtain device address information and diagnostic point information, including: The diagnostic data reference service obtains the diagnostic point table determined by the data proxy service; Find out whether there is a diagnosis point field corresponding to the data request in the diagnosis point table; 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.

7. 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, wherein the diagnostic point table generator is connected to the diagnostic subsystem and the point table service respectively, the data proxy service is connected to an external device and the diagnostic data reference service respectively, and the diagnostic data reference service is connected to the point table service; The data proxy service is used for, if a data request input by the external device is detected, the data proxy 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 being constructed by the diagnostic point table generator based on a system configuration of a certain system; The diagnostic data reference service is used to obtain the diagnostic point table determined by the data proxy service, and use the diagnostic point table corresponding to the data request to parse the data request to obtain device address information and diagnostic point information; query the diagnostic subsystem based on the device address information and diagnostic point information, obtain the diagnostic data corresponding to the data request, and output it to the external device through the data proxy service.

8. The DCS system according to claim 7, characterized in that: The diagnostic point table generator is specifically used for: When a system is detected to be started, the creation of the diagnostic point table is triggered; Obtaining 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 and determines a corresponding diagnostic point table; The system information of the system and the corresponding diagnostic point table are input into the point table service for storage.

9. An electronic device, characterized in that: The electronic device is used to run a program, wherein the program executes the data processing method according to any one of claims 1 to 6 when running.

10. A storage medium, characterized in that: The storage medium includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the data processing method according to any one of claims 1 to 6.

Images