Distributed feeder terminal cooperation method and device and electronic equipment

Abstract

The embodiment of the invention provides a distributed feeder terminal cooperation method and device and electronic equipment, and relates to the technical field of feeder terminals. The method comprises the following steps: dividing feeder terminals having an access relationship with service nodes into first-class nodes and second-class nodes; when any feeder terminal belonging to the second-class node is connected to the service node, updating the superior node of the feeder terminal from the service node to the feeder terminal in the first-class node; generating a fault processing instruction after the feeder terminal belonging to the first-class node receives the fault information reported by the subordinate node; the fault processing instruction is executed after being confirmed by the service node. According to the embodiment of the invention, technical guarantee is provided for efficient positioning of line faults.

Description

Technical Field

[0001] The present application relates to the technical field of feeder terminals, and in particular to a distributed feeder terminal coordination method, a distributed feeder terminal coordination device, an electronic device and a corresponding storage medium. Background Art

[0002] Due to the requirement of power supply reliability, it is of great significance to reduce the time of fault location, isolation and power restoration of distribution network. Feeder terminal FTU, also known as distribution switch monitoring terminal, is installed next to the feeder switch to monitor the switch. It has remote control, telemetry, telesignaling, fault detection functions, and communicates with the distribution automation master station to provide the operation status of the distribution system and various parameters and information required for monitoring and control, including switch status, power parameters, phase-to-phase faults, ground faults and parameters at the time of fault, and executes the commands issued by the distribution automation master station to adjust and control the distribution equipment to achieve functions such as fault location, fault isolation and rapid power restoration in non-fault areas. Among them, telemetry mainly reflects the ability to track and monitor current and voltage in real time, remotely control and test the switches and the entire operation status in the feeder automation system to ensure the normal operation of the system; remote control mainly controls the closing and opening operations of the section switch, tie switch and line switch of the feeder through remote control; telesignaling mainly reads the device status signal remotely; fault handling mainly refers to the ability of feeder automation to monitor and repair some faults.

[0003] The existing technical solution only issues instructions to the intelligent switch through the FTU, and there is no design for the interaction process between the switches. It is not designed from the standard specification. As a result, the FTU only presets a threshold in advance, and the FTU issues instructions to the switch according to the threshold to achieve opening and closing. This leads to an increase in the management pressure of the FTU itself as the number of switches increases, and it is easy to cause other areas to be implicated, and the accuracy is not enough. At the same time, due to the limitations of the software and hardware resources of the FTU itself, it is impossible to achieve real-time control, fault location, and rapid troubleshooting. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a distributed feeder terminal collaboration method, device and electronic equipment, which utilizes hybrid networking and data collaborative processing technology to improve the reliability and safety of the feeder automation system, so that the FTU can grasp the information of line faults in real time, so as to at least solve some of the problems in the background technology.

[0005] In order to achieve the above-mentioned purpose, a distributed feeder terminal collaboration method is provided in the present application, which includes: dividing the feeder terminals having an access relationship with the service node into Class I nodes and Class II nodes; when any feeder terminal belonging to the Class II node is connected to the service node, the upper node of the feeder terminal is updated from the service node to the feeder terminal in the Class I node; when the feeder terminal belonging to the Class I node receives the fault information reported by the subordinate node, it generates a fault handling instruction; the fault handling instruction is executed after being confirmed by the service node.

[0006] Optionally, the feeder terminals having access relations with the service node are divided into first-class nodes and second-class nodes, including: selecting a number of feeder terminals as first-class nodes based on the distance from the service node, and the remaining feeder terminals as second-class nodes.

[0007] Optionally, when any feeder terminal belonging to a Class II node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in the Class I node, including: when any feeder terminal belonging to a Class II node is connected to the service node, the service node sends the link address of a feeder terminal in the Class I node to the connected feeder terminal; the feeder terminal belonging to the Class II node receives the link address, disconnects from the service node, and connects to the feeder terminal in the Class I node corresponding to the link address.

[0008] Optionally, the method further includes: storing the address information of the feeder terminal belonging to the second type of node connected to the service node to the service node; storing the address information of the feeder terminal belonging to the second type of node connected to the feeder terminal in the first type of node to the feeder terminal in the first type of node; and obtaining the address information of all the second type of nodes from the service node when the feeder terminal in the first type of node is connected to the service node.

[0009] Optionally, when a feeder terminal belonging to a class of nodes receives fault information reported by a subordinate node, it generates a fault handling instruction, including: the feeder terminal belonging to a class of nodes makes a comprehensive judgment based on its own synchronization information with the service node and the fault information reported by the subordinate node, and coordinates one or more subordinate nodes to generate a fault handling instruction.

[0010] Optionally, the feeder terminal is deployed at a monitoring point of the section switch and is configured to: monitor feeder parameters, respond to instructions from the service node to perform corresponding regulation and control; the instructions include the fault handling instructions.

[0011] Optionally, the feeder terminal includes: a data acquisition unit for acquiring data from a telesignaling interface or a telemetry interface; an edge computing core board for preprocessing the acquired data to obtain preprocessed data; an edge computing unit for deep processing the preprocessed data and operating the remote control interface; the deep processing includes analysis, calculation, and decision-making; and a data processing unit for determining the data flow direction and distributing the data to functional modules in the feeder terminal based on the data flow direction.

[0012] Optionally, the data processing unit is configured to: construct a read-in queue for storing data obtained from the interface, construct a write-out queue for storing data that needs to be sent out, and construct a read-in controller and a write-out controller distributed for read operations and write operations; the read-in controller is configured to put the data obtained from the interface into the read-in queue; the write-out controller is configured to send the data that needs to be sent out to the corresponding interface.

[0013] Optionally, the data processing unit is also configured to: construct a storage queue for storing data that needs to be saved, construct a display queue for storing data that needs to be displayed, and construct a read-out controller and a local controller; the read-out controller is used to read and parse the data in the read-in queue, and write the data into the storage queue or the display queue based on the parsing result; the local controller is constructed to trigger a storage operation on the data in the storage queue when it detects that there is data in the storage queue, and to trigger a display operation on the data in the display queue when it detects that there is data in the display queue.

[0014] The present application also provides a distributed feeder terminal collaboration device, which includes: a node division module, which is used to divide the feeder terminals having an access relationship with the service node into Class I nodes and Class II nodes; an upper-level update module, which is used to update the upper-level node of the feeder terminal from the service node to a feeder terminal in Class I nodes when any feeder terminal belonging to Class II nodes is connected to the service node; an instruction generation module, which is used to generate a fault handling instruction after the feeder terminal belonging to Class I nodes receives the fault information reported by the lower-level node; and a confirmation execution module, which is used to execute the fault handling instruction confirmed by the service node.

[0015] Optionally, the feeder terminals having access relations with the service node are divided into first-class nodes and second-class nodes, including: selecting a number of feeder terminals as first-class nodes based on the distance from the service node, and the remaining feeder terminals as second-class nodes.

[0016] Optionally, when any feeder terminal belonging to a Class II node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in the Class I node, including: when any feeder terminal belonging to a Class II node is connected to the service node, the service node sends the link address of a feeder terminal in the Class I node to the connected feeder terminal; the feeder terminal belonging to the Class II node receives the link address, disconnects from the service node, and connects to the feeder terminal in the Class I node corresponding to the link address.

[0017] Optionally, the device also includes an address storage module, which is used to: store the address information of the feeder terminal belonging to the second type of node connected to the service node to the service node; store the address information of the feeder terminal belonging to the second type of node connected to the feeder terminal in the first type of node to the feeder terminal in the first type of node; when the feeder terminal in the first type of node is connected to the service node, obtain the address information of all the second type of nodes from the service node.

[0018] Optionally, when a feeder terminal belonging to a class of nodes receives fault information reported by a subordinate node, it generates a fault handling instruction, including: the feeder terminal belonging to a class of nodes makes a comprehensive judgment based on its own synchronization information with the service node and the fault information reported by the subordinate node, and coordinates one or more subordinate nodes to generate a fault handling instruction.

[0019] The present application also provides an electronic device, comprising: at least one processor; a memory connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the at least one processor implements the aforementioned distributed feeder terminal collaboration method by executing the instructions stored in the memory.

[0020] The present application also provides a machine-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the processor is configured to execute and implement the aforementioned distributed feeder terminal collaboration method.

[0021] The present application also provides a computer program product, including a computer program, which implements the aforementioned distributed feeder terminal collaboration method when executed by a processor.

[0022] The above technical solution has the following beneficial effects:

[0023] (1) The implementation method proposes a distributed feeder terminal FTU collaborative processing method based on the architecture to realize the three remote controls of the line switch and fault detection and location, providing technical support for efficient location of line faults.

[0024] (2) A feeder terminal FTU hardware architecture suitable for distributed deployment was constructed, which can promptly detect line faults caused by the new power system;

[0025] (3) Build and deploy a distributed FTU application system to achieve data sharing and collaborative computing and decision-making.

[0026] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the following specific implementations, they are used to explain the embodiments of the present application, but do not constitute a limitation on the embodiments of the present application. In the accompanying drawings:

[0028] Figure 1 A schematic diagram of the steps of the distributed feeder terminal coordination method according to an embodiment of the present application is schematically shown;

[0029] Figure 2 A schematic diagram of a processing architecture of a distributed feeder terminal collaboration method according to an embodiment of the present application is shown;

[0030] Figure 3 A schematic diagram of an application deployment architecture of a feeder terminal according to an embodiment of the present application is shown;

[0031] Figure 4 The schematic diagram shows the hardware composition of the feeder terminal according to the implementation mode of the present application;

[0032] Figure 5 A schematic diagram of a data read and write queue in a feeder terminal according to an embodiment of the present application is schematically shown;

[0033] Figure 6 A schematic diagram of the structure of a distributed feeder terminal coordination device according to an embodiment of the present application is shown;

[0034] Figure 7 The internal structure of an electronic device according to an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0035] The specific implementation of the embodiment of the present application is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described here is only used to illustrate and explain the embodiment of the present application, and is not used to limit the embodiment of the present application.

[0036] Figure 1 The following schematically shows the steps of the distributed feeder terminal coordination method according to the embodiment of the present application. Figure 1As shown, the method includes:

[0037] S01, dividing the feeder terminals having access relationship with the service node into first-class nodes and second-class nodes;

[0038] S02. When any feeder terminal belonging to a second-class node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in a first-class node;

[0039] S03, when the feeder terminal belonging to a type of node receives the fault information reported by the lower-level node, it generates a fault handling instruction;

[0040] S04. The fault handling instruction is executed after being confirmed by the service node.

[0041] Through the above implementation methods, the original centralized feeder terminal collaborative processing is logically updated to distributed feeder terminal collaborative processing, thereby providing technical guarantee for efficient positioning of line faults.

[0042] In some embodiments of the present application, feeder terminals that have an access relationship with a service node are divided into Class I nodes and Class II nodes, including: selecting a number of feeder terminals as Class I nodes based on the distance from the service node, and the remaining feeder terminals as Class II nodes. The division of Class I nodes and Class II nodes in the previous embodiment can be carried out in a variety of ways, such as according to processing capabilities, system configuration information, etc. This embodiment provides a location-based division method, which preferentially divides feeder terminals near service nodes into Class I nodes, which can make nodes with processing capabilities more concentrated and easier to manage.

[0043] In some embodiments of the present application, when any feeder terminal belonging to a class II node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in a class I node, including: when any feeder terminal belonging to a class II node is connected to the service node, the service node sends the link address of a feeder terminal in a class I node to the connected feeder terminal; the feeder terminal belonging to the class II node receives the link address, disconnects from the service node, and connects to the feeder terminal in the class I node corresponding to the link address. This embodiment provides a method for updating an upper node, which is implemented based on link reset during communication. This method does not change the original hardware structure, but is implemented by changing the link structure, and distributed processing is realized at the logical level.

[0044] In some embodiments of the present application, the method further includes: storing the address information of the feeder terminal belonging to the second type of node connected to the service node to the service node; storing the address information of the feeder terminal belonging to the second type of node connected to the feeder terminal in the first type of node to the feeder terminal in the first type of node; when the feeder terminal in the first type of node is connected to the service node, obtaining the address information of all the second type of nodes from the service node. This embodiment provides the storage of address information. Through the existing multiple data interactions, the address information of the feeder terminal of the second type of node is stored in the service node and the feeder terminal in the first type of node, and a mechanism for obtaining the address information of all the second type of nodes from the service node is added, so that the feeder terminal in the first type of node stores the same address information as the service node, realizing the backup of the address information of the whole network, and providing a data basis for the feeder terminal in the first type of node to realize the same function of the service node.

[0045] In some embodiments of the present application, when a feeder terminal belonging to a class of nodes receives fault information reported by a lower-level node, a fault handling instruction is generated, including: the feeder terminal belonging to the class of nodes makes a comprehensive judgment based on the synchronization information between itself and the service node and the fault information reported by the lower-level node, and cooperates with one or more of the lower-level nodes to generate a fault handling instruction. In this embodiment, the function of generating fault handling instructions in the service node is transferred to the feeder terminal of the class of nodes. When the feeder terminal of the class of nodes processes the fault information reported by the lower-level node, it needs to combine the synchronization information with the service node and cooperate with one or more of the lower-level nodes to generate a fault handling instruction after synthesis.

[0046] Figure 2 The following schematically shows a processing architecture diagram of a distributed feeder terminal coordination method according to an embodiment of the present application. Figure 2 As shown, the implementation includes the following steps:

[0047] In the first step, the distribution master station system is designed as a service node SSS to which all FTUs can connect; the FTU feeder terminals S1 and S2 near the SSS are designed as super nodes, i.e., Class I nodes, for backup service nodes; the other FTU feeder terminals P1, P2, P3, and P4 are designed as ordinary nodes, i.e., Class II nodes;

[0048] In the second step, any node among {P1, P2, P3, P4} connects to SSS, and SSS sends the link address of S1 or S2 to the node {P1, P2, P3, P4}, and at the same time, stores the address information of the node {P1, P2, P3, P4};

[0049] Step 3: After {P1, P2, P3, P4} obtain the link address of S1 or S2, they disconnect from SSS and connect to supernode S1 or S2 through the newly obtained link address. At the same time, they send their own addresses to S1 or S2 for backup;

[0050] Step 4: Both S1 and S2 connect to SSS and obtain the address information of all {P1, P2, P3, P4};

[0051] Step 5: If any node among {P1, P2, P3, P4} finds a line fault, it will report it to S1 or S2 to which it is connected in a timely manner;

[0052] Step 6: S1 or S2 makes a comprehensive judgment based on the information synchronized with the SSS and the information reported by {P1, P2, P3, P4}, and coordinates one or more nodes in {P1, P2, P3, P4} to handle the fault;

[0053] Step 7: The final processing instruction is sent by S1 or S2 to SSS for confirmation and execution.

[0054] Through the above implementation, S1 and S2 are added in addition to the SSS node, and new distributed feeder terminal collaborative processing is formed without changing the hardware structure.

[0055] In some embodiments of the present application, the feeder terminal is deployed at a monitoring point of a section switch and is configured to: monitor feeder parameters and perform corresponding adjustments and controls in response to instructions from a service node; the instructions include the fault handling instructions. Figure 3 The following schematically shows an application deployment architecture diagram of a feeder terminal according to an embodiment of the present application. Figure 3 As shown in the figure, the distributed feeder terminal FTU is deployed at the monitoring point of the section switch. Each FTU monitors a section switch. The FTUs cooperate with each other to realize the collaborative discovery of the fault location and make timely processing decisions. Among them, the FTU feeder terminal measures the three-phase parameters of the feeder (including: three-phase voltage, three-phase current, active power, reactive power, frequency, switch position, etc.), monitors and protects the feeder in the distribution system, communicates remotely with the distribution automation system master station in the north, and responds to the instructions of the distribution automation master station to execute the master station's regulation and control of the feeder and its terminal equipment. The FTUs communicate with each other to realize data sharing and collaborative calculation and processing decisions; the section switch responds to the FTU instructions to realize opening and closing.

[0056] In some embodiments of the present application, the feeder terminal includes: a data acquisition unit for acquiring data from a telesignaling interface or a telemetry interface; an edge computing core board for preprocessing the acquired data to obtain preprocessed data; an edge computing unit for deep processing the preprocessed data and operating the remote control interface; the deep processing includes analysis, calculation, and decision-making; and a data processing unit for determining the data flow direction and distributing the data to functional modules in the feeder terminal based on the data flow direction. Figure 4 The schematic diagram shows the hardware composition of the feeder terminal according to the implementation mode of the present application. Figure 4 As shown, it schematically shows the layout of the aforementioned data acquisition unit, edge computing core board, and edge computing unit in the feeder terminal. Figure 4 As shown, the feeder terminal also includes: a power supply unit for supplying power to each functional module in the feeder terminal. Remote control interface. The communication module includes a remote communication module and a local communication unit, wherein the remote communication module is responsible for data interaction with the distribution automation master station; the local communication unit is responsible for local communication processing such as 485 interface communication and high-speed power line carrier HPLC communication. The feeder terminal collects analog quantities such as voltage and current of the feeder loop, and digital quantities such as switch status through the data acquisition unit, and uploads them to the master station system through the communication module after processing by the edge computing unit. At the same time, the remote control command of the master station system is received to control the opening and closing of the switch. This embodiment designs a feeder terminal FTU hardware architecture for distributed deployment in order to promptly detect line faults caused by new power systems.

[0057] In some embodiments of the present application, based on the intermittent and volatile nature of high-proportion photovoltaic access in the new power system that FTU faces, its communication data processing, calculation, and decision-making are relatively complex. This embodiment proposes a FTU data processing method. The processing method mainly includes data read-in and write-out processing and data classification processing. Among them, data read-in and write-out processing includes: constructing a read-in queue for storing data obtained from the interface, constructing a write-out queue for storing data that needs to be sent out, and constructing a read-in controller and a write-out controller for reading and writing operations; the read-in controller is configured to put the data obtained from the interface into the read-in queue; the write-out controller is configured to send the data that needs to be sent out to the corresponding interface. Exemplarily, first, a read-in queue A1 is constructed to store data obtained from the interface, a write-out queue A2 is constructed to store data to be sent out, and a read-in controller Reader is constructed as a thread of a computer for reading operations, and a write-out controller Writer is also constructed as a thread of a computer for writing operations. Secondly, through the Reader, data is received from the 485 interface communication, high-speed power line carrier HPLC communication, remote communication and other interfaces, and the data is placed in the read queue A1; in addition, the Writer is responsible for monitoring the write queue A2, and if data is found, the data is taken out and sent to the corresponding interface. Figure 5 The schematic diagram of the data read and write queue in the feeder terminal according to the embodiment of the present application is schematically shown. Figure 5 As shown, A1 and A2 schematically illustrate the contents including current, voltage, frequency, power, switch, etc.

[0058] On the other hand, data classification processing includes: constructing a storage queue for storing data that needs to be saved, constructing a display queue for storing data that needs to be displayed, and constructing a read-out controller and a local controller; the read-out controller is used to read and parse the data in the read-in queue, and write the data into the storage queue or the display queue based on the parsing result; the local controller is constructed to trigger the storage operation of the data in the storage queue when it detects that there is data in the storage queue, and to trigger the display operation of the data in the display queue when it detects that there is data in the display queue. Exemplarily, first, a data storage queue B1 is constructed to store data locally or in a database, a data display queue B2 is constructed to display data on a display screen or interface, a read controller CC is constructed to read the data in queue A1 and parse the data, and a write local controller DD is constructed to write data to a local database or display it on a display screen or interface; secondly, CC and DD are started, CC reads the data in queue A1 and parses the data, if there is a need to write to the database, the data is put into queue B1, if there is data to be displayed, it is put into queue B2, if there is a need to reply to the interface data, the organized frame data is put into queue A2, and the Writer will send out the data in A2; finally, DD specifically monitors queues B1 and B2, if there is data in B1, it is saved to the database, if there is data in B2, it is displayed on the display screen or interface. Similarly, Figure 5 As shown, B1 and B2 respectively illustrate the storage content or display content including current, voltage, frequency, power, switch, etc.

[0059] Through the above implementation methods, a complete feeder terminal overall solution is constructed through the distributed multi-feeder terminal collaborative processing method, feeder terminal hardware structure and feeder terminal deployment architecture, providing technical guarantee for efficient positioning of line faults.

[0060] Based on the same inventive concept, the present application also provides a distributed feeder terminal coordination device, Figure 6 The structure diagram of the distributed feeder terminal coordination device according to the embodiment of the present application is schematically shown. Figure 6 As shown, the device includes: a node division module, which is used to divide the feeder terminals having an access relationship with the service node into Class I nodes and Class II nodes; an upper-level update module, which is used to update the upper-level node of the feeder terminal from the service node to a feeder terminal in Class I nodes when any feeder terminal belonging to the Class II node is connected to the service node; an instruction generation module, which is used to generate a fault handling instruction after the feeder terminal belonging to the Class I node receives the fault information reported by the lower-level node; and a confirmation execution module, which is used to execute the fault handling instruction confirmed by the service node.

[0061] In some optional implementations of the present application, feeder terminals having access relationships with service nodes are divided into Class I nodes and Class II nodes, including: selecting several feeder terminals as Class I nodes based on the distance from the service node, and the remaining feeder terminals as Class II nodes.

[0062] In some optional embodiments of the present application, when any feeder terminal belonging to a Class II node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in the Class I node, including: when any feeder terminal belonging to a Class II node is connected to the service node, the service node sends the link address of a feeder terminal in the Class I node to the connected feeder terminal; the feeder terminal belonging to the Class II node receives the link address, disconnects from the service node, and connects to the feeder terminal in the Class I node corresponding to the link address.

[0063] In some optional embodiments of the present application, the device also includes an address storage module, which is used to: store the address information of the feeder terminal belonging to the second type of node connected to the service node to the service node; store the address information of the feeder terminal belonging to the second type of node connected to the feeder terminal in the first type of node to the feeder terminal in the first type of node; when the feeder terminal in the first type of node is connected to the service node, obtain the address information of all the second type of nodes from the service node.

[0064] In some optional embodiments of the present application, when a feeder terminal belonging to a class of nodes receives fault information reported by a subordinate node, a fault handling instruction is generated, including: the feeder terminal belonging to a class of nodes makes a comprehensive judgment based on its own synchronization information with the service node and based on the fault information reported by the subordinate node, and cooperates with one or more subordinate nodes to generate a fault handling instruction.

[0065] The specific definition of each functional module in the above-mentioned distributed feeder terminal collaboration device can refer to the definition of the distributed feeder terminal collaboration method above, which will not be repeated here. Each module in the above-mentioned system can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the electronic device in the form of hardware, or can be stored in the memory of the electronic device in the form of software, so that the processor can call and execute the operations corresponding to the above modules. It also achieves the advantage of providing technical support for the efficient positioning of line faults.

[0066] In some embodiments of the present application, an electronic device is further provided, comprising: at least one processor; a memory connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the above-mentioned distributed feeder terminal cooperation method. Its internal structure diagram can be as follows Figure 7 shown. Figure 7 The internal structure diagram of an electronic device according to an embodiment of the present application is schematically shown. The electronic device includes a processor A01, a network interface A02, a memory (not shown in the figure) and a database (not shown in the figure) connected via a system bus. Among them, the processor A01 of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes an internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02 and a database (not shown in the figure). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 in the non-volatile storage medium A04. The network interface A02 of the electronic device is used to communicate with an external terminal through a network connection. When the computer program B02 is executed by the processor A01, a distributed feeder terminal collaboration method is implemented.

[0067] Those skilled in the art will understand that Figure 7 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the electronic device to which the scheme of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0068] In one embodiment provided in the present application, a machine-readable storage medium is provided, on which instructions are stored, and when the instructions are executed by a processor, the processor is configured to execute the aforementioned distributed feeder terminal collaboration method.

[0069] In one embodiment provided in the present application, a computer program product is provided, including a computer program, which implements the aforementioned distributed feeder terminal collaboration method when executed by a processor.

[0070] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt 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.) that include computer-usable program code.

[0071] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), 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 1 A device that provides the functions specified in a block or multiple blocks.

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

[0073] 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 in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0074] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0075] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0076] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0077] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0078] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A distributed feeder terminal coordination method, characterized in that: The method includes: The feeder terminals having access relations with the service nodes are divided into first-class nodes and second-class nodes; When any feeder terminal belonging to the second-class node is connected to the service node, the upper node of the feeder terminal is updated from the service node to the feeder terminal in the first-class node; When a feeder terminal belonging to a type of node receives fault information reported by a lower-level node, it generates a fault handling instruction; The fault handling instruction is executed after being confirmed by the service node.

2. The method according to claim 1, characterized in that Feeder terminals that have access relations with service nodes are divided into Class I nodes and Class II nodes, including: A number of feeder terminals are selected as first-class nodes based on the distance from the service node, and the remaining feeder terminals are second-class nodes.

3. The method according to claim 1, characterized in that When any feeder terminal belonging to the second-class node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in the first-class node, including: When any feeder terminal belonging to the second type of node is connected to the service node, the service node sends a link address of a feeder terminal in the first type of node to the connected feeder terminal; The feeder terminal belonging to the second type of node receives the link address, disconnects from the service node, and connects to the feeder terminal in the first type of node corresponding to the link address.

4. The method according to claim 3, characterized in that The method further comprises: storing address information of a feeder terminal belonging to a second type of node connected to a service node in the service node; storing address information of a feeder terminal belonging to a second type of node connected to a feeder terminal in a first type of node into the feeder terminal in the first type of node; When the feeder terminal in the first type of node is connected to the service node, the address information of all the second type of nodes is obtained from the service node.

5. The method according to claim 1, characterized in that When a feeder terminal belonging to a type 1 node receives fault information reported by a lower-level node, it generates a fault handling instruction, including: The feeder terminal belonging to a type of node makes a comprehensive judgment based on the synchronization information between itself and the service node and the fault information reported by the lower-level node, and cooperates with one or more lower-level nodes to generate a fault processing instruction.

6. The method according to any one of claims 1 to 5, characterized in that The feeder terminal is deployed at the monitoring point of the section switch and is configured to: monitor the parameters of the feeder and respond to the instructions of the service node to perform corresponding regulation and control; the instructions include the fault handling instructions.

7. The method according to claim 6, characterized in that The feeder terminal comprises: A data acquisition unit, used to obtain data from a telesignaling interface or a telemetering interface; The edge computing core board is used to pre-process the acquired data and obtain the pre-processed data. An edge computing unit, used to perform deep processing on the pre-processed data and operate the remote control interface; the deep processing includes analysis, calculation, and decision-making; and The data processing unit is used to determine the data flow direction and distribute the data to the functional modules in the feeder terminal based on the data flow direction.

8. The method according to claim 7, characterized in that The data processing unit is configured to: Build a read queue to store data obtained from the interface, build a write queue to store data to be sent out, build a read controller and a write controller to distribute read and write operations; The read-in controller is configured to put data acquired from the interface into the read-in queue; The write controller is configured to send data to be sent to a corresponding interface.

9. The method according to claim 8, characterized in that The data processing unit is further configured to: Build a storage queue to store data that needs to be saved, build a display queue to store data that needs to be displayed, and build a readout controller and a local controller; The readout controller is used to read out and parse the data in the read-in queue, and write the data into the storage queue or the display queue based on the parsing result; The local controller is configured to trigger a storage operation on the data in the storage queue when detecting that there is data in the storage queue, and to trigger a display operation on the data in the display queue when detecting that there is data in the display queue.

10. A distributed feeder terminal coordination device, characterized in that: The device includes: A node division module, used to divide feeder terminals having access relations with service nodes into first-class nodes and second-class nodes; An upper-level updating module, used for updating the upper-level node of any feeder terminal belonging to the second-class node from the service node to a feeder terminal in the first-class node when the feeder terminal belongs to the second-class node is connected to the service node; An instruction generation module, configured to generate a fault handling instruction after a feeder terminal belonging to a type of node receives fault information reported by a lower-level node; and The confirmation execution module is used to execute the fault handling instruction confirmed by the service node.

11. The device according to claim 10, characterized in that Feeder terminals that have access relations with service nodes are divided into Class I nodes and Class II nodes, including: A number of feeder terminals are selected as first-class nodes based on the distance from the service node, and the remaining feeder terminals are second-class nodes.

12. The device according to claim 10, characterized in that When any feeder terminal belonging to the second-class node is connected to the service node, the upper node of the feeder terminal is updated from the service node to a feeder terminal in the first-class node, including: When any feeder terminal belonging to the second type of node is connected to the service node, the service node sends a link address of a feeder terminal in the first type of node to the connected feeder terminal; The feeder terminal belonging to the second type of node receives the link address, disconnects from the service node, and connects to the feeder terminal in the first type of node corresponding to the link address.

13. The device according to claim 12, characterized in that The device further comprises an address storage module, wherein the address storage module is used for: storing address information of a feeder terminal belonging to a second type of node connected to a service node in the service node; storing address information of a feeder terminal belonging to a second type of node connected to a feeder terminal in a first type of node into the feeder terminal in the first type of node; When the feeder terminal in the first type of node is connected to the service node, the address information of all the second type of nodes is obtained from the service node.

14. The device according to claim 10, characterized in that When a feeder terminal belonging to a type 1 node receives fault information reported by a lower-level node, it generates a fault handling instruction, including: The feeder terminal belonging to a type of node makes a comprehensive judgment based on the synchronization information between itself and the service node and the fault information reported by the lower-level node, and cooperates with one or more lower-level nodes to generate a fault processing instruction.

15. An electronic device, characterized in that: include: at least one processor; a memory connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor implements the steps of the distributed feeder terminal cooperation method as described in any one of claims 1 to 9 by executing the instructions stored in the memory.

16. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the steps of the distributed feeder terminal cooperation method described in any one of claims 1 to 9 are implemented.

17. A computer program product, comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the distributed feeder terminal cooperation method described in any one of claims 1 to 9 are implemented.

Images