WO2017219574A1

WO2017219574A1 - Version rollback method and system for base station

Info

Publication number: WO2017219574A1
Application number: PCT/CN2016/103959
Authority: WO
Inventors: 贾杨威
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-06-24
Filing date: 2016-10-31
Publication date: 2017-12-28
Also published as: CN107548085A

Abstract

The present disclosure relates to a version rollback method and system for a base station. The version rollback method for a base station comprises: obtaining, upon upgrading a base station, a pre-upgrade state parameter and an upgraded state parameter of the base station; comparing the pre-upgrade state parameter to the upgraded state parameter and, after the upgrade determining whether the base station is abnormal; and if so, performing a version rollback operation on the base station. The usage of the present disclosure can improve the efficiency of troubleshooting the abnormal base station and the version rollback of the abnormal base station after the upgrade, reducing the maintenance costs of the base station and improving user experience.

Description

Base station version fallback method and system

Technical field

The present application relates to the field of communications, for example, to a base station version fallback system and method.

Background technique

At present, in the mobile communication network, the number of base stations is large, and the types of services supported may be different. For example, some base stations support GSM (Global System for Mobile communications) services, and some support UMTS (Universal). Mobile Telecommunications System (LTE) services, and some support LTE (Long Term Evolution), which is a long-term evolution of general mobile communication technology. The base stations and environments of different service types are also different. In this way, when the base station network management side upgrades all the base stations in a unified manner, even if the upgrade version used by the base station network management side is a general version, some of the upgraded base stations may still be abnormal when working, for example, after the base station is upgraded. A large number of alarms, degraded service quality, etc. At this point, you need to roll back the abnormal base station to the normal version before the upgrade. However, in the related art, the manual method is often used to check the abnormal base station, and the abnormal base station performs the version fallback operation one by one, and the work efficiency is extremely low, and the user experience is not good.

Summary of the invention

The technical problem to be solved by the present disclosure is how to automatically check whether the base station is abnormal after the base station is upgraded, and automatically perform the base station version rollback when the base station is abnormal, and improve the working efficiency of the abnormal base station check and the abnormal base station version fallback. Improve the user experience.

To solve the above technical problem, the present disclosure provides the following technical solutions:

In one aspect, the disclosure provides a base station version fallback method, where the base station version fallback method includes:

When the base station is upgraded, the status parameters of the base station before and after the upgrade are obtained respectively.

Comparing the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade; and

If an abnormality occurs, the base station performs a version rollback operation.

The status parameter may include an alarm generated by the base station before and after the upgrade, a KPI parameter, and a network element shape. The KPI parameter includes a call drop rate, and the network element status includes a board status.

When the status parameter is an alarm generated by the base station before and after the upgrade, the comparing the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade may include:

The alarms generated before and after the upgrade of the base station are compared with each other, and it is determined whether there is a new alarm that is different from the alarm type generated before the upgrade.

If the new alarm is present, it is counted whether the number of the new alarm exceeds a preset value; and

When the number of the new alarm exceeds a preset value, it is determined that the base station is abnormal after the upgrade.

If the primary key of the alarm generated after the upgrade is different from the primary key of the alarm generated before the upgrade, the alarm generated after the upgrade may be the new alarm.

When the status parameter is a KPI parameter of the base station before and after the upgrade, the step of acquiring the status parameters of the pre-upgrade and the upgraded state of the base station after the base station is upgraded may include:

After the base station is upgraded, the KPI parameter of the base station is obtained according to a preset frequency;

The step of comparing the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade includes:

Comparing the obtained KPI parameters with the KPI parameters before the base station upgrade, and determining whether the performance of the base station after the upgrade tends to decrease;

If the performance of the base station after the upgrade tends to decrease, it is determined that the base station is abnormal after the upgrade.

When the KPI parameter is the dropped call rate, if the dropped call rate of the upgraded base station is higher than or mostly higher than the dropped call rate before the upgrade, it can be determined that the performance of the base station after the upgrade tends to decrease.

When the status parameter is the network element status of the base station before and after the upgrade, the step of determining whether the base station is abnormal after the upgrade is performed by comparing the pre-upgrade and post-upgrade state parameters, and the method may include:

Compare the status of the NEs before and after the upgrade of the base station; and

When the state of the network element is inconsistent, it is determined that the base station is abnormal after the upgrade.

When the status of the network element is in the state of the board, the step of comparing the status of the network element before and after the upgrade of the base station is consistent, and the method may include:

Compare whether the board is in an occluded state or a de-blocked state before and after the base station is upgraded.

Compared with the related art, the base station version fallback method of the present disclosure determines whether an abnormality occurs after the base station is upgraded by comparing the status parameters of the base station before and after the upgrade, and automatically performs the base station version rollback operation when the base station is abnormal. The efficiency of abnormal base station troubleshooting and abnormal base station version rollback work is improved, the maintenance cost of the base station is reduced, and the user experience is improved.

In another aspect, the present disclosure provides a base station version fallback system, where the base station version fallback system includes:

The obtaining module is configured to obtain, before the base station is upgraded, the status parameters of the base station before and after the upgrade;

The comparison module is configured to compare the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade;

The fallback module is configured to perform a version rollback operation on the base station when an abnormality occurs.

The status parameter may include an alarm generated by the base station before and after the upgrade, a KPI parameter, and a network element status, where the KPI parameter includes a call drop rate, and the network element status includes a board status.

When the status parameter is an alarm generated by the base station before and after the upgrade, the comparison module may also be configured to:

Comparing the alarms generated before and after the upgrade of the base station, determining whether there is a new alarm that is different from the alarm type generated before the upgrade, and counting the number of the new alarms;

The comparison module may be configured to determine that the alarm generated after the upgrade is the new alarm when the primary key of the alarm generated after the upgrade is different from the primary key of the alarm generated before the upgrade.

When the state parameter is a KPI parameter of the base station before and after the upgrade, the acquiring module may be further configured to acquire a KPI parameter of the base station according to a preset frequency after the base station is upgraded;

The comparison module is further configured to compare the acquired KPI parameters with KPI parameters before the base station upgrade, determine whether the performance of the base station after the upgrade tends to decrease, and determine when the performance of the base station tends to decrease. The base station has an abnormality after the upgrade.

When the KPI parameter is the call drop rate, the comparison module may be further configured to determine that the base station is in the case where the dropped call rate of the upgraded base station is higher than or mostly higher than the call drop rate before the upgrade. Performance after the upgrade tends to decline.

When the status parameter is the network element status of the base station before and after the upgrade, the comparison module may be further configured to:

Compare the NE status of the base station before and after the upgrade of the base station;

When the state of the network element is in a state of a single board, the comparison module may be configured to compare whether the board is in an occlusion state or a de-blocking state before and after the base station is upgraded.

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing a computer Execution of instructions, the computer executable instructions being arranged to perform the above method.

The embodiment of the present disclosure further provides a base station, including:

At least one processor;

a memory communicatively coupled to the at least one processor; wherein

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.

Compared with the related art, the base station version fallback system of the present disclosure determines whether the base station is abnormal after the upgrade, and automatically performs the base station version rollback operation when the base station is abnormal, by comparing the state parameters of the base station before and after the upgrade. The efficiency of abnormal base station troubleshooting and abnormal base station version rollback work is improved, the maintenance cost of the base station is reduced, and the user experience is improved.

BRIEF abstract

FIG. 1 is a schematic diagram of an operating environment of an embodiment of a base station version fallback system according to the present disclosure.

2 is a functional block diagram of an embodiment of a base station version fallback system of the present disclosure.

3 is a flow chart of an implementation of an embodiment of a base station version fallback method of the present disclosure.

4 is a first detailed flowchart of step S102 of the embodiment of the base station version fallback method of the present disclosure.

FIG. 5 is a second detailed flowchart of step S102 of the embodiment of the base station version fallback method of the present disclosure.

FIG. 6 is a third refinement flowchart of step S102 of the embodiment of the base station version fallback method of the present disclosure.

Reference mark:

Embodiments of the invention

In order to make the technical solutions and advantages of the present disclosure more comprehensible, the present disclosure will be described in detail below with reference to the accompanying drawings and embodiments. The embodiments described herein are merely illustrative of the disclosure and are not intended to limit the disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without departing from the inventive scope are the scope of the disclosure.

The terms "first", "second", and the like, which are used in the present disclosure, are used for description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Thus, features defining "first" or "second" may include at least one of the features, either explicitly or implicitly. In addition, the technical solutions between the various embodiments may be combined with each other.

Referring to FIG. 1 , it is a schematic diagram of an operating environment of an embodiment of the base station version fallback system 10 of the present disclosure. In this embodiment, the base station version fallback system 10 is installed and operates in the base station 1. The base station 1 may be a base station supporting GSM (Global System for Mobile communications) services, or may be supported. The base station of the UMTS (Universal Mobile Telecommunications System) service may be a base station supporting LTE (Long Term Evolution) (Long Term Evolution) service. The base station 1 includes, but is not limited to, a memory 11, a processor 12, and a communication interface 13.

The memory 11 may be an internal storage unit of the base station 1, such as a hard disk or memory of the base station 1. The memory 11 may also be an external storage device of the base station 1, such as a plug-in hard disk equipped with the base station 1, an SMC card (Smart Media Card), and an SD card (Secure Digital: Secure Digital Card). FC card (Flash Card). The memory 11 may also include both an internal storage unit of the base station 1 and an external storage device. The memory 11 is configured to store application software and various types of data installed in the base station 1, for example, to store state parameters before and after the base station 1 is upgraded.

The processor 12 may be a Central Processing Unit (CPU), a microprocessor or other data processing chip configured to run program code or process data installed in the memory 11, such as executing The base station version backs up the system 10 and the like.

The communication interface 13 is configured to connect the base station 1 to a base station upgrade control end (the network management side of the present embodiment) through a wired network (for example, a fiber optic cable) or a wireless network (not shown in the figure). Establishing a communication connection between the base station 1 and the base station upgrade control terminal, so that data exchange between the base station 1 and the base station upgrade control end is facilitated, for example, downloading the base station 1 for upgrading from the base station upgrade control terminal Upgrade packages, etc.

The above components 11-13 of the base station 1 communicate with each other through a system bus.

Referring to FIG. 2, it is a functional block diagram of an embodiment of the base station version fallback system 10 of the present disclosure. In this embodiment, the base station version fallback system 10 may be divided into one or more modules, the one or more modules being stored in the memory 11 and being processed by one or more processors ( This embodiment is performed by the processor 12) to complete the present disclosure. For example, in FIG. 2, the base station version fallback system 10 can be divided into an acquisition module 21, a comparison module 22, and a fallback module 23. The functional modules referred to in the embodiments of the present disclosure refer to a series of computer program instruction segments capable of performing specific functions, which are more suitable than the program to describe the execution process of the base station version fallback system 10 in the base station 1. The function of each of the function modules 21-23 will be described in detail below.

The acquiring module 21 is configured to acquire the pre-upgrade and post-upgrade state parameters of the base station 1 when the base station 1 is upgraded. The parameters include, but are not limited to, alarms, KPI parameters, and network element status generated by the base station 1 before and after the upgrade. The KPI parameter may include a dropped call rate, etc., and the network element status may include a single board status or the like.

Under normal circumstances, the upgrade process of the base station 1 generally includes the steps of: upgrading the data packet downloading, entering the upgrade mode, configuring the data upgrade, configuring the data backup, pre-activation, activation, version verification, exiting the upgrade mode, and confirming after the upgrade. In addition, when the base station upgrade control end performs a unified batch upgrade of a batch of base stations 1, the base station upgrade control end generally sends a corresponding upgrade command to the base station 1 in advance, and the upgrade command includes an upgrade data packet version and a preset upgrade. Information such as time is used to inform the base station 1 to download the upgrade data packet of the version from the upgrade control terminal in advance, and perform upgrade at the preset upgrade time. Therefore, in this embodiment, the acquiring module 21 may acquire the state parameter of the base station 1 before the upgrade time, that is, the state parameter before the base station 1 is upgraded, according to the preset upgrade time; After the upgrade time or after the upgrade of the base station 1 is completed, the state parameter of the base station 1 is obtained, that is, the state parameter after the base station 1 is upgraded. After acquiring the state parameters of the base station 1 before and after the upgrade, the acquiring module 21 stores the state parameters in the memory 11 of the base station 1.

The comparison module 22 is configured to compare the pre-upgrade and post-upgrade state parameters of the base station 1 to determine whether the base station 1 has an abnormality after the upgrade.

Under normal circumstances, the base station upgrade control end performs batch upgrade on the base station 1 to improve the base station 1 Work efficiency and improve the service quality of the communication network. Therefore, if the upgraded base station 1 has a lower working efficiency and a lower service quality, it can be determined that the base station 1 has an abnormality after the upgrade, and a version rollback operation is required.

Generally, before the base station 1 is abnormal, resulting in a decrease in work efficiency and a decrease in service quality, the following three situations generally occur in the base station 1: First, a large number of alarms are added in the base station 1, and the alarms are It is a type that has not appeared before (indicating that the base station 1 has a new problem that has not appeared before); second, the KPI (Key Performance Indicator) parameter of the base station 1 increases or decreases, and the performance of the base station 1 is earlier than that of the previous one. There is a decrease, such as a drop in call rate, a decrease in handover success rate, etc. Third, the state of the network element of the base station 1 changes (the upgrade generally does not change the state of the network element in the base station 1), for example, the cell within the coverage of the base station 1. The position coordinates are changed from before, and the state of the board of the base station 1 is changed from the blocked state to the unblocked state. Therefore, in this embodiment, the comparison module 22 can start according to the above three situations to determine whether the base station 1 has an abnormality after the upgrade.

First, if the state parameter of the base station 1 acquired by the acquiring module 21 is an alarm generated by the base station 1 before and after the upgrade, the comparison module 22 may acquire the base station 1 from the base station 1 before and after the upgrade. The generated alarm is compared with the pre-upgrade alarm of the obtained base station 1 to determine whether there is an alarm that is different from the type of the pre-upgrade alarm. And when there is an alarm that is different from the type of the pre-upgrade alarm in the post-upgrade alarm, the number of new types of alarms is counted. If the number of the new types of alarms exceeds a preset value (for example, 10) within a preset time (for example, 1 hour), the comparison module 22 determines that the base station 1 is abnormal, and needs Perform a version rollback operation. In this embodiment, the alarm includes a primary key, and if the primary keys are the same, the types of the alarms are the same. Therefore, the comparison module 22 can determine whether there is an alarm in the upgraded alarm that is different from the type of the pre-upgrade alarm by comparing the difference between the primary keys.

Second, if the state parameter of the base station 1 acquired by the acquiring module 21 is the KPI parameter of the base station 1 before and after the upgrade, the comparison module 22 may press the preset frequency after the base station 1 is upgraded (for example, Obtaining the KPI parameter of the base station 1 every 5 minutes, and comparing the acquired KPI parameters with the obtained KPI parameters before the base station 1 is upgraded, and determining whether the performance of the base station 1 after the upgrade is based on the comparison result. If the performance of the base station 1 is upgraded and the upgrade is not as good as before the upgrade, the comparison module 22 can determine that the base station 1 is abnormal after the upgrade, and a version rollback operation is required.

In this embodiment, the KPI parameter refers to a set of internal performance indicator parameters of the base station 1, which may be It can be a performance indicator parameter, such as call drop rate or handover success rate, or multiple performance indicator parameters, such as call drop rate and handover success rate. When the KPI parameters are different index parameters, it is not possible to judge whether the performance of the base station 1 tends to decrease only by the magnitude of the value. Whether the KPI parameter value is increased or decreased, it is possible that the performance of the base station 1 tends to decrease. For example, if the KPI parameter is the dropped call rate of the base station 1, it is obvious that the lower the dropped call rate, the better the performance of the base station 1, and the higher the call drop rate, the worse the performance. Therefore, if the dropped call rate obtained after the base station 1 is upgraded is lower than the dropped call rate before the upgrade (for example, the call drop rate before the upgrade is 5.1%, the dropped call rate is 4%, etc.) or most of the drop rate. The remaining part is flat (for example, the call drop rate before the upgrade is 5.0%, the dropped call rate of the upgraded part is 5.1%, and the rest is 4.9%, etc.), and the comparison module 22 can directly determine that the base station 1 is normal, and the version is not required. Roll back operation. Conversely, if the dropped call rate obtained after the base station 1 is upgraded is significantly higher than the dropped call rate before the upgrade (for example, the call drop rate before the upgrade is 5.1%, the dropped call rate is 8%, etc.) or Most of the significant increase (for example, the call drop rate before the upgrade is 5.1%, the partial call drop rate after the upgrade is 8%, and the rest is 5.2%, etc.), the comparison module 22 can directly determine that the base station 1 is abnormal, and needs to Perform a version rollback operation. Compared with the dropped call rate, if the KPI parameter is the handover success rate of the base station 1, it is obvious that the higher the handover success rate, the better the performance of the base station 1, and the lower the handover success rate, the worse the performance. Therefore, if the handover success rate obtained after the base station 1 is upgraded is lower than the handover success rate before the upgrade, the same as the above-mentioned call drop rate (for example, the handover success rate before the upgrade is 5.1%, and the upgrade success rate after the upgrade is 4). %, etc., the comparison module 22 can directly determine that the base station 1 is abnormal, and needs to perform a version fallback operation. On the other hand, if the handover success rate obtained after the upgrade of the base station 1 is higher than the handover success rate before the upgrade (for example, the handover success rate before the upgrade is 5.1%, and the upgrade success rate after the upgrade is 8%, etc.), The comparison module 22 can directly determine that the base station 1 is normal and does not need to perform a version rollback operation. The KPI parameter of this embodiment is not limited to the above-mentioned call drop rate or handover success rate, and the KPI parameter may also be any suitable parameter. Moreover, generally, if the KPI parameter of the base station changes little, for example, the call drop rate changes from 5% to 5.1%, the KPI parameter can be considered as a normal fluctuation, and within the acceptable range, the default is the KPI parameter. normal.

Then, if the state parameter of the base station 1 acquired by the acquiring module 21 is the network element state of the base station 1 before and after the upgrade, the comparison module 22 may compare the base station 1 after the base station 1 is upgraded. Whether the state of the network element is consistent, and when the state of the network element is inconsistent, it is determined that the base station 1 is abnormal after the upgrade. The state of the network element in this embodiment refers to the hardware state inside the base station 1 or the division of the working area of the base station 1. The hardware state of the base station 1 includes whether the working state of the board in the base station 1 is an occlusion state or a occlusion state, and the working area division of the base station 1 includes a cell identifier, a location coordinate, and the like of a cell in the working area. . Under normal circumstances, the base station 1 upgrade will not change. If the status of the network element changes before and after the base station 1 changes, the comparison module 22 can determine that the base station 1 is abnormal and needs to perform a version rewind operation.

The fallback module 23 is configured to perform a version fallback operation on the base station 1 when the base station 1 is abnormal after the upgrade.

In this embodiment, before the base station 1 performs the upgrade, the current version of the base station 1 is backed up in its memory 11 in advance, and the backup is used to perform the version of the base station 1 when an abnormality occurs after the base station 1 is upgraded. In the rollback operation, the base station 1 is restored to the normal version before the upgrade, so that the base station 1 works normally. The related backup or restore method is a relatively mature related technology, and will not be described here.

Through the foregoing modules 21-23, the base station version fallback system 10 according to the embodiment of the present disclosure determines whether the base station 1 is abnormal after the upgrade by comparing the state parameters of the base station 1 before and after the upgrade, and automatically executes when the base station 1 is abnormal. The operation of the base station version rollback improves the efficiency of abnormal base station troubleshooting and abnormal base station version rollback after the upgrade, reduces the maintenance cost of the base station, and improves the user experience.

Referring to FIG. 3, it is a schematic flowchart of an implementation manner of an embodiment of a base station version fallback method according to the present disclosure. In this embodiment, the order of execution of the steps in the flowchart shown in FIG. 3 may be changed according to different requirements, and some steps may be omitted.

In step S101, when the base station 1 is upgraded, the state parameters of the base station 1 before and after the upgrade are respectively acquired. The parameters include, but are not limited to, alarms, KPI parameters, and network element status generated by the base station 1 before and after the upgrade. The KPI parameter may include a dropped call rate, etc., and the network element status may include a single board status or the like.

Under normal circumstances, the upgrade process of the base station 1 generally includes the steps of: upgrading the data packet downloading, entering the upgrade mode, configuring the data upgrade, configuring the data backup, pre-activation, activation, version verification, exiting the upgrade mode, and confirming after the upgrade. In addition, when the base station upgrade control end performs a unified batch upgrade of a batch of base stations 1, the base station upgrade control end generally sends a corresponding upgrade command to the base station 1 in advance, and the upgrade command includes an upgrade data packet version and a preset upgrade. Information such as time is used to inform the base station 1 to download the upgrade data packet of the version from the upgrade control terminal in advance, and perform upgrade at the preset upgrade time. Therefore, in this embodiment, the state parameter of the base station 1 is obtained before the upgrade time according to the preset upgrade time, that is, the state parameter before the base station 1 is upgraded, and after the upgrade time or After the upgrade of the base station 1 is completed, the state parameter of the base station 1 is obtained, that is, the state parameter after the base station 1 is upgraded, and the state parameters of the base station 1 before and after the upgrade are obtained. In the memory 11.

Step S102, the base station 1 compares the pre-upgrade and post-upgrade state parameters, and determines that the base station 1 is Whether an exception occurred after the upgrade. If the base station 1 is abnormal after the upgrade, step S103 is performed; if the base station 1 does not have an abnormality after the upgrade, the process ends.

As shown in FIG. 4, in the embodiment, when the state parameter of the base station 1 is an alarm generated by the base station 1 before and after the upgrade, the step S102 further includes the following refinement steps:

Step S201: After the base station 1 is upgraded, the alarm generated in the base station 1 is obtained. If the alarm is obtained, the process proceeds to step S202. If the alarm is not obtained, the process ends.

Step S202: Comparing the obtained post-upgrade alarms of the base station 1 with the pre-upgrade alarms, and determining whether the types of the upgraded alarms are the same as the types of the pre-upgrade alarms. If the type of the alarm is the same as that of the pre-upgrade alarm, step S203 is performed; if the type of the upgraded alarm is the same as the type of the pre-upgrade alarm, the process ends. In this embodiment, the alarm includes a primary key, and if the primary keys are the same, the types of the alarms are the same.

In step S203, the number of the alarms in the upgraded alarms is different from that of the pre-upgrade alarms, and the number of alarms is determined to be greater than a preset value. If the preset value is exceeded, step S204 is performed; If the preset value is not exceeded, the process ends.

In step S204, it is determined that an abnormality occurs after the base station 1 is upgraded.

As shown in FIG. 5, in the embodiment, when the state parameter of the base station 1 is the KPI parameter of the base station 1 before and after the upgrade, the step S102 further includes the following refinement steps:

Step S301, after the base station 1 is upgraded, obtain the KPI parameter of the base station 1 according to a preset frequency (for example, once every 5 minutes), and compare the acquired KPI parameters with the obtained KPI parameters before the base station 1 is upgraded. Correct.

In step S302, it is determined whether the performance of the base station 1 after the upgrade tends to decrease according to the comparison result; if the performance tends to decrease, the process proceeds to step S303; if the performance does not tend to decrease, the process ends.

In this embodiment, the KPI parameter refers to a set of internal performance indicator parameters of the base station 1, which may be a performance indicator parameter, such as a call drop rate or a handover success rate, or may be multiple performance indicator parameters, such as Call rate and handover success rate. When the KPI parameters are different index parameters, it is not possible to judge whether the performance of the base station 1 tends to decrease only by the magnitude of the value. Whether the KPI parameter value is increased or decreased, it is possible that the performance of the base station 1 tends to decrease. For example, if the KPI parameter is the dropped call rate of the base station 1, it is obvious that the lower the dropped call rate, the better the performance of the base station 1, and the higher the call drop rate, the worse the performance. Therefore, if the dropped call rate obtained after the base station 1 is upgraded is lower than the dropped call rate before the upgrade (for example, the call drop rate before the upgrade is 5.1%, the dropped call rate is 4%, etc.) or most of the drop rate. The rest is flat (for example, the call drop rate before the upgrade is 5.0%, and the call drop rate after the upgrade is 5.1%. If the rest is 4.9%, etc., it can be directly determined that the base station 1 is normal, and no version retraction operation is required. Conversely, if the dropped call rate obtained after the base station 1 is upgraded is significantly higher than the dropped call rate before the upgrade (for example, the call drop rate before the upgrade is 5.1%, the dropped call rate is 8%, etc.) or Most of the significant increase (for example, the call drop rate before the upgrade is 5.1%, the partial call drop rate after the upgrade is 8%, and the rest is 5.2%, etc.), then the base station 1 can be directly determined to be abnormal, and the version fallback operation is required. Compared with the dropped call rate, if the KPI parameter is the handover success rate of the base station 1, it is obvious that the higher the handover success rate, the better the performance of the base station 1, and the lower the handover success rate, the worse the performance. Therefore, if the handover success rate obtained after the base station 1 is upgraded is lower than the handover success rate before the upgrade, the same as the above-mentioned call drop rate (for example, the handover success rate before the upgrade is 5.1%, and the upgrade success rate after the upgrade is 4). %, etc., it can be directly determined that the base station 1 is abnormal, and a version rollback operation is required. On the other hand, if the handover success rate obtained after the upgrade of the base station 1 is higher than the handover success rate before the upgrade (for example, the handover success rate before the upgrade is 5.1%, and the upgrade success rate after the upgrade is 8%, etc.), It is directly determined that the base station 1 is normal, and no version retracting operation is required. The KPI parameter of this embodiment is not limited to the above-mentioned call drop rate or handover success rate, and the KPI parameter may also be any suitable parameter. Moreover, generally, if the KPI parameter of the base station changes little, for example, the call drop rate changes from 5% to 5.1%, the KPI parameter can be considered as a normal fluctuation, and within the acceptable range, the default is the KPI parameter. normal.

In step S303, it is determined that an abnormality occurs after the base station 1 is upgraded. As shown in FIG. 6, in the embodiment, when the state parameter of the base station 1 is the network element state of the base station 1 before and after the upgrade, the step S102 further includes the following refinement steps:

Step S401: After the base station 1 is upgraded, obtain the network element status of the base station 1.

In step S402, it is compared with whether the state of the network element before and after the upgrade of the base station 1 is consistent. If not, the process proceeds to step S403; if not, the process ends.

In step S403, it is determined that an abnormality occurs after the base station 1 is upgraded.

The state of the network element in this embodiment refers to the hardware state inside the base station 1 or the division of the working area of the base station 1. The hardware state of the base station 1 includes whether the working state of the board in the base station 1 is an occlusion state or a occlusion state. The working area division of the base station 1 includes a cell identifier, a location coordinate, and the like in the working area. In general, the upgrade of the base station 1 does not change the state of the network element. Therefore, if the state of the network element before and after the upgrade of the base station 1 changes, it can be determined that the base station 1 is abnormal, and a version retraction operation is required.

In step S103, when the base station 1 is abnormal after the upgrade, the base station 1 performs a version rewind operation. In this embodiment, before the base station 1 performs the upgrade, the base station 1 is previously in the memory 11 thereof. The current version has been backed up. This backup is used to perform a version rollback operation on the base station 1 when the base station 1 is abnormal. The base station 1 is restored to the normal version before the upgrade, so that the base station 1 can work normally. The related backup or restore method is a relatively mature related technology, and will not be described here.

Through the foregoing steps S101-S103, the base station version fallback method according to the embodiment of the present disclosure determines whether the base station 1 is abnormal after the upgrade by comparing the state parameters of the base station 1 before and after the upgrade, and automatically performs the base station when the base station 1 is abnormal. The operation of the 1 version rollback improves the efficiency of abnormal base station troubleshooting and abnormal base station version rollback after the upgrade, reduces the maintenance cost of the base station 1, and improves the user experience.

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of the above embodiments.

In addition, in other embodiments, the base station 1 shown in FIG. 1 may include at least one processor 12, which is exemplified by one processor 12 in FIG. 1; and a memory 11 may further include a communication interface ( Communications Interface 13 and bus 14. The processor 12, the communication interface 13, and the memory 11 can complete communication with each other through the bus 14. The communication interface 13 can be used for information transmission. The processor 12 can call the logic instructions in the memory 11 to perform the method of the above embodiments.

Furthermore, the logic instructions in the memory 11 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.

The memory 11 is a computer readable storage medium and can be used to store software programs, computer executable programs, and program instructions/modules corresponding to the methods in the embodiments of the present disclosure. The processor 12 performs the function application and the data processing by running the software program, the instruction and the module stored in the memory 11, that is, the base station version fallback method in the foregoing method embodiment.

The memory 11 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 11 may include a high speed random access memory, and may also include a nonvolatile memory.

The technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like. A medium that can store program code, or a transitory storage medium.

The above description is only for the embodiments of the present disclosure, and is not intended to limit the disclosure. Any changes or substitutions that are obvious to those skilled in the art within the scope of the present disclosure are intended to be included within the scope of the present disclosure.

Industrial applicability

The disclosure improves the efficiency of the abnormal base station troubleshooting work and the abnormal base station version retreat work after the upgrade, reduces the maintenance cost of the base station, and improves the user experience.

Claims

A base station version fallback method includes:

When the base station is upgraded, the status parameters of the base station before and after the upgrade are obtained respectively.

Comparing the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade; and

If an abnormality occurs, the base station performs a version rollback operation.
The method of claim 1, wherein the status parameter comprises an alarm generated by the base station before and after the upgrade, a KPI parameter, and a network element status, wherein the KPI parameter includes a dropped call rate, and the network element status includes a single Board status.
The method of claim 2, wherein when the status parameter is an alarm generated by the base station before and after the upgrade, comparing the pre-upgrade and post-upgrade state parameters, determining whether the base station is abnormal after the upgrade The steps include:

The alarms generated before and after the upgrade of the base station are compared with each other, and it is determined whether there is a new alarm that is different from the alarm type generated before the upgrade.

If the new alarm is present, it is counted whether the number of the new alarm exceeds a preset value; and

When the number of the new alarm exceeds a preset value, it is determined that the base station is abnormal after the upgrade.
The method of claim 3, wherein if the primary key of the alarm generated after the upgrade is different from the primary key of the alarm generated before the upgrade, the alarm generated after the upgrade is the new alarm.
The method of claim 2, wherein when the state parameter is a KPI parameter of the base station before and after the upgrade, the step of acquiring the pre-upgrade and post-upgrade state parameters of the base station when upgrading the base station includes:

After the base station is upgraded, the KPI parameter of the base station is obtained according to a preset frequency;

The step of comparing the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade includes:

Comparing the obtained KPI parameters with the KPI parameters before the base station upgrade, and determining whether the performance of the base station after the upgrade tends to decrease;

If the performance of the base station after the upgrade tends to decrease, it is determined that the base station is abnormal after the upgrade.
The method according to claim 5, wherein when the KPI parameter is a dropped call rate, if the dropped call rate of the upgraded base station is higher than or mostly higher than the dropped call rate before the upgrade, the base station is determined to be Performance after the upgrade tends to decline.
The method of claim 2, wherein said state parameter is before and after the base station is upgraded In the state of the network element, the comparing the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade includes:

Compare the status of the NEs before and after the upgrade of the base station; and

When the state of the network element is inconsistent, it is determined that the base station is abnormal after the upgrade.
The method of claim 7, wherein the step of comparing the state of the network element before and after the upgrade of the base station to the base station comprises:

Compare whether the board is in an occluded state or a de-blocked state before and after the base station is upgraded.
A base station version fallback system includes:

The obtaining module is configured to obtain, before the base station is upgraded, the status parameters of the base station before and after the upgrade;

The comparison module is configured to compare the pre-upgrade and post-upgrade state parameters to determine whether the base station is abnormal after the upgrade;

The fallback module is configured to perform a version rollback operation on the base station when an abnormality occurs.
The system of claim 9, wherein the status parameter comprises an alarm generated by the base station before and after the upgrade, a KPI parameter, and a network element status, wherein the KPI parameter includes a call drop rate, and the network element status includes a single Board status.
The system of claim 10, wherein when the status parameter is an alarm generated by the base station before and after the upgrade, the comparison module is further configured to:

Comparing the alarms generated before and after the upgrade of the base station, determining whether there is a new alarm that is different from the alarm type generated before the upgrade, and counting the number of the new alarms;

When the number of the new alarm exceeds a preset value, it is determined that the base station is abnormal after the upgrade.
The system of claim 11, wherein the comparison module is further configured to determine that the upgrade is generated after the primary key of the alarm generated after the upgrade is different from the primary key of the alarm generated before the upgrade. The alarm is the new alarm.
The system of claim 10, wherein when the state parameter is a KPI parameter of the base station before and after the upgrade, the acquiring module is further configured to acquire the base station according to a preset frequency after the base station is upgraded. KPI parameter;

The comparison module is further configured to compare the acquired KPI parameters with KPI parameters before the base station upgrade, determine whether the performance of the base station after the upgrade tends to decrease, and determine when the performance of the base station tends to decrease. The base station has an abnormality after the upgrade.
The system of claim 13 wherein when said KPI parameter is a call drop rate, The comparison module is further configured to determine that the performance of the base station after the upgrade tends to decrease when the dropped call rate of the upgraded base station is higher than or mostly higher than the call drop rate before the upgrade.
The system of claim 10, wherein when the status parameter is a network element status of the base station before and after the upgrade, the comparison module is further configured to:

Compare the NE status of the base station before and after the upgrade of the base station;

When the state of the network element is inconsistent, it is determined that the base station is abnormal after the upgrade.
The system of claim 15, wherein the comparison module is further configured to compare whether the board is in an occlusion state or a solution before and after the base station is upgraded, when the state of the network element is a board. Occlusion state.
A non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of claims 1-8.