CN108469960A - A kind of method for edition management and device - Google Patents
A kind of method for edition management and device Download PDFInfo
- Publication number
- CN108469960A CN108469960A CN201710631648.2A CN201710631648A CN108469960A CN 108469960 A CN108469960 A CN 108469960A CN 201710631648 A CN201710631648 A CN 201710631648A CN 108469960 A CN108469960 A CN 108469960A
- Authority
- CN
- China
- Prior art keywords
- version
- upgrading
- mode
- target
- current
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
A kind of method for edition management of the application offer and device, this method include：Compare the current version and target version for delivering part according to version number；If target version is higher than current version, then by the version number of current version respectively with support increment be upgraded to target version minimal version No. the first and supports it is compatible restart be upgraded to minimal version No. the second of target version and be compared, the upgrading mode of target version is upgraded to from current version according to comparison result determination delivery part；If target version is less than current version, the version number of target version is then supported with current version to the third minimal version number that is degraded to of increment respectively and current version supports is compatible restarts minimal version No. the 4th being degraded to and be compared, is downgraded to the degraded mode of target version from current version according to comparison result determination delivery part.Pass through the technical solution of the application, it is ensured that accuracy that upgrading mode selects, reasonability may be used correct upgrading mode and upgrade to stack equipment.
Description
Technical field
This application involves field of communication technology more particularly to a kind of method for edition management and device.
Background technology
IRF (Intelligent Resilient Framework, intelligent elastic framework) stack equipment can be referred to as heap
Stacking device, the logical device being made up of IRF agreements more physical equipments, each physical equipment in the stack equipment
It is properly termed as member device.Wherein, stack equipment usually support ISSU (In-Service Software Upgrade, not in
Disconnected upgrading service) and ISSD (In-Service Software Degrade, non-interrupting service degrade), i.e., in non-interrupting service
In the case of, complete upgrading or the degradation of stack equipment.
By taking escalation process as an example, then upgrades mode and include increment upgrading, compatible restart upgrading, incompatible restart upgrading.Its
In, increment upgrading refers to：In escalation process, impacted process is only restarted, but all member devices of stack equipment are located
In normal operating conditions, it is ensured that customer service is not interrupted.Compatibility restarts upgrading and refers to：In escalation process, restart successively
Member device, after some member device is restarted, the edition compatibility between the member device and the member device that do not restart can be with
Ensure that customer service is not interrupted.It is incompatible to restart upgrading and refer to：In escalation process, restart member device successively, some at
After member's equipment is restarted, the incompatible version between the member device and the member device that do not restart can not ensure customer service not
It interrupts.
Due to upgrading mode include increment upgrading, it is compatible restart upgrading, it is incompatible restart upgrading, therefore, it is necessary to from these
Suitable upgrading mode is selected in upgrading mode, still, in conventional manner, unsuitable upgrading mode selection strategy,
Lead to not carry out upgrading processing using suitable upgrading mode.Similarly, also cause without suitable degraded mode selection strategy
Can not degradation processing be carried out using suitable degraded mode.
Invention content
The application provides a kind of method for edition management, is applied to stack equipment, the method includes：
Compare the current version and target version for delivering part according to version number；
If target version is higher than current version, the version number of current version is upgraded to target version with increment is supported respectively
This minimal version No. the first and support it is compatible restart be upgraded to minimal version No. the second of target version and be compared, according to than
Relatively result determines the upgrading mode that part is upgraded to target version from current version of delivering；
If target version is less than current version, increment is supported to degrade with current version respectively the version number of target version
Third minimal version number extremely and current version support it is compatible restart minimal version No. the 4th being degraded to and be compared, according to than
Relatively result, which determines, delivers the degraded mode that part is downgraded to target version from current version.
The application provides a kind of edition management device, is applied to stack equipment, and described device includes：
Comparison module, for comparing the current version and target version of delivering part according to version number；
Updating and management module is used for when the target version is higher than the current version, then by the version of current version
Number respectively with support increment be upgraded to target version minimal version No. the first and support it is compatible restart be upgraded to target version
Minimal version No. second is compared, and is determined according to comparison result and delivered the upgrading that part is upgraded to target version from current version
Mode；
Degradation management module is used for when the target version is less than the current version, then by the version of target version
Supported number respectively with current version third minimal version number that increment is degraded to and current version support it is compatible restart be degraded to
Minimal version No. 4th is compared, and is determined according to comparison result and delivered the degradation that part is downgraded to target version from current version
Mode.
Based on the above-mentioned technical proposal, in the embodiment of the present application, suitable upgrading mode can be selected, and use the upgrading side
Formula carries out upgrading processing, it is ensured that accuracy that upgrading mode selects, reasonability, so as to using correctly upgrading mode
Carry out upgrading processing.Suitable degraded mode can be selected, and degradation processing is carried out using the degraded mode, it is ensured that is degraded
Accuracy that mode selects, reasonability, so as to carry out upgrading processing using correct degraded mode.Above-mentioned upgrading/degradation
Mode ensures that business is not interrupted as far as possible.
Description of the drawings
It, below will be to the application in order to clearly illustrate the embodiment of the present application or technical solution in the prior art
Embodiment or attached drawing needed to be used in the description of the prior art are briefly described, it should be apparent that, in being described below
Attached drawing is only some embodiments described in the application, for those of ordinary skill in the art, can also be according to this Shen
Please these attached drawings of embodiment obtain other attached drawings.
Fig. 1 is the flow chart of the method for edition management in a kind of embodiment of the application；
Fig. 2 is the structure chart of the edition management device in a kind of embodiment of the application；
Fig. 3 is the hardware structure diagram of the stack equipment in a kind of embodiment of the application.
Specific implementation mode
In the term that the embodiment of the present application uses merely for the sake of the purpose of description specific embodiment, and this unrestricted Shen
Please.The "an" of singulative used in the application and claims, " described " and "the" are also intended to including most shapes
Formula, unless context clearly shows that other meanings.It is also understood that term "and/or" used herein refers to including one
A or multiple associated list items purposes any or all may combine.
It will be appreciated that though various letters may be described using term first, second, third, etc. in the embodiment of the present application
Breath, but these information should not necessarily be limited by these terms.These terms are only used for same type of information being distinguished from each other out.For example,
In the case where not departing from the application range, the first information can also be referred to as the second information, and similarly, the second information can also
It is referred to as the first information.Depending on context, in addition, used word " if " can be construed to " ... when " or
" when ... " or " in response to determination ".
The embodiment of the present application proposes a kind of method for edition management, and this method can be applied to stack equipment, and (such as IRF stackings are set
It is standby), the method for edition management for realizing software version file upgrading/degradation.In escalation process, upgrading mode can wrap
It includes：Increment upgrading compatible restart upgrading, incompatible restarts upgrading.In demotion processes, degraded mode may include：Increment drops
Grade compatible restart degradation, incompatible restarts degradation.
In one example, above-mentioned software version file may include at least one delivery part, and the software version file
In delivery part can include but is not limited to kernel module (ko), User space finger daemon (daemon), User space library file
(library), one or more of User space plug-in unit (plugin).
In one example, in order to realize upgrading/degradation to software version file, then software version text can be first determined
Each of part delivers upgrading mode/degraded mode of part, it is then possible in the way of the upgrading for each delivering part/degradation side
Formula determines upgrading mode/degraded mode of software version file, it is then possible in the way of the upgrading of software version file/drop
Grade mode carries out software version file to upgrade/degradation processing.
In one example, each version for delivering part is corresponding with edition compatibility data, and edition compatibility data can wrap
It includes but is not limited to：The version number C of current version supports increment to be upgraded to the first minimal version U1 of current version, supports simultaneous
Unit weight opens the second minimal version U2 for being upgraded to current version, and current version supports the third minimal version number that increment is degraded to
D1, current version support compatibility to restart the 4th minimal version D2 being degraded to.Based on above-mentioned edition compatibility data, it may be determined that
Go out to deliver upgrading mode/degraded mode of part.
It is shown in Figure 1, for the flow chart of the method for edition management of delivery part, the liter that this method is used to determine to deliver part
Grade mode/degraded mode, and this method can be applied to stack equipment, the method includes：
Step 101, the current version and target version for delivering part are compared according to version number.Wherein, if target version is higher than
Current version then illustrates to need to carry out upgrading processing to delivering part, and executes step 102；If target version is less than current version,
Then illustrate to need to carry out degradation processing to delivering part, and executes step 103.
In one example, since each version for delivering part can be corresponding with edition compatibility data, it can obtain
Get the edition compatibility data of current version and the edition compatibility data of target version.
It may include the version number C of current version in the edition compatibility data of current version, support increment is upgraded to work as
First minimal version U1 of preceding version supports compatibility to restart the second minimal version U2 for being upgraded to current version, current version
The third minimal version D1 that this support increment is degraded to, current version support compatibility to restart minimal version No. the 4th being degraded to
D2.It may include the version number C of target version in addition, in the edition compatibility data of target version, increment supported to be upgraded to mesh
The first minimal version U1 of version is marked, compatibility is supported to restart the second minimal version U2 for being upgraded to target version, target version
The third minimal version D1 that this support increment is degraded to, target version support compatibility to restart minimal version No. the 4th being degraded to
D2。
In one example, after getting above-mentioned edition compatibility data, if the version number C of current version is less than target
The version number C of version then illustrates that target version is higher than current version, needs to carry out upgrading processing to delivering part, and execute step
102.If the version number C of current version is more than the version number C of target version, illustrates that target version is less than current version, need
Degradation processing is carried out to delivering part, and executes step 103.
In one example, may include edition compatibility data in software version file, therefore, stack equipment can be from soft
Above-mentioned edition compatibility data are got in part version file, this acquisition process is not limited.Moreover, because software version file
It can be made of multiple delivery parts, therefore, in order to distinguish the different edition compatibility data for delivering part, then be wrapped in software version file
What is included is the correspondence for delivering part mark and edition compatibility data, is based on this, and stack equipment can be looked by delivering part mark
Ask corresponding edition compatibility data.
Step 102, the version number C of current version is upgraded to the first minimal version of target version with increment is supported respectively
Number U1 and support it is compatible restart be upgraded to the second minimal version U2 of target version and be compared, and determined according to comparison result
The delivery part is upgraded to the upgrading mode of target version from current version.
In one example, for " determining that the delivery part is upgraded to target version from current version according to comparison result
The process of upgrading mode ", can include but is not limited to：If the version number C of current version is more than or equal to target version corresponding the
One minimal version U1 can then determine that deliver part is upgraded to the upgrading mode of target version as increment upgrading from current version；
Alternatively, if the version number C of current version is less than the corresponding first minimal version U1 of target version, and the version number of current version
C is more than or equal to the corresponding second minimal version U2 of target version, then can determine that deliver part is upgraded to target from current version
The upgrading mode of version is that compatibility restarts upgrading；Alternatively, if the version number C of current version is less than target version corresponding first most
The version number C of minor release/point release U1, current version are less than the corresponding second minimal version U2 of target version, then can determine delivery
Part is upgraded to the upgrading mode of target version from current version and restarts upgrading to be incompatible.
For example, the process of the above-mentioned determining upgrading mode for delivering part, can be achieved by the steps of：
Step 1 judges whether the version number C of current version is more than or equal to the corresponding minimal version No. first of target version
U1.If it is, step 2 can be executed；If it is not, then step 3 can be executed.
Step 2 determines that be upgraded to the upgrading mode of target version from current version upgrades for increment.
Step 3 judges whether the version number C of current version is more than or equal to the corresponding minimal version No. second of target version
U2.If it is, step 4 can be executed；If it is not, then step 5 can be executed.
Step 4 determines that the upgrading mode that target version is upgraded to from current version is that compatibility restarts upgrading.
Step 5 determines that be upgraded to the upgrading mode of target version from current version restarts upgrading to be incompatible.
Step 103, the version number C of target version is supported with current version to the third minimal version that increment is degraded to respectively
Number D1 and current version support it is compatible restart the 4th minimal version D2 being degraded to and be compared, and determined according to comparison result
The delivery part is downgraded to the degraded mode of target version from current version.
In one example, for " determining that the delivery part is downgraded to target version from current version according to comparison result
The process of degraded mode ", can include but is not limited to：If the version number C of target version is more than or equal to current version corresponding the
Three minimal version D1 can then determine that deliver part is downgraded to the degraded mode of target version as increment degradation from current version；
Alternatively, if the version number C of target version is less than the corresponding third minimal version D1 of current version, and the version number of target version
C is more than or equal to the corresponding 4th minimal version D2 of current version, then can determine that deliver part is downgraded to target from current version
The degraded mode of version is that compatibility restarts degradation；Alternatively, if the version number C of target version is less than the corresponding third of current version most
The version number C of minor release/point release D1, target version are less than the corresponding 4th minimal version D2 of current version, then can determine delivery
Part is downgraded to the degraded mode of target version from current version and restarts degradation to be incompatible.
For example, the process of the above-mentioned determining degraded mode for delivering part, can be achieved by the steps of：
Step 1 judges whether the version number C of target version is more than or equal to the corresponding third minimal version number of current version
D1.If it is, step 2 can be executed；If it is not, then step 3 can be executed.
Step 2 determines that be downgraded to the degraded mode of target version from current version degrades for increment.
Step 3 judges whether the version number C of target version is more than or equal to the corresponding minimal version No. 4th of current version
D2.If it is, step 4 can be executed；If it is not, then step 5 can be executed.
Step 4 determines that the degraded mode that target version is downgraded to from current version is that compatibility restarts degradation.
Step 5 determines that be downgraded to the degraded mode of target version from current version restarts degradation to be incompatible.
In one example, in the upgrading side for being upgraded to target version from current version according to comparison result determination delivery part
After formula, it is also based on the upgrading mode that each upgrading mode for delivering part determines software version file, and according to described soft
The upgrading mode of part version file carries out upgrading processing to the software version file.
In one example, for " the upgrading mode for determining software version file based on each upgrading mode for delivering part "
Process, can include but is not limited to such as under type：Restart upgrading if having and delivering the upgrading mode of part to be incompatible, it can be true
The upgrading mode of the fixed software version file restarts upgrading to be incompatible；Alternatively, if the upgrading mode for not delivering part is not simultaneous
Unit weight opens upgrading, but it is that compatibility restarts upgrading to have the upgrading mode of delivery part, then can determine the liter of the software version file
Grade mode is that compatibility restarts upgrading；Alternatively, if do not deliver the upgrading mode of part restarts upgrading, and no delivery part to be incompatible
Upgrading mode be compatibility restart upgrading, then can determine the upgrading mode of the software version file for increment upgrading.
For example, it is assumed that software version file may include delivering part 1, delivering part 2, deliver part 3, if delivering the upgrading of part 1
Mode is increment upgrading, and the upgrading mode for delivering part 2 is that compatibility restarts upgrading, delivers the upgrading mode of part 3 and restarts to be incompatible
Upgrading, then can determine the upgrading mode of software version file be it is incompatible restart upgrading, and liter can be restarted by incompatible
The mode of grade will deliver part 1, delivery part 2, delivery part 3 and be upgraded to target version from current version.If delivering the upgrading mode of part 1
Upgrade for increment, the upgrading mode for delivering part 2 is that compatibility restarts upgrading, and the upgrading mode for delivering part 3 is that compatibility restarts upgrading, then
It can determine that the upgrading mode of software version file is that compatibility restarts upgrading, and can will be handed in such a way that compatibility restarts upgrading
It pays part 1, delivery part 2, delivery part 3 and is upgraded to target version from current version.If delivering the upgrading mode of part 1 for increment to upgrade,
It delivers the upgrading mode of part 2 for increment to upgrade, delivers the upgrading mode of part 3 and upgrade for increment, then can determine software version text
The upgrading mode of part is increment upgrading, and can will deliver part 1 in such a way that increment upgrades upgrading, and deliver part 2, deliver part 3
It is upgraded to target version from current version.
In one example, in the degradation side for being downgraded to target version from current version according to comparison result determination delivery part
After formula, it is also based on the degraded mode that each degraded mode for delivering part determines software version file, and according to described soft
The degraded mode of part version file carries out degradation processing to the software version file.
In one example, for " degraded mode for determining software version file based on each degraded mode for delivering part "
Process, can include but is not limited to such as under type：Restart degradation if having and delivering the degraded mode of part to be incompatible, it can be true
The degraded mode of the fixed software version file restarts degradation to be incompatible；Alternatively, if the degraded mode for not delivering part is not simultaneous
Unit weight opens degradation, but it is that compatibility restarts degradation to have the degraded mode of delivery part, then can determine the drop of the software version file
Grade mode is that compatibility restarts degradation；Alternatively, if do not deliver the degraded mode of part restarts degradation, and no delivery part to be incompatible
Degraded mode be compatibility restart degradations, then can determine the degraded mode of the software version file for increment degradation.
For example, it is assumed that software version file may include delivering part 1, delivering part 2, deliver part 3, if delivering the degradation of part 1
Mode is increment degradation, and the degraded mode for delivering part 2 is that compatibility restarts degradation, delivers the degraded mode of part 3 and restarts to be incompatible
Degrade, then can determine the degraded mode of software version file be it is incompatible restart degradation, and drop can be restarted by incompatible
The mode of grade will deliver part 1, delivery part 2, delivery part 3 and be downgraded to target version from current version.If delivering the degraded mode of part 1
Degrade for increment, the degraded mode for delivering part 2 is that compatibility restarts degradation, and the degraded mode for delivering part 3 is that compatibility restarts degradation, then
It can determine that the degraded mode of software version file is that compatibility restarts degradation, and can will be handed in such a way that compatibility restarts degradation
It pays part 1, delivery part 2, delivery part 3 and is downgraded to target version from current version.If delivering the degraded mode of part 1 for increment to degrade,
It delivers the degraded mode of part 2 for increment to degrade, delivers the degraded mode of part 3 and degrade for increment, then can determine software version text
The degraded mode of part is that increment degrades, and can will deliver part 1 by way of increment degradation, and deliver part 2, deliver part 3 from working as
Preceding version is downgraded to target version.
Based on the above-mentioned technical proposal, in the embodiment of the present application, suitable upgrading mode can be selected, and use the upgrading side
Formula carries out upgrading processing, it is ensured that accuracy that upgrading mode selects, reasonability, so as to using correctly upgrading mode
Carry out upgrading processing.Suitable degraded mode can be selected, and degradation processing is carried out using the degraded mode, it is ensured that is degraded
Accuracy that mode selects, reasonability, so as to carry out upgrading processing using correct degraded mode.Above-mentioned upgrading/degradation
Mode ensures that business is not interrupted as far as possible.
In one example, edition compatibility data can also include that isolation version list I, isolation version list I include
The version number for forbidding being degraded to from current version.Based on this, support to increase with current version respectively by the version number of target version
It measures the third minimal version number being degraded to and current version supports compatibility to restart minimal version No. the 4th being degraded to and be compared
Before, the isolation version list of current version can also be obtained, which includes forbidding being degraded to from current version
Version number；Then, if the version number of target version is located in the isolation version list, then it represents that target version is current version
This isolation version, then part will be delivered by forbidding is downgraded to target version from current version；If the version number of target version is not located at
It is isolated in version list, then executes and support the third that increment is degraded to minimum with current version respectively the version number of target version
Version number and current version support compatibility to restart the process that minimal version No. the 4th being degraded to is compared.
Wherein, for all delivery parts, if having any one deliver part definitive result be：Forbid delivering part from current
Version is downgraded to target version, then final to need to forbid degrading to software version file.
Below in conjunction with concrete application scene, the above-mentioned technical proposal of the embodiment of the present application is illustrated.
For example, initial version is version 1, edition compatibility data are as shown in table 1, C 100, without compatible version.Second
The version of publication is version 2, and edition compatibility data are as shown in table 2, C 200, U1 and U2 is 100, D1 and D2 is 100.The
The version issued three times is version 3, and edition compatibility data are as shown in table 3, C 300, U1 200, U2 100, D1 200, D2
It is 100.The version of 4th publication is edition 4, and edition compatibility data are as shown in table 4, C 400, U1 300, U2 200, D1
For 300, D2 200.The version of 5th publication is version 5, and edition compatibility data are as shown in table 5, C 500, U1 300, U2
For 200, D1 400, D2 400.
Wherein, when first version is version 1, and the second edition is version 2,1 increment of version is upgraded to version 2；When
One version is version 1, when the second edition is version 3, the compatibility of version 1 is restarted and is upgraded to version 3；When first version be version 1,
The second edition be edition 4 when, by version 1 it is incompatible restart be upgraded to edition 4, i.e. edition 4 and version 1 is incompatible；Work as the first edition
This be version 1, the second edition be version 5 when, by version 1 it is incompatible restart be upgraded to version 5, i.e. version 5 and version 1 be not simultaneous
Hold.
Restart since version 1 is incompatible when being upgraded to edition 4/version 5, flow interrupt can be caused, it therefore, can be by version
2/ version 3 is as transition version, to avoid flow interrupt.Specifically, 1 increment of version is first upgraded to version 2, then by version 2
Compatibility, which is restarted, is upgraded to edition 4, is upgraded to version 3 alternatively, first restarting the compatibility of version 1, then version 3 increment is upgraded to version
4, this way it is possible to avoid version 1 it is incompatible restart be upgraded to edition 4.In addition, being upgraded to the process class of version 5 for version 1
Seemingly, it repeats no more.Obviously, aforesaid way can support transition version, and compatible bridge is provided between version incompatible.
As can be seen from Table 5, version 3 can be upgraded to version 5 with increment, and version 2, which can be compatible with to restart, is upgraded to version 5,
But version 5 can only increment be downgraded to edition 4, and can not increment be downgraded to version 2, also can not increment be downgraded to version 3, because
This, aforesaid way can support asymmetric promotion and demotion.
Table 1
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 |
Table 2
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 |
Table 3
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 300 | 100 | 300 | 100 |
Table 4
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 200 | 100 | 200 | 100 | |
| 400 | 300 | 200 | 300 | 200 |
Table 5
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 200 | 100 | 200 | 100 | |
| 400 | 300 | 200 | 300 | 200 | |
| 500 | 300 | 200 | 400 | 400 |
Further, it is assumed that the version of the 6th publication is version 6, and edition compatibility data are as shown in table 6, C 600, U1
For 300, U2 200, D1 400, D2 400.Assuming that version 6 is problem version, need to isolate from subsequent version,
It can only be upgraded to normal version from version 6, it can however not being downgraded to version 6, then in released version 7, version from normal version
This compatible data is as shown in table 7, C 700, U1 300, U2 200, D1 400, D2 400, and it is 600 that version, which is isolated,.
Obviously, it is based on isolation version 600 so that version 6 can be upgraded to version 7, but cannot be downgraded to version from version 7
This 6, that is to say, that aforesaid way can support the isolation processing to problem version.
Table 6
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 200 | 100 | 200 | 100 | |
| 400 | 300 | 200 | 300 | 200 | |
| 500 | 300 | 200 | 400 | 400 | |
| 600 | 300 | 200 | 400 | 400 |
Table 7
Further, it is assumed that the version of the 8th publication is version 8, and edition compatibility data are as shown in table 8, C 800, U1
For 500, U2 300, D1 500, D2 400, isolation version is 600.Assuming that the version of the 9th publication is version 9, version
Compatible data is as shown in table 9, C 900, U1 700, U2 700, D1 700, D2 700, and isolation version is 600.
Table 8
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 200 | 100 | 200 | 100 | |
| 400 | 300 | 200 | 300 | 200 | |
| 500 | 300 | 200 | 400 | 400 | |
| 600 | 300 | 200 | 400 | 400 | |
| 700 | 300 | 200 | 400 | 400 | 600 |
| 800 | 500 | 300 | 500 | 400 | 600 |
Table 9
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 200 | 100 | 200 | 100 | |
| 400 | 300 | 200 | 300 | 200 | |
| 500 | 300 | 200 | 400 | 400 | |
| 600 | 300 | 200 | 400 | 400 | |
| 700 | 300 | 200 | 400 | 400 | 600 |
| 800 | 500 | 300 | 500 | 400 | 600 |
| 900 | 700 | 700 | 700 | 700 | 600 |
Further, it is assumed that the version of the tenth publication is version 11, and edition compatibility data are as shown in table 10, C 1100,
U1 is 1000, U2 1000, D1 1000, D2 1000, and isolation version is 600.Version 11 and the version of front 9 be not simultaneous
Hold, i.e., version 11 is version incompatible, but has reserved compatibility condition.If necessary by the edition upgrading in version 1- versions 9
To version 11, then the version 10 that can be 1000 with released version number, and by version 10, by the version liter in version 1- versions 9
Grade arrives version 11.
Table 10
| Version number (C) | Minimal version number (U1) | Minimal version number (U2) | Minimal version number (D1) | Minimal version number (D2) | Version list (I) is isolated |
| 100 | |||||
| 200 | 100 | 100 | 100 | 100 | |
| 300 | 200 | 100 | 200 | 100 | |
| 400 | 300 | 200 | 300 | 200 | |
| 500 | 300 | 200 | 400 | 400 | |
| 600 | 300 | 200 | 400 | 400 | |
| 700 | 300 | 200 | 400 | 400 | 600 |
| 800 | 500 | 300 | 500 | 400 | 600 |
| 900 | 700 | 700 | 700 | 700 | 600 |
| 1100 | 1000 | 1000 | 1000 | 1000 | 600 |
As shown in Fig. 2, for the structure chart of the edition management device proposed in the embodiment of the present application, the edition management device
Stack equipment is can be applied to, and the edition management device may include：
Comparison module 201, for comparing the current version and target version of delivering part according to version number；
Updating and management module 202 is used for when the target version is higher than the current version, then by the version of current version
This number respectively with support increment be upgraded to target version minimal version No. the first and support it is compatible restart be upgraded to target version
Minimal version No. the second be compared, and the liter delivered part and be upgraded to from current version target version is determined according to comparison result
Grade mode；
Degradation management module 203 is used for when the target version is less than the current version, then by the version of target version
This number supported respectively with current version the third minimal version number that is degraded to of increment and current version support it is compatible restart be degraded to
Minimal version No. the 4th be compared, and the drop delivered part and be downgraded to from current version target version is determined according to comparison result
Grade mode.
The updating and management module 202, specifically for determining that deliver part is upgraded to from current version according to comparison result
During the upgrading mode of target version, if the version number of the current version is more than or equal to the minimal version No. first,
Determine that deliver part is upgraded to the upgrading mode of target version as increment upgrading from current version；If alternatively, the current version
Version number is less than the minimal version No. first, and the version number of the current version is more than or equal to the minimal version No. second,
Determine that it is that compatibility restarts upgrading to deliver part to be upgraded to the upgrading mode of target version from current version；If alternatively, the current version
This version number is less than the minimal version No. second, determines the upgrading mode that part is upgraded to target version from current version of delivering
Restart upgrading to be incompatible.
The degradation management module 203, specifically for determining that deliver part is downgraded to from current version according to comparison result
During the degraded mode of target version, if the version number of the target version is more than or equal to the third minimal version number,
Determine that deliver part is downgraded to the degraded mode of target version as increment degradation from current version；If alternatively, the target version
Version number is less than the third minimal version number, and the version number of the target version is more than or equal to the minimal version No. the 4th,
Determine that it is that compatibility restarts degradation to deliver part to be downgraded to the degraded mode of target version from current version；If alternatively, the target version
This version number is less than the minimal version No. the 4th, determines and delivers the degraded mode that part is downgraded to target version from current version
Restart degradation to be incompatible.
In one example, the software version file that the stack equipment includes includes at least one delivery part；
The updating and management module 202 is additionally operable to determining that deliver part is upgraded to mesh from current version according to comparison result
After the upgrading mode for marking version, the upgrading mode of the software version file, root are determined based on each upgrading mode for delivering part
Upgrading processing is carried out to software version file according to the upgrading mode of the software version file；
The degradation management module 203 is additionally operable to determining that deliver part is downgraded to mesh from current version according to comparison result
After the degraded mode for marking version, the degraded mode of the software version file, root are determined based on each degraded mode for delivering part
Degradation processing is carried out to software version file according to the degraded mode of the software version file.
The updating and management module 202, during the upgrading mode for being specifically used for determining the software version file, if
There is the upgrading mode of delivery part to restart upgrading to be incompatible, determines that the upgrading mode of the software version file is restarted to be incompatible
Upgrading；Alternatively, if do not deliver the upgrading mode of part restarts upgrading to be incompatible, it is that compatibility is restarted to have the upgrading mode of delivery part
Upgrading determines that the upgrading mode of the software version file is that compatibility restarts upgrading；If alternatively, not delivering the upgrading mode of part
Restart upgrading to be incompatible, the upgrading mode for not delivering part is that compatibility restarts upgrading, determines the liter of the software version file
Grade mode upgrades for increment.
The degradation management module 203, specifically for during determining the degraded mode of the software version file,
Restart degradation to be incompatible if having and delivering the degraded mode of part, determines that the degraded mode of the software version file is incompatible heavy
Open degradation；Alternatively, if do not deliver the degraded mode of part restarts degradation to be incompatible, has and deliver the degraded mode of part as compatible weight
Degradation is opened, determines that the degraded mode of the software version file is that compatibility restarts degradation；If alternatively, not delivering the degradation side of part
Formula restarts degradation to be incompatible, and the degraded mode for not delivering part is that compatibility restarts degradation, determines the software version file
Degraded mode degrades for increment.
In one example, the degradation management module 203 is additionally operable to obtain the isolation version list of current version, institute
It includes the version number for forbidding being degraded to from current version to state isolation version list；If the version number of target version is located at the isolation
In version list, then forbid the delivery part being downgraded to target version from current version；If the version number of target version not position
In the isolation version list, then the version number of target version is supported to the third that increment is degraded to current version respectively most
Minor release/point release and current version support compatibility to restart minimal version No. the 4th being degraded to and be compared.
Stack equipment provided by the embodiments of the present application, for hardware view, hardware structure schematic diagram specifically may refer to
Shown in Fig. 3.Including：Machine readable storage medium and processor, wherein：
Machine readable storage medium：Store instruction code.
Processor：Communicated with machine readable storage medium, read and execute stored in machine readable storage medium it is described
Instruction code realizes version management operation disclosed in the application above-mentioned example.
Here, machine readable storage medium can be any electronics, magnetism, optics or other physical storage devices, can be with
Including or storage information, such as executable instruction, data, etc..For example, machine readable storage medium can be：RAM(Radom
Access Memory, random access memory), volatile memory, nonvolatile memory, flash memory, memory driver is (as hard
Disk drive), solid state disk, any kind of storage dish (such as CD, dvd) either similar storage medium or they
Combination.
System, device, module or the unit that above-described embodiment illustrates can specifically realize by computer chip or entity,
Or it is realized by the product with certain function.A kind of typically to realize that equipment is computer, the concrete form of computer can
To be personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media play
In device, navigation equipment, E-mail receiver/send equipment, game console, tablet computer, wearable device or these equipment
The combination of arbitrary several equipment.
For convenience of description, it is divided into various units when description apparatus above with function to describe respectively.Certainly, implementing this
The function of each unit is realized can in the same or multiple software and or hardware when application.
It should be understood by those skilled in the art that, embodiments herein can be provided as method, system or computer program
Product.Therefore, complete hardware embodiment, complete software embodiment or reality combining software and hardware aspects can be used in the application
Apply the form of example.Moreover, it wherein includes computer usable program code that the embodiment of the present application, which can be used in one or more,
The computer implemented in computer-usable storage medium (including but not limited to magnetic disk storage, CD-ROM, optical memory etc.)
The form of program product.
The application is with reference to method, the flow of equipment (system) and computer program product according to the embodiment of the present application
Figure and/or block diagram describe.It is generally understood that being realized by computer program instructions each in flowchart and/or the block diagram
The combination of flow and/or box in flow and/or box and flowchart and/or the block diagram.These computer journeys can be provided
Sequence instruct to all-purpose computer, special purpose computer, Embedded Processor or other programmable data processing devices processor with
Generate a machine so that the instruction generation executed by computer or the processor of other programmable data processing devices is used for
Realize the dress for the function of being specified in one flow of flow chart or multiple flows and/or one box of block diagram or multiple boxes
It sets.
Computer or the processing of other programmable datas can be guided to set moreover, these computer program instructions can also be stored in
In standby computer-readable memory operate in a specific manner so that instruction stored in the computer readable memory generates
Manufacture including command device, the command device are realized in one flow of flow chart or multiple flows and/or block diagram one
The function of being specified in a box or multiple boxes.
These computer program instructions can be also loaded into computer or other programmable data processing devices so that counted
Series of operation steps are executed on calculation machine or other programmable devices to generate computer implemented processing, in computer
Or the instruction executed on other programmable devices is provided for realizing in one flow of flow chart or multiple flows and/or block diagram
The step of function of being specified in one box or multiple boxes.
Above is only an example of the present application, it is not intended to limit this application.For those skilled in the art
For, the application can have various modifications and variations.It is all within spirit herein and principle made by any modification, equivalent
Replace, improve etc., it should be included within the scope of claims hereof.
Claims (14)
1. a kind of method for edition management, which is characterized in that it is applied to stack equipment, the method includes：
Compare the current version and target version for delivering part according to version number；
If target version is higher than current version, the version number of current version is upgraded to target version with increment is supported respectively
Minimal version No. first and support it is compatible restart be upgraded to minimal version No. the second of target version and be compared, according to comparing knot
Fruit determines the upgrading mode that part is upgraded to target version from current version of delivering；
If target version is less than current version, the version number of target version is supported to what increment was degraded to current version respectively
Third minimal version number and current version support compatibility to restart minimal version No. the 4th being degraded to and be compared, and are tied according to comparing
Fruit, which determines, delivers the degraded mode that part is downgraded to target version from current version.
2. according to the method described in claim 1, it is characterized in that, described determined according to comparison result delivers part from current version
It is upgraded to the process of the upgrading mode of target version, is specifically included：
If the version number of the current version is more than or equal to the minimal version No. first, it is determined that deliver part from current version liter
The upgrading mode of grade to target version upgrades for increment；If alternatively, the version number of the current version is less than first minimum
Version number, and the version number of the current version is more than or equal to the minimal version No. second, it is determined that part is delivered from current version
Originally the upgrading mode for being upgraded to target version is that compatibility restarts upgrading；If alternatively, the version number of the current version is less than described
Minimal version No. second, it is determined that delivery part is upgraded to the upgrading mode of target version from current version and restarts liter to be incompatible
Grade.
3. according to the method described in claim 1, it is characterized in that, described determined according to comparison result delivers part from current version
It is downgraded to the process of the degraded mode of target version, is specifically included：
If the version number of the target version is more than or equal to the third minimal version number, it is determined that deliver part and dropped from current version
The degraded mode of grade to target version degrades for increment；If alternatively, the version number of the target version is less than third minimum
Version number, and the version number of the target version is more than or equal to the minimal version No. the 4th, it is determined that part is delivered from current version
Originally the degraded mode for being downgraded to target version is that compatibility restarts degradation；If alternatively, the version number of the target version is less than described
Minimal version No. 4th, it is determined that delivery part is downgraded to the degraded mode of target version from current version and restarts drop to be incompatible
Grade.
4. according to claim 1-3 any one of them methods, which is characterized in that
The software version file that the stack equipment includes includes at least one delivery part；
Described determined according to comparison result delivers part after current version is upgraded to the upgrading mode of target version, based on each
The upgrading mode for delivering part determines the upgrading mode of the software version file, and according to the upgrading side of the software version file
Formula carries out upgrading processing to the software version file；
Described determined according to comparison result delivers part after current version is downgraded to the degraded mode of target version, based on each
The degraded mode for delivering part determines the degraded mode of the software version file, and according to the degradation side of the software version file
Formula carries out degradation processing to the software version file.
5. according to the method described in claim 4, it is characterized in that,
The upgrading mode that the software version file is determined based on each upgrading mode for delivering part, including：
Restart upgrading to be incompatible if having and delivering the upgrading mode of part, determines that the upgrading mode of the software version file is not simultaneous
Unit weight opens upgrading；Alternatively, if do not deliver the upgrading mode of part restarts upgrading to be incompatible, it is simultaneous to have the upgrading mode of delivery part
Unit weight opens upgrading, determines that the upgrading mode of the software version file is that compatibility restarts upgrading；If alternatively, not delivering the liter of part
Grade mode restarts upgrading to be incompatible, and the upgrading mode for not delivering part is that compatibility restarts upgrading, determines the software version text
The upgrading mode of part upgrades for increment.
6. according to the method described in claim 4, it is characterized in that,
The degraded mode that the software version file is determined based on each degraded mode for delivering part, including：
Restart degradation to be incompatible if having and delivering the degraded mode of part, determines that the degraded mode of the software version file is not simultaneous
Unit weight opens degradation；Alternatively, if do not deliver the degraded mode of part restarts degradation to be incompatible, it is simultaneous to have the degraded mode of delivery part
Unit weight opens degradation, determines that the degraded mode of the software version file is that compatibility restarts degradation；If alternatively, not delivering the drop of part
Grade mode restarts degradation to be incompatible, and the degraded mode for not delivering part is that compatibility restarts degradation, determines the software version text
The degraded mode of part degrades for increment.
7. according to the method described in claim 1, it is characterized in that, the version number by target version respectively with current version
Support the third minimal version number that is degraded to of increment and current version support it is compatible restart the minimal version No. the 4th that is degraded into
Before row compares, the method further includes：
The isolation version list of current version is obtained, the isolation version list includes the version for forbidding being degraded to from current version
Number；If the version number of target version is located in the isolation version list, forbid degrading the delivery part from current version
To target version；If the version number of target version is not located in the isolation version list, execute the version of target version
Supported number respectively with current version third minimal version number that increment is degraded to and current version support it is compatible restart be degraded to
The process that minimal version No. 4th is compared.
8. a kind of edition management device, which is characterized in that be applied to stack equipment, described device includes：
Comparison module, for comparing the current version and target version of delivering part according to version number；
Updating and management module, for when the target version is higher than the current version, then dividing the version number of current version
With support increment be not upgraded to target version minimal version No. the first and support it is compatible restart be upgraded to the second of target version
Minimal version number is compared, and is determined according to comparison result and delivered the upgrading side that part is upgraded to target version from current version
Formula；
Degradation management module, for when the target version is less than the current version, then dividing the version number of target version
The third minimal version number that is degraded to of increment is supported with current version and current version support is compatible restarts the 4th be degraded to
Minimal version number is compared, and is determined according to comparison result and delivered the degradation side that part is downgraded to target version from current version
Formula.
9. device according to claim 8, which is characterized in that the updating and management module, specifically for according to comparing
As a result it determines during delivering the upgrading mode that part is upgraded to target version from current version, if the version of the current version
Number it is more than or equal to the minimal version No. first, it is determined that deliver part and be upgraded to the upgrading mode of target version from current version and be
Increment upgrades；If alternatively, the version number of the current version is less than the minimal version No. first, and the version of the current version
This number is more than or equal to the minimal version No. second, it is determined that delivers the upgrading mode that part is upgraded to target version from current version
Restart upgrading for compatibility；If alternatively, the version number of the current version is less than the minimal version No. second, it is determined that deliver part
It is upgraded to the upgrading mode of target version from current version and restarts upgrading to be incompatible.
10. device according to claim 8, which is characterized in that the degradation management module, specifically for according to comparing
As a result it determines during delivering the degraded mode that part is downgraded to target version from current version, if the version of the target version
Number it is more than or equal to the third minimal version number, it is determined that deliver part and be downgraded to the degraded mode of target version from current version and be
Increment degrades；If alternatively, the version number of the target version is less than the third minimal version number, and the version of the target version
This number is more than or equal to the minimal version No. the 4th, it is determined that delivers the degraded mode that part is downgraded to target version from current version
Restart degradation for compatibility；If alternatively, the version number of the target version is less than the minimal version No. the 4th, it is determined that deliver part
It is downgraded to the degraded mode of target version from current version and restarts degradation to be incompatible.
11. according to claim 8-10 any one of them devices, which is characterized in that
The software version file that the stack equipment includes includes at least one delivery part；
The updating and management module is additionally operable to determining that deliver part is upgraded to target version from current version according to comparison result
After upgrading mode, the upgrading mode of the software version file is determined based on each upgrading mode for delivering part, and according to described
The upgrading mode of software version file carries out upgrading processing to software version file；
The degradation management module is additionally operable to determining that deliver part is downgraded to target version from current version according to comparison result
After degraded mode, the degraded mode of the software version file is determined based on each degraded mode for delivering part, and according to described
The degraded mode of software version file carries out degradation processing to software version file.
12. according to the devices described in claim 11, which is characterized in that
The updating and management module, during the upgrading mode for being specifically used for determining the software version file, if there is delivery
The upgrading mode of part restarts upgrading to be incompatible, determines that the upgrading mode of the software version file restarts upgrading to be incompatible；
Alternatively, if do not deliver the upgrading mode of part restarts upgrading to be incompatible, it is that compatibility restarts upgrading to have the upgrading mode of delivery part,
Determine that the upgrading mode of the software version file is that compatibility restarts upgrading；Alternatively, if the upgrading mode for not delivering part is not
Compatibility restarts upgrading, and the upgrading mode for not delivering part is that compatibility restarts upgrading, determines the upgrading side of the software version file
Formula upgrades for increment.
13. according to the devices described in claim 11, which is characterized in that
The degradation management module, specifically for during determining the degraded mode of the software version file, if there is friendship
It pays the degraded mode of part and restarts degradation to be incompatible, determine that the degraded mode of the software version file restarts drop to be incompatible
Grade；Alternatively, if do not deliver the degraded mode of part restarts degradation to be incompatible, it is that compatibility restarts drop to have the degraded mode of delivery part
Grade determines that the degraded mode of the software version file is that compatibility restarts degradation；Alternatively, if the degraded mode for not delivering part is
Incompatible to restart degradation, the degraded mode for not delivering part is that compatibility restarts degradation, determines the degradation of the software version file
Mode degrades for increment.
14. device according to claim 8, which is characterized in that the degradation management module is additionally operable to obtain current version
Isolation version list, the isolation version list includes the version number for forbidding being degraded to from current version；If target version
Version number is located in the isolation version list, then forbids the delivery part being downgraded to target version from current version；If mesh
The version number for marking version is not located in the isolation version list, then supports the version number of target version with current version respectively
The third minimal version number and current version that increment is degraded to support compatibility to restart minimal version No. the 4th being degraded to and compared
Compared with.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710631648.2A CN108469960B (en) | 2017-07-28 | 2017-07-28 | Version management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710631648.2A CN108469960B (en) | 2017-07-28 | 2017-07-28 | Version management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108469960A true CN108469960A (en) | 2018-08-31 |
| CN108469960B CN108469960B (en) | 2021-08-24 |
Family
ID=63266891
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710631648.2A Active CN108469960B (en) | 2017-07-28 | 2017-07-28 | Version management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108469960B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109324821A (en) * | 2018-10-10 | 2019-02-12 | 湖南长城医疗科技有限公司 | A kind of self-service terminal system method for edition management |
| CN109874057A (en) * | 2019-01-23 | 2019-06-11 | 视联动力信息技术股份有限公司 | A kind of processing method and processing device of live broadcast service |
| CN113535219A (en) * | 2020-04-15 | 2021-10-22 | 武汉斗鱼鱼乐网络科技有限公司 | APP information publishing method, device, medium and computer equipment |
| CN115208761A (en) * | 2022-06-01 | 2022-10-18 | 上海黑眸智能科技有限责任公司 | OTA upgrading system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103414590A (en) * | 2013-08-19 | 2013-11-27 | 杭州华三通信技术有限公司 | Software upgrading method and device |
| US20140307540A1 (en) * | 2013-04-16 | 2014-10-16 | Arista Networks, Inc. | Method and system for multichassis link aggregation in-service software update |
| US20140372583A1 (en) * | 2013-06-13 | 2014-12-18 | Johnny Tseng | Expandable departmental cloud server systems |
| CN104394016A (en) * | 2014-11-25 | 2015-03-04 | 杭州华三通信技术有限公司 | ISSU (In-Service Software Upgrade) method and system |
| US20150100955A1 (en) * | 2012-06-13 | 2015-04-09 | Tencent Technology (Shenzhen) Company Limited | Method and System for Updating Software |
| CN104899017A (en) * | 2014-03-07 | 2015-09-09 | 施耐德电器工业公司 | Electronic system, circuit breaker and method for generating a deviation indicator |
| CN103581008B (en) * | 2012-08-07 | 2017-04-12 | 杭州华三通信技术有限公司 | Router and software upgrading method thereof |
-
2017
- 2017-07-28 CN CN201710631648.2A patent/CN108469960B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150100955A1 (en) * | 2012-06-13 | 2015-04-09 | Tencent Technology (Shenzhen) Company Limited | Method and System for Updating Software |
| CN103581008B (en) * | 2012-08-07 | 2017-04-12 | 杭州华三通信技术有限公司 | Router and software upgrading method thereof |
| US20140307540A1 (en) * | 2013-04-16 | 2014-10-16 | Arista Networks, Inc. | Method and system for multichassis link aggregation in-service software update |
| US20140372583A1 (en) * | 2013-06-13 | 2014-12-18 | Johnny Tseng | Expandable departmental cloud server systems |
| CN103414590A (en) * | 2013-08-19 | 2013-11-27 | 杭州华三通信技术有限公司 | Software upgrading method and device |
| CN104899017A (en) * | 2014-03-07 | 2015-09-09 | 施耐德电器工业公司 | Electronic system, circuit breaker and method for generating a deviation indicator |
| CN104394016A (en) * | 2014-11-25 | 2015-03-04 | 杭州华三通信技术有限公司 | ISSU (In-Service Software Upgrade) method and system |
Non-Patent Citations (3)
| Title |
|---|
| ANDROID (HTTPS://WWW.GEEK-SHARE.COM/GEEKER/327279.HTML): "Android应用程序版本号管理(官方文档中文版)", 《HTTPS://WWW.GEEK-SHARE.COM/DETAIL/2523725816.HTML》 * |
| JUNIPEI NETWORKS: "UNIFIED ISSU: A COMPLETE APPROACH TO IN-SERVICE SOFTWARE UPGRADES", 《HTTP://WWW.ITBIZ.UA/MEDIA/DOCS/JUNIPER/T%20SERIES/UNIFIED%20ISSU%20A%20COMPLETE%20APPROACH%20TO%20IN-SERVICE%20SOFTWARE%20UPGRADES.PDF》 * |
| 浙江思唯网络: "华为交换机ISSU功能介绍", 《HTTP://WWW.023WG.COM/JCPZ/355.HTML》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109324821A (en) * | 2018-10-10 | 2019-02-12 | 湖南长城医疗科技有限公司 | A kind of self-service terminal system method for edition management |
| CN109324821B (en) * | 2018-10-10 | 2021-11-05 | 湖南长城医疗科技有限公司 | Self-service terminal system version management method |
| CN109874057A (en) * | 2019-01-23 | 2019-06-11 | 视联动力信息技术股份有限公司 | A kind of processing method and processing device of live broadcast service |
| CN113535219A (en) * | 2020-04-15 | 2021-10-22 | 武汉斗鱼鱼乐网络科技有限公司 | APP information publishing method, device, medium and computer equipment |
| CN113535219B (en) * | 2020-04-15 | 2023-12-01 | 北京世标认证中心有限公司 | APP information release method, device, medium and computer equipment |
| CN115208761A (en) * | 2022-06-01 | 2022-10-18 | 上海黑眸智能科技有限责任公司 | OTA upgrading system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108469960B (en) | 2021-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108469960A (en) | A kind of method for edition management and device | |
| EP3537286B1 (en) | Configuration for application using microservices | |
| US10146651B2 (en) | Member replacement in an array of information storage devices | |
| CN106899666B (en) | Data processing method and device for service identification | |
| CN105144074B (en) | It is stored using the block of hybrid memory device | |
| US8544012B2 (en) | Changing a scheduler in a virtual machine monitor | |
| US10594660B2 (en) | Selecting proxies | |
| CN108897492B (en) | Data writing method and device | |
| US20150058383A1 (en) | Systems and methods for operating a flash memory file system | |
| CN103793256A (en) | Method for management of memory cards, and electronic device | |
| CN105573788B (en) | The method and apparatus of patch processing and the method and apparatus for generating patch | |
| US10318612B2 (en) | System and method for implementing screen capture | |
| EP2972795B1 (en) | Operation of software modules in parallel | |
| CN102880478B (en) | Oftware updating method | |
| CN108255504A (en) | Method for updating software in storage system and storage system | |
| CN108459906A (en) | A kind of dispatching method and device of VCPU threads | |
| US20120124429A1 (en) | Apparatus and method for tracing memory access information | |
| US20160196090A1 (en) | Recognizing hard disk movement | |
| CN106102024A (en) | A kind of mobile device message based on translational speed pushes management method and system | |
| CN108205503A (en) | Hardware driving compatibility method and terminal | |
| US8856596B2 (en) | Debugging apparatus and method | |
| CN112241297B (en) | Data display method, system, computer equipment and readable storage medium | |
| CN106131298A (en) | A kind of mobile device message pushes management method and system | |
| JP6273907B2 (en) | Vehicle equipment | |
| CN107025068A (en) | The asynchronous replication of data in memory |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |