Secondary circuit automatic design method, device and system based on screen cabinet interface model and typical design template

Abstract

The application discloses a secondary circuit automatic design method, device and system based on a screen cabinet interface model and a typical design template, the secondary circuit automatic design method comprises the following steps: establishing a typical design template of a secondary circuit according to voltage grades, main wiring forms and interval information, interval information of the typical design template is stored into an interval relationship database, and connection relationships of screen cabinet interfaces involved in the typical design template are stored into an information flow database; function partition and feature extraction are performed on a screen cabinet logic circuit according to secondary circuit design function partition characteristics, a screen cabinet interface model containing a logic function area is established; and based on the typical design template and the screen cabinet interface model, automatic matching of a logic function area of the screen cabinet interface model and the typical design template is realized through step-by-step analysis and mapping between the template and the model, and automatic design of the secondary circuit is completed. The application can greatly improve the efficiency, accuracy and digital level of secondary circuit design.

Description

Technical Field

[0001] This invention belongs to the field of substation secondary circuit design, specifically relating to an automatic design method, device and system for secondary circuits based on panel interface models and typical design templates. Background Technology

[0002] Currently, the design of secondary system circuits in substations primarily relies on CAD schematics of the switchgear provided by secondary equipment manufacturers to create electrical secondary circuit diagrams and wiring diagrams. Compared to the primary system, the secondary system of a substation has numerous and complex circuits. There are currently no unified standards to guide the design of secondary circuits, requiring designers to rely on their own experience to implement the functions of various circuits and cable laying. The design process mainly uses manual drawing, which leads to problems such as low design efficiency, high error rates, time-consuming and laborious drawing verification, and difficulty in effective data transfer, hindering subsequent digitalization requirements for the secondary system. With the continuous development of intelligent and digital substations, manual drawing is no longer sufficient. Therefore, proposing a set of digital, model-based, and intelligent design ideas and methods is of great significance for all aspects of the secondary system.

[0003] Currently, the IED61850 standard defines the model and interaction specifications of IED devices in smart substations, and the GB / T 37755 standard also specifies the fiber optic interface and fiber optic loop model of IED devices through SPCD model files. However, the models only describe the relevant information of the devices and plug-ins, lacking descriptions of loop functions, which makes the models unsuitable for direct use in loop design. Therefore, providing new models based on loop functions is essential. Although the secondary loops of traditional substations are more complex than those of smart substations, the loop design of secondary systems by major design institutes in various regions is basically the same, all designed according to the characteristics of bay functional zoning, with only local signal and loop functions differing, making it feasible for template-based and automated design.

[0004] In related technologies, there is currently no specific research on the secondary design interface of secondary cabinets. In actual design, this concept is often overlooked, and designers design the circuits between cabinets based on their design experience. In the current research on typical templates for secondary circuit design, the design templates are mainly stored in the form of graphics, and the templates are used by overlaying drawings. This results in low template reuse rate and low design efficiency. Since there are large differences between the templates and the actual projects, the method of overlaying templates does not truly achieve automatic design of secondary circuits. Summary of the Invention

[0005] To address the aforementioned problems, this invention proposes an automatic design method, device, and system for secondary circuits based on a cabinet interface model and typical design templates, which can greatly improve the efficiency, accuracy, and digitalization level of secondary circuit design.

[0006] To achieve the above-mentioned technical objectives and effects, the present invention is implemented through the following technical solution:

[0007] In a first aspect, the present invention provides an automatic secondary loop design method based on a cabinet interface model and a typical design template, comprising:

[0008] A typical design template for secondary circuits is established based on voltage level, main wiring form, and interval information. The interval information of the typical design template is stored in the interval relationship database, and the connection relationship of the cabinet interface involved in the typical design template is stored in the information flow database.

[0009] Based on the functional zoning characteristics of the secondary loop design, the logic loop of the cabinet is functionally zoned and its features are extracted to establish a cabinet interface model containing logical functional areas;

[0010] Based on the typical design template and the cabinet interface model, the automatic matching of the logical functional area of ​​the cabinet interface model with the typical design template is achieved through step-by-step parsing and mapping between the template and the model, thus completing the automatic design of the secondary loop.

[0011] Optionally, the method for establishing a typical design template for the secondary circuit includes:

[0012] Establish a bay relationship database to store bay information. The attributes include voltage level, bay type, main wiring form, and function area.

[0013] Establish an information flow database to store the connection relationships between all devices within an interval in the form of information flow. The attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement.

[0014] Optionally, the method for establishing the cabinet interface model includes:

[0015] Based on the functional zoning characteristics of the secondary circuit design, the external logical functions of the cabinet are divided into four levels: FunctionArea element, FunctionGroup element, Interface element, and Point element. The FunctionArea element contains one or more FunctionGroup elements, the FunctionGroup element contains one or more Interface elements, and the Interface element contains one or more Point elements.

[0016] Assign corresponding attributes to the FunctionArea element, FunctionGroup element, Interface element, and Point element to store interface data at different levels.

[0017] Optionally, the FunctionArea element represents a functional area, partitioned by main device circuits, and includes an attribute name and a description. The FunctionArea element contains one or more FunctionGroup elements.

[0018] The FunctionGroup element represents a specific function within a large functional area. The FunctionGroup element contains an attribute name, a description, and a class, and contains one or more sets of logical interface elements.

[0019] The Interface element represents an interface, used to describe a set of input or output interfaces of the cabinet to the outside world; the Interface element contains one or more Point elements, which include attribute name, description desc, and type, corresponding to different FunctionGroups, and the type attribute has different enumeration types;

[0020] The Point element represents an interface connection point, used to map each connection point of the interface to a connection point of a device in the cabinet. The Point element includes the attribute type type, device name deviceName, and subDevice name subDeviceName.

[0021] Optionally, the cabinet interface model and the typical design template have a corresponding relationship;

[0022] The BayType attribute of the database corresponds to the actual design interval type and the interval relationship of the typical design template library;

[0023] The FunctionArea in the interval relational database has a corresponding relationship with the StartFunctionArea and EndFunctionArea in the information flow database;

[0024] The class attribute of the FunctionGroup element in the cabinet interface model corresponds to the StartFunctionGroup and EndFunctionGroup of the information flow in the typical design template.

[0025] The type and desc attributes of the logical function interface Interface element of the cabinet interface model correspond to the information categories InfoType and InfoDesc in the information flow database of the typical design template. The matching of the desc attribute can be determined based on different type types.

[0026] Optionally, the automatic matching of the logical functional areas of the cabinet interface model with the typical design template is achieved through a step-by-step parsing mapping between the template and the model, based on the typical design template and the typical design template. Specifically, this includes:

[0027] For a given secondary loop in a certain bay, all cabinets within the bay are converted into cabinet interface models.

[0028] Based on the actual design interval type, match the BayType attribute of the relational database in the typical design template library to filter out the relational database corresponding to the interval;

[0029] By matching the StartFunctionArea and EndFunctionArea in the information flow database with the FunctionArea attribute of the interval relation database, all information flows that need to be designed for the current interval can be filtered out.

[0030] For each information stream, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the cabinet interface model are matched through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of the information stream. Finally, the information of a certain FunctionGroup element of a certain FunctionArea element under the cabinet interface model at the start and end points is matched.

[0031] By matching the InfoType and InfoDesc of the information flow with the type and desc attributes of the Interface element of the FunctionGroup element of the starting and ending cabinet interface model, it is determined which two groups of interfaces need to be connected. Based on the number of wired connections of the Point connection points of the Interface element of the starting and ending cabinet interface model, it is specified which Point the two groups of interfaces should be connected through. If multiple groups of interfaces meet the conditions, the first group with connectable points is selected by default to complete the connection.

[0032] Repeat the above steps until the automatic design of all information flows in the typical design template is completed.

[0033] Secondly, the present invention provides an automatic secondary loop design device based on a cabinet interface model and a typical design template, comprising:

[0034] The first modeling module is used to establish a typical design template for secondary circuits based on voltage level, main wiring form, and interval information. The interval information of the typical design template is stored in the interval relationship database, and the connection relationship of the cabinet interface involved in the typical design template is stored in the information flow database.

[0035] The second modeling module is used to perform functional partitioning and feature extraction of the logic circuit of the cabinet based on the characteristics of the functional partitioning of the secondary circuit design, and to establish a cabinet interface model containing logical functional areas.

[0036] The automatic design module is used to automatically match the logical functional area of ​​the cabinet interface model with the typical design template based on the typical design template and the cabinet interface model, and complete the automatic design of the secondary loop through the step-by-step parsing mapping between the template and the model.

[0037] Optionally, the method for establishing a typical design template for the secondary circuit includes:

[0038] Establish a bay relationship database to store bay information. The attributes include voltage level, bay type, main wiring form, and function area.

[0039] Establish an information flow database to store the connection relationships between all devices within an interval in the form of information flow. The attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement.

[0040] Optionally, the method for establishing the cabinet interface model includes:

[0041] Based on the functional zoning characteristics of the secondary circuit design, the external logical functions of the cabinet are divided into four levels: FunctionArea element, FunctionGroup element, Interface element, and Point element. The FunctionArea element contains one or more FunctionGroup elements, the FunctionGroup element contains one or more Interface elements, and the Interface element contains one or more Point elements.

[0042] Assign corresponding attributes to the FunctionArea element, FunctionGroup element, Interface element, and Point element to store interface data at different levels.

[0043] Optionally, the FunctionArea element represents a functional area, partitioned by main device circuits, and includes an attribute name and a description. The FunctionArea element contains one or more FunctionGroup elements.

[0044] The FunctionGroup element represents a specific function within a large functional area. The FunctionGroup element contains an attribute name, a description, and a class, and contains one or more sets of logical interface elements.

[0045] The Interface element represents an interface, used to describe a set of input or output interfaces of the cabinet to the outside world; the Interface element contains one or more Point elements, which include attribute name, description desc, and type, corresponding to different FunctionGroups, and the type attribute has different enumeration types;

[0046] The Point element represents an interface connection point, used to map each connection point of the interface to a connection point of a device in the cabinet. The Point element includes the attribute type type, device name deviceName, and subDevice name subDeviceName.

[0047] Optionally, the cabinet interface model and the typical design template have a corresponding relationship;

[0048] The BayType attribute of the database corresponds to the actual design interval type and the interval relationship of the typical design template library;

[0049] The FunctionArea in the interval relational database has a corresponding relationship with the StartFunctionArea and EndFunctionArea in the information flow database;

[0050] The class attribute of the FunctionGroup element in the cabinet interface model corresponds to the StartFunctionGroup and EndFunctionGroup of the information flow in the typical design template.

[0051] The type and desc attributes of the logical function interface Interface element of the cabinet interface model correspond to the information categories InfoType and InfoDesc in the information flow database of the typical design template. The matching of the desc attribute can be determined based on different type types.

[0052] Optionally, the automatic matching of the logical functional areas of the cabinet interface model with the typical design template is achieved through a step-by-step parsing mapping between the template and the model, based on the typical design template and the typical design template. Specifically, this includes:

[0053] For a given secondary loop in a certain bay, all cabinets within the bay are converted into cabinet interface models.

[0054] Based on the actual design interval type, match the BayType attribute of the relational database in the typical design template library to filter out the relational database corresponding to the interval;

[0055] By matching the StartFunctionArea and EndFunctionArea in the information flow database with the FunctionArea attribute of the interval relation database, all information flows that need to be designed for the current interval can be filtered out.

[0056] For each information stream, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the cabinet interface model are matched through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of the information stream. Finally, the information of a certain FunctionGroup element of a certain FunctionArea element under the cabinet interface model at the start and end points is matched.

[0057] By matching the InfoType and InfoDesc of the information flow with the type and desc attributes of the Interface element of the FunctionGroup element of the starting and ending cabinet interface model, it is determined which two groups of interfaces need to be connected. Based on the number of wired connections of the Point connection points of the Interface element of the starting and ending cabinet interface model, it is specified which Point the two groups of interfaces should be connected through. If multiple groups of interfaces meet the conditions, the first group with connectable points is selected by default to complete the connection.

[0058] Repeat the above steps until the automatic design of all information flows in the typical design template is completed.

[0059] Thirdly, the present invention provides an automatic secondary loop design system based on a cabinet interface model and a typical design template, including a storage medium and a processor;

[0060] The storage medium is used to store instructions;

[0061] The processor is configured to operate according to the instructions to perform the steps of the method according to any one of the first aspects.

[0062] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0063] This invention proposes a cabinet interface model to characterize the external design interface of a secondary cabinet, proposes a database-based typical design template, transforms the traditional graphical template storage method into data storage, and finally proposes an automatic design method for secondary loops based on the cabinet interface model and the typical design template.

[0064] This invention digitizes the external interface data of secondary cabinets and typical design templates for secondary circuits, enabling the digital handover of secondary systems and providing fundamental data for subsequent advanced applications. Simultaneously, the proposed secondary circuit design method based on cabinet interface models and typical design templates significantly improves the efficiency, accuracy, and digitization level of secondary circuit design. It addresses the current problems of low efficiency, high error rates, and inability to digitize secondary data in substation secondary system design from the source of secondary cabinet design, thereby enhancing the digital design level of secondary systems. Attached Figure Description

[0065] To make the content of this invention easier to understand, the invention will be further described in detail below with reference to specific embodiments and accompanying drawings, wherein:

[0066] Figure 1 This is a schematic diagram of a cabinet interface model according to an embodiment of the present invention;

[0067] Figure 2 This is a schematic diagram of a typical design template library according to an embodiment of the present invention;

[0068] Figure 3 This is a flowchart illustrating an embodiment of the automatic design method for secondary circuits according to the present invention. Detailed Implementation

[0069] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the scope of protection of the invention.

[0070] The application principle of the present invention will be described in detail below with reference to the accompanying drawings.

[0071] Example 1

[0072] This invention provides an automatic secondary loop design method based on a cabinet interface model and a typical design template, comprising the following steps:

[0073] A typical design template for secondary circuits is established based on voltage level, main wiring form, and interval information. The interval information of the typical design template is stored in the interval relationship database, and the connection relationship of the cabinet interface involved in the typical design template is stored in the information flow database.

[0074] Based on the functional zoning characteristics of the secondary loop design, the logic loop of the cabinet is functionally zoned and its features are extracted to establish a cabinet interface model containing logical functional areas;

[0075] Based on the typical design template and the cabinet interface model, the automatic matching of the logical functional area of ​​the cabinet interface model with the typical design template is achieved through step-by-step parsing and mapping between the template and the model, thus completing the automatic design of the secondary loop.

[0076] In this embodiment of the invention, a cabinet interface model is proposed to characterize the external design interface of a secondary cabinet, and a database-based typical design template is proposed to transform the traditional graphical template storage method into data storage. Finally, an automatic design method for secondary loops is proposed based on the cabinet interface model and the typical design template.

[0077] In one specific embodiment of the present invention, the method for establishing a typical design template for the secondary circuit includes:

[0078] Establish a bay relationship database to store bay information. The attributes include voltage level, bay type, main wiring form, and function area.

[0079] Establish an information flow database to store the connection relationships between all devices within an interval in the form of information flow. The attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement.

[0080] In one specific embodiment of the present invention, the method for establishing the cabinet interface model includes:

[0081] Based on the functional zoning characteristics of the secondary circuit design, the external logical functions of the cabinet are divided into four levels: FunctionArea element, FunctionGroup element, Interface element, and Point element. The FunctionArea element contains one or more FunctionGroup elements, the FunctionGroup element contains one or more Interface elements, and the Interface element contains one or more Point elements.

[0082] Assign corresponding attributes to the FunctionArea element, FunctionGroup element, Interface element, and Point element to store interface data at different levels.

[0083] In one specific embodiment of the present invention, the FunctionArea element represents a functional area, which is partitioned according to the main device circuit. It includes an attribute name and a description. The FunctionArea element contains one or more FunctionGroup elements.

[0084] The FunctionGroup element represents a specific function within a large functional area. The FunctionGroup element contains an attribute name, a description, and a class, and contains one or more sets of logical interface elements.

[0085] The Interface element represents an interface, used to describe a set of input or output interfaces of the cabinet to the outside world; the Interface element contains one or more Point elements, which include attribute name, description desc, and type, corresponding to different FunctionGroups, and the type attribute has different enumeration types;

[0086] The Point element represents an interface connection point, used to map each connection point of the interface to a connection point of a device in the cabinet. The Point element includes the attribute type (type), device name (deviceName), and sub-device name (subDeviceName). See details. Figure 1 .

[0087] In one specific embodiment of the present invention, the cabinet interface model and the typical design template have a corresponding relationship;

[0088] The BayType attribute of the database corresponds to the actual design interval type and the interval relationship of the typical design template library;

[0089] The FunctionArea in the interval relational database has a corresponding relationship with the StartFunctionArea and EndFunctionArea in the information flow database;

[0090] The class attribute of the FunctionGroup element in the cabinet interface model corresponds to the StartFunctionGroup and EndFunctionGroup of the information flow in the typical design template.

[0091] The `type` and `desc` attributes of the `Interface` element in the cabinet interface model correspond to the information categories `InfoType` and `InfoDesc` in the information flow database of the typical design template. The `desc` attribute's matching is determined by different `type` values; see [link to details]. Figure 2 .

[0092] In one specific embodiment of the present invention, the automatic matching of the logical functional area of ​​the cabinet interface model with the typical design template is achieved through a step-by-step parsing mapping between the template and the model, based on the typical design template and the cabinet interface model. This specifically includes:

[0093] For a given secondary loop in a certain bay, all cabinets within the bay are converted into cabinet interface models.

[0094] Based on the actual design interval type, match the BayType attribute of the relational database in the typical design template library to filter out the relational database corresponding to the interval;

[0095] By matching the StartFunctionArea and EndFunctionArea in the information flow database with the FunctionArea attribute of the interval relation database, all information flows that need to be designed for the current interval can be filtered out.

[0096] For each information stream, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the cabinet interface model are matched through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of the information stream. Finally, the information of a certain FunctionGroup element of a certain FunctionArea element under the cabinet interface model at the start and end points is matched.

[0097] By matching the InfoType and InfoDesc of the information flow with the type and desc attributes of the Interface element of the FunctionGroup element of the starting and ending cabinet interface model, it is determined which two groups of interfaces need to be connected. Based on the number of wired connections of the Point connection points of the Interface element of the starting and ending cabinet interface model, it is specified which Point the two groups of interfaces should be connected through. If multiple groups of interfaces meet the conditions, the first group with connectable points is selected by default to complete the connection.

[0098] Repeat the above steps until the automatic design of all information flows in the typical design template is completed.

[0099] The method in the embodiments of the present invention will be described in detail below with reference to a specific implementation method.

[0100] Step 1: Conduct research on the logical functional loops of the secondary system cabinet. Based on the characteristics of the functional partition design of the secondary loops, extract features and divide the logical functional partitions of the cabinet into levels, and establish the cabinet interface model.

[0101] The panel cabinet interface model is divided into four levels: FunctionArea elements, FunctionGroup elements, Interface elements, and Point elements. The FunctionArea element represents a functional area, divided into large areas according to the circuits of major components (such as secondary devices, circuit breakers, and disconnectors). The FunctionArea element contains an attribute name and a description (desc). Each FunctionArea element contains one or more FunctionGroup elements. The FunctionGroup element represents a specific function within a large functional area, such as power supply, time synchronization, or analog quantity. The FunctionGroup element contains an attribute name, a description (desc), and a class, and contains one or more Interface elements. The Interface element represents an interface, used to describe a set of input or output interfaces of the panel cabinet. The Interface element contains one or more Point (connection point) elements, including the attribute name (name), description (desc), and type (type). The type attribute has different enumeration types depending on the FunctionGroup element. For example, when the class attribute of the FunctionGroup element is DC, the type attribute includes DC Power Supply 1, DC Power Supply 2, etc.; when the class attribute of the FunctionGroup element is BI, the type attribute includes Input 1, Input 2, Input 3, etc. The Point element represents the interface connection point, used to map each connection point of the interface to the connection point of a device in the cabinet. The Point element includes the attribute type (type), device name (deviceName), and subDevice name (subDeviceName).

[0102] In the following example, the FunctionArea elements of the 110 kV line protection cabinet are divided into several major areas according to names such as "Line Protection Device" and "CommonArea". According to the characteristics of functional partitioning, they are divided into multiple FunctionGroups and classified into AI, BO, DO, PWRIN, etc. according to the class attribute. Among them, the grouping of the telesignalling FunctionGroup of the 110 kV line protection cabinet with class = "Telesignalling" has Interface elements at its hierarchical level, including: general accident signal, protection trip, reclosing, control circuit open circuit, etc. The type of the Interface element represents the type of this interface, such as "DC", "PT", "CT", etc. in the example. Taking the type = "CT" of the Interface in the example, the connection points of the A-phase protection current's Point are Terminal 1-13 ID: 1 and 1-13 ID: 4, which represent the wiring position of the A-phase current in the terminal. Point only represents the connectable port of the cabinet, and multiple Points indicate that this interface has multiple connection points, and the connection points are equivalent.

[0103] The logic interface model of the 110 kV line protection cabinet is as follows:

[0104] <FunctionArea name = "Line Protection Device" desc = "Line Protection Device Interface">

[0105] <FunctionGroup name = "ProtectionCurrent" desc = "Protection Current Circuit" class = "AI">

[0106] <Interface name = "I1" desc = "A-phase Protection Current" type = "CT">

[0107] <Point type = "s1" deviceName = "1-13ID" subDeviceName = "1" pinName = "1" / >

[0108] <Point type = "s2" deviceName = "1-13ID" subDeviceName = "4" pinName = "1" / >

[0109]

[0110] <! -- Only taking the A-phase protection current as an example, others are similar -- >

[0111]

[0112] <FunctionGroup name="ProtectionVoltage" desc="Protection voltage circuit" class="AI">

[0113] <Interface name="Ua" desc="Phase A protection voltage" type="PT">

[0114] <Point type="s1" deviceName="1-13UD" subDeviceName="1" pinName="1" / >

[0115] <Point type="s2" deviceName="1-13UD" subDeviceName="2" pinName="1" / >

[0116]

[0117] <! -- Only take the phase A voltage as an example, others are similar -- >

[0118]

[0119] <FunctionGroup name="BO" desc="Trip output" class="BO">

[0120] <Interface name="TJ1" desc="Trip output 1" group="Logic" type="BO_1">

[0121] <Point type="s1" deviceName="1KD" subDeviceName="1" pinName="1" / >

[0122] <Point type="s2" deviceName="1CD" subDeviceName="1" pinName="1" / >

[0123]

[0124] <! -- Only take trip outputs 1 and 2 as an example, others are similar -- >

[0125]

[0126] <FunctionGroup name="Telesignalling" desc="Tele-signaling" class="DO">

[0127] <Interface name="SGZ" desc="Total accident" type="NO">

[0128] <Point type="1" deviceName="1-21YD" subDeviceName="1" / >

[0129] <Point type="2" deviceName="1-21YD" subDeviceName="7" / >

[0130]

[0131] <! -- Only taking some signals as examples --!>

[0132]

[0133]

[0134] <FunctionArea name="CommonArea" desc="Common circuit">

[0135] <FunctionGroup name="DCPWR" desc="DC power supply" class="PWRIN">

[0136] <Interface name="DCPWR1" desc="DC power supply 1" type="DC" voltage="220V">

[0137] <Point type="+" deviceName="1ZD" subDeviceName="1" pinName="1" / >

[0138] <Point type="-" deviceName="1ZD" subDeviceName="8" pinName="1" / >

[0139]

[0140]

[0141] <! -- Only taking DC power supply 1 as an example --!>

[0142] <�

[0143] Step 2, in order to convert the traditional method of storing secondary connection information with drawings as templates into structured data, the present invention proposes a typical design template based on a database.

[0144] A typical design template consists of an information flow database and a bay relationship database. When creating a typical design template, the corresponding bay information needs to be stored in the bay relationship database, and then the connection information between devices within the bay is stored in the information flow database. The bay relationship database stores the bay information of the typical design template, with attributes including VoltageLevel, BayType, MainWiringForm, and FunctionArea. The BayType in the bay relationship database can be a virtual bay, such as a time synchronization or power supply bay, or other common circuits. The information flow database stores the connection relationships between devices in the typical design template, with attributes including StartFunctionArea, StartFunctionGroup, EndFunctionArea, EndFunctionGroup, InfoType, InfoRequirement, StartInterface, and EndInterface. Specific requirements for the typical design template can be filled in the InfoRequirement attribute of the information flow database.

[0145] Example: A typical design template bay relationship table for a 110kV voltage level line bay with double busbars, as shown in Table 1. Here, VoltageLevel represents the current voltage level, with attribute values ​​including 10, 35, 66, 110, 220, 330, 500, 750, and 1000kV. BayType represents line bay, main transformer bay, time-matching bay (virtual), power supply bay (virtual), etc. MainWiringForm includes: single busbar, single busbar section, double busbar, double busbar single section, double busbar double section, 3 / 2 connection, etc. FunctionArea represents busbar protection devices, line protection devices, and measurement and control devices; this field corresponds to StartFunctionArea and EndFunctionArea in the information flow database.

[0146] Table 1 Examples of Interval Relationship Databases

[0147]

[0148] Secondly, all information flows involved in this typical design template library are filled into the information flow database. The information flow database stores the connection relationships between devices, and the attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement. Specific requirements of the typical design template can be filled in the information requirement InfoRequirement attribute of the information flow database. Partial information flow storage is shown in Table 2 below. StartFunctionArea and EndFunctionArea represent the starting and ending functional areas involved in the information flow, with the device name corresponding to the FunctionArea attribute in the interval relation database; InfoType represents a specific information type, which has different enumeration values ​​in different FunctionGroup functional groups; InfoDesc is the description of the information flow; InfoRequirement is the information filling attribute, M for required and O for optional; FunctionGroup corresponds to the FunctionGroup element of the cabinet interface model.

[0149] Table 2 Examples of Information Flow Databases

[0150]

[0151] Step 3: Based on the cabinet interface model and typical design template, an automatic design method for secondary loops is proposed.

[0152] First, when designing the secondary circuit of a certain interval, all secondary switchboards in the interval are converted into switchboard interface models. Secondly, according to the relationship database of the BayType attribute of the typical design template library matching the actual design interval type, the typical design template corresponding to this interval is screened out. Then, through the FunctionArea attribute of the relationship database of this interval, the StartFunctionArea and EndFunctionArea in the information flow database are matched, and all the information flows required for the current interval design are screened out. For each information flow, through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of this information flow, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the switchboard interface model are matched, and finally the information of a certain FunctionGroup element of a certain FunctionArea element under the switchboard interface models of the starting point and the end point is matched. Then, through the InfoType and InfoDesc of this information flow, the type attribute and desc attribute of the Interface element of the FunctionGroup element of the switchboard interface models of the starting point and the end point are matched to determine which two groups of interfaces need to be connected. If there are multiple groups of interfaces that meet the conditions, the first group with connectable points is taken by default. Finally, according to the number of wired connections of the Point connection points of the Interface elements of the switchboard interface models of the starting point and the end point, it is specified which Point the two groups of interfaces are connected through, and thus the automatic design of a certain information flow in the typical design template is completed.

[0153] First, the current typical design template is screened out in the typical design template library according to the above method. Taking a certain information flow of this typical design template as an example, the matching process is introduced.

[0154] Table 3 Example of an information flow

[0155]

[0156] As shown in Table 3, an information flow described as "total accident" in the information flow database. Through this information flow, StartFunctionArea = "line protection device" and EndFunctionArea = "measurement and control device", the name attribute of the FunctionArea of the logical interface models of the starting point and the end point is matched, and the switchboard interface models of the starting point and the end point are matched as follows. End switchboard interface model:

[0157] <FunctionArea name="measurement and control device"desc="measurement and control device interface">

[0158] <functiongroup / > ......

[0160]

[0161] Starting cabinet interface model:

[0162] <FunctionArea name="Line protection device" desc="Line protection device interface">

[0163] <functiongroup / > ......

[0165]

[0166] Then, match the Class attribute of the FunctionGroup of the starting and ending cabinet interface models according to the information flow StartFunctionGroup = "DO" and EndFunctionGroup = "BI". The matching results are as follows.

[0167] Ending cabinet interface model:

[0168] <FunctionArea name="Telecontrol device" desc="Telecontrol device interface">

[0169] <FunctionGroup name="BI" desc="Switching input" class="BI">

[0170] [[ID=……]] <interface / > ......

[0172]

[0173]

[0174] Starting cabinet interface model:

[0175] <FunctionArea name="Line protection device" desc="Line protection device interface">

[0176] <FunctionGroup name="Telesignalling" desc="Remote signalling" class="DO">

[0177] <interface / > ......

[0179]

[0180]

[0181] Then, through the InfoType = "Signal" and InfoDesc = "Total Accident" of this information flow, the type attribute and desc attribute of the Interface element of the FunctionGroup element of the starting and ending cabinet interface models are matched. If the Type of FunctionGroup is BI, the desc is not required to be exactly matched. The final matching results are as follows.

[0182] <FunctionArea name="Measuring and Control Device" desc="Measuring and Control Device Interface">

[0183] <FunctionGroup name="BI" desc="Input" class="BI">

[0184] <Interface name="BI4" desc="Input 4" class="Signal" type="DC" voltage="220V">

[0185] <Point type="+" deviceName="1-21GD" subDeviceName="1" / >

[0186] <Point type="-" deviceName="1-21QD" subDeviceName="1" / >

[0187]

[0188]

[0189] <FunctionArea name="Line Protection Device" desc="Line Protection Device Interface">

[0190] <FunctionGroup name="Telesignalling" desc="Tele-signal" class="DO">

[0191] <Interface name="SGZ" desc="Total Accident" type="Signal">

[0192] <Point type="+" deviceName="1-21YD" subDeviceName="1" / >

[0193] <Point type="-" deviceName="1-21YD" subDeviceName="7" / >

[0194]

[0195]

[0196]

[0197] Finally, based on the number and connection status of Points at the Interface level of the matching starting interface cabinet model and the Interface level of the ending cabinet, the connection method between the Points of the two Interfaces is determined. In this example, it is ultimately determined that 1-21YD:1 and 1-21GD:1 will be connected, and 1-21QD:1 and 1-21YD:7 will be connected. This completes the design of a certain information flow within the typical design template. By repeating the above process, the automatic design of the entire typical design template can be achieved, that is, the automatic design of the secondary loop of the actual interval can be completed. See details. Figure 3 .

[0198] Example 2

[0199] This invention provides an automatic secondary loop design device based on a cabinet interface model and a typical design template, comprising:

[0200] The first modeling module is used to establish a typical design template for secondary circuits based on voltage level, main wiring form, and interval information. The interval information of the typical design template is stored in the interval relationship database, and the connection relationship of the cabinet interface involved in the typical design template is stored in the information flow database.

[0201] The second modeling module is used to perform functional partitioning and feature extraction of the logic circuit of the cabinet based on the characteristics of the functional partitioning of the secondary circuit design, and to establish a cabinet interface model containing logical functional areas.

[0202] The automatic design module is used to automatically match the logical functional area of ​​the cabinet interface model with the typical design template based on the typical design template and the cabinet interface model, and complete the automatic design of the secondary loop through the step-by-step parsing mapping between the template and the model.

[0203] Optionally, the method for establishing a typical design template for the secondary circuit includes:

[0204] Establish a bay relationship database to store bay information. The attributes include voltage level, bay type, main wiring form, and function area.

[0205] Establish an information flow database to store the connection relationships between all devices within an interval in the form of information flow. The attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement.

[0206] Optionally, the method for establishing the cabinet interface model includes:

[0207] Based on the functional zoning characteristics of the secondary circuit design, the external logical functions of the cabinet are divided into four levels: FunctionArea element, FunctionGroup element, Interface element, and Point element. The FunctionArea element contains one or more FunctionGroup elements, the FunctionGroup element contains one or more Interface elements, and the Interface element contains one or more Point elements.

[0208] Assign corresponding attributes to the FunctionArea element, FunctionGroup element, Interface element, and Point element to store interface data at different levels.

[0209] Optionally, the FunctionArea element represents a functional area, partitioned by main device circuits, and includes an attribute name and a description. The FunctionArea element contains one or more FunctionGroup elements.

[0210] The FunctionGroup element represents a specific function within a large functional area. The FunctionGroup element contains an attribute name, a description, and a class, and contains one or more sets of logical interface elements.

[0211] The Interface element represents an interface, used to describe a set of input or output interfaces of the cabinet to the outside world; the Interface element contains one or more Point elements, which include attribute name, description desc, and type, corresponding to different FunctionGroups, and the type attribute has different enumeration types;

[0212] The Point element represents an interface connection point, used to map each connection point of the interface to a connection point of a device in the cabinet. The Point element includes the attribute type type, device name deviceName, and subDevice name subDeviceName.

[0213] Optionally, the cabinet interface model and the typical design template have a corresponding relationship;

[0214] The BayType attribute of the database corresponds to the actual design interval type and the interval relationship of the typical design template library;

[0215] The FunctionArea in the interval relational database has a corresponding relationship with the StartFunctionArea and EndFunctionArea in the information flow database;

[0216] The class attribute of the FunctionGroup element in the cabinet interface model corresponds to the StartFunctionGroup and EndFunctionGroup of the information flow in the typical design template.

[0217] The type and desc attributes of the logical function interface Interface element of the cabinet interface model correspond to the information categories InfoType and InfoDesc in the information flow database of the typical design template. The matching of the desc attribute can be determined based on different type types.

[0218] Optionally, the automatic matching of the logical functional areas of the cabinet interface model with the typical design template is achieved through a step-by-step parsing mapping between the template and the model, based on the typical design template and the typical design template. Specifically, this includes:

[0219] For a given secondary loop in a certain bay, all cabinets within the bay are converted into cabinet interface models.

[0220] Based on the actual design interval type, match the BayType attribute of the relational database in the typical design template library to filter out the relational database corresponding to the interval;

[0221] By matching the StartFunctionArea and EndFunctionArea in the information flow database with the FunctionArea attribute of the interval relation database, all information flows that need to be designed for the current interval can be filtered out.

[0222] For each information stream, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the cabinet interface model are matched through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of the information stream. Finally, the information of a certain FunctionGroup element of a certain FunctionArea element under the cabinet interface model at the start and end points is matched.

[0223] By matching the InfoType and InfoDesc of the information flow with the type and desc attributes of the Interface element of the FunctionGroup element of the starting and ending cabinet interface model, it is determined which two groups of interfaces need to be connected. Based on the number of wired connections of the Point connection points of the Interface element of the starting and ending cabinet interface model, it is specified which Point the two groups of interfaces should be connected through. If multiple groups of interfaces meet the conditions, the first group with connectable points is selected by default to complete the connection.

[0224] Repeat the above steps until the automatic design of all information flows in the typical design template is completed.

[0225] Example 3

[0226] This invention provides an automatic secondary loop design system based on a cabinet interface model and a typical design template, including a storage medium and a processor;

[0227] The storage medium is used to store instructions;

[0228] The processor is configured to operate according to the instructions to perform the steps of the method according to any one of Embodiment 1.

[0229] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0230] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0231] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0232] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0233] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

[0234] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. An automatic design method for secondary loops based on a cabinet interface model and typical design templates, characterized in that, include: A typical design template for secondary circuits is established based on voltage level, main wiring form, and interval information. The interval information of the typical design template is stored in the interval relationship database, and the connection relationship of the cabinet interface involved in the typical design template is stored in the information flow database. Based on the functional zoning characteristics of the secondary loop design, the logic loop of the cabinet is functionally zoned and its features are extracted to establish a cabinet interface model containing logical functional areas; Based on the typical design template and cabinet interface model, the automatic matching of the logical functional area of ​​the cabinet interface model with the typical design template is achieved through step-by-step parsing and mapping between the template and the model, thus completing the automatic design of the secondary loop. The method for establishing a typical design template for the secondary circuit includes: Establish a bay relationship database to store bay information. The attributes include voltage level, bay type, main wiring form, and function area. Establish an information flow database to store the connection relationships between all devices within an interval in the form of information flow. The attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement. The method for establishing the interface model of the cabinet includes: Based on the functional zoning characteristics of the secondary circuit design, the external logical functions of the cabinet are divided into four levels: FunctionArea element, FunctionGroup element, Interface element, and Point element. The FunctionArea element contains one or more FunctionGroup elements, the FunctionGroup element contains one or more Interface elements, and the Interface element contains one or more Point elements. Assign corresponding attributes to the FunctionArea element, FunctionGroup element, Interface element, and Point element to store interface data at different levels.

2. The automatic design method for secondary loops based on a cabinet interface model and typical design template as described in claim 1, characterized in that: The FunctionArea element represents a functional area, which is divided according to the main device circuits. It includes the attribute name and description. The FunctionArea element contains one or more FunctionGroup elements. The FunctionGroup element represents a specific function within a large functional area. The FunctionGroup element contains an attribute name, a description, and a class, and contains one or more sets of Interface elements. The Interface element represents an interface, used to describe a set of input or output interfaces of the cabinet to the outside world; the Interface element contains one or more Point elements, which include attribute name, description desc, and type, corresponding to different FunctionGroups, and the type attribute has different enumeration types; The Point element represents an interface connection point, used to map each connection point of the interface to a connection point of a device in the cabinet. The Point element includes the attribute type type, device name deviceName, and subDevice name subDeviceName.

3. The automatic design method for secondary loops based on a cabinet interface model and typical design template according to claim 2, characterized in that: The cabinet interface model and the typical design template have a corresponding relationship; The BayType attribute of the database corresponds to the actual design interval type and the interval relationship of the typical design template library; The FunctionArea in the interval relational database has a corresponding relationship with the StartFunctionArea and EndFunctionArea in the information flow database; The class attribute of the FunctionGroup element in the cabinet interface model corresponds to the StartFunctionGroup and EndFunctionGroup of the information flow in the typical design template. The type and desc attributes of the logical function interface Interface element of the cabinet interface model correspond to the information categories InfoType and InfoDesc in the information flow database of the typical design template. The matching of the desc attribute can be determined based on different type types.

4. The automatic design method for secondary loops based on a cabinet interface model and typical design template as described in claim 3, characterized in that: Based on the typical design template and the cabinet interface model, the automatic matching of the logical functional areas of the cabinet interface model with the typical design template is achieved through a step-by-step parsing mapping between the template and the model. Specifically, this includes: For a given secondary loop in a certain bay, all cabinets within the bay are converted into cabinet interface models. Based on the actual design interval type, match the BayType attribute of the relational database in the typical design template library to filter out the relational database corresponding to the interval; By matching the StartFunctionArea and EndFunctionArea in the information flow database with the FunctionArea attribute of the interval relation database, all information flows that need to be designed for the current interval can be filtered out. For each information stream, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the cabinet interface model are matched through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of the information stream. Finally, the information of a certain FunctionGroup element of a certain FunctionArea element under the cabinet interface model at the start and end points is matched. By matching the InfoType and InfoDesc of the information flow with the type and desc attributes of the Interface element of the FunctionGroup element of the starting and ending cabinet interface model, it is determined which two groups of interfaces need to be connected. Based on the number of wired connections of the Point connection points of the Interface element of the starting and ending cabinet interface model, it is specified which Point the two groups of interfaces should be connected through. If multiple groups of interfaces meet the conditions, the first group with connectable points is selected by default to complete the connection. Repeat the above steps until the automatic design of all information flows in the typical design template is completed.

5. An automatic secondary loop design device based on a cabinet interface model and typical design template, characterized in that, include: The first modeling module is used to establish a typical design template for secondary circuits based on voltage level, main wiring form, and interval information. The interval information of the typical design template is stored in the interval relationship database, and the connection relationship of the cabinet interface involved in the typical design template is stored in the information flow database. The second modeling module is used to perform functional partitioning and feature extraction of the logic circuit of the cabinet based on the characteristics of the functional partitioning of the secondary circuit design, and to establish a cabinet interface model containing logical functional areas. The automatic design module is used to automatically match the logical functional area of ​​the cabinet interface model with the typical design template based on the typical design template and the cabinet interface model, and complete the automatic design of the secondary loop through the step-by-step parsing mapping between the template and the model. The method for establishing a typical design template for the secondary circuit includes: Establish a bay relationship database to store bay information. The attributes include voltage level, bay type, main wiring form, and function area. Establish an information flow database to store the connection relationships between all devices within an interval in the form of information flow. The attributes include the starting device StartFunctionArea, the starting functional area StartFunctionGroup, the ending device EndFunctionArea, the ending functional group EndFunctionGroup, the information type InfoType, the information description InfoDesc, and the information requirement InfoRequirement. The method for establishing the interface model of the cabinet includes: Based on the functional zoning characteristics of the secondary circuit design, the external logical functions of the cabinet are divided into four levels: FunctionArea element, FunctionGroup element, Interface element, and Point element. The FunctionArea element contains one or more FunctionGroup elements, the FunctionGroup element contains one or more Interface elements, and the Interface element contains one or more Point elements. Assign corresponding attributes to the FunctionArea element, FunctionGroup element, Interface element, and Point element to store interface data at different levels.

6. The automatic secondary loop design device based on the cabinet interface model and typical design template according to claim 5, characterized in that, The FunctionArea element represents a functional area, which is divided according to the main device circuits. It includes the attribute name and description. The FunctionArea element contains one or more FunctionGroup elements. The FunctionGroup element represents a specific function within a large functional area. The FunctionGroup element contains an attribute name, a description, and a class, and contains one or more sets of Interface elements. The Interface element represents an interface, used to describe a set of input or output interfaces of the cabinet to the outside world; the Interface element contains one or more Point elements, which include attribute name, description desc, and type, corresponding to different FunctionGroups, and the type attribute has different enumeration types; The Point element represents an interface connection point, used to map each connection point of the interface to a connection point of a device in the cabinet. The Point element includes the attribute type type, device name deviceName, and subDevice name subDeviceName.

7. The automatic secondary loop design device based on the cabinet interface model and typical design template according to claim 6, characterized in that, The cabinet interface model and the typical design template have a corresponding relationship; The BayType attribute of the database corresponds to the actual design interval type and the interval relationship of the typical design template library; The FunctionArea in the interval relational database has a corresponding relationship with the StartFunctionArea and EndFunctionArea in the information flow database; The class attribute of the FunctionGroup element in the cabinet interface model corresponds to the StartFunctionGroup and EndFunctionGroup of the information flow in the typical design template. The type and desc attributes of the logical function interface Interface element of the cabinet interface model correspond to the information categories InfoType and InfoDesc in the information flow database of the typical design template. The matching of the desc attribute can be determined based on different type types.

8. The automatic secondary loop design device based on the cabinet interface model and typical design template according to claim 7, characterized in that, Based on the typical design template and the cabinet interface model, the automatic matching of the logical functional areas of the cabinet interface model with the typical design template is achieved through a step-by-step parsing mapping between the template and the model. Specifically, this includes: For a given secondary loop in a certain bay, all cabinets within the bay are converted into cabinet interface models. Based on the actual design interval type, match the BayType attribute of the relational database in the typical design template library to filter out the relational database corresponding to the interval; By matching the StartFunctionArea and EndFunctionArea in the information flow database with the FunctionArea attribute of the interval relation database, all information flows that need to be designed for the current interval can be filtered out. For each information stream, the name attribute of the FunctionArea element and the class attribute of the FunctionGroup element of the cabinet interface model are matched through the StartFunctionArea, StartFunctionGroup and EndFunctionArea, EndFunctionGroup attributes of the information stream. Finally, the information of a certain FunctionGroup element of a certain FunctionArea element under the cabinet interface model at the start and end points is matched. By matching the InfoType and InfoDesc of the information flow with the type and desc attributes of the Interface element of the FunctionGroup element of the starting and ending cabinet interface model, it is determined which two groups of interfaces need to be connected. Based on the number of wired connections of the Point connection points of the Interface element of the starting and ending cabinet interface model, it is specified which Point the two groups of interfaces should be connected through. If multiple groups of interfaces meet the conditions, the first group with connectable points is selected by default to complete the connection. Repeat the above steps until the automatic design of all information flows in the typical design template is completed.

9. An automatic secondary loop design system based on a cabinet interface model and typical design template, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the steps of the method according to any one of claims 1-4.

Images