Scenario-oriented network operation management method and apparatus

Abstract

A scenario-oriented network operation management method and apparatus, relating to the field of telecommunication network management and control systems. The method comprises the following steps: S1, acquiring a network operation scenario and initial constraint conditions; S2, dividing the initial constraint conditions into a basic constraint condition and an extended constraint condition; S3, on the basis of the network operation scenario, determining a basic task item, analyzing the extended constraint condition, and determining an extended task item to be added; S4, sorting all task items of the network operation scenario on the basis of the task categories, and setting input parameters of the task items; and S5, executing all the task items on the basis of the task sequence. According to the present application, a closed loop can be automatically formed on the basis of a network operation scenario, and the automation level of scenario-oriented network operation management is improved.

Description

A scenario-oriented network operation management method and device Technical Field

[0001] The present application relates to the field of telecommunications network control and management systems, and specifically to a scenario-oriented network operation and management method and device. Background Art

[0002] Currently, each link in telecommunications network operations involves numerous operations and complex operating parameters. Generally, it is necessary to perform different query, creation, update and other operations in the management and control systems at all levels to complete an operation task, which is also very time-consuming. Therefore, in order to ensure network operations, high requirements are placed on operation and maintenance personnel. First of all, they need to have a comprehensive network operation knowledge system, and at the same time, they need to have an in-depth understanding of various operation operations and parameters of network management and control systems at all levels to effectively avoid operational errors.

[0003] Intelligent operations management is a major future trend. Network management and control systems must first achieve automated closed-loop processes to reduce the need for human intervention. Simultaneously, they must simplify input requirements for human-machine interfaces to truly achieve operators' goal of reducing labor costs. Network operations tasks are typically executed at a scenario-based granularity, and scenario-based network operations capabilities are a typical metric used in the industry to assess intelligence levels.

[0004] Existing solutions do not have the ability to automatically close the loop based on the granularity of network operation scenarios. At the same time, there are problems such as complex human-machine interfaces, cumbersome operation steps and parameters, and low operating efficiency in network management and control systems.

[0005] Summary of the Invention

[0006] The present application provides a scenario-oriented network operation management method and device, which can solve the technical problem that the existing technology cannot achieve automatic closed loop based on network operation scenarios.

[0007] In a first aspect, an embodiment of the present application provides a scenario-oriented network operation management method, comprising the steps of:

[0008] S1. Obtain network operation scenarios and initial constraints;

[0009] S2. The initial constraints are divided into basic constraints and extended constraints;

[0010] S3 determines the basic task items according to the network operation scenario, analyzes the expansion constraints, and determines the expansion task items that should be added;

[0011] S4 sort all task items of the network operation scenario according to the task category, and set the input parameters of the task item;

[0012] S5. Execute all task items according to the task sequence.

[0013] In combination with the first aspect, in one embodiment, step S1 or before step S1 also includes: pre-establishing a network operation scenario library to store all segmented scenarios in the entire life cycle of network operation; and establishing an operation task library to store all operation tasks that should be performed in each stage of the entire life cycle of network operation, each operation task including at least one task item.

[0014] In combination with the first aspect, in one embodiment, each stage of the network operation life cycle includes four task types, namely perception, analysis, decision-making and execution. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.

[0015] In combination with the first aspect, in one embodiment, S2 includes:

[0016] When the network operation scenario obtained in step S1 exists in the network operation scenario library, obtaining the minimum constraint set information corresponding to the network operation scenario;

[0017] The initial constraints existing in the minimum constraint set are set as basic constraints, and the other initial constraints are set as extended constraints.

[0018] In combination with the first aspect, in one embodiment, in step S3, parsing the extended constraint conditions and determining the extended task items to be added include: when the extended constraint conditions represent resource information, combining the network operation scenario, determining the task items corresponding to the resource type from the operation task library.

[0019] In conjunction with the first aspect, in one embodiment, in step S3, parsing the extended constraint condition and determining the extended task item to be added includes: when the extended constraint condition represents indicator information, classifying the indicator into a single value class, a hierarchical class, and a composite class according to the indicator value data type and the indicator characteristics;

[0020] For single-value indicators, determine the corresponding task items for the available indicators. Based on the network operation scenario, determine the corresponding task items that need to be added to the single-value indicators from the operation task library.

[0021] For grade-type indicators, there are no corresponding task items;

[0022] For composite indicators, they are decomposed into at least two other types of indicators based on the task selection strategy of network scenario information, and then processed accordingly according to the decomposed indicator types.

[0023] In combination with the first aspect, in one embodiment, in step S3, parsing the extended constraint condition and determining the extended task item to be added includes: when the extended constraint condition represents time information, setting the time and corresponding action of the control task loop.

[0024] In combination with the first aspect, in one embodiment, in step S3, the extended constraint condition is parsed and the task ring control parameter is determined, where the task ring control parameter is a control condition of the task ring;

[0025] In step S5, the corresponding task ring is controlled according to the task ring control parameters, and all task items are executed in the task ring according to the task sequence.

[0026] In conjunction with the first aspect, in one embodiment, sorting all task items of the network operation scenario according to task categories in step S4 includes:

[0027] All task items to be executed are sorted in the order of perception, analysis, decision and execution. For task items of the same type, basic task items take precedence over extended task items. Multiple basic task items or extended task items of the same type support concurrent execution. Duplicate task items are deleted at the same time.

[0028] In conjunction with the first aspect, in one embodiment, setting the input parameters of the task item in step S4 includes:

[0029] Determine the type of data that should be sensed based on network operation scenarios;

[0030] Determine the resource objects of the network operation instance according to the basic constraint conditions and the extended constraint conditions representing resource information described in step S2;

[0031] Determine the input parameter value of the perception-type basic task according to the resource object and the data type to be perceived.

[0032] In combination with the first aspect, in one embodiment, step S1 or before step S1 also includes pre-establishing a management and control interface library to store all interfaces provided by the lower-level management and control system or network element that can be called by the task item; in step S5, the task item calls the associated interface on demand during execution.

[0033] In combination with the first aspect, in one embodiment, an external interface for network operation scenarios is provided, and the input information of the external interface includes network operation scenarios and initial constraints, and the input form is structured or unstructured data; when unstructured data is used, information extraction of the network operation scenarios and initial constraints is further performed.

[0034] In a second aspect, an embodiment of the present application provides a scenario-oriented network operation management device, including:

[0035] An acquisition module is used to obtain network operation scenarios and initial constraints;

[0036] A distinguishing module, configured to divide the initial constraint conditions into basic constraint conditions and extended constraint conditions;

[0037] An extension module, configured to determine basic task items according to the network operation scenario, parse extension constraints, and determine extended task items to be added;

[0038] The setting module is used to sort all task items of the network operation scenario according to task categories and set input parameters of the task items;

[0039] An execution module is used to execute all task items according to the task sequence.

[0040] In combination with the second aspect, in one embodiment, each stage of the network operation life cycle includes four task types, namely perception, analysis, decision-making and execution. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.

[0041] In combination with the second aspect, in one embodiment, the device further includes a management and control interface library for storing all interfaces provided by the lower-level management and control system or network element that can be called by the task item; the task item calls the associated interface on demand during execution.

[0042] The beneficial effects of the technical solutions provided in the embodiments of the present application include at least:

[0043] Determine basic task items through network operation scenarios, and determine the extended task items that should be added by analyzing extension constraints; sort and execute tasks according to task categories, so that network operation scenarios and task items are associated. A closed loop can be formed based on the network operation scenarios, thereby improving the automation level of scenario-based network operation management.

[0044] Further provide external interfaces for network operation scenarios, reduce interface complexity and improve network operation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] FIG1 is a flow chart of an embodiment of a scenario-oriented network operation management method of the present application;

[0046] FIG2 is a schematic diagram of the process of step S2 of the embodiment of the present application;

[0047] FIG3 is a schematic diagram of an embodiment of the present application in which extended constraint conditions represent resource information;

[0048] FIG4 is a schematic diagram of the extended constraint condition representation indicator information in an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0050] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0051] In some processes described in the embodiments of the present application, multiple operations or steps are included that appear in a specific order. However, it should be understood that these operations or steps may not be performed in the order in which they appear in the embodiments of the present application or may be performed in parallel. The sequence numbers of the operations are only used to distinguish between different operations, and the sequence numbers themselves do not represent any order of execution. In addition, these processes may include more or fewer operations, and these operations or steps may be performed in sequence or in parallel, and these operations or steps may be combined.

[0052] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0053] On the first aspect, the embodiments of the present 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.

[0054] As shown in FIG1 , a flow chart of a first embodiment of a scenario-oriented network operation management method of the present application is provided. The network operation management method includes the following steps:

[0055] S1. Obtain network operation scenarios and initial constraints.

[0056] S2. Divide the above initial constraints into basic constraints and extended constraints.

[0057] S3. Determine basic task items based on the above network operation scenario, analyze expansion constraints, and determine the expansion task items that should be added.

[0058] S4. Sort all task items of the network operation scenario according to task categories, and set input parameters of the task items.

[0059] S5. Execute all task items according to the task sequence.

[0060] In or before step S1, the above step further includes: pre-establishing a network operation scenario library and an operation task library. The network operation scenario library is used to store all sub-scenarios throughout the network operation lifecycle and can be considered a collection of all sub-scenarios throughout the network operation lifecycle. Information for each scenario includes, but is not limited to, scenario number, scenario name, operation phase, minimum constraint set, basic task items, and task selection strategy.

[0061] In some embodiments, the entire network operation life cycle typically includes several stages: network planning, network construction, network maintenance, network optimization, and business operations.

[0062] The operation task library is used to store all the operation tasks that should be performed in each stage of the network operation life cycle. It can be regarded as a collection of all the operation tasks that should be performed in each stage of the network operation life cycle. Each operation task can include one task item or multiple task items. The operation tasks that should be performed in each stage should cover the four processes of perception, analysis, decision-making and execution of intelligent operations. 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, scope of application, task type, associated subtasks, and 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 process for one task loop, and the processes of other task loops are the same as the above process.

[0063] As shown in FIG2 , in one embodiment, the specific implementation process of step S2 is as follows:

[0064] S201. Determine whether the network operation scenario obtained in step S1 exists in the network operation scenario library. If yes, proceed to S202; if not, proceed to S203.

[0065] S202. Obtain the minimum constraint set information corresponding to the network operation scenario, and proceed to S204.

[0066] S203. Return to no corresponding scene, and step S2 ends.

[0067] S204. Compare the initial constraints with the obtained minimum constraint set information to determine whether the initial constraints of the network operation scenario meet the requirements of the minimum constraint set. If yes, proceed to S205; if not, proceed to S206.

[0068] S205. Set the initial constraint conditions existing in the minimum constraint set as basic constraint conditions, and set the other initial constraint conditions as extended constraint conditions.

[0069] S206. Return that the scene constraint requirement is not met.

[0070] As shown in Figure 3, an embodiment of the above step S3 is provided. First, the basic task items are determined according to the network operation scenario, which can be obtained from the information of the corresponding network operation scenario in the network operation scenario library. Then, the extended constraint conditions are analyzed to determine the extended task items that should be added, including:

[0071] When extending a constraint to represent resource information, first determine whether the resource type is a network resource or a service resource. Then, based on the applicable scope of the task items in the operation task library, determine the task items corresponding to the resource type. Finally, consider the network operation scenario to determine which task items should be added for this resource type. For example, the ISIS routing area planning task applies to IP networks and SPNs, and the applicable network operation scenario is network planning. Therefore, this task item corresponds to the IP or SPN network in the network planning scenario. For another example, the optical performance degradation analysis task applies to OTN and SPNs, and the network operation scenario is monitoring and troubleshooting. Therefore, this task item corresponds to the OTN or SPN in the monitoring and troubleshooting scenario. For another example, the traffic prediction task applies to VPN services, and the network operation scenario is quality analysis. Therefore, this task item corresponds to the VPN service in the quality analysis scenario.

[0072] When extending the constraint to represent indicator information, the indicator type is first determined. Based on the indicator value data type and indicator characteristics, the indicator is divided into single-value, hierarchical, and composite types. Single-value types represent indicator types with a single value or interval value; hierarchical types represent indicator types with enumerated values, each expressing a different capability level or specification; and composite types reflect comprehensive capability requirements, such as reliability and availability. Further processing methods based on indicator type are as follows:

[0073] For single-value indicators, determine the task items corresponding to the available indicators, for example, including indicator perception, indicator analysis, indicator prediction, indicator verification, and indicator optimization. According to the network operation scenario, determine the corresponding task items that need to be added for the single-value indicators from the operation task library.

[0074] For grade indicators, there are no corresponding task items.

[0075] For composite indicators, they are decomposed into at least two other types of indicators, such as single-value and / or hierarchical indicators, according to the task selection strategy of network scenario information, and then processed accordingly according to the decomposed indicator type.

[0076] The task items corresponding to the above method are the extended task items that should be added. There is no need to add new extended task items for other extended constraints.

[0077] In step S4, all task items in the network operation scenario are sorted by task category. Specifically, the categories of all pending task items are determined based on the task information in the network operation task library. Then, the pending task items are sorted in the order of perception, analysis, decision-making, and execution. For task items of the same type, basic task items take precedence over extended task items. Multiple basic task items or extended task items of the same type can be executed concurrently. Duplicate task items are deleted.

[0078] While sorting all task items, set the input parameters of the task items, including:

[0079] Determine the type of data to be perceived (i.e., the type of data to be obtained through the perception task) based on the network operation scenario; the data types include topology, connection, status, fault, performance, and log, etc. According to the basic constraints in step S2 and the extended constraints representing resource information, determine the resource objects of the network operation instance, specifically including network resources and / or business resources. Based on the above resource objects and the type of data to be perceived, determine the input parameter values ​​of the perception-type basic task items. For other types of task items, determine the input parameter values ​​based on the initial constraints and the data obtained from the perception-type task items.

[0080] In some embodiments, in step S3 above, during the process of parsing the extended constraint conditions, task ring control parameters are also determined. Task ring control parameters are control conditions for the task ring, including but not limited to control conditions for triggering, ending, or pausing the task ring. When the extended constraint conditions represent time information, the control task ring time and corresponding actions are set. In step S5 above, the corresponding task ring is triggered based on the task ring control parameters, and all task items within the task ring are executed according to the task item order.

[0081] In some embodiments, based on the above-mentioned scenario-oriented network operation management method, the above-mentioned step S1 or before step S1 also includes establishing a management and control interface library to store all interfaces provided by the lower-level management and control system or network element that can be called by the task item. The information of each management and control interface includes but is not limited to: interface number, interface name, interface type, input parameters, output parameters, interface provider, where the interface type is divided into two categories: standard interface and private interface. The associated interface in the task information of the network operation task library points to the interface in the management and control interface library. During the execution of S5, the task item can determine the specific information of the associated interface based on the management and control interface library, and call the interface to complete the corresponding operation task.

[0082] Furthermore, based on the above-mentioned scenario-oriented network operation management method embodiment, it also includes providing an external interface for network operation scenarios. 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 constraints. The input form can be structured data or unstructured data. When unstructured data is used, it is necessary to further adopt specific technologies to extract information about the network operation scenario and initial constraints. The constraints input by the external interface together with the network operation scenario are all initial constraints. During implementation, there are also multiple scenarios and all initial constraints together. In this case, the initial constraints of each scenario are the same. The external interface for network operation scenarios combined with a unified automatic closed-loop processing capability will simplify the complexity of the external interface of the current management and control system and improve network operation efficiency.

[0083] On the other hand, an embodiment of a scenario-oriented network operation management device is provided, which can be used to implement the above method. The device includes an acquisition module, a differentiation module, an expansion module, a setting module and an execution module.

[0084] The acquisition module is used to obtain the network operation scenario and the corresponding initial constraints.

[0085] The distinguishing module is used to divide the above initial constraints into basic constraints and extended constraints.

[0086] The extension module is used to determine the basic task items according to the above network operation scenarios, analyze the extension constraints, and determine the extended task items that should be added.

[0087] The setting module is used to sort all task items of the network operation scenario according to task categories and set input parameters of the task items.

[0088] The execution module is used to execute all task items according to the above task sequence.

[0089] Each stage of the above-mentioned network operation life cycle includes four task types: perception, analysis, decision-making and execution. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.

[0090] The above device also includes a management and control interface library, which is used to store all interfaces provided by the lower-level management and control system or network elements that can be called by the task item; the task item calls the associated interface as needed during execution.

[0091] The functional implementation of each module in the above-mentioned scenario-oriented network operation management device corresponds to the steps in the above-mentioned scenario-oriented network operation management method embodiment, and the remaining functions and implementation processes will not be repeated here one by one.

[0092] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the accompanying drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0093] In the description of the embodiments of this application, the words "exemplary," "for example," or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary," "for example," or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.

[0094] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0095] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for enabling a terminal device to execute the methods described in each embodiment of the present application.

[0096] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A scenario-oriented network operation management method, characterized in that: Includes steps: S1. Obtain network operation scenarios and initial constraints; S2. The initial constraints are divided into basic constraints and extended constraints; S3. Determine the basic task items according to the network operation scenario, analyze the expansion constraints, and determine the expansion task items that should be added; S4. Sort all task items of the network operation scenario according to the task category and set the input parameters of the task items; S5. Execute all task items according to the task sequence.

2. The scenario-oriented network operation management method according to claim 1, characterized in that: In or before step S1, the step also includes: pre-establishing a network operation scenario library to store all segmented scenarios in the entire life cycle of network operation; and establishing an operation task library to store all operation tasks that should be performed in each stage of the entire life cycle of network operation, 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 network operation life cycle includes four task types, namely perception, analysis, decision-making and execution. 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: The S2 includes: When the network operation scenario obtained in step S1 exists in the network operation scenario library, obtaining minimum constraint set information corresponding to the network operation scenario; Set the initial constraints existing in the minimum constraint set as the basic constraints. The initial constraints are set as extended constraints.

5. The scenario-oriented network operation management method according to claim 4, characterized in that: In the step S3, parsing the extended constraint condition and determining the extended task item to be added includes: when the extended constraint condition represents resource information, determining the task item corresponding to the resource type from the operation task library in combination with the network operation scenario.

6. The scenario-oriented network operation management method according to claim 4, characterized in that: In the step S3, parsing the extended constraint condition and determining the extended task item to be added includes: when the extended constraint condition represents indicator information, dividing the indicator into a single value class, a level class and a composite class according to the indicator value data type and the indicator characteristic; For single-value indicators, determine the task items corresponding to the available indicators, and determine the corresponding task items that need to be added for the single-value indicators from the operation task library according to the network operation scenario; For level indicators, there are no corresponding task items; For composite indicators, they are decomposed into at least two other types of indicators according to the task selection strategy of network scenario information, and then processed accordingly according to the decomposed indicator types.

7. The scenario-oriented network operation management method according to claim 4, characterized in that: In the step S3, parsing the extended constraint condition and determining the extended task item to be added includes: when the extended constraint condition represents time information, setting the time and corresponding action of the control task loop.

8. The scenario-oriented network operation management method according to claim 3, characterized in that: In the step S3, the extended constraint condition is parsed and the task ring control parameter is determined, where the task ring control parameter is the control condition of the task ring; In step S5, the corresponding task ring is controlled according to the task ring control parameter. All task items are executed according to the task sequence in the task ring.

9. The scenario-oriented network operation management method according to claim 3, characterized in that: The step S4 of sorting all the task items of the network operation scenario according to the task category includes: All task items to be executed are sorted in the order of perception, analysis, decision and execution. For task items of the same type, basic task items take precedence over extended task items. 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: The input parameters for setting the task item in step S4 include: Determine the type of data that should be sensed based on the network operation scenario; Determine the resource object of the network operation instance according to the basic constraint condition and the extended constraint condition representing the resource information in step S2; According to the resource object and the type of data to be sensed, the input parameter value of the perception-type basic task is determined.

11. The scenario-oriented network operation management method according to any one of claims 1 to 10, characterized in that: In or before step S1, the step further includes pre-establishing a management and control interface library to store all interfaces provided by the lower-level management and control system or network element that can be called by the task item; in step S5, the task item calls the associated interface as needed during execution.

12. The scenario-oriented network operation management method according to any one of claims 1 to 10, characterized in that: An external interface for network operation scenarios is provided, wherein input information of the external interface includes network operation scenarios and initial constraints, and the input form is structured or unstructured data; when unstructured data is used, information extraction of network operation scenarios and initial constraints is further performed.

13. A scenario-oriented network operation management device, characterized in that: include: An acquisition module is used to obtain network operation scenarios and initial constraints; A distinguishing module, used for dividing the initial constraint conditions into basic constraint conditions and extended constraint conditions; An extension module, used to determine basic task items according to the network operation scenario, parse extension constraints, and determine extended task items that should be added; A setting module is used to sort all task items of the network operation scenario according to task categories and set input parameters of the task items; An execution module is used to execute all task items according to the task sequence.

14. The scenario-oriented network operation management device according to claim 13, characterized in that: Each stage of the network operation life cycle includes four task types, namely perception, analysis, decision-making and execution. Each operation scenario instance must be associated with at least one task item in each task type to form a complete task loop.

15. The scenario-oriented network operation management device according to claim 14, characterized in that: The device also includes a management and control interface library, which is used to store all interfaces provided by the lower-level management and control system or network elements that can be called by the task item; the task item calls the associated interface as needed during the execution process.

Images