WO2014067324A1 - 一种补丁软件升级方法及系统 - Google Patents

一种补丁软件升级方法及系统 Download PDF

Info

Publication number
WO2014067324A1
WO2014067324A1 PCT/CN2013/082103 CN2013082103W WO2014067324A1 WO 2014067324 A1 WO2014067324 A1 WO 2014067324A1 CN 2013082103 W CN2013082103 W CN 2013082103W WO 2014067324 A1 WO2014067324 A1 WO 2014067324A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
version
software
management
upgraded
Prior art date
Application number
PCT/CN2013/082103
Other languages
English (en)
French (fr)
Inventor
赵真富
Original Assignee
中兴通讯股份有限公司
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
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP13850466.7A priority Critical patent/EP2916487B1/en
Priority to US14/439,274 priority patent/US20150293759A1/en
Publication of WO2014067324A1 publication Critical patent/WO2014067324A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present invention relates to the field of communications, and in particular, to a patch software upgrade method and system.
  • BACKGROUND OF THE INVENTION As the demand for accessing a network to obtain information anytime and anywhere is expanding, various wired or wireless terminals are constantly emerging and connected to the network.
  • network devices used to carry user network services in the network become more and more important.
  • Network devices are abnormal, which affects the user access experience, resulting in user loss, and affects the operation of the enterprise's e-commerce network. , bringing significant economic losses.
  • various network device software upgrades have to be faced due to possible software failure or new functional features.
  • the technical problem to be solved by the embodiments of the present invention is to provide a patch software upgrade method and system for a communication device in which a forwarding plane software is separated from a control plane and a management plane software, and performs a control plane and a management plane software of the communication device.
  • a forwarding plane software is separated from a control plane and a management plane software, and performs a control plane and a management plane software of the communication device.
  • the patch software upgrade method is used for the communication device in which the forwarding plane software is separated from the control plane and the management plane software, and the control plane and the management plane software are upgraded by a single process internal change.
  • the method includes: Step 1: The version management process triggers the old version process to be upgraded to be logged off, and keeps the data and data status of the upstream process and the downstream process of the old version process unchanged; Step 2: After the old version of the process to be upgraded is successfully logged off, the version management process triggers the start of the new version process. Step 3: The upstream process and the downstream process assist the new version process to restore data and data status.
  • the version management process in the first step triggers the logout of the old version of the process to be upgraded, which includes: The version management process simultaneously triggers the old version of the process to be upgraded in the active state and the old version of the standby to be upgraded in the standby state.
  • the step 3 includes: the new version process is re-established with the upstream process and the downstream process respectively; and the upstream process outputs the data outputted to the old version process to the new version process, or The downstream process outputs the data outputted by the old version process to the new version process, so that the data and data state of the new version process are restored.
  • the method further includes: Step 4: The version management process triggers updating the status of the data and data of the process related to the forwarding plane software.
  • the embodiment of the present invention further provides a method for upgrading a patch software.
  • the process set is upgraded due to the change of the interface between the process centralized processes.
  • the method includes: Step 1: The version management process triggers each process in the old version process set to be upgraded to be logged off, and keeps the data and data status of the upstream process and the downstream process of the old version process set unchanged.
  • Step 2 After all processes in the old version of the process set to be upgraded are successfully logged out, the version management process triggers each process in the new version process set to start; Step 3, the upstream process and the downstream process assist the new version process set Restore data and data status.
  • the embodiment of the present invention further provides a patch software upgrade system, where the forwarding device software is separated from the control plane and the management plane software, and the control plane and the management plane software are upgraded by a single process internal change,
  • the system includes: a version management module, configured to trigger an old version of the process to be logged off, and keep the data and data status of the upstream process and the downstream process of the old version process unchanged; Afterwards, the new version process is triggered to start; the data recovery module is located inside each process, and the upstream process and the downstream process assist the new version process to recover the data and data state based on the data recovery module.
  • the version management module is specifically configured to simultaneously trigger the old version of the process to be upgraded in the active state.
  • the old version of the process to be upgraded in the standby state is logged off.
  • the data recovery module specifically includes: a chain building module, wherein the upstream process and the downstream process are re-established with the new version process by the link building module; and the data transmission module, the upstream process is transmitted through the data transmission module
  • the new version process outputs the data outputted to the old version process before, or the downstream process outputs the data to the new version process before the old version process outputs the data to the new version process, so that the data and data state of the new version process are restored.
  • the version management module is further configured to: after the upgrade of the control plane and the management plane software related process is completed, trigger the update of the data and data status of the forwarding plane software related process.
  • the embodiment of the present invention further provides a patch software upgrade system.
  • the process set is upgraded due to the change of the interface between the process centralized processes.
  • the system includes: a version management module, configured to trigger each process in the old version process set to be upgraded to log off, and keep the data and data status of the upstream process and the downstream process of the old version process set unchanged. After all the processes in the old version of the process set to be upgraded are successfully logged off, each process in the new version process set is triggered to be started; the data recovery module is located inside each process, and the upstream process and the downstream process are assisted by the data recovery module.
  • the patch software upgrade method and system according to the embodiment of the present invention can perform a process-level control plane on a communication device in which the forwarding plane software is separated from the control plane and the management plane software. And upgrade the management software to avoid unnecessary service interruption caused by software upgrades, improve service reliability and availability, avoid major economic losses caused by business interruption, and improve user service experience.
  • the process with the changed interface is upgraded as a software upgrade unit, so that the interface change is used as the internal change of the upgrade process set, and the upgrade process of the upgrade process set is to be performed.
  • FIG. 1 is a flowchart of a method for upgrading a patch software according to a first embodiment of the present invention
  • FIG. 2 is a flowchart of a method for upgrading a patch software according to a second embodiment of the present invention
  • FIG. 3 is a third and fourth embodiment of the present invention
  • FIG. 4 is an interaction sequence diagram of a process set software upgrade in a fifth embodiment of the present invention
  • FIG. 5 is a schematic diagram of an access gateway control plane and a management plane software upgrade in an application example of the present invention
  • Figure 6 is a schematic diagram of the deactivation of the old version of the access gateway in the application example of the present invention
  • Figure 7 is a schematic diagram of the startup of the new version of the access gateway in the application example of the present invention
  • Figure 8 is an application example of the present invention
  • the upstream process of the access gateway inputs the data schema to the new version process.
  • FIG. 9 is a schematic diagram of the process of the new version of the access gateway entering the normal working state in the application example of the present invention.
  • a first embodiment of the present invention is a patch software upgrade method, in which a communication device in which a forwarding plane software is separated from a control plane and a management plane software, and a control plane and a management plane software are internally changed by a single process.
  • the method includes the following specific steps: Step S101: The version management process triggers the old version process to be upgraded to log out to exit the operation, and keeps the upstream process and the downstream process of the old version process unchanged in data and data status.
  • the system management process may send an instruction to the upstream process and the downstream process of the old version process to notify the upstream process and the downstream process of the old version process that the data and data status remain unchanged, or may not perform any of the upstream process and the downstream process. Operate to keep the data and data state unchanged.
  • the version management process triggers the process of the old version to be upgraded to be deleted in step S101, specifically: The management process simultaneously triggers the old version of the process to be upgraded in the active state and the old version of the standby to be upgraded in the standby state.
  • Step S102 After the old version process to be upgraded is successfully logged off, the version management process triggers the new version process to start. Before the upgrade, you can package the new version process corresponding to the old version of the process to be upgraded into the software patch package. During the upgrade, the version management process directly replaces the old version process to be upgraded with the new version process in the specified software patch package, and starts the new process. Version process.
  • Step S103 the upstream process and the downstream process assist the new version process to perform data and data state recovery. Specifically, step S103 includes the following process:
  • A1 The new version process is re-established with the upstream process and the downstream process, respectively, and sends data and data state recovery requests to the upstream process and the downstream process.
  • the upstream process After the upstream process and the downstream process receive the data and data state recovery request, the upstream process outputs the data that is output to the old version process to the new version process, or the downstream process outputs the data to the new version process.
  • the old version process outputs its own data, so that the data and data status of the new version process can be restored.
  • the method for upgrading the patch software in the embodiment further includes: Step S104: The version management process triggers updating the status of data and data of the process related to the forwarding plane software. Because the process of the communication device control plane has been upgraded, in order to further reduce the impact on the forwarding service, it is necessary to update the data and data status of the forwarding-side software-related processes after the data and data state recovery of the new version process is completed.
  • a patch software upgrade method for a communication device in which a forwarding plane software is separated from a control plane and a management plane software, for a control plane and a management plane software, between processes in a centralized process
  • the method includes: Step S201: The version management process triggers each process in the old version process set to be upgraded to log out to exit the operation, and maintains the upstream process of the old version process set. Keep the data and data status unchanged with the downstream process.
  • the system management process may send an instruction to the upstream process and the downstream process of the old version process set to notify the upstream process and the downstream process of the old version process set that the data and data status remain unchanged, or may not be the upstream process and the downstream process. Do anything to keep the data and data state intact.
  • the version management process triggers each process in the old version of the process set to be upgraded to be deactivated in step S201, specifically including : When each process is logged off, the old version of the process to be upgraded and the standby state of the standby state that is triggered in the active state are simultaneously logged off.
  • Step S202 After all processes in the old version process set to be upgraded are successfully logged off, the version management process triggers each process in the new version process set to start. Before upgrading, you can package the new version of the process set corresponding to the old version of the process set to be upgraded into the software patch package. When the upgrade, the version management process directly replaces the old version of the process set to be upgraded with the new version of the process set in the specified software patch package. , and start the process in the new version of the process set to start.
  • Step S203 the upstream process and the downstream process assist the new version process set to perform data and data state recovery. Specifically, step S203 includes the following process:
  • B1 The new version process set is re-established with the upstream process and the downstream process respectively, and sends data and data state recovery requests to the upstream process and the downstream process.
  • the upstream process After the upstream process and the downstream process receive the data and data state recovery request, the upstream process outputs the data previously output to the old version process set to the new version process set, or the downstream process goes to the new version process. Before the output is output, the old version of the process set outputs the data to itself, so that the data and data state of the new version of the process set can be restored.
  • the patch software upgrade method in this embodiment further includes: In step S204, the version management process triggers updating the status of the data and data of the forwarding plane software related process.
  • Update that is, the routing table entry for the refresh forwarding plane.
  • a third embodiment of the present invention is a patch software upgrade system, in which a communication device in which a forwarding plane software is separated from a control plane and a management plane software, and a control plane and a management plane software are internally changed by a single process.
  • the system includes:
  • the version management module 10 is configured to trigger the old version process to be upgraded to log out to exit the operation, and keep the data and data status of the upstream process and the downstream process of the old version process unchanged; After success, the new version process is triggered to start.
  • the version management module 10 when any software running on the control plane and the management plane of the communication device has a process running in the active state and the standby state, the version management module 10 is specifically configured to: simultaneously trigger the old version of the process to be upgraded in the active state. The old version of the process to be upgraded in the standby state is logged off.
  • the version management module 10 is further configured to: after the related process of the control plane and the management plane software is upgraded, trigger the update of the data and data status of the process related to the forwarding plane software.
  • Update that is, the routing table entry for the refresh forwarding plane.
  • the data recovery module 20 is located inside each process, and the upstream process and the downstream process assist the new version process to recover the data and data state based on the data recovery module.
  • the data recovery module 20 includes: a chain building module 21, wherein the upstream process and the downstream process are re-established with the new version process by the link building module; and the data transmission module 22, the upstream process passes the data transmission module to The new version process outputs the data outputted to the old version process before, or the downstream process outputs the data to the new version process before the old version process outputs the data to the new version process, so that the data and data state of the new version process are restored.
  • a chain building module 21 wherein the upstream process and the downstream process are re-established with the new version process by the link building module
  • the data transmission module 22 the upstream process passes the data transmission module to
  • the new version process outputs the data outputted to the old version process before, or the downstream process outputs the data to the new version process before the old version process outputs the data to the new version process, so that the data and data state of the new version process are restored.
  • an embodiment of the present invention further provides a patch software upgrade system, where the forwarding plane software is separated from the control plane and the management plane software, and the control plane and the management plane software are In the case of a process set upgrade caused by a change in the interface between processes in the process set, the system includes:
  • the version management module 10 is configured to trigger each process in the old version process set to be upgraded to log out to exit the operation, and keep the data and data status of the upstream process and the downstream process of the old version process set unchanged; After all the processes in the upgraded old version of the process are successfully logged out, each process in the new version of the process set is triggered to start.
  • the version management module 10 is specifically configured to: when each process is logged off, the primary use is triggered at the same time. The old version of the process to be upgraded and the old version of the standby state to be upgraded are logged out.
  • the version management module 10 is further configured to: after the upgrade of the related process set of the control plane and the management plane software, trigger the update of the data and data status of the forwarding plane software related process. Because the communication device control plane and management plane software have been upgraded before, in order to further reduce the impact on the forwarding service, it is necessary to perform the data and data status of the forwarding-side software-related processes after the data and data state recovery of the new version process is completed. Update, that is, the routing table entry for the refresh forwarding plane.
  • the data recovery module 20 is located inside each process, and the upstream process and the downstream process assist the new version process set to recover the data and data state based on the data recovery module.
  • the data recovery module 20 includes: a chain building module 21, wherein the upstream process and the downstream process are re-established with the new version process set by the link building module; the data transmission module 22, the upstream process passes the data transmission module Output the data output to the old version of the process set to the new version of the process set, or the downstream process outputs the data of the old version of the process set to the new version of the process set through the data transfer module to the new version of the process set, so that the data and data of the new version of the process set The state is restored.
  • version management process is responsible for the version upgrade and failure rollback of the management process.
  • the upstream process, the process set to be upgraded, and the downstream process are processes that implement specific business functions, such as FIB (for forwarding information base?).
  • RIP Raster
  • Routing Information Protocol Routing Information Protocol
  • BGP Border Gateway Protocol
  • the upstream process outputs data to the process set to be upgraded, and the process set to be upgraded outputs data to the downstream process.
  • the system management process is responsible for global state management of all service processes. The system management process needs to be reported when each process starts and logs out. The system management process maintains the state information of each process. When a process is started or logged off, other application processes are notified for processing.
  • Figure 4 is an interaction sequence diagram of the process set software upgrade.
  • the software upgrade process includes the following steps:
  • S1 The version management process receives the process set upgrade command, upgrades the process set software that has the interface change between processes, and upgrades the executable file of the process set related to the change interface as the same patch software.
  • S2 The version management process initiates a process logout instruction to each process in the old version process set to be upgraded, and triggers the process in the old version process set to perform logout processing.
  • any software running on the control plane and the management plane of the communication device has both active and standby processes, the processes to be upgraded in the active and standby states need to be logged off at the same time.
  • S3 The system management process is notified when the process in the old version of the process to be upgraded logs out.
  • S4 The system management process sends a logout event notification to the upstream process and the downstream process to notify the upstream and downstream processes to keep the data and data status unchanged, so as to avoid service interruption.
  • the version management process issues a new version of the process set command to start the new version of the process set.
  • the software to be upgraded is a process set whose inter-process interface changes
  • the version management process needs to confirm that all the processes in the process group to be upgraded are successfully logged out before the new version of the process set can be started. If there is a specific process logout timeout or failure during the logout process, the version management process feedback upgrade fails.
  • the version management process needs to wait for the active and standby states to be successfully logged off. After the new version of the process can be started.
  • S6 The new version of the process set is registered with the system management process when it starts.
  • S7 The system management process sends a registration notification to the upstream process and the downstream process to notify the upstream and downstream processes to re-establish the chain with the upgraded new version process set.
  • S8 After the upstream process is successfully established, the data outputted to the old version process set is re-outputted to the upgraded process, and the upgraded process set data and data state recovery are assisted.
  • the downstream process can output the data to the old process set before exporting to the upgraded process as needed, and assist the upgraded new version process set to restore the data and data state.
  • the upgraded new version process set After the upgraded new version process set successfully restores its own data and data status, it enters a normal working state, and outputs the restored data to the downstream process; optionally, the device that separates the control plane and the forwarding plane.
  • the upgraded process is a control plane process, and the data to be restored affects the function of the forwarding plane, the entry of the forwarding plane is triggered after the data recovery is completed, so as to reduce the impact on the forwarding service.
  • the version management process confirms that all processes in the new version process set are successfully started and restored before the upgrade is successful. If there is a specific process startup timeout or failure during the startup process, the version management process feedback upgrade fails.
  • Access gateway control plane and management plane software upgrade scenario Figure 5 to Figure 9 show the upgrade scenario of the access gateway process-level control plane and management plane software.
  • Figure 5 shows the state before the software upgrade.
  • the access gateway needs to be implemented.
  • the upgrade process of the support process and the FIB process involves the following associated processes in the application service process: the version management process, the system management process, the BGP process, the RIP process, the OSPF process, the support process, and the FIB process.
  • Support processes and FIB processes are process sets that need to be upgraded.
  • the supporting process receives the routes learned by each routing protocol, and performs the calculation of the optimal route, and then generates the best FIB and outputs it to the FIB process.
  • the BGP process, the RIP process, and the OSPF process are the processes to be upgraded (the supporting process and the FIB process).
  • the upstream process which implements the relevant routing protocol negotiation, and outputs the negotiated route to the supporting process.
  • the supporting process selects the best route and outputs it to the FIB process.
  • the FIB process acts as the downstream process supporting the process and outputs the output to the supporting process. Maintain and manage your own FIB entries.
  • the steps for implementing the patch software upgrade method for multi-process operating systems on the network are as follows:
  • C1 The version management process receives the process set upgrade command, and the process set of the inter-process interface change that needs to be upgraded at the same time, the support process of the support process and the FIB process are upgraded simultaneously as the same patch software.
  • C2 As shown in Figure 6, the version management process initiates the process logout command to the support process and the FIB process in the old process set of the old version to be upgraded, and triggers the old version support process and the FIB process to log off.
  • the system management process detects that the old version of the support process and the FIB process are to be revoked, and notifies the upstream process of a BGP process, a RIP process, and an OSPF process, so that the upstream process maintains the data and data status unchanged to avoid service interruption.
  • the system management process senses that the new version of the support process and the FIB process are started, and notifies the upstream process of a BGP process, a RIP process, and an OSPF process, so that the upstream process and the upgraded support process and re-chaining;
  • C6 As shown in Figure 8, after the upstream process and the new version support process are successfully established, the data output to the old version process set is re-outputted to the upgraded new version support process, and the data and data of the upgraded support process are assisted. State recovery. As shown in Figure 9, after the upgraded support process successfully restores its own data and data status, it enters the normal working state and outputs the restored data to the FIB process.
  • C7 After the version management process confirms that both the support process and the FIB process in the new version process set are started and restored successfully, the upgrade is confirmed to be successful.
  • the patch software is mainly used to fix local faults or locally added small features in the version.
  • the embodiment of the invention discloses a lightweight patch software service online upgrade scheme.
  • the patch software changes can be basically divided into two categories, one is an internal change of a specific process; and the other is a specific process.
  • Interface change For the first type of change, if the change is only an internal change of a specific process, the software upgrade can only upgrade the process involved in the change separately, which will greatly reduce the impact of the software upgrade on the running business; The software upgrade of the interface change between processes. Because of the interface change, the process with the interface change can be upgraded as a software upgrade unit. In this way, the interface change is used as an internal change to the upgrade process set.
  • the external process of the process set to be upgraded is not aware of, so as to simplify the software upgrade process of the process set.
  • the main consideration is based on the upstream and downstream processes of the software to be upgraded to assist in the completion.
  • each process is not isolated.
  • Each process receives input from the upstream process during the running process, and then processes and generates its own data and data status.
  • the downstream process produces an output. It can be seen that the data and data status of each process are generated according to the input data of the upstream process. Therefore, if a specific process needs to be upgraded, it can be upgraded through the upstream process. After the process re-enters the data to trigger the upgraded process to recreate and generate its own data and data state.
  • the patch software upgrade method and system according to the embodiment of the present invention can perform process level control plane and management plane software upgrade on the communication device with control plane and management plane software and forwarding plane software separated to avoid unnecessary software upgrade.
  • the business interruption improve the reliability and availability of the business, avoid major economic losses caused by business interruption, and enhance the user's business experience.
  • a patch software upgrade method and system provided by an embodiment of the present invention have the following beneficial effects: a process level control plane can be performed on a communication device in which a forwarding plane software is separated from a control plane and a management plane software. Upgrade the management software to avoid unnecessary service interruption caused by software upgrades, improve service reliability and availability, avoid major economic losses caused by business interruption, and improve user service experience.
  • the process with the changed interface is upgraded as a software upgrade unit, so that the interface change is used as the internal change of the upgrade process set, and the upgrade process of the upgrade process set is to be performed. Similar to the upgrade process caused by internal changes in a single process, the software upgrade process of the process set is simplified.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明公开了一种补丁软件升级方法及系统，对于转发面软件与控制面和管理面软件分离的通信设备，该方法包括：版本管理进程触发待升级的老版本进程注销，并保持所述老版本进程的上游进程和下游进程的数据及数据状态不变；在待升级的老版本进程注销成功后，版本管理进程触发新版本进程启动；所述上游进程和下游进程协助所述新版本进程进行数据及数据状态的恢复。该系统包括：版本管理模块和数据恢复模块。本发明可以对通信设备进行进程级的控制面软件升级，以避免软件升级带来不必要的业务中断，提高业务的可靠性和可用性，避免业务中断带来重大的经济损失，提升用户业务体验。

Description

一种补丁软件升级方法及系统 技术领域 本发明涉及通信术领域， 尤其涉及一种补丁软件升级方法及系统。 背景技术 随着人们对随时随地接入网络以获取信息的需求不断扩大， 各种有线或无线终端 不断涌现并接入到网络中。 为了提升用户体验， 网络中用于承载用户网络业务的网络 设备就显得越来越重要， 网络设备出现异常， 轻则影响用户接入体验， 导致用户流失， 重则影响企业的电子商务网络的运行， 带来重大的经济损失。 在网络设备的运行过程中， 由于可能存在软件故障或者新增功能特性， 不得不面 临各种各样的网络设备软件升级。为了避免网络设备在软件升级过程中引起业务中断， 需要考虑在软件升级过程中， 怎样减少业务中断的影响，提高业务的可靠性和可用性， 提升用户业务体验。 业务在线软件升级要解决两个问题， 一、 软件的升级； 二、 业务恢复。 目前， 业 界对通信设备的业务在线软件升级中， 主要方案是基于主备方式的升级。 这种软件升 级方式是基于有主备硬件支持情况的软件升级， 升级的单位是整个软件版本， 在升级 过程中需要执行软件的主备倒换。 对没有主备物理硬件支持的情况下， 这种软件升级 方法不可行。 而即使有主备物理硬件支持， 如果升级的影响面较小， 采用这种升级方 式， 升级持续时间也比较长， 代价较大。 发明内容 本发明实施例要解决的技术问题是， 针对转发面软件与控制面和管理面软件分离 的通信设备， 提供一种补丁软件升级方法及系统， 对通信设备的控制面和管理面软件 进行进程级的升级， 以避免软件升级带来不必要的业务中断， 提升用户业务体验。 本发明实施例采用的技术方案是， 所述补丁软件升级方法， 对于转发面软件与控 制面和管理面软件分离的通信设备， 对于控制面和管理面软件， 在由单进程内部变更 引起进程升级的情况下， 所述方法包括： 步骤一， 版本管理进程触发待升级的老版本进程注销， 并保持所述老版本进程的 上游进程和下游进程的数据及数据状态不变； 步骤二，在待升级的老版本进程注销成功后，版本管理进程触发新版本进程启动； 步骤三， 所述上游进程和下游进程协助所述新版本进程进行数据及数据状态的恢 复。 优选的， 当通信设备上的控制面和管理面的任一软件同时存在主用和备用状态运 行的进程时，在步骤一中所述版本管理进程触发待升级的老版本进程注销， 具体包括: 版本管理进程同时触发主用状态的待升级老版本进程和备用状态的待升级老版本 进程注销。 优选的， 所述步骤三， 具体包括： 所述新版本进程分别与所述上游进程和下游进程重新建链； 通过所述上游进程向新版本进程输出之前向老版本进程输出的数据， 或者， 所述 下游进程向新版本进程输出之前老版本进程输出给自己的数据， 使新版本进程的数据 及数据状态得以恢复。 优选的， 所述方法还包括： 步骤四，版本管理进程触发对转发面软件相关进程的数据及数据的状态进行更新。
本发明实施例还提供一种补丁软件升级方法， 对于转发面软件与控制面和管理面 软件分离的通信设备， 对于控制面和管理面软件， 在由进程集中进程间接口发生变更 引起进程集升级的情况下， 所述方法包括： 步骤一， 版本管理进程触发待升级的老版本进程集中的每个进程注销， 并保持所 述老版本进程集的上游进程和下游进程的数据及数据状态不变； 步骤二， 在待升级的老版本进程集中的所有进程注销成功后， 版本管理进程触发 新版本进程集中的每个进程启动； 步骤三， 所述上游进程和下游进程协助所述新版本进程集进行数据及数据状态的 恢复。 本发明实施例还提供一种补丁软件升级系统， 对于转发面软件与控制面和管理面 软件分离的通信设备， 对于控制面和管理面软件， 在由单进程内部变更引起进程升级 的情况下， 所述系统包括： 版本管理模块， 设置为触发待升级的老版本进程注销， 并保持所述老版本进程的 上游进程和下游进程保持数据及数据状态不变； 在待升级的老版本进程注销成功后， 触发新版本进程启动； 数据恢复模块， 位于各进程内部， 所述上游进程和下游进程基于数据恢复模块协 助所述新版本进程进行数据及数据状态的恢复。 优选的， 当通信设备上的控制面和管理面的任一软件同时存在主用和备用状态运 行的进程时， 所述版本管理模块， 具体设置为- 同时触发主用状态的待升级老版本进程和备用状态的待升级老版本进程注销。 优选的， 所述数据恢复模块， 具体包括- 建链模块， 所述上游进程和下游进程通过建链模块与所述新版本进程重新建链； 数据传输模块， 所述上游进程通过数据传输模块向新版本进程输出之前向老版本 进程输出的数据， 或者， 下游进程通过数据传输模块向新版本进程输出之前老版本进 程输出给自己的数据， 使新版本进程的数据及数据状态得以恢复。 优选的， 所述版本管理模块， 还设置为在控制面和管理面软件相关进程升级完成 后， 触发对转发面软件相关进程的数据及数据的状态进行更新。
本发明实施例还提供一种补丁软件升级系统， 对于转发面软件与控制面和管理面 软件分离的通信设备， 对于控制面和管理面软件， 在由进程集中进程间接口发生变更 引起进程集升级的情况下， 所述系统包括： 版本管理模块， 设置为触发待升级的老版本进程集中的每个进程注销， 并保持所 述老版本进程集的上游进程和下游进程的数据及数据状态不变； 在待升级的老版本进 程集中的所有进程注销成功后， 触发新版本进程集中的每个进程启动； 数据恢复模块， 位于各进程内部， 所述上游进程和下游进程基于数据恢复模块协 助所述新版本进程集进行数据及数据状态的恢复。 采用上述技术方案， 本发明实施例至少具有下列优点: 本发明实施例所述补丁软件升级方法及系统， 可以对转发面软件与控制面和管理 面软件分离的通信设备， 进行进程级的控制面和管理面软件升级， 以避免软件升级带 来不必要的业务中断， 提高业务的可靠性和可用性， 避免业务中断带来重大的经济损 失， 提升用户业务体验。 对支持多进程的通信设备， 当特定进程间的接口变更时， 将 接口存在变更的进程作为一个软件升级单位进行升级， 这样将接口变更作为升级进程 集的内部变更， 待升级进程集的升级过程与单个进程内部变更引起的升级过程类似， 简化了进程集的软件升级过程。 附图说明 图 1 为本发明第一实施例中的补丁软件升级方法流程图； 图 2 为本发明第二实施例中的补丁软件升级方法流程图； 图 3 为本发明第三、 四实施例中的补丁软件升级系统组成示意图； 图 4 为本发明第五实施例中的进程集软件升级的交互序列图； 图 5 为本发明应用实例中的接入网关控制面和管理面软件升级前的状态示意图； 图 6 为本发明应用实例中的接入网关的老版本进程集注销示意图； 图 7 为本发明应用实例中的接入网关的新版本进程集启动示意图； 图 8 为本发明应用实例中的接入网关的上游进程向新版本进程输入数据示意图； 图 9 为本发明应用实例中的接入网关的新版本进程进入正常工作状态示意图。 具体实施方式 为更进一步阐述本发明为达成预定目的所采取的技术手段及功效， 以下结合附图 及较佳实施例， 对本发明进行详细说明如后。 本发明第一实施例， 如图 1所示， 一种补丁软件升级方法， 对于转发面软件与控 制面和管理面软件分离的通信设备， 对于控制面和管理面软件， 在由单进程内部变更 引起进程升级的情况下， 该方法包括以下具体步骤： 步骤 S101， 版本管理进程触发待升级的老版本进程注销以退出运行， 并保持所述 老版本进程的上游进程和下游进程保持数据及数据状态不变。 具体的， 可以通过系统管理进程向老版本进程的上游进程和下游进程发送指令告 知老版本进程的上游进程和下游进程保持数据及数据状态不变， 也可以不对所述上游 进程和下游进程进行任何操作而使其自身保持数据及数据状态不变。 可选的， 当通信设备上的控制面和管理面的任一软件同时存在主用和备用状态运 行的进程时， 在步骤 S101中版本管理进程触发待升级的老版本进程注销， 具体包括： 版本管理进程同时触发主用状态的待升级老版本进程和备用状态的待升级老版本 进程注销。 步骤 S102， 在待升级的老版本进程注销成功后， 版本管理进程触发新版本进程启 动。 升级前可以将待升级的老版本进程对应的新版本进程打包到软件补丁包中， 升级 时版本管理进程直接用指定的软件补丁包中的新版本进程替换待升级的老版本进程， 并启动新版本进程。 步骤 S103，所述上游进程和下游进程协助所述新版本进程进行数据及数据状态的 恢复。 具体的， 步骤 S103包括以下过程：
A1 : 所述新版本进程分别与所述上游进程和下游进程重新建链， 并向所述上游进 程和下游进程发送数据及数据状态恢复请求。
A2: 所述上游进程和下游进程收到数据和数据状态恢复请求后， 通过所述上游进 程向新版本进程输出之前向老版本进程输出的数据， 或者， 所述下游进程向新版本进 程输出之前老版本进程输出给自己的数据，使新版本进程的数据及数据状态得以恢复。 可选的， 本实施例所述补丁软件升级方法还包括： 步骤 S104，版本管理进程触发对转发面软件相关进程的数据及数据的状态进行更 新。 因为之前针对通信设备控制面的进程做了升级， 为了进一步减少对转发业务的影 响， 需要在新版本进程的数据及数据状态恢复完成后对转发面软件相关进程的数据及 数据的状态进行更新， 即对刷新转发面的路由表项。 本发明第二实施例， 如图 2所示， 一种补丁软件升级方法， 对于转发面软件与控 制面和管理面软件分离的通信设备， 对于控制面和管理面软件， 在由进程集中进程间 接口发生变更引起进程集升级的情况下， 所述方法包括： 步骤 S201，版本管理进程触发待升级的老版本进程集中的每个进程注销以退出运 行， 并保持所述老版本进程集的上游进程和下游进程保持数据及数据状态不变。 具体的， 可以通过系统管理进程向老版本进程集的上游进程和下游进程发送指令 告知老版本进程集的上游进程和下游进程保持数据及数据状态不变， 也可以不对所述 上游进程和下游进程进行任何操作而使其自身保持数据及数据状态不变。 可选的， 当通信设备上的控制面和管理面软件同时存在主用和备用状态运行的进 程时，在步骤 S201中版本管理进程触发待升级的老版本进程集中的每个进程注销，具 体包括： 对每个进程注销时， 同时触发主用状态的待升级老版本进程和备用状态的待升级 老版本进程注销。 步骤 S202， 在待升级的老版本进程集中的所有进程注销成功后， 版本管理进程触 发新版本进程集中的每个进程启动。 升级前可以将待升级的老版本进程集对应的新版 本进程集打包到软件补丁包中， 升级时版本管理进程直接用指定的软件补丁包中的新 版本进程集替换待升级的老版本进程集， 并启动新版本进程集中的进程启动。 步骤 S203，所述上游进程和下游进程协助所述新版本进程集进行数据及数据状态 的恢复。 具体的， 步骤 S203包括以下过程：
B1 : 所述新版本进程集分别与所述上游进程和下游进程重新建链， 并向所述上游 进程和下游进程发送数据及数据状态恢复请求。
B2: 所述上游进程和下游进程收到数据和数据状态恢复请求后， 通过所述上游进 程向新版本进程集输出之前向老版本进程集输出的数据， 或者， 所述下游进程向新版 本进程集输出之前老版本进程集输出给自己的数据， 使新版本进程集的数据及数据状 态得以恢复。 可选的， 本实施例所述补丁软件升级方法还包括: 步骤 S204，版本管理进程触发对转发面软件相关进程的数据及数据的状态进行更 新。 因为之前针对通信设备控制面的进程集做了升级， 为了进一步减少对转发业务的 影响， 需要在新版本进程集的数据及数据状态恢复完成后对转发面软件相关进程的数 据及数据的状态进行更新， 即对刷新转发面的路由表项。
本发明第三实施例， 如图 3所示， 一种补丁软件升级系统， 对于转发面软件与控 制面和管理面软件分离的通信设备， 对于控制面和管理面软件， 在由单进程内部变更 引起进程升级的情况下， 该系统包括：
1 ) 版本管理模块 10， 设置为触发待升级的老版本进程注销以退出运行， 并保持 所述老版本进程的上游进程和下游进程的数据及数据状态不变； 在待升级的老版本进 程注销成功后， 触发新版本进程启动。 可选的， 当通信设备上的控制面和管理面的任一软件同时存在主用和备用状态运 行的进程时， 版本管理模块 10， 具体设置为： 同时触发主用状态的待升级老版本进程 和备用状态的待升级老版本进程注销。 可选的， 版本管理模块 10， 还设置为在控制面和管理面软件的相关进程升级完成 后， 触发对转发面软件相关进程的数据及数据的状态进行更新。 因为之前对通信设备 控制面和管理面软件做了升级， 为了进一步减少对转发业务的影响， 需要在新版本进 程的数据及数据状态恢复完成后对转发面软件相关进程的数据及数据的状态进行更 新， 即对刷新转发面的路由表项。 2) 数据恢复模块 20， 位于各进程内部， 所述上游进程和下游进程基于数据恢复 模块协助所述新版本进程进行数据及数据状态的恢复。 具体的， 数据恢复模块 20， 包括- 建链模块 21， 所述上游进程和下游进程通过建链模块与所述新版本进程重新建 链； 数据传输模块 22， 所述上游进程通过数据传输模块向新版本进程输出之前向老版 本进程输出的数据， 或者， 下游进程通过数据传输模块向新版本进程输出之前老版本 进程输出给自己的数据， 使新版本进程的数据及数据状态得以恢复。 本发明第四实施例， 如图 3所示， 本发明实施例还提供一种补丁软件升级系统， 对于转发面软件与控制面和管理面软件分离的通信设备， 对于控制面和管理面软件， 在由进程集中进程间接口发生变更引起进程集升级的情况下， 该系统包括：
1 ) 版本管理模块 10， 设置为触发待升级的老版本进程集中的每个进程注销以退 出运行， 并保持所述老版本进程集的上游进程和下游进程的数据及数据状态不变； 在 待升级的老版本进程集中的所有进程注销成功后， 触发新版本进程集中的每个进程启 动。 可选的， 当通信设备上的控制面和管理面的任一软件同时存在主用和备用状态运 行的进程时， 版本管理模块 10， 具体设置为： 对每个进程注销时， 同时触发主用状态 的待升级老版本进程和备用状态的待升级老版本进程注销。 可选的， 版本管理模块 10， 还设置为在控制面和管理面软件的相关进程集升级完 成后， 触发对转发面软件相关进程的数据及数据的状态进行更新。 因为之前对通信设 备控制面和管理面软件做了升级， 为了进一步减少对转发业务的影响， 需要在新版本 进程的数据及数据状态恢复完成后对转发面软件相关进程的数据及数据的状态进行更 新， 即对刷新转发面的路由表项。
2 ) 数据恢复模块 20， 位于各进程内部， 所述上游进程和下游进程基于数据恢复 模块协助所述新版本进程集进行数据及数据状态的恢复。 具体的， 数据恢复模块 20， 包括- 建链模块 21， 所述上游进程和下游进程通过建链模块与所述新版本进程集重新建 链； 数据传输模块 22， 所述上游进程通过数据传输模块向新版本进程集输出之前向老 版本进程集输出的数据， 或者， 下游进程通过数据传输模块向新版本进程集输出之前 老版本进程集输出给自己的数据， 使新版本进程集的数据及数据状态得以恢复。
本发明第五实施例， 基于图 4， 详细介绍一个由进程集中进程间接口发生变更引 起控制面和管理面软件升级的执行过程。 涉及五种组件： 版本管理进程、 上游进程、 待升级进程集、 下游进程、 系统管理进程。 版本管理进程负责管理进程的版本升级、 失败回滚等； 上游进程、 待升级进程集、 下游进程是实现具体的业务功能的进程， 如 FIB ( forwarding information base? 转发信窗、库) 表项管理、 RIP (Routing information Protocol, 路由信息协议）、 BGP (Border Gateway Protocol, 边界网关协议） 等具体业 务功能。 上游进程和下游进程都与待升级进程集存在数据交互， 上游进程向待升级进 程集输出数据， 待升级进程集向下游进程输出数据； 系统管理进程负责对所有的业务 进程进行全局的状态管理， 每个进程启动和注销时都需要报告系统管理进程， 系统管 理进程维护每个进程的状态信息。 当某个进程的启动或注销时， 通知其他应用进程进 行处理； 图 4为进程集软件升级的交互序列图， 该软件升级过程包括以下步骤：
S1 : 版本管理进程接收进程集升级命令， 对存在进程间的接口变更的进程集软件 升级， 将变更接口相关的进程集的可执行文件作为相同补丁软件同时进行升级。 S2: 版本管理进程向待升级的老版本进程集中的每个进程发起进程注销指令， 触 发老版本进程集中的进程进行注销处理。 可选的， 如果通信设备上的控制面和管理面的任一软件同时存在以主用和备用状 态运行的进程， 则需要同时注销主用和备用状态的待升级进程。
S3： 待升级的老版本进程集中的进程注销时通知系统管理进程。 S4: 系统管理进程向上游进程和下游进程发送注销事件通知， 通知上下游进程保 持数据及数据状态不变， 避免导致业务中断。
S5: 版本管理进程发出启动新版本进程集指令， 启动新版本进程集。 可选的， 若要升级的软件是进程间接口发生变更的进程集， 则版本管理进程需要 确认待升级进程集中的所有进程都注销成功后， 才能启动新版本的进程集。 若在注销 过程中， 存在特定的进程注销超时或失败， 则版本管理进程反馈升级失败。 可选的， 如果通信设备上待升级的控制面和管理面的任一软件同时存在以主用和 备用状态运行的进程， 则版本管理进程需要等待主用和备用状态的待升级进程都注销 成功后才能启动新版本的进程。
S6: 新版本进程集启动时向系统管理进程注册。 S7: 系统管理进程向上游进程和下游进程发送注册通知， 通知上下游进程与升级 后的新版本进程集重新建链。 S8: 上游进程建链成功后， 向升级后的进程重新输出之前向老版本进程集输出的 数据， 协助升级后的进程集数据及数据状态的恢复。 可选的， 下游进程可以按需向升级后的进程输出之前向老版本进程集输出给自己 的数据， 协助升级后的新版本进程集进行数据及数据状态的恢复。
S9: 当升级后的新版本进程集成功恢复完成自己的数据及数据状态后， 进入正常 工作状态， 并向下游进程输出恢复后的数据； 可选的， 对控制面和转发面分离的设备而言， 若被升级进程是控制面进程， 且待 恢复的数据会影响到转发面的功能时， 则需要在数据恢复完成后再触发对转发面的表 项更新， 以减少对转发业务的影响；
S10:版本管理进程确认新版本进程集中的所有进程都启动和恢复成功后，才能确 认升级成功。 若在启动过程中， 存在特定的进程启动超时或失败， 则版本管理进程反 馈升级失败；
基于上述实施例， 下面介绍一个由进程集中进程间接口发生变更引起接入网关控 制面和管理面软件升级的应用实例。 应用场景： 接入网关控制面和管理面软件升级场景 图 5〜图 9显示了接入网关进程级控制面和管理面软件的升级场景， 图 5是软件升 级前的状态， 接入网关需要实现支撑进程和 FIB进程的升级， 涉及应用业务进程集中 的如下关联进程： 版本管理进程、 系统管理进程、 BGP进程、 RIP进程、 OSPF进程、 支撑进程、 FIB进程。 支撑进程和 FIB进程是需要升级的进程集。 支撑进程接收各路 由协议学习到的路由， 并进行最佳路由的计算， 然后生成最佳的 FIB， 输出到 FIB进 程； BGP进程、 RIP进程和 OSPF进程是待升级进程集 （支撑进程和 FIB进程） 的上 游进程， 它们实现相关的路由协议协商， 并将协商的路由输出到支撑进程， 支撑进程 选择最佳路由， 并输出给 FIB进程； FIB进程作为支撑进程的下游进程， 对支撑进程 输出给自己的 FIB表项进行维护和管理； 在网络上实施多进程操作系统的补丁软件升级方法的处理步骤如下：
C1 : 版本管理进程接收进程集升级命令， 将需要同时升级的存在进程间的接口变 更的进程集一支撑进程和 FIB进程的可执行文件作为相同补丁软件同时进行升级。 C2: 如图 6所示， 版本管理进程向待升级的老版本进程集中的支撑进程和 FIB进 程发起进程注销指令， 触发老版本支撑进程和 FIB进程进行注销处理。
C3: 系统管理进程感知到待升级的老版本支撑进程和 FIB进程的注销， 通知上游 进程一 BGP进程、 RIP进程和 OSPF进程， 使上游进程保持数据及数据状态不变， 避 免导致业务中断。
C4: 如图 7所示， 版本管理进程在待升级进程集中的支撑进程和 FIB进程都注销 成后， 发出启动指令， 启动新版本进程集中的支撑进程和 FIB进程， 支撑进程和 FIB 进程启动后向系统管理进程进行注册。
C5: 系统管理进程感知到新版本支撑进程和 FIB进程启动， 通知上游进程一 BGP 进程、 RIP进程和 OSPF进程， 使上游进程与升级后的支撑进程和重新建链；
C6: 如图 8所示， 上游进程与新版本支撑进程建链成功后， 向升级后的新版本支 撑进程重新输出之前向老版本进程集输出的数据， 协助升级后的支撑进程的数据及数 据状态的恢复。 如图 9所示， 当升级后的支撑进程成功恢复完成自己的数据及数据状 态后， 进入正常工作状态， 并向 FIB进程输出恢复后的数据。 C7: 版本管理进程确认新版本进程集中的支撑进程和 FIB进程都启动和恢复成功 后， 确认升级成功。 通常， 对已经发行的软件版本来说， 补丁软件主要用于修正版本中的局部故障或 局部新增小特性。 本发明实施例公开的是一种轻量级的补丁软件业务在线升级方案， 这种补丁软件的变更基本可以分成两类， 一类是特定进程的内部变更； 而另一类是特 定进程间的接口变更。 对第一类变更， 若变更只是特定进程的内部变更， 则软件升级 可以只单独升级变更涉及的进程， 将会极大的降低软件升级对运行中的业务的影响； 而对第二类存在特定进程间的接口变更的软件升级， 由于存在接口变更， 可以将接口 存在变更的进程作为一个软件升级单位进行升级。 这样， 将接口变更作为升级进程集 的内部变更。 待升级进程集的外部进程不感知， 以简化进程集的软件升级过程。 就补丁软件升级后的业务恢复， 主要考虑基于待升级软件的上下游进程来协助完 成。 原因是在支持多进程操作系统的通信设备中， 每个进程都不是孤立的， 每个进程 在运行过程中都会接受到上游进程的输入， 然后进行处理并生成自己的数据和数据状 态， 并向下游进程产生输出。 可见， 每个进程的数据和数据状态都是根据上游进程的 输入数据产生的。 因此， 如果特定的进程需要进行升级， 则可以通过上游进程对升级 后的进程重新输入数据的来触发升级后的进程重新创建和生成自己的数据和数据状 态。 本发明实施例所述补丁软件升级方法及系统， 可以对控制面和管理面软件和转发 面软件分离的通信设备， 进行进程级的控制面和管理面软件升级， 以避免软件升级带 来不必要的业务中断， 提高业务的可靠性和可用性， 避免业务中断带来重大的经济损 失， 提升用户业务体验。
通过具体实施方式的说明， 应当可对本发明为达成预定目的所采取的技术手段及 功效得以更加深入且具体的了解， 然而所附图示仅是提供参考与说明之用， 并非用来 对本发明加以限制。
工业实用性 如上所述， 本发明实施例提供的一种补丁软件升级方法及系统具有以下有益效 果： 可以对转发面软件与控制面和管理面软件分离的通信设备， 进行进程级的控制 面和管理面软件升级， 以避免软件升级带来不必要的业务中断， 提高业务的可靠性 和可用性， 避免业务中断带来重大的经济损失， 提升用户业务体验。 对支持多进程 的通信设备， 当特定进程间的接口变更时， 将接口存在变更的进程作为一个软件升 级单位进行升级， 这样将接口变更作为升级进程集的内部变更， 待升级进程集的升 级过程与单个进程内部变更引起的升级过程类似， 简化了进程集的软件升级过程。

Claims

权 利 要 求 书 、 一种补丁软件升级方法， 对于转发面软件与控制面和管理面软件分离的通信设 备， 对于控制面和管理面软件， 在由单进程内部变更引起进程升级的情况下， 所述方法包括：
步骤一， 版本管理进程触发待升级的老版本进程注销， 并保持所述老版本 进程的上游进程和下游进程的数据及数据状态不变；
步骤二， 在待升级的老版本进程注销成功后， 版本管理进程触发新版本进 程启动；
步骤三， 所述上游进程和下游进程协助所述新版本进程进行数据及数据状 态的恢复。 、 根据权利要求 1所述的补丁软件升级方法， 其中， 当通信设备上的控制面和管 理面的任一软件同时存在主用和备用状态运行的进程时， 在步骤一中所述版本 管理进程触发待升级的老版本进程注销， 具体包括：
版本管理进程同时触发主用状态的待升级老版本进程和备用状态的待升级 老版本进程注销。 、 根据权利要求 1所述的补丁软件升级方法， 其中， 所述步骤三， 具体包括： 所述新版本进程分别与所述上游进程和下游进程重新建链；
通过所述上游进程向新版本进程输出之前向老版本进程输出的数据，或者， 所述下游进程向新版本进程输出之前老版本进程输出给自己的数据， 使新版本 进程的数据及数据状态得以恢复。 、 根据权利要求 1-3中任一项所述的补丁软件升级方法， 其中， 所述方法还包括:
步骤四， 版本管理进程触发对转发面软件相关进程的数据及数据的状态进 行更新。 、 一种补丁软件升级方法， 对于转发面软件与控制面和管理面软件分离的通信设 备， 对于控制面和管理面软件， 在由进程集中进程间接口发生变更引起进程集 升级的情况下， 所述方法包括： 步骤一， 版本管理进程触发待升级的老版本进程集中的每个进程注销， 并 保持所述老版本进程集的上游进程和下游进程的数据及数据状态不变；
步骤二， 在待升级的老版本进程集中的所有进程注销成功后， 版本管理进 程触发新版本进程集中的每个进程启动；
步骤三， 所述上游进程和下游进程协助所述新版本进程集进行数据及数据 状态的恢复。 、 一种补丁软件升级系统， 对于转发面软件与控制面和管理面软件分离的通信设 备， 对于控制面和管理面软件， 在由单进程内部变更引起进程升级的情况下， 所述系统包括：
版本管理模块， 设置为触发待升级的老版本进程注销， 并保持所述老版本 进程的上游进程和下游进程保持数据及数据状态不变； 在待升级的老版本进程 注销成功后， 触发新版本进程启动；
数据恢复模块， 位于各进程内部， 所述上游进程和下游进程基于数据恢复 模块协助所述新版本进程进行数据及数据状态的恢复。 、 根据权利要求 6所述的补丁软件升级系统， 其中， 当通信设备上的控制面和管 理面的任一软件同时存在主用和备用状态运行的进程时， 所述版本管理模块， 具体设置为- 同时触发主用状态的待升级老版本进程和备用状态的待升级老版本进程注 销。 、 根据权利要求 6所述的补丁软件升级系统， 其中， 所述数据恢复模块， 具体包 括- 建链模块， 所述上游进程和下游进程通过建链模块与所述新版本进程重新 建链；
数据传输模块， 所述上游进程通过数据传输模块向新版本进程输出之前向 老版本进程输出的数据， 或者， 下游进程通过数据传输模块向新版本进程输出 之前老版本进程输出给自己的数据，使新版本进程的数据及数据状态得以恢复。 、 根据权利要求 6-8所述的补丁软件升级系统， 其中， 所述版本管理模块， 还设 置为在控制面和管理面软件相关进程升级完成后， 触发对转发面软件相关进程 的数据及数据的状态进行更新。 一种补丁软件升级系统， 对于转发面软件与控制面和管理面软件分离的通信设 备， 对于控制面和管理面软件， 在由进程集中进程间接口发生变更引起进程集 升级的情况下， 所述系统包括：
版本管理模块， 设置为触发待升级的老版本进程集中的每个进程注销， 并 保持所述老版本进程集的上游进程和下游进程的数据及数据状态不变； 在待升 级的老版本进程集中的所有进程注销成功后， 触发新版本进程集中的每个进程 启动；
数据恢复模块， 位于各进程内部， 所述上游进程和下游进程基于数据恢复 模块协助所述新版本进程集进行数据及数据状态的恢复。
PCT/CN2013/082103 2012-10-31 2013-08-22 一种补丁软件升级方法及系统 WO2014067324A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP13850466.7A EP2916487B1 (en) 2012-10-31 2013-08-22 Method and system for upgrading patching software
US14/439,274 US20150293759A1 (en) 2012-10-31 2013-08-22 Method and System for Upgrading Patching Software

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210426136.XA CN102937906B (zh) 2012-10-31 2012-10-31 一种补丁软件升级方法及系统
CN201210426136.X 2012-10-31

Publications (1)

Publication Number Publication Date
WO2014067324A1 true WO2014067324A1 (zh) 2014-05-08

Family

ID=47696805

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/082103 WO2014067324A1 (zh) 2012-10-31 2013-08-22 一种补丁软件升级方法及系统

Country Status (4)

Country Link
US (1) US20150293759A1 (zh)
EP (1) EP2916487B1 (zh)
CN (1) CN102937906B (zh)
WO (1) WO2014067324A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111352643A (zh) * 2020-02-29 2020-06-30 重庆宇涵电子科技有限公司 称重监测防控仪升级插件系统

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102937906B (zh) * 2012-10-31 2015-09-16 中兴通讯股份有限公司 一种补丁软件升级方法及系统
CN106227561A (zh) * 2016-07-20 2016-12-14 杭州华三通信技术有限公司 一种云操作系统升级方法及装置
JP6787475B2 (ja) 2016-07-21 2020-11-18 日本電気株式会社 通信装置、システム、ロールバック方法及びプログラム
CN112600854B (zh) * 2018-01-15 2024-02-13 华为技术有限公司 软件升级方法及系统
CN108712298B (zh) * 2018-08-28 2021-08-13 深信服科技股份有限公司 网络设备升级方法、装置、网络设备及存储介质
US10929124B2 (en) * 2018-09-28 2021-02-23 Workday, Inc. Application release using integration into unified code system
CN110505097B (zh) * 2019-08-28 2023-05-12 深信服科技股份有限公司 一种转发面升级方法、装置及电子设备和存储介质
CN112181469A (zh) * 2020-10-27 2021-01-05 北京百度网讯科技有限公司 软件升级方法、装置、电子设备及可读存储介质
CN114900424A (zh) * 2022-05-27 2022-08-12 网易（杭州）网络有限公司 数据热修复方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070174685A1 (en) * 2006-01-19 2007-07-26 Banks Donald E Method of ensuring consistent configuration between processors running different versions of software
CN101102219A (zh) * 2007-07-30 2008-01-09 华为技术有限公司 软件升级系统以及软件升级方法
CN101533356A (zh) * 2009-04-21 2009-09-16 华为技术有限公司 一种实现软件在线升级的方法、装置及系统
CN102937906A (zh) * 2012-10-31 2013-02-20 中兴通讯股份有限公司 一种补丁软件升级方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7490161B2 (en) * 2001-08-22 2009-02-10 Nokia Inc. Method and system for implementing OSPF redundancy
US7392520B2 (en) * 2004-02-27 2008-06-24 Lucent Technologies Inc. Method and apparatus for upgrading software in network bridges
US7453797B2 (en) * 2004-09-29 2008-11-18 Intel Corporation Method to provide high availability in network elements using distributed architectures
US8190720B1 (en) * 2006-06-01 2012-05-29 Cisco Technology, Inc. Performing an in-service software reload on a network device
CN101329633A (zh) * 2008-07-25 2008-12-24 北大方正集团有限公司 一种软件升级的方法和软件升级装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070174685A1 (en) * 2006-01-19 2007-07-26 Banks Donald E Method of ensuring consistent configuration between processors running different versions of software
CN101102219A (zh) * 2007-07-30 2008-01-09 华为技术有限公司 软件升级系统以及软件升级方法
CN101533356A (zh) * 2009-04-21 2009-09-16 华为技术有限公司 一种实现软件在线升级的方法、装置及系统
CN102937906A (zh) * 2012-10-31 2013-02-20 中兴通讯股份有限公司 一种补丁软件升级方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZHANG, MINDI ET AL.: "Design of ISSU System for Devices in Distributed Network", COMPUTER SYSTEMS & APPLICATIONS, vol. 19, no. 6, June 2010 (2010-06-01), pages 40 - 43, XP008179208 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111352643A (zh) * 2020-02-29 2020-06-30 重庆宇涵电子科技有限公司 称重监测防控仪升级插件系统

Also Published As

Publication number Publication date
EP2916487B1 (en) 2018-01-10
CN102937906B (zh) 2015-09-16
US20150293759A1 (en) 2015-10-15
EP2916487A4 (en) 2016-10-19
EP2916487A1 (en) 2015-09-09
CN102937906A (zh) 2013-02-20

Similar Documents

Publication Publication Date Title
WO2014067324A1 (zh) 一种补丁软件升级方法及系统
US9021459B1 (en) High availability in-service software upgrade using virtual machine instances in dual control units of a network device
WO2014067335A1 (zh) 一种分布式通信设备软件升级方法及系统
EP2619663B1 (en) In-service software upgrade on cards of virtual partition of network element that includes directing traffic away from cards of virtual partition
AU2005236835B2 (en) Routing system and method for transparently recovering routing states after a failover or during a software upgrade
WO2014067330A1 (zh) 一种分布式通信设备软件升级方法及系统
WO2012038872A1 (en) In-service software upgrade of control and line cards of network element
AU2004306913A1 (en) Redundant routing capabilities for a network node cluster
WO2010000142A1 (zh) 一种分布式网管系统及其维护管理方法
US7475280B1 (en) Active-active server for high availability of data replication management application
JP2007304845A (ja) 仮想計算機システムおよびソフトウェア更新方法
WO2013037314A1 (zh) 用于数据处理中心容灾备份的系统及方法
JP5056504B2 (ja) 制御装置、情報処理システム、情報処理システムの制御方法および情報処理システムの制御プログラム
CN106161086B (zh) 主控板重启的控制方法及装置
CN105763442B (zh) 主备倒换lacp聚合链路不中断的pon系统及方法
JP2008042807A (ja) ネットワークシステム
JP2012168623A (ja) 待機系計算機、クラスタシステム、サービス提供方法およびプログラム
JP2010146044A (ja) 冗長システム
CN100413261C (zh) 数据恢复的方法和系统
JP5544516B2 (ja) 高可用サーバシステム、高可用サーバシステムの障害時復旧方法、および高可用サーバ
WO2016197817A1 (zh) 一种退出平滑重启的方法及装置
CN106911568B (zh) Bgp gr实现方法及装置
JP5304359B2 (ja) 通信制御装置、データ同期方法およびデータ同期用プログラム
JP2015153128A (ja) 呼処理制御装置及びそのソフトウェア更新方法、呼処理システム、並びにコンピュータ・プログラム
JP2002149439A (ja) 分散処理システムにおけるサーバ切替え方法及びサーバ装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13850466

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14439274

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013850466

Country of ref document: EP