A cloud management platform micro-service scheduling method and device based on RPA technology

Abstract

This paper relates to the field of artificial intelligence technology, and in particular to a microservice scheduling method and apparatus for a cloud management platform based on RPA technology. The method includes: acquiring historical execution information of users scheduling microservices on the cloud management platform; generating an RPA application based on the historical execution information; receiving microservice scheduling requests from multiple users and verifying the legality of the microservice scheduling requests; after passing the legality verification, analyzing the permissions of the users who input the microservice scheduling requests and the microservice scheduling requests themselves to determine a minimum set of logged-in users; obtaining the login information of users in the minimum set of logged-in users from the cloud management platform; logging into the cloud management platform using the login information; and executing the corresponding RPA application according to the service scheduling requests to complete the microservice scheduling. Through this embodiment of the invention, the need to obtain the login information of the user who input the microservice scheduling request from the cloud management platform for each execution of an RPA application is avoided, thus reducing communication link overhead.

Description

Technical Field

[0001] This article relates to the field of artificial intelligence technology, and in particular to a cloud management platform microservice scheduling method and device based on RPA technology. Background Technology

[0002] Microservices (or microservice architecture) is a service-oriented software development technique and a variant of Service-Oriented Architecture (SOA). It advocates dividing a single application into a set of small services that coordinate and cooperate to deliver end-value to the user. It is a cloud-native architectural approach where a single application consists of many loosely coupled and independently deployable smaller components or services. With the maturation of microservices and Docker-related technologies, a series of open-source microservice frameworks, including Dubbo and Spring Cloud, as well as leading distributed architecture solutions based on container technology, such as Kubernetes, have emerged.

[0003] Robotic process automation (RPA) is a business process automation technology based on software robots and artificial intelligence (AI). An RPA system is an application that automates manual processes by mimicking the manual operations of end users on a computer.

[0004] With the rapid development of domestic IT innovation, the overall progress of on-premises platforms is accelerating, and the scale of applications migrating to the cloud is growing larger. This has led to the emergence of various customized, visual cloud platform management systems (hereinafter referred to as cloud management platforms) based on open-source distributed architectures and microservice frameworks. By encapsulating open-source microservice call interfaces and enabling secondary development, these systems provide operations and maintenance personnel with a relatively convenient visual interface. In large enterprises, especially financial-grade enterprise IT systems, the cloud management platform is one of their core cloud service systems, and its security and reliability are crucial aspects. Due to limitations in the cloud management platform interface and user access control, it is impossible to directly provide convenient, fast, and effective microservice resource scheduling methods. If automated development is used to implement login verification for the cloud management platform, on the one hand, the strict access control and high security level of the cloud management platform make it difficult to directly access the platform through automated parameter passing and redirection. On the other hand, even if access is possible, the relevant application itself may be non-compliant.

[0005] If the underlying framework logic is called directly without bypassing the cloud management platform, on the one hand, the underlying and encapsulated logic are inconsistent, which cannot provide a convenient solution and the program is not reusable; on the other hand, bypassing the cloud management platform to call the underlying framework logic directly increases the risk of use.

[0006] There is an urgent need for a cloud management platform microservice scheduling method based on RPA technology to solve the problems of difficulties in automated development and operation and maintenance for users, and high security risks in microservice resource scheduling in existing technologies. Summary of the Invention

[0007] To address the problems in existing technologies, this paper provides a cloud management platform microservice scheduling method and apparatus based on RPA technology. This overcomes the limitation that cloud management platforms cannot directly provide convenient, fast, and effective service resource scheduling to external users. It enables the scheduling of microservice resources on the cloud management platform through RPA technology, providing software developers, automation testers, and operations and maintenance personnel with an intuitive, convenient, secure, and effective microservice resource scheduling method, facilitating their secondary development and automated operations and maintenance.

[0008] To solve any of the above-mentioned technical problems, the specific technical solution presented in this paper is as follows:

[0009] On the one hand, this embodiment provides a microservice scheduling method for a cloud management platform based on RPA technology, including:

[0010] Obtain historical execution information when users schedule microservices on the cloud management platform;

[0011] Generate an RPA application based on the historical execution information;

[0012] Receive microservice scheduling requests from multiple users and verify the validity of the microservice scheduling requests;

[0013] After the legitimacy verification is passed, the permissions of the users who input microservice scheduling requirements and the microservice scheduling requirements are analyzed to determine the minimum set of logged-in users;

[0014] Obtain login information of users in the minimum login user set from the cloud management platform;

[0015] Log in to the cloud management platform using the login information, and execute the corresponding RPA application according to the service scheduling requirements to complete the microservice scheduling.

[0016] Furthermore, the login information includes a login password and / or a login verification code.

[0017] Furthermore, the historical execution information includes the calling parameters and calling process of the user calling the corresponding module of the microservice on the cloud management platform, and the RPA application is used to call the module on the cloud management platform;

[0018] Generating an RPA application based on the historical execution information further includes:

[0019] For one of the modules, generate the program code for each step in the calling process of that module;

[0020] The type of the calling parameters of this module shall be used as the parameter type of the program code;

[0021] The program code, including the parameter types, is integrated according to the order of each step in the calling process to obtain the RPA application of this module.

[0022] Furthermore, generating the RPA application based on the historical execution information further includes:

[0023] The number of times the module is called is determined based on the historical execution information;

[0024] If the number of calls meets a predetermined condition, the RPA application for that module is generated.

[0025] Furthermore, the microservice scheduling requirement includes the module being invoked and the corresponding parameters.

[0026] Furthermore, verifying the legitimacy of the microservice scheduling request further includes:

[0027] Verify whether the permissions of the user who inputs the microservice scheduling request match those of the module.

[0028] Furthermore, the minimum set of logged-in users is the minimum set of users who include the permissions of all modules involved in the microservice scheduling request among the users who input the microservice scheduling request.

[0029] Furthermore, logging into the cloud management platform using the login information and executing the corresponding RPA application according to the service scheduling requirements further includes:

[0030] Based on the matching relationship between the parameter type and the parameter passing type, the parameter is used as a parameter in the program code of the RPA application;

[0031] Based on the permissions of the module corresponding to the RPA application, determine the login information of the user with the required permissions from the set of minimum logged-in users;

[0032] Log in to the cloud management platform using the determined login information and execute the RPA application including the passed parameters.

[0033] Furthermore, the parameters include the operation object and the operation value.

[0034] Furthermore, before passing the parameter as an argument to the program code in the RPA application, the method further includes:

[0035] The operation values ​​of multiple users targeting the same operation object of the same module are integrated to facilitate the execution of the RPA application based on the integrated operation values.

[0036] Furthermore, before passing the parameter as a parameter to the program code in the RPA application, according to the parameter's type, the method further includes:

[0037] Detect conflicts in operation values ​​of multiple users targeting the same operation object in the same module;

[0038] In the event of a conflict, the conflicting operation values ​​are integrated according to the level of the operation object in the user's microservice scheduling requirements, so that the RPA application can be executed based on the integrated operation values.

[0039] Furthermore, the method also includes:

[0040] Analyze the user's operating habits with the module based on the user's historical execution information;

[0041] After obtaining microservice scheduling requirements from multiple users, it is determined whether the user's operating habits match the microservice scheduling requirements.

[0042] If the operation habits and microservice scheduling requirements are not met, the operation habits and microservice scheduling requirements will be sent to the user so that the user can decide whether to modify the microservice scheduling requirements according to the operation habits.

[0043] On the other hand, embodiments of the present invention also provide a cloud management platform microservice scheduling device based on RPA technology, comprising:

[0044] The historical execution information acquisition unit is used to acquire historical execution information when users schedule microservices on the cloud management platform;

[0045] An RPA application generation unit is used to generate an RPA application based on the historical execution information.

[0046] A microservice scheduling request receiving unit is used to receive microservice scheduling requests input by multiple users and verify the legality of the microservice scheduling requests;

[0047] The minimum login user set determination unit is used to analyze the permissions and microservice scheduling requirements of users who input microservice scheduling requirements after passing the legality verification, and determine the minimum login user set.

[0048] The login information acquisition unit is used to acquire the login information of users in the minimum login user set from the cloud management platform;

[0049] The microservice scheduling unit is used to log in to the cloud management platform using the login information and execute the corresponding RPA application according to the service scheduling requirements to complete the scheduling of microservices.

[0050] On the other hand, embodiments of the present invention also provide a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the above-described method.

[0051] On the other hand, embodiments of the present invention also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0052] Finally, this embodiment of the invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described method.

[0053] This embodiment transforms the manual microservice scheduling process on a cloud management platform into an automatically running RPA application. The RPA application runs on an RPA proxy server, which, after authentication by the cloud management platform, enables secure access. This solves the problem of difficulty in directly accessing the cloud management platform through automated parameter passing due to its strict access control, thus reducing the workload of manual microservice scheduling. Furthermore, since the RPA application needs to obtain user login information from the cloud management platform to execute according to the user's microservice scheduling requirements, it requires logging into the platform with the appropriate permissions and then calling the corresponding modules. To avoid frequently retrieving login information from the cloud management platform for each RPA application execution, which increases communication overhead, this embodiment analyzes the permissions of the users inputting the microservice scheduling requirements and the microservice scheduling requirements themselves to determine a minimum set of logged-in users. The login information of users in this minimum set is then obtained from the cloud management platform. The permissions of all users in this minimum set satisfy the permission requirements of all modules involved in the received microservice scheduling requirements, thus reducing communication overhead. Attached Figure Description

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

[0055] Figure 1The figure shown is a schematic diagram of an implementation system for a cloud management platform microservice scheduling method based on RPA technology in an embodiment of the present invention;

[0056] Figure 2 The diagram shown is a flowchart of a cloud management platform microservice scheduling method based on RPA technology, as described in this embodiment.

[0057] Figure 3 The diagram illustrates the process of conflict detection for microservice scheduling requirements in this embodiment.

[0058] Figure 4 The diagram illustrates the process of generating an RPA application based on the historical execution information in this embodiment.

[0059] Figure 5 The diagram illustrates the process of logging into the cloud management platform using the login information and executing the corresponding RPA application according to the service scheduling requirements in this embodiment.

[0060] Figure 6 The diagram illustrates the process of generating an RPA application based on the historical execution information in this embodiment.

[0061] Figure 7 The image shows the process of reminding users based on their operating habits in this embodiment.

[0062] Figure 8 The diagram shown is a schematic of a cloud management platform microservice scheduling device based on RPA technology according to an embodiment of this paper.

[0063] Figure 9 The diagram shown is a structural schematic of the computer device in the embodiment of this article.

[0064] [Explanation of Figure Markers]:

[0065] 101. User terminal;

[0066] 102. RPA server;

[0067] 103. Cloud Management Platform;

[0068] 801. Historical Execution Information Acquisition Unit;

[0069] 802. RPA Application Generation Unit;

[0070] 803. Microservice scheduling request receiving unit;

[0071] 804. Minimum set of logged-in users determination unit;

[0072] 805. Login Information Acquisition Unit;

[0073] 806. Microservice Scheduling Unit;

[0074] 902. Computer equipment;

[0075] 904. Processing equipment;

[0076] 906. Storage resources;

[0077] 908. Drive mechanism;

[0078] 910. Input / Output Module;

[0079] 912. Input devices;

[0080] 914. Output devices;

[0081] 916. Presentation equipment;

[0082] 918. Graphical User Interface;

[0083] 920. Network interface;

[0084] 922. Communication link;

[0085] 924. Communication bus. Detailed Implementation

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

[0087] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings herein are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0088] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application all comply with the relevant provisions of national laws and regulations.

[0089] like Figure 1The diagram illustrates an implementation system of a cloud management platform microservice scheduling method based on RPA technology, according to an embodiment of the present invention. The system includes a user terminal 101, an RPA server 102, and a cloud management platform 103. Communication between the user terminal 101 and the RPA server 102, between the user terminal 101 and the cloud management platform 103, and between the RPA server 102 and the cloud management platform 103 can occur via a network. This network can include a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, or a combination thereof, and is connected to a website, user equipment (e.g., computing devices), and a backend system.

[0090] In existing technologies, users log into cloud management platform 103 via user terminal 101 to schedule microservices. The cloud management platform microservice scheduling method based on RPA technology described in this invention can be applied to RPA server 102. RPA server 102 can obtain historical execution information when users schedule microservices on cloud management platform 103 via user terminal 101, analyze the historical execution information, generate RPA applications, and store them in the background database of RPA server 102. Subsequently, when users need to schedule microservices, they input microservice scheduling requirements to RPA server 102 via user terminal 101. RPA server 102 executes the corresponding RPA application according to the received microservice scheduling requirements to complete the microservice scheduling.

[0091] In addition, it should be noted that, Figure 1 The example shown is merely one application environment provided by this disclosure. In practical applications, other application environments may also be included, and this specification does not impose any limitations.

[0092] To address the problems existing in the prior art, this paper provides a microservice scheduling method for cloud management platforms based on RPA technology. This method overcomes the limitation that cloud management platforms cannot directly provide convenient, fast, and effective service resource scheduling to the outside world. It realizes the microservice scheduling of cloud management platforms through RPA technology, providing software developers, automation testers, and operation and maintenance personnel with an intuitive, convenient, safe, and effective microservice scheduling method, which facilitates their secondary development and automated operation and maintenance. Figure 2 The diagram illustrates a microservice scheduling method for a cloud management platform based on RPA technology, as described in this embodiment. The process of scheduling microservices on a cloud management platform using RPA technology is illustrated in the diagram. The order of steps listed in the embodiment is merely one possible execution order among many and does not represent the only possible order. In actual system or device products, the methods shown in the embodiment or the accompanying drawings can be executed sequentially or in parallel. Specifically, as shown... Figure 2As shown, the method can be executed by RPA server 102 and may include:

[0093] Step 201: Obtain historical execution information of microservices scheduled by the user on the cloud management platform;

[0094] Step 202: Generate an RPA application based on the historical execution information;

[0095] Step 203: Receive microservice scheduling requests from multiple users and verify the legality of the microservice scheduling requests;

[0096] Step 204: After passing the validity verification, analyze the permissions of the users who input microservice scheduling requirements and the microservice scheduling requirements to determine the minimum set of logged-in users;

[0097] Step 205: Obtain the login information of the users in the minimum login user set from the cloud management platform;

[0098] Step 206: Log in to the cloud management platform using the login information, and execute the corresponding RPA application according to the service scheduling requirements to complete the microservice scheduling.

[0099] This invention transforms the manual microservice scheduling process on a cloud management platform into an automatically running RPA application. The RPA application runs on an RPA proxy server, which, after authentication by the cloud management platform, enables secure access. This solves the problem of difficulty in directly accessing the cloud management platform via automated parameter passing due to its strict access control, thus reducing the workload of manual microservice scheduling. Furthermore, since the RPA application needs to obtain user login information from the cloud management platform to execute according to the user's microservice scheduling requirements, it requires logging into the platform with the appropriate permissions and then calling the corresponding modules. To avoid frequently retrieving login information from the cloud management platform for each RPA application execution, which increases communication overhead, this invention analyzes the permissions of the users inputting the microservice scheduling requirements and the microservice scheduling requirements themselves to determine a minimum set of logged-in users. The login information of users in this minimum set is then retrieved from the cloud management platform. The permissions of all users in this minimum set satisfy the permission requirements of all modules involved in the microservice scheduling requirements, thus reducing communication overhead.

[0100] In this embodiment of the invention, the cloud management platform provides comprehensive cloud resource supply, operation and maintenance, and management capabilities. It features integrated control, automated operation and maintenance, intelligent analysis, and personalized expansion. Users can log in to the cloud management platform to schedule microservices, i.e., call the corresponding modules and pass in the appropriate parameters, thereby performing integrated control or automated operation and maintenance. When a user logs in to the cloud management platform, the platform needs to verify the user's identity and whether the user has the necessary permissions to call the corresponding modules. After the user's identity verification is successful and the platform confirms that the user has the appropriate permissions, it provides the user with the modules to call.

[0101] In this embodiment of the invention, historical execution information includes the process of a user calling a module on the cloud management platform, the parameters passed in, etc. An RPA application is then generated based on this historical execution information. The functionality implemented by the RPA application is consistent with the user's process of calling the module on the cloud management platform, i.e., simulating the user's operations after logging into the cloud management platform. For example, after logging into the cloud management platform, if a user modifies the timeout of function A to 10 minutes, the module called by the user is the one for modifying the timeout, and the parameters passed in are 10 minutes and function A. The RPA server obtains the user's operation of modifying the timeout of function A to 10 minutes on the cloud management platform and then generates the RPA application based on these operations.

[0102] Then, the system receives multiple microservice scheduling requests from users. Each request includes the module to be invoked and its parameters. The request represents the function the user wants to implement. For example, User 1 wants to change the timeout of function B to 5 minutes, User 2 wants to change the timeout of function C to 10 minutes, and User 3 wants to shut down function D at a specified time. Therefore, User 1's microservice scheduling request would include the module for modifying the timeout, with parameters for function B and 5 minutes; User 2's request would include the module for modifying the timeout, with parameters for function C and 10 minutes; and User 3's request would include the module for shutting down the function, with parameters for function D and the specified time. The system then verifies the validity of these microservice scheduling requests to ensure that all microservice scheduling executed by the RPA application complies with the requirements.

[0103] According to one embodiment of the present invention, verifying the legality of the microservice scheduling request further includes:

[0104] Verify whether the permissions of the user who inputs the microservice scheduling request match those of the module.

[0105] In this embodiment of the invention, a user can only execute the corresponding RPA application when their permissions match the module being invoked. For example, only user 1 with the permission to modify the timeout can execute an RPA application that modifies the timeout. This effectively monitors user permissions and prevents unauthorized users from arbitrarily scheduling microservices, as users do not need to log in to the cloud management platform themselves.

[0106] According to one embodiment of the present invention, the parameters include an operation object and an operation value. The operation object indicates which function the user wants to configure, and the operation value indicates the value configured by the user for that object. For example, if the microservice scheduling requirement is that user 1 wants to modify the timeout of function B to 5 minutes, then the operation object is function B, and the operation value is 5 minutes.

[0107] In some other embodiments of the present invention, the microservice scheduling requirements of multiple users may target the same operation object of the same module. This could lead to redundancy or conflict between the operation values ​​of these multiple microservice scheduling requirements. If redundancy exists, such as when the operation values ​​are inclusive or overlap, the operation values ​​can be integrated, and the RPA application can be executed based on the integrated operation values, thus improving the execution efficiency of the microservice scheduling requirements.

[0108] If conflicts exist, it is necessary to perform conflict detection on the operation values ​​beforehand and handle the conflicts accordingly. Specifically, such as... Figure 3 As shown, before passing the parameter as an argument to the program code in the RPA application, the method further includes:

[0109] Step 301: Perform conflict detection on the operation values ​​of multiple users targeting the same operation object in the same module;

[0110] Step 302: In the event of a conflict, the conflicting operation values ​​are integrated according to the level of the operation object in the user's microservice scheduling requirements, so as to execute the RPA application based on the integrated operation values.

[0111] In this embodiment of the invention, conflicts may include two different operation states of the same operation object within the same time period. If a conflict exists, the conflicting operation values ​​can be integrated according to the level of the operation object in the user's microservice scheduling request. This level can be set by the user based on their own business situation when inputting the microservice scheduling request. Each user's microservice scheduling request must be set with a corresponding level when applying, such as distinguishing between routine requests, urgent requests, requests with business impact, and requests without business impact. Necessary levels are set according to specific requirement scenarios to facilitate handling when conflicts occur. For example, if a user sets a module with low business importance to a low level and a module with high business importance to a high level, and a conflict occurs, the RPA application is executed according to the parameter value corresponding to the high level, thereby ensuring that the business with high importance is protected in the event of a conflict. For example, user A needs to shut down service M from 7 PM to 9 PM, and user B needs to shut down service M from 8 PM to 9 PM, but needs to ensure that service M is on between 7:30 PM and 8 PM. At this point, it is necessary to prioritize and control the conflicting parties according to the level of the demand scenario. For routines with lower levels and little impact, they can be appropriately postponed or canceled, while for those with higher levels, they can be appropriately brought forward to achieve dynamic conflict detection.

[0112] In existing technologies, for users 1, 2, and 3 to log in to the cloud management platform to achieve the aforementioned functions, they need to enter their username and password. After logging in, the cloud management platform needs to verify whether the user has permission to call the corresponding module. Only after confirming that the user's permissions meet the requirements can the platform provide the module for the user to call. Because this invention logs into the cloud management platform by executing an RPA application, for privacy reasons, the RPA server should not store the user's login password or other information. Therefore, before executing the RPA application to call the corresponding module on the cloud management platform, it is necessary to obtain the user's password and other information from the cloud management platform, and then use the obtained password and other information to log in. When executing the RPA application, the cloud management platform also needs to determine whether the logged-in user's permissions match the called module. If the number of users issuing microservice scheduling requests is large, each time the corresponding RPA program is executed for a user's microservice scheduling request, it is necessary to obtain the user's password from the cloud management platform, increasing the overhead of the communication link and the communication pressure on the RPA server and the cloud management platform.

[0113] To address the above situation, this invention proposes a minimum set of logged-in users, taking into account the background that a user may have permissions for multiple modules. The permissions of all users in the minimum set of logged-in users can satisfy the permission requirements of all modules involved in the received microservice scheduling requests. Specifically, this invention analyzes the permissions of the user inputting the microservice scheduling request and the microservice scheduling request itself to determine the minimum set of logged-in users. Then, it obtains the login information of the users in the minimum set of logged-in users from the cloud platform. When executing the RPA application, it uses the permissions required by the modules called by the RPA application to determine the corresponding login information from the minimum set of logged-in users and uses this login information to log in to the cloud management platform. This avoids obtaining the login information of all users sending microservice scheduling requests from the cloud management platform, thereby reducing communication overhead.

[0114] According to one embodiment of the present invention, the login information includes a login password and / or a login verification code. The cloud management platform can set users to log in to the cloud management platform according to its own security needs using a login password and / or a login verification code. The RPA server can obtain the user's login password and / or login verification code according to the requirements of the cloud management platform to log in.

[0115] According to one embodiment of the present invention, the historical execution information includes the calling parameters and calling process of the user calling the corresponding module of the microservice on the cloud management platform, and the RPA application is used to call the module on the cloud management platform;

[0116] like Figure 4 As shown, generating an RPA application based on the historical execution information further includes:

[0117] Step 401: For one of the modules, generate the program code for each step in the module's calling process;

[0118] Step 402: Use the type of the calling parameter of this module as the parameter type of the program code;

[0119] Step 403: Integrate the program code including the parameter types according to the order of each step in the calling process to obtain the RPA application of the module.

[0120] In this embodiment of the invention, when a user manually invokes a module on the cloud management platform, they will input some invocation parameters. For example, if a user manually invokes the service timeout management module on the cloud management platform, they need to input parameters such as the timeout period. The RPA server uses the types of these parameters as the parameter types in the generated program code for invoking the service timeout management module. Upon receiving a user's microservice scheduling request, the RPA application invokes the corresponding module according to the request and uses the parameters in the microservice scheduling request as parameters in the program code according to the parameter types.

[0121] Specifically, such as Figure 5 As shown, logging into the cloud management platform using the login information and executing the corresponding RPA application according to the service scheduling requirements further includes:

[0122] Step 501: According to the matching relationship between the parameter type and the parameter passing type, use the parameter as a parameter in the program code of the RPA application;

[0123] Step 502: Based on the permissions of the module corresponding to the RPA application, determine the login information of the user with the required permissions from the set of minimum login users;

[0124] Step 503: Log in to the cloud management platform using the determined login information and execute the RPA application including the passed parameters.

[0125] In this embodiment of the invention, firstly, based on the matching relationship between the parameter types in the microservice scheduling requirements and the parameter types in the program code of the RPA application, the parameters are used as parameters in the program code of the RPA application. Then, it is necessary to log in to the cloud management platform. That is, based on the permissions of the corresponding module in the RPA application, the login information of the user with the required permissions is determined from the defined minimum set of login users. This login information is used to log in to the cloud management platform. After the login information is verified by the cloud management platform, the RPA application, including the parameters, is executed. The program code in the RPA application automatically calls the corresponding module, configures the module according to the parameters, and implements the corresponding functions.

[0126] It should be noted that, in this embodiment of the invention, although the user information logging into the cloud management platform is different from the user information submitting the microservice scheduling request—that is, the RPA server may use user B's login information to log into the cloud management platform to complete user A's microservice scheduling request—the user's microservice scheduling request is validated upon receipt, indicating that the user's microservice scheduling request is legitimate. Therefore, when the RPA application calls the corresponding module, even if it uses another user's login information to log into the cloud management platform, it can still complete the microservice scheduling request. The RPA server can also store the correspondence between the microservice scheduling request, the user sending the request, and the login information of the user logging into the cloud management platform, facilitating subsequent traceability.

[0127] In embodiments of the present invention, some modules may be called infrequently by users. Even if an RPA application is generated for these modules, the RPA application will be executed less frequently, but the generated RPA application still requires a certain amount of storage space. To address this situation, according to one embodiment of the present invention, such as... Figure 6 As shown, generating an RPA application based on the historical execution information further includes:

[0128] Step 601: Determine the number of times the module is called based on the historical execution information;

[0129] Step 602: If the number of calls meets the predetermined conditions, generate the RPA application for this module.

[0130] In this embodiment of the invention, before generating the RPA application, it is also determined whether the number of times the module is manually called by the user meets a predetermined condition, such as exceeding a predetermined threshold. If it meets the condition, the RPA application of the module is generated, thereby avoiding the generation of RPA applications for modules that are not frequently called and reducing the occupation of storage space.

[0131] According to one embodiment of the present invention, in order to improve user experience and prevent users from neglecting to send microservice scheduling requests, thus affecting the normal operation of services, such as... Figure 7 As shown, the method further includes:

[0132] Step 701: Analyze the user's operating habits for the module based on the user's historical execution information;

[0133] Step 702: After obtaining microservice scheduling requirements from multiple users, determine whether the user's operating habits match the microservice scheduling requirements;

[0134] Step 703: If not, the operating habits and microservice scheduling requirements are sent to the user so that the user can decide whether to modify the microservice scheduling requirements according to the operating habits.

[0135] In this embodiment of the invention, the user's operating habits can be analyzed using a model. For example, the modules that the user periodically calls can be identified. After obtaining the microservice scheduling request input by the user, it can be determined whether the user's operating habits match the microservice scheduling request. If they match, the microservice scheduling request can continue to be processed. If they do not match, it may be that the user has forgotten. Therefore, the analyzed user operating habits and the current microservice scheduling request are sent to the user to remind the user. The user can then decide whether to modify the current microservice scheduling request according to their operating habits.

[0136] Furthermore, user profiles can be built based on user history and habits to push information about potential needs. For example, a user might consistently perform relatively fixed operations on multiple microservices at fixed times on Wednesdays and Fridays. If the user subsequently stops performing these operations at the corresponding times, SMS messages can be sent to inquire about and recommend relevant actions based on the user profile and habits.

[0137] Based on the same inventive concept, this embodiment also provides a cloud management platform microservice scheduling device based on RPA technology, such as... Figure 8 As shown, it includes:

[0138] The historical execution information acquisition unit 801 is used to acquire historical execution information when users schedule microservices on the cloud management platform.

[0139] RPA application generation unit 802 is used to generate an RPA application based on the historical execution information;

[0140] The microservice scheduling request receiving unit 803 is used to receive microservice scheduling requests input by multiple users and verify the legality of the microservice scheduling requests;

[0141] The minimum login user set determination unit 804 is used to analyze the permissions and microservice scheduling requirements of the user who inputs the microservice scheduling requirements after the legality verification is passed, and to determine the minimum login user set.

[0142] The login information acquisition unit 805 is used to acquire the login information of users in the minimum login user set from the cloud management platform.

[0143] The microservice scheduling unit 806 is used to log in to the cloud management platform using the login information and execute the corresponding RPA application according to the service scheduling requirements to complete the scheduling of microservices.

[0144] Since the principle of the above-mentioned device in solving the problem is similar to that of the above-mentioned method, the implementation of the above-mentioned device can refer to the implementation of the above-mentioned method, and the repeated parts will not be described again.

[0145] like Figure 9The diagram illustrates the structure of a computer device according to an embodiment of the present invention. The apparatus in this invention can be the computer device described in this embodiment, executing the method of the present invention as described above. The computer device 902 may include one or more processing devices 904, such as one or more central processing units (CPUs), each processing unit implementing one or more hardware threads. The computer device 902 may also include any storage resource 906 for storing information of any kind, such as code, settings, data, etc. Non-limitingly, for example, the storage resource 906 may include any one or more combinations of: any type of RAM, any type of ROM, flash memory, hard disk, optical disk, etc. More generally, any storage resource can use any technology to store information. Further, any storage resource can provide volatile or non-volatile retention of information. Further, any storage resource can represent a fixed or removable component of the computer device 902. In one case, when the processing device 904 executes associated instructions stored in any storage resource or combination of storage resources, the computer device 902 can perform any operation of the associated instructions. The computer device 902 also includes one or more drive mechanisms 908 for interacting with any storage resource, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0146] Computer device 902 may also include an input / output module 910 (I / O) for receiving various inputs (via input device 912) and providing various outputs (via output device 914). A specific output mechanism may include a presentation device 916 and an associated graphical user interface (GUI) 918. In other embodiments, the input / output module 910 (I / O), input device 912, and output device 914 may be omitted, and the device may function solely as a computer device within a network. Computer device 902 may also include one or more network interfaces 920 for exchanging data with other devices via one or more communication links 922. One or more communication buses 924 couple the components described above together.

[0147] Communication link 922 can be implemented in any way, such as via a local area network (LAN), a wide area network (WAN) (e.g., the Internet), a point-to-point connection, or any combination thereof. Communication link 922 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0148] This embodiment also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0149] This embodiment also provides a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to perform the above-described method.

[0150] It should be understood that in the various embodiments of this document, the sequence number of each process 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 this document.

[0151] It should also be understood that, in the embodiments herein, the term "and / or" is merely a description of the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following associated objects have an "or" relationship.

[0152] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this document.

[0153] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0154] In the embodiments provided herein, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, devices, or units, or they may be electrical, mechanical, or other forms of connection.

[0155] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments described herein, depending on actual needs.

[0156] Furthermore, the functional units in the various embodiments of this document can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0157] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this paper, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this paper. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0158] This document uses specific embodiments to illustrate the principles and implementation methods of this document. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this document. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this document. Therefore, the content of this specification should not be construed as a limitation of this document.

Claims

1. A microservice scheduling method for a cloud management platform based on RPA technology, characterized in that, The method includes: Obtain historical execution information when users schedule microservices on the cloud management platform; Generate an RPA application based on the historical execution information; Receive microservice scheduling requests from multiple users and verify the legality of the microservice scheduling requests; After the legitimacy verification is passed, the permissions of the users who input microservice scheduling requests and the microservice scheduling requests are analyzed to determine the minimum set of logged-in users; wherein, the minimum set of logged-in users is the minimum set of users who include the permissions of all modules involved in the microservice scheduling requests among the users who input microservice scheduling requests. Obtain login information of users in the minimum login user set from the cloud management platform; Log in to the cloud management platform using the login information, and execute the corresponding RPA application according to the service scheduling requirements to complete the microservice scheduling.

2. The method according to claim 1, characterized in that, The login information includes a login password and / or a login verification code.

3. The method according to claim 1, characterized in that, The historical execution information includes the calling parameters and calling process of the user calling the corresponding module of the microservice on the cloud management platform, and the RPA application is used to call the module on the cloud management platform; Generating an RPA application based on the historical execution information further includes: For one of the modules, generate the program code for each step in the calling process of that module; The type of the calling parameters of this module shall be used as the parameter type of the program code; The program code, including the parameter types, is integrated according to the order of each step in the calling process to obtain the RPA application of this module.

4. The method according to claim 3, characterized in that, Generating an RPA application based on the historical execution information further includes: The number of times the module is called is determined based on the historical execution information; If the number of calls meets a predetermined condition, the RPA application for that module is generated.

5. The method according to claim 3, characterized in that, The microservice scheduling requirements include the modules to be invoked and the corresponding parameters.

6. The method according to claim 5, characterized in that, Verifying the legitimacy of the microservice scheduling request further includes: Verify whether the permissions of the user who inputs the microservice scheduling request match those of the module.

7. The method according to claim 6, characterized in that, Logging into the cloud management platform using the login information and executing the corresponding RPA application according to the service scheduling requirements further includes: Based on the matching relationship between the parameter type and the parameter passing type, the parameter is used as a parameter in the program code of the RPA application; Based on the permissions of the module corresponding to the RPA application, determine the login information of the user with the required permissions from the set of minimum logged-in users; Log in to the cloud management platform using the determined login information and execute the RPA application including the passed parameters.

8. The method according to claim 7, characterized in that, The parameters include the object to be operated on and the value to be operated on.

9. The method according to claim 8, characterized in that, Before passing the parameter as an argument to the program code in the RPA application, the method further includes: The operation values ​​of multiple users targeting the same operation object of the same module are integrated to facilitate the execution of the RPA application based on the integrated operation values.

10. The method according to claim 8, characterized in that, According to the type of the parameter, before passing the parameter as a parameter to the program code in the RPA application, the method further includes: Detect conflicts in operation values ​​of multiple users targeting the same operation object in the same module; In the event of a conflict, the conflicting operation values ​​are integrated according to the level of the operation object in the user's microservice scheduling requirements, so that the RPA application can be executed based on the integrated operation values.

11. The method according to claim 3, characterized in that, The method further includes: Analyze the user's operating habits with the module based on the user's historical execution information; After obtaining microservice scheduling requirements from multiple users, it is determined whether the user's operating habits match the microservice scheduling requirements. If not, the operating habits and microservice scheduling requirements will be sent to the user so that the user can decide whether to modify the microservice scheduling requirements according to the operating habits.

12. A cloud management platform microservice scheduling device based on RPA technology, characterized in that, include: The historical execution information acquisition unit is used to acquire historical execution information when users schedule microservices on the cloud management platform; An RPA application generation unit is used to generate an RPA application based on the historical execution information. A microservice scheduling request receiving unit is used to receive microservice scheduling requests input by multiple users and verify the legality of the microservice scheduling requests; The minimum login user set determination unit is used to analyze the permissions of users who input microservice scheduling requirements and the microservice scheduling requirements after the legality verification is passed, and determine the minimum login user set; wherein, the minimum login user set is the minimum set of users who include the permissions of all modules involved in the microservice scheduling requirements among the users who input microservice scheduling requirements. The login information acquisition unit is used to acquire the login information of users in the minimum login user set from the cloud management platform; The microservice scheduling unit is used to log in to the cloud management platform using the login information and execute the corresponding RPA application according to the service scheduling requirements to complete the scheduling of microservices.

13. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 11.

15. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 11.

Images