Decision engine execution file processing method, device and electronic equipment

Abstract

The present invention provides an executable file processing method, device and electronic device for a decision engine, the method comprising: determining the workflow of the decision engine; configuring the working environment corresponding to the decision engine based on the workflow of the decision engine; obtaining multiple versions of executable files corresponding to the decision engine; compiling each executable file to obtain an executable file corresponding to each executable file; storing each executable file in a target memory; when the decision engine needs to switch versions, controlling the decision engine to call the stored executable file through the target memory in the working environment to switch versions. By applying the method provided by the present invention, the decision engine does not need to rely on the decision platform when switching versions, avoiding the risks caused by the operation of the decision platform.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device and electronic equipment for processing execution files of a decision engine. Background Art

[0002] The risk control decision engine is the core of financial technology and is widely used in financial risk control, anti-fraud, anti-money laundering, anti-black and gray industries, compliance management and other fields. It needs to support the automated processing of a large number of businesses in real time, which can greatly relieve the bottleneck and efficiency of manual processing. At present, the online decision-making framework of financial business is mostly a peripheral decision platform lined with a decision engine execution component. Every time the decision engine execution version is changed, the entire peripheral decision platform often needs to cooperate.

[0003] In the prior art, due to the high coupling between the decision engine and the decision platform, each version switch requires the coordination of the decision platform, which greatly increases the risks that may be caused by the operation of the decision platform. Summary of the invention

[0004] In view of this, the present invention provides an execution file processing method, device and electronic device of a decision engine, wherein the method can avoid the risk caused by the operation of the decision platform when the decision engine performs version switching without relying on the decision platform.

[0005] A method for processing an execution file of a decision engine, comprising:

[0006] Determine the workflow of the decision engine;

[0007] Based on the workflow of the decision engine, configure the working environment corresponding to the decision engine;

[0008] Obtaining multiple versions of execution files corresponding to the decision engine;

[0009] Compiling each of the execution files to obtain an executable file corresponding to each of the execution files;

[0010] Storing each of the executable files in a preset target memory;

[0011] When the decision engine needs to switch versions, the decision engine is controlled to call the stored executable file through the target memory in the working environment to implement version switching.

[0012] In the above method, optionally, configuring the working environment corresponding to the decision engine based on the workflow of the decision engine includes:

[0013] Based on the workflow of the decision engine, determine an API for connecting the decision engine with a preset decision platform;

[0014] Parsing the API to obtain environment parameters required to run the decision engine;

[0015] A preset construction method is applied to construct a working environment corresponding to the decision engine based on the environmental parameters.

[0016] The above method may optionally further include:

[0017] Detecting whether the working environment can operate normally;

[0018] When the working environment cannot run normally, the working environment is initialized and re-detected to see whether it can run normally. When the working environment can run normally, the working environment is sent to a preset version container.

[0019] Optionally, the method described above compiles each of the executable files to obtain an executable file corresponding to each of the executable files, including:

[0020] Determine the operating format supported by the working environment;

[0021] The running codes in each of the execution files are format-converted according to the running format to obtain an executable file corresponding to each of the execution files.

[0022] The above method, optionally, after storing each of the executable files in a preset target memory, further comprises:

[0023] Running the decision engine in the working environment to simulate the decision engine switching each of the executable files through the target memory;

[0024] When simulating that the decision engine successfully switches each of the executable files, allowing the decision engine to perform a version switching operation;

[0025] When the simulation of the decision engine switching the executable files fails, the workflow of the decision engine is re-determined.

[0026] In the above method, optionally, storing each executable file in a preset target memory includes:

[0027] Determine the application scenario of each executable file currently being applied;

[0028] Determine a storage method supported by the application scenario and a target storage device corresponding to the storage method;

[0029] Each of the executable files is stored in the target memory.

[0030] The above method may optionally further include:

[0031] Obtaining the file signature alias and version number corresponding to each of the executable files;

[0032] Based on the file signature alias and version number corresponding to each executable file, a unique identification code corresponding to each executable file is generated, and the unique identification code is a storage identifier of the corresponding executable file stored in the target memory.

[0033] In the above method, optionally, controlling the decision engine to call the stored executable file through the target memory in the working environment to implement version switching includes:

[0034] Determine the target version number of the target version to be switched to by the decision engine;

[0035] Controlling the decision engine to apply a preset callback program in the working environment to search for a target unique identification code matching the target version number in the target memory;

[0036] The decision engine is controlled to obtain a target executable file corresponding to the target unique identification code, and a version switch of the decision engine is implemented based on the target executable file.

[0037] An execution file processing device of a decision engine, comprising:

[0038] A determination unit, used to determine the workflow of the decision engine;

[0039] A configuration unit, configured to configure a working environment corresponding to the decision engine based on the workflow of the decision engine;

[0040] An acquisition unit, used to acquire multiple versions of execution files corresponding to the decision engine;

[0041] A compiling unit, used to compile each of the execution files to obtain an executable file corresponding to each of the execution files;

[0042] A storage unit, used for storing each of the executable files in a preset target storage;

[0043] The control unit is used to control the decision engine to call the stored executable file through the target memory in the working environment to implement version switching when the decision engine needs to switch versions.

[0044] A storage medium includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the above-mentioned decision engine execution file processing method.

[0045] An electronic device includes a memory and one or more instructions, wherein the one or more instructions are stored in the memory and are configured to be executed by one or more processors to execute the execution file processing method of the decision engine.

[0046] Compared with the prior art, the present invention has the following advantages:

[0047] The present invention provides an executable file processing method for a decision engine, comprising: determining the workflow of the decision engine; configuring the working environment corresponding to the decision engine based on the workflow of the decision engine; obtaining multiple versions of executable files corresponding to the decision engine; compiling each of the executable files to obtain an executable file corresponding to each of the executable files; storing each of the executable files in a preset target memory; when the decision engine needs to switch versions, controlling the decision engine to call the stored executable file through the target memory in the working environment to achieve version switching. By applying the method provided by the present invention, the decision engine can switch versions without relying on the decision platform, thus avoiding the risks caused by the operation of the decision platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0049] Figure 1 A method flow chart of an execution file processing method of a policy engine provided by an embodiment of the present invention;

[0050] Figure 2 A flowchart of another method for processing an execution file of a policy engine provided by an embodiment of the present invention;

[0051] Figure 3 A flowchart of another method for processing an execution file of a policy engine provided by an embodiment of the present invention;

[0052] Figure 4 A flowchart of another method for processing an execution file of a policy engine provided by an embodiment of the present invention;

[0053] Figure 5A flowchart of another method for processing an execution file of a policy engine provided by an embodiment of the present invention;

[0054] Figure 6 A device structure diagram of an execution file processing device of a policy engine provided by an embodiment of the present invention;

[0055] Figure 7 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0057] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, the elements defined by the sentence "comprise one..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0058] The present invention can be used in many general or special computing device environments or configurations, such as personal computers, server computers, handheld or portable devices, tablet devices, multi-processor devices, distributed computing environments including any of the above devices or devices, etc.

[0059] The embodiment of the present invention provides a method for processing an execution file of a decision engine. The method can be applied to a variety of system platforms, and its execution subject can be a processor of a computer terminal or various mobile devices. The method flow chart of the method is as follows: Figure 1 As shown, specifically including:

[0060] S101: Determine the workflow of the decision engine.

[0061] In the present invention, the workflow of the decision engine has its own unique execution mode, which is usually connected with the decision platform to realize the execution of the decision engine workflow. At least one decision engine is set in a service system such as a financial system, and the workflows of each decision engine are different.

[0062] S102: Based on the workflow of the decision engine, configure a working environment corresponding to the decision engine.

[0063] In the present invention, the working environment of the decision engine is configured according to its workflow. The environment parameters required for the operation of the decision engine can be learned through the workflow, so as to configure the corresponding working environment.

[0064] The working environment is a standard operating context support environment.

[0065] S103: Acquire multiple versions of execution files corresponding to the decision engine.

[0066] In the present invention, the decision engine corresponds to multiple versions of execution files, and each execution file contains information such as the version number of its corresponding version and the file signature alias.

[0067] S104: Compile each of the execution files to obtain an executable file corresponding to each of the execution files.

[0068] Specifically, the process of compiling the executable file to obtain the executable file includes:

[0069] Determine the running format supported by the working environment; convert the running code in each of the execution files according to the running format to obtain an executable file corresponding to each of the execution files.

[0070] It is understandable that different working environments support different running formats for running executable files. The executable files are compiled and converted according to the running formats to obtain multiple versions of executable files. The versions of the compiled executable files are consistent with the versions of the corresponding executable files.

[0071] The executable file may be in the form of binary bytecode or byte stream.

[0072] S105: storing each of the executable files in a preset target memory.

[0073] It should be noted that if high-speed and stable switching is required, it needs to be maintained through a version control memory. In practical applications, there are many ways to construct a memory, by selecting one of the memories to store, maintain and store executable files.

[0074] Specifically, the process of storing the executable file may include:

[0075] Determine the application scenario of each executable file currently being applied;

[0076] Determine a storage method supported by the application scenario and a target storage device corresponding to the storage method;

[0077] Each of the executable files is stored in the target memory.

[0078] It is understandable that for multiple application scenarios, each application scenario supports an optimal storage method. Determine the application scenario where each executable file needs to be applied, select the optimal storage method according to the application scenario, and store each executable file in the target memory according to the storage method.

[0079] Optionally, the method provided in the embodiment of the present invention may include the following three storage methods:

[0080] (1) Online physical storage, which is to compile the executable file into an executable state, usually in the form of binary bytecode or byte stream. After serialization, it is directly stored in the disk (database).

[0081] (2) Distributed cache server storage: storing the bytecode or byte stream execution state described in (1) in a highly stable and high-throughput distributed cache server.

[0082] (3) Local memory storage: the bytecode or byte stream execution state described in (1) is stored in the local execution memory. This method can greatly improve the operation performance.

[0083] The method provided in the embodiment of the present invention includes but is not limited to the above-mentioned disk, distributed cache server and local memory for storing executable files. Among them, storage method (3) has the best performance, but because it is stored in local memory, it poses a greater challenge to local server resources.

[0084] Furthermore, after each executable file is stored in the target memory, a unique identification code corresponding to each executable file may be set to facilitate subsequent calls to each version of the executable file. The specific process may include:

[0085] Obtaining the file signature alias and version number corresponding to each of the executable files;

[0086] Based on the file signature alias and version number corresponding to each executable file, a unique identification code corresponding to each executable file is generated, and the unique identification code is a storage identifier of the corresponding executable file stored in the target memory.

[0087] It can be understood that the unique identification code of each executable file is composed of the file signature alias and version number corresponding to the executable file.

[0088] Furthermore, after the executable file is stored in the target memory, the operation process of the decision engine can be simulated in the working environment to further ensure the reliability of the version switching function. The specific process is:

[0089] The decision engine is run in the working environment to simulate the decision engine switching the executable files through the target memory; when the simulation of the decision engine successfully switches the executable files, the decision engine is allowed to perform a version switching operation and execute S106; when the simulation of the decision engine switching the executable files fails, the process returns to execute S101 to redefine the workflow of the decision engine.

[0090] In the present invention, based on the above steps S101 to S105, multi-version storage of the decision engine executable file has been completed. Since each version of the executable file has been processed as an executable file that can be directly executed before storage, it is only necessary to call the callback interface of the version control memory to take out the specified version of the executable file. Therefore, the decision platform can be decoupled from the decision engine version iteration, and multi-version fast and efficient switching can be achieved through simple configuration. It can be understood that all stored versions of the executable file are co-existing on the decision platform. In order to further ensure the reliability of the function, a complete verification and assurance mechanism is required. The executable file is verified for legitimacy according to relevant standards, such as calling the API pre-execution to check whether it is normal, and simulating the decision engine to switch each executable file through the target memory.

[0091] S106: When the decision engine needs to switch versions, control the decision engine to call the stored executable file through the target memory in the working environment to switch versions.

[0092] In the present invention, the decision engine implements version switching without relying on the decision platform.

[0093] In the executable file processing method of the decision engine provided in the embodiment of the present invention, the workflow of the decision engine is determined, and the working environment is configured based on the workflow. Multiple versions of executable files corresponding to the decision engine are obtained, and the executable files are compiled to obtain executable files, which are in the form of binary bytecode or byte stream. The storage method of each version of the executable file is determined, and each version of the executable file is stored in a memory corresponding to the storage method. The decision engine is run, and the process of switching versions of the decision engine is simulated. After the simulation is successful, the decision engine is controlled to switch versions without relying on the decision platform.

[0094] It should be noted that when a new version of an execution file corresponding to a new decision engine is added, the new version of the execution file is compiled to obtain a new version of an executable file, and the executable file is stored in the target memory.

[0095] It should also be noted that the executable files in the target memory are sorted in the form of an execution stack and are sorted according to the versions of the executable files.

[0096] By applying the method provided in the embodiment of the present invention, the decision engine execution file is extracted, converted into an executable file, and multiple versions of the executable file are stored without relying on the decision platform, thereby avoiding the risks caused by the operation of the decision platform and ensuring the switching efficiency of the decision engine when switching versions.

[0097] In the method provided in the embodiment of the present invention, based on the workflow of the decision engine, the specific process of configuring the working environment corresponding to the decision engine is as follows: Figure 2 As shown, it may specifically include:

[0098] S201: Based on the workflow of the decision engine, determine an API for connecting the decision engine with a preset decision platform.

[0099] In the present invention, each decision engine execution process has its own unique execution mode, and usually the decision platform is connected according to the access API (Application Programming Interface) of different engines.

[0100] S202: Parse the API to obtain environment parameters required to run the decision engine.

[0101] In the present invention, in order to ensure the throughput and stability of the decision platform, the decision platform is usually integrated into the execution process of the decision engine in the form of SDK, so the API is parsed to obtain the working parameters required for the operation.

[0102] Among them, working parameters include input parameter format, output parameter format, log parameters and other parameters.

[0103] S203: Apply a preset construction method to construct a working environment corresponding to the decision engine based on the environmental parameters.

[0104] In the present invention, a universal working environment is constructed through an official guidance access method, namely, an application construction method.

[0105] Furthermore, after the working environment is constructed, the working environment can be further verified. The verification process is as follows: Figure 3 As shown, the specific process is:

[0106] S301: Detect whether the working environment can operate normally.

[0107] In the present invention, the code parameters running in the working environment and the instructions corresponding to the parameters and the execution order of the instructions are determined, and the prerequisites for executing the decision engine are verified according to the instruction order and code parameters required by the decision engine, so as to determine whether the working environment can operate normally. When the working environment cannot operate normally, S302 is executed; when the working environment can operate normally, S303 is executed.

[0108] S302: Initialize the working environment.

[0109] Specifically, after initializing the working environment, the process returns to continue executing S301.

[0110] S303: Send the working environment to a preset version container.

[0111] The version container is used to control multiple versions of executable files.

[0112] In the method provided by the embodiment of the present invention, an API connected to the decision platform is determined, the API is parsed to obtain environment parameters, and a working environment is constructed based on the environment parameters. After the construction of the working environment is completed, the working environment can be further inspected to determine whether the working environment can operate normally. If not, the working environment needs to be initialized and the initialized working environment is re-inspected until the current working environment after the initialization can operate normally, and then it is initialized into the version container.

[0113] In the embodiment of the present invention, when constructing the working environment, the execution files of each version of the decision engine are converted into executable files, and each executable file is stored. In the storage process, a unique identification code corresponding to each executable file needs to be set to identify the version of each executable file stored in the target memory through the unique identification code.

[0114] Specifically, based on the content of S107 above, when the control decision engine needs to switch versions, the process of calling the stored executable file through the target memory to implement the version switching is as follows: Figure 4 As shown, the specific process is:

[0115] S401: Determine the target version number of the target version to be switched to by the decision engine.

[0116] S402: Control the decision engine to apply a preset callback program in the working environment to search for a target unique identification code matching the target version number in the target memory.

[0117] The callback program can be used to call back the interface of the target storage, find the target unique identification code that matches the target version number, and thus retrieve the executable file of the specified version.

[0118] S403: Control the decision engine to obtain the target executable file corresponding to the target unique identification code, and implement version switching of the decision engine based on the target executable file.

[0119] In the method provided by the embodiment of the present invention, S401 to S403 describe the process of switching versions of the decision engine. When it is detected that the decision engine needs to switch versions, the target version number of the target version to be switched is determined, and the target unique identification code matching the target version number is searched according to the target version number to obtain the corresponding target executable file, and the decision engine directly switches versions according to the target executable file. Through the method provided by the present invention, it can be achieved that the decision engine does not need to rely on the decision platform when switching versions, thereby achieving the purpose of decoupling the decision engine from the decision platform.

[0120] Based on the method provided in the above embodiment, the specific implementation process of the embodiment of the present invention is as follows Figure 5 As shown, these include the following:

[0121] 1) Automatic analysis and decision engine component workflow:

[0122] The decision engine execution process has its own unique execution method. Usually, the decision platform is connected according to the access API of different engines. As mentioned above, in order to ensure the throughput and stability of the decision platform, the decision platform is usually integrated into the decision engine execution process in the form of SDK. We call this integration process the decision engine execution component. The first step is to analyze different working environments according to different decision engines.

[0123] 2) Working environment required to assemble the decision engine:

[0124] Through step 1), we can accurately know the environment parameters required for the current decision engine to run, including input parameter format, output parameter format, log parameters and other parameters. Next, we need to use the general construction method to build the working environment required by the current decision engine. We can simulate the most standard working environment that meets the decision engine itself according to the internal execution process of the decision engine. It can be obtained through the following methods:

[0125] A. Obtain the execution state parameters required for operation by parsing the relevant APIs, and use these parameters to build a standard operation state environment:

[0126] B. Build a general operating environment through official guidance access

[0127] 3) Secure storage and support for high-speed switching of multiple versions:

[0128] Through step 2), the standard running state context support environment has been obtained. For multi-version executable files, if you want to switch quickly and stably, you need to maintain them through version control storage. The storage can be built mainly in the following three ways:

[0129] (1) Online physical storage, that is, compiling the executable file into an executable state, usually in the form of binary bytecode or byte stream. After serialization, it is directly stored in the disk (database). The executable file's unique signature alias plus the version number is used as the storage identifier.

[0130] (2) Distributed cache server storage: the bytecode or byte stream execution state described in (1) is stored in a highly stable and high-throughput distributed cache server, with the signature alias unique to the executable file plus the version number as the storage identifier.

[0131] (3) Local memory storage: The bytecode or byte stream execution state described in (1) is stored in the local execution memory. This method can greatly improve the operation performance. The signature alias unique to the executable file plus the version number is used as the storage identifier.

[0132] The above three methods can be selected for different scenarios. Among them, method (3) has the best performance, but it is a big challenge for local server resources because it is stored in local memory.

[0133] 4) Verification and assurance:

[0134] Through the above steps, the multi-version storage of the decision engine executable file has been completed. Since each version of the executable file has been processed into an executable state that can be directly executed before storage, it is only necessary to call the callback interface of the version control storage device to retrieve the executable file of the specified version. At this point, the decision platform can be decoupled from the decision engine version iteration, and fast and efficient switching of multiple versions can be achieved through simple configuration. In other words, it can be understood that all stored versions of the executable files exist together on the decision platform. In order to further ensure the reliability of the function, a complete verification and assurance mechanism is required. The execution state file is verified for legitimacy according to relevant standards, such as calling the API pre-execution to check whether it is normal. If it is normal, the version switching operation can be completed. If it is not normal, you can jump to the first step and try again.

[0135] Among them, in step 2), building the working environment also requires determining whether the working environment is running normally. If it is not normal, the working environment is initialized, and if it is normal, the working environment is initialized to the version container. In step 3), after generating the current version unique identification code of each executable file, the executable files of each version are sorted according to the sorting method of the execution stack.

[0136] The specific implementation processes and derivative methods of the above-mentioned embodiments are all within the protection scope of the present invention.

[0137] and Figure 1 Corresponding to the method described above, the embodiment of the present invention further provides an execution file processing device of a decision engine, for Figure 1 In the specific implementation of the method, the execution file processing device of the decision engine provided in the embodiment of the present invention can be applied to a computer terminal or various mobile devices, and its structural diagram is as follows Figure 6 As shown, specifically including:

[0138] A determination unit 601, used to determine the workflow of the decision engine;

[0139] A configuration unit 602, configured to configure a working environment corresponding to the decision engine based on the workflow of the decision engine;

[0140] An acquisition unit 603 is used to acquire multiple versions of execution files corresponding to the decision engine;

[0141] A compiling unit 604 is used to compile each of the execution files to obtain an executable file corresponding to each of the execution files;

[0142] The storage unit 605 is used to store each executable file in a preset target storage;

[0143] The control unit 606 is used to control the decision engine to call the stored executable file through the target memory in the working environment to implement version switching when the decision engine needs to switch versions.

[0144] In the executable file processing device of the decision engine provided by the embodiment of the present invention, the workflow of the decision engine is determined, and the working environment is configured based on the workflow. Multiple versions of executable files corresponding to the decision engine are obtained, and the executable files are compiled to obtain executable files, which are in the form of binary bytecode or byte stream. The storage method of each version of the executable file is determined, and each version of the executable file is stored in a memory corresponding to the storage method. When the decision engine needs to switch versions, the decision engine can achieve version switching without relying on the decision platform.

[0145] By using the device provided in the embodiment of the present invention, the decision engine execution file is extracted, converted into an executable file, and multiple versions of the executable file are stored without relying on the decision platform, thereby avoiding the risks caused by the operation of the decision platform and ensuring the switching efficiency of the decision engine when switching versions.

[0146] In the device provided by the embodiment of the present invention, the configuration unit 602 includes:

[0147] A first determination subunit is used to determine an API for connecting the decision engine with a preset decision platform based on the workflow of the decision engine;

[0148] A parsing subunit, used to parse the API to obtain environment parameters required to run the decision engine;

[0149] The construction subunit is used to apply a preset construction method to construct a working environment corresponding to the decision engine based on the environmental parameters.

[0150] The device provided in the embodiment of the present invention further includes:

[0151] The detection unit is used to detect whether the working environment can operate normally; when the working environment cannot operate normally, the working environment is initialized and re-detected whether the working environment can operate normally, until the working environment can operate normally, the working environment is sent to a preset version container.

[0152] In the device provided by the embodiment of the present invention, the compiling unit 604 includes:

[0153] A second determining subunit is used to determine the operation format supported by the working environment;

[0154] The conversion subunit is used to convert the running code in each of the execution files according to the running format to obtain an executable file corresponding to each of the execution files.

[0155] In the device provided by the embodiment of the present invention, the storage unit 605 includes:

[0156] A third determining subunit is used to determine the application scenario of each executable file currently being applied;

[0157] A fourth determining subunit, used to determine a storage method supported by the application scenario and a target storage device corresponding to the storage method;

[0158] The storage subunit is used to store each of the executable files in the target memory.

[0159] The device provided in the embodiment of the present invention further includes:

[0160] A simulation unit is used to run the decision engine in the working environment, simulate the decision engine switching each of the executable files through the target memory; when the simulation of the decision engine successfully switches each of the executable files, allow the decision engine to perform a version switching operation; when the simulation of the decision engine fails to switch each of the executable files, redefine the workflow of the decision engine.

[0161] The device provided in the embodiment of the present invention further includes:

[0162] An acquisition subunit, used to acquire a file signature alias and a version number corresponding to each of the executable files;

[0163] A generating subunit is used to generate a unique identification code corresponding to each executable file based on the file signature alias and version number corresponding to each executable file, wherein the unique identification code is a storage identifier of the executable file corresponding to the executable file stored in the target memory.

[0164] In the device provided by the embodiment of the present invention, the control unit 607 includes:

[0165] A fifth determining subunit, configured to determine a target version number of a target version to be switched to by the decision engine;

[0166] A first control subunit, configured to control the decision engine to apply a preset callback program in the working environment to search for a target unique identification code matching the target version number in the target memory;

[0167] The second control subunit is used to control the decision engine to obtain the target executable file corresponding to the target unique identification code, and implement version switching of the decision engine based on the target executable file.

[0168] The specific working process of each unit and sub-unit in the execution file processing device of the decision engine disclosed in the above embodiment of the present invention can be found in the corresponding content of the execution file processing method of the decision engine disclosed in the above embodiment of the present invention, and will not be repeated here.

[0169] An embodiment of the present invention further provides a storage medium, which includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the execution file processing method of the decision engine.

[0170] The embodiment of the present invention further provides an electronic device, the structural diagram of which is shown in FIG. Figure 7 As shown, it specifically includes a memory 701 and one or more instructions 702, wherein the one or more instructions 702 are stored in the memory 701 and are configured to be executed by one or more processors 703 to perform the following operations:

[0171] Determine the workflow of the decision engine;

[0172] Based on the workflow of the decision engine, configure the working environment corresponding to the decision engine;

[0173] Obtaining multiple versions of execution files corresponding to the decision engine;

[0174] Compiling each of the execution files to obtain an executable file corresponding to each of the execution files;

[0175] Storing each of the executable files in a preset target memory;

[0176] When the decision engine needs to switch versions, the target memory calls the stored executable file to implement the version switch.

[0177] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

[0178] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein may be implemented by electronic hardware, computer software, or a combination of both.

[0179] In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0180] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing an execution file of a decision engine, characterized in that: include: Determine the workflow of the decision engine; Based on the workflow of the decision engine, configure the working environment corresponding to the decision engine; Obtaining multiple versions of execution files corresponding to the decision engine; Compiling each of the execution files to obtain an executable file corresponding to each of the execution files; Storing each of the executable files in a preset target memory; When the decision engine needs to switch versions, the decision engine is controlled to call the stored executable file through the target memory in the working environment to implement version switching.

2. The method according to claim 1, characterized in that The step of configuring a working environment corresponding to the decision engine based on the workflow of the decision engine includes: Based on the workflow of the decision engine, determine an API for connecting the decision engine with a preset decision platform; Parsing the API to obtain environment parameters required to run the decision engine; A preset construction method is applied to construct a working environment corresponding to the decision engine based on the environmental parameters.

3. The method according to claim 1 or 2, characterized in that: Also includes: Detecting whether the working environment can operate normally; When the working environment cannot run normally, the working environment is initialized and re-detected to see whether it can run normally. When the working environment can run normally, the working environment is sent to a preset version container.

4. The method according to claim 1, characterized in that The step of compiling each of the execution files to obtain an executable file corresponding to each of the execution files includes: Determine the operating format supported by the working environment; The running codes in each of the execution files are format-converted according to the running format to obtain an executable file corresponding to each of the execution files.

5. The method according to claim 1, characterized in that The step of storing each of the executable files in a preset target memory includes: Determine the application scenario of each executable file currently being applied; Determine a storage method supported by the application scenario and a target storage device corresponding to the storage method; Each of the executable files is stored in the target memory.

6. The method according to claim 5, characterized in that After storing each of the executable files in a preset target memory, the method further includes: Running the decision engine in the working environment to simulate the decision engine switching each of the executable files through the target memory; When simulating that the decision engine successfully switches each of the executable files, allowing the decision engine to perform a version switching operation; When the simulation of the decision engine switching the executable files fails, the workflow of the decision engine is re-determined.

7. The method according to claim 5, characterized in that Also includes: Obtaining the file signature alias and version number corresponding to each of the executable files; Based on the file signature alias and version number corresponding to each executable file, a unique identification code corresponding to each executable file is generated, and the unique identification code is a storage identifier of the corresponding executable file stored in the target memory.

8. The method according to claim 6 or 7, characterized in that: The step of controlling the decision engine to call the stored executable file through the target memory in the working environment to implement version switching includes: Determine the target version number of the target version to be switched to by the decision engine; Controlling the decision engine to apply a preset callback program in the working environment to search for a target unique identification code matching the target version number in the target memory; The decision engine is controlled to obtain a target executable file corresponding to the target unique identification code, and a version switch of the decision engine is implemented based on the target executable file.

9. An execution file processing device of a decision engine, characterized in that: include: A determination unit, used to determine the workflow of the decision engine; A configuration unit, configured to configure a working environment corresponding to the decision engine based on the workflow of the decision engine; An acquisition unit, used to acquire multiple versions of execution files corresponding to the decision engine; A compiling unit, used to compile each of the execution files to obtain an executable file corresponding to each of the execution files; A storage unit, used for storing each of the executable files in a preset target storage; The control unit is used to control the decision engine to call the stored executable file through the target memory in the working environment to implement version switching when the decision engine needs to switch versions.

10. An electronic device comprising a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by one or more processors to execute the execution file processing method of the decision engine as described in any one of claims 1 to 8.

Images