WO2016206399A1 - 通信设备中软件版本的升级方法、装置及通信设备 - Google Patents
通信设备中软件版本的升级方法、装置及通信设备 Download PDFInfo
- Publication number
- WO2016206399A1 WO2016206399A1 PCT/CN2016/074725 CN2016074725W WO2016206399A1 WO 2016206399 A1 WO2016206399 A1 WO 2016206399A1 CN 2016074725 W CN2016074725 W CN 2016074725W WO 2016206399 A1 WO2016206399 A1 WO 2016206399A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- control board
- main control
- upgrade
- packet
- message
- Prior art date
Links
Images
Classifications
-
- 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/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
Definitions
- the present invention relates to the field of communications, and in particular to a method, an apparatus, and a communication device for upgrading a software version in a communication device.
- the bearer network has completed the rapid development of IP and flattening to the ALL.
- Traditional telephone users, large customer private line users, mobile users, and Internet users are unified to a transmission after accessing the telecommunication network.
- the network forwards and processes data.
- PDN packet transfer network
- the device upgrade has a great impact on the network. If there is no node-level protection (linear protection or ring network protection cannot be protected in many scenarios), The upgrade will cause the service interruption of all users of the upgraded device, which is unacceptable to the end user; and because of the unified bearer, the service interruption involves many different users, and the time period during which the operator coordinates the interruption of multiple user services is also basically impossible.
- the bearer device proposes a variety of different solutions.
- One way is to provide node-level protection. Configure the active/standby node or the dual-homed node on the core node. When upgrading, let the service be switched to The backup node is used to protect the user's service.
- the other way is that the core router device supports ISSU (In-Service Software Upgrade).
- the ISSU solution is: for compatible versions, the master is switched over the active/standby switch, and the line card is hot-patched through the software. The mode is upgraded, and the upgrade does not interrupt the service. For the incompatible version, you need to reset the line card to implement software upgrade, which will cause service interruption.
- the problem is solved by adding a protection node.
- This method multiplies the network cost and maintenance cost of the operator by multiple times. Most users are reluctant to adopt this method, and mode 2 is only compatible with the version. In this case, the upgrade can be performed without interrupting the service. If the version is incompatible, the service will be interrupted. Actually, as the function continues to increase, the software version is incompatible most of the time.
- the present invention provides a method, an apparatus, and a communication device for upgrading a software version in a communication device, so as to at least solve the problem of how to implement an upgrade without interrupting the service in the case where the software version is incompatible in the related art.
- a method for upgrading a software version in a communication device including: in a software version upgrade process, a main control board in the communication device receives software for the main control board Version upgrade
- the upgrade packet is obtained by determining whether the main control board is compatible with the upgrade packet, and the judgment result is obtained.
- the main control board performs the upgrade message.
- the upgrade packet is discarded when the above-mentioned judgment result indicates that the main control board is not compatible with the upgrade packet.
- determining whether the control board is compatible with the upgrade packet includes: determining whether the upgrade packet is a packet that has been registered on the main control board; wherein, if the determination result is yes, determining The main control board is compatible with the upgrade packet, and if the judgment result is negative, it is determined that the main control board is not compatible with the upgrade message.
- the method further includes: in the communication device, the standby of the main control board
- the main control board receives the upgrade packet from the main control board.
- the standby main control board is upgraded by using the upgrade packet.
- the method further includes: the main control board switching the running service to the foregoing The standby main control board of the main control board.
- the method includes: resetting the main control board, and performing the reset operation on the standby main control board after the service is switched back to the main control board. Reset operation.
- an apparatus for upgrading a software version in a communication device which is applied to a main control board, and includes: a receiving module, configured to receive the foregoing in a software version upgrade process The upgraded version of the software version of the main control board is upgraded; the judging module is configured to determine whether the main control board is compatible with the upgraded message, and the judgment result is obtained; and the upgrade module is configured to indicate the main control order in the foregoing judgment result.
- the board When the board is compatible with the upgrade packet, the board upgrades the upgrade packet. If the result of the judgment indicates that the master board is not compatible with the upgrade packet, the upgrade packet is discarded.
- the determining module is further configured to: determine whether the upgraded packet is a packet that has been registered on the main control board; and if the determination result is yes, determine that the main control board is compatible with the upgrade. In the case of the packet, if the result of the determination is negative, it is determined that the main control board is not compatible with the upgrade message.
- a communications device including: a main control board, wherein the main control board is configured to receive the main control ticket during the software version upgrade process.
- the software version of the board is upgraded and upgraded; determining whether the main control board is compatible with the upgraded packet, and obtaining the judgment result; when the foregoing judgment result indicates that the main control board is compatible with the upgraded packet, the main control board
- the upgrade packet is upgraded by the foregoing upgrade packet.
- the upgrade packet is discarded.
- the main control board is further configured to determine whether the upgrade packet is a packet that has been registered on the main control board, and if the determination result is yes, determine the main control board. If the result of the determination is negative, it is determined that the above-mentioned main control board is not compatible with the upgraded packet.
- the method further includes: the standby main control board of the main control board; the standby main control board is configured to receive the upgrade message from the main control board, and upgrade by using the upgrade message.
- the main control board in the communication device receives the upgrade packet for upgrading the software version of the main control board; determining whether the main control board is compatible with the upgrade report. If the result of the judgment is that the main control board is not compatible with the upgraded packet, the control board is upgraded.
- the upgrade packet solves the problem of how to implement the upgrade without interrupting the service in the case where the software version is incompatible.
- FIG. 1 is a flowchart of a method for upgrading a software version in a communication device according to an embodiment of the present invention
- FIG. 2 is a structural block diagram of an apparatus for upgrading a software version in a communication device according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of a message, message processing control state machine according to an embodiment of the present invention.
- FIG. 4 is a diagram showing an example of a board of a device according to an embodiment of the present invention.
- FIG. 5 is a flowchart of an uninterrupted service upgrade process according to an embodiment of the present invention.
- FIG. 1 is a flowchart of a method for upgrading a software version in a communication device according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps. :
- Step S102 in the software version upgrade process, the main control board in the communication device receives the upgrade message for upgrading the software version of the main control board;
- Step S104 determining whether the main control board is compatible with the upgrade message, and obtaining a judgment result
- step S106 when the result of the judgment indicates that the main control board is compatible with the upgrade message, the main control board is upgraded by using the upgrade message; when the judgment result indicates that the main control board is not compatible with the upgrade message, the upgrade report is discarded. Text.
- the above steps are used to determine whether the upgrade packet is an upgrade packet compatible with the main control board, and the software version is upgraded according to the judgment result. Compared with the related technology, only when the version is compatible, the upgrade can be performed without interruption. The problem of how to implement the upgrade without interrupting the service in the case where the software version is incompatible is solved in the related technology.
- step S104 involves determining whether the main control board is compatible with the upgrade message. In an optional embodiment, determining the Whether the upgrade packet is a packet that has been registered on the master board. If the result of the judgment is yes, the master board is determined to be compatible with the upgrade packet. If the judgment result is negative, the master is determined. The control board is not compatible with the upgrade packet.
- the standby main control board of the main control board in the communication device before the main control board in the communication device receives the upgrade message for upgrading the software version of the main control board, the standby main control board of the main control board in the communication device The upgraded packet is received from the main control board. The standby main control board is upgraded through the upgrade packet. The software upgrade of the main control board and the standby main control board is completed.
- the main control board in the communication device receives the upgrade packet for upgrading the software version of the main control board, and the main control board is running. The service is switched to the standby main control board of the main control board.
- the main control board is upgraded by the upgrade packet, the main control board is reset, and after the service is switched back to the main control board, the standby main control board is reset. operating.
- the version upgrade is successful.
- the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
- the technical solution of the present invention in essence or the contribution to the related art can be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM).
- the instructions include a plurality of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the method of various embodiments of the present invention.
- an apparatus for upgrading a software version in a communication device is also provided.
- the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
- the term "module” may implement a combination of software and/or hardware of a predetermined function.
- the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
- the apparatus includes: a receiving module 22, which is set to be in a software version upgrade process. And receiving the upgrade message for upgrading the software version of the main control board; the determining module 24 is configured to determine whether the main control board is compatible with the upgrade message, and obtain the judgment result; and the upgrade module 26 is set to the judgment result.
- the upgrade packet is upgraded. If the control board indicates that the main control board is not compatible with the upgrade packet, the upgrade packet is discarded.
- the determining module 24 is further configured to determine whether the upgraded packet is a packet that has been registered on the main control board; wherein, if the determination result is yes, determining that the main control board is compatible with the upgrade report If the result of the determination is negative, it is determined that the main control board is not compatible with the upgrade message.
- each of the above modules may be implemented by software or hardware.
- the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
- a communication device including: a main control board, wherein the main control board is configured to receive the main control board during the software version upgrade process. Upgrade message for upgrading the software version; If the main control board is compatible with the upgrade packet, the control board is upgraded by the upgrade packet; the judgment result indicates that the master board is compatible with the upgrade packet. When the main control board is not compatible with the upgrade packet, the upgrade packet is discarded.
- the main control board is further configured to determine whether the upgrade packet is a packet that has been registered on the main control board; where the determination result is yes, determining that the main control board is compatible with the If the result of the judgment is no, the master board is not compatible with the upgrade packet.
- the method further includes: a standby main control board of the main control board; the standby main control board is configured to receive the upgrade message from the main control board, and upgrade the upgrade message.
- Embodiments of the present invention also provide a storage medium.
- the foregoing storage medium may be configured to store program code for performing the following steps:
- the main control board in the communication device receives an upgrade message for upgrading the software version of the main control board
- the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
- ROM Read-Only Memory
- RAM Random Access Memory
- a mobile hard disk e.g., a hard disk
- magnetic memory e.g., a hard disk
- the processor executes S1, S2, and S3 according to the stored program code in the storage medium.
- the optional embodiment provides an upgrade control method to solve the problem of service interruption caused by the device upgrade, which mainly includes:
- the standby master is upgraded first.
- the standby master restarts with the new version, data synchronization is not performed with the active master, but data is loaded locally.
- a registration mechanism is provided. For the upgrade process, messages and messages that are compatible with the process are required to be registered. For the registered messages and messages, the new master receives the message and the message, and then performs compatible processing; for other messages and Packets are discarded directly to avoid incompatibility, causing the main control or line card to be abnormal, causing service interruption.
- the line card reset sequence is controlled.
- the service board of the service is reset first, and the service is switched to the protection.
- the board is upgraded to the new version and works normally. After the service is switched back, the service protection list is reset. board.
- FIG. 3 is a schematic diagram of a message, message processing control state machine according to an embodiment of the present invention, which is explained below with reference to FIG. 3.
- the specific upgrade steps are as follows:
- Step 1 Determine whether the service configuration scripts between the upgraded versions are compatible. If they are not compatible, modify the incompatible parts, and the modified service configuration scripts are uploaded to the standby master.
- Step 2 Determine the reset order of the board, which can be automatically calculated according to the service configuration or manually configured.
- Step 1 Upload a new software version to the device, and the standby master synchronizes from the primary master to the latest software version.
- Step 2 Activate the standby master, restart the standby master, run the new software version, and restore the service data from the board configuration script.
- the third step the active/standby switchover, the standby master switch to the master, the original master restart, and the original master master is updated to the new version.
- the fourth step the main control runs the new version, the line card runs the old version, and the main control processes according to the message and the registration of the message, and performs compatible processing on the registered message and the message. For the unregistered message and the message, directly throw away.
- Step 5 Reset the board according to the determined board reset sequence. After the service board is reset, you need to wait for the board to run normally. After the service is switched back, the service standby board is reset. The entire reset process can be automatically processed. Or manual control.
- Step 1 After all the line cards are reset, check whether the board is running normally and the service is normal.
- the second part the firmware version, the version upgrade is successful.
- the device After the upgrade is complete, the device enters the normal state and works. The message is forwarded normally and the packet is forwarded.
- FIG. 4 is a schematic diagram of a device board insertion board according to an embodiment of the present invention
- FIG. 5 is a flowchart of an uninterrupted service upgrade process according to an embodiment of the present invention.
- FIG. 4 and FIG. 5 are used as an example to describe an upgrade process.
- the interrupt service upgrade process is as follows:
- the board of the S501:1 is the master controller, and the board of the second board is the standby master.
- the software version of the board is activated.
- S502 The version of the board is successfully activated, and the board is restarted. After the restart, the board 2 loads the service configuration data locally according to the current status (upgrade).
- S504 The primary board of the first board is switched to the standby board. After the board is reset, the new version is run and the data is synchronized from the second board.
- Figure 4 is used as an example to describe the sequence of board reset during the upgrade process.
- the registration mechanism provided by the embodiment of the present invention performs compatibility processing on the messages that need to be compatible with the software versions, and the control of the board reset sequence is used to solve the problem of service interruption during the upgrade of the network element.
- the problem is that compared with the ISSU upgrade control mode, the software version is simplified and judged and processed, especially when the software version is incompatible, and the upgrade is not interrupted, and the uninterrupted service of most scenarios is solved. Upgrade issue.
- modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the main control board in the communication device receives the upgrade packet for upgrading the software version of the main control board; determining whether the main control board is compatible with the upgrade. The message is obtained, and the result of the judgment is obtained.
- the main control board is upgraded by using the upgrade message; when the judgment result indicates that the main control board is not compatible with the upgrade message, Discarding the upgrade packet solves the problem of how to implement the upgrade without interrupting the service when the software version is incompatible.
Abstract
本发明提供了一种通信设备中软件版本的升级方法、装置及通信设备，其中，该方法包括：在软件版本升级过程中，通信设备内的主控单板接收用于对主控单板的软件版本进行升级的升级报文；判断主控单板是否兼容该升级报文，得到判断结果；在判断结果指示主控单板兼容该升级报文时，主控单板通过该升级报文进行升级；在判断结果指示主控单板不兼容该升级报文时，丢弃该升级报文。通过本发明解决了相关技术中如何在软件版本不兼容的情况下，实现升级不中断业务的问题。
Description
本发明涉及通信领域，具体而言，涉及一种通信设备中软件版本的升级方法、装置及通信设备。
随着网络融合的发展，承载网完成了向ALL IP化、扁平化的快速发展，传统的电话用户、大客户专线用户、移动用户、互联网用户等在接入到电信网络后，统一到一个传送网络进行数据的转发和处理。对于处于网络汇聚层和核心层的分组传送网(Packet Transfer Network，简称为PTN)设备，设备升级对网络影响非常大，如果没有节点级别的保护(线性保护或者环网保护很多场景无法保护)，升级会造成所有经过升级设备的用户业务中断，对最终用户来说这是不能接受的；而且由于统一承载，业务中断涉及多种不同的用户，运营商协调多种用户业务中断的时间段也基本不可能。
为了解决升级造成的业务中断问题，承载设备提出了多种不同的解决方案，一种方式是提供节点级别的保护，在核心节点配置主备节点或者双归节点，升级的时候，让业务倒换到备用节点，从而保护用户业务；另外一种方式是核心路由器设备支持ISSU(In-Service Software Upgrade)功能，ISSU解决方法是：对于兼容版本，主控通过主备倒换，线卡通过软件热补丁的方式升级，实现升级不中断业务；对于不兼容的版本，需要复位线卡实现软件升级，会造成业务中断。
上述方式一，通过增加保护节点的方式来解决问题，这种方式让运营商的组网成本和维护成本成倍增加，大部分用户不愿意采用这种方式，而方式二，只在版本兼容的情况下，能做到升级不中断业务，在版本不兼容的情况下，业务会发生中断；实际的情况是，随着功能的不断增加，软件版本大部分时候是不兼容的。
如何在软件版本不兼容的情况下，做到升级不中断业务，是迫切需要解决的问题。
针对相关技术中，如何在软件版本不兼容的情况下，实现升级不中断业务的问题，还未提出有效的解决方案。
发明内容
本发明提供了一种通信设备中软件版本的升级方法、装置及通信设备，以至少解决相关技术中如何在软件版本不兼容的情况下，实现升级不中断业务的问题。
根据本发明实施例的一个方面，提供了一种通信设备中软件版本的升级方法，包括：在软件版本升级过程中，通信设备内的主控单板接收用于对上述主控单板的软件版本进行升级
的升级报文；判断上述主控单板是否兼容上述升级报文，得到判断结果；在上述判断结果指示上述主控单板兼容上述升级报文时，上述主控单板通过上述升级报文进行升级；在上述判断结果指示上述主控单板不兼容上述升级报文时，丢弃上述升级报文。
可选地，判断上述主控单板是否兼容上述升级报文包括：判断上述升级报文是否为已在上述主控单板进行注册的报文；其中，在判断结果为是的情况下，确定上述主控单板兼容上述升级报文，在判断结果为否的情况下，确定上述主控单板不兼容上述升级报文。
可选地，通信设备内的主控单板接收用于对上述主控单板的软件版本进行升级的升级报文之前，上述方法还包括：在上述通信设备内，上述主控单板的备用主控单板从上述主控单板接收上述升级报文；上述备用主控单板通过上述升级报文进行升级。
可选地，通信设备内的主控单板接收用于对上述主控单板的软件版本进行升级的升级报文之前，上述方法还包括：上述主控单板将正在运行的业务切换至上述主控单板的备用主控单板。
可选地，上述主控单板通过上述升级报文进行升级之后包括：对上述主控单板进行复位操作，并在上述业务切换回上述主控单板后，对上述备用主控单板进行复位操作。
根据本发明实施例的另一个方面，还提供了一种通信设备中软件版本的升级装置，应用于主控单板，包括：接收模块，设置为在软件版本升级过程中，接收用于对上述主控单板的软件版本进行升级的升级报文；判断模块，设置为判断上述主控单板是否兼容上述升级报文，得到判断结果；升级模块，设置为在上述判断结果指示上述主控单板兼容上述升级报文时，通过上述升级报文进行升级；在上述判断结果指示上述主控单板不兼容上述升级报文时，丢弃上述升级报文。
可选地，上述判断模块还设置为判断上述升级报文是否为已在上述主控单板进行注册的报文；其中，在判断结果为是的情况下，确定上述主控单板兼容上述升级报文，在判断结果为否的情况下，确定上述主控单板不兼容上述升级报文。
根据本发明实施例的再一个方面，还提供了一种通信设备，包括：主控单板；其中，上述主控单板，设置为在软件版本升级过程中，接收用于对上述主控单板的软件版本进行升级的升级报文；判断上述主控单板是否兼容上述升级报文，得到判断结果；在上述判断结果指示上述主控单板兼容上述升级报文时，上述主控单板通过上述升级报文进行升级；在上述判断结果指示上述主控单板不兼容上述升级报文时，丢弃上述升级报文。
可选地，上述主控单板，还设置为判断上述升级报文是否为已在上述主控单板进行注册的报文；其中，在判断结果为是的情况下，确定上述主控单板兼容上述升级报文，在判断结果为否的情况下，确定上述主控单板不兼容上述升级报文。
可选地，还包括：上述主控单板的备用主控单板；上述备用主控单板，设置为从上述主控单板接收上述升级报文，以及通过上述升级报文进行升级。
通过本发明实施例，采用在软件版本升级过程中，通信设备内的主控单板接收用于对主控单板的软件版本进行升级的升级报文；判断主控单板是否兼容该升级报文，得到判断结果；在判断结果指示主控单板兼容该升级报文时，主控单板通过该升级报文进行升级；在判断结果指示主控单板不兼容该升级报文时，丢弃该升级报文，解决了相关技术中如何在软件版本不兼容的情况下，实现升级不中断业务的问题。
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的通信设备中软件版本的升级方法的流程图；
图2是根据本发明实施例的通信设备中软件版本的升级装置的结构框图；
图3是根据本发明实施例的消息、报文处理控制状态机示意图；
图4是根据本发明实施例的设备单板插板示例图；
图5是根据本发明实施例的不中断业务升级处理流程图。
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种通信设备中软件版本的升级方法，图1是根据本发明实施例的通信设备中软件版本的升级方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，在软件版本升级过程中，通信设备内的主控单板接收用于对主控单板的软件版本进行升级的升级报文；
步骤S104，判断主控单板是否兼容该升级报文，得到判断结果；
步骤S106，在判断结果指示主控单板兼容该升级报文时，主控单板通过该升级报文进行升级；在判断结果指示主控单板不兼容该升级报文时，丢弃该升级报文。
通过上述步骤，判断升级报文是否是主控单板兼容的升级报文，根据判断结果进行软件版本的升级，相比于相关技术中，只有版本兼容的情况下，能做到升级不中断业务，解决了相关技术中如何在软件版本不兼容的情况下，实现升级不中断业务的问题。
上述步骤S104涉及到判断主控单板是否兼容该升级报文，在一个可选实施例中，判断该
升级报文是否为已在主控单板进行注册的报文；其中，在判断结果为是的情况下，确定主控单板兼容该升级报文，在判断结果为否的情况下，确定主控单板不兼容该升级报文。
在一个可选实施例中，通信设备内的主控单板接收用于对主控单板的软件版本进行升级的升级报文之前，在通信设备内，主控单板的备用主控单板从主控单板接收该升级报文，备用主控单板通过该升级报文进行升级。从而完成了主控单板与备用主控单板的软件升级。
为了保证业务不丢失，在一个可选实施例中，通信设备内的主控单板接收用于对该主控单板的软件版本进行升级的升级报文之前，主控单板将正在运行的业务切换至主控单板的备用主控单板。
在一个可选实施例中，主控单板通过该升级报文进行升级之后，对主控单板进行复位操作，并在业务切换回该主控单板后，对备用主控单板进行复位操作。从而版本升级成功。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例该的方法。
在本实施例中还提供了一种通信设备中软件版本的升级装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图2是根据本发明实施例的通信设备中软件版本的升级装置的结构框图，应用于主控单板，如图2所示，该装置包括：接收模块22，设置为在软件版本升级过程中，接收用于对主控单板的软件版本进行升级的升级报文；判断模块24，设置为判断主控单板是否兼容该升级报文，得到判断结果；升级模块26，设置为在判断结果指示该主控单板兼容该升级报文时，通过该升级报文进行升级；在判断结果指示该主控单板不兼容该升级报文时，丢弃该升级报文。
可选地，判断模块24还设置为判断该升级报文是否为已在该主控单板进行注册的报文；其中，在判断结果为是的情况下，确定主控单板兼容该升级报文，在判断结果为否的情况下，确定该主控单板不兼容该升级报文。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
在另一个可选实施例中，还提供了一种通信设备，包括：主控单板；其中，主控单板，设置为在软件版本升级过程中，接收用于对该主控单板的软件版本进行升级的升级报文；判
断该主控单板是否兼容该升级报文，得到判断结果；在判断结果指示该主控单板兼容该升级报文时，主控单板通过该升级报文进行升级；在判断结果指示该主控单板不兼容该升级报文时，丢弃该升级报文。
可选地，主控单板，还设置为判断该升级报文是否为已在该主控单板进行注册的报文；其中，在判断结果为是的情况下，确定主控单板兼容该升级报文，在判断结果为否的情况下，确定主控单板不兼容该升级报文。
可选地，还包括：主控单板的备用主控单板；备用主控单板，设置为从主控单板接收该升级报文，以及通过该升级报文进行升级。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，在软件版本升级过程中，通信设备内的主控单板接收用于对主控单板的软件版本进行升级的升级报文；
S2，判断主控单板是否兼容该升级报文，得到判断结果；
S3，在判断结果指示主控单板兼容该升级报文时，主控单板通过该升级报文进行升级；在判断结果指示主控单板不兼容该升级报文时，丢弃该升级报文。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行S1、S2和S3。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
针对PTN的设备特点，本可选实施例提供了一种升级控制方法，来解决设备升级造成业务中断的问题，主要包括：
先升级备用主控，备用主控重启以新版本运行的时候，不与主用主控进行数据同步，而是从本地进行数据加载。
提供注册机制，对于升级过程中，需要兼容处理的消息和报文，进行注册，对于注册的消息和报文，新主控收到该类消息和报文后，进行兼容处理；对于其他消息和报文，直接丢弃，避免不兼容造成主控或者线卡异常，造成业务中断。
线卡复位顺序控制，对跨板保护的业务，先复位业务的工作单板，触发业务倒换到保护，待工作单板升级为新版本，工作正常，业务回切后，再复位业务的保护单板。
图3是根据本发明实施例的消息、报文处理控制状态机示意图，下面针对图3进行解释。具体的升级步骤如下：
升级准备(初始化(initialization，init))：
第一步：确定升级版本间业务配置脚本是否兼容，如果不兼容，对不兼容部分进行修改，修改后的业务配置脚本上传到备用主控。
第二步：确定设备单板复位顺序，可以根据业务配置情况自动进行计算，或者是手动配置。
升级(upgrade)：
第一步：上传新的软件版本到设备上，备用主控从主用主控同步到最新的软件版本。
第二步：激活备用主控，备用主控重启，运行新的软件版本，业务数据从本板业务配置脚本恢复。
第三步：进行主备倒换，备用主控转主，原主用重启，原主用主控更新为新版本。
第四步：主控运行新版本，线卡运行旧版本，主控根据消息和报文注册情况进行处理，对于注册的消息和报文，进行兼容处理，对于未注册的消息和报文，直接丢弃。
第五步：根据确定的单板复位顺序，进行单板复位，业务所在工作单板复位后，需要等单板运行正常，业务回切后，再复位业务备用单板，整个复位过程可以自动处理或者手动控制。
升级完成：
第一步：所有线卡复位后，确认单板是否运行正常，业务是否正常。
第二部：固化版本，版本升级成功。
升级完成后，进入正常态，工作(work)：正常进行消息、报文转发处理。
实施例1：
图4是根据本发明实施例的设备单板插板示例图，图5是根据本发明实施例的不中断业务升级处理流程图，以图4和图5为例，对升级过程进行描述，不中断业务升级流程如下：
S501：1号单板为主用主控，2号单板为备用主控，激活2号单板软件版本；
S502：2号单板版本激活成功，单板重启，重启后，2号单板根据当前状态(升级)从本地进行业务配置数据加载；
S503：2号单板上电成功后，进行主备倒换，2号单板转主成功后，进入升级状态，对于注册的消息、报文进行兼容处理；对于未注册的消息、报文直接丢弃；
S504：1号单板主转备，单板复位，重启后，以新版本运行，数据从2号单板同步；
S505：主控升级完成，复位交换单板；
S506：交换单板上电完成后，复位宽带线卡；
S507：所有单板升级到新版本，单板上电正常，升级完成。
实施例2：
以图4为例，对升级过程进行中单板复位的顺序进行描述
S201：复位2号主控，升级为新版本；
S202：复位1号主控，转为备用主控，运行新版本；
S203：复位4号交换单板，单板加载新版本；
S204：复位5号交换单板，单板加载新版本；
S205：复位3号业务线卡，单板加载新版本；
S206：复位6号业务线卡，单板加载新版本。
综上所述，通过本发明实施例提供的注册机制，对软件版本间需要兼容处理的消息进行兼容处理，并通过单板复位顺序的控制，很好的解决了网元升级期间，业务中断的问题，相对于ISSU的升级控制方式，简化了软件版本是否兼容的判断和处理，特别对软件版本不兼容的情况，也能很好的保证升级不中断业务，解决了大部分场景的不中断业务升级问题。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
在本发明实施例中，采用在软件版本升级过程中，通信设备内的主控单板接收用于对主控单板的软件版本进行升级的升级报文；判断主控单板是否兼容该升级报文，得到判断结果；在判断结果指示主控单板兼容该升级报文时，主控单板通过该升级报文进行升级；在判断结果指示主控单板不兼容该升级报文时，丢弃该升级报文，解决了相关技术中如何在软件版本不兼容的情况下，实现升级不中断业务的问题。
Claims (10)
- 一种通信设备中软件版本的升级方法，包括：在软件版本升级过程中，通信设备内的主控单板接收用于对所述主控单板的软件版本进行升级的升级报文；判断所述主控单板是否兼容所述升级报文，得到判断结果；在所述判断结果指示所述主控单板兼容所述升级报文时，所述主控单板通过所述升级报文进行升级；在所述判断结果指示所述主控单板不兼容所述升级报文时，丢弃所述升级报文。
- 根据权利要求1所述的方法，其中，判断所述主控单板是否兼容所述升级报文包括：判断所述升级报文是否为已在所述主控单板进行注册的报文；其中，在判断结果为是的情况下，确定所述主控单板兼容所述升级报文，在判断结果为否的情况下，确定所述主控单板不兼容所述升级报文。
- 根据权利要求1所述的方法，其中，通信设备内的主控单板接收用于对所述主控单板的软件版本进行升级的升级报文之前，所述方法还包括：在所述通信设备内，所述主控单板的备用主控单板从所述主控单板接收所述升级报文；所述备用主控单板通过所述升级报文进行升级。
- 根据权利要求1所述的方法，其中，通信设备内的主控单板接收用于对所述主控单板的软件版本进行升级的升级报文之前，所述方法还包括：所述主控单板将正在运行的业务切换至所述主控单板的备用主控单板。
- 根据权利要求4所述的方法，其中，所述主控单板通过所述升级报文进行升级之后包括：对所述主控单板进行复位操作，并在所述业务切换回所述主控单板后，对所述备用主控单板进行复位操作。
- 一种通信设备中软件版本的升级装置，应用于主控单板，包括：接收模块，设置为在软件版本升级过程中，接收用于对所述主控单板的软件版本进行升级的升级报文；判断模块，设置为判断所述主控单板是否兼容所述升级报文，得到判断结果；升级模块，设置为在所述判断结果指示所述主控单板兼容所述升级报文时，通过所述升级报文进行升级；在所述判断结果指示所述主控单板不兼容所述升级报文时，丢弃所述升级报文。
- 根据权利要求6所述的装置，其中，所述判断模块还设置为判断所述升级报文是否为已 在所述主控单板进行注册的报文；其中，在判断结果为是的情况下，确定所述主控单板兼容所述升级报文，在判断结果为否的情况下，确定所述主控单板不兼容所述升级报文。
- 一种通信设备，包括：主控单板；其中，所述主控单板，设置为在软件版本升级过程中，接收用于对所述主控单板的软件版本进行升级的升级报文；判断所述主控单板是否兼容所述升级报文，得到判断结果；在所述判断结果指示所述主控单板兼容所述升级报文时，所述主控单板通过所述升级报文进行升级；在所述判断结果指示所述主控单板不兼容所述升级报文时，丢弃所述升级报文。
- 根据权利要求8所述的通信设备，其中，所述主控单板，还设置为判断所述升级报文是否为已在所述主控单板进行注册的报文；其中，在判断结果为是的情况下，确定所述主控单板兼容所述升级报文，在判断结果为否的情况下，确定所述主控单板不兼容所述升级报文。
- 根据权利要求8所述的通信设备，其中，还包括：所述主控单板的备用主控单板；所述备用主控单板，设置为从所述主控单板接收所述升级报文，以及通过所述升级报文进行升级。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510355855.0 | 2015-06-24 | ||
| CN201510355855.0A CN107026743A (zh) | 2015-06-24 | 2015-06-24 | 通信设备中软件版本的升级方法、装置及通信设备 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016206399A1 true WO2016206399A1 (zh) | 2016-12-29 |
Family
ID=57584583
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/074725 WO2016206399A1 (zh) | 2015-06-24 | 2016-02-26 | 通信设备中软件版本的升级方法、装置及通信设备 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107026743A (zh) |
| WO (1) | WO2016206399A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109787789A (zh) * | 2017-11-10 | 2019-05-21 | 中兴通讯股份有限公司 | 软件升级的兼容性管理方法、装置及设备、存储介质 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070256067A1 (en) * | 2006-04-26 | 2007-11-01 | Cisco Technology, Inc. (A California Corporation) | Method and system for upgrading a software image |
| CN101599856A (zh) * | 2009-06-30 | 2009-12-09 | 上海华为技术有限公司 | 一种软件升级的方法及系统 |
| CN103490931A (zh) * | 2013-09-25 | 2014-01-01 | 杭州华三通信技术有限公司 | 一种不中断业务升级过程中协议不中断的方法和装置 |
| CN103533027A (zh) * | 2013-09-22 | 2014-01-22 | 瑞斯康达科技发展股份有限公司 | 一种分布式设备及软件版本兼容性维护的方法、系统 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102136930B (zh) * | 2010-09-03 | 2014-02-19 | 华为技术有限公司 | 一种版本升级方法和路由设备 |
| CN104320475B (zh) * | 2014-10-31 | 2019-01-18 | 新华三技术有限公司 | 一种设备升级方法及装置 |
-
2015
- 2015-06-24 CN CN201510355855.0A patent/CN107026743A/zh active Pending
-
2016
- 2016-02-26 WO PCT/CN2016/074725 patent/WO2016206399A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070256067A1 (en) * | 2006-04-26 | 2007-11-01 | Cisco Technology, Inc. (A California Corporation) | Method and system for upgrading a software image |
| CN101599856A (zh) * | 2009-06-30 | 2009-12-09 | 上海华为技术有限公司 | 一种软件升级的方法及系统 |
| CN103533027A (zh) * | 2013-09-22 | 2014-01-22 | 瑞斯康达科技发展股份有限公司 | 一种分布式设备及软件版本兼容性维护的方法、系统 |
| CN103490931A (zh) * | 2013-09-25 | 2014-01-01 | 杭州华三通信技术有限公司 | 一种不中断业务升级过程中协议不中断的方法和装置 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109787789A (zh) * | 2017-11-10 | 2019-05-21 | 中兴通讯股份有限公司 | 软件升级的兼容性管理方法、装置及设备、存储介质 |
| CN109787789B (zh) * | 2017-11-10 | 2022-08-12 | 中兴通讯股份有限公司 | 软件升级的兼容性管理方法、装置及设备、存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107026743A (zh) | 2017-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190179726A1 (en) | Monitoring method and apparatus of server, and storage medium | |
| CN107357571B (zh) | 设备组件程序的维护方法及系统 | |
| CN104486108A (zh) | 基于Zookeeper的节点配置方法和基于Zookeeper的节点配置系统 | |
| CN107005435B (zh) | 一种网络服务描述符上架方法及装置 | |
| EP3522449B1 (en) | Service state transition method and device | |
| CN111147314A (zh) | 交换机升级方法、装置及存储介质 | |
| CN104503861A (zh) | 一种异常处理方法及系统、代理设备与控制装置 | |
| CN104579889A (zh) | 一种用于调用网络功能的方法及装置 | |
| CN104426816B (zh) | 一种虚拟机通信方法及装置 | |
| CN113037599A (zh) | 一种报文处理的方法、设备及存储介质 | |
| CN109787789B (zh) | 软件升级的兼容性管理方法、装置及设备、存储介质 | |
| WO2016206399A1 (zh) | 通信设备中软件版本的升级方法、装置及通信设备 | |
| JP2006113754A (ja) | ソフトウェア更新装置及び方法 | |
| CN111434098B (zh) | 交换机、通信系统、注册方法以及计算机可读介质 | |
| EP3355480A1 (en) | Communication device, communication processing method, communication processing apparatus and communication system | |
| WO2017080499A1 (zh) | 管理指示发送、vnf自动伸缩功能的管理方法及装置 | |
| WO2016177202A1 (zh) | 一种补丁维护的方法及装置 | |
| CN113535402A (zh) | 基于5g mec的负载均衡处理方法、装置及电子设备 | |
| CN102790814B (zh) | 一种媒体接入控制地址确定方法、相关装置及系统 | |
| CN107528714B (zh) | 脚本处理方法、装置、系统及路由器 | |
| CN109981365A (zh) | 数据监听方法、装置、用户设备及存储介质 | |
| CN111240805A (zh) | 云操作系统用户切换处理方法及装置 | |
| CN112104506B (zh) | 组网方法、装置、服务器及可读存储介质 | |
| CN111857761A (zh) | 一种容器集群服务应用程序升级的方法及设备 | |
| CN106851676A (zh) | 一种快速启动基站的方法及装置 |
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: 16813515 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16813515 Country of ref document: EP Kind code of ref document: A1 |