Remote upgrading method suitable for PLBUS controller

Abstract

The invention discloses a remote upgrading method suitable for PLBUS controllers, which comprises the following steps of: remotely selecting a batch of multiple PLBUS controllers to start upgrading through a master station, adjusting an upgrading information structure, and then effectively upgrading the PLBUS controllers step by step in sequence. According to the method, the applicability and the stability are improved through the enhanced algorithm design, the efficiency, the success rate, the safety and the manageability of the upgrading process are remarkably improved, the method has wide application value in the field of intelligent equipment, and the functionality and the user experience of the equipment can be effectively improved.

Description

Technical Field

[0001] The invention relates to the technical field of PLBUS controllers, and in particular to a remote upgrade method suitable for PLBUS controllers. Background Art

[0002] Remote upgrade of smart devices is essential for improving performance and fixing defects. However, traditional upgrade methods often face problems such as unreliable data transmission and high failure rate, which seriously affects the user experience. Therefore, it is urgent to design a remote upgrade method suitable for PLBUS controllers to enhance the stability and scalability of the smart device upgrade process. Summary of the invention

[0003] In order to solve the above technical problems, the present invention provides a remote upgrade method applicable to a PLBUS controller, which is characterized by comprising the following steps: S1. Remotely select a batch of multiple PLBUS controllers through the master station to start upgrading and adjust the upgrade information structure; S2. Based on S1, according to the status of the last upgrade information structure of the PLBUS controllers in the batch, the strategy of the PLBUS controllers in the batch is adjusted, and the PLBUS controllers after the strategy adjustment and not marked as poor communication are grouped together for batch upgrade in sequence; S3, based on S2, monitors the status of the grouped PLBUS controllers and establishes a feedback mechanism, and feeds back the status data of the PLBUS controllers to the master station through intelligent slicing and transmission algorithms; S4. Based on S3, the master station receives the status data of the PLBUS controller after the packet, starts the security upgrade mechanism, uses the Blake2s algorithm to calculate the checksum, uses two independent encrypted connections to transmit data and checksum information, and even transmits the cloud file and terminal upgrade content to the PLBUS controller; S5. Based on S4, after the PLBUS controller receives the cloud file and the terminal upgrade content, it performs interactive processing. If the interactive data between the terminal and the PLBUS controller is not frequent, the PLBUS controller chooses to perform dynamic adaptive strategy adjustment; if the interactive data between the terminal and the PLBUS controller is stable, an automatic switching mechanism is performed based on the last upgrade of the PLBUS controller, and a retry mechanism is performed; S6.1. Based on S5, the PLBUS controllers after the strategy adjustment are grouped. If the dynamic adaptive strategy is turned on, the PLBUS controllers that have failed the strategy adjustment in this round are upgraded first; if the dynamic adaptive strategy is turned off, the exception is recorded and the next project to be upgraded is continued; S6.2, based on S5, if the retry mechanism upgrade is successful, it means that the remote upgrade of this PLBUS controller is successful, and the upgrade of this PLBUS controller is ended; if the retry mechanism upgrade fails, intelligent rollback and version management are performed until the end.

[0004] Preferably, in step S2 and step S5, the method for adjusting the strategy includes the following steps: S7.1. According to the adjustment of the last measurement point, select the PLBUS controller that is not marked as poor communication, and use the group batch upgrade method. Through one upgrade command, the specific controller can be upgraded without waiting for each controller to reply one by one; S7.2. Based on S7.1, the interaction time threshold of a single PLBUS controller is calculated: S7.3, based on S7.2, record the time taken for successful interaction. If the time taken exceeds the set calculation threshold, mark the PLBUS controller as unstable communication. If the time taken does not exceed the set calculation threshold, mark the PLBUS controller as stable communication and proceed to the next step of upgrading. S7.4, based on S7.3, the PLBUS controller marked as stable communication is broadcast upgraded. If the PLBUS controller fails in the broadcast upgrade process, the PLBUS controller will be marked as poor communication and switched to unicast upgrade mode. If the PLBUS controller succeeds in the broadcast upgrade process, the PLBUS controller will be marked as stable communication. S7.5. Based on S7.3 and S7.4, calculate the overall success rate and failure rate of this upgrade respectively.

[0005] Preferably, in step S7.5, the overall success rate of this group upgrade is: PS1; The number of PLBUS controllers that have been successfully upgraded in the overall group = Nub + Ng; The number of controllers that successfully broadcast: Nub=x×PU1; The number of PLBUS controllers that are successfully grouped: Ng = Nuf × PS1 = (x × PU2) × PS1; The overall failure rate of this group upgrade is: PS2=1−PS1; The number of PLBUS controllers that failed to group as a whole = (x × PU2) × (1 − PS1); Where x represents the total number of PLBUS controllers; PU1 indicates the broadcast success rate; PU2 represents the broadcast failure rate; The number of PLBUS controllers that failed to group: Nuf × PS2; The number of controllers that failed to broadcast: Nuf = x × PU2.

[0006] Preferably, in step S5, the retry mechanism includes a retry triggered when the current interaction times out and a retry triggered when the PLBUS controller fails to reply; If the current interaction times out, the system will record the PLBUS controller and mark it as having poor communication. At the same time, the upgrade status, maximum time, number of retries and other information will be reported, and the upgrade of the PLBUS controller with good communication will be performed first; If the PLBUS controller fails to reply, a retry is triggered immediately. If it still fails within the specified retry count threshold, it is recorded as an upgrade exception and this measurement point is excluded in subsequent upgrades.

[0007] Preferably, the retry triggered by the PLBUS controller in the case of a failed reply includes the following two cases: If the current number of retries Rcurrent is less than the maximum number of retries Rmax, a retry is performed; If the retry interval Tretry is initially set to the default value, the shortest interaction threshold is obtained by subsequent policy adjustment; The retry upgrade process will be broadcast, multicast and unicast in sequence.

[0008] Preferably, in step S1, the method in which the master station remotely selects a batch of multiple PLBUS controllers to start upgrading includes the following steps: S1.1. The back-end staff selects a specific PLBUS controller type at the master station and sends the upgrade file to the terminal; S1.2. Based on S1.1, the terminal upgrade tool actively reads the version information of the PLBUS controller, calculates the subsequent upgrade strategy according to the communication status of the PLBUS controller, and reads and verifies the MD5 value of the upgrade file to ensure the integrity of the upgrade file; S1.3. Based on S1.2, the upgrade tool periodically reads the upgrade status to achieve real-time monitoring; S1.4, based on S1.3, after the upgrade is successful, the master station will confirm the final result after a delay of 2 minutes.

[0009] Compared with the prior art, the present invention has the following beneficial effects: (1) The present invention improves applicability and stability through enhanced algorithm design, significantly improves the efficiency, success rate, security and manageability of the upgrade process, has broad application value in the field of smart devices, and can effectively improve the functionality and user experience of the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 It is the overall flow chart of the present invention.

[0011] Figure 2 It is a flow chart of the security upgrade mechanism of the present invention.

[0012] Figure 3 This is a flow chart of the version management method of the present invention. DETAILED DESCRIPTION

[0013] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0014] In the description of the present invention, unless otherwise specified, "plurality" means two or more than two; the orientations or positional relationships indicated by the terms "upper", "lower", "left", "right", "inner", "outer", "front end", "rear end", "head", "tail", etc. are based on the orientations or positional relationships shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operate in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", "third", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance.

[0015] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "connected" and "connection" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0016] The remote upgrade method applicable to the PLBUS controller includes the following steps: S1. Remotely select a batch of multiple PLBUS controllers through the master station to start upgrading and adjust the upgrade information structure; Specifically, in step S1, the method in which the master station remotely selects a batch of multiple PLBUS controllers to start upgrading includes the following steps: S1.1. The back-end staff selects a specific PLBUS controller type at the master station and sends the upgrade file to the terminal; S1.2. Based on S1.1, the terminal upgrade tool actively reads the version information of the PLBUS controller, calculates the subsequent upgrade strategy according to the communication status of the PLBUS controller, and reads and verifies the MD5 value of the upgrade file to ensure the integrity of the upgrade file; S1.3. Based on S1.2, the upgrade tool periodically reads the upgrade status to achieve real-time monitoring; S1.4, based on S1.3, after the upgrade is successful, the master station will confirm the final result after a delay of 2 minutes.

[0017] The information structure in this embodiment at least includes the following contents: Upgrade file path: the location where the upgrade file is stored; Data to be transmitted: contains the specific data that needs to be upgraded; Number of times sent: counts the number of data packets sent; Last transmission status: records the status of the last transmission for subsequent monitoring; Whether to send the next frame: identifies whether to continue sending data frames; Last sending time: used to control the sending frequency.

[0018] The upgraded information structure makes data organization and analysis more efficient, and the optimized upgrade process reduces operation steps and time, improving user experience.

[0019] S2. Based on S1, according to the status of the last upgrade information structure of the PLBUS controllers in the batch, the strategy of the PLBUS controllers in the batch is adjusted, and the PLBUS controllers after the strategy adjustment and not marked as poor communication are grouped together for batch upgrade in sequence; S3, based on S2, monitors the status of the grouped PLBUS controllers and establishes a feedback mechanism, and feeds back the status data of the PLBUS controllers to the master station through intelligent slicing and transmission algorithms; Specifically, in this embodiment, the status of the grouped PLBUS controllers is monitored and a feedback mechanism is established. By monitoring the current upgrade status and feeding back to the user, it is convenient for the operator to understand the upgrade progress in a timely manner. For example, the current upgrade status is fed back through the status code, such as success, failure or unknown status; the feedback log recording function is designed to facilitate subsequent analysis and troubleshooting. The real-time status monitoring and feedback mechanism provides transparent information for remote upgrades. After each data transmission, the upgrade system will regularly report the current status to ensure that the operator can immediately understand the upgrade process and respond to problems quickly.

[0020] In this embodiment, the intelligent sharding and transmission algorithm includes the following three points: a) Adaptive setting of upgrade data block size: According to the response of carrier upgrade, the data block size is flexibly adjusted to optimize writing efficiency.

[0021] Write unit: Flash memory is usually written in units of page or sector. If the length of the data written in a single time is smaller than the size of the page or sector, it still needs to be fully written, and the actual writing time may not be significantly reduced.

[0022] Total write volume: If the length of the data written each time is close to the size of a page or sector, the write efficiency will be improved when processing large data blocks. On the contrary, frequent small data writes will increase the number of write operations, thereby increasing the overall time consumption.

[0023] Erase and write efficiency: In Flash memory, writing usually requires erasing first, and erasing is also done in units of pages or sectors. Frequent writing of small data will increase the number of erase operations and affect the overall efficiency.

[0024] Write times: Each Flash memory cell supports a limited number of writes (such as thousands to tens of thousands). Larger data writes help evenly distribute the write times, reduce wear on certain areas, and thus increase the success rate; while frequent small writes may cause some areas to reach the write limit early.

[0025] Adaptive adjustment: The maximum receiving length of the controller is 255 bytes. If the maximum transmission length is used, Flash writing will take a long time, and the controller may also experience delays or exceptions when processing data splicing. Therefore, the first upgrade will trigger dynamic adjustment of the data block size until the success rate reaches the optimal level.

[0026] b) Use CRC to calculate the checksum of each upgraded data block to ensure data integrity.

[0027] c) Use encrypted connections to transmit upgrade data blocks and verify integrity information separately to improve security. Ensure that the upgrade data obtained by the terminal can be accurately sent to the controller.

[0028] The intelligent sharding and transmission algorithm adopted by the present invention effectively reduces the network burden and improves the speed and success rate of data transmission.

[0029] S4. Based on S3, the master station receives the status data of the PLBUS controller after the packet, starts the security upgrade mechanism, uses the Blake2s algorithm to calculate the checksum, uses two independent encrypted connections to transmit data and checksum information, and even transmits the cloud file and terminal upgrade content to the PLBUS controller; Specifically, the security upgrade mechanism in this embodiment includes the following three points: d) Use Blake2s algorithm to calculate checksum and improve security: Cloud file transfer and terminal upgrade content transmission to controller e) Use two independent encrypted connections to transmit data and check information: CRC checks whether the file transmission content is complete, and ESAM encrypts the transmission data f) Multiple checks ensure data integrity.

[0030] The security upgrade mechanism of the present invention ensures the integrity and confidentiality of data and effectively prevents potential security threats.

[0031] S5. Based on S4, after the PLBUS controller receives the cloud file and the terminal upgrade content, it performs interactive processing. If the interactive data between the terminal and the PLBUS controller is not frequent, the PLBUS controller chooses to adjust the dynamic adaptive strategy. The dynamic adaptive strategy is adjusted according to the historical records to ensure the maximum optimization of the retry operation. If the interactive data between the terminal and the PLBUS controller is stable, an automatic switching mechanism is performed based on the last upgrade of the PLBUS controller, and a retry mechanism is performed; Specifically, in step S5, the retry mechanism includes a retry triggered in the case of a current interaction timeout and a retry triggered in the case of a PLBUS controller reply failure; If the current interaction times out, the system will record the PLBUS controller and mark it as having poor communication. At the same time, the upgrade status, maximum time, number of retries and other information will be reported, and the upgrade of the PLBUS controller with good communication will be performed first; If the PLBUS controller fails to reply, a retry is triggered immediately. If it still fails within the specified retry count threshold, it is recorded as an upgrade exception and this measurement point is excluded in subsequent upgrades.

[0032] The retry triggered by the PLBUS controller reply failure includes the following two situations: If the current number of retries Rcurrent is less than the maximum number of retries Rmax, a retry is performed; If the retry interval Tretry is initially set to the default value, the shortest interaction threshold is obtained by subsequent policy adjustment; The retry upgrade process will be broadcast, multicast and unicast in sequence.

[0033] The automatic switching mechanism can effectively ensure that the system maintains a stable upgrade experience under different network conditions.

[0034] S6.1. Based on S5, the PLBUS controllers after the strategy adjustment are grouped. If the dynamic adaptive strategy is turned on, the PLBUS controllers that have failed the strategy adjustment in this round are upgraded first; if the dynamic adaptive strategy is turned off, the exception is recorded and the next project to be upgraded is continued; S6.2, based on S5, if the retry mechanism upgrade is successful, it means that the remote upgrade of this PLBUS controller is successful, and the upgrade of this PLBUS controller is ended; if the retry mechanism upgrade fails, intelligent rollback and version management are performed until the end.

[0035] The powerful retry mechanism of the present invention can automatically retry when the upgrade fails, which minimizes the upgrade failure caused by occasional errors and improves the success rate. In addition, the intelligent rollback and version management functions allow rapid recovery to a stable version when the upgrade fails, while flexibly managing the switching between versions to reduce system downtime.

[0036] like Figure 3 As shown, the version management method in this embodiment includes the following steps: 6.2.1. Keep the old version files during the upgrade process to facilitate rollback; S6.2.2. Use a dual partition mechanism (APP2 area and application code area) to ensure that you can roll back to the old version if the upgrade fails; 6.2.3. The new version file will be moved to the application code area only after the upgrade is successful to ensure system stability.

[0037] Among them, the old version file identifier is saved in the BACKUPS storage area; the new version file is temporarily stored in the APP2 area; after the upgrade is completed, the new version file is moved to the application code area.

[0038] In step S2 and step S5, the method for adjusting the strategy includes the following steps: S7.1. According to the adjustment of the last measurement point, select the PLBUS controller that is not marked as poor communication, and use the group batch upgrade method. Through one upgrade command, the specific controller can be upgraded without waiting for each controller to reply one by one; S7.2. Based on S7.1, the interaction time threshold of a single PLBUS controller is calculated: S7.3, based on S7.2, record the time taken for successful interaction. If the time taken exceeds the set calculation threshold, mark the PLBUS controller as unstable communication. If the time taken does not exceed the set calculation threshold, mark the PLBUS controller as stable communication and proceed to the next step of upgrading. S7.4, based on S7.3, the PLBUS controller marked as stable communication is broadcast upgraded. If the PLBUS controller fails in the broadcast upgrade process, the PLBUS controller will be marked as poor communication and switched to unicast upgrade mode. If the PLBUS controller succeeds in the broadcast upgrade process, the PLBUS controller will be marked as stable communication. S7.5. Based on S7.3 and S7.4, calculate the overall success rate and failure rate of this upgrade respectively.

[0039] Specifically, the overall success rate of this group upgrade is: PS1; The number of PLBUS controllers that have been successfully upgraded in the overall group = Nub + Ng; The number of controllers that successfully broadcast: Nub=x×PU1; The number of PLBUS controllers that are successfully grouped: Ng = Nuf × PS1 = (x × PU2) × PS1; The overall failure rate of this group upgrade is: PS2=1−PS1; The number of PLBUS controllers that failed to group as a whole = (x × PU2) × (1 − PS1); Where x represents the total number of PLBUS controllers; PU1 indicates the broadcast success rate; PU2 represents the broadcast failure rate; The number of PLBUS controllers that failed to group: Nuf × PS2; The number of controllers that failed to broadcast: Nuf = x × PU2.

[0040] The master station can automatically adjust the upgrade strategy based on real-time data to adapt to changes in network load and device status to optimize the upgrade effect.

[0041] The PLBUS controller remote upgrade method provided by the present invention improves applicability and stability through enhanced algorithm design, significantly improves the efficiency, success rate, security and manageability of the upgrade process, has broad application value in the field of smart devices, and can effectively improve the functionality and user experience of the device.

[0042] The above-mentioned embodiments are only preferred embodiments of the present invention and cannot be used to limit the scope of rights of the present invention. Therefore, modifications, equivalent changes, improvements, etc. made according to the scope of the patent application of the present invention are still within the scope covered by the present invention.

Claims

1. A remote upgrade method applicable to a PLBUS controller, characterized in that: The following steps are involved: S1. Remotely select a batch of multiple PLBUS controllers through the master station to start upgrading and adjust the upgrade information structure; S2. Based on S1, according to the status of the last upgrade information structure of the PLBUS controllers in the batch, the strategy of the PLBUS controllers in the batch is adjusted, and the PLBUS controllers after the strategy adjustment and not marked as poor communication are grouped together for batch upgrade in sequence; S3, based on S2, monitors the status of the grouped PLBUS controllers and establishes a feedback mechanism, and feeds back the status data of the PLBUS controllers to the master station through intelligent slicing and transmission algorithms; S4. Based on S3, the master station receives the status data of the PLBUS controller after the packet, starts the security upgrade mechanism, uses the Blake2s algorithm to calculate the checksum, uses two independent encrypted connections to transmit data and checksum information, and even transmits the cloud file and terminal upgrade content to the PLBUS controller; S5. Based on S4, after the PLBUS controller receives the cloud file and the terminal upgrade content, it performs interactive processing. If the interactive data between the terminal and the PLBUS controller is not frequent, the PLBUS controller chooses to perform dynamic adaptive strategy adjustment; if the interactive data between the terminal and the PLBUS controller is stable, an automatic switching mechanism is performed based on the last upgrade of the PLBUS controller, and a retry mechanism is performed; S6.

1. Based on S5, the PLBUS controllers after the strategy adjustment are grouped. If the dynamic adaptive strategy is turned on, the PLBUS controllers that have failed the strategy adjustment in this round are upgraded first; if the dynamic adaptive strategy is turned off, the exception is recorded and the next project to be upgraded is continued; S6.2, based on S5, if the retry mechanism upgrade is successful, it means that the remote upgrade of this PLBUS controller is successful, and the upgrade of this PLBUS controller is ended; if the retry mechanism upgrade fails, intelligent rollback and version management are performed until the end.

2. A remote upgrade method applicable to a PLBUS controller according to claim 1, characterized in that: In step S2 and step S5, the method for adjusting the strategy includes the following steps: S7.

1. According to the adjustment of the last measurement point, select the PLBUS controller that is not marked as poor communication, and use the group batch upgrade method. Through one upgrade command, the specific controller can be upgraded without waiting for each controller to reply one by one; S7.

2. Based on S7.1, the interaction time threshold of a single PLBUS controller is calculated: S7.3, based on S7.2, record the time taken for successful interaction. If the time taken exceeds the set calculation threshold, mark the PLBUS controller as unstable communication. If the time taken does not exceed the set calculation threshold, mark the PLBUS controller as stable communication and proceed to the next step of upgrading. S7.4, based on S7.3, the PLBUS controller marked as stable communication is broadcast upgraded. If the PLBUS controller fails in the broadcast upgrade process, the PLBUS controller will be marked as poor communication and switched to unicast upgrade mode. If the PLBUS controller succeeds in the broadcast upgrade process, the PLBUS controller will be marked as stable communication. S7.

5. Based on S7.3 and S7.4, calculate the overall success rate and failure rate of this upgrade respectively.

3. A remote upgrade method applicable to a PLBUS controller according to claim 2, characterized in that: In step S7.5, the overall success rate of this group upgrade is: PS1; The number of PLBUS controllers that have been successfully upgraded in the overall group = Nub + Ng; The number of controllers that successfully broadcast: Nub=x×PU1; The number of PLBUS controllers that are successfully grouped: Ng = Nuf × PS1 = (x × PU2) × PS1; The overall failure rate of this group upgrade is: PS2=1−PS1; The number of PLBUS controllers that failed to group as a whole = (x × PU2) × (1 − PS1); Where x represents the total number of PLBUS controllers; PU1 indicates the broadcast success rate; PU2 represents the broadcast failure rate; The number of PLBUS controllers that failed to group: Nuf × PS2; The number of controllers that failed to broadcast: Nuf = x × PU2.

4. A remote upgrade method applicable to a PLBUS controller according to claim 3, characterized in that: In step S5, the retry mechanism includes a retry triggered when the current interaction times out and a retry triggered when the PLBUS controller fails to reply; If the current interaction times out, the system will record the PLBUS controller and mark it as having poor communication. At the same time, the upgrade status, maximum time, number of retries and other information will be reported, and the upgrade of the PLBUS controller with good communication will be performed first; If the PLBUS controller fails to reply, a retry is triggered immediately. If it still fails within the specified retry count threshold, it is recorded as an upgrade exception and this measurement point is excluded in subsequent upgrades.

5. A remote upgrade method applicable to a PLBUS controller according to claim 4, characterized in that: The retry triggered by the PLBUS controller reply failure includes the following two situations: If the current number of retries Rcurrent is less than the maximum number of retries Rmax, a retry is performed; If the retry interval Tretry is initially set to the default value, the shortest interaction threshold is obtained by subsequent policy adjustment; The retry upgrade process will be broadcast, multicast and unicast in sequence.

6. A remote upgrade method applicable to a PLBUS controller according to claim 1, characterized in that: In step S1, the method for the master station to remotely select a batch of multiple PLBUS controllers to start upgrading includes the following steps: S1.

1. The back-end staff selects a specific PLBUS controller type at the master station and sends the upgrade file to the terminal; S1.

2. Based on S1.1, the terminal upgrade tool actively reads the version information of the PLBUS controller, calculates the subsequent upgrade strategy according to the communication status of the PLBUS controller, and reads and verifies the MD5 value of the upgrade file to ensure the integrity of the upgrade file; S1.

3. Based on S1.2, the upgrade tool periodically reads the upgrade status to achieve real-time monitoring; S1.4, based on S1.3, after the upgrade is successful, the master station will confirm the final result after a delay of 2 minutes.

Images