Scene-oriented network operation management method and device
By obtaining and decomposing the constraints of network operation scenarios, determining and sorting task items, and forming an automatic closed loop, the problem of the inability to achieve automatic closed loop and interface complexity in the existing technology is solved, and the efficiency of network operation is improved.
Patent Information
- Application Number
- CN202311533078.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-15
- Publication Date
- 2025-05-27
AI Technical Summary
In the prior art, automatic closed-loop processing based on network operation scenarios cannot be realized, and the human-computer interface of the network management and control system is complex, the operation steps and parameters are cumbersome, and the operation efficiency is low.
By obtaining the network operation scenario and initial constraints, it is divided into basic constraints and extended constraints, it determines basic task items and extended task items, sorts and executes task items, and forms an automatic closed loop.
Automatic closed-loop processing based on network operation scenarios is realized, which reduces the complexity of human-computer interfaces and improves the efficiency of network operation.
Smart Images
Figure CN120050184A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of telecommunications network management and control systems, and particularly to a scenario-oriented network operation management method and device. Background Art
[0002] Each link in the current telecommunications network operation involves numerous operations and complex operation parameters. Generally, a series of different operations such as querying, creating, and updating need to be performed segmentally in control systems at all levels to complete an operation task, and the corresponding time consumption is very long. Therefore, to ensure network operation, high requirements are imposed on operation and maintenance personnel. Firstly, they need to have a comprehensive network operation knowledge system, and at the same time, have an in-depth understanding of various operation operations and their parameters of control systems at all levels to effectively avoid operation errors.
[0003] Intelligent operation management is one of the main future trends. The actual network management and control system first needs to achieve the ability of automatic closed-loop of processes to reduce the need for human intervention. At the same time, the input requirements of the human-machine interface should be simplified to truly achieve the operator's goal of reducing labor costs. Network operation tasks are usually executed at the granularity of scenarios, and the network operation ability based on scenarios is a typical dimension for evaluating the intelligent level in the industry.
[0004] Existing solutions do not have the ability of automatic closed-loop processing based on the granularity of network operation scenarios, and at the same time, there are problems such as complex human-machine interfaces of network management and control systems, cumbersome operation steps and parameters, and low operation efficiency. Summary of the Invention
[0005] This application provides a scenario-oriented network operation management method and device, which can solve the technical problem that automatic closed-loop based on network operation scenarios cannot be achieved in the prior art.
[0006] In a first aspect, an embodiment of this application provides a scenario-oriented network operation management method, including the steps of:
[0007] S1. Obtain a network operation scenario and initial constraint conditions;
[0008] S2. Divide the initial constraint conditions into basic constraint conditions and extended constraint conditions;
[0009] S3. Determine basic task items according to the network operation scenario, parse the extended constraint conditions, and determine additional extended task items;
[0010] S4. Sort all task items of the network operation scenario according to task categories, and at the same time set input parameters of the task items;
[0011] S5. Execute all task items according to the task sorting.
[0012] In combination with the first aspect, in one embodiment, before or during the step S1, the following steps are further included: establishing a network operation scenario library in advance for storing all sub-scenarios in the entire life cycle of network operation; and establishing an operation task library for storing all operation tasks that should be executed in each stage of the entire life cycle of network operation, where each operation task includes at least one task item.
[0013] In combination with the first aspect, in one embodiment, each stage of the entire life cycle of network operation includes four types of tasks, namely, perception type, analysis type, decision type, and execution type. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.
[0014] In combination with the first aspect, in one embodiment, the step S2 includes:
[0015] When the network operation scenario obtained in step S1 exists in the network operation scenario library, obtain the minimum constraint set information corresponding to the network operation scenario;
[0016] Set the initial constraint conditions existing in the minimum constraint set as the basic constraint conditions, and set the other initial constraint conditions as the extended constraint conditions.
[0017] In combination with the first aspect, in one embodiment, in the step S3, when parsing the extended constraint conditions to determine the extended task items to be added, when the extended constraint condition represents resource information, in combination with the network operation scenario, determine the task items corresponding to the resource type from the operation task library.
[0018] In combination with the first aspect, in one embodiment, in the step S3, when parsing the extended constraint conditions to determine the extended task items to be added, when the extended constraint condition represents index information, divide the index into single-value type, rank type, and composite type according to the index value data type and index characteristics;
[0019] For single-value type indexes, determine the available task items corresponding to the indexes, and determine the corresponding task items to be added for the single-value type indexes from the operation task library according to the network operation scenario;
[0020] For rank type indexes, there are no corresponding task items;
[0021] For composite type indexes, decompose them into at least two other types of indexes according to the task selection strategy of network scenario information, and then perform corresponding processing according to the decomposed index types.
[0022] In combination with the first aspect, in one embodiment, in the step S3, when parsing the extended constraint conditions to determine the extended task items to be added, when the extended constraint condition represents time information, set the time and corresponding actions for controlling the task loop.
[0023] In combination with the first aspect, in one embodiment, in step S3, the extended constraint conditions are parsed, and the task loop control parameters are further determined. The task loop control parameters are the control conditions of the task loop;
[0024] In step S5, the corresponding task loop is controlled according to the task loop control parameters, and all task items are executed according to the task sorting within the task loop.
[0025] In combination with the first aspect, in one embodiment, the sorting of all task items in the network operation scenario according to the task category in step S4 includes:
[0026] All task items to be executed are sorted in the order of the perception class, analysis class, decision class, and execution class; for task items of the same type, the basic task items take precedence over the extended task items; and multiple basic task items or extended task items of the same type support concurrent execution; at the same time, duplicate task items are deleted.
[0027] In combination with the first aspect, in one embodiment, the setting of the input parameters of the task item in step S4 includes:
[0028] Determine the data types to be perceived according to the network operation scenario;
[0029] Determine the resource objects of the network operation instance according to the basic constraint conditions and the extended constraint conditions representing the resource information in step S2;
[0030] Determine the input parameter values of the basic perception tasks according to the resource objects and the data types to be perceived.
[0031] In combination with the first aspect, in one embodiment, before or in step S1, a management and control interface library is further established in advance to store all interfaces provided by the lower-level management and control systems or network elements that can be called by the task items; in step S5, the task items call the associated interfaces as needed during the execution process.
[0032] In combination with the first aspect, in one embodiment, an external interface for the network operation scenario is provided. The input information of the external interface includes the network operation scenario and the initial constraint conditions, and the input form is structured or unstructured data; when unstructured data is used, the information extraction of the network operation scenario and the initial constraint conditions is further performed.
[0033] In a second aspect, an embodiment of the present application provides a scenario-oriented network operation management device, including:
[0034] An acquisition module for acquiring a network operation scenario and initial constraint conditions;
[0035] A distinguishing module, configured to divide the initial constraint conditions into basic constraint conditions and extended constraint conditions;
[0036] An extension module, configured to determine basic task items according to the network operation scenario, parse the extended constraint conditions, and determine the extended task items to be added;
[0037] A setting module, configured to sort all task items of the network operation scenario according to the task category, and set the input parameters of the task items at the same time;
[0038] An execution module, configured to execute all task items according to the task sorting.
[0039] Combined with the second aspect, in one implementation, each stage of the network operation full life cycle includes four task types, namely, sensing type, analysis type, decision type, and execution type. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.
[0040] Combined with the second aspect, in one implementation, the device further includes a management and control interface library, which is used to store all interfaces provided by the lower-level management and control systems or network elements that can be called by the task items; the task items call the associated interfaces as needed during the execution process.
[0041] The beneficial effects brought by the technical solution provided by the embodiments of the present application at least include:
[0042] Determine basic task items through the network operation scenario, determine the extended task items to be added by parsing the extended constraint conditions; sort and execute tasks according to the task category, associate the network operation scenario with the task items, and can form a closed loop automatically based on the network operation scenario, improving the automation level of network operation management based on the scenario.
[0043] Further provide an external interface for the network operation scenario, reduce the interface complexity, and improve the network operation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 It is a schematic flowchart of an embodiment of the network operation management method for scenarios of the present application;
[0045] Figure 2 It is a schematic flowchart of step S2 of the embodiment of the present application;
[0046] Figure 3 It is a schematic diagram when the extended constraint condition represents resource information in the embodiment of the present application;
[0047] Figure 4 It is a schematic diagram when the extended constraint condition represents index information in the embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0048] To enable those skilled in the art to better understand the solution of this application, the following will clearly and completely describe the technical solutions in the embodiments of this application in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this application.
[0049] In the description of the embodiments of this application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more than two.
[0050] In some processes described in the embodiments of this application, multiple operations or steps appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of this application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in order or in parallel, and these operations or steps may be combined.
[0051] To make the purpose, technical solutions and advantages of this application clearer, the following will further describe the embodiments of this application in detail in conjunction with the accompanying drawings.
[0052] In a first aspect, the embodiments of this application provide a scenario-oriented network operation management method, which can form a closed loop based on the network operation scenario and improve the automation level of scenario-based network operation management.
[0053] As Figure 1 shown, the flowchart of the first embodiment of the scenario-oriented network operation management method of this application. This network operation management method includes the following steps:
[0054] S1. Obtain the network operation scenario and initial constraint conditions.
[0055] S2. Divide the above initial constraint conditions into basic constraint conditions and extended constraint conditions.
[0056] S3. Determine the basic task items according to the above network operation scenario, analyze the extended constraint conditions, and determine the extended task items to be added.
[0057] S4. Sort all task items in the network operation scenario according to the task category, and set the input parameters of the task items at the same time.
[0058] S5. Execute all task items according to the task sorting.
[0059] Before step S1 or before step S1, the following is also included: Pre-establish a network operation scenario library and an operation task library. The network operation scenario library is used to store all sub-scenarios in the whole life cycle of network operation, which can be regarded as the set of all sub-scenarios in the whole life cycle of network operation. The information of each scenario includes but is not limited to: scenario number, scenario name, affiliated operation stage, minimum constraint set, basic task items, task selection strategy.
[0060] In some embodiments, the whole life cycle of network operation usually includes several stages such as network planning, network construction, network maintenance, network optimization and business operation.
[0061] The operation task library is used to store all operation tasks that should be executed in each stage of the whole life cycle of network operation, which can be regarded as the set of all operation tasks that should be executed in each stage of the whole life cycle of network operation. Each operation task can include one task item or multiple task items. The operation tasks that should be executed in each stage should cover the four processes of perception, analysis, decision-making and execution of intelligent operation, and these four processes are the four task types included in each stage. The information of each task item includes but is not limited to: task number, task name, applicable scenario, applicable scope, task type, associated subtasks, associated interfaces. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop. The above steps S1 to S5 are the processes for one task loop, and the processes of other task loops are the same as the above process.
[0062] As Figure 2 shown, in one embodiment, the specific implementation process of the above step S2 is:
[0063] S201. Determine whether the network operation scenario obtained in step S1 exists in the network operation scenario library. If so, enter S202; if not, enter S203.
[0064] S202. Obtain the minimum constraint set information corresponding to the network operation scenario, and enter S204.
[0065] S203. Return no corresponding scenario, and step S2 ends.
[0066] S204. Compare the initial constraint conditions with the obtained minimum constraint set information, and judge whether the initial constraint conditions of the network operation scenario meet the requirements of the minimum constraint set. If so, enter S205; if not, enter S206.
[0067] S205. Set the initial constraint conditions existing in the minimum constraint set as the basic constraint conditions, and set the other initial constraint conditions as the extended constraint conditions.
[0068] S206. Return that the scenario constraint requirements are not met.
[0069] As Figure 3 shown, an embodiment of the above step S3 is provided. First, determine the basic task items according to the network operation scenario, which can be obtained from the information corresponding to the network operation scenario in the network operation scenario library. Then parse the extended constraint conditions to determine the extended task items to be added, specifically including:
[0070] When the extended constraint condition represents resource information, first determine whether the resource type is network resource or service resource, then determine the corresponding task items corresponding to the resource type according to the applicable scope of the task items in the operation task library, and then combine the network operation scenario to determine the task items to be added for this resource type. For example, the applicable scope of the ISIS routing area planning task is the IP network and SPN, and the applicable network operation scenario is network planning. Then this task item is the task item corresponding to the IP or SPN network in the network planning scenario. Another example is that the applicable scope of the optical performance degradation analysis task is OTN and SPN, and the network operation scenario is monitoring and troubleshooting. Then this task item is the task item corresponding to OTN or SPN in the monitoring and troubleshooting scenario. Another example is that the applicable scope of the traffic prediction task is the VPN service, and the network operation scenario is quality analysis. Then this task item is the task item corresponding to the VPN service in the quality analysis scenario.
[0071] When the extended constraint condition represents index information, first determine the index type, and classify the index into single-value type, grade type, and composite type according to the index value data type and index characteristics. Among them, the single-value type represents the index type with a single numerical value or interval value; the grade type represents the index type with an enumeration value, and each enumeration value represents a different ability level or specification; the composite type is the index type reflecting the comprehensive ability requirements, such as reliability, availability, etc. The method for further processing according to the index type is:
[0072] For single-value type indexes, determine the corresponding task items of the available indexes. For example, it includes index perception, index analysis, index prediction, index verification, and index optimization. According to the network operation scenario, determine the corresponding task items to be added for the single-value type indexes from the operation task library.
[0073] For grade type indexes, there are no corresponding task items.
[0074] For composite type metrics, the task selection strategy based on network scenario information is decomposed into at least two other types of metrics, such as single-value type and / or rank type metrics, and then corresponding processing is performed according to the decomposed metric types.
[0075] The task items corresponding to the above method are the extended task items to be added, and no new extended task items need to be added for other extended constraint conditions.
[0076] In the above step S4, all task items of the network operation scenario are sorted according to the task category, specifically: First, determine the categories of all task items to be executed according to the task information in the network operation task library. Then, sort all task items to be executed in the order of perception type, analysis type, decision type, and execution type. For task items of the same type, the basic task items take precedence over the extended task items; and multiple basic task items or extended task items of the same type support concurrent execution; at the same time, duplicate task items are deleted.
[0077] While sorting all task items, set the input parameters of the task items, including:
[0078] Determine the data types to be perceived according to the network operation scenario (i.e., the data types that should be obtained through the perception task); where the data types include topology, connection, status, fault, performance, and log, etc. According to the basic constraint conditions in step S2 and the extended constraint conditions representing resource information, determine the resource objects of the network operation instance, specifically including network resources and / or service resources. According to the above resource objects and the data types to be perceived, determine the input parameter values of the basic task items of the perception type. For other types of task items, determine the input parameter values according to the initial constraint conditions and the data obtained by the task items of the perception type.
[0079] In some embodiments, in the above step S3, during the process of parsing the extended constraint conditions, the task loop control parameters are also determined. The task loop control parameters are the control conditions of the task loop, including but not limited to the control conditions for operations such as triggering, ending, or pausing the task loop. When the extended constraint conditions represent time information, set the control task loop time and corresponding actions. In the above step S5, trigger the corresponding task loop according to the task loop control parameters, and execute all task items according to the task item sorting within the task loop.
[0080] In some embodiments, based on the above-described scenario-oriented network operation and management method, before or during step S1, a control interface library is further established to store all the interfaces provided by the underlying control systems or network elements that can be called by task items. The information of each control interface includes, but is not limited to: interface number, interface name, interface type, input parameters, output parameters, and interface provider. The interface type is divided into two categories: standard interfaces and private interfaces. The associated interfaces in the task information of the network operation task library point to the interfaces in the control interface library. During the execution of S5, the task item can determine the specific information of the associated interface according to the control interface library and call the interface to complete the corresponding operation task.
[0081] Furthermore, based on the above-described embodiment of the scenario-oriented network operation and management method, an external interface for the network operation scenario is further provided. The external interface can be a human-machine interface input interface or a call interface between systems. The input information of the external interface includes the network operation scenario and initial constraint conditions, and the input form can be structured data or unstructured data. When unstructured data is used, specific technologies need to be further adopted to extract the information of the network operation scenario and initial constraint conditions. The constraint conditions input by the external interface together with the network operation scenario are all initial constraint conditions; there are also cases where multiple scenarios and all initial constraint conditions exist together during implementation, and in this case, the initial constraints of each scenario are the same. The external interface for the network operation scenario, combined with the unified automatic closed-loop processing ability, will simplify the complexity of the external interface of the current control system and improve the network operation efficiency.
[0082] On the other hand, an embodiment of a scenario-oriented network operation and management device is provided, which can be used to implement the above method. The device includes an acquisition module, a differentiation module, an extension module, a setting module, and an execution module.
[0083] The acquisition module is used to acquire the network operation scenario and the corresponding initial constraint conditions.
[0084] The differentiation module is used to divide the above initial constraint conditions into basic constraint conditions and extended constraint conditions.
[0085] The extension module is used to determine the basic task items according to the above network operation scenario, analyze the extended constraint conditions, and determine the extended task items to be added.
[0086] The setting module is used to sort all the task items of the network operation scenario according to the task category, and at the same time set the input parameters of the task items.
[0087] The execution module is used to execute all the task items according to the above task sorting.
[0088] Each stage of the above-mentioned full life cycle of network operation includes four types of tasks, namely, sensing tasks, analysis tasks, decision-making tasks, and execution tasks. Each operation scenario instance must be associated with at least one task item in each type of task to form a complete task loop.
[0089] The above-mentioned device further includes a control interface library for storing all interfaces provided by the underlying control system or network element that can be called by the task items; the task items call the associated interfaces as needed during the execution process.
[0090] The functional implementation of each module in the above-mentioned scenario-oriented network operation management device corresponds to each step in the above-mentioned embodiment of the scenario-oriented network operation management method. The remaining functions and implementation processes will not be elaborated here one by one.
[0091] The terms "including" and "having" and any variations thereof in the specification, claims, and drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally further include unlisted steps or units, or may optionally further include other steps or units inherent to these processes, methods, products, or devices.
[0092] In the description of the embodiments of this application, words such as "exemplary", "for example", or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary", "for example", or "for instance" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary", "for example", or "for instance" is intended to present relevant concepts in a specific manner.
[0093] It should be noted that the serial numbers of the above-mentioned embodiments of this application are only for description and do not represent the superiority or inferiority of the embodiments.
[0094] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium as described above (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal device to execute the methods described in various embodiments of this application.
[0095] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application accordingly. Any equivalent structural or equivalent process transformations made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, are similarly included in the patent protection scope of the present application.
Claims
1. A scenario-oriented network operation management method, characterized in that, it includes the steps of: S1. Obtain the network operation scenario and initial constraint conditions; S2. Divide the initial constraint conditions into basic constraint conditions and extended constraint conditions; S3. Determine the basic task items according to the network operation scenario, analyze the extended constraint conditions, and determine the extended task items to be added; S4. Sort all the task items of the network operation scenario according to the task category, and set the input parameters of the task items at the same time; S5. Execute all the task items according to the task sorting.
2. The scenario-oriented network operation management method according to claim 1, characterized in that, before or in step S1, it further includes: pre-establishing a network operation scenario library for storing all the sub-scenarios in the entire network operation life cycle; and establishing an operation task library for storing all the operation tasks that should be executed in each stage of the entire network operation life cycle, and each operation task includes at least one task item.
3. The scenario-oriented network operation management method according to claim 2, characterized in that: each stage of the entire network operation life cycle includes four task types, namely perception type, analysis type, decision type and execution type. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.
4. The scenario-oriented network operation management method according to claim 3, characterized in that, S2 includes: when the network operation scenario obtained in step S1 exists in the network operation scenario library, obtain the minimum constraint set information corresponding to the network operation scenario; set the initial constraint conditions existing in the minimum constraint set as the basic constraint conditions, and other initial constraint conditions as the extended constraint conditions.
5. The scenario-oriented network operation management method according to claim 4, characterized in that, in step S3, when analyzing the extended constraint conditions and determining the extended task items to be added, it includes: when the extended constraint conditions represent resource information, combine the network operation scenario and determine the task items corresponding to the resource type from the operation task library.
6. The scenario-oriented network operation management method according to claim 4, characterized in that, in step S3, when analyzing the extended constraint conditions and determining the extended task items to be added, it includes: when the extended constraint conditions represent index information, divide the index into single-value type, grade type and composite type according to the index value data type and index characteristics; for single-value type indexes, determine the corresponding task items of the available indexes, and determine the corresponding task items to be added for the single-value type indexes from the operation task library according to the network operation scenario; for grade type indexes, there are no corresponding task items; for composite type indexes, decompose them into at least two other types of indexes according to the task selection strategy of the network scenario information, and then perform corresponding processing according to the decomposed index types.
7. The scenario-oriented network operation management method according to claim 4, characterized in that, In step S3, the extended constraint conditions are parsed, and it is determined that the extended task items to be added include: when the extended constraint conditions represent time information, the time of the control task loop and the corresponding actions are set.
8. The scenario-oriented network operation management method according to claim 3, characterized in that: in step S3, the extended constraint conditions are parsed, and the task loop control parameters are also determined. The task loop control parameters are the control conditions of the task loop; in step S5, the corresponding task loop is controlled according to the task loop control parameters, and all task items are executed according to the task sorting within the task loop.
9. The scenario-oriented network operation management method according to claim 3, characterized in that, in step S4, the sorting of all task items in the network operation scenario according to the task category includes: sorting all task items to be executed in the order of the perception type, analysis type, decision type, and execution type; for task items of the same type, the basic task items take precedence over the extended task items; and multiple basic task items or extended task items of the same type support concurrent execution; at the same time, duplicate task items are deleted.
10. The scenario-oriented network operation management method according to claim 5, characterized in that, in step S4, the setting of the input parameters of the task items includes: determining the data types to be perceived according to the network operation scenario; determining the resource objects of the network operation instance according to the basic constraint conditions in step S2 and the extended constraint conditions representing resource information; determining the input parameter values of the perception-type basic tasks according to the resource objects and the data types to be perceived.
11. The scenario-oriented network operation management method according to any one of claims 1-10, characterized in that, before step S1 or in step S1, a management and control interface library is also established in advance to store all interfaces provided by the lower-level management and control systems or network elements that can be called by the task items; in step S5, the task items call the associated interfaces as needed during the execution process.
12. The scenario-oriented network operation management method according to any one of claims 1-10, characterized in that: an external interface for the network operation scenario is provided. The input information of the external interface includes the network operation scenario and the initial constraint conditions, and the input form is structured or unstructured data; when unstructured data is used, the information extraction of the network operation scenario and the initial constraint conditions is further performed.
13. A scenario-oriented network operation management device, characterized in that, comprising: an acquisition module for acquiring the network operation scenario and the initial constraint conditions; a differentiation module for dividing the initial constraint conditions into basic constraint conditions and extended constraint conditions; an extension module for determining basic task items according to the network operation scenario, parsing the extended constraint conditions, and determining the extended task items to be added; a setting module for sorting all task items in the network operation scenario according to the task category and setting the input parameters of the task items at the same time; an execution module for executing all task items according to the task sorting.
14. The scenario-oriented network operation management device according to claim 13, characterized in that: Each stage of the full life cycle of network operation includes four types of tasks, namely, perception tasks, analysis tasks, decision-making tasks, and execution tasks. Each operation scenario instance must be associated with at least one task item in each type of task to form a complete task loop.
15. The scenario-oriented network operation management device according to claim 14, characterized in that: the device further includes a control interface library for storing all interfaces provided by the underlying control systems or network elements that can be called by task items; the task items call the associated interfaces as needed during the execution process.