An update rollback framework for patrolling members

Abstract

An update rollback framework, for patrolling members is disclosed. Said framework broadly comprises an at least a bootloading member (103). Said at least one bootloading member (103) is communicatively associated with an at least an application member. Said at least one application member broadly comprises a plurality of storage members. Said plurality of storage members includes: a first storage member (101); and a second storage member (102). Based on certain checks, if an updated program is detected as functioning, without any errors (or faults, or issues), by said framework, no further changes are made. On the other hand, if errors (or faults, or issues) are detected, said at least one bootloading member (103) is configured to automatically execute a non-updated program. The disclosed framework offers at least the following advantages: is simple in construction; is cost-effective; and enables updated programs to be sent out, without worrying about errors or bugs.

We claim: 
     
         1 . An update rollback framework, for patrolling members, comprising:
 an at least a bootloading member ( 103 ) that is communicatively associated with an at least an application member; and   said at least one application member that comprises a plurality of storage members; said plurality of storage members including:
 a first storage member ( 101 ) that is configured to hold an updated program; and 
 a second storage member ( 102 ) that is configured to hold a non-updated program, 
   
       with said at least one bootloading member ( 103 ) being configured to:
 download said updated program, onto said first storage member ( 101 ); 
 perform a hard reset, upon receiving a notification that said updated program is faulty; 
 execute said non-updated program, if said hard reset is performed; 
 transfer said updated program, to said second storage member ( 102 ), upon receiving a notification that said updated program is not faulty; and 
 perform a soft reset, after transferring said updated program, to said second storage member ( 102 ).