CN100568820C - Software version self management method - Google Patents
Software version self management method Download PDFInfo
- Publication number
- CN100568820C CN100568820C CNB2006101606207A CN200610160620A CN100568820C CN 100568820 C CN100568820 C CN 100568820C CN B2006101606207 A CNB2006101606207 A CN B2006101606207A CN 200610160620 A CN200610160620 A CN 200610160620A CN 100568820 C CN100568820 C CN 100568820C
- Authority
- CN
- China
- Prior art keywords
- list information
- version
- allocation list
- software version
- veneer
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a kind of redundancy check method that is used to carry out software version record and veneer record, a kind of software version self management method also is provided, it may further comprise the steps: carry out the redundancy check of software version record and veneer record; And the consistency desired result that carries out software version record and version file.Therefore,, removed the configuration software version of out-of-date no hardware single board, and removed in the system debug process because version information and version file that manual intervention causes are inconsistent by the present invention.
Description
Technical field
The present invention relates to a kind of be used to carry out software version record and the redundancy check method of veneer record and the method for device software version self-management, more specifically, relate to a kind of automatic method for sorting that is used at the redundant software of communication system network element side apparatus system.
Background technology
Be the hardware cost of control whole system and the complexity of reduction board software management, the NODEB system realizes the centralized control and management to board software, promptly all upgraded versions all are kept in the CF card of master control borad BMC (NODEB Main Control), no longer include fixing memory device (as FLASH) on each veneer, no longer preserve version file.But master control board storage capacity also is limited, a general version that is moving of reservation and standby version of only allowing, and because the hardware single board upgrading, the software version of matching running also will be upgraded.
System is through long-term operation, the software version of the hardware single board correspondence that has stepped down from the stage of history also exists on the foreground, become rubbish, taken the precious resources of system, as untimely removing, historical version information and version file are too much, will influence the operational efficiency of equipment greatly even cause the machine of delaying.Present means all are that the plant maintenance personnel judge one by one; remove the rubbish version that these do not re-use, just there is the possibility of misoperation unavoidably in this, and for the equipment of protecting design to be not good at; if mistake has been deleted the version that also will use, will cause catastrophic consequence.
Thereby, must write down software version record and veneer and carry out redundancy check and the software of base station equipment is cleared up automatically.
Summary of the invention
In order to address the above problem, the present invention proposes a kind of be used to carry out software version record and the redundancy check method of veneer record and the software automatic cleaning method of base station equipment, it can improve the reliability and the intellectuality of plant maintenance, the operational efficiency of optimization system, and can set regularly the removing task and come timing trigger equipment system to carry out self-clean, or trigger the execution clean-up process by the backstage by operating personnel.
One aspect of the present invention provides a kind of redundancy check method that is used to carry out software version record and veneer record, may further comprise the steps: obtain veneer allocation list information; Obtain software version allocation list information; And coupling veneer allocation list information and software version allocation list information, filter the redundancy versions record, and removing and redundancy versions write down corresponding colophon and version file.
According to an aspect of the present invention, veneer allocation list information records all veneer records that need use, and the veneer record comprises board type and hardware version numbers.
In addition, software version allocation list information records following at least a: release type, hardware version numbers, filename, file path and file verification and.The redundancy versions record is to exist in the software version allocation list information, and non-existent colophon in the veneer allocation list information.
According to an aspect of the present invention, coupling is to be undertaken by the board type and the hardware version numbers that compare in veneer allocation list information and the software version allocation list information.
Another aspect of the present invention provides a kind of software version self management method, may further comprise the steps: S202, carry out the redundancy check of software version record and veneer record.
In addition, software version self management method according to the present invention also comprises: S204, carry out the consistency desired result of software version record and version file.
Wherein, S202 realizes by following steps: obtain veneer allocation list information; Obtain software version allocation list information; And coupling veneer allocation list information and software version allocation list information, filter the redundancy versions record, and removing and redundancy versions write down corresponding colophon and version file.
S204 realizes by following steps: obtain software version allocation list information; Obtain corresponding version file according to software version allocation list information; And the consistency of verification version file and colophon, if inconsistent, then remove the colophon that does not have version file, and remove the version file that does not have colophon.
According to another aspect of the present invention, veneer allocation list information records all veneer records that need use, and the veneer record comprises board type and hardware version numbers.Software version allocation list information records following at least a: release type, hardware version numbers, filename, file path and file verification and.The redundancy versions record is to exist in the software version allocation list information, and non-existent colophon in the veneer allocation list information.
In addition, according to another aspect of the present invention, coupling is to be undertaken by the board type and the hardware version numbers that compare in veneer allocation list information and the software version allocation list information.
Thereby, rubbish version of the present invention is the method for cleaning automatically, avoid the loaded down with trivial details of user's manual removal, and the systemic breakdown that the misoperation that can avoid artificial removing to exist causes, thereby, removed the configuration software version of out-of-date no hardware single board, and removed in the system debug process because version information and version file that manual intervention causes are inconsistent.
Other features and advantages of the present invention will be set forth in the following description, and, partly from specification, become apparent, perhaps understand by implementing the present invention.Purpose of the present invention and other advantages can realize and obtain by specifically noted structure in the specification of being write, claims and accompanying drawing.
Description of drawings
Accompanying drawing is used to provide further understanding of the present invention, and constitutes the part of specification, is used from explanation the present invention with embodiments of the invention one, is not construed as limiting the invention.In the accompanying drawings:
Fig. 1 is the sequential chart that trigger on version clean-up process backstage;
Fig. 2 is the flow chart according to software version self management method of the present invention;
Fig. 3 is the flow chart according to version redundant check process of the present invention; And
Fig. 4 is the flow chart according to version consistency desired result process of the present invention.
Embodiment
Below in conjunction with accompanying drawing the preferred embodiments of the present invention are described, should be appreciated that preferred embodiment described herein only is used for description and interpretation the present invention, and be not used in qualification the present invention.
The present invention is that example describes with NODEB (Node B) base station equipment in the third generation mobile system.
Fig. 1 is the simple sequential chart that trigger on version clean-up process backstage, as shown in Figure 1, version cleaning request is sent to BMC 104 in backstage 102, and BMC 104 responds its request then, return version cleaning response to backstage 102, thereby realized the cleaning of rubbish version.
Fig. 2 is the flow chart according to software version self management method of the present invention.As shown in Figure 2, software version self management method may further comprise the steps: S202, carry out the redundancy check of software version record and veneer record; And S204, carry out the consistency desired result of software version record and version file.
Fig. 3 is that as shown in Figure 3, S202 realizes by following steps according to the flow chart of version redundant check process of the present invention: S302, obtain veneer allocation list information; S304 obtains software version allocation list information; And S306, coupling veneer allocation list information and software version allocation list information are filtered the redundancy versions record, and removing and redundancy versions write down corresponding colophon and version file.
Wherein, veneer allocation list information records all veneer records that need use, and the veneer record comprises board type and hardware version numbers etc.Software version allocation list information record release type, hardware version numbers, filename, file path and file verification and etc.The redundancy versions record is to exist in the software version allocation list information, and non-existent colophon in the veneer allocation list information.Coupling is to be undertaken by the board type and the hardware version numbers that compare in veneer allocation list information and the software version allocation list information.
Thereby, finished removing to the configuration software version of out-of-date no hardware single board.
Fig. 4 is the flow chart according to version consistency desired result process of the present invention.As shown in Figure 4, S204 realizes by following steps: S402, obtain software version allocation list information; S404 obtains corresponding version file according to software version allocation list information; And S406, if the consistency of verification version file and colophon inconsistent, is then removed the colophon that does not have version file, and is removed the version file that does not have colophon.
Thereby, finished the version information and the inconsistent removing of version file that cause owing to manual intervention in the system debug process.
Realized in communication system automatic arrangement as mentioned above to the redundant software of network element side apparatus system.
In the present invention, the trigger condition of version clean-up process includes but not limited to following mode:
(1) can set regularly removing task, regularly carry out the version cleaning not busy night, during version is changed in upgrading, suspend this task and carry out as business;
(2) manual activation mode, under the situation of confirming the normal operation of existing equipment, the Operation and Maintenance personnel of equipment are by the foreground that says the word, OMC backstage, and trigger equipment carries out self-clean; And
(3) manual activation is confirmed mode, under the situation of confirming the normal operation of existing equipment, the Operation and Maintenance personnel of equipment are by the foreground that says the word, OMC backstage, trigger equipment carries out the arrangement of redundancy versions, and will put the result in order and return to the backstage, shows the redundancy version information tabulation on the interface, personnel confirm by Operation and Maintenance, or full choosing, or therefrom select part, be dealt into version file and colophon that foreground deletion user selection will be deleted.(Fig. 3 process is transformed a little and can be realized).
As can be seen, rubbish version of the present invention is the method for cleaning automatically, avoids the loaded down with trivial details of user's manual removal, and the systemic breakdown that causes of the misoperation that can avoid artificial removing to exist.
Be the preferred embodiments of the present invention only below, be not limited to the present invention, for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (8)
1. a redundancy check method that is used for software version record and veneer record is characterized in that, may further comprise the steps:
S302 obtains veneer allocation list information;
S304 obtains software version allocation list information; And
S306, mate described veneer allocation list information and described software version allocation list information, filter the redundancy versions record, and removing and described redundancy versions write down corresponding colophon and version file, wherein, described redundancy versions record is to exist in the described software version allocation list information, and non-existent colophon in the described veneer allocation list information.
2. redundancy check method according to claim 1 is characterized in that, described veneer allocation list information records the veneer record that all need use, and described veneer record comprises board type and hardware version numbers.
3. redundancy check method according to claim 1 and 2 is characterized in that, described software version allocation list information records following at least a: release type, hardware version numbers, filename, file path and file verification and.
4. redundancy check method according to claim 3 is characterized in that, described coupling is to be undertaken by described board type and described hardware version numbers in more described veneer allocation list information and the described software version allocation list information.
5. a software version self management method is characterized in that, may further comprise the steps:
S202 carries out the redundancy check of software version record and veneer record, comprising:
S302 obtains veneer allocation list information;
S304 obtains software version allocation list information; And
S306, mate described veneer allocation list information and described software version allocation list information, filter the redundancy versions record, and removing and described redundancy versions write down corresponding described colophon and version file, wherein, described redundancy versions record is to exist in the described software version allocation list information, and non-existent colophon in the described veneer allocation list information
S204 carries out the consistency desired result of described software version record and version file, comprising:
S402 obtains software version allocation list information;
S404 obtains corresponding version file according to described software version allocation list information; And
S406, if the consistency of described version file of verification and described colophon inconsistent, is then removed the described colophon that does not have described version file, and is removed the described version file that does not have described colophon.
6. software version self management method according to claim 5 is characterized in that, described veneer allocation list information records all described veneer records that need use, and described veneer record comprises board type and hardware version numbers.
7. according to claim 5 or 6 described software version self management methods, it is characterized in that described software version allocation list information records following at least a: release type, hardware version numbers, filename, file path and file verification and.
8. software version self management method according to claim 7 is characterized in that, described coupling is to be undertaken by described board type and described hardware version numbers in more described veneer allocation list information and the described software version allocation list information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101606207A CN100568820C (en) | 2006-11-29 | 2006-11-29 | Software version self management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101606207A CN100568820C (en) | 2006-11-29 | 2006-11-29 | Software version self management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101192981A CN101192981A (en) | 2008-06-04 |
| CN100568820C true CN100568820C (en) | 2009-12-09 |
Family
ID=39487751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101606207A Expired - Fee Related CN100568820C (en) | 2006-11-29 | 2006-11-29 | Software version self management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100568820C (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101425930B (en) * | 2008-12-05 | 2011-04-20 | 上海华为技术有限公司 | Method and equipment for ensuring single board operation software |
| CN105975284A (en) * | 2016-05-31 | 2016-09-28 | 京东方科技集团股份有限公司 | Automatic software version checking device and method |
-
2006
- 2006-11-29 CN CNB2006101606207A patent/CN100568820C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN101192981A (en) | 2008-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100354825C (en) | Software staging and back spacing method | |
| CN102238093B (en) | Service interruption prevention method and device | |
| CN102681917B (en) | A kind of operating system and restorative procedure thereof | |
| CN107566165B (en) | Method and system for discovering and deploying available resources of power cloud data center | |
| CN100488123C (en) | Software and hardware version management method and system of communication equipment | |
| CN102855146A (en) | Firmware updating system and method | |
| CN101383724B (en) | Network updating method and operation maintaining element, and network element updating system | |
| CN102739451B (en) | Method and device for updating master-slave switchover condition, server and system | |
| CN110377456A (en) | A kind of management method and device of virtual platform disaster tolerance | |
| CN111651523B (en) | MySQL data synchronization method and system of Kubernetes container platform | |
| CN100583782C (en) | Software upgrade method and device | |
| CN101183979B (en) | Method and device of configuration backup | |
| CN103780417A (en) | Database failure transfer method based on cloud hard disk and device thereof | |
| CN103677650A (en) | Drive letter drifting preventing and treating method and device | |
| CN103902399A (en) | Software system repair processing method and software system repair processing device | |
| CN100568820C (en) | Software version self management method | |
| CN100568821C (en) | Software version self management method | |
| CN101510156B (en) | Information system resource recovery method and device | |
| CN103324554A (en) | Standby system device, a control method, and a program thereof | |
| CN101266566B (en) | Multi- test scene automatic dispatch system and method | |
| CN111917588A (en) | Edge device management method, device, edge gateway device and storage medium | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN101192987A (en) | Software version self management device | |
| CN101022633B (en) | Allocation data recovering method, system and device | |
| CN101192988A (en) | Software version self management device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20091209 Termination date: 20151129 |