Network element upgrading method and device, equipment, storage medium and program product
Through automated network upgrade workflows, scheduling and executing upgrade tasks, the risk of misoperation caused by manual operations is solved, and the reliability and stability of network element upgrades are improved.
Patent Information
- Application Number
- CN202410924384.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-09
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2044-07-09
AI Technical Summary
The deployment process of existing network element software versions mainly relies on manual operations, resulting in high risk of misoperation and reducing the reliability of deployment.
Provide a network element upgrade method and device, by receiving user upgrade requests, starting a preset network upgrade workflow, scheduling and executing upgrade implementation subtasks, automatically deploying target upgrade software packages to target network elements, reducing the risk of manual error operation .
It improves the reliability of network element upgrade package deployment, reduces manual errors, and improves the automation and stability of network upgrades.
Smart Images

Figure CN119011397A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and in particular, relates to a network element upgrading method, device, equipment, storage medium and program product. Background Art
[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 network stability and reliability. Through network upgrades, communication networks can better meet users' communication needs and provide higher quality services. There are many network elements involved in the network upgrade. The software version of the network element upgrade is developed by equipment vendors according to the 3rd Generation Partnership Project (3GPP) and operator routing organization principles, and deployed to the corresponding network elements to achieve network upgrades. However, the deployment process of existing network element software versions is mainly completed manually, and the risk of manual misoperation is high, resulting in low reliability of software version deployment. Summary of the invention
[0003] The embodiments of the present application provide a network element upgrade method, apparatus, device, storage medium and program product, which can reduce the risk of misoperation in manual deployment, thereby improving the reliability of network element upgrade package deployment.
[0004] In a first aspect, an embodiment of the present application provides a network element upgrade method, the method comprising:
[0005] 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;
[0006] In response to the upgrade request, start a preset network upgrade workflow of the target network element, the network upgrade workflow is used to schedule a network upgrade task, the network upgrade task includes an upgrade implementation subtask, 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, and different network elements correspond to different network element types and different network element names;
[0007] According to the network upgrade workflow, the upgrade implementation subtask is scheduled and executed, the upgrade implementation subtask is used to indicate that a target upgrade software package is deployed on the target network element in the upgrade time period, 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 includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers.
[0008] In a second aspect, an embodiment of the present application provides a network element upgrading device, the device comprising:
[0009] A receiving module, configured to receive an upgrade request sent by a user, wherein the upgrade request includes a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period;
[0010] A starting module, configured to start a preset network upgrade workflow of a target network element in response to the upgrade request, wherein the network upgrade workflow is used to schedule a network upgrade task, wherein the network upgrade task includes an upgrade implementation subtask, and 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, and different network elements correspond to different network element types and different network element names;
[0011] The first execution module is used to schedule and execute the upgrade implementation subtask according to the network upgrade workflow, wherein the upgrade implementation subtask is used to indicate that a target upgrade software package is deployed on the target network element during the upgrade time period, and the target upgrade software package is an upgrade software package corresponding to the target upgrade software version number in a preset software package library, wherein the software package library includes at least one upgrade software package and an upgrade software version number corresponding to each of the software upgrade packages, and different upgrade software packages correspond to different upgrade software version numbers.
[0012] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the network element upgrade method as described in any one of the above items is implemented.
[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the network element upgrade method as described in any one of the above items is implemented.
[0014] In a fifth aspect, an embodiment of the present application provides a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the network element upgrade method as described in any one of the above.
[0015] The network element upgrade method, apparatus, device, storage medium and program product of the embodiment of the present application can receive an upgrade request sent by a user, the upgrade request includes 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 is used to schedule network upgrade tasks, the network upgrade tasks include upgrade implementation subtasks, 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, and different network elements correspond to different network element types and different network element names; according to the network upgrade workflow, schedule and execute the upgrade implementation subtask, the upgrade implementation subtask is used to indicate that a target upgrade software package is deployed on the target network element during the upgrade time period, 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 includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers. In this way, the embodiment of the present application can respond to an upgrade request, start the preset network upgrade workflow of the target network element, schedule and execute the upgrade implementation subtasks according to the network upgrade workflow, and automatically deploy the target upgrade software package corresponding to the target upgrade software version number to the target network element corresponding to the target network element type and target network element name, thereby reducing the risk of misoperation in manual deployment and improving the reliability of network element upgrade package deployment. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0017] Figure 1 It is a flowchart of a network element upgrade method provided in an embodiment of the present application;
[0018] Figure 2 This is an automatic upgrade architecture diagram based on task scheduling provided in an embodiment of the present application;
[0019] Figure 3 This is an automatic upgrade workflow diagram provided by an embodiment of the present application;
[0020] Figure 4 It is a structural diagram of a network element upgrading device provided in an embodiment of the present application;
[0021] Figure 5 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0022] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.
[0023] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, 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 continuously upgrade network equipment, improve network coverage, increase bandwidth and speed to ensure network stability and reliability. Through network upgrades, communication networks can better meet users' communication needs and provide higher quality services. There are many network elements involved in the network upgrade. The software version of the network element upgrade is developed by equipment vendors according to the 3rd Generation Partnership Project (3GPP) and operator routing organization principles, and deployed to the corresponding network elements to achieve network upgrades. However, the deployment process of existing network element software versions is mainly completed manually, and the risk of manual misoperation is high, resulting in low reliability of software version deployment.
[0025] In order to solve the problems of the prior art, the embodiments of the present application provide a network element upgrade method, device, equipment, storage medium and program product. The network element upgrade method provided by the embodiments of the present application is first introduced below.
[0026] Figure 1 FIG. 1 is a flow chart showing a method for upgrading a network element according to an embodiment of the present application. Figure 1 As shown, a network element upgrade method may include the following steps S101 to S103:
[0027] S101. Receive an upgrade request sent by a user, where the upgrade request includes 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, where the network upgrade workflow is used to schedule a network upgrade task, where the network upgrade task includes an upgrade implementation subtask, and 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, where different network elements correspond to different network element types and different network element names;
[0029] S103. According to the network upgrade workflow, schedule and execute an upgrade implementation subtask, where the upgrade implementation subtask is used to instruct a target upgrade software package to be deployed on a target network element during an upgrade period, where the target upgrade software package is an upgrade software package corresponding to a target upgrade software version number in a preset software package library, where the software package library includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers.
[0030] The network element upgrade method of the embodiment of the present application can receive an upgrade request sent by a user, the upgrade request includes 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, a preset network upgrade workflow of the target network element is started, the network upgrade workflow is used to schedule network upgrade tasks, the network upgrade tasks include upgrade implementation subtasks, 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, and 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 indicate that a target upgrade software package is deployed on the target network element during the upgrade time period, 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 includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers. In this way, the embodiment of the present application can respond to an upgrade request, start the preset network upgrade workflow of the target network element, schedule and execute the upgrade implementation subtasks according to the network upgrade workflow, and automatically deploy the target upgrade software package corresponding to the target upgrade software version number to the target network element corresponding to the target network element type and target network element name, thereby reducing the risk of misoperation in manual deployment and improving the reliability of network element upgrade package deployment.
[0031] The specific implementation methods of the above steps are introduced below.
[0032] In S101, the upgrade request may include a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period.
[0033] The above network element types refer 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 core network devices such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User plane Function (UPF), Network Slice Selection Function (NSSF), and Policy Control Function (PCF).
[0034] The network element name mentioned above refers to a naming method or identifier for identifying and distinguishing different network elements in a network. It is usually an identifier used by a network management system or protocol to uniquely identify each network element in the network.
[0035] The above-mentioned upgrade software version number is a set of numbers and letters used to identify and distinguish different versions of the upgrade software. Generally, the upgrade software version number includes the major version number, the minor version number, the revision number and other parts. Each time the software is updated or a new version is released, the developer will update one part of the version number based on the improvement or modification of the software so that users and developers can clearly understand the update status of the software and distinguish the differences between different versions. The format and rules of the upgrade software version number may vary from software developer to software developer or project.
[0036] The upgrade time period may include an upgrade start time and an upgrade end time. For example, the upgrade time period may be from the upgrade start time 2:00 a.m. to the upgrade end time 4:00 a.m.
[0037] The receiving user's upgrade request may be, illustratively, a request triggered by the receiving user inputting the target network element type, target network element name, target upgrade software version number and upgrade time period into an upgrade work order.
[0038] In S102, the network, illustratively, may be a 4G or 5G core network. The 4G and 5G core networks are key parts of mobile communication networks, responsible for processing functions such as user data transmission, signaling control, user identification, and security authentication. The core network is the hub of the entire mobile communication network, connecting the communication traffic between mobile devices and the Internet.
[0039] The above network includes at least one network element, which is the abbreviation of network element, and refers to various devices, components or nodes in the network, and is a functional unit for transmitting, exchanging, processing and managing data. In a communication network, network elements include routers, switches, servers, firewalls and other devices, which together constitute a complete network system through interconnection. Network elements can be hardware, software, or a combination of the two. In traditional communication networks, network elements usually refer to hardware devices, such as routers, switches, etc., which are used to process functions such as data packet forwarding and signal transmission. With the development of network technology, the rise of concepts such as virtualization and software-defined networking (SDN), network elements can also be virtual devices in the form of software, which implement network functions through software running on general servers. Therefore, network elements can be hardware, software, or a combination of the two, depending on the architecture and technological 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, and different network elements correspond to different network element types and different network element names.
[0041] The above network upgrade workflow can be used to schedule network upgrade tasks, wherein the network upgrade task can include an upgrade implementation subtask, wherein the upgrade implementation subtask is used to instruct the target upgrade software package to be deployed on the target network element during 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 may include at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers.
[0043] In some embodiments, the above-mentioned execution upgrade implementation subtask may specifically include:
[0044] Setting the configuration item of the target network element to a preset first parameter;
[0045] Release the coupling and session of the target network element;
[0046] Obtain the target upgrade software package from the software package library according to the target upgrade software version number;
[0047] Deploy the target upgrade software package on the target network element during the upgrade period;
[0048] Restart the target NE;
[0049] The configuration item of the target network element is set to the preset second parameter.
[0050] The configuration items of the above-mentioned target network element may be, for example, weight items of the target network element. In the embodiment of the present application, the configuration items are not limited to weight items, and the parameters of different configuration items may also be modified according to actual needs of the user, which is not specifically limited here.
[0051] The above-mentioned coupling of the target network element and the release of the session are because the network elements establish a communication connection through coupling, which can be temporary or permanent. The session release refers to the process of disconnecting such a connection to release resources and end the communication.
[0052] The first parameter is a parameter of a configuration item of the target network element in an upgrade environment. The second parameter is a parameter of a configuration item of the target network element in an operating environment.
[0053] In the embodiment of the present application, the configuration item of the target network element is set to the first parameter in the upgrade environment, the coupling and session are released, the target network element is restarted, and the target upgrade software package is deployed to the target network element during the upgrade time period. The upgrade time period is reasonably arranged to reduce the impact on business services and ensure user experience. After the upgrade, the configuration item of the target network element is restored to the second parameter in the operating environment, which can also avoid affecting the normal operation of the network due to configuration errors.
[0054] As an implementation of the present application, in order to improve the reliability of the target network element upgrade, the above network upgrade task may further include a network element backup subtask. Before the above S103, the above method may further include:
[0055] According to the network upgrade workflow, a network element backup subtask is scheduled, where 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] Execute the network element backup subtask to generate a first execution result, where the first execution result is used to indicate whether the execution of the network element backup subtask is successful or failed;
[0057] Generate a first task scheduling rule according to the network element backup subtask and the first execution result, where the first task scheduling rule includes a task name and key task information of the first target subtask;
[0058] When the first execution result indicates that the network element backup subtask is successfully executed, determining the first target subtask as the upgrade implementation subtask;
[0059] The above S103 may specifically include:
[0060] Scheduling the upgrade implementation subtask 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;
[0061] Perform the upgrade implementation subtask.
[0062] The above network element backup subtask instructs to copy the first configuration data of the target network element to a preset storage area, that is, to implement data backup of the target network element.
[0063] The first execution result is used to indicate whether the network element backup subtask is executed successfully or failed, that is, the copying of the first configuration data of the target network element to the preset storage area means that the network element backup subtask is executed successfully, otherwise it fails.
[0064] The first task scheduling rule includes the task name and key task information of the first target subtask. When the first execution result indicates that the network element backup subtask is successfully executed, the first target subtask is determined to be the upgrade implementation subtask; when the first execution result indicates that the network element backup subtask fails to execute, the first target subtask is determined to be the abnormality management subtask.
[0065] In this embodiment, before executing the upgrade implementation subtask, in order to avoid data loss caused by unexpected situations during the upgrade process and to restore it in time, it is also necessary to schedule and execute the network element backup subtask according to the network upgrade workflow, generate a first execution result, copy the first configuration data of the target network element to the preset storage area, and then generate a first task scheduling rule based on the network element backup subtask and the first execution result. When the first execution result indicates that the network element backup subtask is executed successfully, determine that the first target subtask is the upgrade implementation subtask, and then schedule and execute the upgrade implementation subtask 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, thereby improving the reliability of the target network element upgrade.
[0066] As another implementation of the present application, in order to ensure the smooth upgrade process of the target network element, the above network upgrade task may also include a network element inspection subtask. Before scheduling the network element backup subtask according to the network upgrade workflow, the above method may also include:
[0067] Schedule network element inspection subtasks according to the network upgrade workflow;
[0068] Execute the network element inspection subtask, which 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;
[0069] Generate a second execution result according to the inspection report, the second execution result is used to indicate that the network element inspection subtask is executed successfully when the inspection report indicates that the target network element meets the upgrade rule, or to indicate that the network element inspection subtask fails to execute when the inspection report indicates that the target network element does not meet the upgrade rule;
[0070] Generate a second task scheduling rule according to the network element inspection subtask and the second execution result, wherein the second task scheduling rule includes a task name and key task information of the second target subtask;
[0071] When the second execution result indicates that the network element inspection subtask is executed successfully, determining the second target subtask as the network element backup subtask;
[0072] The above-mentioned scheduling of the network element backup subtask according to the network upgrade workflow may specifically include:
[0073] The network element backup subtask is scheduled according to the task name and key task information of the second target subtask in the network upgrade workflow and the second task scheduling rule.
[0074] The network element inspection subtask may instruct the target network element to perform pre-upgrade preparation and inspection and obtain an inspection report, and the inspection report may be used to indicate whether the target network element meets the preset upgrade rules. The pre-upgrade preparation and inspection may be, for example, pre-upgrade software preparation, plug-in preparation, hardware preparation, access inspection, pre-operation environment inspection, etc. The preset upgrade rules may be software preparation, plug-in preparation, and hardware preparation, access inspection to ensure that other devices and environments in the network are ready, and normal environment inspection before the upgrade operation.
[0075] The above second execution result can be used to indicate that the network element inspection subtask is executed successfully when the inspection report indicates that the target network element meets the upgrade rules, or to indicate that the network element inspection subtask fails to execute when the inspection report indicates that the target network element does not meet the upgrade rules. When the second execution result indicates that the network element inspection subtask is executed successfully, the second target subtask is determined to be the network element backup subtask; when the second execution result indicates that the network element inspection subtask fails to execute, the second target subtask is determined to be the abnormality management subtask.
[0076] In this embodiment, before executing the network element backup subtask, in order to ensure the smooth upgrade process of the target network element, it is also necessary to schedule and execute the network element inspection subtask to check whether the target network element meets the preset upgrade rules, and when the inspection report indicates that the target network element meets the upgrade rules, it is characterized that the network element inspection subtask is successfully executed. The second target subtask is determined to be the network element backup subtask, and then the network element backup subtask is scheduled according to the task name and task key information of the second target subtask in the network upgrade workflow and the second task scheduling rules, so as to further improve the reliability of the target network element upgrade.
[0077] As another implementation of the present application, in order to effectively evaluate the upgrade effect, the above network upgrade task may further include a service dialing subtask. After the above upgrade implementation subtask is executed, the above method may further include:
[0078] Generate a third execution result, where the third execution result is used to indicate whether the upgrade implementation subtask is executed successfully or failed;
[0079] Generate a third task scheduling rule according to the upgrade implementation subtask and the third execution result, wherein the third task scheduling rule includes a task name and key task information of the third target subtask;
[0080] If the third execution result indicates that the upgrade implementation subtask is successfully executed, determining the third target subtask as the service dialing subtask;
[0081] Scheduling the service dialing subtask according to the task name and key task information of the third target subtask in the network upgrade workflow and the third task scheduling rule;
[0082] Execute the service dialing test subtask, which is used to instruct the target network element to perform a service test of at least one scenario, obtain test data and test results of each service test, and each test result is used to indicate whether the service test of each scenario is normal.
[0083] The third execution result can be used to indicate that the upgrade implementation subtask is successfully executed when the target upgrade software package is deployed on the target network element during the upgrade period, or to indicate that the upgrade implementation subtask fails to be executed when the target upgrade software package is not deployed on the target network element during the upgrade period. When the third execution result indicates that the upgrade implementation subtask is successfully executed, the third target subtask is determined to be a service dialing subtask; when the third execution result indicates that the upgrade implementation subtask fails to be executed, the third target subtask is determined to be an abnormality management subtask.
[0084] The service dialing subtask instructs the target network element to perform service testing of at least one scenario, and obtains test data and test results of each service test, wherein each test result can be used to indicate whether the service test of each scenario is normal. The at least one scenario can be, for example, data, voice, private network, roaming, etc.
[0085] In this embodiment, after executing the upgrade implementation subtask, a third execution result is generated, and when the third execution result indicates that the upgrade implementation subtask is successfully executed, the third target subtask is determined to be a service dialing subtask, and then the service dialing subtask is scheduled and executed according to the task name and task key information of the third target subtask in the network upgrade workflow and the third task scheduling rule. This can effectively evaluate the upgrade effect and discover problems in a timely manner to ensure the stability and reliability of network operation.
[0086] As another implementation of the present application, in order to ensure that the charges for the service are consistent with the actual usage of the user, the above network upgrade task may also include a billing verification subtask, and after the above execution of the service dialing subtask, it may also include:
[0087] Generate a fourth execution result according to at least one business test result, the fourth execution result being used to characterize the successful execution of the business dialing subtask when at least one business test result indicates that the business test of each scenario is normal, or to characterize the failure of the execution of the business dialing subtask when at least one business test result indicates that the business test of at least one scenario is abnormal;
[0088] Generate a fourth task scheduling rule according to the business dialing subtask and the fourth execution result, wherein the fourth task scheduling rule includes a task name and key task information of the fourth target subtask;
[0089] If the fourth execution result indicates that the service dialing subtask is successfully executed, determining the fourth target subtask as a billing verification subtask;
[0090] Scheduling the billing verification subtask 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;
[0091] Execute the billing verification subtask, which is used to instruct to verify the call record of the target network element according to the test data of at least one scenario to obtain a verification result, and the verification result is used to indicate whether the call record of the target network element is accurate.
[0092] The fourth execution result can be used to indicate that the execution of the service dialing subtask is successful when at least one service test result indicates that the service test of each scenario is normal, or to indicate that the execution of the service dialing subtask fails when at least one service test result indicates that the service test of at least one scenario is abnormal. When the fourth execution result indicates that the execution of the service dialing subtask is successful, the fourth target subtask is determined to be the billing verification subtask; when the fourth execution result indicates that the execution of the service dialing subtask fails, the fourth target subtask is determined to be the abnormality management subtask.
[0093] The billing verification subtask is used to instruct to verify the call list of the target network element according to the test data of at least one scenario to obtain a verification result, wherein the verification result can be used to indicate whether the call list of the target network element is accurate. The call list of the target network element can be obtained in the billing system of the telecommunications operator.
[0094] In this embodiment, after executing the service dialing subtask, a fourth execution result is generated based on at least one service test result, and a fourth task scheduling rule is generated based on the service dialing subtask and the fourth execution result. Then, when the fourth execution result indicates that the service dialing subtask is executed successfully, the fourth target subtask is determined to be the billing verification subtask. Finally, according to the task name and task key information of the fourth target subtask in the network upgrade workflow and the fourth task scheduling rule, the billing verification subtask is scheduled and executed, which can ensure that the service charges are consistent with the actual user usage, and also help to discover possible billing system problems or anomalies.
[0095] As another implementation of the present application, in order to ensure the normal operation of the upgraded network, the above network upgrade task may further include a configuration comparison subtask. After the above billing verification subtask is executed, the above method may further include:
[0096] Generate a fifth execution result according to the verification result, the fifth execution result being used to indicate that the billing verification subtask is executed successfully when the verification result indicates that the billing record of the target network element is accurate, or to indicate that the billing verification subtask fails to execute when the verification result indicates that the billing record of the target network element is inaccurate;
[0097] Generate a fifth task scheduling rule according to the billing verification subtask and the fifth execution result, wherein the fifth task scheduling rule includes a task name and key task information of the fifth target subtask;
[0098] If the fifth execution result indicates that the billing verification subtask is successfully executed, determining the fifth target subtask to be the configuration comparison subtask;
[0099] Scheduling the configuration comparison subtask according to the network upgrade workflow and the task name and key task information of the fifth target subtask in the fifth task scheduling rule;
[0100] The configuration comparison subtask is executed, where the configuration comparison subtask is used to instruct to obtain the second configuration data of the target network element, and compare the second configuration data with the first configuration data to obtain a comparison result, where the comparison result is used to indicate whether the second configuration data is abnormal.
[0101] The fifth execution result can be used to indicate that the billing verification subtask is executed successfully when the verification result indicates that the billing record of the target network element is accurate, or to indicate that the billing verification subtask fails to execute when the verification result indicates that the billing verification subtask is inaccurate. When the fifth execution result indicates that the billing verification subtask is executed successfully, the fifth target subtask is determined to be a configuration comparison subtask; when the fifth execution result indicates that the billing verification subtask fails to execute, the fifth target subtask is determined to be an abnormality management subtask.
[0102] The configuration comparison subtask indicates obtaining the second configuration data of the target network element, and comparing the second configuration data with the first configuration data to obtain a comparison result, wherein the comparison result can be used to indicate whether the second configuration data is abnormal.
[0103] The above-mentioned comparison of the second configuration data and the first configuration data can, illustratively, be to use a text comparison tool or script to identify differences, such as missing configuration, new configuration, modified configuration, etc.; perform a detailed analysis on the compared differences to determine which configuration items have changed, confirm the reasons for the changes, and evaluate the possible impact of these changes on system operation.
[0104] In this embodiment, after executing the billing verification subtask, a fifth execution result is generated based on the verification result, and a fifth task scheduling rule is generated based on the billing verification subtask and the fifth execution result. When the fifth execution result indicates that the billing verification subtask is executed successfully, 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, which can effectively analyze the network element configuration, ensure the normal operation of the network after the upgrade, and promptly discover and resolve potential problems, thereby ensuring the stability and reliability of the network.
[0105] As another implementation of the present application, in order to monitor the performance of the upgraded target network element, the network upgrade task may further include an upgrade duty subtask. After the configuration comparison subtask is executed, the method may further include:
[0106] Generate a sixth execution result according to the comparison result, the sixth execution result being used to indicate that the configuration comparison subtask is executed successfully when the comparison result indicates that the second configuration data is normal, or to indicate that the configuration comparison subtask is executed unsuccessfully when the comparison result indicates that the second configuration data is abnormal;
[0107] Generate a sixth task scheduling rule according to the configuration comparison subtask and the sixth execution result, where the sixth task scheduling rule includes a task name and key task information of the sixth target subtask;
[0108] If the sixth execution result indicates that the configuration comparison subtask is successfully executed, determining the sixth target subtask as the upgrade duty subtask;
[0109] Schedule the upgrade duty subtask according to the network upgrade workflow and the task name and key task information of the sixth target subtask in the sixth task scheduling rule;
[0110] Execute an upgrade duty subtask, where the upgrade duty subtask is used to instruct to obtain operation data of at least one performance indicator of the target network element;
[0111] Generate a seventh execution result according to the operation data of at least one performance indicator of the target network element, the seventh execution result being used to characterize the successful execution of the upgrade duty subtask when the operation data of at least one performance indicator meets the preset threshold value of each performance indicator, or characterize the failure of the upgrade duty subtask when the operation data of at least one performance indicator does not meet the preset threshold value of the performance indicator;
[0112] Generate a seventh task scheduling rule according to the upgrade duty subtask and the seventh execution result, the seventh task scheduling rule including the task name and key task information of the seventh target subtask;
[0113] In the case where the seventh execution result indicates that the upgrade duty subtask is executed successfully, determining that the seventh target subtask indicates the end of the network upgrade workflow;
[0114] The network upgrade workflow is terminated according to the task name and key task information of the seventh target subtask in the network upgrade workflow and the seventh task scheduling rule.
[0115] The sixth execution result can be used to indicate that the configuration comparison subtask is executed successfully when the comparison result indicates that the second configuration data is normal, or to indicate that the configuration comparison subtask fails to execute when the comparison result indicates that the second configuration data is abnormal. When the sixth execution result indicates that the configuration comparison subtask is executed successfully, the sixth target subtask is determined to be the upgrade duty subtask; when the sixth execution result indicates that the configuration comparison subtask fails to execute, the sixth target subtask is determined to be the abnormality management subtask.
[0116] The above-mentioned upgrade duty subtask indicates obtaining the operating data of at least one performance indicator of the target network element, wherein the at least one performance indicator can be, for example, performance indicators such as data flow, bandwidth utilization, packet loss rate, delay time and throughput.
[0117] The seventh execution result can be used to characterize the successful execution of the upgrade duty subtask when the operating data of at least one performance indicator meets the preset threshold of each performance indicator, or to characterize the failure of the upgrade duty subtask when the operating data of at least one performance indicator does not meet the preset threshold of the performance indicator. When the seventh execution result characterizes the successful execution of the upgrade duty subtask, it is determined that the seventh target subtask indicates the end of the network upgrade workflow; when the seventh execution result characterizes the failure of the upgrade duty subtask, it is determined that the seventh target subtask is an abnormal management subtask.
[0118] In this embodiment, after executing the configuration comparison subtask, a sixth execution result is generated based on the comparison result, and a sixth task scheduling rule is generated based on the configuration comparison subtask and the sixth execution result. When the sixth execution result indicates that the configuration comparison subtask is executed successfully, the sixth target subtask is determined to be the upgrade duty 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 duty subtask is scheduled and executed, and according to the operating data of at least one performance indicator of the target network element, a seventh execution result is generated, and according to the upgrade duty subtask and the seventh execution result, a seventh task scheduling rule is generated. When the seventh execution result indicates that the upgrade duty subtask is executed successfully, it is determined that the seventh target subtask indicates the termination of the network upgrade workflow. According to the task name and task key information of the seventh target subtask in the network upgrade workflow and the seventh task scheduling rule, the network upgrade workflow is terminated, which can help monitor the performance of the target network element after the upgrade, so as to promptly discover potential problems and take corresponding measures to repair them.
[0119] As another implementation of the present application, in order to further improve the reliability of the network, the above network upgrade task may further include an abnormal management subtask and an abnormal notification subtask, and the above method may further include:
[0120] In the case where the first execution result indicates that the network element backup subtask has failed to execute, or the second execution result indicates that the network element inspection subtask has failed to execute, or the third execution result indicates that the upgrade implementation subtask has failed to execute, or the fourth execution result indicates that the service dialing subtask has failed to execute, or the fifth execution result indicates that the billing verification subtask has failed to execute, or the sixth execution result indicates that the configuration comparison subtask has failed to execute, or the seventh execution result indicates that the upgrade duty subtask has failed to execute, 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 an abnormal management subtask;
[0121] Scheduling the exception management subtask according to the task name and key task 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;
[0122] Execute the exception management subtask to generate an eighth execution result, where the exception management subtask is used to indicate the identification of the upgrade exception type of the target network element, and perform exception handling according to the exception handling strategy corresponding to the upgrade exception type, and the eighth execution result is used to characterize the success or failure of the execution of the exception management subtask;
[0123] Generate an eighth task scheduling rule according to the abnormal management subtask and the eighth execution result, wherein the eighth task scheduling rule includes a task name and key task information of the eighth target subtask;
[0124] In the case where the eighth execution result indicates that the abnormality management subtask has failed to be executed, determining the eighth target subtask to be the abnormality notification subtask;
[0125] According to the network upgrade workflow and the task name and key task information of the eighth target subtask in the eighth task scheduling rule, schedule the abnormal notification subtask;
[0126] The exception notification subtask is executed. The exception notification subtask is used to instruct the generation of exception information of the target network element and send the exception information to the user, thereby ending the network upgrade workflow.
[0127] The above-mentioned exception management subtask is used to indicate and identify the upgrade exception type of the target network element, and perform exception handling according to the exception handling strategy corresponding to the upgrade exception type.
[0128] The above-mentioned abnormal notification subtask is used to instruct the generation of abnormal information of the target network element and send the abnormal information to the user.
[0129] In this embodiment, when any of the network element backup subtask, network element inspection subtask, upgrade implementation subtask, service dialing subtask, billing verification subtask, configuration comparison subtask and upgrade duty subtask fails to execute, the exception management subtask can be executed to identify the upgrade exception type of the target network element, and perform exception handling according to the exception handling strategy corresponding to the upgrade exception type to further improve the reliability of the network. When the upgrade exception type of the target network element is not identified, the exception notification subtask is executed to send the exception information to the user in a timely manner to ensure the stability of the network.
[0130] In order to facilitate the understanding of the network element upgrade method in the embodiment of the present application, the actual application process of this network element upgrade method is described as follows:
[0131] The embodiment of the present application adopts a task-based scheduling mechanism to manage and schedule multiple subtasks of the core network (i.e. the above-mentioned network) upgrade process, and realize the automatic loading of the software version (i.e. the above-mentioned upgrade software package). The automatic upgrade task (i.e. the above-mentioned network upgrade task) refers to the independent system capabilities of each telecommunications operator, mainly including network element inspection, network element backup, upgrade implementation, service dialing verification, billing verification, configuration comparison and upgrade duty subtasks. Each subtask is executed independently 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 tasks
[0133]
[0134] like 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 rules through the scheduling workflow to complete the entire automatic upgrade. In this architecture, the software storage module (equivalent to the above-mentioned software package library) is a module for storing and managing upgrade software packages, which can be implemented by 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. Tasks can be added, deleted and modified. Different tasks may be called for the upgrade process of different network element types, which can be flexibly called and managed.
[0135] The task scheduling module includes:
[0136] Scheduling start: Scheduling start completes the triggering of the automatic upgrade scheduling workflow (i.e. the above-mentioned network upgrade workflow), which can be achieved in a variety of ways (such as upgrade work order triggering). Scheduling start must contain the key fields required for the automatic upgrade scheduling workflow, such as upgrade network element type, upgrade network element name, upgrade software version number, upgrade start / end time, etc.
[0137] Scheduling rules: Scheduling rules are the key to the execution of task scheduling workflows. The workflow uses scheduling rules to decide the next task to be executed at each subtask node. Table 2 shows the task scheduling rules. The workflow maintains the task scheduling rule table at each subtask node and executes task scheduling according to the rule table. The subtask status may be success, failure, or null.
[0138] Table 2 Task scheduling rules
[0139] Current subtask The name of the subtask currently being executed Subtask Status The result status of the current subtask execution Next subtask The name of the next subtask to be executed Task Keywords Key information required for the next subtask to execute
[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 rules.
[0141] The automatic upgrade workflow schedules each subtask to complete the automatic upgrade process. Figure 3 The following is an automatic upgrade workflow. In each subtask node, the workflow generates task scheduling rules. Figure 3 Scheduling rules 1 and 2 on each subtask node indicate the next subtask scheduled by the workflow and the keywords required for the execution of the next subtask when the current subtask execution status is success and failure, respectively. A subtask node has only one workflow scheduling rule at a time.
[0142] The scheduling starts with triggering the workflow with the key information of the upgrade. The key information is used as the keyword for the execution of subsequent subtasks, including network element type, network element name, version number, and upgrade time. After the scheduling is started, the workflow calls the network element inspection subtask to perform pre-upgrade preparation and inspection. After the execution is completed, the workflow generates a scheduling rule (equivalent to the above-mentioned second task scheduling rule). If the subtask execution fails, the next subtask exception management is executed according to Rule 2. 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 above-mentioned target network element). After the execution is completed, the workflow generates a scheduling rule (equivalent to the above-mentioned first task scheduling rule). If the subtask execution fails, the next subtask exception management is executed according to Rule 2. 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 above-mentioned target upgrade software package) from the version storage module according to the keyword version number, and performs the deployment operation of the specific software package according to the implementation start time. After the execution is completed, the workflow generates a scheduling rule (equivalent to the above-mentioned scheduling rule for the third task). If the subtask fails to execute, the next subtask exception management is executed according to rule 2. If the execution is successful, the next subtask service dial test is executed according to rule 1. The service dial test subtask completes the service test of the upgraded network element. After the execution is completed, the workflow generates a scheduling rule (equivalent to the above-mentioned scheduling rule for the fourth task). If the subtask fails to execute, the next subtask exception management is executed according to rule 2. If the execution is successful, the next subtask billing verification is executed according to rule 1. The billing verification subtask completes the service test call record verification of the billing network element according to the keyword dial test number and dial test time. After the execution is completed, the workflow generates a scheduling rule (equivalent to the above-mentioned scheduling rule for the fifth task). If the subtask fails to execute, the next subtask exception management is executed according to rule 2. If the execution is successful, the next subtask configuration comparison is executed according to rule 1. The configuration comparison subtask collects the network element configuration after the upgrade implementation and compares it with the backup configuration according to the network element name. After the execution is completed, the workflow generates a scheduling rule (equivalent to the scheduling rule of the sixth task mentioned above). If the subtask fails to execute, the next subtask exception management is executed according to rule 2. If the execution is successful, the next subtask upgrade duty is executed according to rule 1. The upgrade duty subtask completes indicator monitoring, business monitoring and network element alarm. After the execution is completed, the workflow generates a scheduling rule (equivalent to the scheduling rule of the seventh task mentioned above). If the subtask fails to execute, the next subtask exception management is executed according to rule 2. If the execution is successful, the workflow ends according to rule 1.
[0143] The exception management subtask in the workflow completes the exception identification and processing of failed subtasks. After the exception management subtask is executed, the workflow generates a scheduling rule (equivalent to the eighth task scheduling rule mentioned above). If the subtask is executed successfully, the workflow ends according to Rule 1. If the execution fails, the next subtask exception notification is executed according to Rule 2. The workflow ends after the exception notification subtask is called.
[0144] In the embodiment of the present application, compared with the manually completed software version management and deployment method, the automatic upgrade of the operator core network software based on task scheduling in the embodiment of the present application greatly improves the agility of software version deployment, provides the ability of rapid deployment for the update and iteration of the telecommunications core network software version, and greatly improves the pace of rapid application of new functions and technologies in 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 human errors and further improve the reliability of software version deployment. Compared with the Development and Operations (DevOps) model, the embodiment of the present application proposes a more rigorous deployment process while constructing the automatic upgrade workflow of the telecommunications core network. First, the task-based workflow is more standardized and systematic, and the executed tasks are more comprehensive, not only completing software deployment, but also completing rigorous business testing and verification; second, exception management is introduced to judge and handle exceptions in the workflow to ensure that the process is manageable and controllable.
[0145] Based on the network element upgrade method provided in the above embodiment, the present application also provides a specific implementation of a network element upgrade device. It can be understood that the relevant descriptions in the following device embodiments can refer to the above method embodiments, and for the sake of brevity, they will not be repeated. Please refer to the following embodiments.
[0146] See also Figure 4 , is a structural diagram of a network element upgrading device 400 provided in an embodiment of the present application, which may include: a receiving module 401, a starting module 402 and a first execution module 403.
[0147] The receiving module 401 is used to receive an upgrade request sent by a user, where the upgrade request includes a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period;
[0148] A starting module 402 is used to start a preset network upgrade workflow of a target network element in response to an upgrade request, where the network upgrade workflow is used to schedule a network upgrade task, where the network upgrade task includes an upgrade implementation subtask, where 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, and different network elements correspond to different network element types and different network element names;
[0149] The first execution module 403 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 software package to be deployed on the target network element during the upgrade time period. 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 includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package. Different upgrade software packages correspond to different upgrade software version numbers.
[0150] The network element upgrade device of the embodiment of the present application is capable of receiving 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; in response to the upgrade request, starting a preset network upgrade workflow of the target network element, the network upgrade workflow is used to schedule a network upgrade task, the network upgrade task includes an upgrade implementation subtask, 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, and different network elements correspond to different network element types and different network element names; according to the network upgrade workflow, scheduling and executing the upgrade implementation subtask, the upgrade implementation subtask is used to indicate that a target upgrade software package is deployed on the target network element during the upgrade time period, 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 includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers. In this way, the embodiment of the present application can respond to an upgrade request, start the preset network upgrade workflow of the target network element, schedule and execute the upgrade implementation subtasks according to the network upgrade workflow, and automatically deploy the target upgrade software package corresponding to the target upgrade software version number to the target network element corresponding to the target network element type and target network element name, thereby reducing the risk of misoperation in manual deployment and improving the reliability of network element upgrade package deployment.
[0151] As an implementation of the present 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, and the device 400 may further include:
[0152] A first scheduling module, configured to schedule a network element backup subtask according to a network upgrade workflow, wherein the network element backup subtask is configured to instruct to copy first configuration data of a target network element to a preset storage area;
[0153] A second execution module is used to execute the network element backup subtask and generate a first execution result, where the first execution result is used to indicate whether the network element backup subtask is executed successfully or failed;
[0154] A first generating module, configured to generate a first task scheduling rule according to the network element backup subtask and the first execution result, wherein the first task scheduling rule includes a task name and key task information of the first target subtask;
[0155] A first determination module is used to determine that the first target subtask is an upgrade implementation subtask when the first execution result indicates that the network element backup subtask is executed successfully;
[0156] The first execution module 403 may include:
[0157] A scheduling unit, configured to schedule the upgrade implementation subtask 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;
[0158] The execution unit is used to execute the upgrade implementation subtask.
[0159] As another implementation of the present application, in order to ensure the smooth upgrading process of the target network element, the network upgrading task may further include a network element inspection subtask, and the device 400 may further include:
[0160] The second scheduling module is used to schedule the network element inspection subtask according to the network upgrade workflow;
[0161] The third execution module is used to execute the network element inspection subtask, which is used to instruct the target network element to perform pre-upgrade preparation and inspection and obtain an inspection report, and the inspection report is used to indicate whether the target network element meets the preset upgrade rules;
[0162] A second generating module is used to generate a second execution result according to the inspection report, the second execution result is used to characterize the successful execution of the network element inspection subtask when the inspection report indicates that the target network element meets the upgrade rule, or to characterize the failure of the network element inspection subtask when the inspection report indicates that the target network element does not meet the upgrade rule;
[0163] A third generating module is used to generate a second task scheduling rule according to the network element inspection subtask and the second execution result, wherein the second task scheduling rule includes a task name and task key information of the second target subtask;
[0164] A second determination module is used to determine that the second target subtask is a network element backup subtask when the second execution result indicates that the network element inspection subtask is executed successfully;
[0165] The first scheduling module is specifically used to schedule the network element backup subtask according to the task name and task key information of the second target subtask in the network upgrade workflow and the second task scheduling rule.
[0166] As another implementation of the present application, in order to effectively evaluate the upgrade effect, the network upgrade task may further include a service dialing subtask, and the device 400 may further include:
[0167] A fourth generating module, used to generate a third execution result, where the third execution result is used to indicate whether the upgrade implementation subtask is executed successfully or failed;
[0168] A fifth generating module, configured to generate a third task scheduling rule according to the upgrade implementation subtask and the third execution result, wherein the third task scheduling rule includes a task name and key task information of the third target subtask;
[0169] A third determination module is used to determine that the third target subtask is a service dialing subtask when the third execution result indicates that the upgrade implementation subtask is successfully executed;
[0170] A third scheduling module is used to schedule the service dialing subtask according to the task name and task key information of the third target subtask in the network upgrade workflow and the third task scheduling rule;
[0171] The fourth execution module is used to execute the service dialing subtask, which is used to instruct the target network element to perform service testing of at least one scenario, obtain test data and test results of each service test, and each test result is used to indicate whether the service test of each scenario is normal.
[0172] As another implementation of the present application, in order to ensure that the charges for the service are consistent with the actual usage of the user, the network upgrade task may further include a billing verification subtask, and the apparatus 400 may further include:
[0173] A sixth generating module, configured to generate a fourth execution result according to at least one business test result, the fourth execution result being used to characterize the successful execution of the business dialing subtask when at least one business test result indicates that the business test of each scenario is normal, or to characterize the failure of the execution of the business dialing subtask when at least one business test result indicates that the business test of at least one scenario is abnormal;
[0174] A seventh generating module, configured to generate a fourth task scheduling rule according to the business dialing subtask and the fourth execution result, wherein the fourth task scheduling rule includes a task name and key task information of the fourth target subtask;
[0175] A fourth determination module, configured to determine that the fourth target subtask is a billing verification subtask when the fourth execution result indicates that the service dialing subtask is successfully executed;
[0176] A fourth scheduling module, used to schedule the billing verification subtask according to the task name and task key information of the fourth target subtask in the network upgrade workflow and the fourth task scheduling rule;
[0177] The fifth execution module is used to execute the billing verification subtask, which is used to instruct the call record of the target network element to be verified according to the test data of at least one scenario to obtain a verification result, and the verification result is used to indicate whether the call record of the target network element is accurate.
[0178] As another implementation of the present application, in order to ensure the normal operation of the upgraded network, the network upgrade task further includes a configuration comparison subtask, and the device 400 may further include:
[0179] an eighth generation module, configured to generate a fifth execution result according to the verification result, the fifth execution result being used to characterize the successful execution of the billing verification subtask when the verification result indicates that the bill of the target network element is accurate, or to characterize the failure of the billing verification subtask when the verification result indicates that the bill of the target network element is inaccurate;
[0180] A ninth generating module, configured to generate a fifth task scheduling rule according to the billing verification subtask and the fifth execution result, wherein the fifth task scheduling rule includes a task name and key task information of the fifth target subtask;
[0181] A fifth determination module, configured to determine that the fifth target subtask is a configuration comparison subtask when the fifth execution result indicates that the billing verification subtask is successfully executed;
[0182] A fifth scheduling module, used to schedule the configuration comparison subtask according to the task name and task key information of the fifth target subtask in the network upgrade workflow and the fifth task scheduling rule;
[0183] The sixth execution module is used to execute the configuration comparison subtask, which is used to instruct to obtain the second configuration data of the target network element, and compare the second configuration data with the first configuration data to obtain a comparison result, and the comparison result is used to indicate whether the second configuration data is abnormal.
[0184] As another implementation of the present application, in order to monitor the performance of the upgraded target network element, the network upgrade task further includes an upgrade duty subtask, and the device 400 may further include:
[0185] a tenth generating module, configured to generate a sixth execution result according to the comparison result, wherein the sixth execution result is used to indicate that the configuration comparison subtask is successfully executed when the comparison result indicates that the second configuration data is normal, or to indicate that the configuration comparison subtask fails to execute when the comparison result indicates that the second configuration data is abnormal;
[0186] An eleventh generating module is used to generate a sixth task scheduling rule according to the configuration comparison subtask and the sixth execution result, where the sixth task scheduling rule includes a task name and key task information of the sixth target subtask;
[0187] A sixth determination module, configured to determine that the sixth target subtask is an upgrade duty subtask when the sixth execution result indicates that the configuration comparison subtask is successfully executed;
[0188] A sixth scheduling module, used to schedule the upgrade duty 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] A seventh execution module, configured to execute an upgrade duty subtask, wherein the upgrade duty subtask is configured to instruct to obtain operation data of at least one performance indicator of a target network element;
[0190] A twelfth generating module, configured to generate a seventh execution result according to the operating data of at least one performance indicator of the target network element, the seventh execution result being used to characterize the successful execution of the upgrade duty subtask when the operating data of at least one performance indicator meets the preset threshold of each performance indicator, or to characterize the failure of the upgrade duty subtask when the operating data of at least one performance indicator does not meet the preset threshold of the performance indicator;
[0191] A thirteenth generating module is used to generate a seventh task scheduling rule according to the upgrade duty subtask and the seventh execution result, wherein the seventh task scheduling rule includes a task name and key task information of the seventh target subtask;
[0192] A seventh determination module, configured to determine that the seventh target subtask indicates that the network upgrade workflow is terminated when the seventh execution result indicates that the upgrade duty subtask is successfully executed;
[0193] The ending module is used to end 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.
[0194] As another implementation of the present application, in order to further improve the reliability of the network, the network upgrade task may further include an abnormal management subtask and an abnormal notification subtask, the network upgrade task also includes an abnormal management subtask and an abnormal notification subtask, and the device 400 further includes:
[0195] an eighth determination module, for determining 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 an abnormal management subtask when the first execution result indicates that the network element backup subtask has failed to execute, or the second execution result indicates that the network element inspection subtask has failed to execute, or the third execution result indicates that the upgrade implementation subtask has failed to execute, or the fourth execution result indicates that the service dialing subtask has failed to execute, or the fifth execution result indicates that the billing verification subtask has failed to execute, or the sixth execution result indicates that the configuration comparison subtask has failed to execute, or the seventh execution result indicates that the upgrade duty subtask has failed to execute;
[0196] a seventh scheduling module, configured to schedule an exception management subtask according to the task name and key task 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] an eighth execution module, configured to execute the exception management subtask and generate an eighth execution result, wherein the exception management subtask is used to indicate and identify the upgrade exception type of the target network element, and perform exception handling according to the exception handling strategy corresponding to the upgrade exception type, and the eighth execution result is used to characterize the success or failure of the execution of the exception management subtask;
[0198] A generating module, used for generating an eighth task scheduling rule according to the abnormal management subtask and the eighth execution result, wherein the eighth task scheduling rule includes a task name and key task information of the eighth target subtask;
[0199] A ninth determination module, configured to determine that the eighth target subtask is an exception notification subtask when the eighth execution result indicates that the exception management subtask has failed to execute;
[0200] An eighth scheduling module, configured to schedule the abnormal notification subtask according to the task name and key task information of the eighth target subtask in the network upgrade workflow and the eighth task scheduling rule;
[0201] The ninth execution module is used to execute the abnormal notification subtask, which is used to instruct the generation of abnormal information of the target network element and send the abnormal information to the user, thereby ending the network upgrade workflow.
[0202] In some embodiments, the first execution module 403 may specifically include:
[0203] A first setting unit, used to set the configuration item of the target network element to a preset first parameter;
[0204] A release unit, used to release the coupling and session of the target network element;
[0205] An acquisition unit, used to acquire a target upgrade software package from a software package library according to a target upgrade software version number;
[0206] A deployment unit, used to deploy the target upgrade software package on the target network element during the upgrade period;
[0207] A restart unit, used to restart the target network element;
[0208] The second setting unit is used to set the configuration item of the target network element to a preset second parameter.
[0209] Figure 5 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application is shown.
[0210] The electronic device may include a processor 501 and a memory 502 storing computer program instructions.
[0211] Specifically, the processor 501 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0212] The memory 502 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 502 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 502 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 502 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 502 is a non-volatile solid-state memory.
[0213] In certain embodiments, the memory 502 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an 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 including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.
[0214] The processor 501 implements any one of the network element upgrading methods in the above embodiments by reading and executing the computer program instructions stored in the memory 502 .
[0215] In one example, the electronic device may further include a communication interface 503 and a bus 510. Figure 5 As shown, the processor 501, the memory 502, and the communication interface 503 are connected via a bus 510 and communicate with each other.
[0216] The communication interface 503 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0217] Bus 510 includes hardware, software or both, and the parts of electronic equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 510 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.
[0218] The electronic device can execute the network element upgrade method in the embodiment of the present application, thereby realizing the combination Figure 1 and Figure 4 The described network element upgrading method and device.
[0219] In addition, in combination with the network element upgrade method in the above embodiment, the embodiment of the present application can provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any network element upgrade method in the above embodiment is implemented.
[0220] In combination with the network element upgrade method in the above embodiment, an embodiment of the present application may provide a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes any one of the network element upgrade methods above.
[0221] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present 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 the steps after understanding the spirit of the present application.
[0222] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting 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, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.
[0223] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.
[0224] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.
[0225] The above is only a specific implementation of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.
Claims
1. A network element upgrade method, It is characterized in that include: 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; In response to the upgrade request, start a preset network upgrade workflow of the target network element, the network upgrade workflow is used to schedule a network upgrade task, the network upgrade task includes an upgrade implementation subtask, 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, and 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 indicate that a target upgrade software package is deployed on the target network element in the upgrade time period, 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 includes at least one upgrade software package and an upgrade software version number corresponding to each software upgrade package, and different upgrade software packages correspond to different upgrade software version numbers.
2. The method according to claim 1, It is 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 also includes: According to the network upgrade workflow, scheduling the network element backup subtask, wherein 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; Execute the network element backup subtask to generate a first execution result, where the first execution result is used to indicate whether the network element backup subtask is executed successfully or failed; Generate a first task scheduling rule according to the network element backup subtask and the first execution result, wherein the first task scheduling rule includes a task name and key task information of the first target subtask; If the first execution result indicates that the network element backup subtask is successfully executed, determining the first target subtask to be the upgrade implementation subtask; The step of scheduling and executing the upgrade implementation subtask according to the network upgrade workflow includes: Scheduling the upgrade implementation subtask 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; Execute the upgrade implementation subtask.
3. The method according to claim 2, It is 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 also includes: Scheduling the network element inspection subtask according to the network upgrade workflow; Executing the network element inspection subtask, 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; Generate a second execution result according to the inspection report, the second execution result being used to indicate that the network element inspection subtask is successfully executed when the inspection report indicates that the target network element complies with the upgrade rule, or to indicate that the network element inspection subtask fails to execute when the inspection report indicates that the target network element does not comply with the upgrade rule; Generate a second task scheduling rule according to the network element inspection subtask and the second execution result, wherein the second task scheduling rule includes a task name and key task information of the second target subtask; If the second execution result indicates that the network element inspection subtask is executed successfully, determining the second target subtask to be the network element backup subtask; The scheduling of the network element backup subtask according to the network upgrade workflow includes: The network element backup subtask is scheduled according to the network upgrade workflow and the task name and task key information of the second target subtask in the second task scheduling rule.
4. The method according to claim 2, It is characterized in that The network upgrade task also includes a service dialing subtask, and after executing the upgrade implementation subtask, further includes: Generate a third execution result, where the third execution result is used to indicate whether the upgrade implementation subtask is executed successfully or failed; Generate a third task scheduling rule according to the upgrade implementation subtask and the third execution result, wherein the third task scheduling rule includes a task name and key task information of the third target subtask; In the case where the third execution result indicates that the upgrade implementation subtask is successfully executed, determining the third target subtask to be the service dialing subtask; Scheduling the service dialing subtask according to the task name and key task information of the third target subtask in the network upgrade workflow and the third task scheduling rule; Execute the service dialing test subtask, the service dialing test subtask is used to instruct the target network element to perform service testing of at least one scenario, obtain test data and test results of each service test, and each test result is used to indicate whether the service test of each scenario is normal.
5. The method according to claim 4, It is characterized in that The network upgrade task also includes a billing verification subtask, and after executing the service dial test subtask, further includes: Generate a fourth execution result according to the at least one service test result, wherein the fourth execution result is used to characterize that the service dialing subtask is successfully executed when the at least one service test result indicates that the service test of each of the scenarios is normal, or to characterize that the service dialing subtask fails to execute when the at least one service test result indicates that the service test of at least one of the scenarios is abnormal; Generate a fourth task scheduling rule according to the service dialing subtask and the fourth execution result, wherein the fourth task scheduling rule includes a task name and key task information of the fourth target subtask; In the case where the fourth execution result indicates that the service dialing subtask is successfully executed, determining that the fourth target subtask is the billing verification subtask; Scheduling the billing verification subtask 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; Execute the billing verification subtask, the billing verification subtask is used to instruct to verify the call record of the target network element according to the test data of the at least one scenario, and obtain a verification result, and the verification result is used to indicate whether the call record of the target network element is accurate.
6. The method according to claim 5, It is characterized in that The network upgrade task also includes a configuration comparison subtask, and after executing the billing verification subtask, further includes: Generate a fifth execution result according to the verification result, wherein the fifth execution result is used to characterize the successful execution of the billing verification subtask when the verification result indicates that the call bill of the target network element is accurate, or to characterize the failure of the execution of the billing verification subtask when the verification result indicates that the call bill of the target network element is inaccurate; Generate a fifth task scheduling rule according to the billing verification subtask and the fifth execution result, wherein the fifth task scheduling rule includes a task name and key task information of the fifth target subtask; In a case where the fifth execution result indicates that the billing verification subtask is successfully executed, determining that the fifth target subtask is the configuration comparison subtask; Scheduling 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; Execute the configuration comparison subtask, where the configuration comparison subtask is used to instruct obtaining second configuration data of the target network element, and comparing the second configuration data with the first configuration data to obtain a comparison result, where the comparison result is used to indicate whether the second configuration data is abnormal.
7. The method according to claim 6, It is characterized in that The network upgrade task also includes an upgrade duty subtask, and after executing the configuration comparison subtask, further includes: Generate a sixth execution result according to the comparison result, wherein the sixth execution result is used to indicate that the configuration comparison subtask is successfully executed if the comparison result indicates that the second configuration data is normal, or to indicate that the configuration comparison subtask is failed if the comparison result indicates that the second configuration data is abnormal; Generate a sixth task scheduling rule according to the configuration comparison subtask and the sixth execution result, wherein the sixth task scheduling rule includes a task name and key task information of the sixth target subtask; When the sixth execution result indicates that the configuration comparison subtask is successfully executed, determining the sixth target subtask as the upgrade duty subtask; Scheduling the upgrade duty 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; Executing the upgrade duty subtask, where the upgrade duty subtask is used to instruct to obtain operation data of at least one performance indicator of the target network element; Generate a seventh execution result according to the operating data of at least one performance indicator of the target network element, wherein the seventh execution result is used to characterize that the upgrade duty subtask is successfully executed when the operating data of at least one performance indicator meets the preset threshold of each performance indicator, or to characterize that the upgrade duty subtask fails to be executed when the operating data of at least one performance indicator does not meet the preset threshold of the performance indicator; Generate a seventh task scheduling rule according to the upgrade duty subtask and the seventh execution result, wherein the seventh task scheduling rule includes a task name and key task information of the seventh target subtask; In a case where the seventh execution result indicates that the upgrade duty subtask is executed successfully, determining that the seventh target subtask indicates to end the network upgrade workflow; The network upgrade workflow is terminated according to the task name and key task information of the seventh target subtask in the network upgrade workflow and the seventh task scheduling rule.
8. The method according to any one of claims 2 to 7, It is characterized in that The network upgrade task also includes an abnormality management subtask and an abnormality notification subtask, and the method further includes: In the case where the first execution result indicates that the network element backup subtask has failed to execute, or the second execution result indicates that the network element inspection subtask has failed to execute, or the third execution result indicates that the upgrade implementation subtask has failed to execute, or the fourth execution result indicates that the service dialing subtask has failed to execute, or the fifth execution result indicates that the billing verification subtask has failed to execute, or the sixth execution result indicates that the configuration comparison subtask has failed to execute, or the seventh execution result indicates that the upgrade duty subtask has failed to execute, 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 abnormal management subtask; Scheduling the exception management subtask 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; Executing the exception management subtask to generate an eighth execution result, wherein the exception management subtask is used to indicate identifying the upgrade exception type of the target network element, and performing exception handling according to the exception handling strategy corresponding to the upgrade exception type, and the eighth execution result is used to characterize the success or failure of the execution of the exception management subtask; generating an eighth task scheduling rule according to the abnormal management subtask and the eighth execution result, wherein the eighth task scheduling rule includes a task name and key task information of the eighth target subtask; In a case where the eighth execution result indicates that the abnormality management subtask fails to be executed, determining the eighth target subtask to be the abnormality notification subtask; Scheduling the abnormal 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; The abnormal notification subtask is executed, where the abnormal notification subtask is used to instruct the generation of abnormal information of the target network element and send the abnormal information to the user, thereby ending the network upgrade workflow.
9. The method according to claim 1, It is characterized in that The performing of the upgrade implementation subtask includes: Setting the configuration item of the target network element to a preset first parameter; releasing the coupling and session of the target network element; According to the target upgrade software version number, obtaining the target upgrade software package in the software package library; Deploy the target upgrade software package on the target network element during the upgrade time period; Restarting the target network element; The configuration item of the target network element is set to a preset second parameter.
10. A network element upgrading device, It is characterized in that The device comprises: A receiving module, configured to receive an upgrade request sent by a user, wherein the upgrade request includes a target network element type, a target network element name, a target upgrade software version number, and an upgrade time period; A starting module, configured to start a preset network upgrade workflow of a target network element in response to the upgrade request, wherein the network upgrade workflow is used to schedule a network upgrade task, wherein the network upgrade task includes an upgrade implementation subtask, and 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, and 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, wherein the upgrade implementation subtask is used to indicate that a target upgrade software package is deployed on the target network element during the upgrade time period, and the target upgrade software package is an upgrade software package corresponding to the target upgrade software version number in a preset software package library, wherein the software package library includes at least one upgrade software package and an upgrade software version number corresponding to each of the software upgrade packages, and different upgrade software packages correspond to different upgrade software version numbers.
11. An electronic device, It is characterized in that The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the network element upgrade method according to any one of claims 1 to 9 is implemented.
12. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by the processor, the network element upgrading method according to any one of claims 1 to 9 is implemented.
13. A computer program product, It is characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the network element upgrading method as described in any one of claims 1-9.
Citation Information
Patent Citations
Lightweight core network element software version upgrading method and system
CN116166295A
Service request processing method and system and electronic equipment
CN116723111A
Network element instruction updating method and device, product, medium and equipment
CN116962164A
Version upgrading method, configuration parameter construction method, equipment and medium
CN118101464A
Method and system for upgrading software versions of network elements with distributed centralized scheduling
WO2012083643A1
