A service processing method and device, electronic equipment and computer readable medium

Abstract

The application discloses a business processing method and device, electronic equipment and computer readable medium, relates to the technical field of big data processing, and a specific embodiment includes receiving a business processing request, in response to detecting that the business processing request exists corresponding customized business, determining the corresponding engine interface; calling a business process integration framework to integrate the engine interface, and then generating a target workflow engine; calling the target workflow engine to execute the customized business, and in response to an execution exception, executing a reverse transaction program based on the customized business and outputting reverse transaction result information. The overall transaction consistency of the business process logic can be realized, and through reverse processing in an abnormal transaction, business development is more convenient and easier to promote, and the business processing efficiency and accuracy are improved.

Description

Technical Field

[0001] This application relates to the field of big data processing technology, and in particular to a business processing method, apparatus, electronic device and computer-readable medium. Background Technology

[0002] By embedding workflow engine interfaces into business systems, the development and processing of business processes can be achieved. The workflow engine, as part of the application system, provides core solutions that significantly impact each application system, determining information routing and content levels based on roles, responsibilities, and conditions. Different business processes require different workflow engines. To adapt to these different processes, the workflow engine's business logic code needs modification, and the corresponding engine interface also needs to be modified, leading to a sharp increase in development workload and low business processing efficiency and accuracy. Summary of the Invention

[0003] In view of this, embodiments of this application provide a business processing method, apparatus, electronic device, and computer-readable medium that can solve the problems of low efficiency and low accuracy in existing business processing.

[0004] To achieve the above objectives, according to one aspect of an embodiment of this application, a business processing method is provided, comprising:

[0005] Receive a business processing request, and in response to the detection that a corresponding customized business exists in the business processing request, determine the corresponding engine interface;

[0006] Call the business process integration framework to integrate the engine interface, and then generate the target workflow engine;

[0007] Invoke the target workflow engine to execute customized business logic. In response to execution exceptions, execute a reverse transaction program based on the customized business logic and output the reverse transaction result information.

[0008] Optionally, before determining the corresponding engine interface, the method further includes:

[0009] Obtain the business identifiers corresponding to the business processing requests;

[0010] Each service identifier is matched with the identifiers in the preset service identifier pool. If there is an identifier in each service identifier that does not match the identifiers in the preset service identifier pool, the service corresponding to the mismatched identifier is identified as a customized service.

[0011] Optionally, the corresponding engine interface is determined, including:

[0012] The customized business is matched with each candidate engine interface, and the successfully matched candidate engine interface is determined as the engine interface corresponding to the customized business.

[0013] Optionally, customized business logic can be matched with various candidate engine interfaces, including:

[0014] Obtain the primary functional data required for the customized business and the secondary functional data that can be provided by the interfaces of each candidate engine;

[0015] Calculate the similarity between the first function data and each of the second function data, and determine the candidate engine interfaces that match the customized business based on the similarity.

[0016] Optionally, the integrated engine interface includes:

[0017] The business process integration framework matches each business process point with the engine interface, and then integrates the matched business process points and engine interfaces.

[0018] Optionally, the various business process points of the business process integration framework are matched with the engine interface, including:

[0019] The similarity between the attributes of each business process point in the computational business process integration framework and the attributes of the engine interface is calculated.

[0020] The business process nodes that match the engine interface are determined based on similarity.

[0021] Optionally, the target workflow engine is generated, including:

[0022] Insert the program corresponding to the engine interface into the program corresponding to the matched business process node to generate the target workflow engine.

[0023] In addition, this application also provides a business processing apparatus, including:

[0024] The receiving unit is configured to receive business processing requests and, in response to detecting that a corresponding customized business exists in the business processing request, determine the corresponding engine interface.

[0025] The engine generation unit is configured to call the business process integration framework to integrate the engine interface and then generate the target workflow engine.

[0026] The execution unit is configured to invoke the target workflow engine to execute customized business logic, and in response to execution exceptions, execute a reverse transaction program based on the customized business logic and output reverse transaction result information.

[0027] Optionally, the receiving unit is further configured to:

[0028] Obtain the business identifiers corresponding to the business processing requests;

[0029] Each service identifier is matched with the identifiers in the preset service identifier pool. If there is an identifier in each service identifier that does not match the identifiers in the preset service identifier pool, the service corresponding to the mismatched identifier is identified as a customized service.

[0030] Optionally, the receiving unit is further configured to:

[0031] The customized business is matched with each candidate engine interface, and the successfully matched candidate engine interface is determined as the engine interface corresponding to the customized business.

[0032] Optionally, the receiving unit is further configured to:

[0033] Obtain the primary functional data required for the customized business and the secondary functional data that can be provided by the interfaces of each candidate engine;

[0034] Calculate the similarity between the first function data and each of the second function data, and determine the candidate engine interfaces that match the customized business based on the similarity.

[0035] Optionally, the engine generation unit is further configured to:

[0036] The business process integration framework matches each business process point with the engine interface, and then integrates the matched business process points and engine interfaces.

[0037] Optionally, the engine generation unit is further configured to:

[0038] The similarity between the attributes of each business process point in the computational business process integration framework and the attributes of the engine interface is calculated.

[0039] The business process nodes that match the engine interface are determined based on similarity.

[0040] Optionally, the engine generation unit is further configured to:

[0041] Insert the program corresponding to the engine interface into the program corresponding to the matched business process node to generate the target workflow engine.

[0042] In addition, this application also provides a business processing electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement the business processing method described above.

[0043] In addition, this application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the business processing method described above.

[0044] To achieve the above objectives, according to another aspect of the embodiments of this application, a computer program product is provided.

[0045] A computer program product according to an embodiment of this application includes a computer program that, when executed by a processor, implements the business processing method provided in the embodiment of this application.

[0046] One embodiment of the above invention has the following advantages or beneficial effects: This application receives a business processing request, and in response to detecting a corresponding customized business in the business processing request, determines the corresponding engine interface; calls the business process integration framework to integrate the engine interface, thereby generating a target workflow engine; calls the target workflow engine to execute the customized business, and in response to an execution exception, executes a reverse transaction program based on the customized business and outputs reverse transaction result information. This enables overall transaction consistency of the business process logic, and through reverse processing in abnormal transactions, makes business development more convenient, easier to promote, and improves business processing efficiency and accuracy.

[0047] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0048] The accompanying drawings are provided to better understand this application and do not constitute an undue limitation thereof. Wherein:

[0049] Figure 1 This is a schematic diagram of the flow of a business processing method according to an embodiment of this application;

[0050] Figure 2 This is a schematic diagram of the flow of a business processing method according to an embodiment of this application;

[0051] Figure 3 This is a schematic flowchart of a business processing method according to an embodiment of this application;

[0052] Figure 4 This is a schematic flowchart of a business processing method according to an embodiment of this application;

[0053] Figure 5 This is a schematic diagram of a unit of a service processing apparatus according to an embodiment of this application;

[0054] Figure 6 This is an exemplary system architecture diagram to which embodiments of this application can be applied;

[0055] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers in the embodiments of this application. Detailed Implementation

[0056] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that the collection, analysis, use, transmission, and storage of user personal information involved in the technical solutions of this application comply with relevant laws and regulations, are used for legitimate and reasonable purposes, are not shared, disclosed, or sold outside of these legitimate uses, and are subject to supervision and management by regulatory authorities. Necessary measures should be taken to prevent unauthorized access to such personal information data, ensure that personnel authorized to access personal information data comply with relevant laws and regulations, and ensure the security of user personal information. Once this user personal information data is no longer needed, the risk should be minimized by restricting or even prohibiting data collection and / or deleting the data.

[0057] When used, including in certain relevant applications, data is deidentified to protect user privacy, for example by removing specific identifiers, controlling the amount or specificity of stored data, controlling how data is stored, and / or other methods.

[0058] Figure 1 This is a schematic diagram of the flow of a business processing method according to an embodiment of this application, as shown below. Figure 1 As shown, the business processing methods include:

[0059] Step S101: Receive a business processing request; in response to the detection that a corresponding customized business exists for the business processing request, determine the corresponding engine interface.

[0060] In this embodiment, the entity executing the business processing method (e.g., a server) can receive business processing requests via wired or wireless connections. Specifically, the existence of customized services can be determined by the business identifier carried in the business processing request.

[0061] Specifically, before determining the corresponding engine interface, the business processing method further includes: obtaining each business identifier corresponding to the business processing request; matching each business identifier with identifiers in a preset business identifier pool; if there is an identifier among the business identifiers that does not match an identifier in the preset business identifier pool, then the business corresponding to the mismatched identifier is determined as a customized business. For example, a customized business can be a business not present in the preset business processing flow, such as a user-defined business. When a corresponding customized business is detected in the business processing request, the executing entity can analyze the customized business to obtain the corresponding business process parameters, and then encapsulate the engine interface according to the functionality of the customized business to be implemented.

[0062] Specifically, the process involves matching each business process point in the business process integration framework with the engine interface, including: calculating the similarity between the attributes of each business process point in the business process integration framework and the attributes of the engine interface; and determining the business process nodes that match the engine interface based on the similarity.

[0063] The attributes of each business process point may include the name of the business process point, the functions that can be implemented, etc. This application embodiment does not specifically limit the content of the attributes of the business process point.

[0064] Step S102: Invoke the business process integration framework to integrate the engine interface and generate the target workflow engine.

[0065] Workflow Engine: As part of the application system, workflow provides core solutions that play a decisive role in various application systems, such as determining information transmission routes and content levels based on different roles, divisions of labor, and conditions.

[0066] Specifically, integrating engine interfaces includes: matching each business process point of the business process integration framework with the engine interface, and then integrating the matched business process points and engine interfaces.

[0067] Specifically, word embedding can be used to match the functionality that each business process point in the business process integration framework can achieve with the functionality that the engine interface can achieve, in order to determine the matching business process points.

[0068] Specifically, generating the target workflow engine includes: inserting the program corresponding to the engine interface into the program corresponding to the matched business process node to generate the target workflow engine.

[0069] For example, the executing entity can segment the program corresponding to the matched business process node to obtain each segment program; input the program corresponding to the engine interface and each segment program into the long short-term memory neural network model to output the segment program associated with the program corresponding to the engine interface and the corresponding correlation degree; determine the target segment program based on the correlation degree; and then concatenate the program corresponding to the engine interface and the target segment program to generate the target workflow engine.

[0070] Step S103: Invoke the target workflow engine to execute customized business. In response to execution exceptions, execute the reverse transaction program based on the customized business and output the reverse transaction result information.

[0071] The defined business logic is executed by calling the engine logic in the target workflow engine. In the event of an exception, a reverse transaction procedure is invoked to execute the reverse transaction and output the corresponding reverse transaction result information. Since the workflow engine is an independent middleware system with its own database and interface for transaction operations, distributed transaction issues arise when integrating with the business system. If the transaction is successful, the target workflow engine central unit can commit the transaction normally. If an exception occurs, it needs to be handled using a reverse transaction. When an exception occurs in the target workflow engine, a reverse transaction is performed on the upstream business logic, achieving overall transactional consistency in the business process logic.

[0072] This embodiment receives a business processing request, and upon detecting a corresponding customized business within the request, determines the corresponding engine interface. It then invokes a business process integration framework to integrate the engine interface, thereby generating a target workflow engine. Finally, it invokes the target workflow engine to execute the customized business. In response to execution exceptions, it executes a reverse transaction program based on the customized business and outputs the reverse transaction result information. This achieves overall transactional consistency in the business process logic. By reversing abnormal transactions, it makes business development more convenient, easier to promote, and improves business processing efficiency and accuracy.

[0073] Figure 2 This is a flowchart illustrating a business processing method according to an embodiment of this application, as shown below. Figure 2 As shown, the business processing methods include:

[0074] Step S201: Receive a business processing request. In response to the detection that a corresponding customized business exists for the business processing request, match the customized business with each candidate engine interface, and determine the successfully matched candidate engine interface as the engine interface corresponding to the customized business.

[0075] Specifically, the executing entity can obtain the data to be processed and the expected output indicators corresponding to the detected customized business, match the expected output indicators with the indicators that each candidate engine interface can output, so as to obtain one or more matching engine interfaces, and automatically integrate the one or more matching engine interfaces to obtain the engine interface corresponding to the customized business.

[0076] Step S202: Invoke the business process integration framework to integrate the engine interface and generate the target workflow engine.

[0077] Specifically, automatically integrating one or more matching engine interfaces may include: calling a business process integration framework to execute an interface integration program, integrating one or more matching engine interfaces to obtain a target workflow engine that can handle the defined business.

[0078] Specifically, when generating the target workflow engine, an abstract class can be created, in which all one or more matching engine interfaces obtained above can be imported to form the target workflow engine. The functionality of the target workflow engine is then divided into three parts: First, preprocessing of process information, which involves processing the data provided to the target workflow engine in advance; second, processing of the data logic that the process needs to handle at this stage, which involves processing business data; and third, process processing, which involves processing the data from the process engine and propelling the process to the next step.

[0079] Step S203: Invoke the target workflow engine to execute customized business. In response to execution exceptions, execute the reverse transaction program based on the customized business and output the reverse transaction result information.

[0080] Because the workflow engine is an independent middleware system with its own database and transaction interfaces, distributed transaction issues arise when integrating it with business systems. If a transaction is successful, the target workflow engine central hub can commit the transaction normally. If an anomaly occurs, a reverse transaction from the business logic is required for handling. When an anomaly occurs in the target workflow engine, a reverse transaction is performed on the upstream business logic, ensuring overall transaction consistency across the business process.

[0081] Figure 3 This is a flowchart illustrating a business processing method according to an embodiment of this application, as shown below. Figure 3 As shown, the business processing methods include:

[0082] Step S301: Receive a business processing request; in response to the detection that a corresponding customized business exists in the business processing request, obtain the first functional data to be implemented by the customized business and the second functional data that can be provided by each candidate engine interface.

[0083] The first functional data to be implemented by the business is defined, such as loan information processing, overdue information processing, and difference summary between different tables. This application embodiment does not specifically limit the first functional data. The second functional data that can be provided by each candidate engine interface may include task submission, task rollback, task retrieval, information processing, and information summary functions provided by each candidate engine interface. This application embodiment does not specifically limit the second functional data.

[0084] Step S302: Calculate the similarity between the first functional data and each of the second functional data, and determine the candidate engine interface that matches the customized business based on the similarity.

[0085] Specifically, the similarity between the first function data and each second function data can be determined by whether each second function data can cover the first function data. If they can, the similarity is high.

[0086] The similarity scores are sorted in descending order to select a subset of engine interfaces as candidate engine interfaces to match the customized business.

[0087] Step S303: The successfully matched candidate engine interface is determined as the engine interface corresponding to the customized business.

[0088] Interfaces with a similarity greater than a preset similarity threshold among the candidate engine interfaces are identified as successfully matched candidate engine interfaces, and then used as engine interfaces corresponding to customized business. There can be one or more of these interfaces.

[0089] Step S304: Invoke the business process integration framework to integrate the engine interface and generate the target workflow engine.

[0090] The business process integration framework is integrated with the various engine interfaces corresponding to customized business processes to form a basic architecture that supports complex business logic at the top and workflow engines at the bottom—this is the target workflow engine. The functions at the top include some basic functionalities, such as parameter settings for submitting processes and handling request parameters for pending queries. The functions at the bottom constitute the workflow engine.

[0091] Step S305: Invoke the target workflow engine to execute the customized business. In response to an execution exception, execute the reverse transaction program based on the customized business and output the reverse transaction result information.

[0092] The defined business logic is executed by calling the engine logic in the target workflow engine. In the event of an exception, a reverse transaction procedure is invoked to execute the reverse transaction and output the corresponding reverse transaction result information. Since the workflow engine is an independent middleware system with its own database and interface for transaction operations, distributed transaction issues arise when integrating with the business system. If the transaction is successful, the target workflow engine central unit can commit the transaction normally. If an exception occurs, it needs to be handled using a reverse transaction. When an exception occurs in the target workflow engine, a reverse transaction is performed on the upstream business logic, achieving overall transactional consistency in the business process logic.

[0093] The embodiments of this application can effectively bind business processes on the business chain to the processes defined by the workflow engine, thereby better realizing the flow of business system data in various processing stages of the company.

[0094] Figure 4 This is a flowchart illustrating a business processing method according to an embodiment of this application. The business process integration framework of this application embodiment may include a business logic function module, a business process integration central function module, a workflow engine function integration module, and a workflow engine module. For example, such as... Figure 4 As shown, the business logic module first calls business function A to operate the business process. Then, it calls the business process integration hub module to process business process parameters. Next, it calls the workflow engine integration module to integrate the workflow interface and encapsulate commonly used workflow functions, such as task submission, task rollback, task retrieval, and other workflow operations. Then, it calls the business process integration hub to execute the integrated business process operation functions and determine if there is an exception. If an exception occurs, it performs reverse transaction processing, and the process terminates after the reverse processing. If no exception occurs, the process terminates directly.

[0095] This application provides a business process integration framework that can: encapsulate commonly used interfaces of the workflow engine; create a central hub for business module implementation and process engine related functions to schedule business process logic; integrate specific business logic processing; and perform reverse transaction processing.

[0096] Specifically, the workflow engine interface is encapsulated: This step encapsulates commonly used interfaces of the workflow engine, introducing the most basic process functions of the workflow engine into the framework. This part can adapt to different workflows depending on the engine, and it is also the core function of the underlying workflow, which depends on the workflow engine. Common process functions provided by the workflow engine API, including task submission, task rollback, and task retrieval, are encapsulated separately. This encapsulation includes adding corresponding input parameters, adding corresponding business logic processing, adding compatibility handling for diverse workflow engines, and various exception handling methods. After encapsulation, the engine interface becomes more generalized and business-oriented, while also supporting multiple commonly used workflow engines.

[0097] The central hub integrating business modules and the workflow engine: This part integrates the business process integration framework with the encapsulated engine interface, forming a basic architecture that supports complex business logic at the top and the workflow engine at the bottom. The upper-level functionality combines basic features, including parameter settings for submitting processes and handling request parameters for pending queries. The lower-level functionality is the workflow engine itself. The concrete implementation uses an abstract class at the top level, importing all the encapsulated workflow engine interfaces into this abstract class, which is divided into three parts: First, preprocessing of process information, where the data provided to the encapsulated workflow engine is processed in advance; second, the data logic that the process needs to process at this stage, which is independent of the process itself and involves processing business data; third, process processing, where the workflow engine's data is processed, propelling the process to the next step. Since the workflow engine is a standalone middleware system, it functions as a state machine outside of the business logic. These three parts effectively bind the business logic in the business chain to the processes defined by the workflow engine, better facilitating the flow of business system data across various processing stages within the company.

[0098] Business Reverse Transactions: Because the workflow engine is an independent middleware system with its own database and transaction handling interfaces, distributed transaction issues arise when integrating with business systems. If transactions are successful, the engine central process commits the transactions normally. However, in case of an exception, business reverse transactions are required. When a downstream engine encounters an exception, a reverse transaction is performed on the upstream business logic, ensuring overall transactional consistency across the business process.

[0099] This application's embodiments can implement a central framework that connects upstream and downstream processes, and can achieve transaction consistency. The central framework not only shields the process details of business development, allowing focus only on the business logic specific to each business process point, but also simplifies business process development by eliminating the need for any development work if no specific logic exists, allowing direct use of the framework's common functionalities. Regarding transaction consistency, when using business development for logic development, there's no need to consider the distributed transaction consistency between business processes and workflows. The framework handles abnormal transactions through reverse processing, making business development more convenient.

[0100] This application provides a business process framework. In an approval process system, after the business logic is configured with the corresponding flowchart through a workflow engine, the business flow of the approval process system can be easily implemented through this framework. The implementation of this application not only effectively reduces the development cost of the process system but also eliminates dependence on a specific workflow engine, allowing for compatibility with various workflow engines. This makes future feature upgrades and other process-related business operations easier to handle.

[0101] Figure 5 This is a schematic diagram of a unit of a service processing apparatus according to an embodiment of this application. For example... Figure 5 As shown, the business processing device 500 includes a receiving unit 501, an engine generation unit 502, and an execution unit 503.

[0102] The receiving unit 501 is configured to receive service processing requests and, in response to detecting that a corresponding customized service exists in the service processing request, determine the corresponding engine interface.

[0103] Engine generation unit 502 is configured to call the business process integration framework to integrate the engine interface and then generate the target workflow engine.

[0104] Execution unit 503 is configured to invoke the target workflow engine to execute customized business, and in response to execution exceptions, execute a reverse transaction program based on the customized business and output reverse transaction result information.

[0105] In some embodiments, the receiving unit 501 is further configured to: obtain each service identifier corresponding to the service processing request; match each service identifier with the identifiers in a preset service identifier pool; if there is an identifier in each service identifier that does not match the identifiers in the preset service identifier pool, then determine the service corresponding to the mismatched identifier as a customized service.

[0106] In some embodiments, the receiving unit 501 is further configured to: match the customized service with each candidate engine interface, and determine the successfully matched candidate engine interface as the engine interface corresponding to the customized service.

[0107] In some embodiments, the receiving unit 501 is further configured to: acquire first functional data to be implemented by the customized service and second functional data that can be provided by each candidate engine interface; calculate the similarity between the first functional data and each second functional data, and determine the candidate engine interface that matches the customized service based on the similarity.

[0108] In some embodiments, the engine generation unit 502 is further configured to match each business process point of the business process integration framework with the engine interface, and then integrate the matched business process points and the engine interface.

[0109] In some embodiments, the engine generation unit 502 is further configured to: calculate the similarity between the attributes of each business process point in the business process integration framework and the attributes of the engine interface; and determine the business process node that matches the engine interface based on the similarity.

[0110] In some embodiments, the engine generation unit 502 is further configured to: insert the program corresponding to the engine interface into the program corresponding to the matched business process node to generate the target workflow engine.

[0111] It should be noted that the business processing method and business processing device in this application are related in terms of specific implementation content, so repeated content will not be described again.

[0112] Figure 6 An exemplary system architecture 600 is shown that can be applied to the business processing method or business processing apparatus of the embodiments of this application.

[0113] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0114] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0115] Terminal devices 601, 602, and 603 can be various electronic devices with business processing screens and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0116] Server 605 can be a server providing various services, such as a backend management server supporting business processing requests submitted by users using terminal devices 601, 602, and 603 (this is just an example). The backend management server can receive business processing requests, and in response to detecting a corresponding customized business within the request, determine the corresponding engine interface; invoke the business process integration framework to integrate the engine interface, thereby generating the target workflow engine; invoke the target workflow engine to execute the customized business; and in response to execution exceptions, execute a reverse transaction program based on the customized business and output the reverse transaction result information. This enables overall transactional consistency of the business process logic, and through reverse processing in abnormal transactions, makes business development more convenient, easier to promote, and improves business processing efficiency and accuracy.

[0117] It should be noted that the business processing method provided in this application embodiment is generally executed by server 605, and correspondingly, the business processing device is generally set in server 605.

[0118] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0119] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device according to the embodiments of this application. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0120] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the computer system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0121] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0122] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this application.

[0123] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0124] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0125] The units described in the embodiments of this application can be implemented in software or hardware. The described units can also be located in a processor; for example, a processor can be described as including a receiving unit, an engine generation unit, and an execution unit. The names of these units do not necessarily limit the specific unit itself.

[0126] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to receive a business processing request, determine the corresponding engine interface in response to detecting a corresponding customized business in the business processing request; invoke a business process integration framework to integrate the engine interface, thereby generating a target workflow engine; invoke the target workflow engine to execute the customized business; and, in response to an execution exception, execute a reverse transaction program based on the customized business and output reverse transaction result information.

[0127] The computer program product of this application includes a computer program that, when executed by a processor, implements the business processing method in the embodiments of this application.

[0128] According to the technical solution of the embodiments of this application, the overall transaction consistency of the business process logic can be achieved. In abnormal transactions, reverse processing can be used to make business development more convenient, easier to promote, and improve business processing efficiency and accuracy.

[0129] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A business processing method, characterized in that, include: Upon receiving a business processing request, and in response to detecting that the business processing request has a corresponding customized business, determine the corresponding engine interface; The business process integration framework is invoked to integrate the engine interface and generate the target workflow engine. The target workflow engine is invoked to execute the customized business. In response to an execution exception, a reverse transaction program is executed based on the customized business, and the reverse transaction result information is output. Before determining the corresponding engine interface, the method further includes: obtaining each business identifier corresponding to the business processing request; matching each business identifier with identifiers in a preset business identifier pool; if there is an identifier in each business identifier that does not match the identifiers in the preset business identifier pool, then the business corresponding to the non-matching identifier is determined as a customized business. The integration of the engine interface includes: matching each business process point of the business process integration framework with the engine interface, and then integrating the matched business process points and the engine interface. It also includes: segmenting the program corresponding to the matched business process node to obtain each segment program; inputting the program corresponding to the engine interface and each segment program into a long short-term memory neural network model to output the segment program associated with the program corresponding to the engine interface and the corresponding correlation degree; determining the target segment program based on the correlation degree; and then concatenating the program corresponding to the engine interface with the target segment program to generate the target workflow engine.

2. The method according to claim 1, characterized in that, The determination of the corresponding engine interface includes: The customized service is matched with each candidate engine interface, and the successfully matched candidate engine interface is determined as the engine interface corresponding to the customized service.

3. The method according to claim 2, characterized in that, The process of matching the customized service with each candidate engine interface includes: Obtain the first functional data to be implemented by the customized business and the second functional data that can be provided by each candidate engine interface; Calculate the similarity between the first functional data and each of the second functional data, and determine the candidate engine interface that matches the customized business based on the similarity.

4. The method according to claim 1, characterized in that, The matching of each business process point in the business process integration framework with the engine interface includes: Calculate the similarity between the attributes of each business process point in the business process integration framework and the attributes of the engine interface; The business process nodes that match the engine interface are determined based on the similarity.

5. The method according to claim 1, characterized in that, The target workflow generation engine includes: The program corresponding to the engine interface is inserted into the program corresponding to the matched business process node to generate the target workflow engine.

6. A business processing apparatus, characterized in that, include: The receiving unit is configured to receive a service processing request and, in response to detecting that the service processing request has a corresponding customized service, determine the corresponding engine interface. The engine generation unit is configured to call the business process integration framework to integrate the engine interface and thereby generate the target workflow engine; The execution unit is configured to invoke the target workflow engine to execute the customized business, and in response to an execution exception, execute a reverse transaction program based on the customized business and output reverse transaction result information. The receiving unit is further configured to: obtain each service identifier corresponding to the service processing request; match each service identifier with the identifiers in a preset service identifier pool; if there is an identifier in each service identifier that does not match the identifiers in the preset service identifier pool, then determine the service corresponding to the non-matching identifier as a customized service. The engine generation unit is further configured to: match each business process point of the business process integration framework with the engine interface, and then integrate the matched business process points and the engine interface. The engine generation unit is further configured to: segment the program corresponding to the matched business process node to obtain each segment program; input the program corresponding to the engine interface and each segment program into a long short-term memory neural network model to output the segment program associated with the program corresponding to the engine interface and the corresponding correlation degree; determine the target segment program based on the correlation degree; and then concatenate the program corresponding to the engine interface with the target segment program to generate the target workflow engine.

7. The apparatus according to claim 6, characterized in that, The receiving unit is further configured to: The customized service is matched with each candidate engine interface, and the successfully matched candidate engine interface is determined as the engine interface corresponding to the customized service.

8. The apparatus according to claim 7, characterized in that, The receiving unit is further configured to: Obtain the first functional data to be implemented by the customized business and the second functional data that can be provided by each candidate engine interface; Calculate the similarity between the first functional data and each of the second functional data, and determine the candidate engine interface that matches the customized business based on the similarity.

9. The apparatus according to claim 6, characterized in that, The engine generation unit is further configured to: Calculate the similarity between the attributes of each business process point in the business process integration framework and the attributes of the engine interface; The business process nodes that match the engine interface are determined based on the similarity.

10. A business processing electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-5.

11. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-5.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-5.

Images