CN114518891A

CN114518891A - Single board upgrading method, single board equipment and computer readable storage medium

Info

Publication number: CN114518891A
Application number: CN202011302415.6A
Authority: CN
Inventors: 刘素勇
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-11-19
Filing date: 2020-11-19
Publication date: 2022-05-20

Abstract

The embodiment of the invention provides a single board upgrading method, single board equipment and a computer readable storage medium, wherein the single board upgrading method is used for activating an obtained patch package; analyzing the patch package to obtain a single board parameter corresponding to the patch package; confirming a setting slot position of the single board to be upgraded corresponding to the patch package according to the single board parameters; and upgrading the single board to be upgraded according to the setting slot position, accurately identifying the effective range of the patch package, and executing upgrading operation.

Description

Single board upgrading method, single board equipment and computer readable storage medium

Technical Field

The embodiment of the invention relates to the field of communication equipment, in particular to a single board upgrading method, single board equipment and a computer readable storage medium.

Background

With the continuous development of communication technology, the requirements of various industries on the stability of communication service and the friendliness of operation and maintenance operation are also improved. In the related technology, the whole software version upgrading process of the communication equipment can realize lossless or micro-loss upgrading, and the influence on the service function is small. However, in practical applications, the upgrade period of the whole basic software version of the network element is still relatively long, and a more frequent upgrade scenario is a problem of repairing the basic version of the network element by a patching method, but in the related art, patching upgrade has a relatively high professional requirement on field upgrade operators, and meanwhile, the work of confirming the effectiveness of cold patches is relatively complex, especially when a plurality of cold patches exist in an engineering environment, the single boards related to each cold patch may be different but need to be maintained, so that engineers are required to ensure the operation and maintenance level of practical operation.

Disclosure of Invention

The single board upgrading method, the single board device and the computer readable storage medium provided by the embodiment of the invention mainly solve the technical problems that patch upgrading has higher professional requirements on field upgrading operators and the upgrading process is complex in the related technology.

To solve the foregoing technical problem, an embodiment of the present invention provides a board upgrading method, including:

activating the obtained patch package;

analyzing the patch package to obtain the single board parameters corresponding to the patch package;

confirming a setting slot position of the single board to be upgraded corresponding to the patch package according to the single board parameters;

and upgrading the single board to be upgraded according to the set slot position.

The embodiment of the invention also provides single board equipment, a processor, a memory and a communication bus;

the communication bus is used for realizing connection communication between the processor and the memory;

the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the single board upgrade method as described above

An embodiment of the present invention further provides a computer-readable storage medium, where one or more programs are stored, and the one or more programs may be executed by one or more processors to implement the steps of the single board upgrade method described above.

According to the single board upgrading method, the single board device and the computer readable storage medium provided by the embodiment of the invention, the obtained patch package is activated; analyzing the patch package to obtain the single board parameters corresponding to the patch package; according to the single board parameters, confirming the setting slot position of the single board to be upgraded corresponding to the patch package, and upgrading the single board to be upgraded; the effective range of the patch package is accurately identified, the upgrading operation is executed, and the technical effects of improving the automation degree of the patch package upgrading and reducing the operation work of field upgrading operators can be achieved in certain implementation processes.

Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Drawings

Fig. 1 is a schematic flowchart of a board upgrading method according to a first embodiment of the present invention;

fig. 2 is a schematic diagram of a version directory installed in a network element device according to a second embodiment of the present invention;

fig. 3 is a schematic diagram of a version directory currently activated and running in a memory by a network element device according to a second embodiment of the present invention;

fig. 4 is a schematic diagram of a version directory in a memory after a network element device activates a cold patch package according to a second embodiment of the present invention;

fig. 5 is a schematic diagram of configuration information of each slot-position board according to a second embodiment of the present invention;

fig. 6 is a schematic view of a detailed flow of a board upgrading method according to a second embodiment of the present invention;

FIG. 7 is a flowchart illustrating a second embodiment of the present invention for obtaining and installing a cold patch;

fig. 8 is a schematic diagram illustrating a service protection group relationship in a board of each slot according to a second embodiment of the present invention;

fig. 9 is a schematic diagram illustrating a configuration of upgrade priority of a board in each slot according to a second embodiment of the present invention;

FIG. 10 is a diagram illustrating calculation of a remaining estimated time according to a second embodiment of the present invention;

fig. 11 is a schematic diagram illustrating an upgrade progress display at startup according to a second embodiment of the present invention;

fig. 12 is a schematic view illustrating an upgrade progress display in the upgrade according to the second embodiment of the present invention;

fig. 13 is a schematic view showing an upgrade progress after the upgrade is completed according to the second embodiment of the present invention;

fig. 14 is a schematic structural diagram of a single board device according to a third embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The first embodiment is as follows:

to reduce the complicated operation in upgrading a board. An embodiment of the present invention provides a method for upgrading a board, please refer to fig. 1, including:

s101, activating the obtained patch package;

it should be noted that the patch package in this embodiment may also be, in other embodiments, a patch package including, but not limited to, an incremental package, a full-scale package, or another patch package that can be upgraded by applying the single board upgrading method of this embodiment.

The patch package may be downloaded in advance, and the patch package includes a software package that can be used to upgrade version software running in part or all of the boards in the board device. As a specific example, the patch package may be stored in a hard disk of the host board, in this example, the directory into which the patch package is introduced is an independent directory, and is parallel to the storage directory of the basic version package; in some embodiments, if a standby device (i.e., a standby main control board) exists, the main control board and the standby main control board may synchronize patch packet files, so as to ensure that a patch packet can still normally take effect after main/standby switching.

It should be noted that, activating a patch package in this embodiment refers to replacing a file of a version package that takes effect in a system of a current single board device with a file in the patch package, and in a specific example, the replacing refers to soft linking of a version file that is expected to take effect by a current system into a file in the patch package, that is, an activating operation is performed, and only is that all version files of a version server are soft linked into a file in the patch package. It should be understood that, after the patch package is activated, the patch package is not actually updated into the corresponding board, after the patch package is activated, the board usually needs to be reset and restarted, the board requests the currently activated version file to be loaded during the reset and restart process, at this time, the file in the activated patch package is loaded by the board, and the update of the patch package is equivalent to the actual application.

S102, analyzing the patch package to obtain a single board parameter corresponding to the patch package;

in practical application, the configuration file may be carried in the patch package, and analyzing the patch package may include reading configuration information in the configuration file, and the single board parameter may be obtained by analyzing the patch package. In this embodiment, the board parameter may reflect information of the patch package for the board, and illustratively, the board parameter includes, but is not limited to, a Central Processing Unit (CPU) model of the board.

S103, according to the single board parameters, determining a setting slot position of the single board to be upgraded corresponding to the patch package;

in practical applications, the slot configuration of the board is recorded, and for example, the information of the board set in each cabinet frame slot can be known by reading the static configuration information of the cabinet frame slot of the board. By analyzing the single board parameters obtained by the patch package, the single board matched with the single board parameters and the slot position information set by the single board parameters can be found out from the cabinet frame slot static configuration. Illustratively, the board parameter is the CPU model of the board, and the board using the CPU model is searched from the cabinet frame slot static configuration, and the slot position set by the board is known.

And S104, upgrading the single board to be upgraded according to the set slot position.

Under normal conditions, the loading of the patch package file can be completed by resetting and restarting the single boards to be upgraded. In this embodiment, the board to be upgraded and the slot position set therein are determined in step S103, so that accurate upgrade control can be achieved, and the board to be upgraded (i.e., the board to be upgraded) can only be reset and restarted by sending the instruction to the board to be upgraded.

It should be understood that the single board upgrading method of the embodiment of the present invention may be applied to a device that includes other control modules not limited to a main control single board or a single board device or is dedicated to upgrading a single board device, and in the process of upgrading a single board, the single board parameter is obtained by analyzing the patch package, the setting slot position of the single board to be upgraded corresponding to the patch package is determined, and the single board in the slot position is upgraded.

In some embodiments, upgrading a board to be upgraded includes:

if the update file in the patch package does not include an update file other than the process update file, that is, the upgrade only relates to the process file in the board to be upgraded, the board to be upgraded may not be restarted, and only the process or the virtual process group corresponding to the upgrade in the board to be upgraded is restarted to complete the upgrade, and if the update file in the patch package includes a file other than the process file, the board to be upgraded is restarted to complete the upgrade. It should be noted that the process update file referred to herein is an update file related to only a process in a board to be upgraded. The upgrade refers to upgrade in one patch package, that is, all upgrade files in one patch package are directed to upgrade process files in a board to be upgraded, and then only the corresponding process can be restarted. Similar to the restarting mode of the single board to be upgraded, the restarting of the process in the single board to be upgraded can be carried out by issuing the process restarting instruction. And in the process of restarting the process, reloading the activated related process files, wherein the process update files in the update files are loaded and activated in the process. If the upgrade not only involves the replacement of the process file (replacing the process file with the process update file), but also involves some resource files in an XML (Extensible Markup Language) format, for example, the upgrade cannot be completely realized only by restarting the process or the virtual process group, and the board to be upgraded should be restarted.

In some embodiments, restarting the process or the virtual process group corresponding to the upgrade in the board to be upgraded to complete the upgrade includes:

acquiring configuration information in the patch package;

confirming the process file name related to the upgrade according to the configuration information;

and restarting the corresponding process or virtual process group after the single board to be upgraded acquires the process file in the patch package.

In one example, a configuration file in the patch package is read, which process files specifically related to the patch package can be confirmed from the configuration file, and after the single board acquires the corresponding upgraded process file in the patch package, the processes or the virtual process group can be restarted through corresponding instructions.

In this embodiment, a virtual process group may also be restarted, and in an actual application, whether a process or a virtual process group is restarted may be flexibly selected, for example, in an example, if a plurality of processes in a certain virtual process group all need to be updated, all the virtual process groups may be directly restarted, and at this time, only an instruction for restarting the virtual process group needs to be sent, so that it is avoided that a restart instruction is sent for each process in the virtual process group that needs to be updated.

Because the analysis of the file in the patch package can not only confirm the single board to be upgraded, but also accurately identify the relevant process involved in the upgrade in some implementation processes, in these scenarios, when the upgrade only involves the process file in the single board to be upgraded, the upgrade process of the single board to be upgraded can be completed only by means of the above-mentioned process restarting or virtual process group, so that a smaller upgrade granularity is realized, and the upgrade efficiency is improved. In the process of restarting the process or the virtual process group, the process or the virtual process group which is not upgraded may still exist in the single board to be upgraded and can normally run, which is beneficial to reducing the influence in the upgrading process.

In some embodiments, before activating the obtained patch package, the method further includes:

when the current single board configuration is verified to not meet the lossless upgrading condition, prompting a user that the current single board configuration does not meet the lossless upgrading condition;

if the current single board configuration is verified to meet the lossless upgrading condition, or a continuous upgrading instruction issued by the user is received after the current single board configuration is prompted to not meet the lossless upgrading condition, the single board to be upgraded is continuously upgraded; if the instruction for continuing upgrading is not received, the single board to be upgraded is not upgraded.

It can be understood that, after receiving the prompt that the current board configuration does not satisfy the lossless upgrade condition, the user may select to issue a continuous upgrade instruction (for example, the user considers that the influence of the current upgrade on the service is within an acceptable range), and at this time, if the upgrade is continued, the conditions such as loss or interruption of the service may occur in the upgrade process; in some scenarios, the user may further select to adjust the configuration of the board after receiving a prompt that the current board configuration does not satisfy the lossless upgrade condition, adjust the board configuration to a state capable of achieving lossless upgrade, and then may perform the upgrade operation again, at this time, the verification may be passed, and a subsequent upgrade process may be started.

In some embodiments, the lossless upgrade conditions include:

the single boards to be upgraded with services have a main and standby single board relationship and/or a protection group relationship;

patching the board to be upgraded comprises the following steps:

generating an upgrade priority according to the relationship between the main and standby single boards and/or the relationship between the protection groups;

the single board to be upgraded is upgraded according to the upgrading priority from high to low, and services are executed through the single board which is not currently executing the upgrading in the upgrading process;

if the master control single board needs to be upgraded, the upgrading priority of the master control single board is the highest priority, and the upgrading priority of the standby master control single board is only second to the master control single board;

if the non-master control single board needs to be upgraded, generating upgrading priorities for the non-master control single board based on the protection group relationship, and setting at least two of the non-master control single boards with the direct protection group relationship as different upgrading priorities;

the service executed by the single board which is not currently executing the upgrade includes at least one of the following:

currently, services corresponding to a single board which is executing upgrading do not exist;

and the service corresponding to the single board which is not currently performing the upgrade and has the relationship between the main single board and the standby single board and/or the protection group.

In practical applications, whether to enable lossless upgrade mainly considers a board to be upgraded having a service currently, so in some embodiments, it is determined whether each board to be upgraded having a service may be temporarily or completely replaced, for example, a standby board exists and/or a protection group relationship exists with other boards. As can be seen, the boards to be upgraded in this embodiment may be a main control board (including a standby main control board) and a non-main control board. It should be noted that the lossless upgrade condition referred to in this embodiment is only a preset judgment condition that may implement lossless or low-loss upgrade, but in practical application, satisfying the lossless upgrade condition does not mean that lossless upgrade may be performed certainly, for example, although a protection group relationship exists in a part of boards to be upgraded, the protection group relationship only covers a part of services therein, and a part of services does not have an effective protection group relationship (i.e., a part of services cannot be replaced); or there may be unforeseen effects during the upgrade process. In other embodiments, the lossless upgrade condition may also be adjusted to other conditions according to practical situations, and is not limited to the one shown in this embodiment.

Meanwhile, in the upgrade process, the service is executed through the board which is not currently executing the upgrade, the board not executing the upgrade not only includes the board to be upgraded, but also can continue to execute the corresponding service under the condition.

If a standby single board relationship exists, for example, the main control single board and the standby main control single board are set to different upgrading priorities; if the single boards to be upgraded have a direct protection group relationship, the single boards to be upgraded are not all in the same upgrade priority. In this embodiment, the boards to be upgraded at the same upgrade priority are simultaneously subjected to upgrade operations such as reset, and after the boards to be upgraded at the current upgrade priority are all upgraded, the boards to be upgraded at the next upgrade priority are sequentially subjected to upgrade operations. By means of dividing upgrading priorities, upgrading execution can be performed in batches, and it can be understood that single boards which are not upgraded can conditionally continue to execute configured services, and influence of upgrading on services is reduced to a certain extent. Meanwhile, at least two of the single boards in the main-standby relationship or the non-main control single boards with the direct protection group relationship are set to be different upgrading priorities, so that at least a part of services or functions can be kept working all the time in the upgrading process, the influence on the services is further reduced, and lossless upgrading can be realized under the condition that the configuration of the single boards is reasonable. As an example, when the main control board and the standby main control board are upgraded, one of the main control board and the standby main control board is upgraded first (for example, the standby main control board), in the upgrading process, the main control board continues to perform the main control through the one that has not been upgraded yet, after the upgrade of the first upgraded board is completed, the upgraded board performs the main control, and the other board starts to perform the upgrade. Of course, as another example, the main control board and the standby main control board may be set to have an upgrade priority (highest upgrade priority), but the main control board and the standby main control board are specially processed in the upgrade process, and upgrade is performed according to the sequence of the previous example. It can be seen that the upgrade priorities mentioned in the present application should not be limited to the data such as software parameters configured in the implementation process, but should be considered in the order of actually performing the upgrade.

In some embodiments, upgrading the board to be upgraded further includes:

if the upgrade of the single board to be upgraded fails in the upgrade process, sending a prompt to a user;

after a prompt of failure of upgrading of the single board to be upgraded is sent to a user, when an instruction for continuing upgrading is received, patch upgrading is continued, and if the instruction for continuing upgrading is not received, the upgraded single board is returned to a state before upgrading. It should be noted that the foregoing lossless upgrade process is a process of performing upgrade after verifying that the current board configuration meets the lossless upgrade condition, and because the relationship between the active and standby boards and/or the protection group exists, a user may select whether to perform the upgrade continuously, for example, the user considers that the influence caused by the upgrade failure of the current board to be upgraded is acceptable. Certainly, the user may also choose not to continue upgrading, and if the instruction to continue upgrading is not received, the upgrading is stopped, and the upgraded board is returned to the state before upgrading, and the upgrading can be performed again after the problem that the upgrading of the board to be upgraded fails is solved.

In some embodiments, the progress of the upgrade is displayed. For example, the progress can be displayed after the instruction of the user is received, and the progress of the upgrading process and/or the expected upgrading remaining time and other information are externally presented, so that the upgrading operation is visualized, the expectation of the user on the upgrading result is improved, and the experience in the upgrading process is improved. As a more specific example, the displayed content may include, but is not limited to: the upgrade version, the upgrade start time, the upgrade end time, the residual estimated time, and the upgrade status of each batch of upgrade priority boards (waiting for upgrade, upgrade in progress, upgrade complete, upgrade success or upgrade failure, etc.).

In some embodiments, access to the new service is stopped before the upgrade for the patch package is completed. The upgrading for the patch package refers to upgrading all boards to be upgraded related to the patch package, and if the boards to be upgraded have upgrading priorities, the upgrading of the patch package is completed after all boards to be upgraded with the upgrading priorities are updated. The access of new services in the upgrading process is avoided, so that the stability of the upgrading process is ensured, and the interruption of the newly accessed services or the interruption of the original services is avoided.

In the board upgrading method provided by the embodiment of the present invention, the obtained patch package is activated, the patch package is analyzed to obtain the board parameter corresponding to the patch package, the setting slot position of the board to be upgraded corresponding to the patch package is determined according to the board parameter, and the board to be upgraded is upgraded; the effective range of the patch package is accurately identified, the upgrading operation is executed, the automation degree of the patch package upgrading is improved, and the operation work of field upgrading operators is reduced.

Furthermore, in some embodiments, the process involved in the upgrade can be identified, and only the process or the virtual process group is restarted, so that a smaller upgrade granularity is realized, the upgrade efficiency is improved, and the influence in the upgrade process is favorably reduced.

Further, in some embodiments, the upgrade can be performed in batches by dividing the upgrade priority, so that the lossless or low-loss upgrade can be realized, and the automation degree is high.

Example two:

in order to better describe the board upgrading method according to the embodiment of the present invention, a specific lossless automatic upgrading process is taken as an example in the present embodiment for further description, in the example of the present embodiment, the patch package is a cold patch package (hereinafter referred to as a cold patch), and the board device is a network element (or a network element device).

Referring to fig. 2, a directory in the network element is illustrated, and the versions installed in the network element include: a network element basic version (baseset1, baseset2) and a cold patch version (coldpatch), wherein the network element basic version is the basis for the operation of a network element system; the cold patch version is used for repairing partial functions of the network element running software version and can only take effect in a reloading mode; as shown in fig. 2, the cold patch version directory is a parallel directory with the network element base version directory, but the cold patch is dependent on the specific network element base version, and the cold patch must be matched with the network element base version for effectiveness.

Referring to fig. 3, a case of a version directory context used in a memory of a network element when a current network element activates and runs a basic version package baseset1 is illustrated, where the directory is a soft link corresponding to a hard disk directory basic version package baseset 1.

Referring to fig. 4, a file condition of a version directory used in a memory of a network element is shown when a cold patch coldpatch is activated by a current network element, where at this time, files in the directory having the same name as the cold patch directory are soft links corresponding to the cold patch coldpatch in a hard disk.

Referring to fig. 5, in the embodiment of the present invention, each slot position single board actually running in a network element is configured by a user except that the main control single board is configured by the default of the minimum version of the basic version, and unique information such as the CPU model of the physical single board actually running in each slot position can be seen from the configuration.

Referring to fig. 6, in an example of the present embodiment, a board upgrading method includes:

s201, acquiring and installing a cold patch;

referring to fig. 7, step S201 may include:

s2011, constructing a cold patch, and configuring version information corresponding to the cold patch;

the cold patch can be locally manufactured offline, and the manufacturing of the cold patch includes but is not limited to the following key information:

the network element basic version information can be used for matching the cold patch to take effect in the specified basic version;

the single board CPU model information can be used for matching the cold patch to take effect on the appointed single board;

in this embodiment, the network element cold patch may be a patch package including a plurality of single patches, or may be a single patch, where the single patches corresponding to different CPU types are different.

S2012, checking the version information of the cold patch, and if the checking is successful, executing the step S2013;

s2013, downloading and installing cold patches;

after the cold patch is manufactured locally, the cold patch is loaded in the current network element environment through network element version installation operation, and legal verification needs to be performed on the cold patch before the cold patch is loaded, and the method mainly comprises the following steps: whether the current system has a duplicate name cold patch, whether the cold patch format is legal, and the like.

The cold patch is loaded to the network element, the basic version which the cold patch depends on is not required to exist or run in the network element, theoretically, the cold patch is also a special version, but the activation of the cold patch is effective, and the basic version which the cold patch depends on is required to be in a running state.

Illustratively, after the cold patch is installed, the subsequent lossless upgrade may be triggered by an instruction, and after triggering, an automated upgrade operation may be performed.

S202, checking whether a lossless upgrading condition is met, if not, executing a step S203, and if so, executing a step S204;

in this example, the main verification content includes: the method comprises the steps of (1) upgrading a cold patch of a master control single board, and judging whether a standby master control single board which normally runs exists or not; the method relates to the cold patch upgrading of a common single board (non-master control single board), and whether the single board to be upgraded of the same CPU type has a protection group relationship or a similar protection group relationship. If a standby main control single board which normally runs exists when the cold patch of the main control single board is upgraded, and if the common single board has a protection group relationship or a similar protection group relationship when the cold patch of the common single board is upgraded, the nondestructive upgrading condition is met. If the board to be upgraded does not satisfy the above condition, the upgrade priority of the board to be upgraded belongs to the invalid priority (in some implementation processes, the invalid priority may be configured as the lowest priority by default), and it should be further noted that, in some implementation processes, the upgrade priority of the board to be upgraded that does not currently have a service may also be set as the invalid priority.

S203, popping up and prompting the current single board configuration not to meet the lossless upgrading condition to a user;

if the user confirms that the same batch of reset upgrading of the single boards to be upgraded of the invalid priority upgrading has no influence or can receive the influence, the user can also select to continue upgrading. And if receiving an upgrade continuing instruction issued by the user, continuing to perform upgrade, and executing the step S204.

S204, activating the obtained cold patch;

it is understood that cold patch activation is a separate process, and it is understood that cold patch activation is simply a hard disk version running an update of the file soft link.

It should be noted that, if the change of the cold patch modification is large, the basic version and the cold patch version may have a compatibility problem, and meanwhile, because the lossless upgrade of the cold patch in this example is performed in batches by the board to be upgraded in the network element according to the upgrade priority order, or a board which does not need to upgrade the cold patch exists, the situation that the board running the basic version and the cold patch coexist all exists, at this time, the incompatible cold patch should include a compatible list white list of the cross-version message (i.e., a list of the corresponding relationship between the cross-version message ID and the new and old message structure), and it is ensured that the board running the whole network element can perform message compatibility processing according to the compatible list white list in the upgrade process. At this time, whether the cold patch has a compatible list should be checked, and if so, the compatible list is firstly issued to each single board of the network element for each single board to perform compatible processing of a white list of the compatible list.

S205, analyzing the cold patch to obtain the CPU model of the single board corresponding to the cold patch; s206, obtaining the static configuration of the cabinet frame slot of the single board in the network element, and confirming which slot position single boards the cold patch relates to and setting slot positions;

according to the CPU model of the board and the record in the static configuration of the cabinet frame slot obtained in step S205, it can be known which slot boards and setting slots the cold patch relates to.

S207, generating an upgrading priority;

to better understand the way in which the upgrade priority is set in this example. Please refer to fig. 8, in the network element environment, the main control board and the standby main control board both operate normally at their respective positions, and the main control board is a central link for communication with the boards, and the main control board and the standby main control board should be upgraded preferentially due to the special existence of the main control board. Illustratively, a value may be set to indicate an upgrade priority. For example, the range of values 0-255, in this example, the smaller the value, the higher the upgrade priority, and the earlier the upgrade operation. In an example, the upgrade priority of the main control board may be set to 0 by default, and the upgrade of the main control board and the standby main control board is completed according to the above manner, where the range of the normal non-main control board is selected from 1 to 254, and the upgrade priority may be set to 255 by default for a board without service or a board with service but without a service protection group relationship.

In fig. 8, a service a on the board of the slot 1 and a service a on the board of the slot 5 are in a protection group relationship, a service B on the board of the slot 3 and a service B on the board of the slot 5 are in a protection group relationship, a service C on the board of the slot 3 and a service C on the board of the slot 7 are in a protection group relationship, and these three services are in a direct protection group relationship. The single boards with direct protection group relationship can not all be configured to use an upgrade priority, and if the single boards have no direct protection group relationship, the single boards can be configured to use the same upgrade priority. In practical application, considering that lots with different upgrade priorities are completely upgraded in series, in order to ensure that the upgrade is completed as early as possible, the number of configured upgrade priorities can be ensured to be the minimum.

In this example, the boards in the slot 1 and the slot 5 are not configured to have the same upgrade priority, the boards in the slot 3 and the slot 7 are not configured to have the same upgrade priority, and the boards in the slot 3 and the slot 5 are not configured to have the same upgrade priority. Therefore, when the service has such a protection group relationship, the calculated upgrade priority result may be that, when the priority of the board in slot 1 is 1, the priority of the board in slot 5 in the direct protection group relationship is 2, and since the boards in slot 3 and slot 5 are also in the direct protection group relationship, the board in slot 3 cannot be configured to be 2, and when the number of upgrade priorities configured to be as minimum as possible is 1, only the board priority in slot 7 is not configured, and since the board in slot 7 is only in the direct protection group relationship with the board in slot 3, the board priority configuration in slot 7 is 2, which meets the requirement On the veneer of slot 7, traffic A, B, C may run normally on the veneer of

slots

1, 3 without interruption. Therefore, the upgrading is sequentially carried out in batches according to the upgrading priority, and lossless upgrading is achieved.

It should be noted that, in a scenario similar to the lossless upgrade performed according to the protection group relationship or the active/standby relationship in this example, the upgrade priority is dynamically calculated according to the actual situation, and generally, static configuration is not performed in advance or the upgrade priority is written to the disk.

S208, upgrading is completed in sequence from high to low according to the upgrading priority;

referring to fig. 9, in this embodiment, when the network element runs with a service, the configuration of the upgrade priority of each board may be checked, the generation of the upgrade priority of each slot is dynamically calculated according to the protection group relationship of the service, generally does not pass through static configuration, and the upgrade priority dynamically calculated by each slot cannot be written to the disk, the upgrade priority generated by each slot based on the protection group relationship is a necessary condition for performing lossless upgrade of a cold patch, for a board without service, the default upgrade priority is default 255 configuration, but the default priority may be that a board has a service but does not have a service protection group relationship, in this case, when performing cold upgrade, when all the upgrade priorities of boards related to upgrade are not all valid, a key upgrade may prompt, if a user confirms that a lot of boards with invalid priorities have no influence or slight loss influence on upgrade, the user may also choose to continue the upgrade.

If the upgrade of the main control single board is involved, the main control single board and the standby main control single board are upgraded according to the strategy in the above S207. The other single boards to be upgraded are carried out in series in batches according to the upgrading priority, and a plurality of single boards to be upgraded in the same batch of upgrading priorities are upgraded simultaneously.

For the cold patch upgrade of the non-master board, it may also be determined whether the file in the cold patch is a file in which only process software exists (i.e., whether the update only involves a process), for example, the determination method in this example is to check whether suffixes of the cold patch file are so-type files (or file types of other process features).

If the current cold patch is a cold patch of a process, the upgrading of the cold patch of the non-master control single board may be implemented only by reloading the corresponding process, and an exemplary specific processing method may include: reading configuration files in a cold patch file, confirming a specific process file name related to the cold patch, then obtaining a slot position of a batch of single boards to be upgraded with the minimum upgrade priority, sending a process upgrade notification message to the single boards to be upgraded, wherein the message content carries a process file list required to be requested, after the single boards to be upgraded receive the notification message, the single boards to be upgraded download corresponding process files to the local through a File Transfer Protocol (FTP) or other transmission protocols, after the single boards to be upgraded are successfully downloaded, respectively responding to a main control single board, after receiving the response, the main control single board sends a specified process restart message corresponding to the single boards to be upgraded, and the single boards to be upgraded carry out process restart actions. Furthermore, if the number of processes involved in the cold patch is large, the processes logically belong to one or more virtual process groups, and at this time, after the main control board receives a response that the cold patch file of the board to be upgraded is successfully downloaded, the main control board may issue a message for restarting the virtual process group corresponding to the board to be upgraded, and does not need to send a process restart message to a plurality of processes of the same virtual process group.

It can be seen that the sequential completion of the upgrade in this step includes not only resetting the board to complete the upgrade, but also reloading only part or all processes and virtual process groups in the board to complete the upgrade. In practical application, at least a part of the steps S202 to S208 may be automatically executed, and the effective range of the cold patch may be automatically identified to execute precise control, so that the user only needs to make a decision according to the prompt and issue a simple instruction, thereby greatly simplifying the operation of field upgrade and reducing the requirement on field upgrade personnel.

When the master control board confirms that all boards to be upgraded in the current upgrade priority batch are restarted normally, the master control board starts to process the next upgrade priority batch until all the upgrade priority batches are processed. Or, when the master control board collects the process restart response messages of all boards to be upgraded in the current upgrade priority batch, and the processes are all restarted normally, the master control board does not start to process the next upgrade priority batch until the upgrade priority batch is all processed. And when the upgrading priority batch is completely processed, finishing the upgrading of the patch package.

In this example, if the upgrade of an individual board fails, at this time, because of the existence of the protection group relationship, the user may select to continue the upgrade or avoid affecting the service, and the upgrade must be completed without loss or according to the current upgrade policy, and if no instruction to continue the upgrade is received, at this time, the upgrade fallback may be triggered, and the upgrade is continued after the problem is solved. In addition, after the cold patch upgrade is started, the access of a new service is generally shielded or prohibited, otherwise, the new access service or the original service may be interrupted in the upgrade process, and the currently-performed service is preferably ensured not to be interrupted in the upgrade process.

In practical application, because the upgrading process is generally longer (dozens of minutes or longer), the display of the upgrading progress can be increased in the upgrading process, the upgrading operation is visualized, and the expectation of a user on the upgrading result is improved. The display of the upgrade is described below with an example.

In this example, a command such as "show" of the user may be provided for displaying the upgrade progress, and the upgrade progress display content includes but is not limited to: the upgrade version, the upgrade start time, the upgrade end time, the residual estimated time, and the upgrade status of each batch of upgrade priority boards (waiting for upgrade, upgrade in progress, upgrade complete, upgrade success or upgrade failure, etc.). The above contents except the residual estimated time are all real-time results of the actual stage of upgrading, and the residual estimated time is an estimated time.

Referring to fig. 10, the actual operation process of the remaining estimated time algorithm is schematically illustrated, the upgrading process is divided into several key stages, and each stage is configured with an estimated time by default. Specifically, for a plurality of boards with the same batch of upgraded priority, the batch of boards with the largest estimated time value can be taken, so that after the upgrading process is subdivided, the overall residual estimated time has the reference estimated time: the estimated time consumption of each stage and the estimated time consumption of each batch of upgrading priority upgrading are related to the upgrading. However, the experience value may be different in different service models or scenes, in order to be more accurate, a learning and adjusting process of network element upgrade time consumption may be introduced, in the actual upgrade process, actual time consumption is calculated after each stage is upgraded, the actual time consumption is compared with the estimated time consumption in the current stage (the estimated time consumption is more than the actual time consumption, an offset value is subtracted from the estimated overall time consumption displayed to the outside, otherwise, the offset value is added), the overall residual estimated time displayed to the outside may be dynamically adjusted, meanwhile, the actual time consumption for each stage is written into the database, and in the next upgrade, the estimated time consumption in the database is preferentially read as an estimation reference (the estimated time consumption does not exist in the database for the first time or only is recorded in the database, and at this time, the estimated time consumption time configured by default in each stage can only be used), so that the residual estimated time is more accurate.

As a specific example, the current upgrade process indicates that there are 6 stages, each stage having a default configuration of estimated elapsed time, the cumulative value of the estimated time spent in the 6 stages is equal to 78min (minutes), which is used as the initial time for displaying the residual estimated time when the upgrade is started, when the actual upgrade of the first stage is completed, the actual time consumption is 12min, because the residual estimated time displayed externally is decreased in real time in the upgrade process, so at the actual upgrade completion of this stage, the estimated time remaining is shown to be 78-12 to 66min, but the estimated time spent at this stage is 15min, therefore, after the upgrade of the stage is completed, the next stage is started, the deviation value needs to be compensated (added or subtracted) for the externally presented residual estimated time, because the estimated time consumption of the stage is greater than the actual time consumption, the residual estimated time needs to be subtracted by the offset 66-3 of the estimated time spent at this stage, which is 63 min. At this time, the display of the remaining estimated time is directly jumped from 66min to 63min without a time decreasing process.

Similarly, the estimated residual time 63min after the second stage starts to be corrected in the first stage is taken as a reference, and it can be seen by way of example that the estimated residual time in the second stage is less than the actual consumed time, and the deviation value is 5min, but since the display of the external time is decreased in real time, the estimated residual time is decreased to 63-25 to 38min just after the second stage ends, but after the compensation of the deviation of the estimated consumed time in this stage is performed after the second stage ends, the estimated residual time jumps, and the estimated residual time displayed by the external adjustment is 38+5 to 43 min.

And the rest stages are analogized in sequence, and after the upgrade is finished, the residual estimated time is adjusted to 0min, which indicates that the current upgrade is finished.

Referring to fig. 11, a display example of the upgrade progress increased in the upgrade process is schematically illustrated, which enables visualization of the upgrade operation, improves the psychological expectation of the user on the upgrade result, and by providing a command (such as "show" command in the foregoing example) for displaying the upgrade progress to the user, the upgrade progress display content includes but is not limited to: the upgrade version, the upgrade start time, the upgrade end time, the residual estimated time, and the upgrade status of each batch of upgrade priority boards (waiting for upgrade, upgrade in progress, upgrade complete, upgrade success or upgrade failure, etc.).

Fig. 11 shows a state when the Upgrade is just started, the current Upgrade end time is not yet known and is not displayed, the boards to be started to perform the cold patch Upgrade are displayed in a row according to the Upgrade priority, the Upgrade state of the priority batch in which the Upgrade is started is displayed as Upgrade (in the Upgrade), and the Upgrade state of the priority batch in which the Upgrade is not started is displayed as Wait-Upgrade (waiting for Upgrade). Meanwhile, the upgrade priority of the main control single board is the highest, and the upgrade priorities of the non-main control single boards are all started from 1.

Meanwhile, it should be noted that the upgrade status displayed in the cold patch upgrade process is only the upgrade status of the board related to the cold patch upgrade, and if the cold patch package does not relate to the upgraded board, the upgrade status is not displayed in the cold patch upgrade status.

As shown in fig. 12, the state during the upgrade is shown, the board currently Upgraded with the cold patch is displayed according to the upgrade priority, the upgrade state of the Upgraded priority batch (Status column) is shown as updated, the upgrade state of the Upgrading priority batch is shown as updated, and the remaining estimated time is adjusted in a real-time descending manner. For the cold patch upgrade of a common single board, a plurality of single boards with the same upgrade priority in the same batch are upgraded simultaneously, and the upgrade progress of the single boards in the batch is displayed as Upgrading. Meanwhile, the cold patch upgrading process displays the upgrading state of the finished upgrading, including the individual upgrading state of each single board of the batch of upgrading priorities. For example: the upgrade priority of the main control board (the priority column) is 0, the main control board has a main slot (the main control board and the standby main control board), the upgrade results are ALL successful, the Success column of Success shows ALL indicating that ALL upgrade succeeds, the board with the upgrade priority of 1 includes boards of 1 and 3 slots, and the priority of the batch is upgraded, but the upgrade results of the boards of the batch may not be completely the same, thus respectively showing that the upgrade of 1 slot succeeds and the upgrade of 3 slots fails. If the upgrade of individual single board fails, the user can select to continue the upgrade or avoid influencing the service to stop the upgrade because of the relation of the protection group, if the upgrade is not continued, the upgrade rollback can be triggered, and the lossless or micro-loss upgrade is continued after the problem is solved.

As shown in fig. 13, the state when the upgrade is finished is shown, the time of the upgrade finish is normally displayed at the current upgrade finish time, and the estimated remaining time of the upgrade is also adjusted to 0min in real time in a descending manner. At this time, the upgrade status of the cold patch is all displayed as Upgraded, but the upgrade result is separately displayed in two columns of Success and Fail, and if the individual board fails to be Upgraded, the problem can be separately confirmed and then the individual board can be recovered separately for the board that fails to be Upgraded.

Example three:

the present embodiment provides a single board device, as shown in fig. 14, which includes a processor 141, a memory 142, and a communication bus 143, where:

the communication bus 143 is used for realizing connection communication between the processor 141 and the memory 142;

processor 141 is configured to execute one or more computer programs stored in memory 142 to implement at least one step of the single board upgrade method in the first and second embodiments.

The present embodiments also provide a computer-readable storage medium including volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media include, but are not limited to, RAM (random Access memory), ROM (Read-Only memory), EEPROM (electrically erasable programmable Read-Only memory), flash memory or other memory technology, CD-ROM (compact disk Read-Only memory), DVD (Digital versatile disk) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

The computer-readable storage medium in this embodiment may be used to store one or more computer programs, and the stored one or more computer programs may be executed by the processor to implement at least one step of the single board upgrading method in the first embodiment and the second embodiment.

It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.

In addition, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to one of ordinary skill in the art. Thus, the present invention is not limited to any specific combination of hardware and software.

The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.

Claims

1. A single board upgrading method includes:

activating the obtained patch package;

2. The board upgrading method according to claim 1, wherein the upgrading the board to be upgraded according to the set slot includes:

if the update file in the patch package does not include an update file other than the process update file, the single board to be upgraded is not restarted, so that the process or the virtual process group corresponding to the upgrade in the single board to be upgraded is restarted to complete the upgrade; and if the update files in the patch package comprise update files except the process update files, resetting and restarting the single board to be upgraded to finish upgrading.

3. The board upgrade method according to claim 2, wherein the restarting the process or the virtual process group corresponding to the upgrade in the board to be upgraded to complete the upgrade includes:

acquiring configuration information in the patch package;

4. The board upgrade method according to claim 1, wherein before activating the obtained patch package, the method further includes:

if the current single board configuration is verified to meet the lossless upgrading condition, or a continuous upgrading instruction issued by the user is received after the current single board configuration is prompted to meet the lossless upgrading condition, continuously upgrading the single board to be upgraded; if the instruction for continuing upgrading is not received, the single board to be upgraded is not upgraded.

5. The board upgrade method according to claim 4, wherein the lossless upgrade condition includes:

the upgrading the board to be upgraded comprises the following steps:

generating an upgrade priority according to the main and standby veneer relation and/or the protection group relation;

sequentially upgrading the single board to be upgraded according to the upgrading priority from high to low, and executing services through the single board which is not currently executing upgrading in the upgrading process;

if the master control single board needs to be upgraded, the upgrade priority of the standby master control single board is the highest priority, and the upgrade priority of the master control single board is only next to that of the standby master control single board;

the service corresponding to the veneer which is not currently executing upgrading is obtained;

and the service corresponding to the single board which is not currently performing the upgrade and has the relationship between the main single board and the standby single board and/or the protection group relationship with the single board performing the upgrade.

6. The board upgrading method according to claim 5, wherein the upgrading the board to be upgraded further includes:

if the upgrading of the single board to be upgraded fails in the process of lossless upgrading, a prompt is sent to a user;

after a prompt of failure of upgrading of the single board to be upgraded is sent to a user, when an instruction for continuing upgrading is received, patch upgrading is continued, and if the instruction for continuing upgrading is not received, the upgraded single board is returned to a state before upgrading.

7. The board upgrading method according to any of claims 1-6, further comprising:

and displaying the progress of upgrading.

8. The board upgrading method according to any of claims 1-6, further comprising:

and stopping the access of the new service before finishing the upgrading aiming at the patch package.

9. A single board device comprises a processor, a memory and a communication bus;

the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the single board upgrade method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores one or more computer programs which are executable by one or more processors to implement the steps of the single board upgrade method according to any one of claims 1 to 8.