Intention-driven system automation operation method, device, equipment and medium

Abstract

The present application belongs to the technical field of automation operation and maintenance, and is suitable for the financial field and the medical field, and discloses a system automation operation and maintenance method, device, equipment and medium based on intention driving, the method comprising: generating a corresponding approval request according to a management intention request, and sending the generated approval request to an external approval system; asynchronously polling the approval state of the approval process instance bound with the management intention in the external approval system; when the approval state of the management intention changes to a target state, driving the management intention into an intention analysis node through a process engine, and calling a rule engine through the intention analysis node; the rule engine makes a decision according to the attribute information and real-time operation and maintenance indicators of the management intention, generates at least one execution intention corresponding to a system operation and maintenance object, and drives the execution intention through the process engine to execute operation and maintenance operation logic on the system operation and maintenance object. The present application realizes automatic operation and maintenance from the user proposing an operation and maintenance target to the machine automatically executing.

Description

Technical Field

[0001] This invention belongs to the field of automated operation and maintenance technology and is applicable to the financial and medical fields. In particular, it relates to an intention-driven system automated operation and maintenance method, device, equipment and medium. Background Technology

[0002] Site reliability engineering and automated operation and maintenance are core means to ensure the stable and reliable operation of large-scale information systems. In scenarios with high requirements for system continuity, such as finance and healthcare, the accuracy of communication of operation and maintenance intentions, the compliance of approval and execution, and the controllability of the entire process are not only related to the continuity of business services, but also affect the safety of user assets and health.

[0003] Currently, most mainstream automated operations and maintenance (O&M) systems adopt a task- or script-centric driving model. However, as the architectures of critical infrastructures such as financial transaction systems and medical information platforms become increasingly complex, the limitations of this model are becoming increasingly apparent. First, existing systems heavily rely on pre-set execution scripts, lacking a unified abstract expression of O&M objectives. For example, scripts ensuring transaction success rates in financial payment systems may involve multiple steps such as database expansion and rate limiting adjustments, making it difficult for subsequent maintenance personnel to quickly understand the overall O&M intent. Similarly, in medical imaging systems, operations ensuring image retrieval response speed are scattered across multiple independent scripts, lacking a unified expression of intent. Second, approval systems and automated execution systems operate independently; even after approval, manual triggering is still required, resulting in a broken operational chain. Third, process engines and rule engines run independently, lacking an effective collaboration mechanism. When dynamic adjustments are needed based on real-time service level indicators and error budget consumption, this separated architecture struggles to support context-based dynamic decision-making.

[0004] Therefore, how to achieve automated operation and maintenance from the user's proposed operation and maintenance goals to the machine's automatic execution is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] This invention provides an intention-driven system automation operation and maintenance method, apparatus, equipment, and medium to solve the technical problem of how to achieve automated operation and maintenance from user-proposed operation and maintenance goals to automatic machine execution.

[0006] In a first aspect, the present invention provides an intent-driven system automated operation and maintenance method, comprising: Obtain the user's input management intent request, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; Asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent; When the approval status of the management intent changes to the target status, the management intent is driven into the intent parsing node through the process engine, and the rule engine is called through the intent parsing node. The rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic. The process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object.

[0007] Secondly, the present invention provides an intent-driven system automated operation and maintenance device, comprising: The acquisition module is used to acquire the management intent request input by the user, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; The update module is used to asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent. The calling module is used to drive the management intent into the intent parsing node through the process engine when the approval status of the management intent changes to the target status, and to call the rule engine through the intent parsing node; The generation module, wherein the rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic; The execution module is used to drive the execution intent through the process engine and execute the operation and maintenance logic on the system operation and maintenance object.

[0008] Thirdly, the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described intention-driven system automated operation and maintenance method.

[0009] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described intention-driven system automated operation and maintenance method.

[0010] The aforementioned intent-driven system automation operation and maintenance method, device, equipment, and medium, in their implemented scheme, can obtain management intent requests input by users through a client, generate corresponding approval requests based on the management intent requests, and send the generated approval requests to an external approval system; asynchronously poll the approval status of the approval process instances bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent; when the approval status of the management intent changes to the target status, the process engine drives the management intent to enter the intent parsing node, and the intent parsing node calls the rule engine; the rule engine makes decisions based on the attribute information and real-time operation and maintenance indicators of the management intent, generating at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic; the process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object. In this invention, after the management intent is approved, the process engine automatically drives it to the intent parsing node and triggers the rule engine, realizing the association between process orchestration and rule decision-making. The rules engine combines the operational goals set by management intent with real-time system operational metrics to make dynamic decisions, assess the difference between the current state and the target state, and automatically generate execution intents containing specific operational logic. This achieves automated operations and maintenance from the user's submission of operational goals to automatic machine execution. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a schematic diagram of an application environment for an intent-driven system automated operation and maintenance method according to an embodiment of the present invention.

[0013] Figure 2 This is a flowchart illustrating an intent-driven system automation operation and maintenance method according to an embodiment of the present invention.

[0014] Figure 3 yes Figure 2 A schematic diagram of a specific implementation method for step S10.

[0015] Figure 4 yes Figure 2 A schematic diagram of a specific implementation method for step S20.

[0016] Figure 5 yes Figure 2A flowchart illustrating a specific implementation of step S40.

[0017] Figure 6 yes Figure 2 A schematic diagram of a specific implementation method for step S50.

[0018] Figure 7 This is a schematic diagram of a system automated operation and maintenance device based on intent-driven operation in one embodiment of the present invention.

[0019] Figure 8 This is a schematic diagram of the structure of a computer device according to an embodiment of the present invention.

[0020] Figure 9 This is another structural schematic diagram of a computer device according to one embodiment of the present invention. Detailed Implementation

[0021] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0022] The intent-driven system automation operation and maintenance method provided in this invention can be applied to, for example... Figure 1 In the application environment, Figure 1This is a schematic diagram of an application environment for an intent-driven system automation operation and maintenance method according to an embodiment of the present invention. The client communicates with the server via a network. The server can obtain management intent requests input by the user through the client, generate corresponding approval requests based on the management intent requests, and send the generated approval requests to an external approval system. It asynchronously polls the approval status of the approval process instances bound to the management intent in the external approval system and synchronously updates the approval status to match the management intent's approval status. When the approval status of the management intent changes to the target status, the process engine drives the management intent to enter the intent parsing node, and the intent parsing node calls the rule engine. The rule engine makes decisions based on the attribute information and real-time operation and maintenance indicators of the management intent, generating at least one execution intent corresponding to the system operation and maintenance object. The execution intent contains machine-executable operation and maintenance logic. The process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object. In this invention, after the management intent is approved, the process engine automatically drives it to the intent parsing node and triggers the rule engine, realizing the association between process orchestration and rule decision-making. The rule engine combines the operational goals set by management intent with real-time system operational metrics to make dynamic decisions, determine the difference between the current state and the target state, and automatically generate execution intents containing specific operational logic. This achieves automated operation and maintenance from the user's proposed operational goals to automatic machine execution. The invention will be described in detail below through specific embodiments.

[0023] Please see Figure 2 As shown, Figure 2 This is a flowchart illustrating a system automation operation and maintenance method based on intent-driven principles provided in an embodiment of the present invention. The system automation operation and maintenance method based on intent-driven principles specifically includes the following steps S10 to S50: S10: Obtain the management intent request input by the user, generate a corresponding approval request based on the management intent request, and send the generated approval request to the external approval system.

[0024] Specifically, in this embodiment of the invention, the user submits a management intent request to the operation and maintenance management platform through an interactive terminal or system interface. This management intent request represents the operation and maintenance goal the user hopes to achieve, rather than specific operational steps. For example, when it is necessary to create a management intent, the user submits a management intent request to the intent interface module through the interactive terminal. After receiving the management intent request, the intent interface module generates a corresponding approval request based on the request and calls the external approval system interface to initiate the approval process. After the external approval system generates an approval process instance, it returns confirmation information. The intent interface module writes the management intent data to its local database and simultaneously returns a successful creation result to the user.

[0025] For example, in a financial scenario, the management intent request submitted by the operations and maintenance personnel is to maintain the transaction success rate of the payment service above a preset threshold; in a medical scenario, the management intent request submitted by the hospital information system operations and maintenance personnel is to ensure that the response time for image retrieval in the image archiving and communication system does not exceed a preset time limit. After receiving the management intent request, the operations and maintenance management platform generates a corresponding approval request based on the request and sends the generated approval request to an external approval system to initiate a compliance approval process.

[0026] In this embodiment of the invention, users only need to declare their operational goals, without needing to write specific operation scripts; the system automatically converts management intentions into approval requests, effectively linking the submission of operational goals with the compliance approval process. Specifically, as follows... Figure 3 The above, Figure 3 yes Figure 2 A flowchart illustrating a specific implementation of step S10. Specifically, it includes the following steps S11-S13: S11: Obtain the management intent request input by the user, extract the operation and maintenance domain attribute from the management intent request, and determine the preset operation and maintenance domain to which the operation and maintenance domain attribute belongs.

[0027] Specifically, in this embodiment of the invention, the operation and maintenance management platform obtains a management intent request submitted by a user through an interactive terminal or system interface. The management intent request carries an operation and maintenance domain attribute, which is selected by the user from a preset list of multiple operation and maintenance domains when submitting the request. These preset multiple operation and maintenance domains include, but are not limited to, cloud product domains, architecture domains, office automation domains, data center domains, wide area network domains, and network operation center domains. The operation and maintenance management platform extracts the operation and maintenance domain attribute from the management intent request and matches it with the preset list of operation and maintenance domains to determine the preset operation and maintenance domain to which the attribute belongs.

[0028] For example, in a financial scenario, a management intent request submitted by operations and maintenance personnel to ensure the availability of payment services carries an operations and maintenance domain attribute from the cloud product domain. After extracting this attribute, the system determines that it belongs to a preset cloud product domain. In a medical scenario, a management intent request submitted by operations and maintenance personnel to ensure the stable operation of image archiving and communication systems carries an operations and maintenance domain attribute from the data center domain; similarly, the system extracts and determines that it belongs to a preset data center domain.

[0029] S12: Generate an approval request corresponding to the management intent request based on the management intent request and the determined preset operation and maintenance domain.

[0030] Specifically, in this embodiment of the invention, the operation and maintenance management platform generates an approval request corresponding to the predetermined preset operation and maintenance domain, combined with the operation and maintenance objectives, associated systems, and other attribute information in the management intent request. Different preset operation and maintenance domains correspond to different approval process templates. For example, the cloud product domain may correspond to a process template that requires approval from both the cloud platform administrator and the business manager, while the data center domain may correspond to a process template that requires approval from both the data center operation and maintenance supervisor and the infrastructure manager.

[0031] For example, in a financial scenario, payment services fall under the cloud product domain. The system generates an approval request that requires approval from both the cloud platform administrator and the financial business manager, based on the corresponding approval process template for that domain. In a medical scenario, image archiving and communication systems fall under the data center domain. The system generates an approval request that requires approval from both the data center operations manager and the head of the medical information department, based on the corresponding approval process template for that domain.

[0032] This invention generates corresponding approval requests based on management intent requests and their respective preset operation and maintenance domains, enabling the approval process to be customized according to domain differences. Operation and maintenance operations in different domains follow their respective management norms and compliance requirements, thereby improving the relevance and compliance of the approval process.

[0033] S13: Add the operation and maintenance domain attribute to the approval request, and send the approval request with the added operation and maintenance domain attribute to the external approval system.

[0034] Specifically, in this embodiment of the invention, the operation and maintenance management platform adds the operation and maintenance domain attribute to the generated approval request, making the approval request carry domain identification information. Subsequently, the approval request with the added operation and maintenance domain attribute is sent to an external approval system. Upon receiving the approval request, the external approval system can match the corresponding approval rules based on the operation and maintenance domain attribute to achieve differentiated approval processing by domain.

[0035] For example, in a financial scenario, the system sends approval requests with cloud product domain attributes to an external approval system. The external approval system then matches the cloud product domain's approval chain for processing and approval. This invention, by sending operation and maintenance domain attributes along with the approval request to the external approval system, enables the external approval system to execute differentiated approval processes based on domain, achieving collaborative linkage between this system and the external approval system in the domain management dimension.

[0036] S20: Asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent.

[0037] Specifically, in this embodiment of the invention, the operation and maintenance management platform continuously tracks the approval status of approval process instances bound to the management intent in the external approval system through an asynchronous task mechanism. For example, when a management intent needs to be updated, the user initiates an update request for an existing management intent through the intent interface module. The update content includes key attributes such as intent description, execution flowchart, or planned execution time. After determining that the update involves key attributes, the intent interface module calls the external approval system interface to generate a new approval report and writes the updated intent data into the database. The asynchronous task synchronization module continuously polls the approval status of the external approval system and, after obtaining the approval result, calls the intent interface module to synchronously update the approval status of the management intent. When a management intent needs to be revoked, the user initiates a revocation request for the management intent through the intent interface module. The intent interface module checks the current approval status of the management intent. If the management intent is associated with an ongoing external approval process, the intent interface module first calls the external approval system interface to terminate the approval report and then updates the management intent status to revoked; if there is no ongoing approval process, the management intent status is directly updated to revoked. The revocation operation is an irreversible result change, and all operation records are persistently stored in the database.

[0038] For example, in financial scenarios, the approval chain for changes to core payment systems typically involves multiple levels of approval, with asynchronous tasks continuously polling the approval status until the final result is returned. In medical scenarios, the approval process for imaging system maintenance operations also obtains approval progress through asynchronous polling. Once the approval status from an external approval system is obtained, that status is synchronously updated to reflect the local management intent.

[0039] This invention, through asynchronous polling and state synchronization, achieves linkage between the approval status of external approval systems and this system, ensuring that approval results are promptly reflected in the lifecycle status of management intentions. Specifically, as follows... Figure 4 The above, Figure 4 yes Figure 2 A flowchart illustrating a specific implementation of step S20. Specifically, it includes the following steps S21-S23: S21: Send an approval status query request for the approval process instance to the external approval system at preset time intervals.

[0040] Specifically, in this embodiment of the invention, the operation and maintenance management platform initiates an asynchronous task to periodically send approval status query requests to the external approval system at preset time intervals. Each query request carries a unique identifier for the approval process instance bound to the management intent. The preset time interval can be flexibly configured according to the urgency of the operation and maintenance scenario. For example, a shorter polling interval can be set for high-priority management intents to obtain approval results more quickly. For instance, in a financial scenario, after a management intent to ensure the availability of the payment transaction system is initiated for approval, the asynchronous task sends a query request to the external approval system every preset time interval, continuously tracking the flow status of the approval process instance at each level of approval node until the entire approval chain is completed. This embodiment of the invention continuously tracks the external approval status through an asynchronous polling mechanism, eliminating the need for manual transfer of approval results between the approval system and the operation and maintenance system, thus automating the tracking of approval status.

[0041] S22: Receive the current approval status of the approval process instance returned by the external approval system, and compare the current approval status of the approval process instance with the approval status of the management intent stored locally.

[0042] Specifically, in this embodiment of the invention, the asynchronous task of the operation and maintenance management platform receives the current approval status of the approval process instance returned by the external approval system, and then compares the current approval status with the management intent approval status stored in the local database to determine whether there is a difference between the two.

[0043] For example, in a financial scenario, an asynchronous task receives an approval process instance from an external approval system, currently showing "Approved by department head, awaiting approval from risk control personnel," while the locally stored management intent approval status shows "Approving under department head." Comparison reveals an inconsistency, indicating the approval status has progressed. In a medical scenario, the asynchronous task receives an external approval system showing "Approved," while the locally stored management intent approval status remains "Approving underway." Comparison confirms the status has changed.

[0044] This invention introduces a comparison and judgment logic, which triggers subsequent updates only when the approval status is confirmed to have changed, thus avoiding indiscriminate duplicate writing to the database and improving the efficiency of system resource utilization.

[0045] S23: When the current approval status of the approval process instance is inconsistent with the approval status of the management intent stored locally, update the approval status of the management intent to the current approval status.

[0046] Specifically, in this embodiment of the invention, when the current approval status of the approval process instance is inconsistent with the locally stored management intent approval status, the asynchronous task updates the management intent approval status to the current approval status. The updated management intent approval status will serve as the basis for subsequent process engine-driven intent parsing and execution.

[0047] For example, in a financial scenario, when an asynchronous task detects that the current status of an approval process instance has changed from "Approving" to "Approved," it synchronously updates the approval status of the local management intent to "Approved." Subsequently, the process engine detects that the management intent's approval status has changed to the target status and automatically drives the management intent to enter the intent parsing node, initiating the generation and execution process of the execution intent. This invention achieves the linkage between approval status and automated execution by synchronously updating the approval status of the external approval system to the local management intent in real time and accurately.

[0048] S30: When the approval status of the management intent changes to the target status, the management intent is driven into the intent parsing node through the process engine, and the rule engine is called through the intent parsing node.

[0049] Specifically, in this embodiment of the invention, the process engine monitors the approval status of management intentions. When it detects that the approval status of a management intention has changed to the target status, the process engine drives the management intention to the intention parsing node. The intention parsing node, as a coordination module between the process engine and the rule engine, is responsible for calling the rule engine and passing the attribute information of the management intention and the current real-time operation and maintenance indicators to the rule engine.

[0050] For example, in a financial scenario, once a management intent is approved, the process engine drives it to the intent parsing node. The intent parsing node obtains the current real-time operational metrics of the payment system, such as transaction success rate and response latency, and sends them along with the attribute information of the management intent to the rules engine. In a medical scenario, the intent parsing node obtains the real-time operational metrics of the imaging system, such as current image retrieval response time and storage node load, and sends them to the rules engine.

[0051] This invention utilizes the event-driven mechanism of the process engine to automatically drive management intent into the parsing stage and invoke the rule engine by using changes in approval status as a trigger condition, thereby achieving effective integration of process orchestration and rule decision-making.

[0052] Furthermore, step S30 specifically includes the following steps S31-S32: S31: When the process engine detects that the approval status of the management intent has changed to the target status, it drives the management intent to the intent parsing node.

[0053] Specifically, the process engine continuously monitors the approval status of management intentions. This monitoring can be done through event listening or periodic scanning. When the process engine detects that the approval status of a management intention has changed from a non-target state to a target state, it drives the management intention from the current process node to the intention parsing node. The target state can be a state indicating that the approval process has been successfully completed, such as "approved" or "passed." For example, in a financial scenario, a management intention for ensuring the availability of a payment transaction system changes its approval status to "approved" after undergoing multiple levels of approval. Upon detecting this status change, the process engine immediately drives the management intention to the intention parsing node, preparing to enter the intention parsing and decision-making stage.

[0054] This invention utilizes a workflow engine to automatically monitor the approval status of management intentions and trigger workflow transitions, thus connecting the approval process with the intention parsing process. Changes in the approval status of management intentions serve as driving events, automatically initiating subsequent processing flows without manual intervention.

[0055] S32: Perform domain rule matching on the management intent, and input the management intent data and real-time operation and maintenance data after domain rule matching into the rule engine.

[0056] Specifically, after receiving the management intent driven by the process engine, the intent parsing node performs pre-processing on the management intent. First, the intent parsing node obtains the operation and maintenance domain to which the management intent belongs from its attribute information. Based on the preset domain-rule correspondence, it matches the corresponding approval rule template, execution strategy template, or permission constraint rule for that domain. Different preset operation and maintenance domains correspond to different rule sets. For example, the cloud product domain corresponds to cloud resource scaling and traffic scheduling rules, the data center domain corresponds to infrastructure change and network switching rules, and the network operation center domain corresponds to network link monitoring and switching rules. Subsequently, the intent parsing node obtains the current real-time operation and maintenance data of the system operation and maintenance object associated with the management intent. The real-time operation and maintenance data includes service level indicators, resource utilization, error budget consumption, and other data that reflect the current operating status of the system. The intent parsing node inputs the management intent data matched with the domain rules and the obtained real-time operation and maintenance data into the rule engine, allowing the rule engine to make subsequent dynamic decisions based on the complete context. For example, when a management intent needs to be created, after the management intent is approved, the user or upstream system initiates a request to create an automation intent through the intent interface module. The intent interface module sends the context information of the automation intent to the rule engine for pre-validation. The rule engine, combining preset policies and real-time operational data, determines whether the creation of the automation intent is compliant. After successful validation, the intent interface module calls the process engine to generate and enable the workflow model corresponding to the automation intent, while establishing and persistently storing the association between the automation intent and the management intent.

[0057] For example, in a financial scenario, the payment system belongs to the cloud product domain. The intent parsing node matches the rule template corresponding to the cloud product domain, and simultaneously obtains real-time operational data such as the current transaction success rate, average response latency, and remaining error budget of the payment service cluster, and inputs the above data into the rule engine. In a medical scenario, the image archiving and communication system belongs to the data center domain. The intent parsing node matches the rule template corresponding to the data center domain, and simultaneously obtains real-time operational data such as the current image retrieval response time, storage node load, and concurrent access volume of the storage cluster, and inputs the above data into the rule engine.

[0058] This invention performs domain rule matching on management intents through intent parsing nodes, enabling different domain operation and maintenance intents to be subject to different rule sets, thus achieving refined rule management by domain.

[0059] S40: The rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic.

[0060] Specifically, in this embodiment of the invention, the rule engine makes dynamic decisions based on the management intent attribute information and real-time operation and maintenance indicators passed in by the intent parsing node. The rule engine comprehensively analyzes the operation and maintenance goals declared by the management intent and the current real-time operation and maintenance indicators of the system operation and maintenance object, determines the difference between the current state and the target state, and generates at least one execution intent based on the difference between the current state and the target state. The execution intent is an encapsulation of operation and maintenance operation logic that can be directly executed by the machine, including information such as specific operation type, operation parameters, and execution order.

[0061] For example, in a financial scenario, the rule engine comprehensively analyzes the transaction success rate target of the payment service and current real-time indicators. If it determines that the current transaction success rate is showing a deteriorating trend, it generates an execution intent that includes operational logic such as expanding payment service instances and adjusting traffic distribution strategies. In a medical scenario, the rule engine generates an execution intent that includes expanding storage nodes or adjusting caching strategies based on the image retrieval response time target and the current system load.

[0062] This invention uses a rule engine to automatically convert abstract management intentions into machine-executable execution intentions, thus realizing the transformation from target declaration to specific operation plan. Figure 5 yes Figure 2 A flowchart illustrating a specific implementation of step S40. Specifically, it includes the following steps S41-S43: S41: The rule engine parses the attribute information of the management intent and determines the system operation and maintenance object and operation and maintenance target corresponding to the management intent.

[0063] Specifically, in this embodiment of the invention, after receiving management intent data from the intent parsing node, the rule engine parses the attribute information of the management intent. The attribute information of the management intent includes intent description, associated system identifier, and operation and maintenance domain. The rule engine extracts the associated system identifier from the attribute information to determine the system operation and maintenance object targeted by the management intent. The system operation and maintenance object can be a server cluster, database instance, network link, or application service, etc. Simultaneously, the rule engine extracts the operation and maintenance objective from the intent description in the attribute information. The operation and maintenance objective can be a quantifiable service level indicator such as availability threshold, response time limit, and resource utilization limit. For example, in a medical scenario, after parsing the management intent attribute information, the rule engine determines that the system operation and maintenance object is the storage cluster of the image archiving and communication system, and the operation and maintenance objective is that the image retrieval response time does not exceed two seconds.

[0064] This invention automatically parses the attribute information of management intentions through a rule engine, and extracts system operation and maintenance objects and quantifiable operation and maintenance goals. It translates the operation and maintenance intentions entered by users in natural language or structured forms into machine-understandable operation objects and numerical goals, providing a clear benchmark for subsequent automated comparison and decision-making.

[0065] S42: Obtain the real-time operation and maintenance indicators of the system operation and maintenance object, and compare the real-time operation and maintenance indicators with the operation and maintenance target.

[0066] Specifically, in this embodiment of the invention, the rule engine obtains the current real-time operation and maintenance indicators of a determined system operation and maintenance object from a monitoring system or data acquisition platform. These real-time operation and maintenance indicators are quantifiable data reflecting the current operating status of the system operation and maintenance object, corresponding to the operation and maintenance goals. The rule engine compares the obtained real-time operation and maintenance indicators with the extracted operation and maintenance goals. For example, in a medical scenario, the rule engine obtains the current image retrieval response time of the image archiving and communication system and compares it with the operation and maintenance goals. If the current response time is one second, the goal is met; if the current response time is three seconds, the preset time limit is exceeded, indicating performance degradation that needs to be addressed.

[0067] In this embodiment of the invention, the rule engine automatically obtains real-time operation and maintenance indicators and compares them with the operation and maintenance goals. The system can perceive the gap between the current operating status and the expected goal in real time, providing a data-driven basis for subsequent decision-making.

[0068] S43: Based on the comparison results between real-time operation and maintenance indicators and operation and maintenance objectives, generate at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent includes machine-executable operation and maintenance logic.

[0069] Specifically, in this embodiment of the invention, the rule engine generates at least one execution intent corresponding to the system's maintenance object based on the comparison results between real-time maintenance metrics and maintenance objectives. When the comparison results indicate that the real-time maintenance metrics have met the maintenance objectives, the rule engine generates an execution intent containing operational logic to maintain the current state. The execution intent encapsulates the maintenance operation logic into a machine-executable data structure, containing information such as operation type, operation parameters, and execution order, which can be directly parsed and driven by the process engine. In this embodiment of the invention, the rule engine generates execution intents of different levels and different operation combinations based on the degree and direction of deviation, achieving refined and differentiated decision-making in maintenance operations.

[0070] S50: Drive the execution intent through the process engine and execute the operation and maintenance logic on the system operation and maintenance object.

[0071] Specifically, in this embodiment of the invention, the process engine receives the execution intent generated by the rule engine and drives the execution intent to execute the operation and maintenance logic contained therein on the system operation and maintenance object.

[0072] For example, in a financial scenario, the process engine driver executes operations on the payment service cluster, including the intent to scale up instances and adjust traffic distribution strategies. In a medical scenario, the process engine driver executes operations on the storage cluster of the image archiving and communication system, including the intent to scale up storage nodes and adjust caching strategies.

[0073] This invention, through a unified process engine driving the execution of execution intentions, achieves automated connection from decision-making to execution. Specifically, as follows... Figure 6 The above, Figure 6 yes Figure 2 A flowchart illustrating a specific implementation of step S50. Specifically, it includes the following steps S51-S53: S51: The process engine instantiates the execution intent into a workflow instance, wherein the workflow instance contains multiple operation and maintenance nodes arranged in a preset order.

[0074] Specifically, in this embodiment of the invention, the process engine receives the execution intent generated by the rule engine. The execution intent is a data structure containing operation and maintenance logic, but it does not yet have a runnable form. The process engine instantiates the execution intent into a workflow instance, parses the operation logic in the execution intent, and decomposes it into multiple operation and maintenance operation nodes arranged in a preset order. Each operation and maintenance operation node corresponds to a minimum execution unit, such as calling the cloud platform interface to create an instance, modifying the load balancing configuration, updating the network policy, or verifying the service health status. The arrangement order between nodes is determined according to the operation and maintenance operation logic. For example, in a financial scenario, the execution intent includes the operation logic of increasing the number of payment service instances and adjusting the load balancing weight. The process engine instantiates the execution intent into a workflow instance, which includes the following operation and maintenance operation nodes arranged in order: the first node is to call the cloud platform interface to create a new instance; the second node is to configure the network policy and security group rules of the new instance; the third node is to add the new instance to the load balancing backend service list and set the weight; the fourth node is to verify the health status of the new instance; and the fifth node is to gradually release old instances or adjust the weight of old instances.

[0075] In this embodiment of the invention, the execution intent is instantiated into a workflow instance containing ordered orchestration nodes through a process engine, so that the originally static operation logic description is transformed into a schedulable and executable dynamic workflow.

[0076] S52: Drive each operation node in the workflow instance to execute the operation logic on the system operation object.

[0077] Specifically, in this embodiment of the invention, the process engine drives each operation node in the workflow instance to execute sequentially according to the preset order determined in step S51. When each node executes, the process engine calls the corresponding underlying operation tool or platform interface to initiate specific operation instructions to the system operation object. When the previous node completes execution and its execution status is successful, the process engine automatically drives the next node to execute. When a node fails to execute, the process engine can retry, skip, or trigger a rollback operation according to a preset exception handling strategy. For example, when an intention automation operation needs to be executed, the created automation intention supports multiple operations such as updating, unbinding, editing flowcharts, and execution. Users initiate operation requests through the intention interface module: update operations are used to modify the attribute information or workflow definition of the automation intention; unbinding operations are used to remove the association between the automation intention and the management intention; editing flowchart operations are used to adjust the arrangement order or parameters of the operation nodes in the workflow model; and execution operations are used to trigger the workflow instance to run. The process engine is responsible for editing and instantiating the workflow model, and after execution, it feeds back the execution status and results to the intention interface module. When an automated operation needs to be deleted, the user initiates a deletion request for a specific automated intent through the intent interface module. Before deletion, the intent interface module first calls the workflow engine to pause the workflow corresponding to the automated intent to prevent any running workflow instances from being deleted. After receiving a successful pause confirmation from the workflow engine, the intent interface module calls the workflow engine again to officially delete the workflow model definition and associated running instance data. Subsequently, the intent interface module updates the automated intent status to deleted and simultaneously cleans up the corresponding mapping records in the association table. For example, in a financial scenario, the workflow engine first drives the first node to call the cloud platform interface to create a new payment service instance. After the instance is successfully created and returns an instance identifier, it drives the second node to configure network policies and security group rules, and so on, until the last node completes the adjustment of the old instance weight. Throughout the entire execution process, the payment service cluster gradually completes capacity expansion and traffic allocation optimization.

[0078] In this embodiment of the invention, the process engine drives each node to execute sequentially, and the operation and maintenance operations proceed step by step according to the preset arrangement order, avoiding confusion or omission of operation steps.

[0079] S53: During the execution of the workflow instance, continuously monitor the execution status and execution results of each operation and maintenance node, and feed the execution results back to the rule engine.

[0080] Specifically, in this embodiment of the invention, the process engine continuously monitors the execution status and results of each operation node during the execution of the workflow instance. The execution status includes status indicators such as not started, in progress, completed, and failed; the execution results include information such as changes in operation metrics before and after the operation, operation time, and whether the operation was successful. The process engine records the execution status and results of each node in real time, and feeds back the execution results to the rule engine according to a preset strategy after the workflow instance is completed or during execution, for the rule engine to evaluate the execution effect and make subsequent decisions.

[0081] For example, in a financial scenario, the process engine continuously monitors the execution status of each node in the payment service expansion workflow instance, including whether the new instance was successfully created, whether the network configuration took effect, whether the load balancing weight was updated, and whether the new instance health check passed. After the entire workflow instance is completed, the process engine feeds back the execution results to the rules engine. The execution results include the number of expanded payment service instances, the load distribution of each instance, and whether the transaction success rate has recovered to the target level. After receiving the feedback, the rules engine compares the execution results with the operational goals of the management intent to determine whether further corrective actions need to be triggered.

[0082] This invention embodiment uses a process engine to continuously monitor and track the status of each node during execution, making the execution process of operation and maintenance traceable. The execution status and results of each node are recorded, providing a complete operation log for subsequent auditing and troubleshooting.

[0083] In this embodiment of the invention, after step S50, where the process engine drives the execution intent and executes the maintenance operation logic on the system maintenance object, the method further includes: S61: Obtain the execution result of the execution intent on the system operation and maintenance object to execute the operation and maintenance operation logic, and compare the execution result with the operation and maintenance target in the management intent request.

[0084] Specifically, in this embodiment of the invention, the execution result includes changes in key operational indicators of the system's operational objects before and after execution, such as the type of operation performed, indicator values ​​before and after the operation, operation time, and whether the operation was successful. Subsequently, the system compares the current operating status of the system reflected in the execution result with the operational goals declared in the management intent request to determine whether the current status has achieved the expected goals.

[0085] For example, in a medical scenario, the execution intent includes operations such as expanding storage nodes and migrating hot image data. The system obtains the image retrieval response time after execution as the execution result and compares it with the operation and maintenance target. If the response time after execution has been reduced to less than two seconds, the target is met; if the response time after execution is three seconds, there is still a deviation.

[0086] This invention, through its embodiment, automatically acquires the execution results after each maintenance operation is completed and compares them with the original maintenance objectives. This gives the system a self-evaluation capability, eliminating the need for manual judgment on whether the operation has achieved the expected results and thus automating the evaluation of maintenance effectiveness.

[0087] S62: When the execution result deviates from the operation and maintenance target, at least one corrective execution intent corresponding to the system operation and maintenance object is generated based on the degree of deviation between the execution result and the operation and maintenance target.

[0088] Specifically, in this embodiment of the invention, if the comparison between the execution result and the operation and maintenance target in the management intent request shows that the execution result still deviates from the operation and maintenance target, the rule engine generates a corrective execution intent for the deviation based on the degree and direction of the deviation.

[0089] For example, in a financial scenario, if the transaction success rate after execution deviates little from the operation and maintenance target, the rule engine generates a corrective execution intent that includes further fine-tuning the load balancing weight or slightly increasing the number of instances; if the deviation is large and the error budget consumption continues to accelerate, the rule engine generates a corrective execution intent that includes higher-level operations such as switching traffic to a backup data center and triggering service degradation.

[0090] This invention, through a rule engine, generates differentiated correction execution intentions based on the degree of deviation, rather than applying the same correction strategy to all scenarios, thus achieving refined control of operation and maintenance. Using the degree of deviation as the decision-making basis ensures that the intensity of the correction operation matches the severity of the actual problem, avoiding either insufficient correction leading to problem persistence or excessive correction causing resource waste.

[0091] S63: Drive the correction execution intent through the process engine, and execute the operation and maintenance logic in the correction execution intent on the system operation and maintenance object.

[0092] Specifically, in this embodiment of the invention, the rule engine transmits the generated correction execution intent to the process engine. The process engine, following the same execution channel as the regular execution intent, instantiates the correction execution intent into a workflow instance and drives the operation nodes within it to execute sequentially in a preset order, performing correction operation logic on the system operation object. The execution process of the correction execution intent is also continuously monitored by the process engine, and the execution result is fed back to the rule engine for comparison and evaluation. If deviations still exist after correction, a new round of correction can be triggered until the operating status of the system operation object approaches the operation goal declared by the management intent.

[0093] For example, in a financial scenario, the process engine drives a corrective execution intent that includes fine-tuning load balancing weights and increasing the number of instances to perform corrective operations on the payment service cluster. After execution, the transaction success rate is retrieved again. If it has recovered to the target level, the loop ends; if there is still a deviation, the next round of correction is triggered. This ensures that regular execution and corrective execution are carried out within a unified framework, guaranteeing the consistency and traceability of the execution process.

[0094] As can be seen, in the above solution, after the management intent is approved, the process engine automatically drives it to the intent parsing node and triggers the rule engine, thus realizing the association between process orchestration and rule decision-making. The rule engine combines the operational goals of the management intent with the real-time operational indicators of the system to make dynamic decisions, judge the difference between the current state and the target state, and automatically generate an execution intent containing specific operational logic. This achieves automated operation and maintenance from the user's submission of operational goals to the machine's automatic execution.

[0095] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0096] In one embodiment, an intent-driven system automation operation and maintenance device is provided, which corresponds one-to-one with the intent-driven system automation operation and maintenance method described in the above embodiments. For example... Figure 7 As shown, Figure 7 This is a schematic diagram of a system automated operation and maintenance device based on intent-driven principles according to an embodiment of the present invention. The device includes an acquisition module 71, an update module 72, a calling module 73, a generation module 74, and an execution module 75. Detailed descriptions of each functional module are as follows: The acquisition module 71 is used to acquire the management intent request input by the user, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; Update module 72 is used to asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent. The calling module 73 is used to drive the management intent into the intent parsing node through the process engine when the approval status of the management intent changes to the target status, and to call the rule engine through the intent parsing node; The generation module 74, the rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic; The execution module 75 is used to drive the execution intent through the process engine and execute the operation and maintenance logic on the system operation and maintenance object.

[0097] In one embodiment, the acquisition module 71 is specifically used for: Obtain the management intent request input by the user, extract the operation and maintenance domain attribute from the management intent request, and determine the preset operation and maintenance domain to which the operation and maintenance domain attribute belongs; Based on the management intent request and the determined preset operation and maintenance domain, generate an approval request corresponding to the management intent request; Add the operation and maintenance domain attribute to the approval request, and send the approval request with the added operation and maintenance domain attribute to the external approval system.

[0098] In one embodiment, the update module 72 is specifically used for: At preset time intervals, send approval status query requests for the approval process instance to the external approval system; Receive the current approval status of the approval process instance returned by the external approval system, and compare the current approval status of the approval process instance with the approval status of the management intent stored locally; When the current approval status of the approval process instance is inconsistent with the approval status of the management intent stored locally, the approval status of the management intent is updated to the current approval status.

[0099] In one embodiment, module 73 is invoked, specifically for: When the process engine detects that the approval status of the management intent has changed to the target status, it drives the management intent to the intent parsing node; The management intent is matched with domain rules, and the management intent data and real-time operation and maintenance data after domain rule matching are input into the rule engine.

[0100] In one embodiment, the generation module 74 is specifically used for: The rule engine parses the attribute information of the management intent to determine the system operation and maintenance object and operation and maintenance goal corresponding to the management intent; Obtain the real-time operation and maintenance indicators of the system operation and maintenance object, and compare the real-time operation and maintenance indicators with the operation and maintenance target; Based on the comparison results between real-time operation and maintenance indicators and operation and maintenance objectives, at least one execution intent corresponding to the system operation and maintenance object is generated, wherein the execution intent contains machine-executable operation and maintenance logic.

[0101] In one embodiment, the execution module 75 is specifically used for: The process engine instantiates the execution intent into a workflow instance, wherein the workflow instance contains multiple operation and maintenance nodes arranged in a preset order; Drive each operation node in the workflow instance to execute the operation logic on the system operation object; During the execution of the workflow instance, the execution status and results of each operation and maintenance node are continuously monitored, and the execution results are fed back to the rule engine.

[0102] In one embodiment, the intent-driven system automation operation and maintenance device is further configured to: Obtain the execution result of the operation and maintenance operation logic executed on the system operation and maintenance object by the execution intent, and compare the execution result with the operation and maintenance target in the management intent request; When the execution result deviates from the operation and maintenance target, at least one corrective execution intent corresponding to the system operation and maintenance object is generated based on the degree of deviation between the execution result and the operation and maintenance target. The process engine drives the correction execution intent, and the operation and maintenance logic in the correction execution intent is executed on the system operation and maintenance object.

[0103] This invention provides an intent-driven automated system operation and maintenance device. After a management intent is approved, the process engine automatically drives it to the intent parsing node and triggers the rule engine, thus linking process orchestration with rule decision-making. The rule engine dynamically decides based on the management intent's operation and maintenance goals and real-time system operation and maintenance indicators, judging the difference between the current state and the target state, and automatically generating an execution intent containing specific operational logic. This achieves automated operation and maintenance from the user's proposed operation and maintenance goals to automatic machine execution.

[0104] Specific limitations regarding intent-driven automated system operation and maintenance devices can be found in the limitations of intent-driven automated system operation and maintenance methods described above, and will not be repeated here. Each module in the aforementioned intent-driven automated system operation and maintenance device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0105] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 8 As shown, Figure 8 This is a schematic diagram of a computer device according to an embodiment of the present invention. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with external clients via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a server-side intention-driven system automation operation and maintenance method.

[0106] In one embodiment, a computer device is provided, which may be a client, and its internal structure diagram may be as follows: Figure 9 As shown, Figure 9 This is another structural schematic diagram of a computer device according to an embodiment of the present invention. The computer device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements client-side functions or steps of an intent-driven system automation operation and maintenance method.

[0107] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps: Obtain the user's input management intent request, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; Asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent; When the approval status of the management intent changes to the target status, the management intent is driven into the intent parsing node through the process engine, and the rule engine is called through the intent parsing node. The rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic. The process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object.

[0108] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor: Obtain the user's input management intent request, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; Asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent; When the approval status of the management intent changes to the target status, the management intent is driven into the intent parsing node through the process engine, and the rule engine is called through the intent parsing node. The rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic. The process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object.

[0109] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or computer device described above can be referred to the relevant descriptions on the server side and client side in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0110] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0111] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0112] It should be noted that any AI models, software tools, or components not belonging to this company appearing in the embodiments of this application are merely illustrative examples and do not represent actual use. All user personal information involved in the embodiments of this application has been authorized (with the knowledge and consent) by the relevant parties or has been fully authorized by all parties, and the executing entity may obtain it through various legal and compliant means. The collection, storage, use, processing, transmission, provision, and disclosure of the information, data, and signals involved all comply with relevant laws and regulations and do not violate public order and good morals.

[0113] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A system automated operation and maintenance method based on intent-driven principles, characterized in that, include: Obtain the user's input management intent request, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; Asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent; When the approval status of the management intent changes to the target status, the management intent is driven into the intent parsing node through the process engine, and the rule engine is called through the intent parsing node. The rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic. The process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object.

2. The intention-driven system automated operation and maintenance method according to claim 1, characterized in that, Obtaining a user-inputted management intent request, generating a corresponding approval request based on the management intent request, and sending the generated approval request to an external approval system, including: Obtain the management intent request input by the user, extract the operation and maintenance domain attribute from the management intent request, and determine the preset operation and maintenance domain to which the operation and maintenance domain attribute belongs; Based on the management intent request and the determined preset operation and maintenance domain, generate an approval request corresponding to the management intent request; Add the operation and maintenance domain attribute to the approval request, and send the approval request with the added operation and maintenance domain attribute to the external approval system.

3. The intention-driven system automated operation and maintenance method according to claim 1, characterized in that, The asynchronous polling of the approval status of the approval process instance bound to the management intent in the external approval system, and the synchronous updating of the approval status to the approval status of the management intent, includes: At preset time intervals, send approval status query requests for the approval process instance to the external approval system; Receive the current approval status of the approval process instance returned by the external approval system, and compare the current approval status of the approval process instance with the approval status of the management intent stored locally; When the current approval status of the approval process instance is inconsistent with the approval status of the management intent stored locally, the approval status of the management intent is updated to the current approval status.

4. The intention-driven system automated operation and maintenance method according to claim 1, characterized in that, When the approval status of the management intent changes to the target status, the process engine drives the management intent to enter the intent parsing node, and the intent parsing node calls the rule engine, including: When the process engine detects that the approval status of the management intent has changed to the target status, it drives the management intent to the intent parsing node; The management intent is matched with domain rules, and the management intent data and real-time operation and maintenance data after domain rule matching are input into the rule engine.

5. The intention-driven system automated operation and maintenance method according to claim 1, characterized in that, The rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, generating at least one execution intent corresponding to the system operation and maintenance object. The execution intent contains machine-executable operation and maintenance logic, including: The rule engine parses the attribute information of the management intent to determine the system operation and maintenance object and operation and maintenance goal corresponding to the management intent; Obtain the real-time operation and maintenance indicators of the system operation and maintenance object, and compare the real-time operation and maintenance indicators with the operation and maintenance target; Based on the comparison results between real-time operation and maintenance indicators and operation and maintenance objectives, at least one execution intent corresponding to the system operation and maintenance object is generated, wherein the execution intent contains machine-executable operation and maintenance logic.

6. The intention-driven system automated operation and maintenance method according to claim 1, characterized in that, The step of driving the execution intent through the process engine to execute the operation and maintenance logic on the system operation and maintenance object includes: The process engine instantiates the execution intent into a workflow instance, wherein the workflow instance contains multiple operation and maintenance nodes arranged in a preset order; Drive each operation node in the workflow instance to execute the operation logic on the system operation object; During the execution of the workflow instance, the execution status and results of each operation and maintenance node are continuously monitored, and the execution results are fed back to the rule engine.

7. The intention-driven system automated operation and maintenance method according to claim 1, characterized in that, After the process engine drives the execution intent to execute the operation and maintenance logic on the system operation and maintenance object, the method further includes: Obtain the execution result of the operation and maintenance operation logic executed on the system operation and maintenance object by the execution intent, and compare the execution result with the operation and maintenance target in the management intent request; When the execution result deviates from the operation and maintenance target, at least one corrective execution intent corresponding to the system operation and maintenance object is generated based on the degree of deviation between the execution result and the operation and maintenance target. The process engine drives the correction execution intent, which executes the operation and maintenance logic in the correction execution intent on the system operation and maintenance object.

8. An intent-driven system automation operation and maintenance device, characterized in that, include: The acquisition module is used to acquire the management intent request input by the user, generate a corresponding approval request based on the management intent request, and send the generated approval request to an external approval system; The update module is used to asynchronously poll the approval status of the approval process instance bound to the management intent in the external approval system, and synchronously update the approval status to the approval status of the management intent. The calling module is used to drive the management intent into the intent parsing node through the process engine when the approval status of the management intent changes to the target status, and to call the rule engine through the intent parsing node; The generation module, wherein the rule engine makes decisions based on the attribute information of the management intent and real-time operation and maintenance indicators, and generates at least one execution intent corresponding to the system operation and maintenance object, wherein the execution intent contains machine-executable operation and maintenance logic; The execution module is used to drive the execution intent through the process engine and execute the operation and maintenance logic on the system operation and maintenance object.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the intent-driven system automation operation and maintenance method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the intent-driven system automation operation and maintenance method as described in any one of claims 1 to 7.

Images