Service execution system and service execution method

Through the data-driven component module architecture, the flexible orchestration of the service platform is achieved, and the problems of low elasticity and high cost of service platforms in the existing technology are solved, and the adaptability and efficiency of business services are improved.

CN118939387APending Publication Date: 2024-11-12DIGIWIN SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310530319.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-11
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When providing business services, existing service platforms need to be designed for specific applications and business systems, resulting in reduced usage flexibility and increased development costs, especially when the number of business systems increases, maintenance costs also increase.

Method used

Using a data-driven component module architecture, the detection module and execution module periodically create tasks, obtain action numbers and call link information, automatically execute tasks and generate execution results, and realize flexible service orchestration and avoid pre-customized orchestration.

Benefits of technology

It improves the application flexibility of services, reduces development and maintenance costs, and can automatically access heterogeneous systems to adapt to a variety of business scenarios and systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939387A_ABST
    Figure CN118939387A_ABST
Patent Text Reader

Abstract

The invention provides a service execution system and a service execution method. The service execution system comprises a memory and a processor. The processor executes the detection module and the execution module in the memory. The detection module periodically creates a first task according to a detection and execution rule in the memory and obtains an action number of the first task. The action number corresponds to the business index. The execution module obtains call link information in the detection and execution rule according to the action number, and executes a first task on the electronic device based on the call link information to generate a first execution result. The detection module judges whether the detection module creates a second task or not according to the detection and execution rule and the first execution result, so that the execution module executes the second task to generate a second execution result, and various service orchestrations are configured according to the second execution result.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to an electronic service system, in particular to a business execution system and a business execution method capable of automatically detecting and executing tasks. Background Art

[0002] The service platform can provide the business indicators or key performance indicators (KPIs) required by users based on the data in multiple business systems. Generally speaking, since these business systems implement different data models, the service platform obtains the corresponding data through different calculation logics. In some applications, the service platform further refers to additional conditions or parameters to process or calculate the obtained data to generate the target business pointer.

[0003] That is to say, for the target business indicators and related business systems, the current service platform achieves customized business service functions by providing a series of service orchestrations. However, the aforementioned operation method must be designed for specific applications and specific business systems, which reduces the flexibility of the service platform and also increases the development cost of the service platform. On the other hand, if the number of required business systems increases, the cost of developing and maintaining the service platform will increase accordingly. Summary of the invention

[0004] The present invention is directed to an execution business system that can configure various service arrangements through a module architecture composed of data-driven components to improve the application elasticity of services and reduce costs.

[0005] According to an embodiment of the present invention, the execution business system of the present invention includes a memory and a processor. The memory is used to store multiple modules and detection and execution rules. The processor is coupled to the memory and the electronic device. The processor is used to execute multiple modules. The multiple modules include a detection module and an execution module. The processor executes the detection module to periodically create a first task according to the detection and execution rules, and obtain the action number of the first task. The action number corresponds to the business indicator. The processor executes the execution module to obtain the call link information in the detection and execution rules according to the action number, and executes the first task on the electronic device based on the call link information to generate a first execution result. The processor executes the detection module to determine whether the detection module creates a second task according to the detection and execution rules and the first execution result, so that the execution module executes the second task to generate a second execution result.

[0006] According to an embodiment of the present invention, the execution business method of the present invention includes the following steps. The detection module executed by the processor periodically creates a first task according to the detection and execution rules, and obtains the action number of the first task. The action number corresponds to the business indicator. The execution module executed by the processor obtains the call link information in the detection and execution rules according to the action number, and executes the first task on the electronic device based on the call link information to generate a first execution result. The detection module determines whether to create a second task according to the detection and execution rules and the first execution result, so that the execution module executes the second task to generate a second execution result.

[0007] Based on the above, the execution service system and execution service method of the present invention can form a component-based module architecture to flexibly configure different service arrangements by initiating tasks and executing tasks through the detection module and the execution module respectively. In addition, the execution module can automatically access heterogeneous systems to generate execution results according to the task number and the corresponding call link information operation without pre-customizing the service arrangement, so the execution service system can improve the application flexibility of the service and reduce the cost of development and maintenance.

[0008] In order to make the above features and advantages of the present invention more clearly understood, embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a schematic diagram of a business execution system according to an embodiment of the present invention;

[0010] Figure 2 is a flow chart of a method for executing a service according to an embodiment of the present invention;

[0011] Figure 3 is a schematic diagram of a business execution system according to another embodiment of the present invention;

[0012] Figure 4 is a flow chart of a method for executing a service according to another embodiment of the present invention;

[0013] Figure 5 The present invention Figure 3 An action diagram of the execution module of the embodiment;

[0014] Figure 6 is a schematic diagram of an execution module according to an embodiment of the present invention.

[0015] Description of Reference Numerals

[0016] 100, 300: Execution business system;

[0017] 110: processor;

[0018] 120: memory;

[0019] 121: detection module;

[0020] 1211: Detection engine;

[0021] 1212: timer (scheduling module);

[0022] 122: execution module;

[0023] 1221: execution engine;

[0024] 122a, 122b: service unit;

[0025] 123: Knowledge map module;

[0026] 1231: Designer;

[0027] 1232: Knowledge map unit;

[0028] 200, 410: electronic devices;

[0029] 211-213, 411-414, 421-425: Application Programming Interface (API);

[0030] 220: memory;

[0031] 310: server (detection engine);

[0032] 311: Detection actuator;

[0033] 312: detection data manager;

[0034] 313: Detection model;

[0035] 314: Deduplication data model;

[0036] 315: Detection and recording model;

[0037] 31a, 32a, 34a: processor;

[0038] 31b, 34b, 34b: memory;

[0039] 320: server (execution engine);

[0040] 330: server (knowledge map);

[0041] 331: Management knowledge graph unit;

[0042] 332: Action logic map unit;

[0043] 340: server (scheduling engine);

[0044] 420: Task processing system;

[0045] 601, 602: known data;

[0046] 611, 621: processing logic;

[0047] 6121, 6122, 6221, 6222: input data;

[0048] 6131~6133, 6231~6233: output data;

[0049] S210-S230, S410-S450: steps;

[0050] S511~S550: module. DETAILED DESCRIPTION

[0051] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Whenever possible, the same reference numerals are used in the drawings and the description to refer to the same or like parts.

[0052] Figure 1 FIG. 1 is a schematic diagram of a business execution system according to an embodiment of the present invention. Figure 1 , the execution business system 100 applies data-driven programming, and automatically operates the data in the electronic device 200 through the component framework structure. In the present embodiment, the execution business system 100 may, for example, be a server set up in the cloud, so that users can access the relevant business service functions of the execution business system 100 through the electronic device 200. The server may, for example, be a Software as a Service (SaaS) server, but the present invention is not limited to this. The business service function may, for example, be a statistical operation of business indicators (or key performance indicators) such as calculating the arrival qualification rate, calculating the on-time completion rate of work orders, calculating the total project cost, or a combination of the foregoing to provide the target business indicators. In some embodiments, the execution business system 100 may be set up on a server at the internal end of the enterprise to provide relevant business service functions.

[0053] In this embodiment, the electronic device 200 is coupled to the execution business system 100. The electronic device 200 may include a plurality of business systems (not shown) and a memory 220. These business systems may include a plurality of corresponding application programming interfaces (APIs) 211-213. In this embodiment, the execution business system 100 accesses data in the memory 220 through the APIs 211-213. The execution business system 100 outputs business service results (i.e., business indicators) to the electronic device 200 through any one of the APIs 211-213 or other transmission interfaces (not shown). The electronic device 200 may be, for example, a mobile phone, a tablet computer, a laptop computer, a desktop computer, etc.

[0054] In this embodiment, the execution service system 100 may include a processor 110 and a memory 120. The memory 120 stores a plurality of modules 121-123, detection and execution rules, and related programs, modules, systems or algorithms for implementing various embodiments of the present invention, so as to be accessed and executed by the processor 110 to implement the related functions and operations described in various embodiments of the present invention. The memory 120 may be, for example, a dynamic random access memory (DRAM), a flash memory or a non-volatile random access memory (NVRAM), but the present invention is not limited thereto.

[0055] In this embodiment, the modules 121-123 may include a detection module 121, an execution module 122, and a knowledge map module 123. In detail, the detection module 121 may include a detection engine 1211 and a timer (also called a scheduling module) 1212. The execution module 122 may include an execution engine 1221 having one or more service units 122a-122b. The knowledge map module 123 may include a designer 1231 and a knowledge map unit 1232. In this embodiment, these modules 121-123 and these engines or units 1211-1212, 122a-122b, 1231-1232 may be implemented in a programming language such as JSON (JavaScript Object Notation), Extensible Markup Language (XML) or YAML, etc., but the present invention is not limited thereto.

[0056] In this embodiment, the processor 110 is coupled to the memory 120 and the electronic device 200. The processor 110 can access the data in the memory 120 and the modules 121-123, as well as the data transmitted between the electronic device 200, and can execute the modules 121-123. The processor 110 can be, for example, a signal converter, a field programmable gate array (FPGA), a central processing unit (CPU), or other programmable general-purpose or special-purpose microprocessor (Microprocessor), a digital signal processor (DSP), a programmable controller, an application specific integrated circuit (ASIC), a programmable logic device (PLD) or other similar devices or a combination of these devices, which can load and execute computer program related firmware or software to achieve functions such as data acquisition, calculation, calling and execution.

[0057] Figure 2 FIG. 1 is a flow chart of a method for executing a service according to an embodiment of the present invention. Figure 1 as well as Figure 2 , the execution service system 100 may execute steps S210 to S230. The order of these steps S210 to S230 is only an example and is not limited thereto. In this embodiment, steps S210 to S230 may be applied to the following exemplary situations.

[0058] In this embodiment, the user inputs user setting data (e.g., a business service request) to the execution business system 100 through the electronic device 200. The execution business system 100 detects and executes the data in the electronic device 200 in segments based on the rules defined by the aforementioned request (i.e., detection and execution rules) to generate execution results (i.e., business indicators). The execution business system 100 outputs the execution results to the electronic device 200 to complete the target business service. In some embodiments, the electronic device 200 executes an enterprise system to operate in coordination with the execution business system 100. The enterprise system may be, for example, an enterprise resource planning (ERP) system.

[0059] In some embodiments, the detection and execution rules may be defined (or set) in advance in the knowledge map module 123 by executing the business system 100. The detection and execution rules may, for example, describe the business indicators predefined or requested by the electronic device 200, describe the program for the detection module 121 to perform detection, and describe the program for the execution module 122 to perform logical calculations. In some embodiments, the detection and execution rules may include business indicator rules, timing scheduling rules, and subsequent processing rules. Business indicator rules may include indicator detection and acquisition logic and detection business screening rules, and may, for example, describe how the execution business system 100 accesses (for example, API calls) the electronic device 200 to obtain business indicators. The timing scheduling rules may, for example, describe how the execution business system 100 periodically initiates (or creates) tasks to start operations on business indicators. Subsequent processing rules may, for example, describe how the execution business system 100 performs subsequent processing on the acquired business indicators to obtain the final business indicators or execute subsequent control processes.

[0060] Specifically, the processor 110 executes the knowledge map module 123. The knowledge map module 123 collects definition data of multiple APIs 211 to 213. The knowledge map module 123 calculates the aforementioned definition data to generate dependency relationships between these APIs 211 to 213. In detail, the knowledge map module 123 collects definition data such as attributes and agreements of each API 211 to 213 through the knowledge map unit 1232. The knowledge map module 123 defines the dependency relationships between these APIs 211 to 213 based on the definition data through the designer 1231. The dependency relationship may, for example, describe the matching relationship between the value of a first field in the input parameter of an API (for example, API 211) and the second field in the output parameter of another API (for example, API 213), so that the value of the aforementioned first field can be obtained from the aforementioned second field and reflected.

[0061] On the other hand, the processor 110 executes the knowledge map module 123. The knowledge map module 123 generates business indicator rules in the detection and execution rules according to multiple fields of the user setting data from the electronic device 200 and the defined dependencies. In this embodiment, the business indicator rule can, for example, describe the program (such as call link information) for the execution module 122 to perform logical calculations, so that the execution module 122 calls at least one of the APIs 211-213 based on this rule. In other words, the knowledge map module 123 can automatically establish call link information between multiple APIs 211-213 through the relationship between multiple fields.

[0062] In this embodiment, the user setting data may be, for example, the application scenario input by the user through the electronic device 200, and the predefined or requested business indicators or a combination of the foregoing. The user setting data may also be, for example, the definition data of the APIs 211 to 213 actually collected by the electronic device 200 itself, and the description of the correspondence between these APIs 211 to 213, or a combination of the foregoing. The correspondence may, for example, describe the matching (e.g., equality) relationship between the meaning of the input field of one API (e.g., API 211) and the meaning of the output field of another API (e.g., API 213), so that the foregoing fields serve as the basic data source for the call operation.

[0063] For example, the knowledge map module 123 defines in the user setting data that "the student name in the student information returned in the student information query service and the student name required to be input in the student score query service are equivalent" provided by the electronic device 200 through the designer 1231. In other words, the designer 1231 defines synonymous fields that are interchangeable between input parameters and / or output parameters of different APIs 211-213, and defines the aforementioned data in the user setting data.

[0064] Continuing with the above description, the processor 110 executes the knowledge map module 123. The knowledge map module 123 sets the timing scheduling rules and subsequent processing rules in the detection and execution rules according to the user setting data. That is, the knowledge map module 123 sets the data content to be detected (i.e., the business indicators of the target and its required parameters) and the detection method through the designer 1231 according to the known and defined application scenarios, the relationship between APIs 211~213, and the business indicators of the target. The data content to be detected may include input parameters and / or output parameters of the business indicators. The detection method may include the definition of the data change observation period and the description of the detection method. The designer 1231 defines the aforementioned data content and detection method in the timing scheduling rules and subsequent processing rules.

[0065] In addition, the processor 110 executes the knowledge map module 123. The knowledge map module 123 publishes the detection and execution rules (i.e., business indicator rules, timing scheduling rules, and subsequent processing rules) to the detection module 121 through the knowledge map unit 1232. The processor 110 executes the detection module 121 so that the detection module 121 deploys programs corresponding to the detection and execution rules through the detection engine 1211.

[0066] In step S210, the processor 110 executes the detection module 121. The detection module 121 periodically creates a first task according to the detection and execution rules, and obtains an action number of the first task, wherein the action number corresponds to a business indicator. That is, the detection module 121 automatically and periodically creates tasks corresponding to business indicators according to the rules defined by the knowledge map module 123, and distinguishes them from other tasks by the action number. The action number may be, for example, an identifier of the first task to indicate the business indicator of the target.

[0067] Specifically, the detection module 121 obtains the data change observation period and the corresponding detection event number in the detection and execution rules through the detection engine 1211. That is, the detection engine 1211 parses the detection and execution rules (such as timed scheduling rules) defined by the knowledge map module 123, and separates the detection period (i.e., data change observation period) of the target data in this rule, and distinguishes it from other data to be detected by the detection event number. The detection event number can be, for example, an identifier of the detection period to indicate the business indicator of the target. In this embodiment, the detection engine 1211 publishes the data change observation period with the attached detection event number to the scheduling module 1212.

[0068] Next, the processor 110 executes the scheduling module 1212. The scheduling module 1212 triggers the processor 110 to execute the detection module 121 according to the detection event number based on the data change observation period. In other words, the scheduling module 1212 creates (or initiates) a scheduled task (i.e., the first task in step S210) with the detection event number attached based on the aforementioned period, and wakes up the detection engine 1211 to enable the detection engine 1211 to perform the corresponding detection operation.

[0069] In this embodiment, the triggered detection engine 1211 parses the action number in the first task and publishes the action number to the execution module 122 to trigger the execution module 122. It should be noted that the detection engine 1211 can implement the detection operation through the execution module 122, so that the execution module 122 acts as a proxy for the detection engine 1211 to perform the detection activity.

[0070] In step S220, the processor 110 executes the execution module 122. The execution module 122 obtains the call link information in the detection and execution rule according to the action number, and executes the first task on the electronic device 200 based on the call link information to generate a first execution result. The first execution result may be, for example, a business indicator of the target, or pre-data of the business indicator for further analysis or processing.

[0071] In detail, the execution module 122 obtains the call link information from the knowledge map module 123 according to the action number of the first task through the execution engine 1221. The execution engine 1221 parses the call link information to construct each program of the call operation. The execution engine 1221 can execute the aforementioned programs through the service unit 122a and / or 122b simultaneously or sequentially to complete the corresponding service. In other words, the service units 122a and 122b respectively call the API 212 and API 212, 213 according to the call link information, and return the obtained one or more call results to the detection module 121.

[0072] In step S220, the processor 110 executes the detection module 121. The detection module 121 determines whether to create a second task according to the detection and execution rule and the first execution result, so that the execution module 122 executes the second task to generate a second execution result.

[0073] In detail, the detection module 121 determines whether the detection module 121 creates a second task to continue the second task through the detection engine 1211 according to whether the first execution result satisfies the detection and execution rules (for example, the subsequent processing rules). The subsequent processing rules may include application scenarios defined by the user (i.e., user setting data). The second task may include processing or parsing the first execution result, other management operations, or a combination of the foregoing. In this embodiment, when the first execution result satisfies the application scenario, the detection engine 1211 automatically creates the second task according to the detection and execution rules, and automatically drives the execution module 122 to execute the second task to generate a corresponding execution result. Conversely, when the first execution result does not meet the application scenario, the detection engine 1211 outputs the first execution result to the electronic device 200 and ends the execution of the business method.

[0074] It is worth mentioning here that by automatically and periodically initiating tasks and executing tasks respectively through the detection module 121 and the execution module 122, various service orchestrations can be implemented through the component-based module architecture to improve the operational flexibility of providing business services to heterogeneous systems. In addition, the execution module 122 can automatically access heterogeneous APIs 211-213 according to the task number and the corresponding call link information operation without pre-customizing the service orchestration. In this way, the execution business system 100 can improve application flexibility and reduce development and maintenance costs at the same time.

[0075] Figure 3 FIG. 1 is a schematic diagram of a business execution system according to another embodiment of the present invention. Figure 3 , the business system 300 applies data-driven programming and automatically operates the data in the electronic device 410 and / or the task processing system 420 through the component framework structure. Figure 3In an embodiment, the execution business system 300 may include a plurality of servers 310 to 340. Server 310 is coupled to servers 320 to 340. Server 320 is coupled to server 330, electronic device 410, and task processing system 420. At least one of these servers 310 to 340 may be set in the cloud. At least one of these servers 310 to 340 may be set on the ground. These servers 310 to 340 include respective processors and memories to independently execute the detection module, the execution module, the knowledge map module, and the scheduling module. The execution business system 300 may refer to the relevant description of the execution business system 100 and be deduced by analogy, so it will not be repeated here.

[0076] In detail, it corresponds to Figure 1 In an embodiment, the processor 110 may include processors 31a, 32a and 34a, and the memory 120 may include memories 31b, 32b and 34b. The processor 31a and the memory 31b may be configured in the server 310 to execute the detection module. The server 310 may be used as a server for executing the detection engine (hereinafter referred to as the detection engine 310). In this embodiment, the memory 31b stores a plurality of modules (or models) 311-315 and related programs for implementing the detection engine for access and execution by the processor 31a. The aforementioned modules may include a detection executor 311, a detection data manager 312, a detection model 313, a deduplication data model 314 and a detection record model 315.

[0077] In this embodiment, the processor 32b and the memory 32b are configured in the server 320 to execute the execution module. The server 320 can be used as a server for executing the execution engine (hereinafter referred to as the execution engine 320). In this embodiment, another processor not shown and another memory not shown are configured in the server 330 to execute the knowledge map module. The server 330 can be used as a server for executing the knowledge map (hereinafter referred to as the knowledge map 330). The memory in the server 330 stores multiple modules (or units) 331-332 and related programs for implementing the knowledge map for access and execution by the processor in the server 330. The aforementioned modules may include a knowledge map management unit 331 and an action logic map unit 332. In this embodiment, the processor 34a and the memory 34b are configured in the server 340 to execute the timer (also called the scheduling module). The server 340 can be used as a server for executing the scheduling engine (hereinafter referred to as the scheduling engine 340).

[0078] In this embodiment, the electronic device 410 may include a plurality of heterogeneous business systems (not shown), wherein these business systems may include a plurality of corresponding APIs 411-414. The aforementioned APIs may be, for example, a device interface API 411, a document center service system API 412, an application system API 413, and other system APIs 414. The execution business system 300 accesses data in the electronic device 410 through the APIs 411-414. The execution business system 300 outputs business service results (i.e., business indicators) to the electronic device 410 through any of the APIs 411-414 or other transmission interfaces (not shown).

[0079] In this embodiment, the task processing system 420 may include multiple business systems (not shown), wherein these business systems may include corresponding multiple APIs 421-425. The aforementioned APIs may be, for example, a workflow system API 421, an alarm system API 422, an email system API 423, a control system API 424, and other system APIs 425. The execution business system 300 accesses and / or operates the task processing system 420 through the APIs 421-425 to generate final business indicators or provide subsequent and additional business services. The task processing system 420 may be, for example, another server or another electronic device to operate in coordination with the electronic device 410.

[0080] Figure 4 is a flow chart of a method for executing a service according to another embodiment of the present invention. Figure 3 as well as Figure 4 , the execution business system 300 may execute steps S410 to S450. The order of these steps S410 to S450 is only an example and is not limited thereto.

[0081] In step S410, the scheduling engine 340 sends a detection instruction to the detection engine 310 at a predetermined time to enable the detection engine 310 to execute the detection executor 311. In other words, the scheduling engine 340 has the function of a timer. The scheduling engine 340 sets the timing scheduling rules in the detection and execution rules. Based on the timing scheduling rules, the scheduling engine 340 outputs the detection instruction to the detection engine 310 at a specified time point (for example, a data change observation period) to trigger the detection executor 311. The detection instruction includes the target detection event and the detection event number, and is distinguished from other detection events by the detection event number.

[0082] It should be noted that the content of the detection instruction may be, for example, a program generated by the detection engine 310 before step S410. By transmitting the detection instruction to the detection engine 310 through the scheduling engine 340, the timing of triggering the detection engine 310 can be increased to improve application flexibility.

[0083] In this embodiment, the detection engine 310 creates a first task based on the detection and execution rules (e.g., business indicator rules) to execute the task on behalf of the execution engine 320. The detection engine 310 determines whether the execution result of the first task needs further processing based on the detection and execution rules (e.g., subsequent processing rules) to continue the second task on behalf of the execution engine 320.

[0084] For example, in some applications, when the business indicator of the target is generated by counting or calculating other data, the first task may include detecting and collecting the aforementioned other data, and the second task may include counting or calculating these data to generate the final business indicator. In some other applications, when the business indicator of the target involves a subsequent processing flow, the first task may include detecting, collecting and calculating the required data to generate the business indicator, and the second task may include executing other processes through the task processing system 420 to provide management services. The aforementioned process may be, for example, initiating an email notification through the email system API 423 and the email system, initiating an immediate warning through the alarm system API 422 and the alarm system, initiating a posture adjustment through the control system API 424 and the control system, or a combination of the aforementioned.

[0085] Specifically, regarding the first task, in step S420, the detection engine 310 calls the execution engine 320 to execute the action logic of the business indicator according to the detection and execution rules. In detail, after the detection engine 310 receives the detection instruction through the detection executor 311, the detection executor 311 obtains the detection and execution rules (for example, business indicator rules) from the management knowledge graph unit 331 according to the detection instruction. The detection executor 311 calls the detection data manager 312 to execute the detection model 313 according to the business indicator rules to query whether the data about the detection event has changed within the specified period, and generates a detection acquisition logic instruction. The detection data manager 312 calls the execution engine 320 to execute the corresponding action logic according to the detection acquisition logic instruction. The detection acquisition logic instruction can be, for example, an instruction with an action number to trigger the execution engine 320.

[0086] It should be noted that, since the data required by the business indicator may require other directly or indirectly related data as the calculation condition or calculation basis of the business indicator, in the first stage of the execution method (i.e., during the first task), the detection data manager 312 obtains and filters the business logic of the real-time data in advance through the execution engine 320, and completes the data acquisition and calculation through the execution engine 320. On the other hand, since the data required by the business indicator may come from different heterogeneous systems, the detection data manager 312 operates according to the action logic through the execution engine 320, which can eliminate the differentiation of multiple interfaces (such as APIs 411-414) in these heterogeneous systems.

[0087] In step S430, the execution engine 320 calls the electronic device 410 to call the specified API and returns the execution result to the detection engine 310 according to the obtained business indicator rules. In detail, the execution engine 320 obtains the business indicator rules from the action logic map unit 332 according to the action number. The business indicator rules may, for example, describe the action logic program of one or more specified APIs (for example, at least one of APIs 411 to 414), and describe one or more input parameters and data conditions corresponding to the aforementioned API(s). The execution engine 320 assembles the aforementioned input parameters and data conditions to form the call link information about the electronic device 410. The execution engine 320 calls at least one of the specified APIs 411 to 414 according to the call link information to obtain the corresponding execution result, and returns the execution result to the detection engine 310.

[0088] In the process of executing step S430, the execution engine 320 accesses the action logic map unit 332 according to the business indicator rule to obtain the input parameters of the first task. Then, the execution engine 320 calls multiple APIs 411-414 based on the call link information about the electronic device 410 according to the input parameters of the first task to generate an execution result. In detail, the action logic map unit 332 provides the logical relationship between the API output parameters and the API input parameters, as well as the dependency and / or correspondence between multiple fields in the input parameters. The execution engine 320 automatically searches for the path of the API call based on the actual situation of the first task (i.e., the action number) according to the aforementioned logical relationship. The execution engine 320 also automatically constructs the data structure of the input parameters based on the actual situation of the first task according to the aforementioned dependency and / or correspondence. Therefore, the execution engine 320 automatically generates a program (i.e., call link information) for executing API call operations on heterogeneous systems based on the path of the API call and the constructed data structure.

[0089] It should be noted that the execution engine 320 automatically refers to the call link information to execute the call operation between multiple APIs 411-414 according to the set (or defined) business indicator rules (i.e., action logic program). In this way, the execution engine 320 automatically calls APIs 411-414, which can adapt to different service interfaces (such as APIs 411-414) of multiple heterogeneous systems, and can avoid the complex execution arrangement of these heterogeneous systems in advance.

[0090] For reference Figure 5 , Figure 5 The present invention Figure 3 Schematic diagram of the actions of the execution module of the embodiment. The execution engine 320 can execute multiple modules S511~S550 to illustrate the operation of the API call. In this embodiment, assuming that the target business indicator is the statistical return of on-time purchase, the execution engine 320 can generate an execution result based on multiple API call results by executing API calls on one or more heterogeneous systems. The multiple API call results may include the on-time purchase rate, the target value, and the difference description. The execution result may be, for example, the statistical return of on-time purchase.

[0091] In modules S511, S521, and S531, the execution engine 320 calls the application system API of the electronic device 410 based on the call link information. The execution engine 320 queries the on-time purchase rate by calling the service to obtain the on-time purchase rate. In modules S512, S522, and S532, the execution engine 320 calls another application system API of the electronic device 410 based on the call link information. The execution engine 320 obtains the target value by performing data conversion on the on-time purchase target value. In modules S513, S523, and S533, the execution engine 320 calls another application system API of the electronic device 410 based on the call link information. The execution engine 320 obtains the difference description by obtaining the mechanism variables of the report task. In modules S540 to S550, the execution engine 320 generates a statistical report on on-time purchase based on the obtained on-time purchase rate, target value, and difference description.

[0092] In this embodiment, when the input parameter obtained by the execution engine 320 is missing, the execution engine 320 supplements the missing of the first input parameter to update the input parameter. The execution engine 320 uses the updated input parameter as the current input parameter to continue the method. In detail, the execution engine 320 refers to the business indicator rule and analyzes whether the input parameter of the first task is missing a field or condition data according to the API (for example, API 411, 413) called by the target. When the aforementioned analysis result indicates that there is a missing, the execution engine 320 issues a missing instruction to the action logic map unit 332. The action logic map unit 332 finds other fields with matching meanings from the business indicator rule according to the missing data. The execution engine 320 performs a pre-call to another field library system (not shown) according to the aforementioned other fields to obtain the parameters corresponding to this field. The execution engine 320 reconstructs the data structure of the input parameter according to the obtained parameters, and generates call link information accordingly. On the other hand, when the aforementioned analysis result indicates that there is no missing, the execution engine 320 executes step S440.

[0093] In step S440, the detection engine 310 compares the execution result and the historical data corresponding to the target business indicator to generate a change execution result, and determines whether to call the execution engine 320 to perform subsequent processing (i.e., create a second task) based on the detection and execution rules (e.g., subsequent processing rules) and the change execution result. In detail, the detection engine 310 executes the detection record model 315 to compare the execution result of the first task with the execution result obtained in the historical record (e.g., the last time). The detection engine 310 executes the deduplication data model 314 to calculate or quantify the difference in the results of the aforementioned comparison (i.e., the change execution result).

[0094] Continuing with the above description, when the detection engine 310 determines that the change execution result satisfies the subsequent processing rule, the detection engine 310 creates a second task to trigger the execution engine 320 to execute the second task on its behalf. In other words, the detection engine 310 determines whether to execute another task through the execution engine 320 for subsequent processing to supplement the data or program that does not meet the user's expectations, or to terminate the execution of the business method based on the actual situation (i.e., the change execution result) and the user's settings in the subsequent processing rule.

[0095] Specifically, regarding the second task, in step S450, the execution engine 320 calls the task processing system 420 to call the specified API and returns the execution result to the detection engine 310 according to the obtained subsequent processing rules. In detail, the execution engine 320 obtains the subsequent processing rules from the action logic map unit 332. The subsequent processing rules may, for example, describe the action logic program of one or more specified APIs (for example, at least one of APIs 421 to 425), and describe one or more input parameters and data conditions corresponding to the aforementioned API(s). The execution engine 320 assembles the aforementioned input parameters and data conditions to form the call link information about the task processing system 420. The execution engine 320 calls at least one of the specified APIs 421 to 425 according to the call link information to obtain the corresponding execution result, and returns the execution result to the detection engine 310.

[0096] During the execution of step S450, the execution engine 320 accesses the action logic map unit 332 according to the subsequent processing rules to obtain the input parameters of the second task. Then, the execution engine 320 calls multiple APIs 421-425 based on the call link information about the task processing system 420 according to the input parameters of the second task to generate an execution result. The calling operation of the second task can refer to the relevant description of step S430 and be inferred by analogy, so it will not be repeated here.

[0097] In this embodiment, when the input parameters obtained by the execution engine 320 are missing, the execution engine 320 supplements the missing second input parameters to update the input parameters. The execution engine 320 uses the updated input parameters as the current input parameters to continue the method. In detail, the execution engine 320 refers to the subsequent processing rules and analyzes whether the input parameters of the second task are complete according to the target API called (for example, API 422, 423). When the aforementioned analysis results indicate that the input parameters are incomplete and missing, the execution engine 320 supplements the missing from the action logic map unit 332, and the operation details can refer to the relevant description of step S430 and be inferred by analogy, so it will not be repeated here. In this way, the execution engine 320 can automatically complete the calling operation to complete the subsequent service specified by the user.

[0098] Figure 6 FIG. 1 is a schematic diagram of an execution module according to an embodiment of the present invention. Figure 1 as well as Figure 6, this embodiment illustrates the execution method of the execution module 122. The execution business system 100 can receive request data to execute the application program interface 610. The detection module 121 can analyze the request data to create a call model including the application program interface 610 and the application program interface 620. The execution module 122 further establishes a call path. The execution module 122 can call the application program interface 610 and the application program interface 620 in sequence according to the call path. Specifically, first, the execution module 122 can execute the application program interface 610. The execution module 122 can assemble the input data 6121 (Pa1) of the application program interface 610, and obtain data according to the field data source of the input data 6121 (Pa1). In this regard, since the input data 6121 (Pa1) comes from the output data 6231 (Rb1) of the application program interface 620, there is no data to be obtained. The execution module 122 can execute the application program interface 620 to assemble the input data 6221 (Pb1) of the application program interface 620, and obtain data according to the field data source of the input data 6221 (Pb1). The execution module 122 can obtain data from the known data 601 (k1) to complete the assembly of the input data 6221 (Pb1). In this regard, the execution module 122 can assemble the input data 6222 (Pb2) of the application program interface 620, and obtain data according to the field data source of the input data 6222 (Pb2). The execution module 122 can obtain data from the known data 602 (k2) to complete the assembly of the input data 6222 (Pb2). In this way, the input data of the application program interface 620 is complete, and the execution module 122 can call the processing logic 621 of the application program interface 620 to generate output data 6231~6233. The execution module 122 can temporarily store the output data 6231 ˜ 6233 ( Rb1 ˜ Rb3 ).

[0099] Next, the execution module 122 may assemble the input data 6121 (Pa1) of the application program interface 610. The execution module 122 may obtain the input data 6121 (Pa1) from the output data 6231 (Rb1) of the application program interface 620 to complete the assembly of the input data 6121 (Pa1). The execution module 122 may assemble the input data 6122 (Pa2) of the application program interface 610, and obtain data according to the field data source of the input data 6122 (Pa2). The execution module 122 may obtain the input data 6122 (Pa2) from the output data 6232 (Rb2) of the application program interface 620 to complete the assembly of the input data 6122 (Pa2). In this way, the input data of the application program interface 610 is complete, and the execution module 122 may execute the processing logic 611 of the application program interface 610 to generate output data 6131-6133 (Ra1-Ra3). The execution module 122 may output output data 6131 ˜ 6133 ( Ra1 ˜ Ra3 ) to complete this data request.

[0100] In summary, the business execution system and business execution method of the present invention use multiple servers as scheduling engines, detection engines, execution engines, and knowledge maps, respectively, to form a system that provides various business services with a combination of components. The execution engine can automatically access heterogeneous APIs 211-213 based on call link information without pre-customizing service orchestration. Therefore, the business execution system can reduce the development work of service orchestration and improve the application flexibility of service orchestration. In this way, the business execution system can adapt to multiple heterogeneous systems, different business scenarios, different detection methods, and can provide different follow-up services.

[0101] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A business execution system, characterized in that: include: Memory to store multiple modules and detection and execution rules; as well as A processor is coupled to the memory and the electronic device, and is used to execute the multiple modules, wherein the multiple modules include a detection module and an execution module. wherein the processor executes the detection module to periodically create a first task according to the detection and execution rule, and obtains an action number of the first task, wherein the action number corresponds to a business indicator, wherein the processor executes the execution module to obtain the call link information in the detection and execution rule according to the action number, and executes the first task on the electronic device based on the call link information to generate a first execution result, The processor executes the detection module to determine whether the detection module creates a second task according to the detection and execution rule and the first execution result, so that the execution module executes the second task to generate a second execution result.

2. The business execution system according to claim 1, characterized in that: The multiple modules also include a knowledge map module. wherein the processor executes the knowledge map module to collect definition data of a plurality of first application program interfaces of the electronic device, calculates the definition data to generate dependency relationships between the plurality of first application program interfaces, and generates business indicator rules in the detection and execution rules according to a plurality of fields of user setting data from the electronic device and the dependency relationships, wherein the business indicator rules include the call link information, The processor executes the knowledge map module to set the timing scheduling rules and subsequent processing rules in the detection and execution rules according to the user setting data.

3. The business execution system according to claim 1, characterized in that: wherein the processor executes the detection module to obtain the data change observation period and the corresponding detection event number in the detection and execution rule, The plurality of modules further include a scheduling module, wherein the processor executes the scheduling module to trigger the processor to execute the detection module according to the detection event number according to the data change observation period.

4. The business execution system according to claim 1, characterized in that: The processor executes the detection module to compare the first execution result and the historical data corresponding to the business indicator to generate a change execution result, and determines whether the detection module creates the second task based on the detection and execution rules and the change execution result.

5. The business execution system according to claim 4, characterized in that: The processor executes the detection module to create the second task to trigger the processor to execute the execution module when the change execution result satisfies the subsequent processing rule in the detection and execution rule.

6. The business execution system according to claim 1, characterized in that: The electronic device includes a plurality of heterogeneous business systems, and the plurality of business systems include a plurality of first application programming interfaces, The processor executes the execution module to call the plurality of first application program interfaces based on the call link information according to the first input parameter of the first task to generate the first execution result.

7. The business execution system according to claim 6, characterized in that: The processor executes the execution module to access the knowledge map module according to the business indicator rule in the detection and execution rule to obtain the first input parameter, and when the first input parameter is missing, the missing first input parameter is supplemented to update the first input parameter.

8. The business execution system according to claim 1, characterized in that: The processor executes the execution module to access the knowledge map module according to the subsequent processing rules in the detection and execution rules to obtain the second input parameter of the second task, and calls multiple second application programming interfaces in the task processing system according to the second input parameter to generate the second execution result.

9. The business execution system according to claim 8, characterized in that: The processor executes the execution module to make up for the missing of the second input parameter to update the second input parameter when the second input parameter is missing.

10. The business execution system according to claim 1, characterized in that: The processor includes a first processor and a second processor, the first processor is configured on a first server to execute the detection module, the second processor is configured on a second server to execute the execution module, and the first server is coupled to the second server.

11. A method for executing a business, characterized in that: include: A detection module executed by a processor periodically creates a first task according to a detection and execution rule, and obtains an action number of the first task, wherein the action number corresponds to a business indicator; acquiring, by the execution module executed by the processor, call link information in the detection and execution rule according to the action number, and executing the first task on the electronic device based on the call link information to generate a first execution result; Through the detection module, it is determined whether the detection module creates a second task according to the detection and execution rules and the first execution result, so that the execution module executes the second task to generate a second execution result.

12. The method for executing business according to claim 11, characterized in that: Also includes: Collecting definition data of a plurality of first application program interfaces of the electronic device through a map recognition module executed by the processor; By means of the map recognition module, the definition data is calculated to generate dependency relationships between the plurality of first application program interfaces; Generate, by the map recognition module, a business indicator rule in the detection and execution rule according to a plurality of fields of the user setting data from the electronic device and the dependency relationship, wherein the business indicator rule includes the call link information; as well as The map recognition module is used to set the timing scheduling rules and subsequent processing rules in the detection and execution rules according to the user setting data.

13. The method for executing business according to claim 11, characterized in that: Also includes: Obtaining the data change observation period and the corresponding detection event number in the detection and execution rules through the detection module; as well as The scheduling module executed by the processor triggers the processor to execute the detection module according to the detection event number according to the data change observation period.

14. The method for executing business according to claim 11, characterized in that: The step of determining whether the detection module creates the second task according to the detection and execution rule and the first execution result includes: By means of the detection module, comparing the first execution result with the historical data corresponding to the business indicator to generate a change execution result; and By means of the detection module, it is determined whether the detection module creates the second task according to the detection and execution rules and the changed execution result.

15. The method for executing business according to claim 14, characterized in that: Also includes: Through the detection module, when the changed execution result satisfies the subsequent processing rule in the detection and execution rule, the second task is created to trigger the processor to execute the execution module.

16. The method for executing business according to claim 11, characterized in that: The electronic device includes a plurality of heterogeneous business systems, and the plurality of business systems include a plurality of application program interfaces, wherein the step of executing the first task on the electronic device based on the call link information to generate the first execution result includes: Through the execution module, according to the first input parameter of the first task, based on the call link information, the plurality of first application programming interfaces are called to generate the first execution result.

17. The method for executing business according to claim 16, characterized in that: Also includes: Accessing the knowledge map module to obtain the first input parameter according to the business indicator rule in the detection and execution rule through the execution module; as well as When the first input parameter is missing, the execution module is used to supplement the missing first input parameter to update the first input parameter.

18. The method for executing business according to claim 11, characterized in that: Also includes: Accessing the knowledge map module to obtain the second input parameter of the second task according to the subsequent processing rule in the detection and execution rule through the execution module; as well as Through the execution module, a plurality of second application programming interfaces in the task processing system are called according to the second input parameter to generate the second execution result.

19. The method for executing business according to claim 18, characterized in that: Also includes: When the second input parameter is missing, the missing second input parameter is supplemented by the execution module to update the second input parameter.

20. The method for executing business according to claim 11, characterized in that: The processor includes a first processor and a second processor, the first processor is configured on a first server to execute the detection module, the second processor is configured on a second server to execute the execution module, and the first server is coupled to the second server.