ICD file generation method and device, computer equipment and storage medium
Patent Information
- Application Number
- CN202280094045.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-22
- Publication Date
- 2024-11-08
AI Technical Summary
In the existing technology, BMS's ICD file generation efficiency is low and error-prone, and cannot be effectively compatible with power energy storage systems from different manufacturers. Moreover, IEC61850 model modeling requires high professionalism and a lot of manual processing, resulting in heavy workload and inconvenient maintenance.
By pre-building multiple information tables with mapping relationships, traversing the data model to determine the target executor and output objects, calling the target executor to automatically generate ICD files, avoiding manual instantiation one by one, reducing error rates and improving versatility.
It improves the accuracy and efficiency of ICD file generation, reduces the coupling between the program and ICD, enhances the versatility of the model, and adapts to the business needs of different application scenarios.
Smart Images

Figure CN118922832A_ABST
Abstract
Description
ICD file generation method, device, computer equipment and storage medium Technical Field
[0001] The present application relates to the field of power system energy storage technology, and in particular to an ICD file generation method, device, computer equipment, storage medium and computer program product. Background Art
[0002] The IEC61850 standard is the only globally accepted standard for power system automation. Through its implementation, it standardizes the engineering operations of smart substations. For example, this includes grid power quality monitoring, line protection, information exchange between substations and between substations and dispatch centers, and power equipment status monitoring. As the IEC61850 standard continues to be finalized, it is being gradually adopted in various applications, including wind farms, distributed energy resources, and hydropower plants.
[0003] The continued expansion of new energy storage systems in power systems has created an urgent need for battery management systems (BMS) to be integrated into the IEC 61850 standard. However, BMS model ICD files are generated manually, resulting in low ICD file generation efficiency.
[0004] Summary of the Invention
[0005] Based on this, it is necessary to provide an ICD file generation method, apparatus, computer device, computer-readable storage medium and computer program product that can solve the low accuracy of ICD files in response to the above technical problems.
[0006] In a first aspect, the present application provides a method for generating an ICD file. The method comprises:
[0007] Acquire a data model including a plurality of information tables corresponding to a hierarchical structure of a battery system model; wherein the plurality of information tables have a mapping relationship between them;
[0008] Traversing each information table of the data model to determine the number of data members and output objects;
[0009] Determine a corresponding number of target execution programs according to the number of data members;
[0010] The target execution program is called to instantiate the output object and generate an ICD file of the battery system model.
[0011] In the above embodiment, when generating a model ICD file, the target object to be instantiated is determined by traversing a pre-built data model. The target object is then instantiated according to a pre-set target execution program, eliminating the need for manual instantiation of each target object. This reduces the error rate and ensures the accuracy of the model ICD file. By instantiating the output object through the target execution program, the model ICD file is automatically generated, avoiding coupling between the program and the ICD and improving the program's versatility.
[0012] In one embodiment, traversing each information table of the data model to determine the number of data members and output objects includes:
[0013] Traversing enabled target information in the first information table according to the mapping relationship between the information tables of the data model;
[0014] The second information table in the data model is traversed according to the enabled target information to determine the number of data members and output objects.
[0015] In the above embodiment, the enabled target information in the first information table is traversed through the mapping relationship between the various information tables of the data model, and the number of data members and the output objects are obtained based on the traversal of the enabled target information. Determining the state and data members to be output based on the data mapping can accurately and quickly determine the state and data members to be output.
[0016] In one embodiment, traversing the second information table in the data model according to the enabled target information to determine the number of data members and the output object includes:
[0017] Traversing the first association information mapped to the enabled target information in the state table of the data model, and determining a state to be output according to the first association information;
[0018] The second association information mapped to the enabled target information in the data table in the data model is traversed, and the data members and the number of data members are determined according to the second association information.
[0019] In the above embodiment, the state table and the data table are traversed separately to obtain the state to be instantiated in the state table and the number of data members in the data table and the data members to be instantiated. There is no need to manually determine the output state to be instantiated and the data members to be instantiated one by one, thereby improving processing efficiency.
[0020] In one embodiment, the calling of the target execution program to instantiate the output object and generate the ICD file of the battery system model includes:
[0021] Determining a mapping data link for the output object; the output object includes a state and a data member;
[0022] Based on the mapping data link, the target execution program is called to instantiate the output object to generate an ICD file of the battery system model.
[0023] In the above embodiment, by determining the mapping data link of the output object and instantiating the output object based on the mapping data link, the ICD file of the battery system model is obtained, which can accurately describe the functions and engineering capabilities of the battery system model.
[0024] In one embodiment, the step of calling the target execution program to instantiate the output object based on the mapping data link to generate the ICD file of the battery system model includes:
[0025] Based on the mapping data link from the access point to each state or data member, the target execution program is called, the address of the output object is written, and the access point, data set name, logical device and logical node associated with the output object are determined to generate an ICD file for the battery system model.
[0026] In the above embodiment, the output object is instantiated based on the mapping data link from the access point to each state or data member to meet the business scenario requirements in the corresponding business scenario.
[0027] In one embodiment, the step of calling the target execution program to instantiate the output object based on the mapping data link to generate the ICD file of the battery system model includes:
[0028] The step of calling the target execution program based on the mapping data link to instantiate the output object and generate the ICD file of the battery system model includes:
[0029] Based on a mapping data link mapping from each state or data member to an access point, the target execution program is called to write the address of the output object and determine the access point, data set name, logical device and logical node associated with the output object to generate an ICD file for the battery system model.
[0030] In the above embodiment, based on the mapping data link from each state or data member to the access point, the business scenario requirements in the corresponding business scenario are met.
[0031] In one embodiment, determining a corresponding number of target execution programs according to the number of data members includes:
[0032] Classifying the data members according to their types to obtain the number of data members of each type;
[0033] Determine the maximum value among the numbers of the data members of each category as the number of target executable programs;
[0034] For each type of data member, determine the corresponding number of target execution programs according to the number of target execution programs.
[0035] In the above embodiment, by classifying the data members, the corresponding number of target execution programs is determined according to the maximum number of each type of data members, and the target execution programs required for each type of data members are accurately determined, thereby avoiding the failure to instantiate all data members, resulting in inaccurate generated ICD files.
[0036] In one embodiment, the method further comprises:
[0037] When an update request is detected, the constructed data model is updated according to the update business requirements carried in the update request.
[0038] In the above embodiment, when the business requirements are updated, the constructed data model is updated according to the business update requirements to adapt to different application scenarios, thereby improving the versatility of the data model.
[0039] In a second aspect, the present application further provides an ICD file generation device. The device comprises:
[0040] A data traversal module is used to obtain a data model of multiple information tables corresponding to the hierarchical structure of the battery system model; the multiple information tables have a mapping relationship;
[0041] Traversing each information table of the data model to determine the number of data members and output objects;
[0042] A matching module, configured to determine a corresponding number of target execution programs according to the number of data members;
[0043] The file generation module is used to call the target execution program to instantiate the output object and generate an ICD file of the battery system model.
[0044] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:
[0045] Acquire a data model including a plurality of information tables corresponding to a hierarchical structure of a battery system model; wherein the plurality of information tables have a mapping relationship between them;
[0046] Traversing each information table of the data model to determine the number of data members and output objects;
[0047] Determine a corresponding number of target execution programs according to the number of data members;
[0048] The target execution program is called to instantiate the output object and generate an ICD file of the battery system model.
[0049] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:
[0050] Acquire a data model including a plurality of information tables corresponding to a hierarchical structure of a battery system model; wherein the plurality of information tables have a mapping relationship between them;
[0051] Traversing each information table of the data model to determine the number of data members and output objects;
[0052] Determine a corresponding number of target execution programs according to the number of data members;
[0053] The target execution program is called to instantiate the output object and generate an ICD file of the battery system model.
[0054] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:
[0055] Acquire a data model including a plurality of information tables corresponding to a hierarchical structure of a battery system model; wherein the plurality of information tables have a mapping relationship between them;
[0056] Traversing each information table of the data model to determine the number of data members and output objects;
[0057] Determine a corresponding number of target execution programs according to the number of data members;
[0058] The target execution program is called to instantiate the output object and generate an ICD file of the battery system model.
[0059] The details of one or more embodiments of the present application are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the present application will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0060] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0061] FIG1 is a schematic diagram of an application of an ICD file in one embodiment;
[0062] FIG2 is a schematic flow chart of a method for generating an ICD file in one embodiment;
[0063] FIG3 is a flow chart of a method for determining the number of output objects and data members in one embodiment;
[0064] FIG4 is a flow chart of a method for constructing a data model in one embodiment;
[0065] FIG5 is a schematic diagram of a hierarchical structure of a battery management system in one embodiment;
[0066] FIG6 is a schematic diagram of a flow chart of a method for constructing a preset data model in one embodiment;
[0067] FIG7 is a schematic diagram of mapping a battery system model and an IEC61850 model in one embodiment;
[0068] FIG8 is a schematic diagram of the steps of determining a constructed data model in one embodiment;
[0069] FIG9 is a schematic flow chart of a method for generating an ICD file in another embodiment;
[0070] FIG10 is a schematic diagram of an ICD file according to an embodiment;
[0071] FIG11 is a schematic diagram of a framework of an ICD file generation method according to an embodiment;
[0072] FIG12 is a block diagram of an ICD file generating device according to an embodiment;
[0073] FIG13 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0074] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.
[0075] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned figure descriptions are intended to cover non-exclusive inclusions.
[0076] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.
[0077] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0078] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.
[0079] In the description of the embodiments of the present application, the term "multiple" refers to more than two (including two). Similarly, "multiple groups" refers to more than two groups (including two groups), and "multiple pieces" refers to more than two pieces (including two pieces).
[0080] In the description of the embodiments of the present application, the technical terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing the embodiments of the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.
[0081] In the description of the embodiments of the present application, unless otherwise expressly specified or limited, technical terms such as "installed," "connected," "connected," and "fixed" should be understood in a broad sense. For example, they can refer to fixed connections, detachable connections, or integration; mechanical connections or electrical connections; direct connections or indirect connections through an intermediate medium; internal connections between two components or interactions between two components. Those skilled in the art can understand the specific meanings of the above terms in the embodiments of the present application based on specific circumstances.
[0082] In the IEC 61850 system, each device is an IED, and each IED file corresponds to an ICD file. The IEDs in the entire application scenario (for example, a smart substation) are made into an SCD file. The SCD file is used to establish connections and communication relationships between each ICD, and the CID file is exported and downloaded to each device. This is a requirement for the application of BMS in power systems.
[0083] Regarding the application of new electric energy storage systems in power systems, the current ICD modeling for BMS is not compatible with all manufacturers. ICD modeling is implemented through manual modeling based on IEC61850. Since the IEC61850 model is a system, modeling requires proficiency in the entire IEC61850 system documentation and high modeling capabilities of staff. The large amount of data in the modeling process needs to be processed manually, which leads to problems such as heavy workload, easy errors, inconvenience in verification, and difficulty in maintenance and upgrading.
[0084] Based on the above considerations, multiple information tables with mapping relationships are pre-built, and the target information table in the multiple information tables with mapping relationships is traversed to determine the target execution program and output object. The target execution program is called to instantiate the output object to generate the ICD file of the battery system model.
[0085] By pre-building the data model, when generating the model ICD file, the target object to be instantiated is determined by traversing the target information tables in multiple information tables with mapping relationships. The target objects are instantiated according to the set target execution program, eliminating the need for manual instantiation of target objects one by one. This reduces the error rate and ensures the accuracy of the model ICD file. By instantiating the output objects through the target execution program, the model ICD file is automatically generated, avoiding coupling between the program and the ICD and improving the program's versatility.
[0086] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.
[0087] The ICD file generation method provided in the embodiment of the present application is illustrated by applying the method to a terminal. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and implemented through the interaction between the terminal and the server.
[0088] Optionally, the application of the ICD file generated by this example is shown in Figure 1. By traversing the target information table of the constructed data model, the number of data members and the output object are determined; the constructed data model includes multiple information tables corresponding to the hierarchical structure of the battery system model, and the multiple information tables have a mapping relationship; the corresponding number of target execution programs is determined according to the number of data members; the output object of the called target execution program is instantiated to generate an ICD file of the battery system model. In the IEC61850 system, each device is an IED, and each IED file corresponds to an ICD file. The IEDs in the entire application scenario (for example, a smart substation) are made into SCD files, and the connection and communication relationship between each ICD is established through the SCD file, and the CID file is exported and downloaded to each device. Among them, making the IED into an SCD file can be achieved through existing methods, which are not limited here.
[0089] In one embodiment, as shown in FIG2 , a method for generating an ICD file is provided. The method is described by taking the application of the method to a terminal as an example, and includes the following steps:
[0090] Step 202 : Acquire a data model including a plurality of information tables corresponding to the hierarchical structure of the battery system model; the plurality of information tables have a mapping relationship between them.
[0091] Step 204: traverse each information table of the data model to determine the number of data members and output objects.
[0092] The data model is pre-built and refers to the model corresponding to the battery management system. An ICD file for the battery system model can be generated based on the data model. The data model includes multiple information tables corresponding to the hierarchical structure of the battery system model, with mapping relationships between the multiple information tables. For example, a mapping relationship exists between the port table and the access point table, a mapping relationship exists between the logical devices in the logical device table and the access points, and a mapping relationship exists between the logical nodes in the logical node table and the logical devices. The information tables include at least one of the following: an access point table, a physical port table, a logical device table, a logical node table, a data set grouping table, a status table, and a data table.
[0093] In this embodiment, the information table includes an access point table, a physical port table, a logical device table, a logical node table, a data set grouping table, a state table, and a data table. The data model includes different types of data sets, including alarm types, integer types, and floating-point types.
[0094] The output object may include the state to be output and the data member to be output. The state to be output and the data member to be output are determined based on the reference in the information table in the data model. One reference corresponds to one state or one data member. The reference is a reference defined in IEC61850. For example, the reference includes S1, M1, and G1.
[0095] Specifically, when generating an ICD file for a battery system model, a constructed data model is obtained. Each information table within the constructed data model is traversed, and the constructed data model and the data in the information tables with mapping relationships are written to memory. A data set within the information table is obtained, and the number of data members within the data set is determined. Furthermore, when determining the number of data members, if the target information table contains multiple data sets with different numbers of data members, the data set with the largest number of data members is used as the final number of data members.
[0096] Step 206: Determine the corresponding number of target execution programs according to the number of data members.
[0097] The target execution program can be understood as a template in the IEC 61850 template library.
[0098] Specifically, the data type of the data member is determined, and the corresponding template is obtained from the IEC 61850 template library according to the data type and the number of data members.
[0099] Step 208: Call the target execution program to instantiate the output object and generate an ICD file of the battery system model.
[0100] Specifically, a corresponding number of templates are obtained from the IEC 61850 template library, the templates obtained from the IEC 61850 template library are called to instantiate the output objects, and the ICD file of the battery system model is generated according to the preset hierarchical structure of the ICD file, thereby completing the creation of the ICD file.
[0101] In the above-mentioned ICD file generation method, when generating a model ICD file, the target object to be instantiated is determined by traversing a pre-built data model. The target object is then instantiated according to a pre-set target execution program, eliminating the need for manual instantiation of each target object one by one. This reduces the error rate and ensures the accuracy of the model ICD file. By instantiating the output object through the target execution program, the model ICD file is automatically generated, avoiding coupling between the program and the ICD and improving the program's versatility.
[0102] When generating the ICD file for the battery system model, the objects to be instantiated are determined manually. This requires inputting a large number of strings, which is error-prone and inefficient. Therefore, the number of data members and output objects is determined based on the relevant information tables in the traversal data model with mapping relationships.
[0103] In one embodiment, a method for determining the number of output objects and data members, as shown in FIG3 , includes the following steps:
[0104] Step 302: traverse the enabled target information in the first information table according to the mapping relationship between the information tables of the data model.
[0105] The data model includes an access point table, a port table, a logical device table, a logical node table, a data set grouping table, a state table, and a data table related to the battery system model. The first information table includes an access point table, a port table, a logical device table, a logical node table, and a data set grouping table.
[0106] Specifically, according to the mapping relationship between each information table of the data model, the first information table is traversed in sequence; and by traversing the first information table, the enabled information in the first information table is obtained, including the following steps:
[0107] Step 1: Traverse the access point table and check the enable flag of the access point modeling. If it is enabled, read the name and reference of the enabled access point row by row; if it is not enabled, issue an alarm prompt.
[0108] Step 2: Traverse the physical port table of the BMS device and check the enable flag of the device physical port row by row. If it is enabled, read the enabled physical port row by row to set the port ID and port name; if it is not enabled, issue an alarm to prompt the alarm information;
[0109] Step 3: Traverse the logical device table and check the enable flag of the logical device row by row. If it is enabled, read the name and reference of the enabled logical device row by row, and obtain the mapping relationship between the logical device and the access point according to the corresponding column. If it is not enabled, an alarm is issued.
[0110] Step 4: Traverse the logical node table and check the enable flag of the logical node table row by row. If it is enabled, obtain the mapping relationship between the logical node and the logical device according to the reference and reference prefix read in the row and the column of the table; if it is not enabled, issue an alarm prompt.
[0111] Step 5: Traverse the dataset grouping table and check the enable flag of the dataset grouping row by row. If it is enabled, read the group number (which can be understood as the dataset name) and the group reference of the dataset group by row; if it is not enabled, an alarm is issued to prompt the alarm information.
[0112] Step 304: traverse the second information table in the data model according to the enabled target information to determine the number of data members and output objects.
[0113] The enabled target information includes the name and reference of the access point, the port ID and port name of the enabled physical port, the name and reference of the enabled logical device, the mapping between logical devices and access points, the reference and prefix of the enabled logical node, the mapping between logical nodes and logical devices, the group number of the enabled data set group and the reference of the data set group, etc. The second information table includes a state table and a data table. The output object includes the output state and data members.
[0114] Furthermore, the output state can be determined by traversing first association information mapped to enabled target information in a state table of the data model and determining the output state based on the first association information. The first association information includes a reference to the state table, a group number, a logical device associated with the logical node, an access point, and the like.
[0115] Determining the data member and the number of data members can be achieved by traversing the second association information mapped to the enabled target information in the data table in the data model, and determining the data member and the number of data members based on the second association information. The second association information includes a reference to the data table, a group number, a logical device associated with a logical node, and an access point.
[0116] Specifically, the state table and data table are traversed based on the enabled target information. Specifically, the state table is traversed, and the state table's references, group numbers, and logical node associations are checked row by row. The state table's name and references are then read row by row. Furthermore, the state's time stamp and quality are determined based on actual business requirements. States with time stamps and quality are marked, and a mapping relationship is established between the data set group and logical node. The state table's references, group numbers, and logical node associations are checked row by row, and an alarm is issued if the associations are incomplete. The data table is traversed, and the state table's references, data set names, and logical node associations are checked row by row. The data table's name, references, and keywords are then read row by row. Furthermore, the data's time stamp and quality are determined based on actual business requirements. States with time stamps and quality are marked, and a mapping relationship is established between the data set group and logical node. The data table's references, data set names, and logical nodes are checked row by row if the associations are incomplete, and an alarm is issued if the associations are incomplete.
[0117] In the above embodiment, the state table and the data table are traversed separately to obtain the state to be instantiated in the state table and the number of data members in the data table and the data members to be instantiated. There is no need to manually determine the output state to be instantiated and the data members to be instantiated one by one, thereby improving processing efficiency.
[0118] In one embodiment, based on the mapping data link, the target execution program is called to instantiate the output object and generate the ICD file of the battery system model, including the following two methods:
[0119] Method 1: Based on the mapping data link from each state or data member to the access point, the target execution program is called, the address of the output object is written, and the access point, data set name, logical device and logical node associated with the output object are determined to generate the ICD file of the battery system model.
[0120] Method 2: Based on the mapping data link from the access point to each state or data member, the target execution program is called, the address of the output object is written, and the access point, data set name, logical device and logical node associated with the output object are determined to generate the ICD file of the battery system model.
[0121] In the above embodiment, by determining the mapping data link of the output object and determining different mapping data links to instantiate the output object, the ICD file of the battery system model is obtained, which can accurately describe the functions and engineering capabilities of the battery system model and meet the needs of the corresponding business scenarios.
[0122] It is understood that in order to generate an ICD file for the battery system model, it is necessary to model the ICD and generate the ICD file based on the established ICD model. The ICD modeling is determined based on the mapping relationship between the hierarchical structure of the battery management system and the IEC61850 model.
[0123] In one embodiment, as shown in FIG4 , a method for constructing a data model is provided. The method is described by taking the application of the method to a terminal as an example, and includes the following steps:
[0124] Step 402 : According to the hierarchical structure of the battery management system, an information table associated with the access points and the logical devices is established to obtain a preset data model.
[0125] Among them, the battery management system includes battery system, battery cluster, battery module and battery cell. The hierarchical structure of battery system, battery cluster, battery module and battery cell is shown in Figure 5. The battery system of BMS consists of n battery clusters, each battery cluster consists of m battery modules, and each battery module consists of p battery cells.
[0126] The information tables include an access point table, a physical port table, a logical device table, a logical node table, a data set grouping table, a state table, and a data table. The fields in the information tables are predetermined. By constructing multiple information tables with mapping relationships, a preset data model is obtained. As shown in Figure 6, a method for constructing a preset data model is provided, comprising the following steps:
[0127] Step 602 : Determine a mapping relationship between the hierarchical structure of the battery system model of the battery management system and the target model.
[0128] The target model can be an IEC61850 model. The hierarchical structure of the IEC61850 model is IED, logical device, logical node, and logical object. The battery system model includes the battery system, battery system body, battery cluster, battery cluster body, battery module, battery module body, and battery cell. To generate an ICD file, it is necessary to determine the corresponding IED information based on the battery management system's hierarchical structure, create access points and logical devices according to the IED information hierarchy, and create logical nodes and data objects for the logical devices.
[0129] The battery system model and the IEC61850 model are mapped, as shown in Figure 7. The battery system is mapped to an IED, the battery system body is mapped to a common logical device LD0, the battery cluster is mapped to a logical device LD, the battery cluster body and battery module are mapped to a logical node LN, and the battery module body and battery cell are mapped to a data attribute DA.
[0130] For example, the battery system ontology is mapped to the public logical device LD0, which contains four logical nodes: the point zero node LLN0, the logical device node LPHD, the logical node GGIO, and the measurement node MMXN. The predefined data set (dsBatSys) in LLN0 contains the battery system ontology information. The information in the predefined data set in LLN0 is the state information represented by the logical node GGIO and the measurement information represented by the MMXN node.
[0131] The battery cluster is mapped as a logical device (LD), including the LLNO, LPHD, and GGIO logical nodes. LLN0 should predefine a battery cluster data set (dsBatClu) and multiple battery module data sets (dsBatMod). The battery cluster data set includes all data objects (DOs) representing telesignaling, telemetry, and remote control information in the battery cluster entity information logical node (batCluGGIO). The multiple battery module data sets (dsBatMod) include all data objects (DOs) representing telesignaling and telemetry information in the battery module information logical node (batModGGIO).
[0132] Step 604 : Create an access point of the battery management system and define a logical device of the battery system model according to the mapping relationship.
[0133] Specifically, an access point of the battery management system and a logical device defining a battery system model are created according to the mapping relationship.
[0134] Step 606: Create an information table associated with the access point and the logical device, and construct a preset data model.
[0135] Specifically, according to the access points of the battery management system and the logical devices defining the battery system model, information tables associated with the access points and the logical devices are established, a mapping relationship exists between the information tables, and a preset data model is constructed according to the information tables with the mapping relationship.
[0136] Furthermore, the methods for constructing the preset data model include:
[0137] An access point table is established according to the preset fields of the access table; a physical port table is established according to the preset fields of the physical port table; a logical device table is established according to the preset fields of the logical device table; a logical node table is established according to the preset fields of the logical node table; a dataset grouping table is established according to the preset fields of the dataset grouping table; a state table is constructed according to the preset fields of the state table; a data table is constructed according to the preset fields of the data table; a mapping relationship is established among the access point table, the physical port table, the logical device table, the logical node table, the dataset grouping table, the state table and the data table according to the key fields of the access point table, the physical port table, the logical device table, the logical node table, the dataset grouping table, the state table and the data table to obtain a preset data model.
[0138] The preset fields of the access table include access point identifier, whether enabled, access point type, and reference. Access point types include station control layer type, bay layer type, and process layer type. The preset fields of the physical port table include whether enabled, access point identifier, and port identifier. The preset fields of the logical device table include logical device name, reference, whether enabled, access point identifier, and keyword. The preset fields of the logical node table include logical node name, whether enabled, reference, prefix, and keyword. The preset fields of the dataset grouping table include dataset name, description, and control block name. The preset fields of the state table include state name, logical device name, logical node name, reference, dataset name, composite member, and time stamp. The preset fields of the data table include data information name, logical device name, logical node name, reference, dataset name, composite member, and time stamp.
[0139] The key fields of the access point table include access point ID, whether enabled, access point type and reference; the key fields of the physical port table include whether enabled, access point ID and port ID; the key fields of the logical device table include logical device name, reference, whether enabled and the access point ID to which it belongs; the keywords of the logical node table include logical node name, whether enabled and reference; the key fields of the data set grouping table include data set name, description and control block name; the key fields of the status table include status name, logical device name, logical node name, reference and data set name; the key fields of the data table include data information name, logical device name, logical node name, reference type and data set name.
[0140] In the above embodiment, an access point of the battery management system and a logical device defining the battery system model are created based on the mapping relationship between the battery system model and the target model in the battery management system; an information table associated with the access point and the logical device is established, and a preset data model is constructed, thereby simplifying the data model construction process.
[0141] Step 404 : Acquire the association information of the logical devices and the attribute information of the access points according to the business requirements of the battery management system.
[0142] Among them, the attribute information of the access point includes the access point identifier, the enabling information of the access point to be modeled, the access point type, and the reference corresponding to the access point type; the associated information of the logical device includes the port identifier of the physical port associated with the logical device, the enabling information of the physical port to be enabled, the access point identifier associated with the physical port, the logical device name, the reference of the logical device, the enabling information of the logical device to be enabled, and the associated access point identifier of the logical device; the logical node name associated with the logical device, the reference associated with the logical node, the access point to which the logical node belongs, the enabling information of the logical node to be enabled, the dataset name and description corresponding to the logical device, and the control block corresponding to the dataset name; the state signal name of the battery management system, the logical device associated with the state signal name, the logical node associated with the state signal name, the reference corresponding to the state signal name, and the associated dataset name; and the data signal name of the battery management system, the logical device associated with the data signal name, the logical node associated with the data signal name, the reference corresponding to the data signal name, and the dataset name associated with the data signal name.
[0143] Specifically, according to the business requirements of the battery management system, the association information of the logical devices and the attribute information of the access points in the battery management system are obtained.
[0144] Step 406: Write the associated information and attribute information into the preset data model to obtain a constructed data model.
[0145] Furthermore, the steps of writing the association information and attribute information into the preset data model, as shown in FIG8 , include the following:
[0146] Step 802: Write the access point identifier, the enabling information of the access point to be modeled, the access point type, and the reference corresponding to the access point type into the access point table.
[0147] There is a corresponding relationship between the access point identifier and the access point name.
[0148] Step 804: Write the port identifier in the association information, the enabling information of the physical port to be enabled, and the access point identifier associated with the port identifier into the physical port table.
[0149] There is a corresponding relationship between the port identifier and the port name.
[0150] Step 806: Write the logical device name, the reference of the logical device, the enabling information of the logical device to be enabled, and the associated access point identifier of the logical device in the association information into the logical device table.
[0151] Step 808: Write the logical node name associated with the logical device, the reference associated with the logical node, the access point to which the logical node belongs, and the enabling information of the logical node to be enabled in the association information into the logical node table.
[0152] Step 810: Write the dataset name, description, and control block corresponding to the logical device into the dataset grouping table.
[0153] Step 812: Write the status signal name of the battery management system, the logical device associated with the status signal name, the logical node associated with the status signal name, the reference corresponding to the status signal name, and the associated data set name into the status table.
[0154] The battery management system status signal names include the overall battery management system status signal and the individual battery status signal names. Furthermore, the overall battery management system status signal and individual battery status signal names, the associated logical devices, the associated logical nodes, the references, and the associated dataset names, keywords, quality, and time stamps are written into the data table. References of the same type can be distinguished by adding a sequence number after the reference.
[0155] Step 814 writes the battery management system's data signal name, the logical device associated with the data signal name, the logical node associated with the data signal name, the reference corresponding to the data signal name, and the data set name associated with the data signal name into a data table. The data signal name includes the names of the total data signal in the battery management system and the data signal of each battery cell.
[0156] Furthermore, the associated information, including the battery management system's overall data signal and individual battery cell data signal names, associated logical devices, associated logical nodes, references, and associated dataset names, keywords, quality, and time stamps, is written into the data table. References of the same type can be distinguished by adding a sequence number after the reference. It is understood that no duplicate keywords exist in the various information tables.
[0157] In the above-determined constructed data model, the attribute information of the determined access points and the associated information in the logical devices, as well as the access points, logical devices and logical nodes that need to be enabled, are sequentially written into the various information tables of the preset data model to complete the creation of the IED information.
[0158] In the above embodiment, information tables associated with access points and logical devices are established based on the battery management system's hierarchical structure. These information tables have mapping relationships, resulting in a pre-defined data model. Based on the battery management system's business requirements, associated information about logical devices and attribute information about access points are obtained; this associated information and attribute information are written into the pre-defined data model, resulting in a constructed data model. When establishing the data model, multiple information tables with mapping relationships are simply constructed based on the battery management system's hierarchical structure. Furthermore, data is written into these multiple information tables with mapping relationships based on the needs of the business layer, resulting in a constructed data model. This model can meet diverse business needs, improve model development efficiency, and enhance maintainability.
[0159] In another embodiment, as shown in FIG9 , a method for generating an ICD file is provided, which is described by taking the method applied to a terminal as an example, including the following steps:
[0160] Step 902 : Establish an information table associated with access points and logical devices according to the hierarchical structure of the battery management system to obtain a preset data model.
[0161] Step 904 : Acquire the association information of the logical devices and the attribute information of the access points according to the business requirements of the battery management system.
[0162] Step 906: Write the associated information and attribute information into the preset data model to obtain a constructed data model.
[0163] Step 908: traverse each information table of the data model to determine the number of data members and output objects.
[0164] Step 910: Determine the corresponding number of target execution programs according to the number of data members.
[0165] When determining the corresponding number of target execution programs based on data members, it is necessary to determine the type of the data members. If there are different types of data members, it is necessary to determine the target execution programs for each type of data member.
[0166] In one embodiment, determining the corresponding number of target execution programs based on the number of data members includes: classifying the data members according to their types to obtain the number of data members of each type; determining the maximum value among the number of data members of each type as the number of target execution programs; and determining the corresponding number of target execution programs for each type of data member based on the number of target execution programs. For example, the types of data members include integer int, floating point float, and double types, and determining the maximum value of the number of data members in different types of data sets, and determining the maximum value among the number of data members of each type as the number of target execution programs. Accurately determining the target execution programs required for each type of data member avoids the inability to instantiate all data members, which results in an inaccurate generated ICD file.
[0167] Step 912: Call the target execution program to instantiate the output object and generate an ICD file of the battery system model.
[0168] In one embodiment, as shown in Figure 10, a schematic diagram of an ICD file is provided. The ICD file includes the dataset name, description, access point, logical device, logical node, and number of data members. The dataset names include dataset 1, dataset 2, dataset 3, dataset 4, dataset 5, and dataset N. The access point is S1, the logical devices include LD0, BC1, and BC2, and the logical node is LLN0. The dataset members corresponding to dataset 2 are dataset member 1, dataset member 2, dataset member 3, dataset member 4, and dataset member 5. Each dataset member has a corresponding reference, description, and short address. For example, in a battery management system, the temperature of n cells can be described in n clusters.
[0169] Step 914: When an update request is detected, the constructed data model is updated according to the update business requirements carried in the update request.
[0170] The update is determined according to the requirements of the battery management system business layer, and the update may be an update of the access point, logical device or logical node to be used in the data model.
[0171] The following is a framework for an ICD file generation method for an application scenario, as shown in Figure 11. Specifically, the battery system modeling hierarchy is obtained by mapping the hierarchical relationships of the battery system in the battery management system to the logical levels in the IEC61850 model. Based on the modeling hierarchy, the battery management system access points, logical devices, and logical nodes are determined. Multiple information tables with mapping relationships are established based on the determined access points, logical devices, and logical nodes associated with the logical devices.
[0172] An access point table for the battery management system is established, wherein the fields of the access point table include the access point name, whether enabled, the access point type, and the reference; a physical port table is established, wherein the fields of the physical port table include whether enabled, the access point ID, and the port ID; a logical device table is established, wherein the fields of the logical device table include the logical device name, the reference, whether enabled, the access point to which it belongs, and the keyword; a logical node table is established, wherein the fields of the logical node table include the logical node name, the reference, whether enabled, the access point to which it belongs, and the keyword; a data set grouping table is established, wherein the fields of the data set grouping table include the data set name, description, and control block name; a state table is constructed, wherein the fields of the state table include the state name, the logical device, the logical node, the reference, the composite member, the time stamp, and the data set group; a data table is constructed, wherein the fields of the data table include the data table name, the logical device, the logical node, the reference type, the composite member, and the data set group, thereby obtaining a preset data model.
[0173] According to the business requirements of the battery management system, the access point name is written into the access point table, the access point corresponding to the access point name is enabled, and the access point type and reference are written. In the physical port table, the port ID is written, the port corresponding to the port ID is enabled, and the access point ID associated with the port ID is written. In the logical device table, the logical device name and reference are written, the logical device to be used is enabled, and the access point to which the logical device belongs and the keyword corresponding to the execution program are associated. In the logical node table, the logical node name, reference and access point to which the logical node belongs, and the keyword corresponding to the execution program are written, and the logical node to be used is enabled. In the dataset grouping table, the dataset name, description, and control block name are written, and keywords are established. In the status table, the total status signal of the battery management system and the status signal name of each battery cell are written, and the corresponding logical device, logical node, reference, and dataset group are associated. In the data table, the total data signal of the battery management system and the data signal name of each battery cell are written, and the corresponding logical device, logical node, reference, and dataset group are associated. The constructed data model is obtained.
[0174] The state table and data table are traversed, and information from the access point table, physical port table, logical device table, logical node table, data set grouping table, state table, and data table is written to memory. The data set with the largest number of data members is determined from the state table and data table. Based on the data set with the largest number of data members, a corresponding number of templates are retrieved from the IEC61850 template library. The templates are then used to instantiate the objects and data members to be output, generating the ICD file for the battery system model.
[0175] In the above-mentioned ICD file generation method, a battery management system data model is pre-built. The pre-built data model is traversed to determine the number of data members and output objects. The output objects are instantiated by executing the target execution program corresponding to the number of data members to obtain the model instantiation content. The ICD file of the battery system model is automatically generated based on the model instantiation content, eliminating the need for manual generation, reducing the error rate and ensuring the accuracy of the model ICD file. When an update request is detected, the constructed data model is updated according to the update business requirements carried by the update request, adapting to different application scenarios and improving the versatility of the data model.
[0176] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.
[0177] Based on the same inventive concept, embodiments of the present application also provide an ICD file generation device for implementing the aforementioned ICD file generation method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of one or more of the following ICD file generation device embodiments can be found in the aforementioned limitations of the ICD file generation method and will not be further elaborated here.
[0178] In one embodiment, as shown in FIG12 , an ICD file generation device is provided, comprising: a data traversal module 1202 , a matching module 1204 , and a file generation module 1206 , wherein:
[0179] The data traversal module 1202 is used to obtain a data model including multiple information tables corresponding to the hierarchical structure of the battery system model; the multiple information tables have a mapping relationship; and traverse each information table of the data model to determine the number of data members and output objects.
[0180] The matching module 1204 is configured to determine a corresponding number of target execution programs according to the number of data members.
[0181] The file generation module 1206 is used to call the target execution program to instantiate the output object and generate an ICD file of the battery system model.
[0182] In the aforementioned ICD file generation device, when generating a model ICD file, the target object to be instantiated is determined by traversing a pre-built data model. The target object is then instantiated according to a pre-set target execution program, eliminating the need for manual instantiation of each target object one by one. This reduces the error rate and ensures the accuracy of the model ICD file. By instantiating the output object through the target execution program, the model ICD file is automatically generated, avoiding coupling between the program and the ICD and improving the program's versatility.
[0183] In another embodiment, an ICD file generation device is provided, which includes, in addition to a data traversal module 1202, a matching module 1204, and a file generation module 1206, a data link determination module and an update module, wherein:
[0184] The data traversal module 1202 is further configured to traverse enabled target information in the first information table according to the mapping relationship between the information tables of the data model;
[0185] The second information table in the data model is traversed according to the enabled target information to determine the number of data members and the output object.
[0186] The data traversal module 1202 is further configured to traverse the first associated information mapped to the enabled target information in the state table of the data model, and determine the output state according to the first associated information;
[0187] The second association information mapped to the enabled target information in the data table in the data model is traversed, and the data members and the number of data members are determined according to the second association information.
[0188] The data link determination module is used to determine the mapping data link of the output object; the output object includes status and data members.
[0189] The file generation module 1206 is further configured to call the target execution program to instantiate the output object based on the mapping data link, and generate an ICD file of the battery system model.
[0190] The file generation module 1206 is further used to call the target execution program based on the mapping data link from the access point to each state or data member, write the address of the output object, and determine the access point, data set name, logical device and logical node associated with the output object to generate an ICD file for the battery system model.
[0191] The file generation module 1206 is further used to call the target execution program based on the mapping data link from each state or data member to the access point, write the address of the output object, and determine the access point, data set name, logical device and logical node associated with the output object to generate an ICD file for the battery system model.
[0192] The update module is used to update the constructed data model according to the update business requirements carried in the update request when an update request is detected.
[0193] Each module in the above-mentioned ICD file generation device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.
[0194] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be shown in Figure 13. The computer device includes a processor, memory, a communication interface, a display screen, and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner. The wireless manner may be achieved through WiFi, a mobile cellular network, NFC (near field communication), or other technologies. When the computer program is executed by the processor, an ICD file generation method is implemented. The display screen of the computer device may be a liquid crystal display or an electronic ink display screen. The input device of the computer device may be a touch layer covering the display screen, or may be a key, trackball, or touchpad provided on the computer device housing, or may be an external keyboard, touchpad, or mouse.
[0195] Those skilled in the art will understand that the structure shown in FIG13 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
[0196] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.
[0197] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0198] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0199] It should be noted that the information and data involved in this application (including but not limited to data used for analysis, stored data, displayed data, etc.) are all information and data authorized by the user or fully authorized by all parties.
[0200] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.
[0201] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0202] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.
Claims
1. A method for generating an ICD file, characterized in that: The method comprises: Acquire a data model including a plurality of information tables corresponding to a hierarchical structure of a battery system model; wherein the plurality of information tables have a mapping relationship between them; Traversing each information table of the data model to determine the number of data members and output objects; Determine a corresponding number of target execution programs according to the number of data members; The target execution program is called to instantiate the output object and generate an ICD file of the battery system model.
2. The method according to claim 1, characterized in that Traversing each information table of the data model to determine the number of data members and output objects, including: Traversing enabled target information in the first information table according to the mapping relationship between the information tables of the data model; The second information table in the data model is traversed according to the enabled target information to determine the number of data members and output objects.
3. The method according to claim 2, characterized in that The traversing the second information table in the data model according to the enabled target information to determine the number of data members and the output object includes: Traversing the first association information mapped to the enabled target information in the state table of the data model, and determining the output state according to the first association information; The second association information mapped to the enabled target information in the data table in the data model is traversed, and the data members and the number of data members are determined according to the second association information.
4. The method according to claim 3, characterized in that The calling of the target execution program to instantiate the output object and generate the ICD file of the battery system model includes: Determining a mapping data link for the output object; the output object includes a state and a data member; Based on the mapping data link, the target execution program is called to instantiate the output object to generate an ICD file of the battery system model.
5. The method according to claim 4, characterized in that The step of calling the target execution program based on the mapping data link to instantiate the output object and generate the ICD file of the battery system model includes: Based on the mapping data link from the access point to each state or data member, the target execution program is called, the address of the output object is written, and the access point, data set name, logical device and logical node associated with the output object are determined to generate an ICD file for the battery system model.
6. The method according to claim 4, characterized in that The step of calling the target execution program based on the mapping data link to instantiate the output object and generate the ICD file of the battery system model includes: Based on a mapping data link mapping from each state or data member to an access point, the target execution program is called to write the address of the output object and determine the access point, data set name, logical device and logical node associated with the output object to generate an ICD file for the battery system model.
7. The method according to claim 1 or 3, characterized in that The determining of a corresponding number of target execution programs according to the number of data members includes: Classifying the data members according to their types to obtain the number of data members of each type; Determine the maximum value among the numbers of the data members of each category as the number of target executable programs; For each type of data member, determine the corresponding number of target execution programs according to the number of target execution programs.
8. The method according to claim 1, characterized in that The method further comprises: When an update request is detected, the data model is updated according to the update service requirements carried in the update request.
9. An ICD file generating device, characterized in that: The device comprises: A data model determination module is used to obtain a data model of a plurality of information tables corresponding to a hierarchical structure including a battery system model; the plurality of information tables have a mapping relationship between them; A data traversal module, used to traverse the target information table of the data model to determine the number of data members and output objects; A matching module, configured to determine a corresponding number of target execution programs according to the number of data members; The file generation module is used to call the target execution program to instantiate the output object and generate an ICD file of the battery system model.
10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.
12. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.
