Network element upgrading method, device, equipment, storage medium and program product

Abstract

The application discloses a network element upgrading method and device, equipment, a storage medium and a program product. The method comprises the following steps: receiving an upgrading request sent by a user; in response to the upgrading request, starting a preset network upgrading workflow of a target network element, the network upgrading workflow is used for scheduling a network upgrading task, the network upgrading task comprises an upgrading implementation subtask, and the target network element is a network element corresponding to a target network element type and a target network element name in at least one network element of the network; according to the network upgrading workflow, the upgrading implementation subtask is scheduled and executed, and the upgrading implementation subtask is used for instructing a target upgrading software package to be deployed on the target network element in an upgrading time period, the target upgrading software package is an upgrading software package corresponding to a target upgrading software version number in a preset software package library, the software package library comprises at least one upgrading software package and an upgrading software version number corresponding to each software upgrading package, and different upgrading software packages correspond to different upgrading software version numbers.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a network element upgrading method, device, equipment, storage medium and program product. BACKGROUND

[0002] With the continuous development and innovation of communication technology, communication networks need to continuously upgrade network equipment, improve network coverage, increase bandwidth and speed to ensure the stability and reliability of the network. Through network upgrading, communication networks can better meet the communication needs of users to provide higher quality services. There are many network elements involved in the upgrading of the network, and the software version of the network element upgrading is developed by the equipment manufacturer according to the 3rd Generation Partnership Project (3GPP) and the principles of the operator routing organization, and is deployed in the corresponding network element, thereby realizing the upgrading of the network. However, the existing deployment process of the software version of the network element is mainly completed by manual operation, which has a high risk of manual operation error, resulting in low reliability of software version deployment. SUMMARY

[0003] The embodiments of the present application provide a network element upgrading method, device, equipment, storage medium and program product, which can reduce the risk of manual operation error and improve the reliability of network element upgrading package deployment.

[0004] In a first aspect, the embodiments of the present application provide a network element upgrading method, which comprises:

[0005] receiving an upgrading request sent by a user, the upgrading request comprising a target network element type, a target network element name, a target upgrading software version number and an upgrading time period;

[0006] in response to the upgrading request, starting a preset network upgrading workflow of a target network element, the network upgrading workflow being used to schedule a network upgrading task, the network upgrading task comprising an upgrading implementation subtask, the target network element being a network element corresponding to the target network element type and the target network element name in at least one network element of the network, different network elements corresponding to different network element types and different network element names;

[0007] scheduling and executing the upgrading implementation subtask according to the network upgrading workflow, the upgrading implementation subtask being used to instruct a target upgrading software package to be deployed in the target network element in the upgrading time period, the target upgrading software package being an upgrading software package corresponding to the target upgrading software version number in a preset software package library, the software package library comprising at least one upgrading software package and an upgrading software version number corresponding to each software upgrading package, different upgrading software packages corresponding to different upgrading software version numbers.

[0008] In a second aspect, an embodiment of the present application provides a network element upgrading apparatus, the apparatus comprising:

[0009] a receiving module configured to receive an upgrading request sent by a user, the upgrading request comprising a target network element type, a target network element name, a target upgrading software version number, and an upgrading time period;

[0010] a starting module configured to start a preset network upgrading workflow of a target network element in response to the upgrading request, the network upgrading workflow being configured to schedule a network upgrading task, the network upgrading task comprising an upgrading implementation subtask, the target network element being a network element corresponding to the target network element type and the target network element name among at least one network element of a network, different network elements corresponding to different network element types and different network element names;

[0011] a first executing module configured to schedule and execute the upgrading implementation subtask according to the network upgrading workflow, the upgrading implementation subtask being configured to instruct a target upgrading software package to be deployed on the target network element in the upgrading time period, the target upgrading software package being an upgrading software package corresponding to the target upgrading software version number in a preset software package library, the software package library comprising at least one upgrading software package and an upgrading software version number corresponding to each of the software upgrading packages, different upgrading software packages corresponding to different upgrading software version numbers.

[0012] In a third aspect, an embodiment of the present application provides an electronic device, the device comprising a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the network element upgrading method according to any one of the preceding aspects.

[0013] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing computer program instructions, the computer program instructions being executed by a processor to implement the network element upgrading method according to any one of the preceding aspects.

[0014] In a fifth aspect, an embodiment of the present application provides a computer program product, instructions in the computer program product being executed by a processor of an electronic device to cause the electronic device to perform the network element upgrading method according to any one of the preceding aspects.

[0015] The network element upgrading method, device, equipment, storage medium and program product provided by the embodiments of the present application can receive an upgrading request sent by a user, the upgrading request comprising a target network element type, a target network element name, a target upgrading software version number and an upgrading time period; in response to the upgrading request, a preset network upgrading workflow of a target network element is started, the network upgrading workflow being used to schedule a network upgrading task, the network upgrading task comprising an upgrading implementation subtask, the target network element being a network element corresponding to the target network element type and the target network element name among at least one network element of a network, different network elements corresponding to different network element types and different network element names; according to the network upgrading workflow, the upgrading implementation subtask is scheduled and executed, the upgrading implementation subtask being used to instruct a target upgrading software package to be deployed on the target network element in the upgrading time period, the target upgrading software package being an upgrading software package corresponding to the target upgrading software version number in a preset software package library, the software package library comprising at least one upgrading software package and an upgrading software version number corresponding to each software upgrading package, different upgrading software packages corresponding to different upgrading software version numbers. In this way, the embodiments of the present application can, in response to the upgrading request, start the preset network upgrading workflow of the target network element, schedule and execute the upgrading implementation subtask according to the network upgrading workflow, and automatically deploy the target upgrading software package corresponding to the target upgrading software version number into the target network element corresponding to the target network element type and the target network element name, so as to reduce the risk of misoperation of manual deployment and improve the reliability of network element upgrading package deployment. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly introduced as follows, and other drawings can also be obtained by those of ordinary skill in the art without creative labor on the premise of not paying creative labor.

[0017] Figure 1 FIG. 1 is a flow diagram of a network element upgrading method provided by the embodiments of the present application;

[0018] Figure 2 FIG. 2 is an automatic upgrading architecture diagram based on task scheduling provided by the embodiments of the present application;

[0019] Figure 3 FIG. 3 is an automatic upgrading workflow diagram provided by the embodiments of the present application;

[0020] Figure 4 FIG. 4 is a structural diagram of a network element upgrading device provided by the embodiments of the present application;

[0021] Figure 5 FIG. 5 is a structural diagram of an electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0022] The features and exemplary embodiments of the various aspects of the present application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended to explain the principles of the present application, but are not intended to limit the present application. The present application can be implemented without some of the specific details, which are well known to those skilled in the art. The following description of the embodiments is merely provided to better illustrate the present application by showing examples of the present application.

[0023] It should be noted that, in this paper, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the elements defined by the statement "include" do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0024] With the continuous development and innovation of communication technology, communication networks need to upgrade network equipment, improve network coverage, increase bandwidth and speed to ensure the stability and reliability of the network. Through network upgrade, communication networks can better meet the communication needs of users to provide higher quality services. There are many network elements involved in the upgrade of the network, and the software version of the network element upgrade is developed by the equipment manufacturer according to the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) and the principles of operator routing organization, and is deployed to the corresponding network element, so as to realize the upgrade of the network. However, the deployment process of the existing network element software version is mainly completed by manual operation, which has a high risk of manual operation error, resulting in low reliability of software version deployment.

[0025] In order to solve the technical problems of the prior art, the embodiments of the present application provide a network element upgrade method, device, equipment, storage medium and program product. First, the network element upgrade method provided by the embodiments of the present application will be introduced.

[0026] Figure 1 The flowchart of the network element upgrade method provided by an embodiment of the present application is shown. As shown in Figure 1 The network element upgrade method can include the following steps S101-S103:

[0027] S101, receive an upgrade request sent by a user, the upgrade request comprising a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period;

[0028] S102, in response to the upgrade request, start a preset network upgrade workflow of the target network element, the network upgrade workflow being used to schedule a network upgrade task, the network upgrade task comprising an upgrade implementation subtask, the target network element being a network element corresponding to the target network element type and the target network element name among at least one network element of the network, different network elements corresponding to different network element types and different network element names;

[0029] S103, schedule and execute the upgrade implementation subtask according to the network upgrade workflow, the upgrade implementation subtask being used to instruct a target upgrade software package to be deployed on the target network element in the upgrade time period, the target upgrade software package being an upgrade software package corresponding to the target upgrade software version number in a preset software package library, the software package library comprising at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, different upgrade software packages corresponding to different upgrade software version numbers.

[0030] The network element upgrade method of the embodiments of the present application can receive an upgrade request sent by a user, the upgrade request comprising a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period; in response to the upgrade request, start a preset network upgrade workflow of the target network element, the network upgrade workflow being used to schedule a network upgrade task, the network upgrade task comprising an upgrade implementation subtask, the target network element being a network element corresponding to the target network element type and the target network element name among at least one network element of the network, different network elements corresponding to different network element types and different network element names; schedule and execute the upgrade implementation subtask according to the network upgrade workflow, the upgrade implementation subtask being used to instruct a target upgrade software package to be deployed on the target network element in the upgrade time period, the target upgrade software package being an upgrade software package corresponding to the target upgrade software version number in a preset software package library, the software package library comprising at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, different upgrade software packages corresponding to different upgrade software version numbers. In this way, the embodiments of the present application can, in response to the upgrade request, start a preset network upgrade workflow of the target network element, schedule and execute the upgrade implementation subtask according to the network upgrade workflow, and automatically deploy a target upgrade software package corresponding to the target upgrade software version number to a target network element corresponding to the target network element type and the target network element name, so as to reduce the risk of misoperation of manual deployment and improve the reliability of network element upgrade package deployment.

[0031] The specific implementation modes of the above steps are described below.

[0032] In S101, the above upgrade request can comprise a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period.

[0033] The network element type refers to different functional units or devices in the network, which are classified according to their roles and functional characteristics in the network. Common network element types include Access and Mobility Management Function (AMF), Session Management Function (SMF), The User plane Function (UPF), The Network Slice Selection Function (NSSF), Policy Control Function (PCF), and other core network devices.

[0034] The network element name refers to the naming method or identifier used to identify and distinguish different network elements in the network. It is usually an identifier used by network management systems or protocols to uniquely identify each network element in the network.

[0035] The upgrade software version number is a set of numbers and letters used to identify and distinguish different versions of upgrade software. Typically, the upgrade software version number includes major version number, minor version number, revision number, and other parts. Each time the software is updated or a new version is released, the developer will update one of the parts of the version number according to the improvements or modifications to the software, so that users and developers can clearly understand the updates and differences between different versions. The format and rules of the upgrade software version number may vary depending on the software developer or project.

[0036] The upgrade time period can include the upgrade start time and the upgrade end time. For example, the upgrade time period can be from 2:00 AM to 4:00 AM.

[0037] The upgrade request sent by the user can be, for example, a request triggered by the user inputting the target network element type, target network element name, target upgrade software version number, and upgrade time period into the upgrade work order.

[0038] In S102, the network can be, for example, a 4G or 5G core network. The 4G and 5G core network is a key part of the mobile communication network, responsible for handling user data transmission, signaling control, user identity recognition, and security authentication functions. The core network is the hub of the entire mobile communication network, connecting communication traffic between mobile devices and the Internet.

[0039] The network includes at least one network element, which is short for network element, refers to various devices, components or nodes in the network, functional units for transmitting, exchanging, processing and managing data. In a communication network, network elements include routers, switches, servers, firewalls and other devices, which form a complete network system through interconnection. Network elements can be hardware, software, or a combination of both. In traditional communication networks, network elements usually refer to hardware devices such as routers, switches, etc., for processing data packet forwarding, signal transmission, etc. With the development of network technology, the rise of concepts such as virtualization and software-defined network (Software-Defined Networking, SDN), network elements can also be virtual devices in the form of software, which realize network functions through software running on general servers. Therefore, network elements can be hardware, software, or a combination of both, depending on the architecture and technology development of the network.

[0040] The target network element is a network element corresponding to the target network element type and the target network element name in at least one network element of the network. Different network elements correspond to different network element types and different network element names.

[0041] The network upgrade workflow can be used to schedule network upgrade tasks. The network upgrade task can include an upgrade implementation subtask, wherein the upgrade implementation subtask is used to indicate that the target upgrade software package is deployed on the target network element in the upgrade time period.

[0042] In S103, the target upgrade software package is an upgrade software package corresponding to the target upgrade software version number in a preset software package library. The software package library can include at least one upgrade software package and the upgrade software version number corresponding to each software upgrade package. Different upgrade software packages correspond to different upgrade software version numbers.

[0043] In some embodiments, the execution of the upgrade implementation subtask can specifically include:

[0044] Setting the configuration item of the target network element to a preset first parameter;

[0045] Releasing the coupling and session of the target network element;

[0046] According to the target upgrade software version number, the target upgrade software package is obtained from the software package library;

[0047] Deploying the target upgrade software package on the target network element in the upgrade time period;

[0048] Restarting the target network element;

[0049] Setting the configuration item of the target network element to a preset second parameter.

[0050] The configuration item of the target network element may be exemplarily a weight item of the target network element. In the embodiment of the application, the configuration item is not limited to the weight item, and different configuration item parameters may be modified according to actual user requirements, which is not limited herein.

[0051] The coupling and session release of the target network element are because the network elements establish a communication connection through the coupling. The connection may be temporary or persistent. The session release refers to a process of disconnecting the connection to release resources and end the communication.

[0052] The first parameter is a parameter of the configuration item of the target network element in the upgrade environment. The second parameter is a parameter of the configuration item of the target network element in the running environment.

[0053] In the embodiment of the application, the configuration item of the target network element is set as the first parameter in the upgrade environment, the coupling and the session are released, and the target network element is restarted. The target upgrade software package is deployed in the target network element in the upgrade time period. Reasonable arrangement of the upgrade time period can reduce the impact on the service and guarantee the user experience. After the upgrade, the configuration item of the target network element is restored to the second parameter in the running environment, which can also avoid the impact on the normal operation of the network due to configuration errors.

[0054] As an implementation manner of the application, in order to improve the reliability of the target network element upgrade, the network upgrade task may further include a network element backup subtask. Before the S103, the method may further include:

[0055] According to the network upgrade workflow, the network element backup subtask is scheduled. The network element backup subtask is used to instruct to copy the first configuration data of the target network element to a preset storage area.

[0056] The network element backup subtask is executed to generate a first execution result. The first execution result is used to represent whether the network element backup subtask is executed successfully or failed.

[0057] According to the network element backup subtask and the first execution result, a first task scheduling rule is generated. The first task scheduling rule includes a task name and task key information of the first target subtask.

[0058] In a case where the first execution result represents that the network element backup subtask is executed successfully, the first target subtask is determined as an upgrade implementation subtask.

[0059] The S103 may specifically include:

[0060] According to the network upgrade workflow and the task name and task key information of the first target subtask in the first task scheduling rule, the upgrade implementation subtask is scheduled.

[0061] The upgrade implementation subtask is executed.

[0062] The network element backup subtask is used to instruct copying the first configuration data of the target network element to a preset storage area, i.e., achieving data backup of the target network element.

[0063] The first execution result is used to represent success or failure of the network element backup subtask, i.e., copying the first configuration data of the target network element to the preset storage area means success of the network element backup subtask, otherwise, failure of the network element backup subtask.

[0064] The first task scheduling rule includes a task name and task key information of the first target subtask. In a case where the first execution result represents success of the network element backup subtask, the first target subtask is determined as the upgrade implementation subtask; in a case where the first execution result represents failure of the network element backup subtask, the first target subtask is determined as the abnormal management subtask.

[0065] In the embodiment, before the upgrade implementation subtask is executed, in order to avoid data loss caused by unexpected situations in the upgrade process and to recover in time, the network element backup subtask is also scheduled and executed according to the network upgrade workflow, the first execution result is generated by copying the first configuration data of the target network element to the preset storage area, the first task scheduling rule is generated according to the network element backup subtask and the first execution result, and in a case where the first execution result represents success of the network element backup subtask, the first target subtask is determined as the upgrade implementation subtask. Then, the upgrade implementation subtask is scheduled and executed according to the network upgrade workflow and the task name and task key information of the first target subtask in the first task scheduling rule, so as to improve the reliability of the target network element upgrade.

[0066] As another implementation manner of the present application, in order to ensure the smoothness of the target network element upgrade process, the network upgrade task can also include a network element inspection subtask. Before the network element backup subtask is scheduled according to the network upgrade workflow, the method can further include:

[0067] Scheduling the network element inspection subtask according to the network upgrade workflow;

[0068] Executing the network element inspection subtask, the network element inspection subtask is used to instruct the target network element to prepare and check before the upgrade and obtain an inspection report, the inspection report is used to instruct whether the target network element meets a preset upgrade rule;

[0069] Generating a second execution result according to the inspection report, the second execution result is used to represent success of the network element inspection subtask in a case where the inspection report instructs that the target network element meets the upgrade rule, or represent failure of the network element inspection subtask in a case where the inspection report instructs that the target network element does not meet the upgrade rule;

[0070] According to the network element inspection subtask and the second execution result, a second task scheduling rule is generated, and the second task scheduling rule includes task name and task key information of the second target subtask;

[0071] In a case where the second execution result indicates that the network element inspection subtask is executed successfully, the second target subtask is determined as the network element backup subtask.

[0072] According to the network upgrade workflow, the network element backup subtask can be scheduled, and the method can specifically include the following steps.

[0073] According to the network upgrade workflow and the task name and the task key information of the second target subtask in the second task scheduling rule, the network element backup subtask is scheduled.

[0074] The network element inspection subtask can instruct the target network element to perform pre-upgrade preparation and inspection and obtain an inspection report, and the inspection report can be used to indicate whether the target network element meets a preset upgrade rule. The pre-upgrade preparation and inspection can be, for example, pre-upgrade software preparation, plug-in preparation, hardware preparation, access check, pre-operation environment check, and the like. The preset upgrade rule can be, for example, that the software preparation, the plug-in preparation, and the hardware preparation are ready, the access check ensures that other devices and environments in the network are ready, and the pre-operation environment check is normal.

[0075] The second execution result can be used to indicate that the network element inspection subtask is executed successfully in a case where the inspection report indicates that the target network element meets the upgrade rule, or to indicate that the network element inspection subtask fails in a case where the inspection report indicates that the target network element does not meet the upgrade rule. In a case where the second execution result indicates that the network element inspection subtask is executed successfully, the second target subtask is determined as the network element backup subtask. In a case where the second execution result indicates that the network element inspection subtask fails, the second target subtask is determined as the exception management subtask.

[0076] In the embodiment, before the network element backup subtask is executed, the network element inspection subtask is scheduled and executed to check whether the target network element meets the preset upgrade rule. In a case where the inspection report indicates that the target network element meets the upgrade rule and the network element inspection subtask is executed successfully, the second target subtask is determined as the network element backup subtask. Then, according to the network upgrade workflow and the task name and the task key information of the second target subtask in the second task scheduling rule, the network element backup subtask is scheduled, and the reliability of the target network element upgrade is further improved.

[0077] As another implementation manner of the present application, in order to effectively evaluate the upgrade effect, the network upgrade task can further include a service stress test subtask. After the upgrade implementation subtask is executed, the method can further include the following steps.

[0078] a third execution result is generated, the third execution result being used to represent success or failure of the upgrade implementation subtask execution;

[0079] According to the upgrade implementation subtask and the third execution result, a third task scheduling rule is generated, the third task scheduling rule including a task name and task key information of the third target subtask;

[0080] In a case where the third execution result represents success of the upgrade implementation subtask execution, the third target subtask is determined to be a service dialing test subtask;

[0081] According to the network upgrade workflow and the task name and task key information of the third target subtask in the third task scheduling rule, the service dialing test subtask is scheduled;

[0082] The service dialing test subtask is executed, the service dialing test subtask being used to instruct the target network element to perform service tests of at least one scene, to obtain test data and test results of each service test, and each test result being used to indicate whether the service test of each scene is normal.

[0083] The third execution result can be used to represent success of the upgrade implementation subtask execution in a case where the target upgrade software package is deployed on the target network element in the upgrade time period, or to represent failure of the upgrade implementation subtask execution in a case where the target upgrade software package fails to be deployed on the target network element in the upgrade time period. In a case where the third execution result represents success of the upgrade implementation subtask execution, the third target subtask is determined to be the service dialing test subtask; in a case where the third execution result represents failure of the upgrade implementation subtask execution, the third target subtask is determined to be an exception management subtask.

[0084] The service dialing test subtask instructs the target network element to perform service tests of at least one scene, to obtain test data and test results of each service test, and each test result can be used to indicate whether the service test of each scene is normal. The at least one scene may, for example, be a data, voice, private network, roaming, or the like.

[0085] In the embodiment, after the upgrade implementation subtask is executed, the third execution result is generated, and in a case where the third execution result represents success of the upgrade implementation subtask execution, the third target subtask is determined to be the service dialing test subtask. Then, according to the network upgrade workflow and the task name and task key information of the third target subtask in the third task scheduling rule, the service dialing test subtask is scheduled and executed, which can effectively evaluate the upgrade effect and discover problems in time to ensure stability and reliability of network operation.

[0086] As a further implementation manner of the present application, in order to ensure that the charging of the service is consistent with the actual use of the user, the network upgrade task can further include a billing verification subtask, and after the service dialing test subtask is executed, the network upgrade task can further include:

[0087] According to the at least one service test result, a fourth execution result is generated, the fourth execution result being used to represent that the service dialing test subtask is executed successfully in a case where the at least one service test result indicates that the service test of each scenario is normal, or the service dialing test subtask is executed unsuccessfully in a case where the at least one service test result indicates that the service test of at least one scenario is abnormal;

[0088] According to the service dialing test subtask and the fourth execution result, a fourth task scheduling rule is generated, the fourth task scheduling rule including a task name and task key information of a fourth target subtask;

[0089] In a case where the fourth execution result represents that the service dialing test subtask is executed successfully, the fourth target subtask is determined to be the billing verification subtask;

[0090] According to the network upgrade workflow and the task name and task key information of the fourth target subtask in the fourth task scheduling rule, the billing verification subtask is scheduled;

[0091] The billing verification subtask is executed, the billing verification subtask being used to indicate that a bill of a target network element is verified according to test data of at least one scenario, to obtain a verification result, the verification result being used to indicate whether the bill of the target network element is accurate.

[0092] The fourth execution result can be used to represent that the service dialing test subtask is executed successfully in a case where the at least one service test result indicates that the service test of each scenario is normal, or the service dialing test subtask is executed unsuccessfully in a case where the at least one service test result indicates that the service test of at least one scenario is abnormal. In a case where the fourth execution result represents that the service dialing test subtask is executed successfully, the fourth target subtask is determined to be the billing verification subtask; in a case where the fourth execution result represents that the service dialing test subtask is executed unsuccessfully, the fourth target subtask is determined to be an exception management subtask.

[0093] The billing verification subtask is used to indicate that a bill of a target network element is verified according to test data of at least one scenario, to obtain a verification result, the verification result being used to indicate whether the bill of the target network element is accurate. The bill of the target network element can be obtained in a charging system of a telecom operator.

[0094] In the embodiment, after the service dialing test subtask is executed, a fourth execution result is generated according to at least one service test result, a fourth task scheduling rule is generated according to the service dialing test subtask and the fourth execution result, the fourth target subtask is determined as a charging verification subtask in a case where the fourth execution result indicates that the service dialing test subtask is executed successfully, and finally the charging verification subtask is scheduled and executed according to the network upgrade workflow and the task name and the task key information of the fourth target subtask in the fourth task scheduling rule, which can ensure that the charging of the service is consistent with the actual use of the user, and help to find possible problems or exceptions of the charging system.

[0095] As another implementation manner of the application, in order to ensure the normal operation of the upgraded network, the network upgrade task can further include a configuration comparison subtask, and the method can further include:

[0096] generating a fifth execution result according to the verification result, the fifth execution result being used to indicate that the charging verification subtask is executed successfully in a case where the verification result indicates that the bill of the target network element is accurate, or to indicate that the charging verification subtask is executed unsuccessfully in a case where the verification result indicates that the bill of the target network element is inaccurate;

[0097] generating a fifth task scheduling rule according to the charging verification subtask and the fifth execution result, the fifth task scheduling rule including a task name and task key information of a fifth target subtask;

[0098] determining that the fifth target subtask is the configuration comparison subtask in a case where the fifth execution result indicates that the charging verification subtask is executed successfully;

[0099] scheduling the configuration comparison subtask according to the network upgrade workflow and the task name and the task key information of the fifth target subtask in the fifth task scheduling rule;

[0100] executing the configuration comparison subtask, the configuration comparison subtask being used to indicate that the second configuration data of the target network element is acquired, and the second configuration data is compared with the first configuration data to obtain a comparison result, the comparison result being used to indicate whether the second configuration data is abnormal.

[0101] The fifth execution result can be used to indicate that the charging verification subtask is executed successfully in a case where the verification result indicates that the bill of the target network element is accurate, or to indicate that the charging verification subtask is executed unsuccessfully in a case where the verification result indicates that the bill of the target network element is inaccurate. The fifth target subtask is determined as the configuration comparison subtask in a case where the fifth execution result indicates that the charging verification subtask is executed successfully, and the fifth target subtask is determined as an abnormal management subtask in a case where the fifth execution result indicates that the charging verification subtask is executed unsuccessfully.

[0102] The configuration comparison subtask is instructed to acquire second configuration data of the target network element, and the second configuration data is compared with the first configuration data to obtain a comparison result, which can be used to indicate whether the second configuration data is abnormal.

[0103] The comparison between the second configuration data and the first configuration data can be performed by using a text comparison tool or a script to identify differences, such as missing configurations, newly added configurations, modified configurations, and the like. Differences are analyzed in detail to determine which configuration items have changed, confirm the reasons for the changes, and evaluate the possible impact of the changes on system operation.

[0104] In this embodiment, after the billing verification subtask is executed, a fifth execution result is generated according to the verification result, and a fifth task scheduling rule is generated according to the billing verification subtask and the fifth execution result. In the case where the fifth execution result represents that the billing verification subtask is successfully executed, the fifth target subtask is determined to be the configuration comparison subtask. According to the network upgrade workflow and the task name and task key information of the fifth target subtask in the fifth task scheduling rule, the configuration comparison subtask is scheduled and executed. This can effectively analyze the network element configuration, ensure the normal operation of the upgraded network, and timely discover and solve potential problems, thereby ensuring the stability and reliability of the network.

[0105] As another implementation manner of the present application, in order to monitor the performance of the target network element after the upgrade, the network upgrade task can further include an upgrade watch subtask. After the configuration comparison subtask is executed, the method can further include:

[0106] According to the comparison result, a sixth execution result is generated. The sixth execution result is used to represent that the configuration comparison subtask is successfully executed in the case where the comparison result indicates that the second configuration data is normal, or to represent that the configuration comparison subtask fails to execute in the case where the comparison result indicates that the second configuration data is abnormal.

[0107] According to the configuration comparison subtask and the sixth execution result, a sixth task scheduling rule is generated. The sixth task scheduling rule includes a task name and task key information of a sixth target subtask.

[0108] In the case where the sixth execution result represents that the configuration comparison subtask is successfully executed, the sixth target subtask is determined to be the upgrade watch subtask.

[0109] According to the network upgrade workflow and the task name and task key information of the sixth target subtask in the sixth task scheduling rule, the upgrade watch subtask is scheduled.

[0110] The upgrade watch subtask is executed. The upgrade watch subtask is used to acquire running data of at least one performance indicator of the target network element.

[0111] The seventh execution result is used to represent that the upgrade guard subtask is executed successfully when the running data of the at least one performance index meets the preset threshold of each performance index, or represent that the upgrade guard subtask is executed unsuccessfully when the running data of the at least one performance index does not meet the preset threshold of the performance index;

[0112] The seventh task scheduling rule is generated according to the upgrade guard subtask and the seventh execution result, and the seventh task scheduling rule includes the task name and the task key information of the seventh target subtask.

[0113] When the seventh execution result represents that the upgrade guard subtask is executed successfully, it is determined that the seventh target subtask indicates to end the network upgrade workflow.

[0114] The network upgrade workflow is ended according to the network upgrade workflow and the task name and the task key information of the seventh target subtask in the seventh task scheduling rule.

[0115] The sixth execution result can be used to represent that the configuration comparison subtask is executed successfully when the comparison result indicates that the second configuration data is normal, or represent that the configuration comparison subtask is executed unsuccessfully when the comparison result indicates that the second configuration data is abnormal. When the sixth execution result represents that the configuration comparison subtask is executed successfully, the sixth target subtask is determined to be an upgrade guard subtask; when the sixth execution result represents that the configuration comparison subtask is executed unsuccessfully, the sixth target subtask is determined to be an abnormal management subtask.

[0116] The upgrade guard subtask indicates to obtain the running data of at least one performance index of the target network element, and the at least one performance index may be, for example, a performance index such as data flow, bandwidth utilization, packet loss rate, delay time and throughput.

[0117] The seventh execution result can be used to represent that the upgrade guard subtask is executed successfully when the running data of the at least one performance index meets the preset threshold of each performance index, or represent that the upgrade guard subtask is executed unsuccessfully when the running data of the at least one performance index does not meet the preset threshold of the performance index. When the seventh execution result represents that the upgrade guard subtask is executed successfully, the seventh target subtask is determined to indicate to end the network upgrade workflow; when the seventh execution result represents that the upgrade guard subtask is executed unsuccessfully, the seventh target subtask is determined to be an abnormal management subtask.

[0118] In this embodiment, after the configuration comparison subtask is executed, a sixth execution result is generated according to the comparison result, and a sixth task scheduling rule is generated according to the configuration comparison subtask and the sixth execution result. In the case where the sixth execution result represents that the configuration comparison subtask is executed successfully, the sixth target subtask is determined as an upgrade guard subtask. Then, according to the network upgrade workflow and the task name and task key information of the sixth target subtask in the sixth task scheduling rule, the upgrade guard subtask is scheduled and executed. According to the running data of at least one performance indicator of the target network element, a seventh execution result is generated. According to the upgrade guard subtask and the seventh execution result, a seventh task scheduling rule is generated. In the case where the seventh execution result represents that the upgrade guard subtask is executed successfully, the seventh target subtask is determined to indicate the end of the network upgrade workflow. According to the network upgrade workflow and the task name and task key information of the seventh target subtask in the seventh task scheduling rule, the network upgrade workflow is ended. This can help monitor the performance of the target network element after the upgrade, so as to discover potential problems in time and take corresponding measures for repair.

[0119] As another implementation manner of the present application, in order to further improve the reliability of the network, the network upgrade task can further include an exception management subtask and an exception notification subtask, and the method can further include:

[0120] In the case where the first execution result represents that the network element backup subtask is executed unsuccessfully, or the second execution result represents that the network element inspection subtask is executed unsuccessfully, or the third execution result represents that the upgrade implementation subtask is executed unsuccessfully, or the fourth execution result represents that the service dialing test subtask is executed unsuccessfully, or the fifth execution result represents that the billing verification subtask is executed unsuccessfully, or the sixth execution result represents that the configuration comparison subtask is executed unsuccessfully, or the seventh execution result represents that the upgrade guard subtask is executed unsuccessfully, the first target subtask, the second target subtask, the third target subtask, the fourth target subtask, the fifth target subtask, the sixth target subtask or the seventh target subtask is determined as the exception management subtask.

[0121] According to the task name and task key information of the first target subtask, the second target subtask, the third target subtask, the fourth target subtask, the fifth target subtask, the sixth target subtask or the seventh target subtask, and the network upgrade workflow, the exception management subtask is scheduled.

[0122] The exception management subtask is executed to generate an eighth execution result. The exception management subtask is used to indicate the identification of the upgrade exception type of the target network element, and the exception handling strategy corresponding to the upgrade exception type is used for exception handling. The eighth execution result is used to represent that the exception management subtask is executed successfully or unsuccessfully.

[0123] According to the exception management subtask and the eighth execution result, an eighth task scheduling rule is generated, and the eighth task scheduling rule includes task name and task key information of the eighth target subtask;

[0124] In a case where the eighth execution result represents that the exception management subtask fails to execute, the eighth target subtask is determined to be an exception notification subtask.

[0125] According to the network upgrade workflow and the task name and the task key information of the eighth target subtask in the eighth task scheduling rule, the exception notification subtask is scheduled.

[0126] The exception notification subtask is executed, and the exception notification subtask is used to instruct to generate exception information of the target network element and send the exception information to a user, and end the network upgrade workflow.

[0127] The above exception management subtask is used to instruct to identify an upgrade exception type of the target network element, and perform exception handling according to an exception handling strategy corresponding to the upgrade exception type.

[0128] The above exception notification subtask is used to instruct to generate exception information of the target network element and send the exception information to a user.

[0129] In the embodiment, in a case where any one of the network element backup subtask, the network element inspection subtask, the upgrade implementation subtask, the service dialing test subtask, the billing verification subtask, the configuration comparison subtask, and the upgrade watch subtask fails to execute, the exception management subtask is executed to identify an upgrade exception type of the target network element, and perform exception handling according to an exception handling strategy corresponding to the upgrade exception type, thereby further improving the reliability of the network, and in a case where the upgrade exception type of the target network element is not identified, the exception notification subtask is executed to timely send exception information to a user, thereby ensuring the stability of the network.

[0130] In order to facilitate understanding of the network element upgrade method in the embodiments of the present application, the actual application process of the network element upgrade method is described as follows.

[0131] The embodiments of the present application adopt a task-based scheduling mechanism to manage and schedule multiple subtasks in the upgrade process of the core network (i.e., the above network), and realize automatic loading of a software version (i.e., the above upgrade software package). The automatic upgrade task (i.e., the above network upgrade task) refers to each independent system capability of a telecom operator, mainly including subtasks such as network element inspection, network element backup, upgrade implementation, service dialing test verification, billing verification, configuration comparison, and upgrade watch. Each subtask is independently executed and cooperates with each other to complete the entire core network automatic upgrade work under the scheduling of the automatic upgrade scheduling workflow. Table 1 shows the execution content of each subtask.

[0132] Table 1 Automatic upgrade task

[0133]

[0134] As Figure 2 The figure shows the core network automatic upgrade architecture based on task scheduling. The task scheduling module schedules each subtask according to the automatic upgrade scheduling rule through the scheduling workflow to complete the entire automatic upgrade. In the architecture, the software storage module (equivalent to the software package library mentioned above) is used as a module for storing and managing the upgrade software package, which can be implemented by using a version library or other methods. The task management module manages each task in the core network automatic upgrade process, and each task is independent of each other. The task can be added, deleted, and modified. Different tasks can be called for different network element type upgrade processes, and can be flexibly called and managed.

[0135] The task scheduling module includes:

[0136] Scheduling start: The scheduling start completes the automatic upgrade scheduling workflow (i.e. the network upgrade workflow mentioned above) trigger, which can be implemented in multiple ways (such as upgrade work order trigger). The scheduling start needs to include the key fields required by the automatic upgrade scheduling workflow, such as the upgrade network element type, the upgrade network element name, the upgrade software version number, the upgrade start / end time, etc.

[0137] Scheduling rule: The scheduling rule is the key to the execution of the task scheduling workflow. The workflow decides the next task to be executed under each subtask node through the scheduling rule. Table 2 shows the task scheduling rule. The workflow maintains the task scheduling rule table at each subtask node, and executes the task scheduling according to the rule table. The subtask state can be success, failure, or empty.

[0138] Table 2 Task scheduling rule

[0139] Current subtask Name of the subtask currently being executed Subtask status Result status of the current subtask execution Next subtask Name of the subtask to be executed next Task keyword Key information required for the next subtask execution

[0140] Scheduling workflow: The workflow completes the scheduling of each subtask of the automatic upgrade, and executes the next subtask scheduling of each subtask node according to the scheduling rule.

[0141] The automatic upgrade workflow schedules each subtask to complete the automatic upgrade process. As Figure 3 The figure shows the automatic upgrade workflow. In each subtask node, the workflow generates a task scheduling rule, Figure 3 The scheduling rule 1 and rule 2 on each subtask node respectively indicate the next subtask and the key required for the next subtask execution scheduled by the workflow when the current subtask execution state is success and failure. There is only one workflow scheduling rule for a subtask node at a time.

[0142] From the dispatch start carrying the upgrade key information trigger workflow, the key information is used as the key of the subsequent subtask execution, including the network element type, network element name, version number, and upgrade time. After the dispatch is started, the workflow calls the network element inspection subtask to perform the pre-upgrade preparation and inspection, and after the execution is completed, the workflow generates the dispatch rule (equivalent to the second task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the next subtask network element backup is executed according to rule 1. The network element backup subtask completes the data backup of the upgraded network element (i.e., the target network element described above), and after the execution is completed, the workflow generates the dispatch rule (equivalent to the first task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the next subtask upgrade implementation is executed according to rule 1. The upgrade implementation subtask downloads the software package (i.e., the target upgrade software package described above) according to the key version number in the version storage module, and performs the deployment operation of the specific software package according to the implementation start time. After the execution is completed, the workflow generates the dispatch rule (equivalent to the third task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the next subtask business dialing test is executed according to rule 1. The business dialing test subtask completes the business test of the upgraded network element, and after the execution is completed, the workflow generates the dispatch rule (equivalent to the fourth task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the next subtask billing verification is executed according to rule 1. The billing verification subtask completes the business test call verification of the billing network element according to the key dialing number and dialing time, and after the execution is completed, the workflow generates the dispatch rule (equivalent to the fifth task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the next subtask configuration comparison is executed according to rule 1. The configuration comparison subtask completes the comparison between the network element configuration after the upgrade implementation and the backup configuration according to the network element name, and after the execution is completed, the workflow generates the dispatch rule (equivalent to the sixth task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the next subtask upgrade watch is executed according to rule 1. The upgrade watch subtask completes the index monitoring, business monitoring, and network element alarm, and after the execution is completed, the workflow generates the dispatch rule (equivalent to the seventh task dispatch rule described above). If the subtask execution fails, the next subtask exception management is executed according to rule 2, and if the execution is successful, the workflow is ended according to rule 1.

[0143] The exception management subtask in the workflow completes the exception identification and processing of the execution failure of each subtask. After the execution of the exception management subtask is completed, the workflow generates the dispatch rule (equivalent to the eighth task dispatch rule described above). If the subtask execution is successful, the workflow is ended according to rule 1, and if the execution fails, the next subtask exception notification is executed according to rule 2. The exception notification subtask calls the end of the workflow.

[0144] Compared with the software version management and deployment mode completed by artificial, the automatic upgrade of the operator core network software based on task scheduling in the embodiments of the present application greatly improves the agility of software version deployment, provides the capability of fast deployment for the software version update iteration of the telecommunication core network, and greatly improves the pace of fast application of new functions and new technologies of the current core network. On the other hand, the standardization of task management and the systematization of workflow scheduling in the automatic upgrade process reduce the human error and further improve the reliability of software version deployment. Compared with the development and operations (DevOps) mode, the embodiments of the present application propose a more rigorous deployment process while constructing the automatic upgrade workflow of the telecommunication core network. First, the task-based workflow is more standardized and systematic, and the tasks executed are more comprehensive, not only completing the software deployment, but also completing rigorous business test verification. Second, the abnormality management is introduced to judge and handle the abnormality in the workflow, so as to ensure the controllability of the process.

[0145] Based on the network element upgrade method provided in the above embodiments, the present application also provides a specific implementation mode of a network element upgrade device. It can be understood that the related description in each of the following device embodiments can refer to the foregoing method embodiments, and for the sake of brevity, will not be described again. Please refer to the following embodiments.

[0146] Please refer to Figure 4 is a structural schematic diagram of a network element upgrade device 400 provided by the embodiments of the present application, which can include a receiving module 401, a starting module 402 and a first execution module 403.

[0147] The receiving module 401 is configured to receive an upgrade request sent by a user, the upgrade request including a target network element type, a target network element name, a target upgrade software version number and an upgrade time period.

[0148] The starting module 402 is configured to start a preset network upgrade workflow of a target network element in response to the upgrade request, the network upgrade workflow being configured to schedule a network upgrade task, the network upgrade task including an upgrade implementation subtask, the target network element being at least one network element in a network corresponding to the target network element type and the target network element name, different network elements corresponding to different network element types and different network element names.

[0149] The first execution module 403 is configured to schedule and execute the upgrade implementation subtask according to the network upgrade workflow, the upgrade implementation subtask being configured to instruct a target upgrade software package to be deployed on the target network element in the upgrade time period, the target upgrade software package being an upgrade software package corresponding to the target upgrade software version number in a preset software package library, the software package library including at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, different upgrade software packages corresponding to different upgrade software version numbers.

[0150] The network element upgrading apparatus of the embodiment of the application can receive an upgrading request sent by a user, the upgrading request comprising a target network element type, a target network element name, a target upgrading software version number and an upgrading time period; in response to the upgrading request, a preset network upgrading workflow of a target network element is started, the network upgrading workflow being used to schedule a network upgrading task, the network upgrading task comprising an upgrading implementation subtask, the target network element being a network element corresponding to the target network element type and the target network element name among at least one network element of a network, different network elements corresponding to different network element types and different network element names; according to the network upgrading workflow, the upgrading implementation subtask is scheduled and executed, the upgrading implementation subtask being used to instruct a target upgrading software package to be deployed on the target network element in the upgrading time period, the target upgrading software package being an upgrading software package corresponding to the target upgrading software version number in a preset software package library, the software package library comprising at least one upgrading software package and an upgrading software version number corresponding to each software upgrading package, different upgrading software packages corresponding to different upgrading software version numbers. In this way, the embodiment of the application can start the preset network upgrading workflow of the target network element in response to the upgrading request, schedule and execute the upgrading implementation subtask according to the network upgrading workflow, and automatically deploy the target upgrading software package corresponding to the target upgrading software version number into the target network element corresponding to the target network element type and the target network element name, so as to reduce the risk of misoperation of manual deployment and improve the reliability of network element upgrading package deployment.

[0151] As an implementation manner of the application, in order to improve the reliability of target network element upgrading, the above network upgrading task can further comprise a network element backup subtask, and the apparatus 400 can further comprise:

[0152] a first scheduling module, configured to schedule the network element backup subtask according to the network upgrading workflow, the network element backup subtask being used to instruct first configuration data of the target network element to be copied to a preset storage area;

[0153] a second execution module, configured to execute the network element backup subtask to generate a first execution result, the first execution result being used to represent whether the network element backup subtask is executed successfully or fails;

[0154] a first generation module, configured to generate a first task scheduling rule according to the network element backup subtask and the first execution result, the first task scheduling rule comprising a task name and task key information of the first target subtask;

[0155] a first determination module, configured to determine that the first target subtask is the upgrading implementation subtask in a case where the first execution result represents that the network element backup subtask is executed successfully;

[0156] The first execution module 403 can comprise:

[0157] The scheduling unit is configured to schedule the upgrade implementation subtask according to the network upgrade workflow and the task name and the task key information of the first target subtask in the first task scheduling rule.

[0158] The execution unit is configured to execute the upgrade implementation subtask.

[0159] As another implementation form of the present application, in order to ensure the smoothness of the target network element upgrade process, the network upgrade task can further include a network element inspection subtask, and the device 400 can further include:

[0160] The second scheduling module is configured to schedule the network element inspection subtask according to the network upgrade workflow.

[0161] The third execution module is configured to execute the network element inspection subtask, and the network element inspection subtask is configured to instruct the target network element to make preparations and checks before the upgrade and obtain an inspection report, and the inspection report is configured to indicate whether the target network element meets the preset upgrade rule.

[0162] The second generation module is configured to generate a second execution result according to the inspection report, and the second execution result is configured to represent that the network element inspection subtask is executed successfully in a case where the inspection report indicates that the target network element meets the upgrade rule, or represent that the network element inspection subtask is executed unsuccessfully in a case where the inspection report indicates that the target network element does not meet the upgrade rule.

[0163] The third generation module is configured to generate a second task scheduling rule according to the network element inspection subtask and the second execution result, and the second task scheduling rule includes the task name and the task key information of the second target subtask.

[0164] The second determination module is configured to determine that the second target subtask is a network element backup subtask in a case where the second execution result represents that the network element inspection subtask is executed successfully.

[0165] The first scheduling module is specifically configured to schedule the network element backup subtask according to the network upgrade workflow and the task name and the task key information of the second target subtask in the second task scheduling rule.

[0166] As another implementation form of the present application, in order to effectively evaluate the upgrade effect, the network upgrade task can further include a service stress test subtask, and the device 400 can further include:

[0167] The fourth generation module is configured to generate a third execution result, and the third execution result is configured to represent that the upgrade implementation subtask is executed successfully or unsuccessfully.

[0168] The fifth generation module is configured to generate a third task scheduling rule according to the upgrade implementation subtask and the third execution result, and the third task scheduling rule includes the task name and the task key information of the third target subtask.

[0169] The third determining module is configured to determine that the third target subtask is a service dialing subtask in a case where the third execution result represents that the execution of the upgrade implementation subtask is successful.

[0170] The third scheduling module is configured to schedule the service dialing subtask according to the network upgrade workflow and the task name and the task key information of the third target subtask in the third task scheduling rule.

[0171] The fourth execution module is configured to execute the service dialing subtask, and the service dialing subtask is configured to instruct the target network element to perform service testing of at least one scene, to obtain testing data and testing results of each service testing, and each testing result is configured to indicate whether the service testing of each scene is normal.

[0172] As another implementation manner of the present application, in order to ensure that the charging of the service is consistent with the actual use of the user, the network upgrade task described above can further include a charging verification subtask, and the apparatus 400 described above can further include:

[0173] The sixth generating module is configured to generate a fourth execution result according to the at least one service testing result, and the fourth execution result is configured to represent that the execution of the service dialing subtask is successful in a case where the at least one service testing result indicates that the service testing of each scene is normal, or represent that the execution of the service dialing subtask fails in a case where the at least one service testing result indicates that the service testing of at least one scene is not normal.

[0174] The seventh generating module is configured to generate a fourth task scheduling rule according to the service dialing subtask and the fourth execution result, and the fourth task scheduling rule includes a task name and task key information of a fourth target subtask.

[0175] The fourth determining module is configured to determine that the fourth target subtask is the charging verification subtask in a case where the fourth execution result represents that the execution of the service dialing subtask is successful.

[0176] The fourth scheduling module is configured to schedule the charging verification subtask according to the network upgrade workflow and the task name and the task key information of the fourth target subtask in the fourth task scheduling rule.

[0177] The fifth execution module is configured to execute the charging verification subtask, and the charging verification subtask is configured to instruct to verify a bill of the target network element according to the testing data of at least one scene to obtain a verification result, and the verification result is configured to indicate whether the bill of the target network element is accurate.

[0178] As still another implementation manner of the present application, in order to ensure the normal operation of the network after the upgrade, the network upgrade task described above can further include a configuration comparison subtask, and the apparatus 400 described above can further include:

[0179] The eighth generating module is configured to generate a fifth execution result according to the verification result, the fifth execution result being used to represent that the charging verification subtask is executed successfully when the verification result indicates that the bill of the target network element is accurate, or the charging verification subtask is executed unsuccessfully when the verification result indicates that the bill of the target network element is inaccurate;

[0180] The ninth generating module is configured to generate a fifth task scheduling rule according to the charging verification subtask and the fifth execution result, the fifth task scheduling rule including a task name and task key information of the fifth target subtask;

[0181] The fifth determining module is configured to determine that the fifth target subtask is the configuration comparison subtask when the fifth execution result represents that the charging verification subtask is executed successfully.

[0182] The fifth scheduling module is configured to schedule the configuration comparison subtask according to the network upgrade workflow and the task name and task key information of the fifth target subtask in the fifth task scheduling rule.

[0183] The sixth execution module is configured to execute the configuration comparison subtask, the configuration comparison subtask being used to instruct to acquire second configuration data of the target network element, and compare the second configuration data with the first configuration data to obtain a comparison result, the comparison result being used to indicate whether the second configuration data is abnormal.

[0184] As another implementation manner of the present application, in order to monitor the performance of the target network element after the upgrade, the network upgrade task further includes an upgrade watch subtask, and the apparatus 400 further includes:

[0185] The tenth generating module is configured to generate a sixth execution result according to the comparison result, the sixth execution result being used to represent that the configuration comparison subtask is executed successfully when the comparison result indicates that the second configuration data is normal, or the configuration comparison subtask is executed unsuccessfully when the comparison result indicates that the second configuration data is abnormal.

[0186] The eleventh generating module is configured to generate a sixth task scheduling rule according to the configuration comparison subtask and the sixth execution result, the sixth task scheduling rule including a task name and task key information of a sixth target subtask.

[0187] The sixth determining module is configured to determine that the sixth target subtask is the upgrade watch subtask when the sixth execution result represents that the configuration comparison subtask is executed successfully.

[0188] The sixth scheduling module is configured to schedule the upgrade watch subtask according to the network upgrade workflow and the task name and task key information of the sixth target subtask in the sixth task scheduling rule.

[0189] The seventh execution module is configured to execute an upgrade guarding subtask, and the upgrade guarding subtask is configured to instruct to acquire running data of at least one performance index of the target network element;

[0190] The twelfth generation module is configured to generate a seventh execution result according to the running data of the at least one performance index of the target network element, and the seventh execution result is configured to represent that the upgrade guarding subtask is executed successfully in a case where the running data of the at least one performance index meets preset threshold values of the performance indexes, or represent that the upgrade guarding subtask is executed unsuccessfully in a case where the running data of the at least one performance index does not meet the preset threshold values of the performance indexes;

[0191] The thirteenth generation module is configured to generate a seventh task scheduling rule according to the upgrade guarding subtask and the seventh execution result, and the seventh task scheduling rule includes a task name and task key information of the seventh target subtask.

[0192] The seventh determination module is configured to determine that the seventh target subtask instructs to end the network upgrade workflow in a case where the seventh execution result represents that the upgrade guarding subtask is executed successfully.

[0193] The ending module is configured to end the network upgrade workflow according to the network upgrade workflow and the task name and the task key information of the seventh target subtask in the seventh task scheduling rule.

[0194] As another implementation manner of the present application, in order to further improve the reliability of the network, the network upgrade task can further include an exception management subtask and an exception notification subtask, the network upgrade task further includes the exception management subtask and the exception notification subtask, and the apparatus 400 further includes:

[0195] The eighth determination module is configured to determine that the first target subtask, the second target subtask, the third target subtask, the fourth target subtask, the fifth target subtask, the sixth target subtask or the seventh target subtask is the exception management subtask in a case where the first execution result represents that the network element backup subtask is executed unsuccessfully, or the second execution result represents that the network element inspection subtask is executed unsuccessfully, or the third execution result represents that the upgrade implementation subtask is executed unsuccessfully, or the fourth execution result represents that the service probing subtask is executed unsuccessfully, or the fifth execution result represents that the charging verification subtask is executed unsuccessfully, or the sixth execution result represents that the configuration comparison subtask is executed unsuccessfully, or the seventh execution result represents that the upgrade guarding subtask is executed unsuccessfully.

[0196] The seventh scheduling module is configured to schedule the exception management subtask according to the task name and the task key information of the first target subtask, the second target subtask, the third target subtask, the fourth target subtask, the fifth target subtask, the sixth target subtask or the seventh target subtask, and the network upgrade workflow.

[0197] The eighth execution module is configured to execute an exception management subtask, and generate an eighth execution result. The exception management subtask is configured to indicate identification of an upgrade exception type of the target network element, and perform exception handling according to an exception handling strategy corresponding to the upgrade exception type. The eighth execution result is configured to represent success or failure of execution of the exception management subtask.

[0198] The generation module is configured to generate an eighth task scheduling rule according to the exception management subtask and the eighth execution result. The eighth task scheduling rule includes a task name and task key information of the eighth target subtask.

[0199] The ninth determination module is configured to determine, in a case where the eighth execution result represents failure of execution of the exception management subtask, that the eighth target subtask is an exception notification subtask.

[0200] The eighth scheduling module is configured to schedule the exception notification subtask according to the network upgrade workflow and the task name and task key information of the eighth target subtask in the eighth task scheduling rule.

[0201] The ninth execution module is configured to execute the exception notification subtask. The exception notification subtask is configured to generate exception information of the target network element, and send the exception information to a user, and end the network upgrade workflow.

[0202] In some embodiments, the first execution module 403 can specifically include:

[0203] The first setting unit is configured to set a configuration item of the target network element to a preset first parameter.

[0204] The release unit is configured to release coupling and session of the target network element.

[0205] The acquisition unit is configured to acquire, according to the target upgrade software version number, a target upgrade software package from a software package library.

[0206] The deployment unit is configured to deploy the target upgrade software package to the target network element in an upgrade time period.

[0207] The restart unit is configured to restart the target network element.

[0208] The second setting unit is configured to set the configuration item of the target network element to a preset second parameter.

[0209] Figure 5 A hardware structure schematic diagram of an electronic device provided by an embodiment of the present application is shown.

[0210] The electronic device can include a processor 501 and a memory 502 having stored computer program instructions.

[0211] In particular, the processor 501 can include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to perform the operations of one or more embodiments of the application.

[0212] The memory 502 can include mass storage for data or instructions. As an example and not by way of limitation, the memory 502 can include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a solid-state drive (SSD), a USB drive, or a combination of two or more of these. Where appropriate, the memory 502 can include removable or non-removable (or fixed) media, where appropriate. The memory 502 can be internal or external to the integrated gateway disaster recovery device. In particular embodiments, the memory 502 is non-volatile, solid-state memory.

[0213] In particular embodiments, the memory 502 can include read-only memory (ROM), random access memory (RAM), a magnetic disk storage medium, an optical storage medium, a flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software that, when executed (by one or more processors), is operable to perform operations described with reference to the methods according to an aspect of the present disclosure.

[0214] The processor 501 implements any of the network element upgrade methods in the above embodiments by reading and executing computer program instructions stored in the memory 502.

[0215] In one example, the electronic device can further include a communication interface 503 and a bus 510. As shown, the processor 501, the memory 502, and the communication interface 503 are connected through the bus 510 and complete communication among each other. Figure 5

[0216] The communication interface 503 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiments of the application.

[0217] ​Bus 510 includes hardware, software, or both, to couple electronic devices to each other in a network. While Figure 5 illustrates a bus coupling only three devices, it is understood that the network of Figure 5 can include many more devices. Bus 510 can be any of several types of bus structures including an accelerated graphics port (AGP) or other graphics bus, an enhanced industry standard architecture (EISA) bus, a front-side bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (ISA) bus, an infiniband (IB) interconnect, a low pin count (LPC) bus, a memory bus, a microchannel architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a video electronics standards association local (VLB) bus, or another suitable bus or interconnect, or a combination of two or more of these. Where appropriate, bus 510 can include one or more buses. Although this application describes and illustrates a particular bus, this application contemplates any suitable bus or interconnect.

[0218] The electronic device can perform the network element upgrading method in the embodiments of the application, thereby realizing the network element upgrading method and device described in combination with Figure 1 and Figure 4 the above embodiments.

[0219] In addition, in combination with the network element upgrading method in the above embodiments, the embodiments of the application can provide a computer readable storage medium to realize. The computer readable storage medium has computer program instructions stored thereon; the computer program instructions are executed by a processor to realize any one of the network element upgrading methods in the above embodiments.

[0220] In combination with the network element upgrading method in the above embodiments, the embodiments of the application can provide a computer program product, instructions in the computer program product are executed by a processor of an electronic device, so that the electronic device executes the network element upgrading method of any one of the above.

[0221] It needs to be clear that the application is not limited to the specific configurations and processes described above and shown in the drawings. For the sake of brevity, detailed descriptions of well-known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between steps, after understanding the spirit of the application.

[0222] The functions noted in the description of the structural block diagrams above can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, and the like. When implemented in software, the elements of the present application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine-readable medium, or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. A "machine-readable medium" includes any medium that can store or transport information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like. The code segments can be downloaded via computer networks such as the Internet, intranets, and the like.

[0223] It is also important to note that the examples mentioned in the present application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the steps mentioned above, that is, the steps can be performed in the order mentioned in the examples, or in an order different from the examples, or several steps can be performed simultaneously.

[0224] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer program instructions can also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other processing device to operate in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks. The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer program instructions can also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other processing device to operate in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0225] The above merely describes a specific implementation of the present application. Those skilled in the art can clearly understand the specific working processes of the system, modules and units described above for the convenience and brevity of description, and can refer to the corresponding processes in the foregoing method embodiments, which will not be described herein again. It should be understood that the protection scope of the present application is not limited to this, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed by the present application, and these modifications or replacements should be covered within the protection scope of the present application.

Claims

1. A method for upgrading network elements, characterized in that, include: Receive upgrade requests sent by users, the upgrade requests including target network element type, target network element name, target upgrade software version number and upgrade time period; In response to the upgrade request, a preset network upgrade workflow for the target network element is initiated. The network upgrade workflow is used to schedule network upgrade tasks. The network upgrade tasks include upgrade implementation sub-tasks. The target network element is at least one network element in the network that corresponds to the target network element type and the target network element name. Different network elements correspond to different network element types and different network element names. According to the network upgrade workflow, the upgrade implementation subtask is scheduled and executed. The upgrade implementation subtask is used to instruct the target upgrade package to be deployed on the target network element during the upgrade time period. The target upgrade package is an upgrade package in a preset package library that corresponds to the target upgrade software version number. The package library includes at least one upgrade package and the upgrade software version number corresponding to each upgrade package. Different upgrade packages correspond to different upgrade software version numbers.

2. The method according to claim 1, characterized in that, The network upgrade task also includes a network element backup subtask, and before scheduling and executing the upgrade implementation subtask according to the network upgrade workflow, it further includes: According to the network upgrade workflow, the network element backup subtask is scheduled, and the network element backup subtask is used to instruct the first configuration data of the target network element to be copied to a preset storage area. The network element backup subtask is executed, and a first execution result is generated. The first execution result is used to indicate whether the network element backup subtask was executed successfully or failed. Based on the network element backup subtask and the first execution result, a first task scheduling rule is generated. The first task scheduling rule includes the task name and key task information of the first target subtask. If the first execution result indicates that the network element backup subtask was successfully executed, the first target subtask is determined to be the upgrade implementation subtask; The step of scheduling and executing the upgrade implementation sub-tasks according to the network upgrade workflow includes: Based on the network upgrade workflow and the task name and key information of the first target sub-task in the first task scheduling rule, schedule the upgrade implementation sub-task; Execute the aforementioned upgrade implementation subtask.

3. The method according to claim 2, characterized in that, The network upgrade task also includes a network element inspection subtask, and before scheduling the network element backup subtask according to the network upgrade workflow, it further includes: According to the network upgrade workflow, schedule the network element inspection sub-tasks; The network element inspection subtask is executed. The network element inspection subtask is used to instruct the target network element to perform pre-upgrade preparation and inspection and obtain an inspection report. The inspection report is used to indicate whether the target network element meets the preset upgrade rules. Based on the inspection report, a second execution result is generated. The second execution result is used to indicate that the network element inspection sub-task was successfully executed when the inspection report indicates that the target network element meets the upgrade rules, or to indicate that the network element inspection sub-task failed when the inspection report indicates that the target network element does not meet the upgrade rules. Based on the network element inspection subtask and the second execution result, a second task scheduling rule is generated. The second task scheduling rule includes the task name and key task information of the second target subtask. If the second execution result indicates that the network element inspection subtask was successfully executed, the second target subtask is determined to be the network element backup subtask; The step of scheduling the network element backup subtask according to the network upgrade workflow includes: Based on the network upgrade workflow and the task name and key information of the second target subtask in the second task scheduling rule, the network element backup subtask is scheduled.

4. The method according to claim 3, characterized in that, The network upgrade task also includes a service testing subtask, and after executing the upgrade implementation subtask, it further includes: A third execution result is generated, which is used to characterize whether the upgrade implementation subtask was executed successfully or failed. Based on the upgrade implementation sub-task and the third execution result, a third task scheduling rule is generated, which includes the task name and key task information of the third target sub-task. If the third execution result indicates that the upgrade implementation subtask was successfully executed, the third target subtask is determined to be the service testing subtask; Based on the network upgrade workflow and the task name and key information of the third target sub-task in the third task scheduling rule, schedule the service testing sub-task. The service testing subtask is executed to instruct the target network element to perform service testing in at least one scenario, and to obtain test data and test results for each service test. The test results are used to indicate whether the service test for each scenario is normal.

5. The method according to claim 4, characterized in that, The network upgrade task also includes a billing verification subtask, and after executing the service testing subtask, it further includes: Based on the at least one business test result, a fourth execution result is generated. The fourth execution result is used to characterize the successful execution of the business testing subtask when the at least one business test result indicates that the business test of each scenario is normal, or to characterize the failure of the business testing subtask when the at least one business test result indicates that the business test of at least one scenario is abnormal. Based on the business testing subtask and the fourth execution result, a fourth task scheduling rule is generated, which includes the task name and key task information of the fourth target subtask. If the fourth execution result indicates that the service testing subtask was successfully executed, the fourth target subtask is determined to be the billing verification subtask; Based on the network upgrade workflow and the task name and key information of the fourth target subtask in the fourth task scheduling rule, schedule the billing verification subtask; The billing verification subtask is executed, which is used to instruct the call detail records (CDRs) of the target network element to be verified based on the test data of the at least one scenario, and to obtain a verification result. The verification result is used to indicate whether the CDRs of the target network element are accurate.

6. The method according to claim 5, characterized in that, The network upgrade task also includes a configuration comparison subtask, and after executing the billing verification subtask, it further includes: Based on the verification result, a fifth execution result is generated. The fifth execution result is used to characterize the successful execution of the billing verification subtask when the verification result indicates that the call detail records of the target network element are accurate, or to characterize the failure of the billing verification subtask when the verification result indicates that the call detail records of the target network element are inaccurate. Based on the billing verification subtask and the fifth execution result, a fifth task scheduling rule is generated, which includes the task name and key task information of the fifth target subtask. If the fifth execution result indicates that the billing verification subtask was executed successfully, the fifth target subtask is determined to be the configuration comparison subtask; Based on the network upgrade workflow and the task name and key information of the fifth target subtask in the fifth task scheduling rule, schedule the configuration comparison subtask; The configuration comparison subtask is executed, which is used to instruct the acquisition of the second configuration data of the target network element, and to compare the second configuration data with the first configuration data to obtain a comparison result. The comparison result is used to indicate whether the second configuration data is abnormal.

7. The method according to claim 6, characterized in that, The network upgrade task also includes an upgrade monitoring subtask, and after executing the configuration comparison subtask, it further includes: Based on the comparison results, a sixth execution result is generated. The sixth execution result is used to characterize the successful execution of the configuration comparison subtask when the comparison results indicate that the second configuration data is normal, or to characterize the failure of the configuration comparison subtask when the comparison results indicate that the second configuration data is abnormal. Based on the configuration comparison of the sub-tasks and the sixth execution result, a sixth task scheduling rule is generated. The sixth task scheduling rule includes the task name and key task information of the sixth target sub-task. If the sixth execution result indicates that the configuration comparison subtask was executed successfully, the sixth target subtask is determined to be the upgrade guard subtask; Based on the network upgrade workflow and the task name and key information of the sixth target subtask in the sixth task scheduling rule, schedule the upgrade duty subtask; The upgrade monitoring subtask is executed, which is used to instruct the acquisition of operational data of at least one performance indicator of the target network element; Based on the operating data of at least one performance indicator of the target network element, a seventh execution result is generated. The seventh execution result is used to indicate that the upgrade guarding subtask was successfully executed when the operating data of at least one performance indicator meets the preset threshold of each performance indicator, or to indicate that the upgrade guarding subtask was unsuccessful when the operating data of at least one performance indicator does not meet the preset threshold of the performance indicator. Based on the upgraded duty subtask and the seventh execution result, a seventh task scheduling rule is generated, which includes the task name and key task information of the seventh target subtask. If the seventh execution result indicates that the upgrade monitoring subtask was successfully executed, then the seventh target subtask indicates the end of the network upgrade workflow; The network upgrade workflow is terminated based on the task name and key information of the seventh target subtask in the network upgrade workflow and the seventh task scheduling rule.

8. The method according to claim 7, characterized in that, The network upgrade task further includes an anomaly management subtask and an anomaly notification subtask, and the method further includes: If the first execution result indicates that the network element backup subtask failed, or the second execution result indicates that the network element inspection subtask failed, or the third execution result indicates that the upgrade implementation subtask failed, or the fourth execution result indicates that the service dialing test subtask failed, or the fifth execution result indicates that the billing verification subtask failed, or the sixth execution result indicates that the configuration comparison subtask failed, or the seventh execution result indicates that the upgrade monitoring subtask failed, then the first target subtask, the second target subtask, the third target subtask, the fourth target subtask, the fifth target subtask, the sixth target subtask, or the seventh target subtask is determined to be the anomaly management subtask. Based on the task names and key information of the first target sub-task, the second target sub-task, the third target sub-task, the fourth target sub-task, the fifth target sub-task, the sixth target sub-task, or the seventh target sub-task, and the network upgrade workflow, schedule the anomaly management sub-task; The anomaly management subtask is executed to generate an eighth execution result. The anomaly management subtask is used to identify the upgrade anomaly type of the target network element and to perform anomaly handling according to the anomaly handling strategy corresponding to the upgrade anomaly type. The eighth execution result is used to characterize whether the anomaly management subtask was executed successfully or failed. Based on the exception management subtask and the eighth execution result, an eighth task scheduling rule is generated, which includes the task name and key task information of the eighth target subtask. If the eighth execution result indicates that the exception management subtask has failed, the eighth target subtask is determined to be the exception notification subtask. Based on the network upgrade workflow and the task name and key information of the eighth target subtask in the eighth task scheduling rule, schedule the exception notification subtask; The exception notification subtask is executed, which is used to instruct the generation of exception information for the target network element and send the exception information to the user, thereby ending the network upgrade workflow.

9. The method according to claim 1, characterized in that, The execution of the upgrade implementation subtask includes: Set the configuration item of the target network element to the preset first parameter; Release the coupling and session of the target network element; Based on the target upgrade software version number, obtain the target upgrade package from the package library; Deploy the target upgrade package on the target network element during the upgrade period; Restart the target network element; Set the configuration item of the target network element to the preset second parameter.

10. A network element upgrade device, characterized in that, The device includes: The receiving module is used to receive upgrade requests sent by users. The upgrade request includes the target network element type, target network element name, target upgrade software version number, and upgrade time period. The startup module is used to respond to the upgrade request and start a preset network upgrade workflow for the target network element. The network upgrade workflow is used to schedule network upgrade tasks. The network upgrade tasks include upgrade implementation sub-tasks. The target network element is at least one network element in the network that corresponds to the target network element type and the target network element name. Different network elements correspond to different network element types and different network element names. The first execution module is used to schedule and execute the upgrade implementation subtask according to the network upgrade workflow. The upgrade implementation subtask is used to instruct the target upgrade package to be deployed on the target network element during the upgrade time period. The target upgrade package is an upgrade package in a preset package library that corresponds to the target upgrade software version number. The package library includes at least one upgrade package and the upgrade software version number corresponding to each upgrade package. Different upgrade packages correspond to different upgrade software version numbers.

11. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, it implements the network element upgrade method as described in any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the network element upgrade method as described in any one of claims 1-9.

13. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the network element upgrade method as described in any one of claims 1-9.

Images