An object-oriented method for classification and communication of power data

Abstract

The present invention relates to an object-oriented method for power data classification and communication. The present invention specifically discloses step 1, abstractly defining and instantiating power business data based on a pre-established XML configuration file to generate instantiated data; step 2, realizing communication interaction of the instantiated data based on a specific communication protocol and the XML configuration file, or filtering and classifying data based on the instantiated data, generating and displaying classified data. Based on the method of the present invention, the coupling degree between data model and business processing and data communication can be better reduced, the workload of repeated development can be reduced, and the scalability of the program can be improved.

Description

Technical Field

[0001] The present invention relates to the field of electric power automation, and more specifically, to the field of object-oriented electric power data classification and electric power data communication. Background Art

[0002] With the continuous improvement of the degree of power automation, power data has become more diverse. In power automation applications, through public protocols such as IEC (International Electrotechnical Commission) 61850 (international standard for substation automation system based on a common network communication platform), IEC608875-5-103 (supporting standard for information interface of relay protection equipment), etc., the data of various power equipment are unified and standardized. Communication technology has become relatively mature and stable. However, the interaction of data within the device is still limited by hardware resources, software platforms, development and maintenance costs, etc., which makes most manufacturers tend to adopt customized data management and interaction strategies based on their own software and hardware platforms.

[0003] In the development process of data interaction and processing, different data determines different business processing, different data has different attributes and processing methods, and the data structure and communication methods are diverse. At present, most data processing and interaction methods are customized, and a data structure corresponds to a specific communication method and business processing flow. This leads to the problem of changing multiple links of the program when adding new data structures or new requirements.

[0004] Therefore, in order to reduce the coupling between data models, business processing and data communication, reduce repetitive development workload, and improve program scalability, it is an inevitable choice to classify data and process them in a unified manner. Summary of the invention

[0005] In order to solve the deficiencies in the prior art, the purpose of the present invention is to provide an object-oriented method for power data classification and communication, which can abstract different types of business data into objects, process power data through instantiation configuration and screening classification, and rely on communication protocols for data interaction.

[0006] The present invention adopts the following technical solution.

[0007] An object-oriented method for power data classification and communication comprises the following steps: step 1, abstractly defining and instantiating power business data based on a pre-established XML configuration file to generate instantiated data; step 2, realizing communication interaction of instantiated data based on a specific communication protocol and XML configuration file, or filtering and classifying data based on instantiated data, generating and displaying classified data.

[0008] Preferably, step 1 also includes: step 101, abstractly defining the attributes and hierarchical structure of the power business data; step 102, setting attribute values ​​for the data template nodes to instantiate the abstract data template and generate instantiated data.

[0009] Preferably, step 101 also includes: defining a data template node and establishing a data template node identifier; defining an abstracted business data object node according to the attributes and commonalities of the business data to identify the power data block, as well as the data groups and data points in the data block.

[0010] Preferably, step 102 also includes: defining a data instantiation node and establishing a data instantiation node identifier; setting attribute values ​​and adding descriptions for abstract business data objects to instantiate the business data objects and generate instantiation data, wherein the instantiation data includes data block attributes, data group attributes and data point attributes.

[0011] Preferably, the communication interaction of instantiated data based on a specific communication protocol and an XML configuration file in step 2 also includes: sending, receiving and parsing data based on the index number of the object identifier, group identifier and point identifier of the instantiated data and the data length of the data block.

[0012] Preferably, in step 2, filtering and classifying data based on instantiated data, generating and displaying classified data also includes: establishing filtering conditions according to attribute values, matching different objects in the instantiated data, and classifying and displaying different objects in the instantiated data.

[0013] Preferably, a data classification node is defined to establish filtering conditions based on specific grammatical rules and attribute values ​​of business data objects; an object is established in the data classification node to identify filtering conditions for data blocks, filtering conditions for data groups, and filtering conditions for data points; and data object nodes, data group nodes, and data point nodes that meet the filtering conditions are matched.

[0014] Preferably, the pre-established XML configuration file includes node definitions, node names, attribute names and hierarchical structures.

[0015] Preferably, the node definition includes data template nodes, data instantiation nodes and data classification nodes; the node name includes a node name keyword for identifying the node; the attribute name includes an attribute name keyword, a position, a name and an index number, wherein the attribute name keyword is used to identify the attribute, the position includes the placement order of the attribute, the name includes the XML attribute name corresponding to the fixed keyword, and the index number includes the XML fixed attribute corresponding to the node; the hierarchical structure includes data object nodes, data group nodes, and data point nodes, wherein the data object node contains a set of specific data group nodes, the data group node contains a set of specific data point nodes, and the data point node contains a set of specific data structures and attributes.

[0016] The beneficial effect of the present invention is that, compared with the prior art, the object-oriented method of power data classification and communication in the present invention reduces the coupling degree between data model and business processing and data communication, reduces the repeated development work before power data fusion processing, and improves development efficiency. The method of the present invention for data classification and communication has good system stability, portability and data scalability.

[0017] The beneficial effects of the present invention also include:

[0018] 1. The present invention uses object-oriented thinking to abstract different types of business data into different objects, uses inheritance thinking to unify the common attributes between data, and classifies different types of business data. Based on the extensive development support advantage of XML, the XML configuration file can be redeveloped at any time, reducing duplication of work and improving development efficiency.

[0019] 2. The present invention cooperates with specific communication protocols for data interaction, reduces the coupling degree between data communication and processing, and improves the scalability of data. When adding new data categories, it is only necessary to find the template corresponding to the data to instantiate the new data. At the same time, the power data can also be imported into the database for reference at any time.

[0020] 3. The power business data of the present invention can be reconstructed through an object-oriented method and transmitted in accordance with the communication protocol, so there is no need to change the internal structure of the power protection device, and no customized module is required to modify the original data, thereby simplifying the data communication and management within the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A flow chart of a method for power data classification and communication in the present invention;

[0022] Figure 2 A schematic diagram of the structure of a data node in a method for power data classification and communication in the present invention;

[0023] Figure 3 A flowchart of a method for generating instantiated data in a method for classifying and communicating power data in the present invention;

[0024] Figure 4 It is a schematic diagram of realizing communication interaction in a method for power data classification and communication in the present invention. DETAILED DESCRIPTION

[0025] The present application is further described below in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and cannot be used to limit the protection scope of the present application.

[0026] Figure 1 FIG. 1 is a flow chart of a method for power data classification and communication in the present invention. Figure 1 As shown, an object-oriented method for power data classification and communication includes steps 1 and 2.

[0027] Step 1: Based on a pre-established XML (Extensible Markup Language) configuration file, abstract definition and instantiation configuration are performed on the power business data to generate instantiation data.

[0028] XML can be used to mark data and define data types. It is a source language that allows users to define their own markup languages. Therefore, XML is very suitable for reclassifying power data with diverse structures and sources, and is also very suitable for solving the problems of diverse data structures and high repeated development costs in the existing power data classification and communication process.

[0029] The XML configuration file is generated in advance by the device developers according to the functions of the power device using the XML extensible markup language. Figure 2 FIG. 1 is a schematic diagram of the structure of a data node in a method for power data classification and communication in the present invention. Figure 2 As shown, the pre-built XML configuration file includes node definition, node name, attribute name and hierarchical structure.

[0030] Preferably, the node definition includes a data template node, a data instantiation node and a data classification node. In one embodiment of the present disclosure, the above nodes can be defined as ObjectLib, ObjectCaseDB and DataClassification respectively using XML language. The above nodes are used for abstract definition, instantiation configuration and screening and classification of power business data respectively. Among them, the data classification node also includes a data screening rule node and a data classification node result set. The data screening rule node is used to classify the instantiated data, and the data classification node result set records the classified data after screening. The role of the above nodes and the method for reclassifying data are described in detail in the following content of the present disclosure.

[0031] Preferably, the node name includes a node name keyword for identifying the node. That is, the node name specifically refers to the name description of the node, which is used as a keyword for semantic identification.

[0032] Preferably, the attribute name includes attribute, position, name and index number. The attribute field is a series of nodes containing fixed attributes and different attribute values. For example, in the Config_pt attribute node, a set of fixed attributes and Val nodes with different keywords are included, where ord is a fixed attribute description, and the semantic identification of specific attributes is performed based on different values ​​in the ord attribute as keywords. The position includes the order of placement of the attributes, the name includes the fixed keywords corresponding to the XML attributes, and the index number includes the XML fixed attributes corresponding to the node.

[0033] Preferably, the hierarchical structure includes data object nodes, data group nodes, and data point nodes, wherein the data object nodes contain a set of specific data group nodes, the data group nodes contain a set of specific data point nodes, and the data point nodes contain a set of specific data structures and attributes.

[0034] Among them, power business data refers to the data in the power protection device. The data is usually modified by a customized module in the power protection device to implement data structure or data format, and then communicated and transmitted within the device, for example, from a data acquisition unit in the device to a data management unit in the device. In the present invention, power business data can be considered as raw data directly generated by the power protection device. Since the power business data in the present invention can be reconstructed through an object-oriented method and adapted to the communication protocol for transmission, there is no need to change the internal structure of the power protection device, and there is no need for a customized module to modify the raw data.

[0035] Based on XML language, the power business data can be structured and arranged through hierarchical structure, abstraction and instantiation, so as to realize the structured and visual configuration of data. Through screening and classification, the power business data can be converted into classified data distinguished by different attributes or combinations of different attributes.

[0036] The classified data is generated by reasonably dividing the power business data in the XML configuration file. The XML configuration file may include standardized classified data processing rules, which are specifically defined by data template nodes and data classification nodes. These defined templates can also form a public resource library for use in other power grid systems to achieve the reuse of data classification rules.

[0037] Figure 3 The flowchart of the instantiation data generation method in the method of power data classification and communication in the present invention is as follows. Figure 3 As shown, step 1 further specifically includes step 101 to step 102. In step 101, the attributes and hierarchical structure of the power business data are abstractly defined.

[0038] The process of abstract definition is to divide the power business data according to common attributes, etc., and store it in the data template node in the hierarchical structure of the data object template.

[0039] Specifically, step 101 includes: defining a data template node and establishing a data template node identifier; defining an abstract business data object node according to the attributes and other commonalities of the business data to identify the power data block, as well as the data groups and data points in the data block.

[0040] In the data template node, the power business data can be divided and the business data objects can be defined.

[0041] The data object template node Resource consists of a template identifier and multiple specific attributes to identify the template available in the XML configuration file. The template identifier can be used to locate the unique address of each template object, so as to manage the template object. Multiple specific attributes identify the attributes that the data using the template should have.

[0042] In one embodiment of the present disclosure, the hierarchical structure of the data object template node Resource is that each object template node Resource includes multiple groups Param, and each group includes multiple data points Content. Each data object template node can be used to describe the hierarchical structure of a power data block and its abstract attributes.

[0043] In one embodiment, when a data block is an alarm block, a business data object of the alarm block is defined, and the business data object of the alarm block has two business data groups, namely, the logical address group and the specific alarm definition group. The specific alarm definition group includes multiple business data points, namely, alarm points, which can contain specific attribute information such as a table number and an alarm type.

[0044] In another embodiment, the data information of an input board is a business data object, a business data group under the object identifies the logical address of the board, and another business data group is specifically used to identify the information of the input point on the input board. The business data point under the business data group specifically includes the information of each input point.

[0045] Each data object template node can also be a collection of business data objects with common fixed attribute identifiers and other business commonalities. Each business data object also includes multiple business data groups, each of which can be a collection of attribute classifications; each business data group also includes multiple business data points, and each business data point as a leaf node of the business data group can be a single attribute.

[0046] In another embodiment of the present disclosure, in the data object template node, the definition of some specific attributes is included. These attributes can semantically identify the XML configuration file, and these attributes are valid in the entire XML configuration file. In one embodiment, the specific attributes include ID, key, guid, Mtype, offset, dt_size, datatype, config_pt, etc. Each of the specific attributes indicates a specific meaning. For example, the ID attribute represents the identifier of the template. The Key attribute represents the string identifier of the template. The guid attribute represents the connection address of the multilingual entry. Therefore, the unique information of the multilingual entry can be obtained based on the guid attribute information and the language currently set by the system. Mtype represents the classification information of the template. The offset attribute represents the offset of the data in a data node in the group to which it belongs. The dt_size attribute represents the size of the data in a data node. The datatype attribute represents the type of data in a data node. The Config_pt attribute represents the attributes of configuring a data node.

[0047] According to the template information in the pre-established XML configuration file, the attributes and hierarchical structure of the power business data are abstractly defined to obtain abstract data. The abstract data is stored in the form of hierarchical and attribute-based data templates according to the hierarchical structure in the XML configuration file.

[0048] Preferably, step 102 is to set attribute values ​​for the data template node to instantiate the abstract data template and generate instantiated data. In the data instantiation node, specific attribute values ​​and descriptions can also be assigned to the abstract data through instantiation configuration.

[0049] Preferably, step 102 also includes: defining a data instantiation node ObjectCaseDB and establishing a data instantiation node identifier; setting attribute values ​​and adding descriptions for abstract business data objects to instantiate the business data objects and generate instantiation data, wherein the instantiation data includes data block attributes, data group attributes and data point attributes.

[0050] Specifically, a data object instantiation node ObjectCase can be established based on the data template node, and specific content can be assigned to the data object instantiation node. According to the properties of the instantiation configuration, a data template node can be derived into multiple data object instantiation nodes. After the data object instantiation node is established, node properties such as offset and size can be added according to the specific content of the node and the position of the node. According to the actual application requirements of the power business, a function activation attribute can be added to the instantiation node to modify the state of the node to make it activated or inactivated. In order to describe the inheritance relationship between nodes, a parent node identification attribute (ParentID) can also be added, and the relationship between nodes can be described through this attribute. At the same time, for all abstract data from the data object template node, the data object instantiation node can selectively instantiate the above data according to the different template attributes in the above data.

[0051] Under each data object instantiation node ObjectCase, there may be multiple group nodes Param, which are used to identify the attribute family of the instantiated object, that is, the attribute classification set of the object. Under each group node, there may be multiple data point nodes Content, which are used to identify the specific attributes of the instantiated data point. The specific attributes may include the value attribute, configuration attribute, display attribute, logical operation attribute, and single and double point attributes of the parent class template. For example, after the alarm block is abstracted through the data template node, the alarm block can be further instantiated and configured through the instantiated object node. In the data point node of each alarm block instantiated object, the initialization state of the alarm and the identification information of the alarm can be instantiated.

[0052] It is worth noting that in the power business processing flow, these attributes can be obtained at any time according to business needs. The above configurable attributes are all static attributes, that is, the above attributes cannot be modified at will during operation.

[0053] Step 2: Implement communication interaction of classified data based on specific communication protocols and XML configuration files.

[0054] Figure 4 FIG. 1 is a schematic diagram of realizing communication interaction in a method for power data classification and communication in the present invention. Figure 4 As shown, after the power business data is generated into instantiated data through abstract definition and instantiated configuration, the classified data can be interacted through a specific communication protocol according to the hierarchical structure of the XML configuration file.

[0055] Preferably, data transmission, data reception and data parsing are performed based on the index numbers of the object identification, group identification and point identification of the instantiated data and the data length of the data block.

[0056] Specifically, according to a specific communication protocol, the data transmitter or power equipment can send data according to the three-segment index number and data length in the classification set node. Similarly, the data receiver can also obtain corresponding data attributes, such as data length, from the same XML configuration file according to the index number, so as to reasonably receive and parse the data.

[0057] A specific communication protocol refers to a data communication method that is compatible with a pre-generated XML configuration file. Generally speaking, the definition of a communication protocol includes an address block and a data block. The address block is a three-segment index number, which corresponds to the three-segment index number in the classified data, and includes the object identification index, group identification index, and point identification index of the instantiated data. The data content for transmission can be obtained through the above three-segment index number. Similarly, when the data sending end obtains the data content and packages it for transmission according to the three-segment index number in the communication protocol, the data receiving end can also obtain the three-segment index number from the received package content, and query the node corresponding to the three-segment index number from the instantiated data according to the same XML configuration file, and parse the data packet.

[0058] The data block included in the definition of the communication protocol is composed of a 2-byte data length and a data area of ​​dynamic length. The total length of the data block is the data length. Usually, the data block is generated by packaging the group in the XML configuration file as the smallest unit. The size of the data can be determined by the dt_size attribute of each object node. By instantiating the offset attribute of each object node in the data, the offset of the data in the node can be determined, thereby determining the storage location. In one embodiment, the group node records the information of each input point in an input board. In this group of data, the size of each input point is 1 byte, that is, dt_size can be set to 1. Without considering data alignment, the data offset of the node where each input point data is located is added by 1 starting from 0, so the offset attribute of each data point node can also be set to 0, 1, 2, ...

[0059] Similarly, data transmission is also carried out in groups as the smallest unit. The size of the data to be transmitted is determined according to the dt_size attribute, and the offset of the data to be transmitted in the group to which it belongs is determined according to the offset attribute. Then the data is framed and the frame data is used for transmission. Similarly, during data parsing, the method of deframing the data can be determined according to the dt_size attribute and the offset attribute. During data parsing, the datatype attribute in the node can also be referred to. This attribute defines the data type of the data in the node, and the data can be parsed according to the corresponding data type through this attribute.

[0060] In addition to using instantiated data for communication transmission, instantiated data can be filtered and classified to form classified data and displayed in an XML interface.

[0061] Preferably, a screening condition is established according to the attribute value, different objects in the instantiated data are matched, and the different objects in the instantiated data are classified and displayed.

[0062] Specifically, define data classification nodes to establish filtering conditions based on specific grammatical rules and attribute values ​​of business data objects; establish objects in the data classification nodes to identify filtering conditions for data blocks, filtering conditions for data groups, and filtering conditions for data points; and match data object nodes, data group nodes, and data point nodes that meet the filtering conditions.

[0063] In one embodiment of the present invention, a data classification node DataClassification may be defined to establish a screening condition based on a specific grammatical rule and the attribute value of a business data object. The data classification node may establish a screening condition according to the attribute value in the instantiated object node in the data instantiation node.

[0064] The specific grammar rules include a set of keyword combinations of attribute names and attribute values ​​of fixed XML attributes. The specific grammar rules can be set manually according to the characteristics of power business data, and should include all attribute values ​​of business data objects to realize data processing and transmission.

[0065] Generally speaking, the screening conditions may include a screening rule object and a set of screening rule keyword sets. Among them, the keywords in the screening keyword set can be combined arbitrarily, and can also be combined with logical operators such as AND and OR. The combined keywords can match a certain attribute in the business data object. In one embodiment of the present invention, a data screening rule node RuleConfig can be defined in the data classification node, and a data object RuleConfig is established in the node to identify the combination keyword when matching the object attribute. A data group node RuleGrp is established in the object to identify the combination keyword when matching the group attribute, and a data point Rule is established in the group to identify the combination keyword when matching the data point attribute.

[0066] In one embodiment, the filter condition may be composed of a set of attribute keywords and attribute values. For example, the filter condition may be set to "<Rule ID="1"oper="AND"Object_Mtype="0.2.2" / > ”.

[0067] Therefore, according to the screening condition, that is, the combined keyword, an association relationship can be established between the attributes of the business data object, and the business data objects with the established association relationship can be screened out. Among them, "oper" represents a logical operator, and the logical operator can be AND or OR. In the present disclosure, "oper="AND"" is used, which means that AND is selected as the logical operator. The other two keywords are RuleID and Object_Mtype, where "Rule ID="1"" represents a node with a data point identifier of 1, and Object_Mtype indicates that the attribute value of the attribute Mtype in the object Object should be 0.2.2. Through this screening condition, all object nodes that meet the screening condition can be found from the instantiated data. Similarly, screening conditions can be set for data group nodes and data point nodes, and all data group nodes and all data point nodes that meet the conditions can be matched, and all nodes are temporarily stored as a category in the classified data.

[0068] The instantiated data filtered out according to the filtering conditions defined by the data filtering rule node can be uniformly stored in the data classification node result set Datasets. By establishing a data classification node result set under the data classification node, the addresses of the filtered instantiated data can be uniformly stored. The three-segment identification index consists of the index numbers of the instantiated object identifier, the instantiated group identifier, and the instantiated data point identifier. Through the indexes of the above three identifiers, the specific content indicated by the data can be found. Among them, the index refers to the fixed XML attributes on the object node, group node, and data point node.

[0069] The group node SdmProtocol under the object node has an addr attribute. This attribute is used to identify the CPU address number corresponding to the node. When the node exists in multiple logical addresses at the same time, this attribute can be used to distinguish nodes under different logical addresses. The data point node DataContent under the data group node also has a sequence attribute. This attribute can be used to sort the display order of the data point nodes. Since the sequence attribute is only used to define the display order of the data point nodes rather than the communication order, this attribute is often used to achieve logical isolation between data communication and data display.

[0070] The data classification node can also have a node attribute RelateTableRule, the value of which should be a fixed and unchangeable keyword. For example, if the value of the node attribute is set to "PROT_SetValue", a type of classification data under the node should be a protection value. When sending, receiving or parsing the data, the classification data can be batch processed according to the business logic of the protection value.

[0071] The beneficial effect of the present invention is that, compared with the prior art, the object-oriented method of power data classification and communication in the present invention reduces the coupling degree between data model and business processing and data communication, reduces the repeated development work before power data fusion processing, and improves development efficiency. The method of the present invention for data classification and communication has good system stability, portability and data scalability.

[0072] The beneficial effects of the present invention also include:

[0073] 1. The present invention uses object-oriented thinking to abstract different types of business data into different objects, uses inheritance thinking to unify the common attributes between data, and classifies different types of business data. Based on the extensive development support advantage of XML, the XML configuration file can be redeveloped at any time, reducing duplication of work and improving development efficiency.

[0074] 2. The present invention cooperates with specific communication protocols for data interaction, reduces the coupling degree between data communication and processing, and improves the scalability of data. When adding new data categories, it is only necessary to find the template corresponding to the data to instantiate the new data. At the same time, the power data can also be imported into the database for reference at any time.

[0075] 3. The power business data of the present invention can be reconstructed through an object-oriented method and transmitted in accordance with the communication protocol, so there is no need to change the internal structure of the power protection device, and no customized module is required to modify the original data, thereby simplifying the data communication and management within the device.

[0076] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation schemes of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, but not to limit the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present invention.

Claims

1. An object-oriented method for power data classification and communication, characterized in that: The method comprises the following steps: Step 1: abstractly define and instantiate the power business data based on the pre-established XML configuration file to generate instantiated data; The abstract definition is used to divide the power business data according to common attributes, and store the power business data in a data template node in a hierarchical structure of a data object template; The data object template node is composed of a template identifier and a plurality of the common attributes, and is used to describe the power data block; The instantiation configuration is used to establish a data object instantiation node according to the data template node, so as to derive a data template node into multiple data object instantiation nodes, and to add a function activation attribute to each instantiation node according to the application requirements of the power business; Step 2, realizing communication interaction of the instantiated data based on a specific communication protocol and the XML configuration file, or filtering and classifying data based on the instantiated data, generating and displaying classified data; The specific communication protocol defines an address block, which includes a three-segment index number. The three-segment index number corresponds one-to-one to the object identification index, group identification index and point identification index in the classified data, so as to obtain the data content to be transmitted and package it for sending.

2. According to the object-oriented method for power data classification and communication as described in claim 1, it is characterized in that: The step 1 also includes: Step 101, abstractly define the attributes and hierarchical structure of the power business data; Step 102, setting attribute values ​​for the data template nodes to instantiate the abstracted data template and generate instantiated data.

3. According to the object-oriented method for power data classification and communication as described in claim 2, it is characterized in that: The step 101 further includes: Define data template nodes and establish data template node identifiers; Abstracted business data object nodes are defined according to the attributes and commonalities of the business data to identify power data blocks, as well as data groups and data points in the data blocks.

4. The object-oriented method for power data classification and communication according to claim 3, characterized in that: The step 102 further includes: Define data instantiation nodes and establish data instantiation node identifiers; Attribute values ​​are set and descriptions are added for the abstracted business data object to instantiate the business data object and generate instantiation data, wherein the instantiation data includes data block attributes, data group attributes and data point attributes.

5. The object-oriented method for power data classification and communication according to claim 4, characterized in that: The step 2 of implementing the communication interaction of the instantiated data based on the specific communication protocol and the XML configuration file also includes: Data sending, data receiving and data parsing are performed based on the index numbers of the object identification, group identification and point identification of the instantiated data and the data length of the data block.

6. The object-oriented method for power data classification and communication according to claim 4, characterized in that: In the step 2, screening and classifying the data based on the instantiated data, generating and displaying the classified data also includes: Establish filtering conditions based on attribute values, match different objects in the instantiated data, and classify and display different objects in the instantiated data.

7. The object-oriented method for power data classification and communication according to claim 6, characterized in that: Defining data classification nodes to establish screening conditions based on specific grammatical rules and attribute values ​​of the business data objects; Creating objects in a data classification node to identify filter conditions for data blocks, filter conditions for data groups, and filter conditions for data points; Match the data object nodes, data group nodes and data point nodes that meet the filtering conditions.

8. The object-oriented method for power data classification and communication according to claim 1, characterized in that: The pre-established XML configuration file includes node definitions, node names, attribute names and hierarchical structures.

9. The object-oriented method for power data classification and communication according to claim 8, characterized in that: The node definition includes a data template node, a data instantiation node and a data classification node; The node name includes a node name keyword, which is used to identify the node; The attribute name includes an attribute name keyword, a position, a name, and an index number, wherein the attribute name keyword is used to identify the attribute, the position includes the placement order of the attribute, the name includes the XML attribute name corresponding to the fixed keyword, and the index number includes the XML fixed attribute corresponding to the node; The hierarchical structure includes data object nodes, data group nodes, and data point nodes, wherein: The data object node contains a set of specific data group nodes, the data group node contains a set of specific data point nodes, and the data point node contains a set of specific data structures and attributes.

Images