CN112702183A - Method and device for controlling software version rollback of base station, base station and readable storage medium - Google Patents
Method and device for controlling software version rollback of base station, base station and readable storage medium Download PDFInfo
- Publication number
- CN112702183A CN112702183A CN201911008081.9A CN201911008081A CN112702183A CN 112702183 A CN112702183 A CN 112702183A CN 201911008081 A CN201911008081 A CN 201911008081A CN 112702183 A CN112702183 A CN 112702183A
- Authority
- CN
- China
- Prior art keywords
- reset
- base station
- software version
- time
- version
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000012544 monitoring process Methods 0.000 claims abstract description 26
- 230000002159 abnormal effect Effects 0.000 claims description 39
- 238000004891 communication Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 8
- 230000005540 biological transmission Effects 0.000 claims description 6
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000007726 management method Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
- H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
- H04L41/0863—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions by rolling back to previous configuration versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0823—Errors, e.g. transmission errors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Environmental & Geological Engineering (AREA)
- Automation & Control Theory (AREA)
- Mobile Radio Communication Systems (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a method for controlling the rollback of a base station software version, which records the reason and the time of resetting by monitoring the resetting occurring in the preset time; entering a version rollback control program when the monitored resetting times reach a preset threshold value; the base station can fall back to the standby version when the reset condition occurs for many times; when the base station is reset for multiple times, the base station can automatically enter a version rollback control program, load the rollback version and replace the currently running software version, so that the base station is prevented from continuously running the current software version which causes multiple resets, the service interruption time is shortened to the greatest extent, and the operation and maintenance cost is reduced. The embodiment of the invention also provides a device for controlling the software version rollback of the base station, so that the base station can automatically enter the version rollback control program to load the rollback version to replace the currently running software version when the base station is reset for multiple times.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to but not limited to a method and a device for controlling the software version rollback of a base station, the base station and a readable storage medium.
Background
The abnormal restart reset caused by the software bugs when the base station operates is a fatal fault for network operators, due to the fact that commercial network scenes are complex and changeable, certain abnormal scenes which are not considered or can not be completely simulated by software developers and testers exist, bugs are usually triggered in the scenes, the abnormal restart reset of the base station can cause long-time service interruption, if the software with bugs is operated all the time, the base station can be repeatedly abnormally restarted and reset, the service is interrupted and cannot be recovered, direct or indirect economic loss is brought to network access persons, and serious negative effects are also caused to the network operators.
In the related art, in the face of a fault of repeated restart and reset of a base station, because a transmission link between the base station and a network management server is abnormal, an operator cannot effectively intervene through network management operation and can only solve the problem on site manually, the labor cost of network operation is obviously increased, and the fault recovery period is prolonged, especially for a fault base station located in severe environments such as a remote mountain area, a jungle, an island and the like.
The automatic rollback of the abnormal restart software of the base station is an effective self-healing mechanism, the conventional software rollback strategy in the industry can only cover the scene with software bugs in the upgrading process, and the problem that the software is not abnormal after the upgrading process and is restarted due to sudden abnormality of the software after running for a period of time cannot be solved; meanwhile, a software exception rollback method in the related art is a mandatory rollback method (i.e., an exception immediately rollback occurs), a rollback strategy cannot be dynamically customized for different sites, and diversified scene requirements of users cannot be met, experience proves that operation and maintenance personnel cannot flexibly customize the rollback strategy according to actual situations on site, and the method is passive, and an exception rollback control method needs to be provided urgently to shorten service interruption time to the greatest extent and reduce operation and maintenance cost.
Disclosure of Invention
The method for controlling the rollback of the software version of the base station mainly solves the technical problem that the software version cannot be automatically rolled back when the base station is reset for multiple times.
To solve the foregoing technical problem, an embodiment of the present invention provides a method for controlling a base station software version rollback, including:
monitoring the reset occurring in the preset time, and recording the reset reason and the reset time;
and entering a version rollback control program when the monitored reset times reach a preset threshold value.
The embodiment of the invention also provides a base station software version rollback control device, which comprises a monitoring module and a control module;
the monitoring module monitors the reset occurring in the preset time and records the reset reason and the reset time;
and the control module enters a version rollback control program when the monitored reset times reach a preset threshold value. The embodiment of the invention also provides a base station, which is characterized by comprising a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the steps of the base station software version backoff control method as described above.
Embodiments of the present invention also provide a readable storage medium, which stores one or more programs that are executable by one or more processors to implement the steps of the method for controlling fallback by base station software version as described above.
The invention has the beneficial effects that:
according to the method for controlling the software version rollback of the base station, provided by the embodiment of the invention, the reset occurring in the preset time is monitored, and the reset reason and the reset time are recorded; entering a version rollback control program when the monitored resetting times reach a preset threshold value; therefore, the problem of service interruption caused by repeated resetting of the base station is solved; when the base station is reset for multiple times, the version rollback control program can be automatically entered, the rollback version is loaded, and the currently running software version is replaced, so that the situation that the base station continuously runs the current software version which causes multiple resets is avoided, the service interruption time is shortened to the greatest extent, the operation and maintenance cost is reduced, and the running reliability of the base station software is improved.
Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a basic flowchart of a method for controlling a base station software version rollback according to a first embodiment of the present invention;
fig. 2 is a flowchart illustrating a method for controlling a base station software version rollback according to a first embodiment of the present invention;
fig. 3 is a schematic diagram of a basic flow of another method for controlling a software version backoff of a base station according to a second embodiment of the present invention;
fig. 4 is a schematic diagram of a basic structure of a base station software version backoff control apparatus according to a third embodiment of the present invention;
fig. 5 is a schematic diagram of a basic structure of a base station according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment is as follows:
in order to solve the problem that a base station cannot automatically rollback a software version according to a reset condition and a self requirement, an embodiment of the present invention provides a method for controlling rollback of a software version of a base station, please refer to fig. 1, where fig. 1 is a basic flowchart of the method for controlling rollback of a software version of a base station according to the embodiment of the present invention, and the method for controlling rollback of a software version of a base station includes:
s101, monitoring reset occurring in preset time, and recording reset reasons and reset time;
it should be understood that the preset time for monitoring the reset occurring within the preset time can be flexibly configured by the relevant designer or gateway, the preset time of different base stations can be flexibly set, and the preferred preset time can be in the range of 10 minutes to 120 minutes. If multiple resets occur within the preset time, the reason of each reset and the corresponding reset time are recorded, and relevant designers can set the upper limit of the reset history information cache such as the reset reason and the reset time which can be stored in the base station according to requirements; preferably, it is set that the base station can store 20 reset reasons and reset time. And the reset times are increased once within the preset time every time the reset reason and the reset time are recorded once. Each preset time is one period. Specifically, when the preset time is 30 minutes, the reset occurring in 30 minutes is monitored, and after the period is ended, the reset occurring in the next period, that is, the reset occurring in the next 30 minutes, is continuously monitored.
In this embodiment, after the monitoring the reset occurring within the preset time, before the recording the reset reason and the reset time, as shown in fig. 2, the method further includes the following steps:
s201, monitoring reset occurring in preset time;
it should be understood that the preset time is a period, and specifically, the preset time may be 30 minutes, and then 30 minutes is a period, and the reset occurring in the period is monitored.
S202, judging whether the reset is normal reset or not, if so, turning to S203, and if not, turning to S204;
in this embodiment, the normal reset includes, but is not limited to, any one of the following: power failure reset, island reset, transmission self-establishment reset, whole table configuration reset and gateway operation reset. Specifically, power down reset means: reset caused by power supply interruption of the base station; and (3) resetting and restarting the island: the self-healing reset automatically initiated by the base station; transmission self-set up reset finger: when the base station and the network management server can not establish a link, the base station tries to establish a link with the server through a Dynamic Host Configuration Protocol (DHCP), and the reset is initiated in the process; resetting the whole table configuration: a reset caused by base station configuration modification; gateway operation reset indicates: the network manager dynamically manages the issued reset command; it should be understood that the network manager dynamically manages the issued reset command, but is not limited to include at least one of the following: and resetting the whole station command and the main control single board command.
It should be understood that when the base station is a normal reset or a reset generated by a related designer or network management operation, the reason and time of the reset do not need to be recorded. In this embodiment, the normal reset is not limited to the above reset, and the normal reset may be added or deleted by the related designer.
And S203, not recording the reset.
It is to be understood that after the reset is not recorded, the reset occurring within the preset time needs to be continuously monitored; specifically, the base station monitors the reset condition occurring within 30 minutes, when the reset occurs within 15 th minute, the base station judges that the reset is normal reset, does not record the reset, and continues to monitor the preset time of the period, that is, the reset occurring within the remaining 15 minutes, and starts to monitor the reset occurring within the preset time period again after the preset time within 30 minutes elapses.
S204, judging whether the reset is reset or not, if so, turning to S205, and if not, turning to S206;
in this embodiment, the reset includes, but is not limited to, any of the following: upgrade reset and rollback reset. It should be understood that the upgrade reset refers to a reset generated by upgrading the software version of the base station; the back-off reset refers to a reset generated by the back-off of the software version of the base station. It is to be understood that the upgrade reset or the rollback reset may be an operation performed by a relevant designer or network administrator.
S205, if yes, uploading the recorded reset reason and reset time, and re-monitoring the reset occurring in the preset time.
It should be understood that when reset occurs, all reset reason, reset time and other reset history information caches need to be uploaded, monitoring of the preset time in the period is finished, and monitoring of the preset time in the next period is started.
S206, judging that the reset is abnormal reset, and recording the reason of the abnormal reset and the time of the abnormal reset.
In this embodiment, when the reset is not a reset: determining the reset is an abnormal reset; and when the reset is abnormal reset, recording the reset reason and the reset time as recording the abnormal reset reason and the abnormal reset time. It should be understood that, in this embodiment, the abnormal reset is also a reset that is not the normal reset and the reset, and when it is determined that the current reset is not the normal reset and is not the reset, it is determined that the current reset is the abnormal reset.
In this embodiment, in some cases, when a reset condition occurs, a condition of state switching (active/standby switching) between the active main control board and the standby main control board may occur when power is turned on, and then all reset history information caches such as reset reasons and reset time are uploaded at this time, and the monitoring of the preset time in this cycle is ended, and the monitoring of the preset time in the next cycle is started.
And S102, entering a version rollback control program when the monitored reset times reach a preset threshold value.
It should be understood that different base stations may set different preset thresholds, for example, for relatively important base stations, the preset threshold of the reset times may be set to a lower value, so as to ensure that the important base stations can timely return to the previous version when the reset condition occurs, and shorten the service interruption time; for a relatively unimportant base station or an experimental base station, the preset threshold of the reset times can be set to be a higher value, so that when the base station enters a version rollback control program, the reason for resetting the base station can be acquired more accurately.
In this embodiment, a version rollback control program is entered, after the version of the base station is rolled back, all reset history information caches such as reset reasons and reset time need to be uploaded, the monitoring of the preset time in this period is ended, and the monitoring of the preset time in the next period is started.
In the embodiment, the reset reason and the reset time are recorded by monitoring the reset occurring in the preset time; when the monitored resetting times reach a preset threshold value, entering a version rollback control program, so that the base station can rollback to a standby version when resetting is performed for multiple times, and the problem that effective operation cannot be performed to solve the situation of multiple resetting when service is interrupted due to multiple times of resetting of the base station is solved; when the base station is reset for multiple times, the version rollback control program can be automatically entered, the rollback version is loaded, and the currently running software version is replaced, so that the situation that the base station continuously runs the current software version which causes multiple resets is avoided, the service interruption time is shortened to the greatest extent, the operation and maintenance cost is reduced, and the running reliability of the base station software is improved. In some embodiments, it is further required to determine whether the reset is an abnormal reset, and the version rollback control program is only entered when the number of times of the abnormal reset reaches a preset threshold, and the version rollback control program is not entered due to a normal reset or a reset, so that the situation that the version rollback control program is entered due to a normal reset or a reset is avoided.
Example two:
in order to better understand the present invention, a more specific example is provided in the implementation of the present invention to describe a method for controlling a software version backoff of a base station, as shown in fig. 3, the method for controlling a software version backoff of a base station includes:
s301, configuring a base station version rollback control parameter;
in this embodiment, the specific version rollback control parameter may include, but is not limited to, at least one of the following: the method comprises the steps of standby software version, period preset time, reset times preset threshold value in the period preset time, normal reset list, caching information upper limit and the like. It should be understood that, related designers may configure specific fallback control parameters through a network manager, and then upload the parameters to a corresponding base station, or directly set version fallback control parameters for the corresponding base station.
It should be understood that the standby software version refers to a standby version different from the current running software version of the base station, and when the reset times reach a preset threshold, the base station can load and run the standby software version to replace the current running software version; it should be understood that the preferred backup software version is a historical software version, that is, a historical software version normally used by the base station, so that the base station can normally operate when the backup software version is loaded and operated, and the situation of resetting for many times is avoided.
It should be understood that, related designers may set different period preset times according to the importance degrees of different base stations, and reset time preset thresholds within the different period preset times, specifically, the relationship between the period preset time and the reset time preset threshold may be as shown in table 1 below:
TABLE 1 Preset time and reset times Preset threshold
As shown in table 1 above, when the preset period time is 20 minutes and the preset threshold of the reset times is 5 times, that is, when the flag detects 5 times of reset within 20 minutes, the version rollback control procedure is entered.
In this embodiment, specifically, the list of normal resets is shown in table 2 below:
| No | reason for reduction |
| 1 | Power down reset |
| 2 | Island reset |
| 3 | Transmission self-established reset |
| 4 | Whole table configuration reset |
| 5 | Network management operation reset |
TABLE 2 Normal reset List
Specifically, power down reset means: reset caused by power supply interruption of the base station; and (3) resetting and restarting the island: the self-healing reset automatically initiated by the base station; transmission self-set up reset finger: when the base station and the network management server can not establish a link, the base station tries to establish a link with the server through a Dynamic Host Configuration Protocol (DHCP), and the reset is initiated in the process; resetting the whole table configuration: a reset caused by base station configuration modification; gateway operation reset indicates: the network manager dynamically manages the issued reset command; it should be understood that the network manager dynamically manages the issued reset command, but is not limited to include at least one of the following: and resetting the whole station command and the main control single board command.
In this embodiment, when the base station has a reset on the normal reset list, that is, this reset is indicated as a normal reset, and the reason and the reset time of this reset will not be recorded. It should be understood that in some embodiments, the reset reason and the reset time for recording the normal reset may be flexibly set according to requirements.
Specifically, the reset list includes, but is not limited to, at least one of the following: upgrade reset and rollback reset.
It should be noted that when a reset occurs, the recorded reset reason and reset time are uploaded. And the history buffer is emptied and the detection of the reset occurring in the next period is restarted.
S302, monitoring abnormal resetting occurring in preset time, and recording the reason and time of the abnormal resetting;
in this embodiment, after the reset and restart of the base station each time, the reason and the time for causing the reset and restart of the base station at this time are analyzed, and when the reason for causing the reset and restart of the base station at this time is analyzed to be not any one of the normal reset or the reset, the reason and the reset time at this time are recorded. That is, when the monitored reset does not belong to any one of the normal reset or the reset, the reset is determined to be an abnormal reset, and when the abnormal reset occurs within the preset time, the reason for the abnormal reset and the abnormal reset time are recorded.
Specifically, when the preset time is 60 minutes, the reset occurring within 60 minutes of the preset time in each period is monitored, and when the reset occurring is judged to be an abnormal reset, the reason for the abnormal reset and the abnormal reset time are recorded.
And S303, entering a version rollback control program when the monitored abnormal resetting times reach a preset threshold value.
In this embodiment, specifically, when it is detected that 5 times of abnormal reset occurs within 60 minutes of the preset time, the version rollback control program is entered, so that the base station loads and runs the standby software version to replace the software version currently running by the base station. And the reset reason and the reset time recorded within 60 minutes of the preset time are uploaded, so that related designers can know the abnormal reset reason and the abnormal reset time. It should be noted that, if the abnormal reset occurring within the preset time of 60 minutes does not reach the preset threshold value for 5 times, the next cycle of the preset time of 60 minutes is entered, and the abnormal reset occurring within the preset time is continuously monitored.
According to the method for controlling the software version rollback of the base station, provided by the embodiment of the invention, relevant designers configure the version rollback control parameters of the base station through design, the base station monitors abnormal reset occurring in preset time according to the version rollback control parameters of the base station, and records the reason and the time of the abnormal reset; and when the monitored abnormal reset times reach a preset threshold value, entering a version rollback control program. Therefore, the problem that the situation of repeated resetting cannot be solved by effective operation when the service is interrupted due to repeated resetting of the base station is solved; when the base station is reset for multiple times, the base station can automatically enter the version rollback control program, load the rollback version and replace the currently running software version, so that the situation that the base station continuously runs the current software version which causes multiple resets is avoided, the service interruption time is shortened to the greatest extent, the operation and maintenance cost is reduced, the running reliability of the base station software is improved, and meanwhile, the situation that the base station normally resets or resets to cause the version rollback control program to enter is avoided.
Example three:
the present embodiment further provides a device for controlling rollback of a software version of a base station, as shown in fig. 4, which includes a monitoring module and a control module, wherein:
the monitoring module is used for monitoring reset occurring in preset time and recording reset reasons and reset time;
and the control module is used for entering a version rollback control program when the monitored reset times reach a preset threshold value.
The present embodiment further provides a base station, as shown in fig. 5, which includes a processor 51, a memory 52 and a communication bus 53, wherein:
the communication bus 53 is used for realizing connection communication between the processor 51 and the memory 52;
the processor 51 is configured to execute one or more computer programs stored in the memory 52 to implement at least one step of the method for controlling the software version backoff of the base station in the first and second embodiments.
Example four
The present embodiments also provide a readable storage medium that includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as instructions, data structures, computer program modules or other data. Readable storage media include, but are not limited to, RAM (Random Access memory), ROM (Read-Only memory), EEPROM (Electrically Erasable Programmable Read-Only memory), flash memory or other memory technology, CD-ROM (Compact disk Read-Only memory), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
The readable storage medium in this embodiment may be used to store one or more computer programs, and the one or more computer programs stored in the readable storage medium may be executed by a processor, and may be executed by the processor, so as to implement all or part of the steps of the method for controlling the fallback of the software version of the base station in the above embodiments.
It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
In addition, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to one of ordinary skill in the art. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (11)
1. A method for controlling the software version rollback of a base station comprises the following steps:
monitoring the reset occurring in the preset time, and recording the reset reason and the reset time;
and entering a version rollback control program when the monitored reset times reach a preset threshold value.
2. The method for controlling software version back-off of a base station according to claim 1, wherein the monitoring after the reset occurred within the preset time, the recording the reason for the reset and before the reset time further comprises:
judging whether the reset is normal reset or not;
if yes, the reset is not recorded, and the reset occurring in the preset time is continuously monitored.
3. The method for controlling software version back-off of a base station according to claim 2, wherein the normal reset comprises any one of:
power failure reset, island reset, transmission self-establishment reset, whole table configuration reset and gateway operation reset.
4. The base station software version backoff control method of claim 3, wherein when the reset is not a normal reset:
judging whether the reset is reset or not;
if yes, uploading the recorded reset reason and reset time, and re-monitoring the reset occurring in the preset time.
5. The base station software version backoff control method of claim 4 wherein said reset comprises any one of:
upgrade reset and rollback reset.
6. The base station software version backoff control method of claim 5, wherein when said reset is not a reset, it is determined that said reset is an abnormal reset;
and when the reset is abnormal reset, recording the reset reason and the reset time as recording the abnormal reset reason and the abnormal reset time.
7. The method for controlling software version back-off of a base station according to claim 6, wherein the monitoring after the reset occurred within the preset time, the recording the reason for the reset and before the reset time further comprises:
judging whether the state switching of the main control single board and the standby main control single board occurs or not;
if yes, uploading the recorded reset reason and reset time, and re-monitoring the reset occurring in the preset time.
8. The base station software version backoff control method of claims 6 to 7, wherein entering a version backoff control procedure further comprises:
and uploading the recorded reset reason and reset time, and restarting to monitor reset occurring in preset time.
9. A base station software version backoff control apparatus, comprising:
the monitoring module monitors the reset occurring in the preset time and records the reset reason and the reset time;
and the control module enters a version rollback control program when the monitored reset times reach a preset threshold value.
10. A base station, comprising a processor, a memory, and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the steps of the base station software version backoff control method according to any one of claims 1 to 8.
11. A readable storage medium storing one or more computer programs, the one or more computer programs being executable by one or more processors for implementing the steps of the base station software version backoff control method according to any one of claims 1 to 8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911008081.9A CN112702183A (en) | 2019-10-22 | 2019-10-22 | Method and device for controlling software version rollback of base station, base station and readable storage medium |
| PCT/CN2020/115493 WO2021077948A1 (en) | 2019-10-22 | 2020-09-16 | Base station software version rollback control method, apparatus, base station, and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911008081.9A CN112702183A (en) | 2019-10-22 | 2019-10-22 | Method and device for controlling software version rollback of base station, base station and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112702183A true CN112702183A (en) | 2021-04-23 |
Family
ID=75504976
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911008081.9A Pending CN112702183A (en) | 2019-10-22 | 2019-10-22 | Method and device for controlling software version rollback of base station, base station and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112702183A (en) |
| WO (1) | WO2021077948A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143619A (en) * | 2021-11-25 | 2022-03-04 | 新华三技术有限公司成都分公司 | Base station over-temperature protection method and device and electronic equipment |
| CN114500241A (en) * | 2022-04-15 | 2022-05-13 | 荣耀终端有限公司 | Abnormal reset processing method and terminal equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009109145A1 (en) * | 2008-03-07 | 2009-09-11 | 华为技术有限公司 | A method for improving the reliability of communication devices and an apparatus thereof |
| CN102483713A (en) * | 2009-08-04 | 2012-05-30 | 富士通株式会社 | Reset method and monitor |
| CN107548085A (en) * | 2016-06-24 | 2018-01-05 | 中兴通讯股份有限公司 | Base station edition backing method and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7043485B2 (en) * | 2002-03-19 | 2006-05-09 | Network Appliance, Inc. | System and method for storage of snapshot metadata in a remote file |
| CN1311337C (en) * | 2004-06-24 | 2007-04-18 | 华为技术有限公司 | Realization and maintainment for running mode of preventing apparatus |
| CN102164363B (en) * | 2011-04-14 | 2014-05-07 | 新邮通信设备有限公司 | Base station version updating realization method and base station |
| CN108008800B (en) * | 2017-11-29 | 2022-02-15 | 锐捷网络股份有限公司 | Reset request processing method, device and equipment |
-
2019
- 2019-10-22 CN CN201911008081.9A patent/CN112702183A/en active Pending
-
2020
- 2020-09-16 WO PCT/CN2020/115493 patent/WO2021077948A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009109145A1 (en) * | 2008-03-07 | 2009-09-11 | 华为技术有限公司 | A method for improving the reliability of communication devices and an apparatus thereof |
| CN102483713A (en) * | 2009-08-04 | 2012-05-30 | 富士通株式会社 | Reset method and monitor |
| CN107548085A (en) * | 2016-06-24 | 2018-01-05 | 中兴通讯股份有限公司 | Base station edition backing method and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143619A (en) * | 2021-11-25 | 2022-03-04 | 新华三技术有限公司成都分公司 | Base station over-temperature protection method and device and electronic equipment |
| CN114500241A (en) * | 2022-04-15 | 2022-05-13 | 荣耀终端有限公司 | Abnormal reset processing method and terminal equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021077948A1 (en) | 2021-04-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107515796B (en) | Equipment abnormity monitoring processing method and device | |
| CN107179957B (en) | Physical machine fault classification processing method and device and virtual machine recovery method and system | |
| CN105808394B (en) | Server self-healing method and device | |
| EP3617886A1 (en) | Hot backup system, hot backup method, and computer device | |
| CN103607297A (en) | Fault processing method of computer cluster system | |
| CN111796959B (en) | Self-healing method, device and system for host container | |
| CN111209110B (en) | Task scheduling management method, system and storage medium for realizing load balancing | |
| WO2021077948A1 (en) | Base station software version rollback control method, apparatus, base station, and readable storage medium | |
| CN105607973B (en) | Method, device and system for processing equipment fault in virtual machine system | |
| CN113434337B (en) | Retry strategy control method and device and electronic equipment | |
| CN111901176B (en) | Fault determination method, device, equipment and storage medium | |
| US9092396B2 (en) | Standby system device, a control method, and a program thereof | |
| TW201510995A (en) | Method for maintaining file system of computer system | |
| CN115470009B (en) | Memory resource management method, system, device and medium | |
| CN113778607A (en) | Method and device for realizing high availability of virtual machine, cloud management platform and storage medium | |
| CN111949384A (en) | Task scheduling method, device, equipment and computer readable storage medium | |
| CN115964142A (en) | Application service management method, device and storage medium | |
| CN112269693B (en) | Node self-coordination method, device and computer readable storage medium | |
| CN115686831A (en) | Task processing method and device based on distributed system, equipment and medium | |
| CN115686951A (en) | Fault processing method and device for database server | |
| CN111858183A (en) | Restarting method and apparatus for electronic device | |
| CN107783855B (en) | Fault self-healing control device and method for virtual network element | |
| CN114510433A (en) | Memory management method, device and storage medium for optical transmission device | |
| US11460910B2 (en) | Systems and methods for mitigating power failover | |
| CN109815064B (en) | Node isolation method, node isolation device, node equipment and computer readable storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210423 |