Task Execution Method, Apparatus and Electronic Device

Abstract

The present invention provides a task execution method, apparatus and electronic device, relating to the field of computer technology. The method includes: receiving first intent information input by a user; recognizing the first intent information, and determining a first workflow template corresponding to the first intent information from a plurality of preset workflow templates, wherein tasks are set in each preset workflow template; and executing the tasks in the first workflow template. In the embodiments of the present invention, by recognizing the first intent information input by the user, the workflow tasks corresponding to the first intent information can be automatically executed, and the degree of automation is relatively high.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular, to a task execution method, apparatus, and electronic device. Background Art

[0002] NFV (Network Function Virtualization) refers to a technology that uses virtualization technology to carry various software-based network functions through servers, memories, and switches to replace traditional proprietary hardware devices, such as routers, firewalls, content distribution networks, etc. The NFV architecture involves many components. Currently, the management of NFV, such as the testing of NFV, is performed manually, resulting in low efficiency. Summary of the Invention

[0003] Embodiments of the present invention provide a task execution method, apparatus, and electronic device to solve the problem that the existing management of NFV, such as the testing of NFV, is performed manually and has low efficiency.

[0004] To solve the above technical problem, the present invention is implemented as follows:

[0005] In a first aspect, an embodiment of the present invention provides a task execution method, the method including:

[0006] Receiving first intent information input by a user;

[0007] Identifying the first intent information, and determining a first workflow template corresponding to the first intent information from multiple preset workflow templates, where each preset workflow template is provided with tasks;

[0008] Executing the tasks in the first workflow template.

[0009] Optionally, the tasks in the first workflow template include second intent information;

[0010] The executing the tasks in the first workflow template includes:

[0011] Identifying the second intent information, and determining a set of test cases corresponding to the second intent information from a test case library;

[0012] Executing the test cases in the set of test cases.

[0013] Optionally, the tasks in the first workflow template include third intent information;

[0014] The executing the tasks in the first workflow template includes:

[0015] Identify the third intent information, and determine a second workflow template corresponding to the third intent information from multiple preset workflow templates;

[0016] Execute the tasks in the second workflow template.

[0017] Optionally, each preset workflow template in the multiple preset workflow templates is set with corresponding first intent description information. The identifying the first intent information and determining a first workflow template corresponding to the first intent information from multiple preset workflow templates includes:

[0018] Identify the first intent information;

[0019] Determine the preset workflow template corresponding to the first intent description information that matches the first intent information as the first workflow template corresponding to the first intent information.

[0020] Optionally, the first intent description information includes at least one of the following:

[0021] A first field for identifying a management object, a second field for identifying a management effect, and a third field for identifying a management operation.

[0022] Optionally, after determining the first workflow template corresponding to the first intent information from multiple preset workflow templates, the method further includes:

[0023] Determine the instantiation parameters required in the first workflow template;

[0024] Display a prompt message for prompting the user to input the instantiation parameters;

[0025] Receive the instantiation parameters input by the user;

[0026] The executing the tasks in the first workflow template includes:

[0027] Execute the tasks in the first workflow template based on the instantiation parameters input by the user.

[0028] In a second aspect, an embodiment of the present invention provides a task execution device, and the device includes:

[0029] A receiving module, configured to receive the first intent information input by the user;

[0030] A determining module, configured to identify the first intent information and determine a first workflow template corresponding to the first intent information from multiple preset workflow templates, where each preset workflow template is provided with tasks;

[0031] An executing module, configured to execute the tasks in the first workflow template.

[0032] Optionally, the tasks of the first workflow template include second intent information;

[0033] The execution module is specifically configured to:

[0034] Identify the second intent information, and determine a set of test cases corresponding to the second intent information in the test case library;

[0035] Execute the test cases in the set of test cases.

[0036] Optionally, the tasks of the first workflow template include third intent information;

[0037] The execution module is specifically configured to:

[0038] Identify the third intent information, and determine a second workflow template corresponding to the third intent information from multiple preset workflow templates;

[0039] Execute the tasks in the second workflow template.

[0040] Optionally, each of the multiple preset workflow templates is provided with corresponding first intent description information, and the determination module is specifically configured to:

[0041] Identify the first intent information;

[0042] Determine the preset workflow template corresponding to the first intent description information that matches the first intent information as the first workflow template corresponding to the first intent information.

[0043] Optionally, the first intent description information includes at least one of the following:

[0044] A first field for identifying a management object, a second field for identifying a management effect, and a third field for identifying a management operation.

[0045] Optionally, the determination module is further configured to:

[0046] Determine the instantiation parameters required in the first workflow template;

[0047] Display a prompt message for prompting the user to input the instantiation parameters;

[0048] Receive the instantiation parameters input by the user;

[0049] The execution module is specifically configured to:

[0050] Execute the tasks in the first workflow template based on the instantiation parameters input by the user.

[0051] In a third aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory, and a program stored on the memory and executable on the processor. When the program is executed by the processor, the steps of the task execution method described in the first aspect above are implemented.

[0052] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the task execution method described in the first aspect above are implemented.

[0053] In an embodiment of the present invention, first intention information input by a user is received; the first intention information is recognized, and a first workflow template corresponding to the first intention information is determined from a plurality of preset workflow templates, where each preset workflow template is provided with tasks; the tasks in the first workflow template are executed. In the embodiment of the present invention, by recognizing the first intention information input by the user, the workflow tasks corresponding to the first intention information can be automatically executed, and the degree of automation is relatively high. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for describing the embodiments of the present invention will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0055] Figure 1 is a flowchart of a task execution method provided by an embodiment of the present invention;

[0056] Figure 2 is a schematic structural diagram of an automatic test system provided by an embodiment of the present invention;

[0057] Figure 3 is a schematic structural diagram of an automatic test system provided by an embodiment of the present invention;

[0058] Figure 4 is a schematic structural diagram of an automatic test system provided by an embodiment of the present invention;

[0059] Figure 5 is a schematic diagram of a task flow of a workflow provided by an embodiment of the present invention;

[0060] Figure 6 is a schematic diagram of a task flow of a workflow provided by an embodiment of the present invention;

[0061] Figure 7It is the third schematic diagram of the task process of a workflow provided by an embodiment of the present invention;

[0062] Figure 8 It is the fourth schematic diagram of the task process of a workflow provided by an embodiment of the present invention;

[0063] Figure 9 It is the fifth schematic diagram of the task process of a workflow provided by an embodiment of the present invention;

[0064] Figure 10 It is the sixth schematic diagram of the task process of a workflow provided by an embodiment of the present invention;

[0065] Figure 11 It is the structural schematic diagram of a task execution device provided by an embodiment of the present invention;

[0066] Figure 12 It is the structural schematic diagram of an electronic device provided by an embodiment of the present invention. Detailed implementation manners

[0067] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0068] In the embodiments of the present invention, a task execution method, device and electronic device are proposed to solve the problem that the existing management of NFV is executed manually with low efficiency.

[0069] See Figure 1 , Figure 1 It is the flowchart of a task execution method provided by an embodiment of the present invention. As Figure 1 shown, the method includes the following steps:

[0070] Step 101, receive the first intent information input by the user.

[0071] Among them, the user may be a management executor, and the first intent information can be parsed into a management intent statement. An input box can be displayed on the display interface, so that the user can input the first intent information in the input box, and the input first intent information can be used to match a preset workflow template.

[0072] Step 102, identify the first intent information, and determine the first workflow template corresponding to the first intent information from multiple preset workflow templates. Each preset workflow template is provided with tasks.

[0073] Among them, the recognition of the first intent information may be to parse the first intent information one by one and convert the first intent information into a management intent statement. The natural language processing module may be called to recognize the first intent information and translate the first intent information into a formal management intent statement. Moreover, the first workflow template corresponding to the first intent information may be determined in the workflow intent knowledge base through a fuzzy matching module.

[0074] In addition, the multiple preset workflow templates may be stored in a workflow template library, and a UUID (Universally Unique Identifier) may be set for each preset workflow template in the workflow template library. In the workflow intent knowledge base, the relevant information of each preset workflow template may be recorded. By way of example, the relevant information of each preset workflow template may include an intent identification field. By way of example, the intent identification field may include a fourth field for identifying a management operation, a fifth field for identifying a management object, a sixth field for identifying a preset workflow template, and a seventh field for identifying other preset workflow templates on which the preset workflow template depends.

[0075] For example, in the workflow intent knowledge base, the relevant information of each preset workflow template may include <action> <object><ref ID> <deplist>, where action is used to identify the management operation, object is used to identify the management object, ref ID is used to identify the preset workflow template, and depList is used to identify other preset workflow templates on which the preset workflow template depends.

[0076] It should be noted that each preset workflow template in the workflow template library can be set with corresponding first intention description information, and the first intention description information may include: a first field for identifying the management object, a second field for identifying the management effect, and a third field for identifying the management operation. In the process of constructing the workflow intention knowledge base, the first intention description information of each preset workflow template in the workflow template library and the tasks in each preset workflow template can be parsed to create relevant information for each preset workflow template. The manifestation form of the first intention description information can be limited according to a preset format to standardize its description syntax and semantics, so as to be automatically read, parsed, and stored, facilitating the construction of the workflow intention knowledge base.

[0077] Exemplarily, in the process of constructing the workflow intention knowledge base, the third field in the first intention description information of each preset workflow template for identifying the management operation associated with the intention can be parsed, and the third field can be used as the fourth field in the workflow intention knowledge base for identifying the management operation; the first field in the first intention description information for identifying the management object can be parsed, and the first field can be used as the fifth field in the workflow intention knowledge base for identifying the management object; the UUID of the preset workflow template can be used as the sixth field for identifying the preset workflow template; the first intention description information included in the preset workflow template can be parsed, and the UUID of the preset workflow template corresponding to the first intention description information can be found and used as the seventh field for identifying other preset workflow templates on which the preset workflow template depends.

[0078] It should be noted that in the process of loading the record information corresponding to the new workflow template into the workflow intention knowledge base, if the UUID of the preset workflow template corresponding to the first intention description information cannot be found when parsing the first intention description information included in the preset workflow template, an error can be reported and exited, or the user can be reminded to create the preset workflow template corresponding to the first intention description information included in the task.

[0079] Step 103, execute the tasks in the first workflow template.

[0080] Among them, the tasks in the first workflow template may include multiple task steps that need to be executed. By executing the tasks in the first workflow template, the functions expected to be achieved by the first workflow template when designing the first workflow template can be realized.

[0081] It should be noted that before receiving the first intention information input by the user, a workflow template can be designed as a preset workflow template. During the workflow design process, an input interface for entering the first intention description information can be displayed, and the first intention description information input by the designer for the workflow template can be received, and the workflow template including the first intention description information can be stored in the workflow template library as a preset workflow template for matching during the workflow execution process. Further, syntax verification and semantic checking tools can be used to verify and check the first intention description information input by the designer, and prompt the designer to set the first intention description information corresponding to the workflow template in a preset format to complete the workflow design. For the newly added workflow template in the workflow template library, relevant information of the newly added workflow template can be created in the workflow intention knowledge base, so as to support retrieving and matching the workflow template by the intention identification field.

[0082] Further, during the workflow design process, during the process of the designer entering the first intention description information and compiling the execution steps of the tasks of the workflow template, etc., a service for finding, matching, and reusing confirmation of the preset workflow template based on the first intention information can be provided to the designer, so as to support the reuse of existing workflows in complex workflow design.

[0083] Exemplarily, the task execution method of this embodiment can be implemented through a management intention orchestration and capability open system, and the management intention orchestration and capability open system can be divided into a workflow design subsystem, a workflow execution subsystem, a test design subsystem, and a test execution subsystem. The workflow design subsystem is used to provide a graphical interaction interface for workflow designers to design workflow templates according to workflow specifications, convert the workflow templates containing workflow intention descriptions into formal description files that can be automatically processed by the system, and publish them to the workflow template library and workflow intention knowledge base that can be used by workflow executors. The workflow execution subsystem is used to be responsible for selecting a workflow template from the workflow template library for the workflow intention input by the workflow executor and triggering the workflow task execution process. The test design subsystem is used to provide a graphical network topology design interaction interface for test designers to design test cases according to test specifications, convert the test cases containing test intention descriptions and the corresponding test network descriptions into formal description files that can be automatically processed by the system, and publish them to the test case library and test intention knowledge base that can be used by test executors. The test execution subsystem is used to be responsible for selecting test cases from the test case library for the test intention input by the test executor and triggering the test task execution process.

[0084] It should be noted that, as Figure 2 As shown, for the workflow design subsystem, workflow intention parsing and intention association can be performed in the workflow design module; for the test design subsystem, test intention parsing and intention association can be performed in the test case design module.

[0085] In an embodiment of the present invention, the first intention information input by the user is received; the first intention information is recognized, and the first workflow template corresponding to the first intention information is determined from multiple preset workflow templates, where each preset workflow template is provided with tasks; the tasks in the first workflow template are executed. In the embodiment of the present invention, by recognizing the first intention information input by the user, the workflow tasks corresponding to the first intention information can be automatically executed, and the degree of automation is relatively high.

[0086] Optionally, the tasks in the first workflow template include second intention information;

[0087] The execution of the tasks in the first workflow template includes:

[0088] Recognize the second intention information, and determine the set of test cases corresponding to the second intention information in the test case library;

[0089] Execute the test cases in the set of test cases.

[0090] Among them, multiple test cases can be stored in the test case library. Each test case can be provided with corresponding second intention description information, and the corresponding relationship between each test case and the corresponding second intention description information can be recorded in the test intention knowledge base. The second intention description information can be information for describing the test case set by the test designer in a preset format during the test design stage. For example, it can include fields for identifying management operations, fields for identifying management objects, and fields for identifying management effects. The test cases corresponding to the second intention description information matching the second intention information can be used as the test cases in the set of test cases. The execution order of the test cases in the set of test cases can be optimized and scheduled, and the test cases in the set of test cases are executed according to the optimized and scheduled execution order, and the record of the test case execution situation can be updated correspondingly according to the execution result.

[0091] In addition, during the test design phase, the topology design module can convert the corresponding test network topology, including several systems under test, several test instruments, and their network connection relationships and specific configuration information, into a formal test topology description file based on the user's input on the graphical interface. Each test topology description file has a globally unique identifier UUID. The use case design module can convert the test script, input and output parameters of each test case into a formal test case description file based on the user's input, wherein each test case description file contains a reference to the test topology description file it depends on, as well as formal second intention description information, and may contain references to other test intentions in other fields such as preconditions, test steps and decision conditions. The test case library can encapsulate the test case description file, including the test topology description template, second intention description information, test script, test process file, etc., in a specified format. The test intention knowledge base can record the correspondence between each test case and the corresponding second intention description information.

[0092] It should be noted that if Figure 3 As shown, a unified intent management subsystem for management operations and complex tests can be designed. For the workflow design subsystem and the test design subsystem, the intent management subsystem can uniformly add intent descriptions for atomic workflows and atomic test cases to form atomic intents. Atomic workflows are workflows that do not contain other intent references and can be directly parsed and executed by the general workflow execution subsystem. Atomic test cases are test cases that do not contain other intent references and can be directly parsed and executed by the general test sub-execution system. For the test execution subsystem and the workflow execution subsystem, the intent management subsystem can uniformly complete the process of management operation intent parsing, instantiation, and layer-by-layer decomposition to atomic intent through the intent translation engine; it can also call the general test execution subsystem as the atomic test intent execution engine; it can also call the general workflow execution engine as the atomic workflow intent execution engine.

[0093] In this embodiment, by identifying the second intent information, determining the test case set corresponding to the second intent information in the test case library, and executing the test cases in the test case set, the test intent reference contained in the workflow description can be parsed, and the intention-based automatic test optimization system can be called to complete the execution of relevant steps.

[0094] Optionally, the task of the first workflow template includes third intent information;

[0095] The executing the task in the first workflow template includes:

[0096] Identifying the third intent information, and determining a second workflow template corresponding to the third intent information from a plurality of preset workflow templates;

[0097] Execute the tasks in the second workflow template.

[0098] Among them, the third intent information can be recognized, and the preset workflow template corresponding to the first intent description information that matches the third intent information is determined as the second workflow template corresponding to the third intent information.

[0099] It should be noted that in the workflow design state, a high-level business workflow design service that encapsulates and opens the underlying resource workflow call based on intent can be provided; adding an underlying resource workflow call based on intent during the design process of slice services, networks, or resource workflows; adding a consistency check on the intent and implementation of the underlying resource workflows they reference during the loading and verification process of third-party slice services, networks, or resources. In the workflow running state, a service that encapsulates and opens the workflow execution and result feedback based on intent can be provided; it can respond to service requests for business, slice, or subnet slice lifecycle management services based on intent, parse the corresponding management intent, query and determine the corresponding workflow template, extract and execute the corresponding workflow; the underlying resource workflow intent references included in the workflow description can be parsed by a general workflow engine and orchestration business logic, and a workflow execution system based on intent can be called to complete the execution of relevant steps.

[0100] In this embodiment, by nesting intent information in the task process of the workflow template, it is possible to encapsulate and open the underlying resource workflow service based on intent for the design and invocation of high-level service management operation workflows.

[0101] Optionally, each preset workflow template in the multiple preset workflow templates is provided with corresponding first intent description information. The recognition of the first intent information and the determination of the first workflow template corresponding to the first intent information in the multiple preset workflow templates include:

[0102] Recognize the first intent information;

[0103] The preset workflow template corresponding to the first intent description information that matches the first intent information is determined as the first workflow template corresponding to the first intent information.

[0104] Among them, the first intent description information that matches the first intent information can be that the first intent description information completely matches the first intent information, or it can be that the first intent description information is vaguely matched with the first intent information. For example, it can be that the first intent description information includes the first intent information, or it can be that the formalized management statement obtained by parsing the first intent information is a semantic equivalent field in the first intent description information.

[0105] In this embodiment, by matching the user intention with the first intention description information, the workflow required by the user can be quickly found.

[0106] Optionally, the first intention description information includes at least one of the following:

[0107] The first field for identifying the management object, the second field for identifying the management effect, and the third field for identifying the management operation.

[0108] Among them, the management object in the first intention description information may include: slice service template, slice template, subnet slice template, network service template, and network element resource template, etc. The management effect in the first intention description information may include two parts: operation target and effect index. The second field may include a first sub-field for identifying a single management operation target for a specific management object, and a second sub-field for identifying the value of the management effect index. The management operation in the first intention description information may include: Create, Initiate, Configure, Activate, Delete, Stop, Update, Deactivate, etc.

[0109] Exemplarily, the first intention description information may include <action> <object> <statement> ， <action>Can be an optional field that identifies the administrative operation associated with the intent and can be further extended. <object>Can be an optional field, identifying the managed object and can be further extended. <statement>Can be used as a mandatory field to identify the management effect, including two parts: the operation target and the effect index, and can include <objective> <expectation>Two subfields. <objective>It can be used as a mandatory field to identify the single management operation target for a specific management object, and a unique UUID can be correspondingly assigned. For example, it can include Assure, Optimize, Diagnose, etc. <expectation>It can be based on <action>The field values are different. As conditional optional fields, they can be used as instantiation parameters to identify the management effect index values. For example, if <action>If the value is Delete or Stop or Deactivate, then Expectation can be empty; if the value of Action is other operations, then Expectation can be an optional field. For example, if the value of Objective is Diagnosis, then the value of Expectation is of Bool type (Pass / Fail); if the value of Objective is Assurance, then the value of Expectation is a composite Metric type consisting of a numerical value (Value) and a unit (Unit).

[0110] In this embodiment, the first intent description information includes at least one of the following: a first field for identifying a management object, a second field for identifying a management effect, a third field for identifying a management operation, and an ability to standardize the first intent description information to facilitate workflow design.

[0111] Optionally, after determining the first workflow template corresponding to the first intent information among multiple preset workflow templates, the method further includes:

[0112] Determine the instantiation parameters required in the first workflow template;

[0113] Display a prompt message for prompting the user to input the instantiation parameters;

[0114] Receive the instantiation parameters input by the user;

[0115] Executing the tasks in the first workflow template includes:

[0116] Execute the tasks in the first workflow template based on the instantiation parameters input by the user.

[0117] Among them, after determining the first workflow template corresponding to the first intent information, the first intent description information of the first workflow template can be detected to determine the instantiation parameters required for executing the tasks in the first workflow template; further, the first intent description information included in the tasks of the first workflow template can be detected to determine the instantiation parameters required for executing the tasks in other workflow templates referenced by the first workflow template.

[0118] In this embodiment, by using the prompt message to prompt the user to input the instantiation parameters required in the first workflow template, it is possible to implement parsing the lower-layer resource workflow intent references included in the workflow description and invoking the intent-based workflow execution subsystem.

[0119] As a specific embodiment, such as Figure 4 As shown, for the slice service test requirements, the workflow design module can design test intentions based on the user experience guarantee requirements, and the intention parsing module can perform intention parsing. Workflow parsing and test intention recognition can be performed in the workflow execution module in the workflow execution subsystem, and the workflow execution module can call the task construction module in the test execution subsystem to execute test tasks.

[0120] In the prior art, network slice testing uses the combined subnet slice instance test process to implement end-to-end slice instance testing, and considers the situation of sharing subnet slice instances across slice instances to trigger relevant test tasks automatically. However, the testing implemented through the subnet slice manager cannot cover the network links across professional subnet domains within the operator network, and can only perform simple end-to-end metric verification testing, and cannot complete proactive testing in the operation and maintenance management process to assist in fine-grained problem location testing services; moreover, in the prior art, the use of test orchestration and its capability open is not considered to open test flexible orchestration and on-demand call services to content providers and industry users, and cannot provide open capabilities for end-to-end service testing outside the operator network. In this embodiment, the above task execution method can be applied to business processes such as template design, service deployment, and operation and maintenance management of end-to-end network slices, for realizing service quality guarantee, cross-domain fault diagnosis, and automatic experience optimization.

[0121] Taking the end-to-end slice service SLA guarantee as an example, as Figure 5 shown, the first intention description information corresponding to the service experience guarantee workflow can be: Assure<CST ID><SLA parameter>. The task process of the service experience guarantee workflow can include the following processes: measuring the slice service SLA metrics; judging whether they meet the SLA; if not, then performing slice service update; if so, then exiting normally. As Figure 6 shown, the first intention description information corresponding to the slice service update workflow can be: Update<CSI ID><parameter x>. The task process of the slice service update workflow can include the following processes: decomposing service metric X into a slice metric set Y; sequentially and cyclically measuring the slice metric y in the slice metric set Y; judging whether it meets the slice metric y; if so, then continuing to measure the next metric; if not, then calling the NSI slice instance update.

[0122] Taking the end-to-end slice instance fault demarcation as an example, a fault demarcation workflow can be added in the workflow design state, and the test intention for resource performance such as subnet slices and connection points can be called sequentially according to the slice template topology. As Figure 7 As shown, the first intent description information corresponding to the fault demarcation workflow can be: Diagnose<NST ID><parameter>. The task process of the fault demarcation workflow can include the following processes: decomposing the subnet slice function parameters; cyclically measuring the function index n of sub-slice n; determining whether it meets index n; if not, performing sub-slice fault demarcation. The fault demarcation workflow can be parsed and executed in the workflow running state, and according to the slice instance topology, the performance test intents of the subnet slice instance or the connection point instance can be called in sequence. As Figure 8 As shown, the task process of the sub-slice fault demarcation workflow can include the following processes: decomposing the network element resource function parameters; cyclically measuring the function index y of network element resource y; determining whether it meets index y; if so, continuing to measure the next index; if not, returning the faulty resource.

[0123] Taking the end-to-end slice service experience optimization as an example, an experience optimization workflow can be added in the workflow design state, and according to the slice template topology, the performance test intents for resources such as subnet slices and connection points can be called in sequence. As Figure 9 As shown, the first intent description information corresponding to the experience optimization workflow can be: Optimize<CST ID><parameter>. The task process of the experience optimization workflow can include the following processes: measuring the slice service experience index; if it meets the index, exiting normally; if not, performing slice performance diagnosis and updating the slice configuration. The experience optimization workflow can be parsed and executed in the workflow running state, and according to the slice instance topology, the performance test intents of the subnet slice instance or the connection point instance can be called in sequence. As Figure 10 As shown, the task process of the slice performance diagnosis workflow can include the following processes: decomposing the subnet slice performance parameters;; cyclically measuring the performance index y of sub-slice y; determining whether it meets index y; if so, continuing to measure the next index; if not, returning the subnet slice y that needs to be updated.

[0124] See Figure 11 , Figure 11 is a schematic structural diagram of a task execution device provided by an embodiment of the present invention. As Figure 11 As shown, the task execution device 200 includes:

[0125] A receiving module 201, configured to receive the first intent information input by the user;

[0126] A determining module 202, configured to identify the first intent information and determine a first workflow template corresponding to the first intent information from multiple preset workflow templates, where each preset workflow template is provided with tasks;

[0127] An execution module 203, configured to execute the tasks in the first workflow template.

[0128] Optionally, the tasks of the first workflow template include second intent information;

[0129] The execution module 203 is specifically configured to:

[0130] Identify the second intent information, and determine a set of test cases corresponding to the second intent information in the test case library;

[0131] Execute the test cases in the set of test cases.

[0132] Optionally, the tasks of the first workflow template include third intent information;

[0133] The execution module 203 is specifically configured to:

[0134] Identify the third intent information, and determine a second workflow template corresponding to the third intent information from multiple preset workflow templates;

[0135] Execute the tasks in the second workflow template.

[0136] Optionally, each of the multiple preset workflow templates is provided with corresponding first intent description information, and the determination module 202 is specifically configured to:

[0137] Identify the first intent information;

[0138] Determine the preset workflow template corresponding to the first intent description information that matches the first intent information as the first workflow template corresponding to the first intent information.

[0139] Optionally, the first intent description information includes at least one of the following:

[0140] A first field for identifying a management object, a second field for identifying a management effect, and a third field for identifying a management operation.

[0141] Optionally, the determination module 202 is further configured to:

[0142] Determine the instantiation parameters required in the first workflow template;

[0143] Display a prompt message for prompting the user to input the instantiation parameters;

[0144] Receive the instantiation parameters input by the user;

[0145] The execution module 203 is specifically configured to:

[0146] Execute the tasks in the first workflow template based on the instantiation parameters input by the user.

[0147] The task execution device can implement Figure 1 each process implemented in the method embodiments shown. To avoid repetition, they will not be described here again.

[0148] See Figure 12 , Figure 12 which is a schematic structural diagram of an electronic device provided by an embodiment of the present invention. As Figure 12 shown, the electronic device 300 further includes: a memory 302, a processor 301, and a program stored on the memory 302 and executable on the processor 301, where:

[0149] The processor 301 reads the program in the memory 302 and is used to execute:

[0150] Receive the first intent information input by the user;

[0151] Identify the first intent information, and determine a first workflow template corresponding to the first intent information from multiple preset workflow templates, where each preset workflow template is provided with tasks;

[0152] Execute the tasks in the first workflow template.

[0153] Optionally, the tasks in the first workflow template include second intent information;

[0154] The processor 301 executes the task of executing the tasks in the first workflow template, including:

[0155] Identify the second intent information, and determine a set of test cases corresponding to the second intent information from the test case library;

[0156] Execute the test cases in the set of test cases.

[0157] Optionally, the tasks in the first workflow template include third intent information;

[0158] The processor 301 executes the task of executing the tasks in the first workflow template, including:

[0159] Identify the third intent information, and determine a second workflow template corresponding to the third intent information from multiple preset workflow templates;

[0160] Execute the tasks in the second workflow template.

[0161] Optionally, each preset workflow template in the multiple preset workflow templates is provided with corresponding first intent description information. The processor 301 executes the identification of the first intent information and determines the first workflow template corresponding to the first intent information from the multiple preset workflow templates, including:

[0162] Identify the first intention information;

[0163] Determine the preset workflow template corresponding to the first intention description information that matches the first intention information as the first workflow template corresponding to the first intention information.

[0164] Optionally, the first intention description information includes at least one of the following:

[0165] The first field for identifying the management object, the second field for identifying the management effect, and the third field for identifying the management operation.

[0166] Optionally, the processor 301 is further configured to execute:

[0167] Determine the instantiation parameters required in the first workflow template;

[0168] Display a prompt message for prompting the user to input the instantiation parameters;

[0169] Receive the instantiation parameters input by the user;

[0170] The execution of the tasks in the first workflow template includes:

[0171] Execute the tasks in the first workflow template based on the instantiation parameters input by the user.

[0172] In Figure 12 The bus architecture may include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors represented by the processor 301 and the memory represented by the memory 302 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, so they will not be further described herein. The bus interface provides an interface.

[0173] The processor 301 is responsible for managing the bus architecture and general processing, and the memory 302 can store the data used by the processor 301 when executing operations.

[0174] It should be noted that any implementation manner in the method embodiment of the present invention can be implemented by the above-mentioned electronic device in this embodiment, and the same beneficial effects can be achieved, which will not be elaborated herein.

[0175] An embodiment of the present invention also provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, it implements each process of the above-described method for task execution, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here. Among them, the computer-readable storage medium is, for example, ROM, RAM, magnetic disk or optical disc, etc.

[0176] It should be noted that in this article, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such a process, method, article or device. Without more limitations, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article or device including that element.

[0177] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described method of the embodiment can be implemented by means of software plus a 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 such an understanding, the technical solution of the present invention, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc), and includes several instructions for causing a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present invention.

[0178] The embodiments of the present invention have been described above in conjunction with the accompanying drawings. However, the present invention is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present invention, those of ordinary skill in the art can also make many forms without departing from the purpose of the present invention and the scope protected by the claims, and all of them belong to the protection scope of the present invention.< / action> < / action> < / expectation> < / objective> < / expectation> < / objective> < / statement> < / object> < / action> < / statement> < / object> < / action> < / deplist> < / object> < / action>

Claims

1. A task execution method, characterized in that: The method comprises: receiving first intention information input by a user; Identifying the first intent information, and determining a first workflow template corresponding to the first intent information from a plurality of preset workflow templates, wherein each preset workflow template is provided with a task; Execute the tasks in the first workflow template; The task of the first workflow template includes second intent information; The executing the task in the first workflow template includes: Identify the second intent information, and determine a test case set corresponding to the second intent information in a test case library, where the test case library includes a plurality of test cases, each of the plurality of test cases is provided with corresponding second intent description information, and the test cases in the test case set are test cases corresponding to the second intent description information that matches the second intent information; Executing the test cases in the test case set; After determining the first workflow template corresponding to the first intent information from a plurality of preset workflow templates, the method further includes: Determining the instantiation parameters required in the first workflow template; Display prompt information, wherein the prompt information is used to prompt the user to input the instantiation parameters; Receive instantiation parameters input by the user; The executing the task in the first workflow template includes: Executing the tasks in the first workflow template based on the instantiation parameters input by the user; The determining of the instantiation parameters required in the first workflow template includes: Detecting first intention description information of the first workflow template, and determining instantiation parameters required to execute tasks in the first workflow template; The first intention description information included in the task of the first workflow template is detected, and the instantiation parameters required for executing the tasks in other workflow templates referenced by the first workflow template are determined.

2. The method according to claim 1, characterized in that The task of the first workflow template includes third intent information; The executing the task in the first workflow template includes: Identifying the third intent information, and determining a second workflow template corresponding to the third intent information from a plurality of preset workflow templates; Execute the tasks in the second workflow template.

3. The method according to claim 1, characterized in that Each of the plurality of preset workflow templates is provided with corresponding first intent description information, and the identifying the first intent information and determining a first workflow template corresponding to the first intent information from the plurality of preset workflow templates includes: identifying the first intent information; The preset workflow template corresponding to the first intent description information matching the first intent information is determined as the first workflow template corresponding to the first intent information.

4. The method according to claim 3, characterized in that The first intention description information includes at least one of the following: The first field is used to identify the management object, the second field is used to identify the management effect, and the third field is used to identify the management operation.

5. A task execution device, characterized in that: The device comprises: A receiving module, configured to receive first intention information input by a user; a determination module, configured to identify the first intent information and determine a first workflow template corresponding to the first intent information from a plurality of preset workflow templates, wherein each preset workflow template is provided with a task; An execution module, configured to execute tasks in the first workflow template; The task of the first workflow template includes second intent information; The execution module is specifically used for: Identify the second intent information, and determine a test case set corresponding to the second intent information in a test case library, where the test case library includes a plurality of test cases, each of the plurality of test cases is provided with corresponding second intent description information, and the test cases in the test case set are test cases corresponding to the second intent description information that matches the second intent information; Executing the test cases in the test case set; The determining module is further configured to: Determining the instantiation parameters required in the first workflow template; Display prompt information, wherein the prompt information is used to prompt the user to input the instantiation parameters; Receive instantiation parameters input by the user; The execution module is specifically used for: Executing the tasks in the first workflow template based on the instantiation parameters input by the user; The determining of the instantiation parameters required in the first workflow template includes: Detecting first intention description information of the first workflow template, and determining instantiation parameters required to execute tasks in the first workflow template; The first intention description information included in the task of the first workflow template is detected, and the instantiation parameters required for executing the tasks in other workflow templates referenced by the first workflow template are determined.

6. The device according to claim 5, characterized in that The task of the first workflow template includes third intent information; The execution module is specifically used for: Identifying the third intent information, and determining a second workflow template corresponding to the third intent information from a plurality of preset workflow templates; Execute the tasks in the second workflow template.

7. The device according to claim 5, characterized in that Each of the plurality of preset workflow templates is provided with corresponding first intention description information, and the determining module is specifically configured to: identifying the first intent information; The preset workflow template corresponding to the first intent description information matching the first intent information is determined as the first workflow template corresponding to the first intent information.

8. The device according to claim 7, characterized in that The first intention description information includes at least one of the following: The first field is used to identify the management object, the second field is used to identify the management effect, and the third field is used to identify the management operation.

9. An electronic device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the task execution method according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the task execution method according to any one of claims 1 to 4.

Images