Multi-service data processing method, device, system and computer equipment

Abstract

The application relates to a multi-service data processing method, device, system and computer equipment. The method comprises the following steps: obtaining a target business process request; running a trigger type service to generate trigger type data; selecting an initial execution type service from execution type services based on an execution sequence corresponding to the target business process request, converting the trigger type data into initial standard data based on a target cloud information model, and running the initial execution type service based on the initial standard data to generate current execution service data; selecting a current execution type service from the execution type services, converting the current execution service data into current standard data based on the target cloud information model, and running the current execution type service based on the current standard data to generate target execution service data; taking the target execution service data as the current execution service data, returning to the step of selecting the current execution type service from the execution type services until a process end condition is met. The method improves the data flow efficiency between multiple different services.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to multi-service data processing methods, apparatus, systems, computer equipment, and storage media. Background Technology

[0002] With the development of computer technology, SaaS (Software-as-a-Service) emerged, which means providing software services over the network. Currently, because different enterprises have different business needs, and these business needs generally use different software services, which are often provided by different SaaS providers, data cannot be directly transferred between multiple services, requiring manual operation, which greatly reduces the work efficiency of enterprises.

[0003] Furthermore, the common practice among existing enterprises is to assign developers to create custom SaaS service connectivity solutions or directly purchase customized development services from SaaS service providers. Essentially, this involves secondary development to achieve point-to-point connections between SaaS services. While this secondary development approach offers highly targeted solutions for connecting and communicating between SaaS services and can meet customized enterprise needs, it also suffers from long development cycles, high costs, and high system complexity. Moreover, the industry and market are rapidly evolving, and enterprise needs face uncertainties. Secondary development systems lack the ability to adapt in a timely manner, resulting in low efficiency in data flow between different services or systems. Summary of the Invention

[0004] Based on this, it is necessary to provide a multi-service data processing method, apparatus, system, computer equipment, and storage medium that can enable data to flow between different services and systems, thereby improving the efficiency of data flow between multiple different services or systems.

[0005] A multi-service data processing method, the method comprising:

[0006] Obtain the target business process request, wherein the target business process request includes a triggering service and at least two execution services;

[0007] When the triggering conditions are met, the triggering class service is run to generate triggering class data;

[0008] Based on the execution order corresponding to the target business process request, an initial execution service is selected from the execution services. Based on the target cloud information model, the trigger data is converted into initial standard data applied to the initial execution service. The initial execution service runs based on the initial standard data to generate the current execution service data.

[0009] Based on the execution order, the current execution service is selected from the execution services. Based on the target cloud information model, the data of the current execution service is converted into current standard data applicable to the current execution service. The current execution service runs based on the current standard data to generate target execution service data.

[0010] The target execution service data is used as the current execution service data. The step of selecting the current execution class service from the execution class services based on the execution order is returned until the process termination condition is met, and the target execution service data corresponding to each execution class service is obtained.

[0011] In one embodiment, before obtaining a target business process request, which includes a triggering service and at least two execution services, the process further includes:

[0012] Obtain the target trigger class service and at least two target execution class services;

[0013] The target triggering service and the at least two target execution services are combined sequentially to generate an intermediate business process request;

[0014] Develop corresponding target operation rules for the intermediate business process request, and determine the target business process request.

[0015] In one embodiment, before obtaining the target triggering class service and at least two target execution class services, the method further includes:

[0016] Obtain the target trigger class service from the target service library, obtain the test trigger request parameters corresponding to the target trigger class service, perform the test based on the test trigger request parameters, and obtain the target trigger class service;

[0017] Obtain the execution class service to be tested from the target service library, obtain the forward service data, and based on the target cloud information model, convert the forward service data into standard execution data applicable to the execution class service to be tested;

[0018] Obtain the test execution request parameters corresponding to the execution class service to be tested, and test the execution class service to be tested based on the standard execution data and the test execution request parameters to obtain the target execution class service;

[0019] Return to the step of obtaining the execution class service to be tested from the target service library until the end addition condition is met, and obtain the at least two target execution class services.

[0020] In one embodiment, based on the target cloud information model, converting the triggering data into initial standard data applicable to the initial execution service includes:

[0021] Obtain the first mapping relationship between the trigger class service corresponding to the trigger class data and the target cloud information model, and obtain the second mapping relationship between the initial execution class service and the target cloud information model;

[0022] Based on the first mapping relationship and the second mapping relationship, the target cloud information model transforms the trigger class data into initial standard data applied to the initial execution class service.

[0023] In one embodiment, the method further includes:

[0024] Obtain the mapping relationship between the target service and the target cloud information model, wherein the target service includes trigger-type services and execution-type services;

[0025] Run the target service to generate target service data;

[0026] Based on the mapping relationship, the target cloud information model converts the target service data into common type data;

[0027] Store the public type data.

[0028] A multi-service data processing apparatus, the apparatus comprising:

[0029] The acquisition module is used to acquire a target business process request, wherein the target business process request includes a triggering service and at least two execution services;

[0030] The trigger module is used to run the trigger class service and generate trigger class data when the trigger conditions are met.

[0031] The initial execution module is used to select an initial execution class service from the execution class services based on the execution order corresponding to the target business process request, and convert the trigger class data into initial standard data applied to the initial execution class service based on the target cloud information model. The initial execution class service runs based on the initial standard data to generate the current execution service data.

[0032] The repetitive execution module is used to select the current execution service from the execution services based on the execution order, and convert the current execution service data into current standard data applicable to the current execution service based on the target cloud information model. The current execution service runs based on the current standard data to generate target execution service data.

[0033] The execution termination module is used to take the target execution service data as the current execution service data, return the step of selecting the current execution class service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service.

[0034] A multi-service data processing system, the system comprising:

[0035] The first server creates a corresponding target business process request by sequentially combining trigger-type services and execution-type services. The target business process request includes a trigger-type service and at least two execution services. The target business process request is then sent to the second server.

[0036] The second server includes a first server node and a second server node. The first server node is used to obtain the target business process request. When the triggering condition is met, it runs the triggering class service of the target business process request, generates triggering class data, and sends the triggering class data to the second server node.

[0037] The first server node is further configured to select an initial execution class service from the execution class services based on the execution order corresponding to the target business process request, obtain the initial standard data that has been converted from the trigger class data, the initial execution class service runs based on the initial standard data, generates current execution service data, and sends the current execution service data to the second server node;

[0038] The first server node is further configured to select the current execution class service from the execution class services based on the execution order, obtain the current standard data that the current execution class service has been converted, the current execution class service runs based on the current standard data to generate target execution service data, use the target execution service data as the current execution service data, send the current execution service data to the second server node, return the step of selecting the current execution service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service;

[0039] The second server node is used to obtain the trigger class data and the currently executed service data. Based on the target cloud information model, it converts the trigger class data into the initial standard data and the currently executed service data into the current standard data, and sends the initial standard data and the current standard data to the first server node.

[0040] In one embodiment, the second server node is further configured to obtain the mapping relationship between the target service and the target cloud information model, wherein the target service includes trigger-type services and execution-type services, obtain the target service data corresponding to the target service, and based on the mapping relationship, the target cloud information model converts the target service data into common type data and stores the common type data.

[0041] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program performing the following steps:

[0042] Obtain the target business process request, wherein the target business process request includes a triggering service and at least two execution services;

[0043] When the triggering conditions are met, the triggering class service is run to generate triggering class data;

[0044] Based on the execution order corresponding to the target business process request, an initial execution service is selected from the execution services. Based on the target cloud information model, the trigger data is converted into initial standard data applied to the initial execution service. The initial execution service runs based on the initial standard data to generate the current execution service data.

[0045] Based on the execution order, the current execution service is selected from the execution services. Based on the target cloud information model, the data of the current execution service is converted into current standard data applicable to the current execution service. The current execution service runs based on the current standard data to generate target execution service data.

[0046] The target execution service data is used as the current execution service data. The step of selecting the current execution class service from the execution class services based on the execution order is returned until the process termination condition is met, and the target execution service data corresponding to each execution class service is obtained.

[0047] A computer-readable storage medium having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0048] Obtain the target business process request, wherein the target business process request includes a triggering service and at least two execution services;

[0049] When the triggering conditions are met, the triggering class service is run to generate triggering class data;

[0050] Based on the execution order corresponding to the target business process request, an initial execution service is selected from the execution services. Based on the target cloud information model, the trigger data is converted into initial standard data applied to the initial execution service. The initial execution service runs based on the initial standard data to generate the current execution service data.

[0051] Based on the execution order, the current execution service is selected from the execution services. Based on the target cloud information model, the data of the current execution service is converted into current standard data applicable to the current execution service. The current execution service runs based on the current standard data to generate target execution service data.

[0052] The target execution service data is used as the current execution service data. The step of selecting the current execution class service from the execution class services based on the execution order is returned until the process termination condition is met, and the target execution service data corresponding to each execution class service is obtained.

[0053] The aforementioned multi-service data processing method, apparatus, system, computer equipment, and storage medium, by acquiring a target business process request, wherein the target business process request includes a triggering service and at least two execution services; when a triggering condition is met, the triggering service is run to generate triggering data; based on the execution order corresponding to the target business process request, an initial execution service is selected from the execution services; based on a target cloud information model, the triggering data is converted into initial standard data applicable to the initial execution service; the initial execution service runs based on the initial standard data to generate current execution service data; based on the execution order, a current execution service is selected from the execution services; based on the target cloud information model, the current execution service data is converted into current standard data applicable to the current execution service; the current execution service runs based on the current standard data to generate target execution service data; the target execution service data is used as the current execution service data, and the step of selecting the current execution service based on the execution order is returned until the process termination condition is met, thereby obtaining target execution service data corresponding to each execution service. The system considers two target business process requests with fewer execution-type services. When a triggering condition is met, the triggering service is executed, generating triggering data. Based on the execution order of the target business process request, an initial execution-type service is selected from the execution-type services. The triggering data is then transformed into initial standard data applicable to the initial execution-type service based on the target cloud information model. The initial execution-type service can then run according to the initial standard data, generating current execution service data. This process is repeated iteratively, selecting the current execution-type service based on the execution order, and transforming the current execution service data into current standard data applicable to the current execution-type service based on the target cloud information model. The current execution-type service then runs according to the current standard data, generating target execution service data. This process is iterated until the process conditions are met, ensuring that each execution-type service has generated corresponding target execution service data. Through the target cloud information model, data standardization is achieved for different types of triggering and execution services, enabling the flow of data generated by the execution of triggering and execution services, and execution services, and automating the execution of various services in the target business process request. This improves the efficiency of data flow between multiple different services. Attached Figure Description

[0054] Figure 1 This is an application environment diagram of a multi-service data processing method in one embodiment;

[0055] Figure 2 This is a flowchart illustrating a multi-service data processing method in one embodiment;

[0056] Figure 3 This is a flowchart illustrating the creation of a target business process request in one embodiment;

[0057] Figure 4 This is a flowchart illustrating the service testing process in one embodiment;

[0058] Figure 5 This is a schematic diagram of the process that triggers class data conversion in one embodiment;

[0059] Figure 6 This is a schematic diagram of the data conversion and storage process in one embodiment;

[0060] Figure 7 This is an application environment diagram of a multi-service data processing system in one embodiment;

[0061] Figure 8 This is a schematic diagram of a SaaS service integration platform in one embodiment;

[0062] Figure 9 This is a flowchart illustrating the creation of a business process in one embodiment;

[0063] Figure 10 This is a flowchart illustrating the process of initiating a business process in one embodiment;

[0064] Figure 11 This is a schematic diagram of a CIM model in one embodiment;

[0065] Figure 12 This is a structural block diagram of a multi-service data processing device in one embodiment;

[0066] Figure 13 This is an internal structural diagram of a computer device in one embodiment;

[0067] Figure 14 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0068] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0069] The multi-service data processing method provided in this application embodiment can be applied to, for example... Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or located in the cloud or on another network server. Terminal 102 is used to send user requests and input related data. Server 104 is used to acquire target business process requests, which include triggering services and at least two execution services. When the triggering conditions are met, the triggering services are run to generate triggering data. Based on the execution order corresponding to the target business process request, an initial execution service is selected from the execution services. Based on the target cloud information model, the triggering data is converted into initial standard data applicable to the initial execution service. The initial execution service runs based on the initial standard data to generate current execution service data. Based on the execution order, the current execution service is selected from the execution services. Based on the target cloud information model, the current execution service data is converted into current standard data applicable to the current execution service. The current execution service runs based on the current standard data to generate target execution service data. The target execution service data is used as the current execution service data, and the steps of selecting the current execution service from the execution services based on the execution order are returned until the process termination conditions are met, thus obtaining the target execution service data corresponding to each execution service. The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. Server 104 can be implemented using a standalone server or a server cluster composed of multiple servers.

[0070] In one embodiment, such as Figure 2 As shown, a multi-service data processing method is provided, which can be applied to... Figure 1 Taking the server in the example, the following steps are included:

[0071] Step S200: Obtain the target business process request. The target business process request includes a triggering service and at least two execution services.

[0072] Among them, target business process requests refer to the execution requests of various services used by users to achieve certain business requirements, and the execution of these services has corresponding operating rules, which are customized and configured by the user. Triggering services refer to services used to trigger target business process requests. Execution services refer to services used to achieve certain business requirements, such as WeChat Work and Kingsoft Docs. Triggering and execution services can be understood using the scenario of "pushing approved purchase orders to WeChat by supplier" as an example. In this scenario, the triggering service retrieves the purchase order data when the purchase order from the specified supplier has been approved; the execution service has two parts: converting the purchase order data into Kingsoft online documents, and then pushing the online document link to the user through a WeChat official account.

[0073] Specifically, each user can select the corresponding triggering service and execution service according to their own needs to construct the corresponding target business process request, which can then be used to realize the user's corresponding needs.

[0074] Step S202: When the triggering conditions are met, run the triggering class service and generate triggering class data.

[0075] The triggering condition refers to the condition that triggers the execution of the target business process request. Trigger-type data refers to the data obtained after executing the corresponding trigger-type service. For example, in the scenario where the trigger-type service is "when a purchase order from a specified supplier has been approved, retrieve the purchase order data," the trigger-type data would include the purchase order data.

[0076] Specifically, each user has different business needs, resulting in different business trigger points. By executing the user's corresponding trigger service, trigger data corresponding to the trigger service in the target business process request is obtained. This trigger data is then used to execute subsequent execution services. However, successful execution of the trigger service requires certain triggering conditions to be met. These conditions may include the web API request calling the trigger service not containing error messages. Once the corresponding triggering conditions are met, the trigger service can be used to generate the corresponding trigger data. If the triggering conditions are not met, the request is repeatedly initiated until the corresponding request is error-free. To avoid such problems, corresponding testing is performed before creating the user's corresponding business process request to improve the operational efficiency between various services. These services include trigger services and execution services.

[0077] Step S204: Based on the execution order corresponding to the target business process request, select the initial execution class service from the execution class services. Based on the target cloud information model, convert the trigger class data into initial standard data applied to the initial execution class service. The initial execution class service runs based on the initial standard data to generate the current execution service data.

[0078] The execution order refers to the order in which triggering services and execution services are executed in the target business process request when fulfilling the user's corresponding business needs. This includes corresponding timing rules, such as executing the corresponding execution service every 10 minutes. The initial execution service is the first execution service in the execution order corresponding to the target business process request. The target cloud information model refers to the CIM (Cloud Information Model), which can be used to unify service integration data standards. Initial standard data refers to data that has been converted from triggering data to data types compatible with the initial execution service. Current execution service data refers to the data generated when executing the corresponding execution service; this data retains the data format corresponding to the execution service data. Here, current execution service data refers to the data generated when running the initial execution service.

[0079] Specifically, the target business process requests have their corresponding execution order, which controls which services data flows between. Trigger data generated by the triggering service needs to be applied to the initial execution service. However, since the data format of the trigger data may differ from that of the initial execution service, the trigger data needs to be converted into initial standard data that is compatible with the data type of the initial execution service and can be applied to that service through the target cloud information model. Only then can the initial execution service perform corresponding operations based on the initial standard data and generate the corresponding current execution service data, thereby realizing the data flow between the triggering service and the execution service.

[0080] Step S206: Based on the execution order, select the current execution service from the execution services. Based on the target cloud information model, convert the current execution service data into current standard data applicable to the current execution service. The current execution service runs based on the current standard data to generate target execution service data.

[0081] Here, "current execution service" refers to the execution service being executed at the current time point. "Current standard data" refers to data that has been converted from the current execution service data into a data format compatible with the current execution service and can be directly applied to it. "Target execution service data" refers to the data generated by executing the current execution service data; this data still retains the data format corresponding to the current execution service and has not yet undergone any data conversion operations.

[0082] Specifically, the target business process request may contain multiple execution services, each with its own execution order. Based on this order, the current execution service is selected sequentially from these services. Then, according to the target cloud information model, the current execution service data from the previous step is converted into standard data that matches the current execution service's data format. This standard data can then be used directly for relevant execution operations, such as data manipulation, approval, and notification. This generates the target execution service data for the current execution service. If further execution services need to be run, the target execution service data undergoes further data conversion to enable the operation of subsequent execution services and generate the corresponding target execution service data.

[0083] Step S208: Take the target execution service data as the current execution service data, return the steps of selecting the current execution class service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service.

[0084] The process termination condition can be either receiving a process termination signal corresponding to the target business process request, or the execution-type service in the target business process request has been completed.

[0085] Specifically, there can be multiple execution-type services. When there are multiple execution-type services corresponding to the target business process request, the data generated by the execution-type service corresponding to the previous step will serve as the input data required for the execution-type service corresponding to the next step. Therefore, the target execution service data is used as the current execution service data, providing the data foundation for the next current execution-type service to be selected, so as to realize the execution of the next current execution-type service. This achieves the sequential execution of execution-type services in the target business process request until the corresponding process end signal is received or the execution-type service in the target business process request has been completed, that is, the corresponding process end condition is met. Then, the target execution service data corresponding to each execution-type service is obtained, realizing the data flow between these multiple different execution-type services.

[0086] Furthermore, in one embodiment, the target business process request may also include a triggering service and an execution service, enabling the execution operation corresponding to the target business process request and the data flow between the triggering service and the execution service. That is, when the corresponding triggering condition is met, the execution operation corresponding to the triggering service is automatically triggered, i.e., the triggering service is automatically run, thereby generating triggering data corresponding to the triggering service. Then, based on the target cloud information model, this triggering service data is converted into data that is compatible with the data format corresponding to the execution service and can be directly applied to the execution service. The execution service then performs corresponding operations based on this converted data to generate the corresponding target execution service data, thus realizing the data flow from the triggering service to the execution service.

[0087] The aforementioned multi-service data processing method involves acquiring a target business process request that includes a triggering service and at least two execution services, running the triggering service to generate triggering data, selecting an initial execution service from the execution services based on the execution order of the target business process request, and converting the triggering data into initial standard data applicable to the initial execution service based on the target cloud information model. The initial execution service can then run according to the initial standard data to generate current execution service data. Again, based on the execution order, the current execution service is selected from the execution services, and the current execution service data is converted into data applicable to the current execution service based on the target cloud information model. The current standard data of the service is used to run the current execution service based on the current standard data, generate target execution service data, and repeatedly iterate to select the operation of the current execution service from the execution services based on the execution order until the process conditions are met, so that each execution service has generated the corresponding target execution service data. Through the target cloud information model, the data of different types of trigger services and execution services is standardized, realizing the flow of execution data between trigger services and execution services, and between execution services, and realizing the automated execution of various services in the target business process request, thereby improving the efficiency of data flow between multiple different services.

[0088] In one embodiment, such as Figure 3 As shown, before step S200, the following steps are also included:

[0089] Step S300: Obtain the target trigger class service and at least two target execution class services.

[0090] Among them, target triggering services refer to triggering services that have been authorized and passed testing. Target execution services refer to execution services that have been authorized and passed testing.

[0091] Specifically, users can obtain the corresponding target triggering services and target execution services according to their own needs. Both target triggering services and target execution services have passed security certification and undergone corresponding testing, and can be directly applied to the creation of the user's corresponding business processes.

[0092] Step S302: Combine the target triggering service and at least two target execution services in sequence to generate an intermediate business process request.

[0093] Among them, intermediate business process requests refer to business process requests for which further operation rules have not yet been configured for the business process requests obtained from the initial combination of triggering services and execution services.

[0094] Specifically, when creating a business process request, it is necessary to combine the triggering services and execution services according to the order in which they are added. The triggering services can be regarded as trigger nodes and the execution services as execution nodes, thus forming an initial execution process that can realize the user's corresponding business scenario, which is the implementation operation corresponding to the intermediate business process request.

[0095] Step S304: Formulate corresponding target operation rules for intermediate business process requests and determine the target business process requests.

[0096] Among them, the target execution rules refer to the configuration of rules for the scheduled execution of intermediate business processes, and these rules are user-defined.

[0097] Specifically, to more flexibly and effectively meet user business needs, users can define corresponding target execution rules to automatically execute multiple services and achieve better and more efficient data flow between them, thereby better fulfilling user business requirements. These target execution rules for intermediate business process requests can be executed at fixed intervals, such as once a day at 9:00 AM or once a week at 5:00 PM. Furthermore, these target execution rules can be CRON expression strings, such as "0 0 10**?" indicating execution once a day at 10:00 AM.

[0098] In this embodiment, by acquiring a target triggering service and at least two target execution services, and then combining the target triggering service and the at least two target execution services in sequence to generate an intermediate business process request, and by formulating corresponding target execution rules for the intermediate business process request, the target business process request is determined, thereby realizing the creation of the target business process request, improving the efficiency of business process creation, and formulating corresponding target execution rules, which is conducive to the automated execution of the operation corresponding to the target business process request, thereby ensuring the efficiency of sequential execution between different services to a certain extent.

[0099] In one embodiment, such as Figure 4 As shown, before step S300, the following steps are also included:

[0100] Step S400: Obtain the trigger class service to be tested from the target service library, obtain the test trigger request parameters corresponding to the trigger class service to be tested, perform the test based on the test trigger request parameters, and obtain the target trigger class service.

[0101] The target service repository refers to a repository used to integrate and provide services corresponding to SaaS products. These SaaS products can be Kingdee Cloud Starry Sky, WeChat Work, Kingsoft Docs, etc. All integrated services can be divided into two categories: trigger-type services and execution-type services. Trigger-type services to be tested refer to authorized trigger-type services that have not yet been tested. Test trigger request parameters refer to parameters used to test trigger-type services. These can be request parameters for the trigger-type service, such as API request parameters. For example, trigger-type service A accesses a web API at regular intervals, such as querying whether there are new orders in the sales system within 5 minutes before the current time. Here, the test trigger request parameter is the time parameter, meaning the time range is from 5 minutes before the current time to the current time. The target trigger-type service refers to the trigger-type service that has been authorized and whose request parameters are tested, resulting in a successful test.

[0102] Specifically, the target service library integrates services provided by different SaaS products. When users want to apply corresponding services to achieve their business needs, they can obtain these third-party services through the target service library. After obtaining these services and applying them, authorization is granted to ensure that the applied services are securely authenticated. These securely authenticated services are then used as trigger services for testing. Furthermore, to better avoid issues such as call failures during the execution of the corresponding trigger services, appropriate testing can be performed before creating the corresponding business process request. If the test trigger request parameters of the trigger service are API request parameters, their format needs to be converted to conform to the parameter specifications of the trigger service. To determine test success, the results obtained from the trigger service request can be analyzed. Typically, web API response parameters carry error codes and error messages. Success or failure is determined by judging these error codes or messages; generally, an error code of 0 indicates a successful test, otherwise, the test is considered unsuccessful. If the test fails, you can request the API again. However, in general, the data will not be changed. Only parameters related to the current time will be changed. For example, in the example of "querying whether there are any new orders in the sales system within 5 minutes before the current time", if the test fails in this scenario and is tested again after 3 minutes, the time zone corresponding to the current time has changed. Therefore, the original time parameter cannot be used as the time parameter of the current time.

[0103] Step S402: Obtain the execution class service to be tested from the target service library, obtain the forward service data, and convert the forward service data into standard execution data applicable to the execution class service to be tested based on the target cloud information model.

[0104] Among them, "Execution-Class Services to be Tested" refers to execution-class services that have been authorized but not yet tested. "Forward Service Data" refers to data generated by the service executed in the previous step corresponding to the current execution step; this service can be a triggering service or an execution service. "Standard Execution Data" refers to data that has been converted from forward service data into a format compatible with the intermediate execution-class service and applicable to that service.

[0105] Specifically, the different SaaS products integrated in the target service library also provide execution services that implement various functionalities. Users can select execution services from the target service library according to their needs and perform security authentication on the selected execution services. Furthermore, to improve the success rate of the final generated business process, the selected execution services can be tested. During testing, some corresponding parameter information can be obtained. This parameter information can be the data generated when executing the corresponding service (trigger service or execution service) in the previous step, i.e., the forward service data. Because the data formats of the forward service data differ, the data format of the forward service data can be converted into the data format corresponding to the execution service under test through the target cloud information model, i.e., converted into standard execution data. This standard execution data can be directly applied to the execution service under test.

[0106] Step S404: Obtain the test execution request parameters corresponding to the execution class service to be tested, and test the execution class service to be tested based on the standard execution data and the test execution request parameters to obtain the target execution class service.

[0107] Among them, the test execution request parameters refer to the request parameters corresponding to the execution class service. These request parameters can be parameters of the API request, data manually entered by the user terminal, or a mixture of API request parameters and manually entered data.

[0108] Specifically, when calling and testing an execution-type service, testing can be performed using parameters corresponding to that service. These parameters can be standard execution data generated during the previous step's execution of the corresponding service (trigger service or execution service), test execution request parameters, or a combination of both. The testing process for execution-type services is similar to that for trigger services: requesting a web API. If the test succeeds, this intermediate execution service is used as the target execution service to create the target business process request. If the test fails, the corresponding API is requested again, without changing other data unrelated to the current time, until the test succeeds.

[0109] Step S406: Return to the step of obtaining the execution class service to be tested from the target service library until the end addition condition is met, and at least two target execution class services are obtained.

[0110] Among them, the termination condition refers to the condition used to restrict the continued creation of business processes, which can be the receipt of a signal from the user terminal to terminate the addition execution class service.

[0111] Specifically, when adding execution-type services to the target business process request, security authentication and testing operations can be performed on the execution-type services. Because the data used for testing the currently added execution-type service may use the data obtained from testing the execution-type service added in the previous step, multiple execution-type services cannot be added in parallel. Users can add corresponding execution-type services according to their business needs until the corresponding end-add signal is received, that is, the end-add condition is met. At least two target execution-type services can then be identified, and these target execution-type services can be directly applied to the creation of the target business process.

[0112] In this embodiment, the process involves obtaining a trigger service to be tested from the target service library, acquiring the corresponding test trigger request parameters, performing tests based on the test trigger request parameters, and obtaining the target trigger service. Then, the process continues with obtaining an execution service to be tested from the target service library, acquiring forward service data, converting the forward service data into standard execution data applicable to the execution service to be tested based on the target cloud information model, acquiring the corresponding test execution request parameters, and performing tests based on the standard execution data and test execution request parameters to obtain the target execution service. The process then returns to the step of obtaining the execution service to be tested from the target service library, repeating until the end-addition condition is met, resulting in at least two target execution services. This implements the testing operations for trigger services and execution services, ensuring the security of trigger service and execution service calls and the stability of the final target business process request. This improves the success rate of target business process request execution and, to a certain extent, facilitates smooth data flow between services, thereby improving the corresponding data flow efficiency.

[0113] In one embodiment, such as Figure 5 As shown, step S204 includes:

[0114] Step S500: Obtain the first mapping relationship between the trigger class service corresponding to the trigger class data and the target cloud information model, and obtain the second mapping relationship between the initial execution class service and the target cloud information model.

[0115] The first mapping relationship refers to the mapping relationship between the data fields corresponding to the triggering service and the target cloud information model. The second mapping relationship refers to the mapping relationship between the data fields corresponding to the initial execution service and the target cloud information model.

[0116] Specifically, the target cloud information model can be a CIM model. The CIM model can be used to unify data standards for service integration. When a new SaaS product is added to the target service library, a mapping relationship between the service corresponding to that new product and the target cloud information model is configured, enabling the service corresponding to the new product to quickly connect with the services corresponding to other SaaS products. Here, to achieve rapid connection between trigger-type services and initial execution-type services, it is necessary to obtain a first mapping relationship and a second mapping relationship so that the target cloud information model can connect the trigger-type service and the initial execution-type service data through the first and second mapping relationships.

[0117] In step S502, based on the first mapping relationship and the second mapping relationship, the target cloud information model transforms the trigger class data into initial standard data applied to the initial execution class service.

[0118] Specifically, the target cloud information model converts the triggering data into corresponding CIM (Cloud Information Model) data according to the first mapping relationship. This CIM data can be regarded as a common data format, and the CIM data corresponding to the triggering service is saved. When the corresponding initial execution service needs to use the data corresponding to the triggering service, the target cloud information model converts the CIM data corresponding to the triggering service into initial standard data that is compatible with the data format corresponding to the initial execution service according to the second mapping relationship. This realizes the conversion from triggering data to initial standard data, that is, the flow of triggering service data to initial execution service data.

[0119] In this embodiment, by obtaining the first mapping relationship between the triggering service corresponding to the triggering data and the target cloud information model, and obtaining the second mapping relationship between the initial execution service and the target cloud information model, the target cloud information model converts the triggering data into initial standard data applied to the initial execution service, realizing the data flow between the triggering service and the initial service, providing a data foundation for the operation of subsequent execution services, thereby facilitating the continued operation of subsequent execution services.

[0120] In one embodiment, such as Figure 6 As shown, it also includes:

[0121] Step S600: Obtain the mapping relationship between the target service and the target cloud information model. The target service includes trigger-type services and execution-type services.

[0122] Here, the target service refers to the service currently running, which can be a trigger-type service or an execution-type service. The mapping relationship refers to the mapping relationship between the data fields of the target service and the corresponding target cloud information model.

[0123] Specifically, each service is configured with a mapping relationship with the target cloud information model when it is added to the target service library. Subsequently, the data obtained by the target service is converted into CIM data through this mapping relationship and the corresponding CIM data of the target service is stored so that when the CIM data is needed in the corresponding operation, it can be directly obtained and the corresponding data conversion can be performed, thereby improving the efficiency of data flow between services.

[0124] Step S602: Run the target service and generate target service data.

[0125] Among them, target service data refers to the data generated when the corresponding target service is executed. The data format of this data is consistent with the data format of the target service and has not yet been converted.

[0126] Specifically, each service generates corresponding data after it runs, and this data is also applied to the services of subsequent processes. This target service data provides the data foundation for the execution of services in subsequent processes. The services mentioned here can be trigger-type services or execution-type services, and the specific type of service is determined by the specific service being executed.

[0127] Step S604: Based on the mapping relationship, the target cloud information model converts the target service data into common type data.

[0128] Among them, public type data can be CIM data, which can be regarded as a public data format.

[0129] Specifically, each target service has a pre-defined field mapping relationship with the target cloud information model. Therefore, the target service data generated by the target service can be converted into the corresponding common type data, i.e., CIM data, through the target cloud information model. Subsequent target services can also convert their corresponding target service data into their required data format based on the pre-defined mapping relationship with the target cloud information model. More specifically, the data format and fields obtained from services (which can be trigger-type services or execution-type services) are usually inconsistent. Assuming there are N services, each of which has established a field mapping relationship with the target cloud information model, the data of service A, after being converted by the target cloud information model, can be used by the other N-1 services, with an integration complexity of O(N). If the data is not converted through the target cloud information model, a mapping relationship needs to be established between each service, resulting in an integration complexity of O(N^2), which makes the data flow efficiency between services low.

[0130] Step S606: Store common type data.

[0131] Specifically, after the data obtained from the execution of each target service is converted into corresponding common type data by the target cloud information model, this data needs to be stored so that when the target service needs to use the corresponding data in subsequent executions, it can directly convert the corresponding common type data into the data format corresponding to the target service based on the mapping relationship between the target service and the target cloud information model, thereby improving the execution efficiency between target services.

[0132] In this embodiment, by obtaining the mapping relationship between the target service and the target cloud information model, the target service includes trigger-type services and execution-type services. Running the target service generates target service data. Based on the mapping relationship, the target cloud information model converts the target service data into common type data and stores the common type data, thus realizing the initial data conversion. Converting the target service data into the corresponding common type data is beneficial to improving the conversion efficiency of data between services, thereby improving the flow efficiency of data between multiple services.

[0133] In one embodiment, a multi-service data processing system is provided, which is applied to Figure 7 The application environment shown, in which Figure 7 In the diagram, 700 can represent a terminal, 702 can represent a first server, 704 can represent a second server, 704A and 704B represent the first server node and the second server node, respectively. The second server 704 includes, but is not limited to, the first server node 704A and the second server node 704B shown in the diagram. The first server 702 and the second server 704 can be implemented using independent servers or a server cluster composed of multiple servers. The system includes:

[0134] The first server creates a corresponding target business process request by sequentially combining trigger-type services and execution-type services. The target business process request includes a trigger-type service and at least two execution-type services, and then sends the target business process request to the second server.

[0135] Specifically, the first server receives a creation request for the user's target business process. The user creates a business process that can execute multiple services according to their business needs. The first server then obtains the triggering or execution services authorized by the third-party service library according to the user's needs, and creates the corresponding target business process request. This target business process request is configured with user-defined running rules. When the operation corresponding to the target business process request needs to be executed, the target business process request is sent to the second server. If the execution of the operation corresponding to the target business process request needs to be terminated during the execution of the operation, a process termination signal can be sent to the second server to terminate the execution of the process. The execution status of the operation corresponding to the specific target business process request can be controlled by the first server.

[0136] The second server includes a first server node and a second server node. The first server node is used to obtain the target business process request. When the triggering condition is met, it runs the triggering class service of the target business process request, generates triggering class data, and sends the triggering class data to the second server node.

[0137] Specifically, the second server may include a first server node and a second server node, each with its own specific function. The first server node primarily performs the relevant execution tasks for the operations corresponding to the target business process request. When the corresponding triggering conditions are met, it automatically runs the trigger-type service, generates trigger-type data, and sends the trigger-type data to the second server node. The second server node primarily performs the conversion of data generated between services and stores this converted data.

[0138] The first server node is also used to select an initial execution class service from the execution class services based on the execution order corresponding to the target business process request, obtain the initial standard data that has been converted from the trigger class data, run the initial execution class service based on the initial standard data, generate the current execution service data, and send the current execution service data to the second server node.

[0139] Specifically, the first server node can also select an initial execution class service from the execution class services according to the execution order corresponding to the target business process request, so as to realize the data flow between the trigger class service and the initial execution class service. To this end, the first server node obtains the initial standard data that has been converted by the second server node into a data format that is compatible with the data format corresponding to the initial execution class service and can be directly applied to the initial execution class service. Then, the initial execution class service performs the corresponding execution operation according to the initial standard data, generates the current execution service data, and sends the current execution service data to the second server node to realize the data conversion of the current execution service data, thereby promoting the data flow between subsequent execution class services and demonstrating the data interaction between server nodes.

[0140] The first server node is also used to select the current execution class service from the execution class services based on the execution order, obtain the current standard data that the current execution class service has been converted, run the current execution class service based on the current standard data, generate target execution service data, use the target execution service data as the current execution service data, send the current execution service data to the second server node, return the steps of selecting the current execution service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service.

[0141] Specifically, a target business process request may correspond to multiple execution-type services. To achieve the sequential execution of these services, the current execution-type service needs to be selected based on the execution order of the target business process request. Then, the data of the current execution-type service is converted into standard data that matches the data format of the current execution-type service and can be directly applied to it, via a second server node. The current execution-type service then performs its corresponding operations based on the standard data and generates its corresponding target execution-type service data. To achieve orderly iterative execution of multiple execution-type services, this target execution-type service data is used as the current execution-type service data, providing a targeted data foundation for the execution of subsequent execution-type services. Furthermore, the data generated after the execution of each execution-type service needs to be sent to the second server node for data conversion and storage to improve the execution efficiency between services, i.e., to achieve efficient data flow between services. During the execution of services on the first server node, a process termination signal may be received from the first server. When the corresponding process termination signal is received, the process termination condition is met, and the execution of related operations is terminated. In addition, when the execution of the execution class service corresponding to the target business process request is completed, the process termination condition is also met, thereby obtaining the target execution service data corresponding to each execution class service, realizing the data flow between trigger class services and execution class services, and between execution class services.

[0142] The second server node is used to obtain trigger-type data and currently executed service data. Based on the target cloud information model, it converts the trigger-type data into initial standard data and the currently executed service data into current standard data, and then sends the initial standard data and current standard data to the first server node.

[0143] Specifically, the first server node acquires data generated by the execution of various services (which can be trigger-type services or execution-type services). Then, based on the mapping relationship between these services and the target cloud information model, it converts the data corresponding to these services into data formats corresponding to other services, thereby enabling data flow between multiple different services. In this embodiment, the second server node acquires trigger-type data and currently executing service data. It first converts this data into CIM data according to the target cloud information model. This CIM data can be considered a common data format. Then, based on the mapping relationship between the currently running service and the target cloud information model, it performs further data conversion. Here, the second server node first converts the trigger-type data into corresponding CIM data based on the mapping relationship between the trigger-type service and the target cloud information model. Then, based on the initial mapping relationship between the execution-type service and the target cloud information model, it converts the CIM data corresponding to the trigger-type data into initial standard data. The conversion of the currently executing service data into current standard data is done in the same way. Finally, the converted initial standard data and current standard data are sent to the first server node, thereby realizing data flow between services and data interaction between server nodes.

[0144] In addition, in one embodiment, the target business process request may also include a triggering service and an execution service. The first server mainly performs the relevant operations corresponding to the creation of the target business process request and controls the sending of execution and termination signals of the business process request. The second server mainly performs the operations corresponding to the target business process request, realizes the flow of data between different services and the storage service generated data, realizes data conversion. The servers perform their respective functions and cooperate with each other, realizing the interaction of data between servers, the interaction of data between server nodes and the interaction of data between different services, thereby improving the efficiency of data flow between various different services. That is, it realizes the efficient flow of data between the triggering service and the execution service. The above services include the triggering service and the execution service.

[0145] The aforementioned multi-service data processing system uses a first server to sequentially combine trigger-type services and execution-type services to create a corresponding target business process request. The target business process request includes a trigger-type service and at least two execution-type services. The target business process request is then sent to a second server, which executes the corresponding operations of each service in the target business process request and realizes data interaction between server nodes. This enables data interaction between servers, between multiple services, and between server nodes, significantly improving the efficiency of data flow between multiple different services.

[0146] In one embodiment, the second server node is also used to create a mapping relationship between the target service and the target cloud information model. The target service includes trigger-type services and execution-type services. The target service data corresponding to the target service is obtained. Based on the mapping relationship, the target cloud information model converts the target service data into common type data and stores the common type data.

[0147] Specifically, the second server node implements the conversion and storage of data between services. Whenever a new service is added to the target service library, the second server node configures the mapping relationship between the new service and the target cloud information model. Furthermore, in this embodiment, the target service refers to the service corresponding to the current execution process. This service can be a trigger-type service or an execution-type service. When the target service generates corresponding target service data through the execution of the first server node, the second server node obtains the target service data and then obtains the mapping relationship between the target service and the target cloud information model. Based on this mapping relationship, the target cloud information model converts the target service data into corresponding CIM data, i.e., common type data, and stores this common type data. This allows subsequent service execution processes to directly obtain the corresponding common type data and perform the appropriate data conversion, greatly improving the efficiency of data conversion between services and thus improving the execution efficiency between services.

[0148] In this embodiment, the conversion and storage of data between services are realized through the second server node, which to a certain extent helps to improve the conversion of data formats between services, thereby improving the execution efficiency between services, and thus facilitating efficient interaction of data between servers, between server nodes, and between multiple services.

[0149] In one embodiment, Figure 8 This is a schematic diagram illustrating the principle of a specific example of a SaaS service integration platform. Service integration refers to connecting different services, enabling systems within an enterprise that cannot communicate to form a new system, thus breaking down data silos between them. Figure 8 The external system module provides external users with ways to use or invoke the functions of this integration platform, including client access and API interface access; the SaaS service integration center module includes, but is not limited to, [other methods]. Figure 8The platform showcases four sub-modules: SaaS Service Library, Security Authentication, Process Management, and Scheduled Tasks. The SaaS Service Library module integrates services provided by SaaS products, such as Kingdee Cloud Starry Sky, WeChat Work, and Kingsoft Docs. In this integration platform, services in the SaaS Service Library are categorized into trigger-based and execution-based services. The Security Authentication module authorizes third-party services in the SaaS Service Library, providing authorization methods such as OAuth2.0, Auth Code, BasicAuth, and WebHook. The Process Management module manages business processes, supporting operations such as process testing, creation, and execution, including creating, testing, starting, and closing business processes. The Scheduled Tasks module automatically runs business processes and supports customizable process execution rules. The Data Unification Standards module handles data conversion between services, transforming service-generated data into CIM data or other service-specific data formats. It provides a common data model for different business domains, namely CIM (Cloud Information Modeling). The business system module is used to request services from the SaaS service library, that is, to execute the corresponding business process. It can acquire and process data. In addition, an automated business process usually consists of 1 trigger node (trigger service) and N execution nodes (execution services). When the trigger condition of the trigger node is met, the business process is started and subsequent execution nodes are executed, such as data operations, approvals, notifications and other operations required in the process. The message and data module is used to cache data during the execution of the business process. It includes message middleware, cache middleware and database.

[0150] Figure 8 The service integration platform shown integrates services corresponding to various types of SaaS products, forming a SaaS service library. It allows users to access services from this library, configure data relationships between services, orchestrate and combine services, create business processes, and standardize data generated by services corresponding to SaaS products using a CIM model. This enables data flow between different services and systems, or seamless data transfer between different cloud services, significantly improving the efficiency of data flow between multiple different services. Figure 9 This is a schematic diagram of a business process created by a user according to their own business needs in one embodiment. Figure 9 In the testing process of trigger-type services, the test form refers to the request parameters required during the test. In the testing process of execution-type services, the form is filled out manually, which refers to the relevant data manually entered by the user terminal. The specific data required will vary from service to service and should be entered according to the actual scenario. Figure 10This is a flowchart illustrating the user-initiated business process in one embodiment, wherein... Figure 10 In the execution process of trigger-type services, timed triggering or event triggering are the relevant operations corresponding to the trigger-type services. When the triggering conditions are met, the data corresponding to the trigger-type service can be obtained, and the data can be transformed and stored based on the CIM model before the subsequent execution-type services are executed. Figure 11 This refers to the relationship diagram between the CIM model and services. It can be used to unify service integration data standards and store the mapping relationship between data fields and the common data model, thereby effectively reducing the integration complexity between services corresponding to SaaS products. Furthermore, whenever a new SaaS product is added, only the mapping relationship between the corresponding service of the SaaS product and the CIM model needs to be configured to achieve rapid integration between that service and services corresponding to other SaaS products. For the multi-service data processing system mentioned in this case, most of the tasks performed by the first server correspond to the relevant operations and interactions between the external system modules and the SaaS service integration center module in this integration platform embodiment. Most of the tasks performed by the second server correspond to the relevant operations performed by the business system modules, the data unification standard module, and the message and data modules, as well as the interactions between these modules and the external system modules and the SaaS service integration center module. While each server and module performs its own duties, they also cooperate, thereby achieving flexible point-to-point connections between services, which enables the flow of data between different services, greatly improving the efficiency of data flow between multiple services, and thus significantly improving the work efficiency of the enterprise.

[0151] Based on the same inventive concept, this application also provides a multi-service data processing apparatus for implementing the multi-service data processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more multi-service data processing apparatus embodiments provided below can be found in the limitations of the multi-service data processing method described above, and will not be repeated here.

[0152] In one embodiment, such as Figure 12 As shown, a multi-service data processing device is provided, including: an acquisition module 1200, a triggering module 1202, a preliminary execution module 1204, an iterative execution module 1206, and a termination execution module 1208, wherein:

[0153] The acquisition module 1200 is used to acquire a target business process request, which includes a triggering service and at least two execution services.

[0154] Trigger module 1202 is used to run the trigger class service and generate trigger class data when the trigger condition is met.

[0155] The initial execution module 1204 is used to select an initial execution class service from the execution class services based on the execution order corresponding to the target business process request, and convert the trigger class data into initial standard data applied to the initial execution class service based on the target cloud information model. The initial execution class service runs based on the initial standard data to generate current execution service data.

[0156] The iterative execution module 1206 is used to select the current execution class service from the execution class services based on the execution order, and convert the current execution service data into current standard data applied to the current execution class service based on the target cloud information model. The current execution class service runs based on the current standard data to generate target execution service data.

[0157] The execution termination module 1208 is used to take the target execution service data as the current execution service data, return the step of selecting the current execution class service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service.

[0158] In one embodiment, the multi-service data processing device further includes a creation module 1210, which is used to obtain a target triggering service and at least two target execution services; sequentially combine the target triggering service and the at least two target execution services to generate an intermediate business process request; formulate corresponding target operation rules for the intermediate business process request, and determine the target business process request.

[0159] In one embodiment, the multi-service data processing device further includes a testing module 1212, configured to: obtain a trigger-type service to be tested from a target service library; obtain test trigger request parameters corresponding to the trigger-type service to be tested; perform testing based on the test trigger request parameters to obtain a target trigger-type service; obtain an execution-type service to be tested from the target service library; obtain forward service data; convert the forward service data into standard execution data applied to the execution-type service to be tested based on the target cloud information model; obtain test execution request parameters corresponding to the execution-type service to be tested; perform testing on the execution-type service to be tested based on the standard execution data and the test execution request parameters to obtain a target execution-type service; return to the step of obtaining the execution-type service to be tested from the target service library until the end addition condition is met, thereby obtaining the at least two target execution-type services.

[0160] In one embodiment, the initial execution module 1204 is further configured to obtain a first mapping relationship between the trigger class service corresponding to the trigger class data and the target cloud information model, and to obtain a second mapping relationship between the initial execution class service and the target cloud information model; based on the first mapping relationship and the second mapping relationship, the target cloud information model converts the trigger class data into initial standard data applied to the initial execution class service.

[0161] In one embodiment, the multi-service data processing apparatus further includes a conversion and storage module 1214, used to obtain the mapping relationship between a target service and a target cloud information model, wherein the target service includes trigger-type services and execution-type services; run the target service to generate target service data; based on the mapping relationship, the target cloud information model converts the target service data into common type data; and stores the common type data.

[0162] Each module in the aforementioned multi-service data processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can invoke and execute the operations corresponding to each module.

[0163] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 13 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data exchanged between multiple different services. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a multi-service data processing method.

[0164] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 14As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a multi-service data processing method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0165] Those skilled in the art will understand that Figure 13 and Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0166] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method examples.

[0167] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0168] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0169] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0170] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0171] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0172] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A multi-service data processing method, characterized in that, The method includes: Obtain the target business process request, wherein the target business process request includes a triggering service and at least two execution services; When the triggering conditions are met, the triggering class service is run to generate triggering class data; Based on the execution order corresponding to the target business process request, an initial execution service is selected from the execution services. Based on the target cloud information model, the trigger data is converted into initial standard data applied to the initial execution service. The initial execution service runs based on the initial standard data to generate the current execution service data. Based on the execution order, the current execution service is selected from the execution services. Based on the target cloud information model, the data of the current execution service is converted into current standard data applicable to the current execution service. The current execution service runs based on the current standard data to generate target execution service data. The target execution service data is used as the current execution service data. The step of selecting the current execution class service from the execution class services based on the execution order is returned until the process termination condition is met, and the target execution service data corresponding to each execution class service is obtained.

2. The method according to claim 1, characterized in that, Before obtaining the target business process request, which includes a triggering service and at least two execution services, the process further includes: Obtain the target trigger class service and at least two target execution class services; The target triggering service and the at least two target execution services are combined sequentially to generate an intermediate business process request; Develop corresponding target operation rules for the intermediate business process request, and determine the target business process request.

3. The method according to claim 2, characterized in that, Before obtaining the target triggering class service and at least two target execution class services, the process also includes: Obtain the target trigger class service from the target service library, obtain the test trigger request parameters corresponding to the target trigger class service, perform the test based on the test trigger request parameters, and obtain the target trigger class service; Obtain the execution class service to be tested from the target service library, obtain the forward service data, and based on the target cloud information model, convert the forward service data into standard execution data applicable to the execution class service to be tested; Obtain the test execution request parameters corresponding to the execution class service to be tested, and test the execution class service to be tested based on the standard execution data and the test execution request parameters to obtain the target execution class service; Return to the step of obtaining the execution class service to be tested from the target service library until the end addition condition is met, and obtain the at least two target execution class services.

4. The method according to claim 1, characterized in that, The process of converting the triggering data into initial standard data applicable to the initial execution service based on the target cloud information model includes: Obtain the first mapping relationship between the trigger class service corresponding to the trigger class data and the target cloud information model, and obtain the second mapping relationship between the initial execution class service and the target cloud information model; Based on the first mapping relationship and the second mapping relationship, the target cloud information model transforms the trigger class data into initial standard data applied to the initial execution class service.

5. The method according to claim 1, characterized in that, The method further includes: Obtain the mapping relationship between the target service and the target cloud information model, wherein the target service includes trigger-type services and execution-type services; Run the target service to generate target service data; Based on the mapping relationship, the target cloud information model converts the target service data into common type data; Store the public type data.

6. A multi-service data processing apparatus, characterized in that, The device includes: The acquisition module is used to acquire a target business process request, wherein the target business process request includes a triggering service and at least two execution services; The trigger module is used to run the trigger class service and generate trigger class data when the trigger conditions are met. The initial execution module is used to select an initial execution class service from the execution class services based on the execution order corresponding to the target business process request, and convert the trigger class data into initial standard data applied to the initial execution class service based on the target cloud information model. The initial execution class service runs based on the initial standard data to generate the current execution service data. The repetitive execution module is used to select the current execution service from the execution services based on the execution order, and convert the current execution service data into current standard data applicable to the current execution service based on the target cloud information model. The current execution service runs based on the current standard data to generate target execution service data. The execution termination module is used to take the target execution service data as the current execution service data, return the step of selecting the current execution class service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service.

7. A multi-service data processing system, characterized in that, The system includes: The first server creates a corresponding target business process request by sequentially combining trigger-type services and execution-type services. The target business process request includes a trigger-type service and at least two execution services. The target business process request is then sent to the second server. The second server includes a first server node and a second server node. The first server node is used to obtain the target business process request. When the triggering condition is met, it runs the triggering class service of the target business process request, generates triggering class data, and sends the triggering class data to the second server node. The first server node is further configured to select an initial execution class service from the execution class services based on the execution order corresponding to the target business process request, obtain the initial standard data that has been converted from the trigger class data, the initial execution class service runs based on the initial standard data, generates current execution service data, and sends the current execution service data to the second server node; The first server node is further configured to select the current execution class service from the execution class services based on the execution order, obtain the current standard data that the current execution class service has been converted, the current execution class service runs based on the current standard data to generate target execution service data, use the target execution service data as the current execution service data, send the current execution service data to the second server node, return the step of selecting the current execution service from the execution class services based on the execution order, until the process termination condition is met, and obtain the target execution service data corresponding to each execution class service; The second server node is used to obtain the trigger class data and the currently executed service data. Based on the target cloud information model, it converts the trigger class data into the initial standard data and the currently executed service data into the current standard data, and sends the initial standard data and the current standard data to the first server node.

8. The system according to claim 7, characterized in that, The second server node is also used to obtain the mapping relationship between the target service and the target cloud information model. The target service includes trigger-type services and execution-type services. The target service data corresponding to the target service is obtained. Based on the mapping relationship, the target cloud information model converts the target service data into common type data and stores the common type data.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images