Information interaction document generation method suitable for intelligent power distribution network

Abstract

The invention discloses an information interaction document generation method suitable for an intelligent power distribution network, and the method comprises the steps: building a topological information interaction document, and enabling topological information to be a topological information data structure with a transformer substation or a bus as a unit; establishing a fault positioning result interaction file; the fault positioning result interaction file comprises fault analysis result identification information, fault occurrence time information, fault occurrence line information, fault working condition identification information, all alarm monitoring point information in front of a fault occurrence point, adjacent alarm monitoring point information in front of the fault occurrence point and adjacent monitoring point information behind the fault occurrence point.

Description

Technical Field

[0001] The present invention relates to the field of electric power technology, and in particular to a method for generating information interaction documents suitable for a smart distribution network. Background Art

[0002] With the rapid development of the national economy and the continuous improvement of people's living standards, people's dependence on power supply has deepened, the demand for electricity has increased, and higher requirements have been put forward for the reliable, safe and stable operation of the power grid. In recent years, the structure of the distribution network has become more and more complex. When a fault occurs, the alarm information is extremely large, and it is difficult for operation and maintenance personnel to make correct judgments in a short time. It is very important to collect and screen the fault information in time, complete the fault diagnosis quickly, and feedback the diagnosed fault situation to the operation and maintenance personnel in time.

[0003] The fault location method based on transient recording has been proven to be an effective method for locating various types of faults, especially grounding faults in low-current grounding systems. The entire method mainly consists of two parts: a transient recording type fault indicator and a fault location module based on transient recording. The transient recording type fault indicator is mainly used to capture the key information required to determine the fault, such as current, voltage and electric field, to form a transient recording file and upload it to the algorithm server containing the fault location module. The algorithm server locates the fault by centrally analyzing the transient recording and combining it with the line topology. The way to configure the algorithm server in the current distribution automation master station is generally that the algorithm server obtains topology information, telemetry, telesignaling, and recording from the application server of the distribution automation master station, and then outputs the fault location result.

[0004] It can be seen that in the prior art, a document generation method suitable for information interaction between a distribution automation master station and an algorithm server is needed, so as to effectively and standardizedly determine the information interaction between the distribution automation master station and the algorithm server. Summary of the invention

[0005] The present invention provides a method for generating information interaction documents applicable to a smart distribution network, which solves the problem of information interaction standardization between a distribution automation master station and a fault location algorithm server in the current smart distribution network.

[0006] To achieve the above technical objectives, the present invention provides a method for generating information interaction documents applicable to a smart distribution network, the method comprising:

[0007] Establish a topology information interaction file. The topology information is a topology information data structure based on a substation or a busbar. Each topology information data structure contains transient waveform recording type fault indicators installed under the same substation or busbar and the logical connection relationship between them.

[0008] A fault location result interaction file is established, wherein the fault location result interaction file includes:

[0009] Fault analysis result identification information, wherein the fault analysis result identification information is used to identify whether a fault occurs;

[0010] Fault occurrence time information, where the fault occurrence time information is represented by a UTC timestamp;

[0011] Fault line information, where the fault line information is described according to the line ID defined in the topology information interaction file;

[0012] Fault condition identification information, wherein the fault condition identification information expresses the fault type determined by the transient recording fault analysis algorithm server;

[0013] All alarm monitoring point information before the fault occurrence point, wherein the information of all alarm monitoring points before the fault occurrence point is described according to the topology elements defined in the aforementioned topology information interaction file; all alarm monitoring points before the fault occurrence point;

[0014] The information of the alarm monitoring points adjacent to the fault occurrence point is described according to the topology elements defined in the above-mentioned topology information interaction file;

[0015] Before the fault occurs refers to the range between the fault occurrence point and the substation;

[0016] The monitoring point information adjacent to the fault occurrence point is described according to the topology elements defined in the aforementioned topology information interaction file;

[0017] After the fault point refers to the range from the fault point to the end of the line.

[0018] In one embodiment, the method for constructing a topology information data structure based on a substation comprises:

[0019] a. Assign an ID number to each substation and monitoring point;

[0020] b. Define topology elements, which include substation information and monitoring point information;

[0021] c. Build data indexes for all topological elements;

[0022] d. Define each sub-line in the distribution network line topology, including assigning a sub-line ID and an index of the topological elements contained in the sub-line;

[0023] f. The minimum structure of the topology information data structure at least includes a substation ID, a topology element, and a bus relation including at least one sub-line.

[0024] In one embodiment, the method for constructing a topology information data structure based on a bus includes:

[0025] a. Assign an ID number to each bus;

[0026] b. Define topology elements, which include substation information and monitoring point information;

[0027] c. Build data indexes for all topological elements;

[0028] d. Define each sub-line in the distribution network line topology, including assigning a sub-line ID and an index of the topological elements contained in the sub-line;

[0029] e. Construct line relationships for each busbar and its contained sub-lines in the distribution network line topology;

[0030] f. The minimum structure of the topology information data structure at least includes a bus ID, a topology element containing a substation node, and at least one line in a line relationship.

[0031] In one embodiment, the fault location result interaction file further includes:

[0032] Fault cause information, wherein the fault cause information includes at least one fault cause of fault condition identification information, and the fault cause is represented by a fault code.

[0033] In one embodiment, the fault location result interaction file further includes: fault handling suggestion information, where the fault handling suggestion information is used to express line inspection suggestions given for the current fault.

[0034] In one embodiment, the fault location result interaction file further includes: fault recording data information, wherein the fault recording data information includes the name of the recording file and an identification of whether the recording file is a recording file uploaded by a monitoring point on the fault line.

[0035] In one embodiment, the fault location result interaction file further includes: bus telemetry data information, wherein the bus telemetry data information is used to describe the voltage data of the bus when the fault occurs.

[0036] In one embodiment, the topology information interaction file is in JSON format.

[0037] In one embodiment, the terminal device for performing fault recording at the monitoring point may be a fault indicator, a DTU or a FTU device.

[0038] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0040] Figure 1 It is a schematic diagram of the information interaction document structure applicable to the smart distribution network of the present invention;

[0041] Figure 2 is a schematic diagram of an example of a distribution network topology structure of the present invention; DETAILED DESCRIPTION

[0042] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below with reference to the accompanying drawings.

[0043] The document generation method in this embodiment applicable to information interaction between the distribution automation master station and the transient recording fault analysis algorithm server includes:

[0044] 1. Establish a topology information interaction file. The topology information is a topology information data structure based on substations or busbars. Each topology information data structure contains transient waveform fault indicators installed under the same substation or busbar and the logical connection relationship between them. The topology information interaction file adopts JSON format.

[0045] In this embodiment, the distribution network topology is described in two ways: using a substation as a unit or using a bus as a unit.

[0046] For example Figure 2 The topology of a distribution network shown in the figure includes the following steps when describing the topology of the distribution network using substations as units:

[0047] a. Assign an ID number to each substation and monitoring point;

[0048] b. Define topology elements, which include substation information and monitoring point information;

[0049] c. Build data indexes for all topological elements;

[0050] d. Define each sub-line in the distribution network line topology, including assigning a sub-line ID and an index of the topological elements contained in the sub-line;

[0051] e. Define each bus in the distribution network line topology, including assigning bus ID and sub-line ID contained under the bus; and determine the line relationship between the bus and the sub-line;

[0052] Described in JSON format Figure 2 The distribution network topology information shown can be expressed as:

[0053] Represent the entire substation in one data structure.

[0054] {“id”:“0”, / / Substation ID

[0055] "items":[ / / Topological elements, which include substations (type is 1) and monitoring points (type is 2),

[0056] {"id":"0","type":1}, / / Substation node (array index is 0)

[0057] {"id":"1.1.1","type":2}, / / Monitoring point No. 1.1.1 (array index is 1)

[0058] {"id":"1.1.2","type":2}, / / Monitoring point No. 1.1.2 (array index is 2)

[0059] {"id":"1.2.1","type":2}, / / Monitoring point No. 1.2.1 (array index is 3)

[0060] {"id":"1.2.2","type":2}, / / Monitoring point No. 1.2.2 (array index is 4)

[0061] {"id":"1.2.3","type":2}, / / Monitoring point No. 1.2.3 (array index is 5)

[0062] {"id":"1.2.4","type":2}, / / Monitoring point No. 1.2.4 (array index is 6)

[0063] {"id":"1.2.5","type":2}, / / Monitoring point No. 1.2.5 (array index is 7)

[0064] {"id":"2.1.1","type":2} / / Monitoring point No. 2.1.1 (array index is 8)

[0065] ],

[0066] "mlines":[ / / mlines relationship

[0067] {"id":"1","lines":["1.1","1.2"]}, / / Bus 1, including lines 1.1 and 1.2

[0068] {"id":"2","lines":["2.1","2.2"]} / / Bus 2, including lines 2.1 and 2.2

[0069] ],"lines":[ / / Line relationship

[0070] {"id":"1.1","items":[0,1,2]}, / / Line 1.1

[0071] {"id":"1.2","items":[0,3,4,5,6,7]}, / / Line 1.2

[0072] {"id":"2.1","items":[0,8]} / / Line 2.1

[0073] ],"links":[

[0074] [0,1],[0,3],[0,8],[1,2],[3,4],[4,5],[5,6],[4,7] ]

[0076] }

[0077] f. The minimum structure of the topology represented in this way includes at least the substation ID, topological elements items (including substation nodes) and the bus relationship of at least one sub-line in lines. For example:

[0078] {“id”:“0”, / / Substation ID

[0079] "items":[ / / Topological elements, topological elements include substations (type is 1)

[0080] {"id":"0","type":1}, / / Substation node (array index is 0)

[0081] ],"mlines":[ / / mlines relationship

[0082] {"id":"1","lines":["1.1"]}, / / bus 1, including line 1.1

[0083] ],"lines":[ / / Line relationship

[0084] {"id":"1.1","items":[0]}, / / Line 1.1 ]

[0086] }

[0087] If you want to delete this topology, the content only contains the substation ID.

[0088] {“id”:“0”, / / Substation ID

[0089] }

[0090] For example Figure 2 The topology of a distribution network shown in the figure includes the following steps when describing the distribution network topology in units of buses:

[0091] a. Assign an ID number to each bus;

[0092] b. Define topology elements, which include substation information and monitoring point information;

[0093] c. Build data indexes for all topological elements;

[0094] d. Define each sub-line in the distribution network line topology, including assigning a sub-line ID and an index of the topological elements contained in the sub-line;

[0095] e. Construct line relationships for each busbar and its contained sub-lines in the distribution network line topology;

[0096] Since a single bus is represented in one data structure, Figure 2 The described topology requires two data structures to describe.

[0097] Taking bus 1 as an example, its data structure is as follows. Compared with the transformer description method, the bus relationship attributes and the two-telemetry wave information under bus 2 are removed:

[0098] {“id”:“1”, / / bus ID

[0099] "items":[ / / Topological elements, which include substations (type is 1) and monitoring points (type is 2),

[0100] {"id":"0","type":1}, / / Substation node (array index is 0)

[0101] {"id":"1.1.1","type":2}, / / Monitoring point No. 1.1.1 (array index is 1)

[0102] {"id":"1.1.2","type":2}, / / Monitoring point No. 1.1.2 (array index is 2)

[0103] {"id":"1.2.1","type":2}, / / Monitoring point No. 1.2.1 (array index is 3)

[0104] {"id":"1.2.2","type":2}, / / Monitoring point No. 1.2.2 (array index is 4)

[0105] {"id":"1.2.3","type":2}, / / Monitoring point No. 1.2.3 (array index is 5)

[0106] {"id":"1.2.4","type":2}, / / Monitoring point No. 1.2.4 (array index is 6)

[0107] {"id":"1.2.5","type":2} / / Monitoring point No. 1.2.5 (array index is 7)

[0108] ],

[0109] "lines":[ / / Line relationship

[0110] {"id":"1.1","items":[0,1,2]}, / / Line 1.1

[0111] {"id":"1.2","items":[0,3,4,5,6,7]} / / Line 1.2

[0112] ],

[0113] "links":[

[0114] [0,1],[0,3],[1,2],[3,4],[4,5],[5,6],[4,7] ]

[0116] }

[0117] f. The minimum structure of this topology should at least include the bus ID, the topological element items containing the substation node, and at least one line in the line relationship lines. For example:

[0118] {“id”:“1”, / / bus ID

[0119] "items":[ / / Topological elements, topological elements include substations (type is 1)

[0120] {"id":"0","type":1} / / Substation node (array index is 0)

[0121] ],"lines":[ / / Line relationship

[0122] {"id":"1.1","items":[0]} / / Line 1.1 ]

[0124] }

[0125] If you want to delete this topology, the content only contains the bus ID.

[0126] {"id":"1" / / bus ID

[0127] }

[0128] The topology information interaction files are exchanged using the SFTP protocol, with the transient recording fault analysis system acting as the SFTP server and the distribution automation master station acting as the SFTP client.

[0129] Each topology unit is placed in a JSON file. The distribution automation master station transmits the recording to the transient recording fault analysis system in the following ways: scheduled transmission and event-triggered transmission. Scheduled transmission is to transmit the topology information interaction file of all topology units on a daily basis. Event-triggered transmission is to immediately transmit the topology information interaction file of the changed topology unit when the topology changes due to the switching of the tie switch.

[0130] 2. Create a fault location result interaction file, which contains:

[0131] Fault analysis result identification information, wherein the fault analysis result identification information is used to identify whether a fault occurs;

[0132] Fault occurrence time information, where the fault occurrence time information is represented by a UTC timestamp;

[0133] Fault line information, where the fault line information is described according to the line ID defined in the topology information interaction file;

[0134] Fault condition identification information, wherein the fault condition identification information expresses the fault type determined by the transient recording fault analysis algorithm server;

[0135] All alarm monitoring point information before the fault occurrence point, wherein the information of all alarm monitoring points before the fault occurrence point is described according to the topology elements defined in the aforementioned topology information interaction file; all alarm monitoring points before the fault occurrence point;

[0136] The information of the alarm monitoring points adjacent to the fault occurrence point is described according to the topological elements defined in the aforementioned topological information interaction file; according to the topological structure of the distribution network, there is only one alarm monitoring point adjacent to the fault occurrence point;

[0137] The area before the fault occurrence point refers to the area between the fault occurrence point and the substation;

[0138] The monitoring point information adjacent to the fault occurrence point is described according to the topological elements defined in the aforementioned topological information interaction file; according to the topological structure of the distribution network, there may be multiple alarm monitoring points adjacent to the fault occurrence point, for example, when the fault occurrence point is at the junction of the busbar and the sub-line;

[0139] The fault point refers to the range from the fault point to the end of the line;

[0140] According to the needs, the fault location result interaction file also includes:

[0141] Fault cause information, the fault cause information including at least one fault cause of the fault condition identification information, the fault cause being represented by a fault code;

[0142] Fault handling suggestion information, which is used to express line inspection suggestions given for the current fault;

[0143] Fault recording data information, the fault recording data information including the name of the recording file and an identification of whether the recording file is a recording file uploaded by a monitoring point on the fault line;

[0144] Busbar telemetry data information, wherein the busbar telemetry data information is used to describe the voltage data of the busbar when a fault occurs;

[0145] After analyzing the fault, the transient recording fault analysis system sends the fault location result to the distribution automation master station in the form of SFTP. The distribution automation master station is the SFTP server, and the transient recording fault analysis system is the SFTP client.

[0146] In this embodiment, when there are multiple fault points, the fault location result interaction file includes the fault line information, fault condition identification information, all alarm monitoring point information before the fault point, the first alarm monitoring point information before the fault point, and the monitoring point information after the fault point for each fault point;

[0147] It also includes the fault cause information and fault handling suggestions for each fault point;

[0148] Each fault is described by a file, and the file name format is: ground_$busbar ID or substation ID_fault time.json

[0149] Such as: ground_1_1501560264.json

[0150] The bus ID or substation ID is consistent with the ID in the topology information.

[0151] The fault time is the time when the fault occurs, expressed in UTC timestamp, accurate to seconds.

[0152] The ground fault location result is described in JSON format, for example:

[0153] {

[0154] "retCode":0, / / 0 analysis result identifier

[0155] "timestamp":1432863884, / / Fault / event time (in seconds)

[0156] "lineId":"1.1", / / Fault / event line

[0157] "condition":"A_ground", / / Working condition identifier

[0158] "faultNodes":["1.1.1"], / / Fault / monitoring point ID of all alarms before the event point / may be the substation ID

[0159] "faultBefore":"1.1.1", / / Fault / the first monitoring point ID before the event point / may be the substation ID

[0160] "faultAfter":["1.1.2"] / / The monitoring point ID after the fault / event point (used for section location. If there is a branch after the fault point, the length of faultAfter may be greater than 1)

[0161] "suggestion":"Arc grounding, suspected transformer breakdown, please focus on inspecting the transformer",

[0162] "faultReasons":[ / / Multiple possible fault reasons

[0163] {"faultEquipment":"transformer",

[0164] "faultCause":"thunder"}, / / Reason 1

[0165] ...,

[0166] {"faultEquipment":,

[0167] "faultCause":}, / / reason n

[0168] ],

[0169] "detail":[ / / Multiple point failures / events

[0170] {"lineId":"1.1",

[0171] "condition":"A_ground",

[0172] "faultNodes":["1.1.1"],

[0173] "faultBefore":"1.1.1",

[0174] "faultAfter":["1.1.2"],

[0175] "suggestion":"Arc grounding, suspected transformer elbow breakdown, please focus on inspecting the transformer elbow",

[0176] "faultReasons":[ / / Multiple possible fault reasons

[0177] {"faultEquipment":"transformer",

[0178] "faultCause":"thunder"}, / / Reason 1

[0179] ...,

[0180] {"faultEquipment":,

[0181] "faultCause":}, / / reason n

[0182] ],

[0183] }, / / Fault 1

[0184] ...,

[0185] {"lineId":,

[0186] "condition":,

[0187] "faultNodes":,

[0188] "faultBefore":,

[0189] "faultAfter":

[0190] "suggestion":,

[0191] "faultReasons":[ / / Multiple possible fault reasons

[0192] {"faultEquipment":,

[0193] "faultCause":}, / / Reason 1

[0194] ...,

[0195] {"faultEquipment":,

[0196] "faultCause":}, / / reason n

[0197] ],

[0198] InHand Networks iAlgo Algorithm Server and Distribution Automation Master Station Integration Solution V1.8 twenty three

[0200] } / / Fault / Event n

[0201] ],

[0202] "waves":[

[0203] {

[0204] "name":"comtrade_1.1.1_1432863884", / / Recording file name

[0205] "priority":1 / / Is it a key recording? 1: Yes 2: No

[0206] },

[0207] {

[0208] "name":"comtrade_1.1.1_1432863884","priority":2

[0209] }

[0210] ],

[0211] "mlineSoes":[

[0212] {

[0213] "addr":416650, / / A phase voltage

[0214] "ts":1431952808000, / / Feature collection time, in milliseconds

[0215] "value":10 / / telemetry value

[0216] },

[0217] {

[0218] "addr":416651, / / B phase voltage

[0219] "ts":1431952808000, / / Feature collection time, in milliseconds

[0220] "value":10 / / telemetry value

[0221] }, ... ]

[0224] }

[0225] Field Description:

[0226] retCode: analysis result identifier, 0 indicates a fault, 1 indicates no fault

[0227] timestamp: the time when the fault occurred, in seconds

[0228] detail: When a line has multiple faults at the same time (multiple lines or different locations on the same line), all fault points will be listed in detail (single point faults will also appear in it).

[0229] In this embodiment, the working condition identification is shown in Table 1 below:

[0230] Table 1

[0231] Identification name meaning A_ground Phase A is grounded B_ground Phase B is grounded C_ground Phase C is grounded A_permant_ground Phase A is permanently grounded B_permant_ground Phase B is permanently grounded C_permant_ground Phase C is permanently grounded A_sup_permant_ground Suspected permanent grounding of phase A B_sup_permant_ground Suspected permanent grounding of phase B C_sup_permant_ground Suspected permanent grounding of phase C ABC_short ABC three-phase short circuit AB_short AB phase short circuit AC_short AC phase short circuit BC_short BC phase short circuit A_break Phase A is disconnected B_break Phase B is disconnected C_break Phase C is disconnected ABC_outstage ABC phase power outage

[0232] In this embodiment, the causes of the failure are shown in Table 2 below:

[0233] Table 2

[0234]

[0235]

[0236] In this embodiment, the bus telemetry data information is shown in Table 3 below:

[0237] Table 3

[0238]

[0239] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on such an understanding, the above technical solution can be essentially or partly contributed to the prior art in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, and the computer-readable recording medium includes any mechanism for storing or transmitting information in a computer (e.g., computer) readable form. For example, a machine-readable medium includes a read-only memory (ROM), a random access memory (RAM), a disk storage medium, an optical storage medium, a flash storage medium, an electrical, optical, acoustic or other form of propagation signal (e.g., a carrier wave, an infrared signal, a digital signal, etc.), etc. The computer software product includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiment.

[0240] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

[0241] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices (equipment), or computer program products. Therefore, the present application can be implemented in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the present application can be implemented in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0242] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, apparatuses (devices) and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1A device that provides the functions specified in a block or multiple blocks.

[0243] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0244] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0245] The above description is only a specific implementation case of the present invention, and the protection scope of the present invention is not limited thereto. Any modification or replacement of the present invention by any technician familiar with the present technology within the technical specifications described in the present invention should be within the protection scope of the present invention.

Claims

1. A method for generating information interaction documents applicable to a smart distribution network, characterized in that: The method includes: Establish a topology information interaction file. The topology information is a topology information data structure based on a substation or a busbar. Each topology information data structure contains transient waveform recording type fault indicators installed under the same substation or busbar and the logical connection relationship between them. A fault location result interaction file is established, wherein the fault location result interaction file includes: Fault analysis result identification information, wherein the fault analysis result identification information is used to identify whether a fault occurs; Fault occurrence time information, where the fault occurrence time information is represented by a UTC timestamp; Fault line information, where the fault line information is described according to the line ID defined in the topology information interaction file; Fault condition identification information, wherein the fault condition identification information expresses the fault type determined by the transient recording fault analysis algorithm server; All alarm monitoring point information before the fault occurrence point, wherein the all alarm monitoring point information before the fault occurrence point is described according to the topology elements defined in the aforementioned topology information interaction file; The information of the alarm monitoring points adjacent to the fault occurrence point is described according to the topology elements defined in the above-mentioned topology information interaction file; Before the fault occurs refers to the range between the fault occurrence point and the substation; The monitoring point information adjacent to the fault occurrence point is described according to the topology elements defined in the aforementioned topology information interaction file; The area after the fault occurrence point refers to the range from the fault occurrence point to the end of the line.

2. The information interaction document generation method according to claim 1, characterized in that: The method for constructing a topology information data structure based on a substation comprises: a. Assign an ID number to each substation and monitoring point; b. Define topology elements, which include substation information and monitoring point information; c. Build data indexes for all topological elements; d. Define each sub-line in the distribution network line topology, including assigning a sub-line ID and an index of the topological elements contained in the sub-line; f. The minimum structure of the topology information data structure at least includes a substation ID, a topology element, and a bus relation including at least one sub-line.

3. The information interaction document generation method according to claim 1, characterized in that: The method for constructing a topology information data structure with busbars as units includes: a. Assign an ID number to each bus; b. Define topology elements, which include substation information and monitoring point information; c. Build data indexes for all topological elements; d. Define each sub-line in the distribution network line topology, including assigning a sub-line ID and an index of the topological elements contained in the sub-line; e. Construct line relationships for each busbar and its contained sub-lines in the distribution network line topology; f. The minimum structure of the topology information data structure at least includes a bus ID, a topology element containing a substation node, and at least one line in a line relationship.

4. The information interaction document generation method according to claim 1, characterized in that: The fault location result interaction file also includes: Fault cause information, wherein the fault cause information includes at least one fault cause of fault condition identification information, and the fault cause is represented by a fault code.

5. The information interaction document generation method according to claim 1, characterized in that: The fault location result interaction file further includes: fault handling suggestion information, where the fault handling suggestion information is used to express line inspection suggestions given for the current fault.

6. The information interaction document generation method according to claim 1, characterized in that: The fault location result interaction file further includes: fault recording data information, wherein the fault recording data information includes the name of the recording file and an identification of whether the recording file is a recording file uploaded by a monitoring point on the fault line.

7. The information interaction document generation method according to claim 1, characterized in that: The fault location result interaction file further includes: bus telemetry data information, wherein the bus telemetry data information is used to describe the voltage data of the bus when the fault occurs.

8. The information interaction document generation method according to claim 1, characterized in that: The topology information interaction file adopts JSON format.

9. A computing device comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the document generation method described in any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the document generation method according to any one of claims 1 to 8.

Images