Feeder automation terminal updating method and device, computer equipment and storage medium

Abstract

The invention relates to a feeder automation terminal updating method, which comprises the following steps of: acquiring a physical address of FTU (Feeder Terminal Unit) equipment to be subjected to software updating, and numbering the FTU equipment according to the physical address; according to the serial number, determining a starting FTU device for software updating, and establishing an updating path tree diagram and an updating local area network of each FTU device; and according to the update path tree diagram, the cloud server sends a software update data packet and an update device list to the initial FTU device, and sequentially updates according to the path tree diagram. The software updating time is effectively shortened, the problem of locking of an Internet of Things card is solved, and the software updating safety is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent distribution transformer terminals, and in particular to a feeder automation terminal updating method, device, computer equipment and storage medium. Background Art

[0002] With the rapid development of the power industry, the construction and transformation of smart grids have also expanded rapidly. In smart grids, the smart distribution terminal (FTU) is an indispensable part, which can realize remote monitoring and control, thereby improving the efficiency and quality of the power system. FTU deployment methods are often deployed in different places, and with the continuous improvement of technology, FTU software updates are also an indispensable part.

[0003] The existing online update method of FTU is that the background connects with a single FTU device, sends the software to be updated and the update instruction for update, that is, one master device updates multiple slave devices. It needs to use an IoT card, and use the APN networking of the IoT card to assign a fixed IP to each FTU. The management background connects with the IP of a single FTU device, sends the update instruction, sends the update data, and the FTU verifies the data after the update data is received. The update is performed after the data is complete.

[0004] And this update method also has the following problems:

[0005] 1. With excessive investment in FTU, the time cost of updating will also increase.

[0006] 2. When updating FTU remotely, the existing technical solution uses IoT card for communication:

[0007] 3. When the IoT card is replaced with a new card device, it will be locked and needs to be unlocked by the Unicom operator before it can be used again. The IoT card has a fixed IP address. When the IoT IP address is known, it can communicate with the corresponding device, thereby sending the corresponding update instructions and content updates to the corresponding device. This has poor security and requires a lot of manpower. Summary of the invention

[0008] The object of the present invention is to provide a feeder automation terminal updating method to solve the problems raised in the above background technology.

[0009] A first aspect of the present invention provides a feeder automation terminal updating method, comprising:

[0010] S1. Obtain the physical address of the FTU device to be updated, and number each FTU device according to the physical address;

[0011] S2. According to the number, determine the starting FTU device for software update, and establish an update path tree diagram and an update local area network for each of the FTU devices, wherein only the starting FTU device is connected to the cloud server, and the remaining FTU devices are not connected to the cloud server;

[0012] S3. According to the update path tree diagram, the cloud server sends a software update data packet and an update device list to the starting FTU device. After the starting FTU device performs the software update, the software update data packet and the update device list are sent to the next-level child node in the update path tree diagram. After the next-level child node performs the software update, the above steps are repeated until all nodes in the update path tree diagram complete the software update.

[0013] In a possible implementation manner, the step S1 includes: obtaining the last four bits of the physical address of each FTU device to be software updated, and numbering each FTU device in ascending order according to the size of the last four bits.

[0014] In a possible implementation manner, determining the starting FTU device for software update according to the number includes:

[0015] Determine whether the maximum value of the number is greater than a preset update threshold. If it is greater than the update threshold, the FTU devices corresponding to numbers less than or equal to the update threshold are grouped into one group, and the FTU devices corresponding to numbers greater than the update threshold are grouped into another group. The FTU device corresponding to the first number in each group is taken as the starting FTU device.

[0016] In a possible implementation manner, after the starting FTU device performs software update, before sending the software update data packet and the update device list to the next level child node in the update path tree diagram, the method further includes:

[0017] Obtain the pre-stored authentication certificate of the next-level child node, compare the pre-stored authentication certificate with the real-time authentication certificate in the software update data packet, and if the pre-stored authentication certificate is consistent with the real-time authentication certificate, send the software update data packet, otherwise disconnect the next-level child node from the starting FTU device.

[0018] In a possible implementation manner, comparing the pre-stored authentication certificate with the real-time authentication certificate in the software update data packet includes:

[0019] Extract the real-time certificate hash value in the pre-stored authentication certificate, determine whether the real-time certificate hash value is consistent with the authentication certificate hsah value of the pre-stored authentication certificate, if they are consistent, the pre-stored authentication certificate is credible, otherwise, send the pre-stored authentication certificate hash value to the cloud server, and the cloud server determines whether the pre-stored hsah value belongs to an authorized value, if so, the FTU device corresponding to the pre-stored certificate is deemed credible, otherwise it is untrustworthy and the connection is disconnected.

[0020] A second aspect of the present invention provides a feeder automation terminal updating device, comprising:

[0021] The acquisition module is used to obtain the physical address of the FTU device to be updated, and number each FTU device according to the physical address;

[0022] An analysis module is used to determine the starting FTU device for software update according to the number, and to establish an update path tree diagram and an update local area network for each of the FTU devices.

[0023] A processing module is used for the cloud server to send a software update data packet and an update device list to the starting FTU device according to the update path tree diagram. After the starting FTU device performs software update, the software update data packet and the update device list are sent to the next level child node in the update path tree diagram. After the next level child node performs software update, the above steps are repeated until all nodes in the update path tree diagram complete the software update.

[0024] A third aspect of the present invention provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the feeder automation terminal updating method as described in the first aspect of the present invention is implemented.

[0025] A fourth aspect of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the feeder automation terminal updating method as described in the first aspect of the present invention is implemented.

[0026] Compared with the prior art, the present invention has the following beneficial effects:

[0027] By changing the centralized software update method in which all FTU devices are connected to the cloud server to a method in which only the starting FTU device is connected to the cloud server to obtain the software update data packet, and other FTU devices are updated step by step, the software update time can be effectively improved, the problem of IoT card lock can be solved, and the security of software updates can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic diagram of a flow chart of a feeder automation terminal updating method of the present invention;

[0029] Figure 2 A schematic diagram of a process of updating a feeder automation terminal according to the present invention;

[0030] Figure 3 Schematic diagram of the process for updating existing feeder automation terminals;

[0031] Figure 4 It is a structural schematic diagram of a feeder automation terminal updating device of the present invention;

[0032] Figure 5 FIG. 4 is a schematic diagram of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0034] It should be noted that the serial numbers assigned to the components in the embodiments of the present invention, such as "first" and "second", are only used to distinguish the objects being described and do not have any order or technical meaning.

[0035] like Figure 1 As shown, a feeder automation terminal updating method includes:

[0036] S1. Obtain the physical address of the FTU device to be updated, and number each FTU device according to the physical address;

[0037] Specifically, the last four digits of the physical address of each FTU device to be updated can be obtained, and each FTU device can be numbered in ascending order according to the size of the last four digits. Similar to computers and mobile terminals, each FTU device is set with a different hexadecimal physical address when it leaves the factory. The physical address query instruction can be used to obtain the physical address of each FTU device, and then the last four digits of the physical address can be extracted for sorting. For the present invention, in other embodiments, other methods can also be used to number FTU devices, such as numbering according to the distance of the FTU device.

[0038] S2. According to the number, determine the starting FTU device for software update, and establish an update path tree diagram and an update local area network for each of the FTU devices, wherein only the starting FTU device is connected to the cloud server, and the remaining FTU devices are not connected to the cloud server;

[0039] The following steps can be used to determine the starting FTU device:

[0040] Determine whether the maximum value of the number is greater than a preset update threshold. If it is greater than the update threshold, the FTU devices corresponding to numbers less than or equal to the update threshold are grouped into one group, and the FTU devices corresponding to numbers greater than the update threshold are grouped into another group. The FTU device corresponding to the first number in each group is taken as the starting FTU device.

[0041] For example, there are 100 FTU devices to be updated, and the update threshold is 50. Then the FTU devices numbered 1-50 are the first group, and the FTU devices numbered 51-100 are the second group. Among them, the two FTU devices numbered 1 and 51 are the starting FTU devices.

[0042] The following takes the first group as an example to explain the update path. Figure 2 As shown, FTU devices numbered 2 and 3 are the next-level child nodes, FTU devices numbered 4 and 5 are the next-level child nodes of number 2, FTU devices numbered 6 and 7 are the next-level child nodes of number 3, and so on. The entire update path is an exponential tree diagram.

[0043] The existing software update method uses a central node, such as Figure 3 As shown, each FTU device establishes a connection with the cloud server, and then downloads the software update data package from the cloud server for update. This update method has a slow update speed and requires IoT card APN networking, which has poor security.

[0044] When updating the software of the next-level sub-node, the next-level sub-node needs to be authenticated. The update can only be performed after the authentication is passed. This is to prevent the FTU device that does not need to be updated from being mistakenly updated or the software update data package from being leaked to external devices. The specific authentication steps are as follows:

[0045] Obtain the pre-stored authentication certificate of the next-level child node, compare the pre-stored authentication certificate with the real-time authentication certificate in the software update data packet, and if the pre-stored authentication certificate is consistent with the real-time authentication certificate, send the software update data packet, otherwise disconnect the next-level child node from the starting FTU device.

[0046] When comparing the pre-stored authentication certificate with the real-time authentication certificate in the software update data packet, the following steps may be used:

[0047] Extract the real-time certificate hash value in the pre-stored authentication certificate, determine whether the real-time certificate hash value is consistent with the authentication certificate hsah value of the pre-stored authentication certificate, if they are consistent, the pre-stored authentication certificate is credible, otherwise, send the pre-stored authentication certificate hash value to the cloud server, and the cloud server determines whether the pre-stored hsah value belongs to an authorized value, if so, the FTU device corresponding to the pre-stored certificate is deemed credible, otherwise it is untrustworthy and the connection is disconnected.

[0048] In the present invention, the hash value can be generated according to a hash algorithm such as MD5, SHA-1, etc. When performing certificate authentication, the following method can also be adopted: a public key is stored in a cloud server, a private key is stored in each FTU device, and certificate authentication is performed by matching the public key and the private key.

[0049] S3. According to the update path tree diagram, the cloud server sends a software update data packet and an update device list to the starting FTU device. After the starting FTU device performs the software update, the software update data packet and the update device list are sent to the next-level child node in the update path tree diagram. After the next-level child node performs the software update, the above steps are repeated until all nodes in the update path tree diagram complete the software update.

[0050] In the present invention, a distributed local area network is used for software update, which is decentralized and exponentially updated step by step. Only the starting FTU device needs to obtain the software update data packet from the cloud server, and the remaining devices only need to apply NAT technology in the local area network for update, which effectively improves the efficiency of software update.

[0051] like Figure 4 As shown, the second aspect of the present invention provides a feeder automation terminal updating device, comprising:

[0052] The acquisition module 10 is used to obtain the physical address of the FTU device to be updated with software, and number each FTU device according to the physical address;

[0053] The analysis module 20 is used to determine the starting FTU device for software update according to the number, and to establish an update path tree diagram and an update local area network for each of the FTU devices.

[0054] The processing module 30 is used for the cloud server to send a software update data packet and an update device list to the starting FTU device according to the update path tree diagram. After the starting FTU device performs the software update, the software update data packet and the update device list are sent to the next level child node in the update path tree diagram. After the next level child node performs the software update, the above steps are repeated until all nodes in the update path tree diagram complete the software update.

[0055] In one embodiment, Figure 5 As shown, a computer device 40 is provided, including a memory 42, a processor 41, and a computer program 43 stored in the memory 42 and executable on the processor 41. When the processor 41 executes the computer program 43, the steps in the data processing method in the above embodiment are implemented. To avoid repetition, they are not described here. Alternatively, when the processor 41 executes the computer program 43, the functions of each module in the above feeder automation terminal updating device embodiment are implemented. To avoid repetition, they are not described here.

[0056] In one embodiment, a readable storage medium is provided, wherein the readable storage medium stores a computer program 43. When the computer program 43 is executed by the processor 41, the steps in the data processing method in the above embodiment are implemented. To avoid repetition, it is not described here. Alternatively, when the processor 41 executes the computer program 43, the functions of each module in the above data processing device embodiment are implemented. To avoid repetition, it is not described here.

[0057] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0058] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the division of the above-mentioned functional units and modules is taken as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules, sub-modules and units as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0059] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention 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 invention.

Claims

1. A feeder automation terminal updating method, characterized in that: include: S1. Obtain the physical address of the FTU device to be updated, and number each FTU device according to the physical address; S2. According to the number, determine the starting FTU device for software update, and establish an update path tree diagram and an update local area network for each of the FTU devices, wherein only the starting FTU device is connected to the cloud server, and the remaining FTU devices are not connected to the cloud server; S3. According to the update path tree diagram, the cloud server sends a software update data packet and an update device list to the starting FTU device. After the starting FTU device performs the software update, the software update data packet and the update device list are sent to the next-level child node in the update path tree diagram. After the next-level child node performs the software update, the above steps are repeated until all nodes in the update path tree diagram complete the software update.

2. The feeder automation terminal updating method according to claim 1, characterized in that: The step S1 comprises: The last four bits of the physical address of each FTU device to be software updated are obtained, and the FTU devices are numbered in ascending order according to the size of the last four bits.

3. The feeder automation terminal updating method according to claim 1, characterized in that: The step of determining the starting FTU device for software update according to the number includes: Determine whether the maximum value of the number is greater than a preset update threshold. If it is greater than the update threshold, the FTU devices corresponding to numbers less than or equal to the update threshold are grouped into one group, and the FTU devices corresponding to numbers greater than the update threshold are grouped into another group. The FTU device corresponding to the first number in each group is taken as the starting FTU device.

4. The feeder automation terminal updating method according to claim 1, characterized in that: After the starting FTU device performs software update, before sending the software update data packet and the update device list to the next level child node in the update path tree diagram, the method further includes: Obtain the pre-stored authentication certificate of the next-level child node, compare the pre-stored authentication certificate with the real-time authentication certificate in the software update data packet, and if the pre-stored authentication certificate is consistent with the real-time authentication certificate, send the software update data packet, otherwise disconnect the next-level child node from the starting FTU device.

5. The feeder automation terminal updating method according to claim 4, characterized in that: The comparing the pre-stored authentication certificate with the real-time authentication certificate in the software update data packet includes: Extract the real-time certificate hash value in the pre-stored authentication certificate, determine whether the real-time certificate hash value is consistent with the authentication certificate hsah value of the pre-stored authentication certificate, if they are consistent, the pre-stored authentication certificate is credible, otherwise, send the pre-stored authentication certificate hash value to the cloud server, and the cloud server determines whether the pre-stored hsah value belongs to an authorized value, if so, the FTU device corresponding to the pre-stored certificate is deemed credible, otherwise it is untrustworthy and the connection is disconnected.

6. A feeder automation terminal updating device, used to execute the feeder automation terminal updating according to claims 1-4, characterized in that: include: The acquisition module is used to obtain the physical address of the FTU device to be updated, and number each FTU device according to the physical address; An analysis module is used to determine the starting FTU device for software update according to the number, and to establish an update path tree diagram and an update local area network for each of the FTU devices. A processing module is used for the cloud server to send a software update data packet and an update device list to the starting FTU device according to the update path tree diagram. After the starting FTU device performs software update, the software update data packet and the update device list are sent to the next level child node in the update path tree diagram. After the next level child node performs software update, the above steps are repeated until all nodes in the update path tree diagram complete the software update.

7. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the feeder automation terminal updating method according to any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the feeder automation terminal updating method according to any one of claims 1 to 5 is implemented.

Images