Automatic service management method and system based on event flow driving model

Through the service automation management method based on the event process-driven model, the abnormal service components of the automation system are analyzed and managed, and the problem of difficulty in discovering performance problems in the existing technology is solved, and the system maintenance efficiency and operation stability are improved.

CN119025321AInactive Publication Date: 2024-11-26CHINA HUADIAN GROUP CO LTD SICHUAN BRANCH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411193307.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-11-26
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

It is difficult to detect performance problems in the current automation system in time when business development and scale expansion, resulting in increased operation and maintenance complexity and affecting the operating efficiency and stability of the system.

Method used

The service automation management method based on the event process-driven model is adopted, and targeted management and quality testing are carried out by analyzing the operating parameters of the driver equipment, locating and classifying abnormal service components, and targeted management and quality testing are carried out to ensure the high-quality operation of the system in various scenarios.

Benefits of technology

Improve maintenance efficiency and operation stability. Through precise analysis and management, one-sidedness brought about by a single indicator is avoided, and the system performance is comprehensively evaluated to ensure the efficient operation of the system in various scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025321A_ABST
    Figure CN119025321A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of event flow automation services, and particularly discloses an event flow driving model-based service automation management method and system, and the method comprises the steps: obtaining the operation parameters of a driving device to which an event flow driving model belongs, analyzing the operation stability index of the driving device to which the event flow driving model belongs, and obtaining the operation parameters of the driving device to which the event flow driving model belongs; therefore, the driving equipment accurately analyzes and positions each abnormal service component of the event flow driving model, performs anomaly classification on each abnormal service component, improves the maintenance efficiency of the event flow driving model, ensures that high-quality operation can be kept in various scenes through the quality test of the event flow driving model, and improves the maintenance efficiency of the event flow driving model. According to the method, the quality test parameters of the event process-driven model are received, data support is provided for subsequent evaluation and optimization, the quality stability index of the event process-driven model is analyzed, so that quality management is performed on services of the event process-driven model, and the operation stability of driving equipment and the accuracy of the event process-driven model are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of event process automation services, and in particular to a service automation management method and system based on an event process driven model. Background Art

[0002] Event process automation service technology aims to automatically execute a series of tasks through preset rules and logic, thereby realizing automated control of business processes. However, when this service technology lacks corresponding management mechanisms, its potential advantages will be difficult to fully realize, and it may also trigger a series of chain reactions, exposing significant deficiencies.

[0003] For example, the invention patent with announcement number CN106445536B proposes an automated business design management system; the system includes a server and a client, and the server includes a server program and a database; the client program collects user business design information through a design tool and submits it to the server; the server program is used to receive user business design information and perform design processing; the server program provides data information or business processing results related to the business according to the client's business usage requirements; the client program displays the corresponding business interface based on the business data and interface information returned by the server program; the system is suitable for all software development using relational databases, guiding business personnel to quickly complete business development and put it into production immediately. The business can be reused and can be modified at any time according to needs, greatly reducing the cost of business development and maintenance.

[0004] For example, the invention patent with announcement number CN113448561B announces a CI-based automated requirement progress difference analysis method and management server, which can discover delivery deviations of business versions during the research and development process, ensure on-time delivery of business and continuously improve the competitiveness of the enterprise. The method includes: receiving planning information sent by the first terminal device of the business personnel, the planning information includes a business requirement list and identification information of the business version; configuring the identification information into the CI pipeline in the management server, and sending the business requirement list to the second terminal device of the R&D personnel; receiving submission information sent by the second terminal device, the submission information includes ID information corresponding to at least one business requirement; based on the submission information, triggering the CI pipeline to run, based on the ID information corresponding to at least one business requirement, analyzing the development progress of at least one business requirement, and obtaining a development progress difference analysis report corresponding to at least one business requirement.

[0005] However, in the process of implementing the embodiments of the present application, it was found that the above-mentioned technology has at least the following technical problems: although the automation system involved in the above-mentioned application can effectively respond to and process various events and drive the automated execution of business processes, with the development of the business and the expansion of the scale of the automation system, performance bottlenecks gradually emerge, but the automation system involved in the above-mentioned application is often difficult to detect performance problems in a timely manner, thereby increasing the complexity of operation and maintenance of the automation system. Summary of the invention

[0006] In view of the deficiencies in the prior art, the present invention provides a service automation management method and system based on an event process driven model, which can effectively solve the problems involved in the above-mentioned background technology.

[0007] To achieve the above objectives, the present invention is implemented through the following technical solutions: In the first aspect, the present invention provides a service automation management method based on an event process driven model, including: S1. By executing the event process driven model, the operating parameters of the driving device belonging to the event process driven model are obtained, the operating stability index of the driving device belonging to the event process driven model is analyzed, and compared with the operating stability threshold. If the operating stability index of the driving device belonging to the event process driven model is less than the operating stability threshold, the event process driven model executes S2; otherwise, if the operating stability index of the driving device belonging to the event process driven model is greater than or equal to the operating stability threshold, the event process driven model executes S3; S2. Locate each abnormal service component of the event process driven model, analyze the performance abnormality index of each abnormal service component of the event process driven model, and classify each abnormal service component abnormally, thereby managing each abnormal service component of the event process driven model; S3. Through the quality test of the event process driven model, the quality test parameters of the event process driven model are received, and the quality stability index of the event process driven model is analyzed, thereby performing quality management on the service of the event process driven model.

[0008] As a further method, the abnormal service components are classified as abnormal, and the specific analysis process is: the performance abnormality index of each abnormal service component of the event process driven model is compared with the performance abnormality reference value. If the performance abnormality index of an abnormal service component is less than the performance abnormality reference value, the abnormal service component of the event process driven model is marked as a first-category abnormal service component. If the performance abnormality index of an abnormal service component is greater than or equal to the performance abnormality reference value, the abnormal service component of the event process driven model is marked as a second-category abnormal service component, thereby classifying the abnormal service components as abnormal.

[0009] As a further method, the management of each abnormal service component of the event process driven model is carried out. The specific analysis process is: by performing abnormal classification on each abnormal service component, the abnormal type of each abnormal service component of the event process driven model is obtained, and the abnormal types are matched with the performance management methods corresponding to the abnormal types stored in the information repository in turn to obtain the performance management methods corresponding to each abnormal service component of the event process driven model, thereby managing the performance of each abnormal service component of the event process driven model.

[0010] As a further method, the quality management of the services of the event process driven model is carried out, and the specific analysis process is: comparing the quality stability index of the event process driven model with the quality stability threshold. If the quality stability index of the event process driven model is less than the quality stability threshold, the automated management system performs quality management on the services of the event process driven model.

[0011] The second aspect of the present invention provides an application such as a system of a service automation management method based on an event process driven model, including: a driving device operation analysis module, which is used to obtain the operation parameters of the driving device belonging to the event process driven model through the execution of the event process driven model, analyze the operation stability index of the driving device belonging to the event process driven model, and compare it with the operation stability threshold. If the operation stability index of the driving device belonging to the event process driven model is less than the operation stability threshold, the event process driven model executes the abnormal service component classification module; conversely, if the operation stability index of the driving device belonging to the event process driven model is greater than or equal to the operation stability threshold, the event process driven model executes the model service quality management module; an abnormal service component classification module, which is used to locate each abnormal service component of the event process driven model, analyze the performance abnormality index of each abnormal service component of the event process driven model, and perform abnormal classification on each abnormal service component, thereby managing each abnormal service component of the event process driven model; a model service quality management module, which is used to receive the quality test parameters of the event process driven model through the quality test of the event process driven model, analyze the quality stability index of the event process driven model, thereby performing quality management on the service of the event process driven model.

[0012] Compared with the prior art, the embodiments of the present invention have at least the following advantages or beneficial effects:

[0013] (1) The present invention provides a service automation management method and system based on an event process driven model. By obtaining the operating parameters of the driving device to which the event process driven model belongs and analyzing the operating stability index of the driving device to which the event process driven model belongs, the driving device can accurately analyze and locate each abnormal service component of the event process driven model, and classify each abnormal service component as abnormal, so as to take targeted repair measures to improve the maintenance efficiency of the event process driven model. Through the quality test of the event process driven model, it is ensured that high-quality operation can be maintained in various scenarios. The quality test parameters of the event process driven model are received to provide data support for subsequent evaluation and optimization. The quality stability index of the event process driven model is analyzed, thereby performing quality management on the service of the event process driven model, thereby improving the operating stability of the driving device, and improving the operating efficiency and accuracy of the event process driven model.

[0014] (2) The present invention obtains the operation stability index of the driving device belonging to the event process driven model by comprehensively analyzing the response time, processing rate and average temperature increment of the driving device belonging to the event process driven model, which can accurately locate the cause of the performance degradation of the driving device, thereby formulating the event process driven model analysis strategy and improvement measures in a targeted manner.

[0015] (3) The present invention obtains the performance anomaly index of each abnormal service component of the event process driven model by comprehensively analyzing the average memory occupied rate, average CPU usage rate and the number of correctly processed tasks in the corresponding execution processing sub-cycle of each abnormal service component of the event process driven model. It can analyze the potential problems of the event process driven model from a hardware perspective, increase the analysis dimension of the event process driven model, and evaluate the overall performance of the event process driven model more comprehensively and accurately, avoiding the one-sidedness that may be caused by a single indicator. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention is further described using the accompanying drawings, but the embodiments in the accompanying drawings do not constitute any limitation to the present invention. A person skilled in the art can obtain other drawings based on the following drawings without creative work.

[0017] Figure 1 It is a schematic diagram of the method steps of the present invention;

[0018] Figure 2 It is a schematic diagram of system module connection of the present invention;

[0019] Figure 3 It is a schematic diagram of the driving device involved in the present invention.

[0020] Reference numerals: 1. Temperature measurement point. DETAILED DESCRIPTION

[0021] The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only 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 ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0022] Reference Figure 1 As shown, the first aspect of the present invention provides a service automation management method based on an event process driven model, including: S1. Through the execution of the event process driven model, the operating parameters of the driving device belonging to the event process driven model are obtained, the operating stability index of the driving device belonging to the event process driven model is analyzed, and compared with the operating stability threshold. If the operating stability index of the driving device belonging to the event process driven model is less than the operating stability threshold, the event process driven model executes S2; conversely, if the operating stability index of the driving device belonging to the event process driven model is greater than or equal to the operating stability threshold, the event process driven model executes S3; the above-mentioned execution of the event process driven model refers to the process in which the driving device starts the event process driven model until it can execute the service therein, such as the driving device starts the Guangdong Company Ruisi Industrial Internet Platform Integrated Platform to its Material management can be carried out. The event process driven model described below can be substituted into the integrated platform of Guangdong Ruisi Industrial Internet Platform in an example embodiment. The above-mentioned operation stability threshold represents the minimum value of the reasonable range of the operation stability index of the driving device belonging to the event process driven model, which is formulated by the model deployment technicians based on the historical deployment work experience. If the operation stability index of the driving device belonging to the event process driven model is less than the operation stability threshold, it indicates that the problems of the service components in the event process driven model are more significant, and it is necessary to manage the internal service components first, so enter S2. If the operation stability index of the driving device belonging to the event process driven model is greater than or equal to the operation stability threshold, it indicates that the problems of the service components in the event process driven model are relatively small, and the overall performance analysis of the event process driven model can be performed.

[0023] It should be explained that the above-mentioned drive devices include but are not limited to computer devices.

[0024] In a specific embodiment, the present invention obtains the operation stability index of the driving device belonging to the event process driven model by comprehensively analyzing the response time, processing rate and average temperature increment of the driving device belonging to the event process driven model, and can accurately locate the cause of the performance degradation of the driving device, so as to formulate the event process driven model analysis strategy and improvement measures in a targeted manner.

[0025] Specifically, the analysis of the operation stability index of the driving device to which the event flow driven model belongs has the following specific analysis process: extracting the sending time point of the execution request of the event flow driven model and the sending time point when the driving device receives the execution request of the event flow driven model from the operation parameters of the driving device to which the event flow driven model belongs, and performing difference processing to obtain the response duration of the driving device to which the event flow driven model belongs; the sending time point of the execution request of the above-mentioned event flow driven model can be extracted from the log generated by the event flow driven model, and the sending time point when the above-mentioned driving device receives the execution request of the event flow driven model can be obtained through the timestamp recorded by the time service of the operating system to which the driving device belongs; the response duration of the driving device to which the event flow driven model belongs refers to the sending time point when the driving device receives the execution request of the event flow driven model minus the sending time point of the execution request of the event flow driven model.

[0026] The number of request processing of the driving device to which the event flow driven model belongs is extracted from the operating parameters of the driving device to which the event flow driven model belongs within the model execution cycle, and the ratio is processed with the duration corresponding to the model execution cycle to obtain the processing rate of the driving device to which the event flow driven model belongs; the number of request processing of the above-mentioned driving device to which the model is executed can be obtained by filtering the log file generated by the driving device through log analysis tools such as data search and analysis engine; the above-mentioned request processing refers to the driving device receiving and processing the request of the event flow driven model, such as when the driving device receives a request from the event flow driven model to execute a certain instruction, the driving device executes the request.

[0027] It should be explained that the above-mentioned model execution cycle refers to the period from starting the event process driving model to being able to execute the services therein, and the specific duration is extracted from the timestamp recorded by the time service of the operating system to which the driving device belongs.

[0028] Locate each temperature measurement point of the driving device, extract the temperature of each temperature measurement point of the event flow driven model at the end time of the model execution cycle and the temperature at the start time of the model execution cycle from the operating parameters of the driving device belonging to the event flow driven model, perform difference processing to obtain the temperature increment of each temperature measurement point of the event flow driven model, and perform mean analysis to obtain the average temperature increment of the driving device belonging to the event flow driven model. The temperature measurement points of the above driving device, such as Figure 3 As shown in the schematic diagram of the driving device, various temperature measurement points (1) are randomly arranged on the surface of the driving device; the temperature of each temperature measurement point belonging to the above event flow driven model at the end time point of the model execution cycle and the temperature at the start time point of the model execution cycle are both obtained through temperature sensors, and the temperature increment of each temperature measurement point belonging to the above event flow driven model refers to the temperature of each temperature measurement point belonging to the driving model at the end time point of the model execution cycle minus the temperature at the start time point of the model execution cycle.

[0029] The operation stability index of the driving device belonging to the event flow driven model is obtained by comprehensive analysis. In this embodiment, the operation stability index of the driving device belonging to the event flow driven model is obtained by comprehensive analysis of the response time, processing rate and average temperature increment of the driving device belonging to the event flow driven model. It is used to determine the numerical value of the operation stability of the driving device belonging to the event flow driven model. The specific expression is:

[0030]

[0031] Among them, DW is the operation stability index of the drive device to which the event flow driven model belongs. The faster processing rate of the drive device to which the event flow driven model belongs helps to shorten its response time. At the same time, a faster processing rate may cause the temperature of the drive device to increase abnormally, deviating greatly from the ideal value, thereby reversely limiting the processing rate to increase the response time. Excessive response time will reduce the user experience and may cause the performance of the drive device to deteriorate. Too low a processing rate may cause the drive device resources to be occupied for too long, causing the drive device to overheat, and other problems. If the temperature increment deviates too much from the ideal value, it will directly affect the stability of the drive device. Therefore, through detailed data analysis of the three parameters, the event flow driven model algorithm and scheduling strategy can be optimized in a targeted manner to reduce the idling of drive device resources and improve the overall processing efficiency of the drive device.

[0032] RT is the response time of the driving device belonging to the event process driven model, which reflects the response status of the driving device to the event process driven model. If the response time is long, the response time can be reduced by optimizing the system architecture of the event process driven model. For example, the services belonging to the event process driven model can be modularized by defining a standardized API service interface, and the modules of the event process driven model can communicate through a RESTful interface to reduce the module coupling of the event process driven model.

[0033] TP is the processing rate of the driver device to which the event process driven model belongs, which refers to the number of requests from the event process driven model that the driver device can process per unit time. High-quality event process driven models are often more robust, easy to maintain, and can better cope with various complex scenarios. Such event process driven model codes can usually show a higher processing rate when running on the driver device.

[0034] CP is the average temperature increment of the driving device belonging to the event process driven model, which refers to the temperature increase of the driving device relative to the initial state during the execution of the event process driven model task, reflecting the stability of the driving device under working conditions. If the average temperature increment of the driving device is large, it reflects that the code complexity of the event process driven model is large, and there may be problems of resource competition and code redundancy.

[0035] e is a natural constant, CP c It is the temperature increment reference value, which represents the reference value of the average temperature increment of the driving device belonging to the analysis event process driving model, and is formulated by the model deployment technicians based on historical deployment work experience.

[0036] si1 is the impact factor corresponding to the unit value of the response time preset in the information repository, which represents the degree of influence of the unit value of the response time on the operation stability index of the driving device belonging to the event process driven model. The fitting curve corresponding to the response time is obtained by fitting the relationship between the historical network delay, the historical data volume and the response time, and the fitting curve corresponding to the response time is introduced according to the real-time network delay and the data volume, thereby obtaining the impact factor corresponding to the unit value of the response time in this example. The value range of this value in this example is 0 to 1.

[0037] si2 is the impact factor corresponding to the processing rate unit value preset in the information repository, which represents the degree of influence of the processing rate unit value on the operation stability index of the driving device belonging to the event process driven model. The fitting curve corresponding to the processing rate is obtained by fitting the relationship between the historical concurrency number, the historical data access frequency and the processing rate, and the fitting curve corresponding to the processing rate is brought into the fitting curve according to the real-time concurrency number and the data access frequency, thereby obtaining the impact factor corresponding to the processing rate unit value in this example. The value range of this value in this example is 0 to 1.

[0038] si3 is the correction value corresponding to the average temperature increment preset in the information repository, which represents the degree of correction for the change in the average temperature increment. The fitting curve corresponding to the average temperature increment is obtained by fitting the relationship between the historical operating time, the historical data complexity and the average temperature increment. The fitting curve corresponding to the average temperature increment is brought into play according to the real-time operating time and data complexity, thereby obtaining the impact factor corresponding to the unit value of the average temperature increment in this example. The value range of this value in this example is 0 to 1.

[0039] In this exemplary embodiment, a table showing changes in the operation stability index of the driving device to which the event flow driving model belongs and its corresponding parameters is shown in Table 1:

[0040] Table 1 Changes in the operation stability index and corresponding parameters of the drive equipment belonging to the event process drive model

[0041]

[0042] In this example embodiment, the value of the impact factor corresponding to the unit value of the response time is set to 0.30, the value of the impact factor corresponding to the unit value of the processing rate is set to 0.35, the value of the correction value corresponding to the average temperature increment is set to 0.36, and the temperature increment reference value is set to 23 degrees Celsius. It can be seen from Table 1 that the values ​​of the operation stability index are relatively small, so it is necessary to accurately obtain the information of the three parameters in order to better analyze the operation stability index.

[0043] S2. Locate each abnormal service component of the event process driven model, analyze the performance anomaly index of each abnormal service component of the event process driven model, and classify each abnormal service component as abnormal, thereby managing each abnormal service component of the event process driven model. It should be explained that the above positioning of each abnormal service component of the event process driven model, the specific positioning process is: through the execution of the event process driven model, the operating system to which the driver device belongs generates a log file, which records the abnormal information of the event process driven model, including but not limited to timeout errors, error codes, occurrence time, memory resource usage abnormalities, the driver device locates the service component to which the abnormal information belongs according to the abnormal information, thereby locating each abnormal service component of the event process driven model.

[0044] In a specific embodiment, the present invention obtains the performance anomaly index of each abnormal service component of the event process driven model by comprehensively analyzing the average memory occupied rate, the average CPU usage rate and the number of correctly processed tasks in the corresponding execution processing sub-cycle of each abnormal service component of the event process driven model. The potential problems of the event process driven model can be analyzed from a hardware perspective, and the analysis dimension of the event process driven model can be increased. The overall performance of the event process driven model can be evaluated more comprehensively and accurately, and the one-sidedness that may be caused by a single indicator can be avoided.

[0045] Specifically, the abnormal service components are classified as abnormal, and the specific analysis process is as follows: the performance abnormality index of each abnormal service component of the event process driven model is compared with the performance abnormality reference value. If the performance abnormality index of a certain abnormal service component is less than the performance abnormality reference value, the abnormal service component of the event process driven model is marked as a first-class abnormal service component. If the performance abnormality index of a certain abnormal service component is greater than or equal to the performance abnormality reference value, the abnormal service component of the event process driven model is marked as a second-class abnormal service component, thereby classifying the abnormal service components as abnormal; the above-mentioned performance abnormality reference value is formulated by the model deployment technicians based on the historical deployment work experience; the above-mentioned first-class abnormal service component refers to the service component with a low problem severity level; the above-mentioned second-class abnormal service component refers to the service component with a high problem severity level; the above-mentioned classification rules have The main points are: higher CPU usage and memory occupancy rate may indicate that the driver device is processing the service component. However, if these two indicators deviate abnormally from the ideal conditions and the number of correct task processing deviates from the reference task processing number by a small amount, that is, the abnormal service component can complete the task correctly, but it uses too many resources. In this case, it can be considered that there is an algorithm efficiency problem, and only the code structure of the abnormal service component needs to be performance managed. It belongs to the first type of abnormal service component. If these two indicators deviate greatly from the ideal conditions and the number of correct task processing deviates greatly from the reference task processing number, that is, the deviation from the reference task processing number is large, it may indicate that the abnormal service component conflicts when competing for limited resources, and there is a resource competition failure, resulting in a small number of correct task processing. In this case, performance management needs to be performed on the abnormal service component and its related service components. It belongs to the second type of abnormal service component.

[0046] It should be explained that the above-mentioned service components include but are not limited to user services, authentication and authorization services, workflow services, and form services, and the service component framework adopts a microservice architecture.

[0047] Specifically, the management of each abnormal service component of the event process driven model is carried out, and the specific analysis process is: by performing abnormal classification on each abnormal service component, the abnormal type of each abnormal service component of the event process driven model is obtained, and the abnormal types are matched in turn with the performance management methods corresponding to the abnormal types stored in the information repository to obtain the performance management methods corresponding to each abnormal service component of the event process driven model, thereby managing the performance of each abnormal service component of the event process driven model; if an abnormal service component of the event process driven model is a first type of abnormal service component, the performance management method corresponding to the first type of abnormal service component is matched from the information repository, thereby managing the performance of the abnormal service component of the event process driven model; if an abnormal service component of the event process driven model is a second type of abnormal service component, the performance management method corresponding to the second type of abnormal service component is matched from the information repository, thereby managing the performance of the abnormal service component of the event process driven model.

[0048] In an example embodiment, if the user service component in the integrated platform of Guangdong Company's Ruisi Industrial Internet Platform is a first-class abnormal service component, the corresponding performance management method is matched, including but not limited to algorithm reconstruction, parameter tuning, and the model deployment technicians perform corresponding adjustment management; if the form service component in the integrated platform of Guangdong Company's Ruisi Industrial Internet Platform is a second-class abnormal service component, the corresponding performance management method is matched, including but not limited to current limiting strategies and locking mechanisms, and the model deployment technicians perform corresponding adjustment management.

[0049] Furthermore, the analysis of the performance anomaly index of each abnormal service component of the event flow driven model is specifically performed as follows: the amount of drive device memory of each abnormal service component of the event flow driven model at the end time point of the corresponding execution processing sub-cycle and the amount of drive device memory at the start time point of the corresponding execution processing sub-cycle are obtained, the amount of memory occupied by each abnormal service component of the event flow driven model in the corresponding execution processing sub-cycle is obtained by difference processing, and the average rate of memory occupied by each abnormal service component of the event flow driven model is obtained by ratio processing with the corresponding execution processing sub-cycle duration; the above-mentioned execution processing sub-cycle represents the cycle for analyzing the performance of the service component, and its specific duration is determined by the model deployment technician according to the actual situation. Different service components have corresponding execution processing sub-cycles, and the execution processing sub-cycles corresponding to different service components do not overlap in time, and analyzing the drive devices of each abnormal service component essentially refers to analyzing the drive devices in different execution processing sub-cycles; the amount of drive device memory of each abnormal service component at the end time point of the corresponding execution processing sub-cycle and the amount of drive device memory at the start time point of the corresponding execution processing sub-cycle of the above-mentioned event flow driven model can be obtained by calling the memory management function in the language standard library provided by the operating system to which the drive device belongs.

[0050] The real-time CPU usage rate of the driving device of each abnormal service component of the event process driven model in the corresponding execution processing sub-cycle is collected, and the average CPU usage rate of each abnormal service component of the event process driven model is obtained by average processing; the real-time CPU usage rate of the driving device of each abnormal service component of the above event process driven model in the corresponding execution processing sub-cycle can be monitored by the monitoring component of the container orchestration tool (such as the metric data server).

[0051] At the same time, the number of correctly processed tasks of each abnormal service component of the event process driven model in the corresponding execution processing sub-cycle is counted, which can be extracted from the log recorded by the logging function integrated by the abnormal service component, where the log includes but is not limited to the execution process, results and status of each abnormal component.

[0052] The performance anomaly index of each abnormal service component of the event flow driven model is obtained by comprehensive analysis. In this embodiment, the performance anomaly index of each abnormal service component of the event flow driven model is obtained by comprehensive analysis of the average rate of memory occupation, average CPU usage and the number of correctly processed tasks in the corresponding execution processing sub-cycle of each abnormal service component of the event flow driven model. It is used to evaluate the performance anomaly degree of each abnormal service component of the event flow driven model. The specific expression is:

[0053]

[0054] Among them, AP k is the performance anomaly index of the kth abnormal service component of the event process driven model. A higher CPU usage rate and memory occupancy rate may indicate that the driving device is processing the service component. However, if these two indicators are abnormally high and the number of correct task processing deviates from the reference task processing number by a small amount, that is, the abnormal service component can complete the task correctly, but it uses too many resources. If these two indicators are abnormally high and the number of correct task processing is small, that is, the deviation from the reference task processing number is large, it may indicate that the abnormal service component conflicts when competing for limited resources, and there is a situation where resource competition fails, resulting in a small number of correct task processing. Therefore, if the three parameters deviate too much from the reference standard, the performance anomaly index of the service component will increase. By comprehensively analyzing the three parameters into a performance anomaly index and expanding the influence of the three parameters, the abnormal problem type of the abnormal service component can be accurately distinguished, so as to solve the abnormal problem in a targeted manner and ensure that the event process driven model can run stably and reliably.

[0055] MU kIt is the average memory usage rate of the kth abnormal service component in the event process driven model, which refers to the average speed at which the memory usage of the kth abnormal service component changes over time during its execution, reflecting the consumption of memory resources by the kth abnormal service component.

[0056] CU k The average CPU usage rate of the k-th abnormal service component in the event process driven model refers to the proportion of the CPU time occupied by the k-th abnormal service component during its execution to the total CPU time, reflecting the utilization of CPU resources by the k-th abnormal service component.

[0057] FC k It is the number of correctly processed tasks of the kth exception service component in the event process driven model in the corresponding execution processing sub-cycle, reflecting the business processing capability and stability of the kth exception service component.

[0058] MU is the reference rate of memory usage, which indicates the reference value of the average rate of memory usage of each abnormal service component of the event process driven model. It is determined by model deployment technicians based on historical deployment experience.

[0059] CU is the CPU reference usage preset in the information repository, which represents the reference value of the average CPU usage of each abnormal service component of the event process driven model for analysis. It is formulated by model deployment technicians based on historical deployment work experience.

[0060] FC is the reference value of the number of correctly processed tasks preset in the information repository, which represents the reference value of the number of correctly processed tasks of each abnormal service component of the analysis event process driven model in the corresponding execution processing sub-cycle, and is formulated by model deployment technicians based on historical deployment work experience.

[0061] xs1 is the correction factor corresponding to the average rate of memory occupation preset in the information repository, which represents the numerical value of the degree of correction for the change in the average rate of memory occupation. The fitting curve corresponding to the average rate of memory occupation is obtained by fitting the relationship between the historical data processing volume, the historical memory leakage volume and the average rate of memory occupation, and the fitting curve corresponding to the average rate of memory occupation is brought into the fitting curve according to the real-time data processing volume and the memory leakage volume, thereby obtaining the impact factor corresponding to the unit value of the average rate of memory occupation in this example. The value range of this value in this example is 0 to 1.

[0062] xs2 is the correction factor corresponding to the average CPU usage, which represents the degree of correction for the change in average CPU usage. The fitting curve corresponding to the average CPU usage is obtained by fitting the relationship between the historical load, the historical algorithm efficiency and the average CPU usage. The real-time load and the algorithm efficiency are brought into the fitting curve corresponding to the average CPU usage, thereby obtaining the influencing factor corresponding to the unit value of the average CPU usage in this example. The value range of this value in this example is 0 to 1.

[0063] xs3 is the correction factor corresponding to the number of correctly processed tasks, which represents the degree of correction for the change in the number of correctly processed tasks. The fitting curve corresponding to the number of correctly processed tasks is obtained by fitting the relationship between the historical task complexity, the historical network bandwidth and the number of correctly processed tasks. The fitting curve corresponding to the number of correctly processed tasks is brought into the fitting curve according to the real-time task complexity and the network bandwidth, thereby obtaining the impact factor corresponding to the unit value of the number of correctly processed tasks in this example. The value range of this value in this example is 0 to 1.

[0064] k is the number of each abnormal service component, k={1,2,3,...,n}, and n is the total number of abnormal service components.

[0065] S3. Through the quality test of the event process driven model, the quality test parameters of the event process driven model are received, and the quality stability index of the event process driven model is analyzed, thereby performing quality management on the service of the event process driven model.

[0066] Specifically, the receiving quality test parameters of the event process driven model specifically involves performing a quality test on the event process driven model to obtain the parameters of the event process driven model during the quality test process, which are recorded as the quality test parameters of the event process driven model; specifically, the model deployment technicians perform a quality test on the event process driven model based on the demand analysis report and project test report of the event process driven model, and the driving device receives the parameters of the event process driven model during the quality test process, thereby performing analysis. In an example embodiment, assuming that the test code coverage of the integrated platform of Guangdong Company's Ruisi Industrial Internet Platform is 90% when tested using a Java code coverage component, the test code coverage of the integrated platform of Guangdong Company's Ruisi Industrial Internet Platform received by the driving device is 90%.

[0067] Specifically, the quality management of the service of the event process driven model is carried out, and the specific analysis process is: comparing the quality stability index of the event process driven model with the quality stability threshold. If the quality stability index of the event process driven model is less than the quality stability threshold, the automated management system performs quality management on the service of the event process driven model; the above-mentioned automated management system refers to a system that receives relevant parameters of the event process driven model and analyzes and manages them; the above-mentioned quality stability threshold represents the minimum value of the reasonable range of the quality stability index of the event process driven model; if the quality stability index of the event process driven model is less than the quality stability threshold, it indicates that the quality stability of the event process driven model in the current state fails to meet the predetermined minimum standard, which may be caused by various factors, including but not limited to defects in model design, uneven resource allocation, external environmental interference or degradation of internal component correlation performance. Therefore, the automated management system generates an early warning feedback log, and the model deployment technician performs quality management on the service of the event process driven model based on the early warning feedback log. If the quality stability index of the event process driven model is greater than or equal to the quality stability threshold, it indicates that the quality stability of the event process driven model meets the predetermined minimum standard, and thus there is no need to perform quality management on its service.

[0068] Specifically, the quality stability index of the event flow driven model, in this embodiment, is obtained by comprehensive analysis of the test case completion rate, test code coverage and average execution time of the test cases of the event flow driven model, and is used to evaluate the quality stability of the event flow driven model. The above specific expression is:

[0069]

[0070] Among them, QI is the quality stability index of the event flow driven model. The shorter average execution time of test cases indicates that the test process of the event flow driven model is faster, and more test cycles can be completed in a limited time, thereby accelerating the verification and iteration cycle of the event flow driven model. According to the verification results, a high test case completion rate is often accompanied by a high code coverage rate, because more test case execution means more code is executed. Excessive execution time may lead to an extension of the test cycle, fully exposing potential quality problems in the event flow driven model. Through the completion rate of test cases, logical problems of the event flow driven model can be discovered. High code coverage can increase the chance of discovering potential errors in the event flow driven model, thereby improving the quality of the event flow driven model in a targeted manner. Therefore, by comprehensively considering the three parameters, the reliability of the test results of the event flow driven model is enhanced, providing strong support for the subsequent test optimization and performance management of the event flow driven model.

[0071] RC is the test case completion rate of the event-flow driven model. A high completion rate means that more test cases are executed correctly and fewer test cases are interrupted due to quality issues of the event-flow driven model.

[0072] FCR is the test code coverage of the event flow driven model. A high test code coverage indicates that more test cases are executed, indicating that the functions of the event flow driven model are closer to the requirements, thereby increasing the quality of the event flow driven model, because the test cases are formulated by model deployment technicians based on the ideal conditions of the event flow driven model.

[0073] ERR is the average execution time of the test cases of the event-flow driven model. Too long an execution time may not fully expose potential problems in the event-flow driven model.

[0074] op1 is the impact factor corresponding to the unit value of the test case completion rate preset in the information repository, which represents the numerical value of the impact of the unit value of the test case completion rate on the quality stability index of the event process driven model. The fitting curve corresponding to the test case completion rate is obtained by fitting the relationship between the historical integration interface quality level, the historical event processing logic completeness and the test case completion rate, and the fitting curve corresponding to the test case completion rate is brought into the fitting curve according to the real-time integration interface quality level and the event processing logic completeness, thereby obtaining the impact factor corresponding to the unit value of the test case completion rate in this example. The value range of this value in this example is 0 to 1.

[0075] op2 is the impact factor corresponding to the unit value of the test code coverage preset in the information repository, which represents the degree of influence of the unit value of the test code coverage on the quality stability index of the event process driven model. The fitting curve corresponding to the test code coverage is obtained by fitting the relationship between the historical model defect density, the historical model repair rate and the test code coverage, and the fitting curve of the test code coverage is brought into account according to the real-time model defect density and the model repair rate, thereby obtaining the impact factor corresponding to the unit value of the test code coverage in this example. The value range of this value in this example is 0 to 1.

[0076] op3 is the impact factor corresponding to the unit value of the average execution time of the test cases preset in the information repository, which represents the degree of influence of the unit value of the average execution time of the test cases on the quality stability index of the event process driven model. The fitting curve corresponding to the average execution time of the test cases is obtained by fitting the relationship between the historical network delay, the historical memory utilization and the average execution time of the test cases, and the fitting curve corresponding to the average execution time of the test cases is introduced according to the real-time network delay and memory utilization, thereby obtaining the impact factor corresponding to the unit value of the average execution time of the test cases in this example. The value range of this value in this example is 0 to 1.

[0077] In this exemplary embodiment, the quality stability index of the event flow driven model and its corresponding parameter change table are shown in Table 2:

[0078] Table 2 Changes of quality stability index and corresponding parameters of event process driven model

[0079]

[0080] In this example embodiment, the value of the impact factor corresponding to the unit value of the test case completion rate is set to 0.23, the value of the impact factor corresponding to the unit value of the test code coverage rate is set to 0.21, and the value of the impact factor corresponding to the unit value of the test case average execution time is set to 0.20. It can be seen from Table 2 that the test case completion rate is positively correlated with the test code coverage rate. When the test case completion rate and the test code coverage rate increase and the average execution time of the test case decreases, the quality stability index increases.

[0081] Furthermore, the quality stability index of the event flow driven model is analyzed, and the specific analysis process is: extracting the number of completed test cases and the total number of test cases of the event flow driven model from the quality test parameters of the event flow driven model, and performing ratio processing to obtain the test case completion rate of the event flow driven model; the number of completed test cases and the total number of test cases of the above-mentioned event flow driven model are extracted from the test management tool (such as test track) to which the driving device belongs; the test case completion rate of the above-mentioned event flow driven model refers to the number of completed test cases of the event flow driven model divided by the total number of test cases; the above-mentioned test case, in a specific test case in the integrated platform of Guangdong Company's Ruisi Industrial Internet Platform, is: Precondition: the test environment has been configured, including database, server, etc., and the test user account has been created; Input: correct user name and password; Expected result: successful login.

[0082] The test coverage code length of the event flow driven model is extracted from the quality test parameters of the event flow driven model, and the ratio is processed with the total code length of the event flow driven model to obtain the test code coverage rate of the event flow driven model; the test coverage code length of the event flow driven model and the total code length of the event flow driven model can be extracted from the test report generated by the test coverage tool (such as Java code coverage).

[0083] The execution time of each test case of the event flow driven model is extracted from the quality test parameters of the event flow driven model, and the average execution time of the test cases of the event flow driven model is obtained by mean processing. The quality stability index of the event flow driven model is obtained by comprehensive analysis. The execution time of each test case of the above event flow driven model can be extracted from the test report generated by the test coverage tool (such as Java code coverage).

[0084] In a specific embodiment, the present invention provides a service automation management method and system based on an event process driven model, which obtains the operating parameters of the driving device to which the event process driven model belongs and analyzes the operating stability index of the driving device to which the event process driven model belongs, thereby driving the device to accurately analyze and locate each abnormal service component of the event process driven model, and classifies each abnormal service component as an abnormality, thereby taking targeted repair measures to improve the maintenance efficiency of the event process driven model, and through quality testing of the event process driven model, ensures that high-quality operation can be maintained in various scenarios, receives quality test parameters of the event process driven model, provides data support for subsequent evaluation and optimization, and analyzes the quality stability index of the event process driven model, thereby performing quality management on the service of the event process driven model, thereby improving the operating stability of the driving device, as well as improving the operating efficiency and accuracy of the event process driven model.

[0085] Reference Figure 2 As shown, the second aspect of the present invention provides an application system such as a service automation management method based on an event process driven model, including: a driving device operation analysis module, an abnormal service component classification module, and a model service quality management module.

[0086] The second aspect of the present invention provides a system for application such as a service automation management method based on an event process driven model, which also includes an information repository, wherein the information repository is used to store the influencing factor corresponding to the unit value of the response time, the influencing factor corresponding to the unit value of the processing rate, the correction value corresponding to the average temperature increment, the performance management method corresponding to the abnormal type, the influencing factor corresponding to the unit value of the test case completion rate, the influencing factor corresponding to the unit value of the test code coverage rate, the influencing factor corresponding to the unit value of the test case average execution time, the correction factor corresponding to the average rate of memory occupation, the correction factor corresponding to the average CPU usage rate and the correction factor corresponding to the number of correctly processed tasks.

[0087] The driving device operation analysis module is respectively connected to the abnormal service component classification module, the model service quality management module and the information repository; the abnormal service component classification module is connected to the information repository; and the model service quality management module is connected to the information repository.

[0088] The driving device operation analysis module is used to obtain the operating parameters of the driving device belonging to the event process driven model through the execution of the event process driven model, analyze the operating stability index of the driving device belonging to the event process driven model, and compare it with the operating stability threshold. If the operating stability index of the driving device belonging to the event process driven model is less than the operating stability threshold, the event process driven model executes the abnormal service component classification module; conversely, if the operating stability index of the driving device belonging to the event process driven model is greater than or equal to the operating stability threshold, the event process driven model executes the model service quality management module.

[0089] The abnormal service component classification module is used to locate each abnormal service component of the event process driven model, analyze the performance abnormality index of each abnormal service component of the event process driven model, and classify each abnormal service component abnormally, thereby managing each abnormal service component of the event process driven model.

[0090] The model service quality management module is used to perform quality testing of the event process driven model, receive quality test parameters of the event process driven model, and analyze the quality stability index of the event process driven model, thereby performing quality management on the service of the event process driven model.

[0091] The above contents are merely examples and explanations of the structure of the present invention. The technicians in this technical field may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the structure of the invention or exceed the scope defined by the present invention, they should all fall within the protection scope of the present invention.

Claims

1. A service automation management method based on an event process driven model, characterized in that: include: S1. Obtain the operating parameters of the driving device to which the event process driven model belongs through the execution of the event process driven model, analyze the operating stability index of the driving device to which the event process driven model belongs, and compare it with the operating stability threshold. If the operating stability index of the driving device to which the event process driven model belongs is less than the operating stability threshold, the event process driven model executes S2. Conversely, if the operating stability index of the driving device to which the event process driven model belongs is greater than or equal to the operating stability threshold, the event process driven model executes S3. S2. Locate each abnormal service component of the event process driven model, analyze the performance abnormality index of each abnormal service component of the event process driven model, and classify each abnormal service component, thereby managing each abnormal service component of the event process driven model; S3. Through the quality test of the event process driven model, the quality test parameters of the event process driven model are received, and the quality stability index of the event process driven model is analyzed, thereby performing quality management on the service of the event process driven model.

2. The service automation management method based on the event process driven model according to claim 1 is characterized by: The operation stability index of the driving device to which the event flow driving model belongs is analyzed, and the specific analysis process is as follows: Extracting the sending time point of the execution request of the event flow driven model and the sending time point of the execution request of the event flow driven model received by the driving device from the operating parameters of the driving device to which the event flow driven model belongs, and performing difference processing to obtain the response time length of the driving device to which the event flow driven model belongs; Extract the number of request processing of the driving device in the model execution cycle from the operating parameters of the driving device belonging to the event flow driven model, perform ratio processing with the duration corresponding to the model execution cycle, and obtain the processing rate of the driving device belonging to the event flow driven model; The temperature measurement points of the driving device are located, and the temperatures of the temperature measurement points of the event flow driven model at the end time point of the model execution cycle and the temperature at the start time point of the model execution cycle are extracted from the operating parameters of the driving device belonging to the event flow driven model. The temperature increment of each temperature measurement point of the event flow driven model is obtained by difference processing, and the mean analysis is performed to obtain the average temperature increment of the driving device belonging to the event flow driven model. Based on this comprehensive analysis, the operating stability index of the driving device belonging to the event flow driven model is obtained.

3. The service automation management method based on the event process driven model according to claim 1 is characterized by: The analysis of the performance anomaly index of each abnormal service component of the event process driven model is specifically performed as follows: Obtain the amount of drive device memory of each abnormal service component of the event process driven model at the end time point of the corresponding execution processing sub-cycle and the amount of drive device memory at the start time point of the corresponding execution processing sub-cycle, perform difference processing to obtain the amount of memory occupied by each abnormal service component of the event process driven model in the corresponding execution processing sub-cycle, and perform ratio processing with the corresponding execution processing sub-cycle duration to obtain the average rate of memory occupied by each abnormal service component of the event process driven model; Collect the real-time CPU usage of the driving device of each abnormal service component of the event process driven model in the corresponding execution processing sub-cycle, and obtain the average CPU usage of each abnormal service component of the event process driven model by averaging; At the same time, the number of correctly processed tasks of each abnormal service component of the event process driven model in the corresponding execution processing sub-cycle is counted, and the performance abnormality index of each abnormal service component of the event process driven model is obtained through comprehensive analysis.

4. The service automation management method based on the event process driven model according to claim 1 is characterized by: The specific analysis process of abnormal classification of each abnormal service component is as follows: The performance anomaly index of each abnormal service component of the event process driven model is compared with the performance anomaly reference value. If the performance anomaly index of an abnormal service component is less than the performance anomaly reference value, the abnormal service component of the event process driven model is marked as a first-category abnormal service component. If the performance anomaly index of an abnormal service component is greater than or equal to the performance anomaly reference value, the abnormal service component of the event process driven model is marked as a second-category abnormal service component, thereby classifying each abnormal service component as an abnormality.

5. The service automation management method based on the event process driven model according to claim 1 is characterized by: The management of each abnormal service component of the event process driven model is carried out, and the specific analysis process is as follows: By classifying the exceptions of each abnormal service component, the exception type of each abnormal service component of the event process driven model is obtained, and then the exception types are matched with the performance management methods corresponding to the exception types stored in the information repository in turn to obtain the performance management methods corresponding to each abnormal service component of the event process driven model, thereby managing the performance of each abnormal service component of the event process driven model.

6. The service automation management method based on the event process driven model according to claim 1 is characterized by: The receiving of the quality test parameters of the event flow driven model specifically involves performing a quality test on the event flow driven model to obtain parameters of the event flow driven model during the quality test, which are recorded as the quality test parameters of the event flow driven model.

7. The service automation management method based on the event process driven model according to claim 1 is characterized by: The quality stability index of the event process driven model is analyzed in the following specific analysis process: Extracting the number of completed test cases and the total number of test cases of the event flow driven model from the quality test parameters of the event flow driven model, and performing ratio processing to obtain the test case completion rate of the event flow driven model; Extract the test coverage code length of the event flow driven model from the quality test parameters of the event flow driven model, perform ratio processing on the total code length of the event flow driven model, and obtain the test code coverage rate of the event flow driven model; The execution time of each test case of the event process driven model is extracted from the quality test parameters of the event process driven model, and the average execution time of the test cases of the event process driven model is obtained by mean processing. Based on this comprehensive analysis, the quality stability index of the event process driven model is obtained.

8. The service automation management method based on the event process driven model according to claim 7 is characterized by: The quality stability index of the event flow driven model is specifically expressed as: Among them, QI is the quality stability index of the event flow driven model, RC is the test case completion rate of the event flow driven model, FCR is the test code coverage of the event flow driven model, ERR is the average execution time of the test cases of the event flow driven model, op1 is the impact factor corresponding to the unit value of the test case completion rate preset in the information repository, op2 is the impact factor corresponding to the unit value of the test code coverage preset in the information repository, and op3 is the impact factor corresponding to the unit value of the test case average execution time preset in the information repository.

9. The service automation management method based on the event process driven model according to claim 8 is characterized by: The quality management of the service of the event process driven model is carried out, and the specific analysis process is as follows: The quality stability index of the event process driven model is compared with the quality stability threshold. If the quality stability index of the event process driven model is less than the quality stability threshold, the automated management system performs quality management on the service of the event process driven model.

10. A system using any one of claims 1 to 9, such as a service automation management method based on an event process driven model, characterized in that: include: The driving device operation analysis module is used to obtain the operation parameters of the driving device belonging to the event process driven model through the execution of the event process driven model, analyze the operation stability index of the driving device belonging to the event process driven model, and compare it with the operation stability threshold. If the operation stability index of the driving device belonging to the event process driven model is less than the operation stability threshold, the event process driven model executes the abnormal service component classification module; conversely, if the operation stability index of the driving device belonging to the event process driven model is greater than or equal to the operation stability threshold, the event process driven model executes the model service quality management module; The abnormal service component classification module is used to locate each abnormal service component of the event process driven model, analyze the performance abnormality index of each abnormal service component of the event process driven model, and classify each abnormal service component abnormally, thereby managing each abnormal service component of the event process driven model; The model service quality management module is used to receive quality test parameters of the event process driven model through quality testing of the event process driven model, analyze the quality stability index of the event process driven model, and thus perform quality management on the service of the event process driven model.