US20070220503A1 - Method For Upgrading The Communication Device - Google Patents

Method For Upgrading The Communication Device Download PDF

Info

Publication number
US20070220503A1
US20070220503A1 US10/586,952 US58695205A US2007220503A1 US 20070220503 A1 US20070220503 A1 US 20070220503A1 US 58695205 A US58695205 A US 58695205A US 2007220503 A1 US2007220503 A1 US 2007220503A1
Authority
US
United States
Prior art keywords
communication equipment
configuration data
server
update
iad
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US10/586,952
Other versions
US8495616B2 (en
Inventor
Jinfei Fan
Jiangfa She
Bing Luo
Weichuan Ye
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=34832060&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US20070220503(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Assigned to HUAWEI TECHNOLOGIES CO. LTD. reassignment HUAWEI TECHNOLOGIES CO. LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FAN, JINFEI, LUO, BING, SHE, JIANGFA, YE, WEICHUAN
Publication of US20070220503A1 publication Critical patent/US20070220503A1/en
Application granted granted Critical
Publication of US8495616B2 publication Critical patent/US8495616B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1433Saving, restoring, recovering or retrying at system level during software upgrading
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/085Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H04L41/0856Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to communication field, more particularly to a method for updating communication equipment.
  • the software to be updated is stored in an independent server, and then a data transmission connection is established between this server and the communication equipment to be updated, so that the software stored in the server can be transmitted to the communication equipment.
  • the corresponding files of the software stored in the server are directly transmitted to the communication equipment, and then the communication equipment loads the software to replace the old files with the new files, and the equipment is updated accordingly.
  • the communication equipment does not back up the old configuration data which includes the user data, therefore during the software update procedure, if the communication equipment is powered off or the updated files error happens and so on, the old configuration data may be lost, which can bring great loss to the operators.
  • the risk of losing data during the equipment update procedure exists in the prior art, which affects the security of the equipment update.
  • the software update procedure is not monitored. If an error occurs during the update procedure, e.g., the communication equipment is powered off or the updated files error happens, the old service ability of equipment may not be inherited after the update procedure is finished, which may lead to unsuccessful equipment update and harm the security of the equipment update.
  • the old software version is usually not saved during the update procedure, so the old software version is not available to the equipment anymore in the case of unsuccessful update. Therefore, after the unsuccessful update, the communication equipment may change into failure or fault and cannot function normally, which greatly affects the security of the equipment update.
  • the present invention is to provide a method for updating equipment that can implement a secure update, so as to avoid data loss from happening during the update procedure and make sure that the update is successful.
  • the present invention discloses a method for updating communication equipment in a communication system through a server, which stores updated files used for updating the communication equipment.
  • the method at least includes:
  • the step of backing up the configuration data in the communication equipment to the server further includes: the server monitoring the backup procedure of the configuration data and judging whether the configuration data are successfully backed up, if yes, executing the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update; otherwise, instructing the communication equipment to execute the backup operation for the configuration data again.
  • the step of the server judging whether the configuration data are successfully backed up includes: judging whether a backup failure message is received from the communication equipment or judging whether the backup operation exceeds a scheduled time. Moreover, before instructing the communication equipment to execute the backup operation for the configuration data again, the method further includes: notifying a user that the current configuration data backup has failed and asking the user whether to back up the data over again; after receiving the user's instruction to back up the data over again, executing the step of instructing the communication equipment to execute the backup operation again; otherwise, ending the current process.
  • the step of backing up the configuration data in the communication equipment to the server further includes:
  • the configuration data include one or more than one type among user data, port data, protocol parameter data and default parameter data for guaranteeing the normal operation of the equipment.
  • the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update further includes: the server monitoring the update procedure of the communication equipment and judging whether the update is successful, if yes, executing the step of recovering the configuration data backed up in the server to the communication equipment; otherwise, instructing the communication equipment to execute the update operation over again.
  • the server judging whether the update is successful includes: judging whether an update failure message is received from the communication equipment or judging whether the update operation exceeds the scheduled time. Moreover, before instructing the communication equipment to execute the update operation again, the method further includes: notifying the user that the current update has failed and asking the user whether to update the equipment over again or not; after receiving the user's instruction to update the equipment over again, executing the step of instructing the communication equipment to execute the update operation again; otherwise, ending the current process.
  • the method may further include a step of storing an old software version in the communication equipment before executing the update operation, and a step of instructing the communication equipment to recover the current software to the old version before instructing the communication equipment to execute the update operation over again.
  • the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update further includes:
  • the step of recovering the configuration data backed up in the server to the communication equipment further includes: the server monitoring the recovery procedure of the configuration data, and judging whether the configuration data are successfully recovered, if yes, ending the current process; otherwise, instructing the communication equipment to execute the recovery operation for the configuration data over again.
  • the server judging whether the configuration data are successfully recovered includes: judging whether a recovery failure message is received from the communication equipment or judging whether the recovery operation exceeds the scheduled time. Moreover, before instructing the communication equipment to execute the recovery operation for the configuration data over again, the method further includes: notifying the user that the current configuration data recovery has failed and asking the user whether to recover the configuration data over again; after receiving the user's instruction to recover the configuration data over again, executing the step of instructing the communication equipment to execute the recovery operation over again; otherwise, ending the current process.
  • the step of recovering the configuration data backed up in the server to the communication equipment further includes:
  • the step of recovering the configuration data backed up in the server to the communication equipment further includes a step of modifying the format of the configuration data.
  • the present invention further includes the process of backing up the configuration data before the update and recovering the configuration data after the update, so that data loss will not happen when the communication equipment power off happens or the update is unsuccessful and the old software version needs be maintained. So the present invention can avoid great loss for the operators due to the data loss and the security of the equipment update is improved accordingly.
  • the communication equipment operation is monitored all the time to judge whether the operation is successful. If the operation is unsuccessful, the corresponding operation will be executed again automatically, so that the configuration data can be backed up, the software can be updated and the configuration data can be recovered again even if the communication equipment is powered off or the update is unsuccessful. Therefore, the present invention can guarantee the update is successful anyway and thus improve the security of the equipment update.
  • the old software version can be stored before the update, so that the old software version is available once the update is unsuccessful.
  • the update is unsuccessful, new software cannot be run and the old software is not available, so the communication equipment changes into failure or fault, while the present invention can prevent such situation from happening and thus further improve the security of the equipment update.
  • FIG. 1 is a flowchart illustrating the equipment update method according to one embodiment of the present invention.
  • the communication equipment can be the equipment utilized in any fixed or mobile communication networks, such as exchangers, routers, Integrated Access Devices (IADs) and so on.
  • IAD Integrated Access Devices
  • the IAD can be the video telephone, the Media Gateway Control Protocol (MGCP) IAD, the Internet Protocol (IP) telephone terminal or others.
  • MGCP Media Gateway Control Protocol
  • IP Internet Protocol
  • FIG. 1 is a flowchart illustrating the whole equipment update method after adding the above-mentioned processes.
  • the configuration data are backed up at first. Specifically, firstly the FTP/TFTP server information is configured to the IAD through the IADMS, and then the IADMS sends an SNMP backup configuration data command to IAD. After receiving this command, the IAD transmits the configuration data to the specified FTP/TFTP server via the FTP/TFTP protocol.
  • the configuration data hereby can be one or more than one type among user data, port data, protocol parameter data and default parameter data for guaranteeing the normal operation of the equipment.
  • the configuration data can also be other types of data besides the above mentioned ones.
  • step 110 the procedure of backing up the configuration data is monitored. While backing up the configuration data, the IAD will report the current backup progress to the IADMS through the progress TRAP, so that the IADMS can acquire the backup status of the IAD through the progress TRAP received from the IAD, thus the monitor function is implemented.
  • step 120 the IADMS judges whether the configuration data are successfully backed up, if yes, executing the next step 130 ; otherwise, returning to the step 100 , which is to instruct the IAD to back up the configuration data over again, and the IAD will back up the configuration data over again after receiving this instruction.
  • the process of judging whether the configuration data are successfully backed up is to judge whether a backup failure TRAP is received or whether the backup procedure exceeds the scheduled time. If the IADMS receives the backup failure TRAP from the IAD or detects that the operating time of the backup procedure of the IAD exceeds the scheduled time, the IADMS confirms the backup has failed; otherwise, the backup is successful.
  • IADMS can notify a user that the current backup fails and that the user can choose whether to back up the data over again. After receiving the user's indication of backing up the data over again, the IADMS will instruct the IAD to back up the configuration data over again. If the user chooses not to back up the data anymore, the current process will be ended.
  • the equipment software is updated.
  • the IADMS sends an SNMP update command to the IAD, and this command comprises updated FTP/TFTP server address, updated files name and other information.
  • the IAD analyzes it and downloads the updated files from the FTP/TFTP server via the FTP/TFTP protocol, according to the FTP/TFTP server address, the updated files name and other information comprised in this command.
  • the IAD loads the updated files to implement the equipment software update.
  • the loaded software is not effective until resetting the equipment.
  • the IADMS needs to send an SNMP reset command to the IAD and request the IAD to reset.
  • the IAD resets itself after receiving this SNMP reset command, so that the current loaded new software version can be effective.
  • the above-illustrated reset process can be removed.
  • step 140 the update procedure of the equipment software is monitored. While downloading and loading the updated files, the IAD will report the current update progress to the IADMS through the progress TRAP, so that IADMS can acquire the update status of the IAD through the progress TRAP received from the IAD, thus the monitor function is implemented.
  • step 150 IADMS judges whether the equipment update is successful. If it is unsuccessful, it go to step 160 , i.e., the IADMS will instruct the IAD to recover the old software version before the software update, and the IAD will automatically replace the current software with the old one after receiving this indication. If the IADMS judges that update is successful, it will execute the next step 170 .
  • the step 130 will be automatically executed, which means the IADMS will instruct the equipment to execute the update process over again.
  • the update may be unsuccessful finally due to power off in the previous update procedure, executing the update process over again can guarantee the update function after the power is recovered; while if the update is unsuccessful because of the updated files error, the IADMS can re-specify the correct updated files name in the SNMP update command sent to the IAD so as to make sure that the update is successful this time.
  • the IADMS can also notify the user of this situation after the IAD has recovered the old software version.
  • the IADMS can also ask the user whether to update the equipment over again. After receiving the user's indication of updating equipment over again, the IADMS will instruct the IAD to execute the update operation over again. If the user chooses not to update anymore, the current process will be ended.
  • two memory buffers can be set inside the equipment to be updated, one for storing the software version before the update and the other for storing the new software version.
  • the equipment can read the old software version from the memory buffer that stores the software version before update so as to recover the old software. Since the two software versions are stored in two memory buffers respectively, the unsuccessful update will not affect the software version before update, so that communication equipment can recover the complete old software and will not change into failure or fault because of the abnormal operation.
  • the procedure of judging whether the update is successful is to judge whether an update failure TRAP is received or whether the update operation exceeds the scheduled time. If the IADMS receives the update failure TRAP from the IAD or determines that the update operation of IAD exceeds the scheduled time, the update is deemed as unsuccessful, otherwise, the update is successful.
  • the backup configuration data are recovered.
  • the IADMS sends the recovery configuration data command to the IAD, and the command comprises the address information of the FTP/TFTP server which stores the configuration data, the configuration data files name and so on.
  • the IAD analyzes this command and downloads the configuration data from the corresponding FTP/TFTP server via the FTP/TFTP protocol according to the FTP/TFTP server address, the configuration data name and other information comprised in this command. After downloading all the configuration data files, the IAD loads the updated files.
  • step 180 the recovery procedure of the configuration data is monitored. While downloading the configuration data and loading the configuration data, the IAD will report the current progress to the IADMS through the progress TRAP, so that the IADMS can acquire the recovery status of the IAD through the progress TRAP received from the IAD, thus the monitor function is implemented.
  • step 190 the IADMS judges whether the configuration data are successfully recovered, if yes, the equipment update procedure is successfully completed and the current process is ended. If the configuration data are not successfully recovered, the step 170 is executed, namely the IADMS instructs the IAD to recover the configuration data over again. After receiving this instruction, the IAD downloads and loads the configuration data over again.
  • the process of judging whether the configuration data are successfully recovered is to judge whether a recovery failure TRAP is received or whether the recovery procedure exceeds the scheduled time. If the IADMS receives the recovery failure TRAP from the IAD or determines that the recovery operation of the IAD exceeds the scheduled time, the IADMS confirms that the recovery operation fails; otherwise, the recovery operation is successful.
  • the IADMS can notify the user that current recovery operation fails and asks the user whether to recover the data over again. After receiving the user's instruction of recovering the data over again, the IADMS instructs the IAD to recover the configuration data over again. If the user chooses not to recover the data anymore, the current process will be ended.
  • the IADMS further judges whether it is needed to modify the configuration data, if yes, the IADMS notifies the user to modify the data or instructs the IAD to automatically modify the data by running an application program which is specially used for modifying the configuration data, and continues to execute the recovery operation for the configuration data in the step 170 after finishing the modification.
  • the configuration data modification like conversing configuration data's format, can make the new configuration data format accord with the requirement of the new software, so as to make sure the configuration data can be successfully applied in the new software environment.
  • the configuration data recovery may be unsuccessful finally because of the incorrect configuration data modification, when the IADMS finds the configuration data recovery unsuccessful, it will return to the process of instructing the user to modify the configuration data or instructing the IAD to run the application program to modify the configuration data. After the configuration data are correctly modified, the configuration data are recovered again so as to make sure the configuration data can be successfully recovered.

Abstract

Disclosed is a method for updating communication equipment through a server in a communication system, where the server stores the updated files used for updating the communication equipment. In this method, configuration data in the communication equipment are backed up in the server at first, and then the updated files are downloaded to the communication equipment from the server, and the updated files are loaded to the communication equipment to implement the communication equipment update; at last, the configuration data backed up in the server are recovered to the communication equipment. The disclosed method can guarantee the successful update of the communication equipment and no data loss after the update, thus the security of the communication equipment update is greatly improved.

Description

    FIELD OF THE TECHNOLOGY
  • The present invention relates to communication field, more particularly to a method for updating communication equipment.
  • BACKGROUND OF THE INVENTION
  • In the communication field, as new technologies and new services continuously emerge, the software of the communication equipment needs to be updated frequently, so as to maintain and optimize the communication network and provide more extensive and better communication services. Software update involves almost all communication equipment, such as exchangers, routers, Integrated Access Devices (IADs) and so on.
  • In all the existing software update procedures, the software to be updated is stored in an independent server, and then a data transmission connection is established between this server and the communication equipment to be updated, so that the software stored in the server can be transmitted to the communication equipment. During the update procedure, the corresponding files of the software stored in the server are directly transmitted to the communication equipment, and then the communication equipment loads the software to replace the old files with the new files, and the equipment is updated accordingly.
  • However, in the existing methods for updating equipment, the communication equipment does not back up the old configuration data which includes the user data, therefore during the software update procedure, if the communication equipment is powered off or the updated files error happens and so on, the old configuration data may be lost, which can bring great loss to the operators. In other words, the risk of losing data during the equipment update procedure exists in the prior art, which affects the security of the equipment update.
  • In addition, in the existing methods for updating equipment, the software update procedure is not monitored. If an error occurs during the update procedure, e.g., the communication equipment is powered off or the updated files error happens, the old service ability of equipment may not be inherited after the update procedure is finished, which may lead to unsuccessful equipment update and harm the security of the equipment update.
  • Moreover, in the existing communication equipment, the old software version is usually not saved during the update procedure, so the old software version is not available to the equipment anymore in the case of unsuccessful update. Therefore, after the unsuccessful update, the communication equipment may change into failure or fault and cannot function normally, which greatly affects the security of the equipment update.
  • SUMMARY OF THE INVENTION
  • In view of the above, the present invention is to provide a method for updating equipment that can implement a secure update, so as to avoid data loss from happening during the update procedure and make sure that the update is successful.
  • The present invention discloses a method for updating communication equipment in a communication system through a server, which stores updated files used for updating the communication equipment. The method at least includes:
      • backing up configuration data in the communication equipment to the server;
      • downloading the updated files to the communication equipment from the server, and loading the updated files to the communication equipment to implement the communication equipment update;
      • recovering the configuration data backed up in the server to the communication equipment.
  • Preferably, the step of backing up the configuration data in the communication equipment to the server further includes: the server monitoring the backup procedure of the configuration data and judging whether the configuration data are successfully backed up, if yes, executing the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update; otherwise, instructing the communication equipment to execute the backup operation for the configuration data again.
  • Hereby, the step of the server judging whether the configuration data are successfully backed up includes: judging whether a backup failure message is received from the communication equipment or judging whether the backup operation exceeds a scheduled time. Moreover, before instructing the communication equipment to execute the backup operation for the configuration data again, the method further includes: notifying a user that the current configuration data backup has failed and asking the user whether to back up the data over again; after receiving the user's instruction to back up the data over again, executing the step of instructing the communication equipment to execute the backup operation again; otherwise, ending the current process.
  • When the communication equipment is an Integrated Access Device (IAD), and the server is a File Transfer Protocol/Trivial File Transfer Protocol (FTP/TFTP) server, the step of backing up the configuration data in the communication equipment to the server further includes:
      • an IAD Management System (IADMS) sending a Simple Network Management Protocol (SNMP) backup configuration data command to the IAD;
      • and the step of backing up the configuration data in the communication equipment to the server includes:
      • after receiving the SNMP backup configuration data command, the IAD transmitting the configuration data files to the specified FTP/TFTP server via the FTP/TFTP protocol.
  • The configuration data include one or more than one type among user data, port data, protocol parameter data and default parameter data for guaranteeing the normal operation of the equipment.
  • Preferably, the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update further includes: the server monitoring the update procedure of the communication equipment and judging whether the update is successful, if yes, executing the step of recovering the configuration data backed up in the server to the communication equipment; otherwise, instructing the communication equipment to execute the update operation over again.
  • Hereby, the server judging whether the update is successful includes: judging whether an update failure message is received from the communication equipment or judging whether the update operation exceeds the scheduled time. Moreover, before instructing the communication equipment to execute the update operation again, the method further includes: notifying the user that the current update has failed and asking the user whether to update the equipment over again or not; after receiving the user's instruction to update the equipment over again, executing the step of instructing the communication equipment to execute the update operation again; otherwise, ending the current process.
  • The method may further include a step of storing an old software version in the communication equipment before executing the update operation, and a step of instructing the communication equipment to recover the current software to the old version before instructing the communication equipment to execute the update operation over again.
  • When the communication equipment is the IAD, and the server is the FTP/TFTP server, the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update further includes:
      • the IADMS sending an SNMP update command which includes the address information of the FTP/TFTP server and the name information of the updated files;
      • and the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment includes:
      • after receiving the SNMP update command, the IAD downloading the updated files corresponding to the updated files name from the specified FTP/TFTP server via the FTP/TFTP protocol, and then loading the updated files.
  • Preferably, the step of recovering the configuration data backed up in the server to the communication equipment further includes: the server monitoring the recovery procedure of the configuration data, and judging whether the configuration data are successfully recovered, if yes, ending the current process; otherwise, instructing the communication equipment to execute the recovery operation for the configuration data over again.
  • Hereby, the server judging whether the configuration data are successfully recovered includes: judging whether a recovery failure message is received from the communication equipment or judging whether the recovery operation exceeds the scheduled time. Moreover, before instructing the communication equipment to execute the recovery operation for the configuration data over again, the method further includes: notifying the user that the current configuration data recovery has failed and asking the user whether to recover the configuration data over again; after receiving the user's instruction to recover the configuration data over again, executing the step of instructing the communication equipment to execute the recovery operation over again; otherwise, ending the current process.
  • When the communication equipment is the IAD, and the server is the FTP/TFTP server, the step of recovering the configuration data backed up in the server to the communication equipment further includes:
      • the IADMS sending an SNMP recovery configuration data command which includes the address information of the FTP/TFTP server and the name information of the configuration data files;
      • and the step of recovering the configuration data backed up in the server to the communication equipment includes:
      • after receiving the SNMP recovery configuration data command, the IAD downloading the configuration data files corresponding to the configuration data files name from the specified FTP/TFTP server via the FTP/TFTP protocol, and then loading the configuration data files.
  • The step of recovering the configuration data backed up in the server to the communication equipment further includes a step of modifying the format of the configuration data.
  • It can be seen from the above-mentioned technical schemes that, besides the equipment update by directly downloading the updated files and loading the updated files according to the prior art, the present invention further includes the process of backing up the configuration data before the update and recovering the configuration data after the update, so that data loss will not happen when the communication equipment power off happens or the update is unsuccessful and the old software version needs be maintained. So the present invention can avoid great loss for the operators due to the data loss and the security of the equipment update is improved accordingly.
  • During the procedures of backing up the configuration data, updating the software and recovering the configuration data, the communication equipment operation is monitored all the time to judge whether the operation is successful. If the operation is unsuccessful, the corresponding operation will be executed again automatically, so that the configuration data can be backed up, the software can be updated and the configuration data can be recovered again even if the communication equipment is powered off or the update is unsuccessful. Therefore, the present invention can guarantee the update is successful anyway and thus improve the security of the equipment update.
  • Moreover, in the present invention, the old software version can be stored before the update, so that the old software version is available once the update is unsuccessful. In the prior art, once the update is unsuccessful, new software cannot be run and the old software is not available, so the communication equipment changes into failure or fault, while the present invention can prevent such situation from happening and thus further improve the security of the equipment update.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a flowchart illustrating the equipment update method according to one embodiment of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • The present invention will be further described in detail hereinafter with reference to the accompanying drawings and specific embodiments.
  • The communication equipment can be the equipment utilized in any fixed or mobile communication networks, such as exchangers, routers, Integrated Access Devices (IADs) and so on. Hereby the IAD can be the video telephone, the Media Gateway Control Protocol (MGCP) IAD, the Internet Protocol (IP) telephone terminal or others. The following embodiment will be illustrated taking the IAD for example, but those skilled in the art should understand that all the above illustrations can be applied in the other communication equipment without any obstacles.
  • In the prior art, the data can be easily lost and the software update is not guaranteed to be successful. In order to solve such problems, processes of backing up the configuration data, recovering the configuration data and monitoring the whole software update procedure are added to the present invention. FIG. 1 is a flowchart illustrating the whole equipment update method after adding the above-mentioned processes.
  • As shown in FIG. 1, in step 100, the configuration data are backed up at first. Specifically, firstly the FTP/TFTP server information is configured to the IAD through the IADMS, and then the IADMS sends an SNMP backup configuration data command to IAD. After receiving this command, the IAD transmits the configuration data to the specified FTP/TFTP server via the FTP/TFTP protocol.
  • The configuration data hereby can be one or more than one type among user data, port data, protocol parameter data and default parameter data for guaranteeing the normal operation of the equipment. Of course, those skilled in the art should understand that the configuration data can also be other types of data besides the above mentioned ones.
  • In step 110, the procedure of backing up the configuration data is monitored. While backing up the configuration data, the IAD will report the current backup progress to the IADMS through the progress TRAP, so that the IADMS can acquire the backup status of the IAD through the progress TRAP received from the IAD, thus the monitor function is implemented.
  • In step 120, the IADMS judges whether the configuration data are successfully backed up, if yes, executing the next step 130; otherwise, returning to the step 100, which is to instruct the IAD to back up the configuration data over again, and the IAD will back up the configuration data over again after receiving this instruction.
  • The process of judging whether the configuration data are successfully backed up is to judge whether a backup failure TRAP is received or whether the backup procedure exceeds the scheduled time. If the IADMS receives the backup failure TRAP from the IAD or detects that the operating time of the backup procedure of the IAD exceeds the scheduled time, the IADMS confirms the backup has failed; otherwise, the backup is successful.
  • Moreover, after confirming the backup has failed, IADMS can notify a user that the current backup fails and that the user can choose whether to back up the data over again. After receiving the user's indication of backing up the data over again, the IADMS will instruct the IAD to back up the configuration data over again. If the user chooses not to back up the data anymore, the current process will be ended.
  • In step 130, the equipment software is updated. Firstly, the IADMS sends an SNMP update command to the IAD, and this command comprises updated FTP/TFTP server address, updated files name and other information. After receiving this command, the IAD analyzes it and downloads the updated files from the FTP/TFTP server via the FTP/TFTP protocol, according to the FTP/TFTP server address, the updated files name and other information comprised in this command. After downloading all the updated files, the IAD loads the updated files to implement the equipment software update.
  • In addition, as to some communication equipment, the loaded software is not effective until resetting the equipment. In this case, the IADMS needs to send an SNMP reset command to the IAD and request the IAD to reset. The IAD resets itself after receiving this SNMP reset command, so that the current loaded new software version can be effective. Of course, as to those communication equipment that can make the loaded software effective without resetting themselves, the above-illustrated reset process can be removed.
  • In step 140, the update procedure of the equipment software is monitored. While downloading and loading the updated files, the IAD will report the current update progress to the IADMS through the progress TRAP, so that IADMS can acquire the update status of the IAD through the progress TRAP received from the IAD, thus the monitor function is implemented.
  • In step 150, IADMS judges whether the equipment update is successful. If it is unsuccessful, it go to step 160, i.e., the IADMS will instruct the IAD to recover the old software version before the software update, and the IAD will automatically replace the current software with the old one after receiving this indication. If the IADMS judges that update is successful, it will execute the next step 170.
  • In the present embodiment, after the step 160, which means after the IAD has replaced the current software version with the old one, the step 130 will be automatically executed, which means the IADMS will instruct the equipment to execute the update process over again. As the update may be unsuccessful finally due to power off in the previous update procedure, executing the update process over again can guarantee the update function after the power is recovered; while if the update is unsuccessful because of the updated files error, the IADMS can re-specify the correct updated files name in the SNMP update command sent to the IAD so as to make sure that the update is successful this time.
  • Of course, the IADMS can also notify the user of this situation after the IAD has recovered the old software version. The IADMS can also ask the user whether to update the equipment over again. After receiving the user's indication of updating equipment over again, the IADMS will instruct the IAD to execute the update operation over again. If the user chooses not to update anymore, the current process will be ended.
  • In the present invention, two memory buffers can be set inside the equipment to be updated, one for storing the software version before the update and the other for storing the new software version. In this way, if the current update is unsuccessful, the equipment can read the old software version from the memory buffer that stores the software version before update so as to recover the old software. Since the two software versions are stored in two memory buffers respectively, the unsuccessful update will not affect the software version before update, so that communication equipment can recover the complete old software and will not change into failure or fault because of the abnormal operation.
  • The procedure of judging whether the update is successful is to judge whether an update failure TRAP is received or whether the update operation exceeds the scheduled time. If the IADMS receives the update failure TRAP from the IAD or determines that the update operation of IAD exceeds the scheduled time, the update is deemed as unsuccessful, otherwise, the update is successful.
  • In step 170, the backup configuration data are recovered. The IADMS sends the recovery configuration data command to the IAD, and the command comprises the address information of the FTP/TFTP server which stores the configuration data, the configuration data files name and so on. After receiving this command, the IAD analyzes this command and downloads the configuration data from the corresponding FTP/TFTP server via the FTP/TFTP protocol according to the FTP/TFTP server address, the configuration data name and other information comprised in this command. After downloading all the configuration data files, the IAD loads the updated files.
  • In step 180, the recovery procedure of the configuration data is monitored. While downloading the configuration data and loading the configuration data, the IAD will report the current progress to the IADMS through the progress TRAP, so that the IADMS can acquire the recovery status of the IAD through the progress TRAP received from the IAD, thus the monitor function is implemented.
  • In step 190, the IADMS judges whether the configuration data are successfully recovered, if yes, the equipment update procedure is successfully completed and the current process is ended. If the configuration data are not successfully recovered, the step 170 is executed, namely the IADMS instructs the IAD to recover the configuration data over again. After receiving this instruction, the IAD downloads and loads the configuration data over again.
  • The process of judging whether the configuration data are successfully recovered is to judge whether a recovery failure TRAP is received or whether the recovery procedure exceeds the scheduled time. If the IADMS receives the recovery failure TRAP from the IAD or determines that the recovery operation of the IAD exceeds the scheduled time, the IADMS confirms that the recovery operation fails; otherwise, the recovery operation is successful.
  • Moreover, after confirming that the recovery operation fails, the IADMS can notify the user that current recovery operation fails and asks the user whether to recover the data over again. After receiving the user's instruction of recovering the data over again, the IADMS instructs the IAD to recover the configuration data over again. If the user chooses not to recover the data anymore, the current process will be ended.
  • In some cases, like when the new software and old software are different from each other, it is needed to modify the configuration data properly, so that the configuration data can be successfully applied in the new software environment after being recovered, i.e. the configuration data can be successfully recovered. Hereby after the IAD resets in the above-mentioned step 170, the IADMS further judges whether it is needed to modify the configuration data, if yes, the IADMS notifies the user to modify the data or instructs the IAD to automatically modify the data by running an application program which is specially used for modifying the configuration data, and continues to execute the recovery operation for the configuration data in the step 170 after finishing the modification. Hereby, the configuration data modification, like conversing configuration data's format, can make the new configuration data format accord with the requirement of the new software, so as to make sure the configuration data can be successfully applied in the new software environment.
  • In case of needing to modify the configuration data, the configuration data recovery may be unsuccessful finally because of the incorrect configuration data modification, when the IADMS finds the configuration data recovery unsuccessful, it will return to the process of instructing the user to modify the configuration data or instructing the IAD to run the application program to modify the configuration data. After the configuration data are correctly modified, the configuration data are recovered again so as to make sure the configuration data can be successfully recovered.
  • The above mentioned is just the preferred embodiment of the present invention and not used to confine the present invention. Any modification, equivalent substitute and improvement within the spirit of the present invention are with the protection scope of the present invention.

Claims (16)

1. A method for updating communication equipment in a communication system through a server, which stores updated files used for updating the communication equipment, comprising:
backing up configuration data in the communication equipment to the server;
downloading the updated files to the communication equipment from the server, and loading the updated files to the communication equipment to implement the communication equipment update;
recovering the configuration data backed up in the server to the communication equipment.
2. The method according to claim 1, wherein, the step of backing up the configuration data in the communication equipment to the server further comprises:
the server monitoring the backup procedure of the configuration data and judging whether the configuration data are successfully backed up, if yes, executing the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update; otherwise, instructing the communication equipment to execute the backup operation for the configuration data again.
3. The method according to claim 2, wherein, the step of the server judging whether the configuration data are successfully backed up comprises one of the two following procedures:
judging whether a backup failure message is received from the communication equipment; and
judging whether the backup operation exceeds a scheduled time.
4. The method according to claim 2, before instructing the communication equipment to execute the backup operation for the configuration data again further comprising:
notifying a user the current configuration data backup has failed and asking the user whether to back up the data over again; after receiving the user's instruction to back up the data over again, executing the step of instructing the communication equipment to execute the backup operation again; otherwise, ending the current process.
5. The method according to claim 1, wherein, the communication equipment is an Integrated Access Device (IAD) and the server is a File Transfer Protocol/Trivial File Transfer Protocol (FTP/TFTP) server, and the step of backing up the configuration data in the communication equipment to the server further comprises:
an IAD Management System (IADMS) sending a Simple Network Management Protocol (SNMP) backup configuration data command to the IAD;
and the step of backing up the configuration data in the communication equipment to the server comprises: after receiving the SNMP backup configuration data command, the IAD transmitting the configuration data files to the specified FTP/TFTP server via the FTP/TFTP protocol.
6. The method according to claim 1, wherein, the configuration data comprise one or more than one type among user data, port data, protocol parameter data and default parameter data for guaranteeing the normal operation of the equipment.
7. The method according to claim 1, wherein, the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update further comprises:
the server monitoring the update procedure of the communication equipment and judging whether the update is successful, if yes, executing the step of recovering the configuration data backed up in the server to the communication equipment; otherwise, instructing the communication equipment to execute the update operation over again.
8. The method according to claim 7, wherein, the step of the server judging whether the update is successful comprises one of the two following procedures:
judging whether an update failure message is received from the communication equipment; and
judging whether the update operation exceeds the scheduled time.
9. The method according to claim 7, before instructing the communication equipment to execute the update operation again further comprising:
notifying the user that the current update has failed and asking the user whether to update the equipment over again; after receiving the user's instruction to update the equipment over again, executing the step of instructing the communication equipment to execute the update operation over again; otherwise, ending the current process.
10. The method according to claim 7, further comprising: a step of storing an old software version in the communication equipment before executing the update operation, and
a step of instructing the communication equipment to recover the current software to the old version before instructing the communication equipment to execute the update operation over again.
11. The method according to claim 1, wherein, the communication equipment is the IAD, and the server is the FTP/TFTP server, and the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment to implement the communication update further comprises:
the IADMS sending an SNMP update command which comprises the address information of the FTP/TFTP server and the name information of the updated files;
and the step of downloading the updated files to the communication equipment from the server and loading the updated files to the communication equipment comprises:
after receiving the SNMP update command, the IAD downloading the updated files corresponding to the updated files name from the specified FTP/TFTP server via the FTP/TFTP protocol, and then loading the updated files.
12. The method according to claim 1, wherein, the step of recovering the configuration data backed up in the server to the communication equipment further comprises:
the server monitoring the recovery procedure of the configuration data, and judging whether the configuration data are successfully recovered, if yes, ending the current process; otherwise, instructing the communication equipment to execute the recovery operation for the configuration data over again.
13. The method according to claim 12, wherein, the step of the server judging whether the configuration data are successful recovered comprises one of the two following procedures:
judging whether a recovery failure message is received from the communication equipment; and
judging whether the recovery operation exceeds the scheduled time.
14. The method according to claim 12, before instructing the communication equipment to execute the recovery operation for the configuration data over again, further comprising:
notifying the user that the current configuration data recovery has failed and asking the user whether to recover the configuration data over again; after receiving the user's instruction to recover the configuration data over again, executing the step of instructing the communication equipment to execute the recovery operation over again; otherwise, ending the current process.
15. The method according to claim 1, wherein, the communication equipment is the IAD, and the server is the FTP/TFTP server, and the step of recovering the configuration data backed up in the server to the communication equipment further comprises:
the IADMS sending an SNMP recovery configuration data command which comprises the address information of the FTP/TFTP server and the name information of the configuration data files;
and the step of recovering the configuration data backed up in the server to the communication equipment comprises:
after receiving the SNMP recovery configuration data command, the IAD downloading the configuration data files corresponding to the configuration data files name from the specified FTP/TFTP server via the FTP/TFTP protocol, and then loading the configuration data files.
16. The method according to claim 1, wherein, the step of recovering the configuration data backed up in the server to the communication equipment further comprises a step of modifying the format of the configuration data.
US10/586,952 2004-02-04 2005-02-04 Method for upgrading communication equipment Active 2028-10-13 US8495616B2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CNB2004100051442A CN100372294C (en) 2004-02-04 2004-02-04 Appratus upgrading method
CN200410005144 2004-02-04
CN200410005144.2 2004-02-04
PCT/CN2005/000159 WO2005076525A1 (en) 2004-02-04 2005-02-04 A Method for Upgrading the Communication Device

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/000159 A-371-Of-International WO2005076525A1 (en) 2004-02-04 2005-02-04 A Method for Upgrading the Communication Device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/864,965 Continuation US10007502B2 (en) 2004-02-04 2013-04-17 Method for upgrading communication device

Publications (2)

Publication Number Publication Date
US20070220503A1 true US20070220503A1 (en) 2007-09-20
US8495616B2 US8495616B2 (en) 2013-07-23

Family

ID=34832060

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/586,952 Active 2028-10-13 US8495616B2 (en) 2004-02-04 2005-02-04 Method for upgrading communication equipment
US13/864,965 Active US10007502B2 (en) 2004-02-04 2013-04-17 Method for upgrading communication device

Family Applications After (1)

Application Number Title Priority Date Filing Date
US13/864,965 Active US10007502B2 (en) 2004-02-04 2013-04-17 Method for upgrading communication device

Country Status (7)

Country Link
US (2) US8495616B2 (en)
EP (1) EP1713198B2 (en)
CN (1) CN100372294C (en)
AT (1) ATE403996T1 (en)
DE (1) DE602005008712D1 (en)
ES (1) ES2310809T5 (en)
WO (1) WO2005076525A1 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080086229A1 (en) * 2006-08-24 2008-04-10 Hitachi Kokusai Electric Inc. Substrate processing system
US20080134167A1 (en) * 2005-01-17 2008-06-05 Jong Jin Chae Method for Representing Description Language and Data Structure to Update Pump Tool, Ipmp Tool Updating Method and Client Apparatus Using the Same
US20110055823A1 (en) * 2009-08-27 2011-03-03 Microsoft Corporation Logical Migration Of Applications And Data
US20110167418A1 (en) * 2005-05-27 2011-07-07 Niraj Gopal Method for supporting new network element software versions in an element management system without upgrading
US20120016972A1 (en) * 2010-07-13 2012-01-19 Fujitsu Telecom Networks Limited Snmp agent device and configuration undo method
CN111865670A (en) * 2020-07-03 2020-10-30 宏图智能物流股份有限公司 Warehouse network rapid recovery method and warehouse network rapid recovery server
US20230333936A1 (en) * 2022-04-15 2023-10-19 Dell Products L.P. Smart cataloging of excluded data

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100461696C (en) * 2006-08-04 2009-02-11 华为技术有限公司 Method for remote updating equipment
CN1976517B (en) * 2006-11-30 2010-08-11 华为技术有限公司 Mobile terminal
CN102082730B (en) * 2011-02-09 2014-12-31 中兴通讯股份有限公司 Router upgrading method and router
CN104104527A (en) * 2013-04-03 2014-10-15 华为终端有限公司 Upgrade method for access terminal device and access terminal device
US20140344800A1 (en) * 2013-05-20 2014-11-20 Trane International Inc. Device and method for device identification and file transfer to bacnet devices
CN103414771B (en) * 2013-08-05 2017-02-15 国云科技股份有限公司 Monitoring method for long task operation between nodes in cloud computing environment
CN105320528A (en) * 2014-06-30 2016-02-10 广东九联科技股份有限公司 Router with automatic system updating function and method for automatically updating system
US20160085538A1 (en) * 2014-09-22 2016-03-24 Qualcomm Technologies International, Ltd. Over-the-air updates for ble devices
CN106469069B (en) * 2015-08-17 2021-06-11 中兴通讯股份有限公司 Version upgrading method and system
JP2017228246A (en) * 2016-06-24 2017-12-28 株式会社リコー Information processing apparatus, information processing system, program, and information processing method
EP4270796A3 (en) * 2017-07-21 2024-01-17 Apple Inc. Multiradio interface for software reconfiguration
CN107945858A (en) * 2017-12-14 2018-04-20 无锡祥生医疗科技股份有限公司 Upgrading backup method, the apparatus and system of diasonograph
CN108984193A (en) * 2018-06-21 2018-12-11 深圳伊泉净品科技有限公司 Software service dispositions method
CN109358871B (en) * 2018-09-18 2022-11-15 深圳Tcl数字技术有限公司 Method and device for replacing application system of embedded system equipment and storage medium
CN109358892B (en) * 2018-09-26 2022-04-05 潍柴动力股份有限公司 Software version upgrading method and device
US20210157696A1 (en) * 2019-11-22 2021-05-27 Rohde & Schwarz Gmbh & Co. Kg Radio frequency test and measurement device, system and method
CN111258608A (en) * 2020-01-16 2020-06-09 宁波三星医疗电气股份有限公司 Software upgrading method and device for terminal equipment and electronic system

Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6023620A (en) * 1997-02-26 2000-02-08 Telefonaktiebolaget Lm Ecrisson Method for downloading control software to a cellular telephone
US6119212A (en) * 1997-04-23 2000-09-12 Advanced Micro Devices, Inc. Root size decrease on a UNIX based computer system
US20020023258A1 (en) * 2000-06-27 2002-02-21 Elwahab Amgad Mazen System and method for managing telecommunications devices
US20020072350A1 (en) * 2000-12-08 2002-06-13 Atsushi Fukuzato Backup method of applications of portable cellular phone
US20020104080A1 (en) * 2000-03-29 2002-08-01 Virtual Access Networks, Inc. Server based extraction, transfer, storage and processing of remote settings, files and data
US20030037323A1 (en) * 2001-08-18 2003-02-20 Lg Electronics Inc. Method for upgrading data
US20030041133A1 (en) * 2001-07-27 2003-02-27 Hitachi, Ltd. Method for providing information apparatus together with setups transfer service
US20030204578A1 (en) * 2002-04-26 2003-10-30 Michael Yip Method and apparatus for restoring the configuration of a network device
US20030204711A1 (en) * 2002-04-29 2003-10-30 Guess Alan J. Method and system for restoring custom user configuration settings across a host application download
US20030225985A1 (en) * 2002-05-31 2003-12-04 William J. Ruenle Vp & Cfo Interleaver for iterative decoder
US20030225986A1 (en) * 2002-04-23 2003-12-04 Casio Computer Co., Ltd. Program install method, file renewal method, program and computer system
US20040015940A1 (en) * 2001-05-29 2004-01-22 3Com Corporation Intelligent device upgrade engine
US20040068721A1 (en) * 2000-11-17 2004-04-08 O'neill Patrick Network for updating firmware and / or software in wireless communication devices
US20040093597A1 (en) * 2002-11-05 2004-05-13 Rao Bindu Rama Firmware update system for facilitating firmware update in mobile handset related applications
US6832373B2 (en) * 2000-11-17 2004-12-14 Bitfone Corporation System and method for updating and distributing information
US20040261072A1 (en) * 2003-06-20 2004-12-23 Samsung Electronics Co., Ltd. Apparatus and method for performing an over-the-air software update in a dual processor mobile station
US6836657B2 (en) * 2002-11-12 2004-12-28 Innopath Software, Inc. Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade
US20050132351A1 (en) * 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback
US20050144616A1 (en) * 2003-10-27 2005-06-30 Hammond Brad T. System and method for updating a software program
US20050289533A1 (en) * 2002-10-09 2005-12-29 Xpoint Technologies, Inc. Method and system for updating a software image
US7221912B2 (en) * 2003-08-29 2007-05-22 Lucent Technologies Inc. Telecommunications management interface system
US7386846B2 (en) * 2001-07-26 2008-06-10 Kyocera Wireless Corp. System and method for the management of wireless communications device system software downloads in the field
US7472386B2 (en) * 2001-09-24 2008-12-30 Siemens Energy & Automation, Inc. Method for utilizing remote data access to provide engineering tool services

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020004935A1 (en) * 2000-07-03 2002-01-10 Huotari Allen Joseph System for remote automated installation and configuration of digital subscriber line modems
US6931558B1 (en) * 2000-11-29 2005-08-16 Veritas Operating Corporation Computer restoration systems and methods
JP3938475B2 (en) * 2001-03-29 2007-06-27 株式会社日立製作所 Backup processing method, its execution system, and its processing program
EP1267261A3 (en) 2001-05-08 2006-09-06 Pioneer Corporation Upgrade method for navigation data and apparatus for saving user data
KR100440950B1 (en) 2001-06-30 2004-07-21 삼성전자주식회사 Method for upgrading software in network environment and network device thereof
US20030084337A1 (en) * 2001-10-03 2003-05-01 Simionescu Dan C. Remotely controlled failsafe boot mechanism and manager for a network device
US6728833B2 (en) * 2002-02-28 2004-04-27 International Business Machines Corporation Upgrading firmware on disks of the raid storage system without deactivating the server
US6996818B2 (en) * 2002-11-22 2006-02-07 Bitfone Corporation Update system for facilitating software update and data conversion in an electronic device
KR100936390B1 (en) * 2002-11-26 2010-01-14 삼성전자주식회사 Method for data backup and recovery
US7836337B1 (en) * 2003-09-12 2010-11-16 Wavelink Corporation Method and system for restoration of a mobile device to its state prior to loss of standard memory
US7467267B1 (en) * 2004-07-23 2008-12-16 Sprint Communications Company L.P. Method and system for backing up or restoring data in remote devices over a communications network
US20060031476A1 (en) * 2004-08-05 2006-02-09 Mathes Marvin L Apparatus and method for remotely monitoring a computer network

Patent Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6023620A (en) * 1997-02-26 2000-02-08 Telefonaktiebolaget Lm Ecrisson Method for downloading control software to a cellular telephone
US6119212A (en) * 1997-04-23 2000-09-12 Advanced Micro Devices, Inc. Root size decrease on a UNIX based computer system
US20020104080A1 (en) * 2000-03-29 2002-08-01 Virtual Access Networks, Inc. Server based extraction, transfer, storage and processing of remote settings, files and data
US20020023258A1 (en) * 2000-06-27 2002-02-21 Elwahab Amgad Mazen System and method for managing telecommunications devices
US20040068721A1 (en) * 2000-11-17 2004-04-08 O'neill Patrick Network for updating firmware and / or software in wireless communication devices
US6832373B2 (en) * 2000-11-17 2004-12-14 Bitfone Corporation System and method for updating and distributing information
US20020072350A1 (en) * 2000-12-08 2002-06-13 Atsushi Fukuzato Backup method of applications of portable cellular phone
US20040015940A1 (en) * 2001-05-29 2004-01-22 3Com Corporation Intelligent device upgrade engine
US7386846B2 (en) * 2001-07-26 2008-06-10 Kyocera Wireless Corp. System and method for the management of wireless communications device system software downloads in the field
US20030041133A1 (en) * 2001-07-27 2003-02-27 Hitachi, Ltd. Method for providing information apparatus together with setups transfer service
US20030037323A1 (en) * 2001-08-18 2003-02-20 Lg Electronics Inc. Method for upgrading data
US7472386B2 (en) * 2001-09-24 2008-12-30 Siemens Energy & Automation, Inc. Method for utilizing remote data access to provide engineering tool services
US20030225986A1 (en) * 2002-04-23 2003-12-04 Casio Computer Co., Ltd. Program install method, file renewal method, program and computer system
US20030204578A1 (en) * 2002-04-26 2003-10-30 Michael Yip Method and apparatus for restoring the configuration of a network device
US20030204711A1 (en) * 2002-04-29 2003-10-30 Guess Alan J. Method and system for restoring custom user configuration settings across a host application download
US20030225985A1 (en) * 2002-05-31 2003-12-04 William J. Ruenle Vp & Cfo Interleaver for iterative decoder
US20050289533A1 (en) * 2002-10-09 2005-12-29 Xpoint Technologies, Inc. Method and system for updating a software image
US20040093597A1 (en) * 2002-11-05 2004-05-13 Rao Bindu Rama Firmware update system for facilitating firmware update in mobile handset related applications
US6836657B2 (en) * 2002-11-12 2004-12-28 Innopath Software, Inc. Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade
US20040261072A1 (en) * 2003-06-20 2004-12-23 Samsung Electronics Co., Ltd. Apparatus and method for performing an over-the-air software update in a dual processor mobile station
US7221912B2 (en) * 2003-08-29 2007-05-22 Lucent Technologies Inc. Telecommunications management interface system
US20050144616A1 (en) * 2003-10-27 2005-06-30 Hammond Brad T. System and method for updating a software program
US20050132351A1 (en) * 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Probst et al. Flexible Configuration and Concurrent Upgrade for the IBM eServer z900. IBM Journal of Research and Development, July 2002, pages 551-558, Retrieved on [2013-14-03] Retrieved from the Internet: URL *
Srivastava, Sameer. Redundancy Management for Network Devices. The 9th Asia-Pacific Conference on Communications, September 2003, pages 1157-1162, Retrieved on [2013-14-03] Retrieved from the Internet: URL *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080134167A1 (en) * 2005-01-17 2008-06-05 Jong Jin Chae Method for Representing Description Language and Data Structure to Update Pump Tool, Ipmp Tool Updating Method and Client Apparatus Using the Same
US20110167418A1 (en) * 2005-05-27 2011-07-07 Niraj Gopal Method for supporting new network element software versions in an element management system without upgrading
US8887147B2 (en) * 2005-05-27 2014-11-11 Cisco Technology, Inc. Method for supporting new network element software versions in an element management system without upgrading
US20080086229A1 (en) * 2006-08-24 2008-04-10 Hitachi Kokusai Electric Inc. Substrate processing system
US8560107B2 (en) * 2006-08-24 2013-10-15 Hitachi Kokusai Electric Inc. Substrate processing system
US20110055823A1 (en) * 2009-08-27 2011-03-03 Microsoft Corporation Logical Migration Of Applications And Data
US8918779B2 (en) * 2009-08-27 2014-12-23 Microsoft Corporation Logical migration of applications and data
US10209975B2 (en) 2009-08-27 2019-02-19 Microsoft Technology Licensing, Llc Logical migration of applications and data
US20120016972A1 (en) * 2010-07-13 2012-01-19 Fujitsu Telecom Networks Limited Snmp agent device and configuration undo method
CN111865670A (en) * 2020-07-03 2020-10-30 宏图智能物流股份有限公司 Warehouse network rapid recovery method and warehouse network rapid recovery server
US20230333936A1 (en) * 2022-04-15 2023-10-19 Dell Products L.P. Smart cataloging of excluded data
US11947424B2 (en) * 2022-04-15 2024-04-02 Dell Products L.P. Smart cataloging of excluded data

Also Published As

Publication number Publication date
WO2005076525A8 (en) 2005-10-13
CN1652512A (en) 2005-08-10
US10007502B2 (en) 2018-06-26
EP1713198A1 (en) 2006-10-18
ES2310809T5 (en) 2012-12-05
WO2005076525A1 (en) 2005-08-18
EP1713198A4 (en) 2007-04-11
ATE403996T1 (en) 2008-08-15
US8495616B2 (en) 2013-07-23
DE602005008712D1 (en) 2008-09-18
CN100372294C (en) 2008-02-27
ES2310809T3 (en) 2009-01-16
EP1713198B2 (en) 2012-07-25
US20130239103A1 (en) 2013-09-12
EP1713198B1 (en) 2008-08-06

Similar Documents

Publication Publication Date Title
EP1713198B1 (en) A method for upgrading software of communication equipment
CN107608706B (en) Automatic hot updating method for application program based on functional module
JP4268969B2 (en) Media message upload control method via wireless communication network
US20050055689A1 (en) Software management for software defined radio in a distributed network
CN100525206C (en) Realizing method and system for automatic restoring equipment fault
US20080183862A1 (en) Network communication management system including network with improved safety and reliability
US7290164B1 (en) Method of reverting to a recovery configuration in response to device faults
EP3002930A1 (en) Method, system, terminal and device management server for installing software components
WO2004049104A2 (en) Software self-repair toolkit for electronic devices
EP2628273B1 (en) Method for operating a remote controlled network element
EP1259028A2 (en) A method of managing a network device, a management system, and a network device
CN105407475A (en) Processing method for use of configuration file and eUICC (Embedded Universal Integrated Circuit Card)
EP2104274B1 (en) Method, system, dm client and dm server for installing software component
CN112399455A (en) Lora gateway control method and Lora communication system
JP7219568B2 (en) Base station, control method and program
JP2950262B2 (en) How to set up a multi-integrated agent system
EP1371172B1 (en) Method for upgrading network server programming conditions, associated system and software product
CN110532012B (en) Distributed system software upgrading method and device
WO2005064866A1 (en) Method of automatically transferring router functionality
JP4191155B2 (en) Supervisory control program, supervisory control device, supervisory control method
CN110913416A (en) Terminal, networking method thereof and computer-readable storage medium
EP1805935B1 (en) Persistent confirmed configuration method
JP2818575B2 (en) Wireless base station remote reset system
JP4493461B2 (en) Backup device, backup method and broadcasting system
CN115309430A (en) eSIM card operating system upgrading method, apparatus, eSIM card, server and storage medium

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO. LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FAN, JINFEI;SHE, JIANGFA;LUO, BING;AND OTHERS;REEL/FRAME:019379/0937

Effective date: 20061228

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8