Method for updating at least one program of firmware of a protection or automation system in the field of electrical energy transmission and distribution
The method allows for cost-effective, uninterrupted firmware updates in protection and automation systems by transferring operation to an updated instance with coordinated data exchange and status messaging, addressing the need for continuous operation and cost reduction in existing update processes.
Patent Information
- Application Number
- PCT/EP2024/062293
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-03
- Publication Date
- 2024-11-14
AI Technical Summary
Existing methods for updating firmware in protection and automation systems in electrical energy transmission and distribution require system interruption, which is costly and inconvenient, especially when redundant systems are used.
A method where an updated instance of the firmware program is started alongside the existing one, with data transfer and status messages enabling seamless operation transfer to the new instance without interrupting the system, using an external update program for coordination.
Enables uninterrupted firmware updates, reducing costs and maintaining system operation, with the option to revert if issues arise, and utilizing a containerized runtime environment for isolation and efficiency.
Smart Images

Figure EP2024062293_14112024_PF_FP_ABST
Abstract
Description
[0001] Description
[0002] Method for updating at least one program of a firmware of a protection or automation system in the field of electrical power transmission and distribution
[0003] In the field of electrical power transmission and distribution, substations are used to increase or decrease the mains voltage in the supply network. In addition to at least one transformer, substations have switching units which, upon receipt of a switching signal, disconnect the substation's outgoing conductors from the rest of the supply network. These switching signals are generated by protection and automation systems which monitor the current and voltage curves in the substation's conductors for fault conditions. If a fault condition exists, a switching signal is generated and sent to one or more selected switching units so that selected switching units are moved to their open position. In the open position, the contacts of the selected switching unit are separated from one another. This prevents current from flowing through the switching unit's contacts.A conductor strand connected to one contact of said switching unit is then separated from the remaining supply network which is connected to the other contact of said circuit breaker.
[0004] Protection and automation systems in a substation contain programs stored by the manufacturer which are referred to here as firmware. The firmware or its configuration requires updating from time to time. This update is referred to as an update. A previously widespread procedure has been to interrupt the operation of the protection and automation systems when a firmware update becomes necessary. The new programs are then transferred. The protection or automation system can resume operation with the new firmware. This procedure has the disadvantage that the operation of the system to be updated must be interrupted.
[0005] Another approach known to those skilled in the art involves redundant protection and automation systems, i.e., duplicated. This approach obviously entails increased costs.
[0006] The object of the invention is therefore to provide a method for updating the firmware of a protection and automation system, which allows the firmware or its configuration to be updated at lower costs without having to interrupt the operation of a system equipped with the firmware.
[0007] The invention solves this problem by a method for updating at least one program of a firmware of a protection or automation system in the field of electrical power transmission or distribution, in which, in addition to the program to be updated that is in operation, an updated version or configuration of the program to be updated is started as a new instance, the new instance informs an update program as a first status message that it is ready to transfer operation from the program to be updated to itself at the start of the takeover process, then operating data and parameters of the program to be updated are transmitted to the new instance, the new instance informs the program to be updated with a second status message and the program to be updated with a third status message,that they are ready to switch operations to the new instance and then operations will be taken over by the new instance.
[0008] According to the invention, an instance of the updated program is started during ongoing operation of the firmware programs. Within the scope of the invention, the update is accompanied by an update program, wherein the update program is application software that has no relevance whatsoever to the system. The application software is also referred to in English as an application program, abbreviated to app. The program to be updated, the new instance, and the update program are configured to exchange data with one another.
[0009] First, a status message is sent from the new instance to the update program. This informs the update program that the new instance is ready to take over operation. To do so, however, the new instance requires a bundle of data such as the position of the assigned switches, the time standard with which the protection system for which the new instance is to be used is synchronized, recently obtained measured values, or the like. The new instance must receive this bundle of data from the program being updated so that it can seamlessly continue operation of the protection system.
[0010] The updating program therefore informs the program being updated that the new instance is ready to accept the bundle of data and also instructs the program being updated to send the bundle of data to the new instance.
[0011] After sending the data, the program to be updated informs the updating program that the said data bundle has been sent and that it is ready to switch operation to the new instance.
[0012] Once the new instance has received the said data bundle, it informs the updating program by means of status messages that it has received the requested data and is now ready to switch over. Once the updating program has received the said status messages, it initiates the switchover of operation by sending the corresponding data telegrams to the program to be updated or to the new instance. Operation then switches over to the new instance, which is then saved in a memory of the protection and automation system during ongoing operation. Operation is now continued by the new instance, i.e. with the current version of the program.
[0013] The invention thus enables uninterrupted updating - or in other words uninterrupted update - of a program of the firmware of a protection and automation system during ongoing operation of the protection system.
[0014] Advantageously, all status notifications are sent to the update program, and the switchover is initiated by the update program. This establishes a division of tasks that has proven to be useful.
[0015] In a variant of the method according to the invention, the program to be updated continues its operation for a transition period after switching to the new instance. Should malfunctions occur in the new instance, switching back to the program to be updated is therefore possible without any problems. In other words, this is a safety measure.
[0016] Further advantages arise when the new instance and the program to be updated communicate with the update program via status messages that they are in normal operation or have ceased operation. After receiving this information or status messages, the update program has fulfilled its purpose and can also be terminated.
[0017] In a preferred embodiment of the invention, the program to be updated and the new instance each run in a container. The execution of programs in containers is known to those skilled in the art, thus eliminating the need for a more detailed description of programs in containers. Advantages within the scope of the invention arise from a runtime environment that is isolated from other processes and programs.
[0018] As already explained, the program to be updated and the new instance and application software are set up to exchange data with each other.
[0019] The invention is explained in more detail below using an embodiment example with reference to the attached figure, wherein the
[0020] Figure illustrates the sequence of an embodiment of the method according to the invention.
[0021] The figure schematically illustrates the sequence of the method 1 according to the invention using a bar chart. The program to be updated is identified by reference numeral 2. The new instance of an updated version of the program bears reference numeral 4, with an update program being identified by reference numeral 3. The lengths of the bars extending horizontally from left to right in the figure are intended to illustrate the time during which the respective program is active.
[0022] During period 5, the program 2 to be updated is in normal operation. The switchover to the new instance 4 is initiated over a period marked by a rectangle 6 crossing the horizontal bars at right angles. The vertical triangle 7 represents the period during which the switchover of operation from the program 2 to be updated to the new instance 4 takes place.
[0023] First, the new instance 4 is started. This start is communicated to the update program 3 via a status message 8. The message 8 triggers a new status 9 in the update program. At the end of an initialization phase 31, the new instance 4 communicates to the update program 3 via a status message 10 that it is in its observation state. The observation period is identified in the figure by the reference symbol 11.
[0024] With a further status message 12, the new instance informs the updating program 3 that it is ready to take over operation. The updating program 3 is thus transferred to a new state 13. In the new state 13, the updating program 3 sends two messages 14 and 15, which are sent one to the program 2 to be updated and the other to the new instance 4. The status message 14 triggers a transmission of data 16 from the program 2 to be updated to the new instance 4. In this case, a predetermined data bundle is transmitted which includes, for example, the current switch positions, a time standard to which the protection or automation system has synchronized itself, the most recently received current or voltage values or the like.
[0025] Following this data transfer, which is carried out during the preparation period 6, the new instance 4 informs the update program 3 via status message 17 that it is ready to switch over. A corresponding readiness message 18 is also sent by the program to be updated. This triggers states 19 and 20, respectively, into which the update program 3 is transferred via the aforementioned readiness messages 17, 18.
[0026] Once both have submitted their readiness messages 17, 18, the order being irrelevant, the updating program 4 triggers the switchover by sending corresponding instruction messages 21 and 22. During the switchover period 7, operation switches to the new instance 4. Following the switchover, the program 2 to be updated continues to run for a while, i.e., the period 23, before it is finally shut down at time 24.
[0027] Previously, program 2 to be updated informed update program 3 with message 27 that it was about to terminate. Status message 26, which is sent from the new instance to update program 3, is sent as soon as new instance 4 has taken over operation and has determined that it is running under normal operating conditions. The last status message sent by program 2 to be updated is 27. This is a notification to update program 3 stating that the program to be updated is terminating its operation. This enables uninterrupted updating of firmware programs.
Claims
Patent claims 1. Method (1) for updating at least one program (2) of a firmware of a protection or automation system in the field of electrical energy transmission or distribution, in which - in addition to the program to be updated (2) that is in operation, an updated version or configuration of the program is started as a new instance (4), - the new instance (4) informs an update program (3) by means of a first status message (12) that it is ready to transfer operation from the program (2) to be updated to itself (4), - the program to be updated (2) then transfers operating data and parameters (16) to the new instance (4), - the new instance (4) by means of a second status message (17) and the program (2) to be updated by means of a third status message (18) each inform that they are ready to switch operation to the new instance (4), and - subsequently, the operation is switched from the program to be updated (2) to the new instance (4).
2. Method (1) according to claim 1, characterized in that all status messages (12, 17, 18) are sent to the update program (3) and the switching of the operation is initiated by the update program (3).
3. Method (1) according to claim 2, characterized in that the program (2) to be updated remains active for a transition period (23) after the switchover.
4. Method (1) according to one of the preceding claims, characterized in that the new instance (4) and the program to be updated (2) inform the update program (3) as third and fourth status messages (25, 26) that they have taken over or handed over the operation.
5. Method (1) according to one of the preceding claims, characterized in that the program to be updated (2) and the new instance (4) each run in a container.
6. Method (1) according to one of the preceding claims, characterized in that the update program (3) runs in a container.
7. Method (1) according to one of the preceding claims, characterized in that the program to be updated (2), the new instance (2) and the update program (3) are set up for mutual data exchange.
Citation Information
Patent Citations
Embedded control device, computer program product and method of controlling a control target
EP3968150A1
Method for real-time updating of process software
EP4064045A1
Embedded control device, method for updating a broker unit of the embedded device and computer program product
EP4145287A1
Transparent upgrade of a system service or application
US20180314515A1
