Software running method and device, software system, electronic equipment, medium and product

Abstract

The present disclosure provides a software running method and device, a software system, an electronic device, a medium and a product, relates to the technical field of computers, in particular to the field of space-time big data. The specific implementation scheme is: based on the engine start request sent by the engineering end, starting the engine process corresponding to the fusion engine; using the engine process to perform the following operations: obtaining at least one service function registered by the policy end in the fusion engine; based on at least one service function, generating a space-time service interface; based on the space-time service interface, the engineering end and the policy end correspond to the interaction of the target service function corresponding service in at least one service function. The technical scheme of the present disclosure improves the service efficiency between the engineering end and the policy end.

Description

Technical Field

[0001] This disclosure relates to the field of spatiotemporal big data in the field of computer technology, and in particular to a software operation method and apparatus, software system, electronic device, medium, and product. Background Technology

[0002] With the continuous development of technology, software types are becoming increasingly diverse. Generally, based on their functions and roles, software code can be divided into engineering-side code and strategy-side code. Engineering-side code typically refers to code related to the application scenario, which displays relevant application content to the user. Strategy-side code refers to the core algorithms that implement the application logic and is independent of the scenario.

[0003] In existing technologies, the engineering and strategy sides are written in different programming languages. The engineering side can be written in languages ​​such as Java and Scala, while the strategy side can be written in languages ​​such as Python. Code written in different programming languages ​​cannot directly transmit data or information. In actual operation, separate running processes need to be established for the engineering and strategy sides. Then, in practical applications, it is necessary to constantly switch between the engineering and strategy side processes to complete application processing normally. However, this approach requires constant process switching, resulting in excessively low application processing efficiency. Summary of the Invention

[0004] This disclosure provides a software operation method, apparatus, software system, electronic device, medium, and product for achieving efficient service between the engineering end and the strategy end.

[0005] According to a first aspect of this disclosure, a software operation method is provided, the method being applied to a fusion engine, the fusion engine having communication connections with both the engineering end and the strategy end of a software system, the method comprising:

[0006] Based on the engine start request sent by the engineering side, start the engine process corresponding to the fusion engine;

[0007] The engine process performs the following operations:

[0008] Obtain at least one service function registered by the strategy side in the fusion engine;

[0009] Generate a spatiotemporal service interface based on at least one service function;

[0010] The interaction between the engineering end and the strategy end is based on the spatiotemporal service interface, which corresponds to the service corresponding to the target service function in at least one service function.

[0011] According to a second aspect of this disclosure, a software operation method is provided, the method being applied to an engineering end, the software system further including a strategy end, and a fusion engine having communication connections with both the engineering end and the strategy end, the method comprising:

[0012] In response to a user-triggered usage request, obtain the service request data provided by the user;

[0013] Generate an engine start request for the fusion engine and send the engine start request to the fusion engine; the engine start request instructs the fusion engine to start the engine process to provide the target service function in the spatiotemporal service interface to the engineering end; the target service function is one of at least one service function registered by the strategy end in the fusion engine;

[0014] Based on the spatiotemporal service interface, the interaction between the execution and strategy ends corresponds to the service corresponding to the target service function.

[0015] According to a third aspect of this disclosure, a software operation method is provided. The method is used on a strategy end, and the software system further includes an engineering end and a fusion engine that has communication connections with both the engineering end and the strategy end. The method includes:

[0016] Send a function registration request for at least one service function to the fusion engine; the registration request instructs the fusion engine to generate a spatiotemporal service interface based on at least one service function; the spatiotemporal service interface is used to provide function information of the target service function in at least one service function to the engineering end;

[0017] Based on the spatiotemporal service interface, the interaction between the execution and engineering sides corresponds to the service corresponding to the target service function.

[0018] According to a fourth aspect of this disclosure, a software operating system is provided, comprising: an engineering end, a strategy end, and a fusion engine that has communication connections with both the engineering end and the strategy end;

[0019] The engineering side is used to: respond to user-triggered usage requests and obtain service request data provided by the user; generate engine startup requests for the fusion engine and send the engine startup requests to the fusion engine; and, based on the spatiotemporal service interface, execute interactions with the strategy side corresponding to the services corresponding to the target service functions.

[0020] The fusion engine is used to: start the engine process corresponding to the fusion engine based on the engine start request sent by the engineering side; and use the engine process to perform the following operations: obtain at least one service function registered by the strategy side in the fusion engine; generate a spatiotemporal service interface based on the at least one service function; and perform interaction between the engineering side and the strategy side for the service corresponding to the target service function in the at least one service function based on the spatiotemporal service interface.

[0021] The strategy side is used to: send function registration requests for at least one service function to the fusion engine; and perform interactions between the strategy side and the engineering side corresponding to the target service function based on the spatiotemporal service interface.

[0022] According to a fifth aspect of this disclosure, a software execution apparatus is provided, the apparatus being located in a fusion engine, the fusion engine having communication connections with both the engineering end and the strategy end of a software system, the apparatus comprising:

[0023] The process startup unit is used to start the engine process corresponding to the fusion engine based on the engine startup request sent by the engineering side.

[0024] The engine process performs the following operations:

[0025] The function registration unit is used to obtain at least one service function registered by the strategy side in the fusion engine;

[0026] An interface generation unit is used to generate a spatiotemporal service interface based on at least one service function.

[0027] The first interaction unit is used to conduct interaction between the engineering end and the strategy end based on the spatiotemporal service interface, corresponding to the service corresponding to the target service function in at least one service function.

[0028] According to a sixth aspect of this disclosure, a software running apparatus is provided, the apparatus being located at an engineering end, the software system further including a strategy end, and a fusion engine having communication connections with both the engineering end and the strategy end, the apparatus comprising:

[0029] The request and response unit is used to respond to user-triggered usage requests and to receive service request data provided by the user.

[0030] The startup generation unit is used to generate an engine startup request for the fusion engine and send the engine startup request to the fusion engine. The engine startup request instructs the fusion engine to start the engine process to provide the target service function in the spatiotemporal service interface to the engineering end. The target service function is one of at least one service function registered by the strategy end in the fusion engine.

[0031] The second interaction unit is used to perform the interaction between the strategy end and the service corresponding to the target service function, based on the spatiotemporal service interface.

[0032] According to a seventh aspect of this disclosure, a software running apparatus is provided, the apparatus being located at a strategy end, the software system further comprising: an engineering end and a fusion engine having communication connections with both the engineering end and the strategy end, the method comprising:

[0033] The registration request unit is used to send a function registration request for at least one service function to the fusion engine; the registration request instructs the fusion engine to generate a spatiotemporal service interface based on at least one service function; the spatiotemporal service interface is used to provide function information of the target service function in at least one service function to the engineering end;

[0034] The third interaction unit is used to perform the interaction between the project side and the service corresponding to the target service function, based on the spatiotemporal service interface.

[0035] According to an eighth aspect of this disclosure, an electronic device is provided, comprising:

[0036] At least one processor; and

[0037] A memory that is communicatively connected to at least one processor; wherein,

[0038] The memory stores instructions that can be executed by at least one processor, such that the at least one processor is able to perform the method of any one of the first, second, or third aspects.

[0039] According to a ninth aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause a computer to perform the method of any one of the first, second, or third aspects.

[0040] According to a tenth aspect of this disclosure, a computer program product is provided, comprising: a computer program stored in a readable storage medium, at least one processor of an electronic device being able to read the computer program from the readable storage medium, and the at least one processor executing the computer program causing the electronic device to perform the methods of any one of the first, second, or third aspects.

[0041] The technology disclosed herein solves the problem of low application processing efficiency between the engineering end and the strategy end. By establishing a communication bridge between the engineering end and the strategy end through a fusion engine, the drawback of the engineering end and the strategy end being unable to communicate directly can be resolved. The engineering end and the strategy end can complete service interaction in the engine process, avoiding repeated switching and calling of the engineering end process and the strategy end process, improving data transmission efficiency, and thus improving the application of the engineering end and the strategy end.

[0042] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0043] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0044] Figure 1 This is an application diagram of a software operation method provided in an embodiment of this disclosure;

[0045] Figure 2 This is a flowchart of one embodiment of a software operation method provided in this disclosure;

[0046] Figure 3 This is a flowchart of yet another embodiment of a software operation method provided in this disclosure;

[0047] Figure 4 This is a flowchart of yet another embodiment of a software operation method provided in this disclosure;

[0048] Figure 5 This is a flowchart of yet another embodiment of a software operation method provided in this disclosure;

[0049] Figure 6 This is a flowchart of yet another embodiment of a software operation method provided in this disclosure;

[0050] Figure 7 This is a schematic diagram of the structure of one embodiment of a software system provided in this disclosure;

[0051] Figure 8 This is a schematic diagram of the structure of one embodiment of a software running device provided in this disclosure;

[0052] Figure 9 This is a schematic diagram of the structure of yet another embodiment of a software running device provided in this disclosure;

[0053] Figure 10 This is a schematic diagram of the structure of yet another embodiment of a software running device provided in this disclosure;

[0054] Figure 11 This is a block diagram of an electronic device used to implement the software running method of the embodiments of this disclosure. Detailed Implementation

[0055] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0056] The technical solution disclosed herein can be applied to software systems, which may include engineering end and strategy end written in different programming languages ​​that cannot communicate directly. In addition, a fusion engine is added to establish a communication bridge between the engineering end and the strategy end, so as to solve the drawback that the engineering end and the strategy end cannot communicate directly.

[0057] In existing technologies, engineering and strategy interfaces written in different programming languages ​​cannot communicate directly, meaning accurate information transmission is impossible. To enable communication between these interfaces, a common approach is to run them separately, constantly switching between their processes during operation. However, this method of continuously switching between the engineering and strategy processes increases operational costs and reduces software efficiency.

[0058] To address the aforementioned technical problems, this disclosure provides a software operation method and apparatus, software system, electronic device, medium, and product, which are applied in the field of cloud computing in the field of computer technology, in order to improve the interaction efficiency between the engineering end and the strategy end, thereby improving service efficiency.

[0059] In this embodiment, a fusion engine is considered to be used to establish communication connections with both the engineering and policy ends of the software system. By registering the service functions provided by the policy end in the fusion engine, the fusion engine can directly notify the engineering end of the usage of the service functions through the established spatiotemporal service interface, so that the engineering end can use the services of the policy end and obtain accurate service results.

[0060] In this embodiment, the fusion engine can communicate with both the engineering and policy ends of the software system. The fusion engine can start its corresponding engine process based on an engine start request sent by the engineering end. The sampling engine process can perform the following operations: obtain at least one service function registered by the policy end in the fusion engine; generate a spatiotemporal service interface based on the at least one service function; and perform interaction between the engineering end and the policy end based on the spatiotemporal service interface, corresponding to the service corresponding to the target service function in the at least one service function. Therefore, the engineering end and the policy end can complete service interaction within the engine process, avoiding repeated switching between the engineering end process and the policy end process, improving data transmission efficiency, and thus enhancing the application of the engineering end and the policy end.

[0061] The technical solution of this disclosure will now be described in detail with reference to the accompanying drawings.

[0062] like Figure 1The diagram illustrates the application of this disclosure to the software operation method provided in the embodiments of this disclosure. The software system may include: an electronic device corresponding to the engineering end, such as computer 1; an electronic device corresponding to the strategy end, such as cloud server 2; and an electronic device corresponding to the fusion engine, such as cloud server 3, which has communication connections with both the computer 1 corresponding to the engineering end and the cloud server 2 corresponding to the strategy end.

[0063] Electronic device 1 can generate and send an engine startup request to cloud server 3. Cloud server 3 can generate a spatiotemporal service interface based on at least one service function registered on the policy side, and realize the interaction between electronic device 1 and the corresponding service of cloud server 2 through the spatiotemporal service interface. Computer 1 provides service request data to cloud server 2 through cloud server 3, and cloud server 2 feeds back service results to electronic device through cloud server 3. By merging the engine with cloud server 3, a communication path can be established between the engineering side and the policy side, realizing the rapid transmission of service data or information and improving service efficiency.

[0064] like Figure 2 The diagram shown is a flowchart of one embodiment of a software operation method provided in this disclosure. This method can be applied to a fusion engine, which can have communication connections with both the engineering and policy ends of the software system. The method may include:

[0065] 201: Based on the engine start request sent by the engineering side, start the engine process corresponding to the fusion engine.

[0066] Optionally, the engineering side can send an engine start request to the fusion engine when it needs to use the service functions of the strategy side. The fusion engine can receive the engine start request sent by the engineering side, respond to the engine start request, and start the engine process corresponding to the fusion engine. After the engine process corresponding to the fusion engine starts, the startup of the fusion engine is complete, and all operation steps of the fusion engine can be executed in the engine process.

[0067] The fusion engine can configure code access tools between different programming languages. For example, the py4j tool (full name: Python for Java) allows Python to dynamically access Java objects in Java, and Java programs can also call back Python objects.

[0068] Optionally, the strategy side can be programmed using the Python programming language. The engineering side can be programmed using the Java programming language or Scala (Scalable Language). The strategy side and the engineering side can be programmed using different programming languages.

[0069] The engine process performs the following operations:

[0070] 202: Obtain at least one service function registered by the strategy side in the fusion engine.

[0071] The strategy side can contain the implementation code of the core algorithm, which may include, for example, click-through rate prediction algorithms, face recognition algorithms, classification algorithms, image processing algorithms, A / B testing algorithms, etc. The engineering side can contain implementation code related to the application scenario, such as prediction interfaces, face recognition interfaces, etc., which can be displayed to the user. The strategy side can reside on a cloud server, while the engineering side can reside on the user's electronic device, enabling interaction with the user.

[0072] The strategy side can register at least one service function in the fusion engine.

[0073] 203: Generate a spatiotemporal service interface based on at least one service function.

[0074] The fusion engine generates a spatiotemporal service interface, which can be provided to the engineering side. This interface enables data retrieval from the engineering side and interaction with the strategy side.

[0075] 204: Based on the spatiotemporal service interface, perform interaction between the engineering end and the strategy end corresponding to the service corresponding to the target service function in at least one service function.

[0076] Optionally, the spatiotemporal service interface can be used to declare the types of services that the fusion engine can provide externally. Each service function corresponds to a specific service type. These service functions can be the code corresponding to the core algorithms on the strategy side.

[0077] In this embodiment, the fusion engine can communicate with both the engineering and policy ends of the software system. The fusion engine can start its corresponding engine process based on an engine start request sent by the engineering end. The sampling engine process can perform the following operations: obtain at least one service function registered by the policy end in the fusion engine; generate a spatiotemporal service interface based on the at least one service function; and perform interaction between the engineering end and the policy end based on the spatiotemporal service interface, corresponding to the service corresponding to the target service function in the at least one service function. Therefore, the engineering end and the policy end can complete service interaction within the engine process, avoiding repeated switching between the engineering end process and the policy end process, improving data transmission efficiency, and thus enhancing the application of the engineering end and the policy end.

[0078] like Figure 3 The diagram shown is a flowchart of another embodiment of a software operation method provided in this disclosure. This method can be applied to a fusion engine, which can have communication connections with both the engineering and policy ends of the software system. The method may include:

[0079] 301: Based on the engine start request sent by the engineering side, start the engine process corresponding to the fusion engine.

[0080] Some steps in this embodiment are the same as some steps in the foregoing embodiments, and for the sake of brevity, they will not be repeated here.

[0081] The engine process performs the following operations:

[0082] 302: Get at least one service function registered in the fusion engine by the strategy side.

[0083] 303: Generate a spatiotemporal service interface based on at least one service function.

[0084] 304: Feedback the function information of the target service function in the spatiotemporal service interface to the engineering side.

[0085] The spatiotemporal service interface is used to obtain service requests initiated by the engineering side for at least one target service function in the service functions.

[0086] 305: Obtain the service request provided by the spatiotemporal service interface and parse the service request data corresponding to the target service function in the service request.

[0087] Optionally, the engineering side can provide an application interface to the user, through which the user can input data to be processed. When the engineering side receives the data to be processed, it can determine that the data is service request data. The engineering side can then send the service request data to the fusion engine via the spatiotemporal service interface. The fusion engine can then retrieve the service request data from the engineering side via the spatiotemporal service interface.

[0088] 306: Sends service request data to the policy side. The service request data is used to obtain the corresponding service result from the policy side.

[0089] The fusion engine can be configured with a code access tool, which can forward service request data to the policy side. The service request data can be code written in Java, and the code access tool can access the core code written in Python on the policy side.

[0090] 307: Use the spatiotemporal service interface to feed the service results back to the engineering side.

[0091] In this embodiment, the function information of the target service function is fed back to the engineering end through a spatiotemporal service interface. When the engineering end obtains the function information of the target service function, it can initiate a service request for that target service function. The service request includes the service request data corresponding to the target service function. The fusion engine can obtain the service request provided by the spatiotemporal service interface, parse the service request data corresponding to the target service function in the service request, and send the service request data to the strategy end. The strategy end can then obtain the service result corresponding to the service request data. The fusion engine can then feed back the service result to the engineering end. By implementing the transmission and interaction of service request data and corresponding service results through the spatiotemporal service interface, accurate data transmission between the engineering end and the strategy end can be achieved through the engine process, avoiding data transmission between the strategy end and the interaction end, thus improving service efficiency.

[0092] As one example, generating a spatiotemporal service interface based on at least one service function may include:

[0093] Obtain the registration information of at least one service function in the fusion engine.

[0094] Based on the registration information corresponding to at least one service function in the fusion engine, a spatiotemporal service interface is generated.

[0095] The strategy side can register at least one service function in the fusion engine. Registration information can include the function information obtained during registration. Function information can include: function name, number of parameters, parameter names, parameter types, and / or function invocation method, etc. Parameters can include at least one of input parameters and output parameters.

[0096] The spatiotemporal service interface can declare at least one service function, each corresponding to a specific service. The engineering side can retrieve the declaration information of the spatiotemporal service interface.

[0097] In this embodiment of the disclosure, when generating the spatiotemporal service interface, the registration information corresponding to at least one service function in the fusion engine can be used to generate the spatiotemporal service interface accurately. This allows the spatiotemporal service interface to accurately use at least one service function to achieve interaction between the fusion engine and the policy side.

[0098] In one possible design, the strategy acquisition process, prior to registering at least one service function with the fusion engine, also includes:

[0099] Receive function registration requests sent by the policy side.

[0100] Based on the function registration request from the strategy side, obtain at least one service function provided by the strategy side.

[0101] After the strategy side initiates a function registration request to the fusion engine, it can send the function information corresponding to at least one service function to the fusion engine. The fusion engine obtains the function information corresponding to at least one service function provided by the strategy side, and uses the function information of each service function to register, thereby obtaining the registration information of the corresponding service function.

[0102] In this embodiment of the disclosure, the fusion engine can also receive a function registration request sent by the strategy end, so as to obtain at least one service function provided by the strategy end according to the function registration request of the strategy end, thereby realizing accurate acquisition of the service function of the strategy end and providing a basis for service interaction between the fusion engine and the strategy end.

[0103] To enable communication with the policy endpoint, the fusion engine can pass the policy communication port to the policy endpoint after starting the engine process. In some embodiments, obtaining at least one service function registered by the policy endpoint with the fusion engine includes:

[0104] Determine the policy communication port with the policy side.

[0105] Obtain at least one service function registered by the policy side with the fusion engine through the policy communication port.

[0106] Send service request data to the policy end, including:

[0107] The service request data is sent to the policy end through the policy communication port.

[0108] A policy communication port can refer to a virtual port within a computer, switch, or router. It is invisible and is used to enable applications from the convergence engine and the engineering side. Examples of ports include ports 80, 21, and 23 on a computer. Specifically, a policy communication port can be an unused port on the corresponding electronic device. The choice of policy communication port can be determined based on actual usage requirements.

[0109] In this embodiment of the disclosure, when the policy end and the fusion engine transmit different types of information such as service functions and data, they can do so through the policy communication port between the fusion engine and the policy end, thereby achieving accurate and efficient data transmission.

[0110] As another embodiment, the function information of the target service function in the spatiotemporal service interface is fed back to the engineering end, including:

[0111] Based on the engine startup request, obtain the service request data in the engine startup request;

[0112] Based on the service request data, determine the target service function from at least one service function;

[0113] The function information of the target service function is fed back to the engineering side through the spatiotemporal service interface.

[0114] In this embodiment of the disclosure, when the fusion engine obtains service request data from the engine startup request, it can determine the target service function from at least one service function based on the service request data, thereby achieving accurate acquisition of the target service function. The target service function can be accurately determined through the service request data, improving the efficiency and accuracy of target service function determination.

[0115] like Figure 4 The flowchart shown is a further embodiment of a software operation method provided by this disclosure. The method is applied to the engineering end, and the software system also includes a strategy end and a fusion engine that has communication connections with both the engineering end and the strategy end. The method includes:

[0116] 401: In response to a user-triggered service request, retrieve the service request data provided by the user.

[0117] 402: Generate an engine start request for the fusion engine and send the engine start request to the fusion engine. The engine start request instructs the fusion engine to start the engine process to provide the target service function in the spatiotemporal service interface to the project side; the target service function is one of at least one service function registered by the strategy side in the fusion engine.

[0118] Optionally, after the engineering side sends the engine start request to the fusion engine, it can pass the engineering communication port of the engineering side to the fusion engine. The fusion engine then transmits data or information to the spatiotemporal service interface through the engineering communication port.

[0119] The specific steps performed by the engineering end in this embodiment can be referred to the description in the foregoing embodiments, and will not be repeated here.

[0120] 403: Based on the spatiotemporal service interface, the interaction between the execution and policy ends corresponds to the service corresponding to the target service function.

[0121] In this embodiment, the fusion engine can communicate with both the engineering and policy ends of the software system. The fusion engine can start its corresponding engine process based on an engine start request sent by the engineering end. The sampling engine process can perform the following operations: obtain at least one service function registered by the policy end in the fusion engine; generate a spatiotemporal service interface based on the at least one service function; and perform interaction between the engineering end and the policy end based on the spatiotemporal service interface, corresponding to the service corresponding to the target service function in the at least one service function. Therefore, the engineering end and the policy end can complete service interaction within the engine process, avoiding repeated switching between the engineering end process and the policy end process, improving data transmission efficiency, and thus enhancing the application of the engineering end and the policy end.

[0122] like Figure 5 The flowchart shown is a further embodiment of a software operation method provided by this disclosure. The method is applied to the engineering end, and the software system also includes a strategy end and a fusion engine that has communication connections with both the engineering end and the strategy end. The method includes:

[0123] 501: In response to a user-triggered service request, retrieve the service request data provided by the user.

[0124] 502: Generate an engine start request for the fusion engine and send the request to the fusion engine. The engine start request instructs the fusion engine to start the engine process to provide the target service function in the spatiotemporal service interface to the project side. The target service function is one of at least one service function registered by the policy side in the fusion engine.

[0125] 503: Generate a service request for the target service function based on the service request data.

[0126] 504: A service request is sent to the fusion engine via the spatiotemporal service interface. The fusion engine retrieves the corresponding service result from the service request data in the service request.

[0127] Optionally, sending a service request to the fusion engine via the spatiotemporal service interface includes sending the service request to the spatiotemporal service interface of the fusion engine through the engineering service port, so that the fusion engine can obtain the service request through the spatiotemporal service interface and parse the service request data in the service request.

[0128] 505: Obtain the service results fed back by the fusion engine through the spatiotemporal service interface, and output the service results to the user.

[0129] The spatiotemporal service interface sends the service results to the engineering communication port so that the engineering side can obtain the service results fed back by the spatiotemporal service interface. The communication port of the engineering side receives the service results fed back by the spatiotemporal service interface.

[0130] In this embodiment, after the engineering end sends an engine start request to the fusion engine, it can generate a service request for the target service function based on the service request data, and then send the service request to the fusion engine through the spatiotemporal service interface. After the fusion engine obtains the corresponding service result from the strategy end, the engineering end can obtain the service result fed back by the fusion engine through the spatiotemporal service interface, thereby outputting the service result to the user. The spatiotemporal service interface enables the transmission of service request data and service results between the engineering end and the strategy end, ensuring accurate data transmission between them. Accurate data transmission ensures accurate data interaction and improves interaction efficiency.

[0131] As one embodiment, after generating the engine start request for the fusion engine and sending the engine start request to the fusion engine, the process further includes:

[0132] Receive function information of the target service function from at least one service function provided by the fusion engine through the spatiotemporal service interface;

[0133] Determine the target service function corresponding to the function information.

[0134] In this embodiment of the disclosure, when receiving function information of a target service function from at least one service function provided by the fusion engine through the spatiotemporal service interface, the target service function corresponding to the function information can be determined, thereby achieving accurate determination of the target service function. Direct determination through function information improves the efficiency and accuracy of target service function determination.

[0135] like Figure 6 The diagram shown is a flowchart of another embodiment of a software operation method provided in this disclosure. The method is used on a strategy end, and the software system also includes an engineering end and a fusion engine that has communication connections with both the engineering end and the strategy end. The method includes:

[0136] 601: Send a function registration request for at least one service function to the fusion engine. The registration request instructs the fusion engine to generate a spatiotemporal service interface based on at least one service function. The spatiotemporal service interface is used to provide function information of the target service function in at least one service function to the project side;

[0137] 602: Based on the spatiotemporal service interface, execute the interaction between the execution and engineering side corresponding to the service corresponding to the target service function.

[0138] The specific steps executed by the strategy terminal in this embodiment can be referred to the description in the foregoing embodiments, and will not be repeated here.

[0139] In this embodiment, after the engineering end sends an engine start request to the fusion engine, it can generate a service request for the target service function based on the service request data, and then send the service request to the fusion engine through the spatiotemporal service interface. After the fusion engine obtains the corresponding service result from the strategy end, the engineering end can obtain the service result fed back by the fusion engine through the spatiotemporal service interface, thereby outputting the service result to the user. The spatiotemporal service interface enables the transmission of service request data and service results between the engineering end and the strategy end, ensuring accurate data transmission between them. Accurate data transmission ensures accurate data interaction and improves interaction efficiency.

[0140] As one example, based on the spatiotemporal service interface, performing the interaction between the project side and the service corresponding to the target service function can include:

[0141] Receive service request data sent by the fusion engine. Each service request data corresponds to a target service function.

[0142] Transmit the service request data to the target service function;

[0143] Run the target service function to obtain the service result corresponding to the service request data;

[0144] The service results are fed back to the fusion engine.

[0145] Optionally, the system can receive service request data sent by the fusion engine through the policy communication port. The service request data may include the name of the requested service function, the numerical values ​​of the input parameters, etc. Transferring the service request data to the target service function may include: transferring the numerical values ​​of the input parameters from the service request data to the target service function corresponding to the function name. Running the target service function and obtaining the service result corresponding to the service request data may include calculating the numerical values ​​of the input parameters in the target service function, and using the calculation result as the output value of the output parameter. The service result is then generated based on the output value of the output parameter.

[0146] In practical applications, the service result can be determined based on the service content of the target service function on the strategy side. For example, taking a click-through rate prediction scenario, the service request data can be the tested ad link, the output parameter value can be the probability that the ad link will be clicked, and the service result can be a webpage with that probability as the prompt content. Of course, in addition to the output method of a webpage, the service result can also be output through voice, images, videos, short messages, instant messaging messages, etc. The specific output method of the service result is not limited in this embodiment.

[0147] In this embodiment of the disclosure, when receiving service request data sent by the fusion engine, the target service function corresponding to the service request data can be determined. The service request data is then transmitted to the target service function. After running the target service function, the service result corresponding to the service request data can be obtained, achieving accurate acquisition of the service result. The service result is then fed back to the fusion engine, which provides it to the engineering end, achieving accurate transmission of data and information and improving service efficiency.

[0148] like Figure 7 The diagram shown is a structural schematic of one embodiment of a software system provided in this disclosure. The software system may include:

[0149] The system includes an engineering end 701, a strategy end 702, and a fusion engine 703 that has communication connections with both the engineering end 701 and the strategy end 702.

[0150] The engineering side 701 is used to: respond to user-triggered usage requests, obtain service request data provided by the user; generate an engine startup request for the fusion engine and send the engine startup request to the fusion engine; and, based on the spatiotemporal service interface, execute the interaction between the strategy side and the service corresponding to the target service function.

[0151] The Fusion Engine 703 is used to: start the engine process corresponding to the Fusion Engine based on the engine start request sent by the engineering side; and use the engine process to perform the following operations: obtain at least one service function registered by the strategy side in the Fusion Engine; generate a spatiotemporal service interface based on the at least one service function; and perform interaction between the engineering side and the strategy side for the service corresponding to the target service function in the at least one service function based on the spatiotemporal service interface.

[0152] The strategy side 702 is used to: send the function registration request of at least one service function to the fusion engine; and based on the spatiotemporal service interface, it is used to perform the interaction between the project side and the service corresponding to the target service function.

[0153] The specific steps executed by the fusion engine, the engineering end, and the policy end can be referred to the description in the foregoing embodiments, and will not be repeated here. It should be noted that the engineering end can send its engineering communication port to the fusion engine to achieve communication with it. The policy end can send its policy communication port to the fusion engine to achieve communication with it. In addition to the spatiotemporal service interface, the fusion engine may include a communication module, which may contain the engineering communication port of the engineering end and the policy communication port of the policy end.

[0154] In this embodiment, after the engineering end sends an engine start request to the fusion engine, it can generate a service request for the target service function based on the service request data, and then send the service request to the fusion engine through the spatiotemporal service interface. After the fusion engine obtains the corresponding service result from the strategy end, the engineering end can obtain the service result fed back by the fusion engine through the spatiotemporal service interface, thereby outputting the service result to the user. The spatiotemporal service interface enables the transmission of service request data and service results between the engineering end and the strategy end, ensuring accurate data transmission between them. Accurate data transmission ensures accurate data interaction and improves interaction efficiency.

[0155] like Figure 8 The diagram shown is a structural schematic of one embodiment of a software running device provided in this disclosure. This device can be located within a fusion engine, which can have communication connections with both the engineering and policy ends of the software system. The software running device 800 may include:

[0156] Process startup unit 801: Used to start the engine process corresponding to the fusion engine based on the engine startup request sent by the engineering end;

[0157] The engine process performs the following operations:

[0158] Function registration unit 802: Used to obtain at least one service function registered by the strategy side in the fusion engine;

[0159] Interface generation unit 803: used to generate a spatiotemporal service interface based on at least one service function;

[0160] First interaction unit 804: used for interaction between the engineering end and the strategy end based on the spatiotemporal service interface, corresponding to the service corresponding to the target service function in at least one service function.

[0161] As one embodiment, the first interactive unit includes:

[0162] The information feedback module is used to feed back the function information of the target service in the spatiotemporal service interface to the engineering side; the spatiotemporal service interface is used to obtain the service request initiated by the engineering side for at least one target service function in the service functions.

[0163] The request parsing module is used to obtain the service requests provided by the spatiotemporal service interface and parse the service request data corresponding to the target service function in the service request.

[0164] The data sending module is used to send service request data to the policy terminal, and the service request data is used to obtain the corresponding service result from the policy terminal.

[0165] The first feedback module is used to feed the service results back to the engineering side using the spatiotemporal service interface.

[0166] In some embodiments, the interface generation unit includes:

[0167] The information acquisition module is used to acquire the registration information corresponding to at least one service function in the fusion engine.

[0168] The interface generation module is used to generate spatiotemporal service interfaces based on the registration information corresponding to at least one service function in the fusion engine.

[0169] One possible design also includes:

[0170] The request receiving unit is used to receive function registration requests sent by the policy end;

[0171] The function registration unit is used to obtain at least one service function provided by the strategy side based on the function registration request from the strategy side.

[0172] In some embodiments, the function registration unit includes:

[0173] The interface determination module is used to determine the policy communication port with the policy terminal;

[0174] The interface acquisition module is used to obtain at least one service function registered by the policy end in the fusion engine through the policy communication port;

[0175] The data transmission module includes:

[0176] The data sending submodule is used to send service request data to the policy end through the policy communication port.

[0177] As an optional implementation, the information feedback module includes:

[0178] The data acquisition submodule is used to acquire service request data from the engine startup request based on the engine startup request.

[0179] The target determination submodule is used to determine the target service function from at least one service function based on the service request data;

[0180] The information feedback submodule is used to feed back the function information of the target service function to the engineering side through the spatiotemporal service interface.

[0181] The software running device of this disclosure embodiment can correspond to Figures 2-3 The software operation method shown can be referenced in the description of the software operation method in the foregoing embodiments for the specific steps executed by each unit, module, and submodule.

[0182] like Figure 9 The diagram shown is a structural schematic of another embodiment of a software running device provided in this disclosure. The device is located at the engineering end, and the software system also includes a strategy end and a fusion engine that has communication connections with both the engineering end and the strategy end. The software running device 900 includes:

[0183] Request Response Unit 901: Used to respond to a user-triggered usage request and receive service request data provided by the user;

[0184] Startup generation unit 902: used to generate an engine start request for the fusion engine and send the engine start request to the fusion engine; the engine start request instructs the fusion engine to start the engine process to provide the target service function in the spatiotemporal service interface to the engineering end; the target service function is one of at least one service function registered by the strategy end in the fusion engine;

[0185] The second interaction unit 903 is used to perform the interaction between the strategy end and the service corresponding to the target service function based on the spatiotemporal service interface.

[0186] As one embodiment, the second interaction unit includes:

[0187] The first generation module is used to generate a service request for the target service function based on the service request data.

[0188] The first sending module is used to send service requests to the fusion engine through the spatiotemporal service interface; the service request data in the service request is used by the fusion engine to obtain the corresponding service result.

[0189] The result acquisition module is used to obtain the service results fed back by the fusion engine through the spatiotemporal service interface, and to output the service results to the user.

[0190] As one possible design, the device 900 also includes:

[0191] The information receiving unit is used to receive function information of the target service function in at least one service function provided by the fusion engine through the spatiotemporal service interface;

[0192] The function determination unit is used to determine the target service function corresponding to the function information.

[0193] The software running device of this disclosure embodiment can correspond to Figures 4-5 The software operation method shown can be referenced in the description of the software operation method in the foregoing embodiments for the specific steps executed by each unit, module, and submodule.

[0194] like Figure 10 The diagram shown is a structural schematic of another embodiment of a software running device provided in this disclosure. The device is located at the strategy end, and the software system further includes: an engineering end and a fusion engine that has communication connections with both the engineering end and the strategy end. The software running device 1000 may include:

[0195] Registration request unit 1001: used to send a function registration request for at least one service function to the fusion engine; the registration request instructs the fusion engine to generate a spatiotemporal service interface based on at least one service function; the spatiotemporal service interface is used to provide function information of the target service function in at least one service function to the engineering end;

[0196] The third interaction unit 1002 is used to perform the interaction between the project side and the service corresponding to the target service function based on the spatiotemporal service interface.

[0197] As one embodiment, the third interaction unit includes:

[0198] The data receiving module is used to receive service request data sent by the fusion engine; the service request data corresponds to the target service function.

[0199] The data transmission module is used to transmit service request data to the target service function;

[0200] The function execution module is used to run the target service function and obtain the service result corresponding to the service request data;

[0201] The second feedback module is used to feed the service results back to the fusion engine.

[0202] The software running device of this disclosure embodiment can correspond to Figure 6 The software operation method shown can be referenced in the description of the software operation method in the foregoing embodiments for the specific steps executed by each unit, module, and submodule.

[0203] It should be noted that the engineering end in this embodiment is not designed for any specific user and does not reflect the personal information of any particular user. The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution of this disclosure all comply with relevant laws and regulations and do not violate public order and good morals.

[0204] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0205] According to embodiments of this disclosure, this disclosure also provides a computer program product comprising: a computer program stored in a readable storage medium, at least one processor of an electronic device being able to read the computer program from the readable storage medium, and the at least one processor executing the computer program causing the electronic device to perform the scheme provided in any of the above embodiments.

[0206] Figure 11 A schematic block diagram of an example electronic device 1100 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0207] like Figure 11As shown, device 1100 includes a computing unit 1101, which can perform various appropriate actions and processes according to a computer program stored in read-only memory (ROM) 1102 or a computer program loaded from storage unit 1108 into random access memory (RAM) 1103. The RAM 1103 may also store various programs and data required for the operation of device 1100. The computing unit 1101, ROM 1102, and RAM 1103 are interconnected via bus 1104. Input / output (I / O) interface 1105 is also connected to bus 1104.

[0208] Multiple components in device 1100 are connected to I / O interface 1105, including: input unit 1106, such as keyboard, mouse, etc.; output unit 1107, such as various types of monitors, speakers, etc.; storage unit 1108, such as disk, optical disk, etc.; and communication unit 1109, such as network card, modem, wireless transceiver, etc. Communication unit 1109 allows device 1100 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0209] The computing unit 1101 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1101 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1101 performs the various methods and processes described above, such as software execution methods. For example, in some embodiments, the software execution method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 1108. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1100 via ROM 1102 and / or communication unit 1109. When the computer program is loaded into RAM 1103 and executed by the computing unit 1101, one or more steps of the software execution method described above may be performed. Alternatively, in other embodiments, the computing unit 1101 may be configured to execute software execution methods by any other suitable means (e.g., by means of firmware).

[0210] The electronic devices for the engineering side, the electronic devices for the strategy side, and the electronic devices for the fusion engine can all be referenced. Figure 11 The block diagram of the electronic device shown in this disclosure does not impose too many restrictions on the specific types of electronic devices corresponding to the engineering end, strategy end, and fusion engine.

[0211] In one possible design, the engineering side, the policy side, and the fusion engine can reside in the same electronic device, such as a single computer. In another possible design, the engineering side can reside in one electronic device, while the policy side and the fusion engine can reside in the same electronic device. For example, the engineering side could be a user-accessible terminal device such as a computer, laptop, tablet, or mobile phone, while the policy side and the fusion engine could reside in a cloud server. In yet another possible design, the engineering side, policy side, and fusion engine can reside in different electronic devices. In some embodiments, the engineering side and policy side can also reside in the same electronic device, while the fusion engine resides in a different device. The device structure of the electronic device can be referenced... Figure 11 The device block diagram shown.

[0212] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0213] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0214] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on 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 of the foregoing.

[0215] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0216] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0217] Computer systems can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. A server can be a cloud server, also known as a cloud computing server or cloud host, a hosting product within the cloud computing service ecosystem, addressing the shortcomings of traditional physical hosts and VPS (Virtual Private Server, or simply "VPS") services, such as high management difficulty and weak business scalability. Servers can also be servers for distributed systems or servers incorporating blockchain technology.

[0218] It should be understood that the various forms of processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

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

Claims

1. A software running method, applied to a fusion engine, the fusion engine being in communication connection with an engineering end and a strategy end of a software system respectively, the engineering end and the strategy end being written in different programming languages, the engineering end code being a code related to an application scenario, and the strategy end code being a core algorithm for implementing an application logic, the method comprising: starting an engine process corresponding to the fusion engine based on an engine starting request sent by the engineering end; using the engine process to perform the following operations: obtaining at least one service function registered by the strategy end in the fusion engine; generating a space-time service interface based on the at least one service function; based on the space-time service interface, performing interaction between the engineering end and the strategy end corresponding to a service of a target service function in the at least one service function.

2. The method of claim 1, wherein, The interaction between the engineering end and the strategy end corresponding to the service of the target service function based on the space-time service interface comprises: feeding back function information of the target service function in the space-time service interface to the engineering end; the space-time service interface is used to obtain a service request initiated by the engineering end for the target service function in the at least one service function; obtaining a service request provided by the space-time service interface and analyzing service request data corresponding to the target service function in the service request; sending the service request data to the strategy end, the service request data being used to obtain a corresponding service result from the strategy end; using the space-time service interface, feeding back the service result to the engineering end.

3. The method of claim 1 or 2, wherein, The generation of the space-time service interface based on the at least one service function comprises: obtaining registration information corresponding to the at least one service function in the fusion engine respectively; generating the space-time service interface based on the registration information corresponding to the at least one service function in the fusion engine respectively. 4.The method of claim 1 or 2, before the obtaining of the at least one service function registered by the strategy end in the fusion engine, further comprising: receiving a function registration request sent by the strategy end; obtaining at least one service function provided by the strategy end according to the function registration request of the strategy end.

5. The method of claim 4, wherein, The obtaining of the at least one service function registered by the strategy end in the fusion engine comprises: determining a strategy communication port of the strategy end; obtaining the at least one service function registered by the strategy end in the fusion engine through the strategy communication port; The sending of the service request data to the strategy end comprises: sending the service request data to the strategy end through the strategy communication port.

6. The method of claim 2 or 5, wherein, The feeding back of the function information of the target service function in the space-time service interface to the engineering end comprises: obtaining service request data in the engine starting request based on the engine starting request; determining a target service function from the at least one service function according to the service request data; feeding back function information of the target service function to the engineering end through the space-time service interface.

7. A software running method, the method is applied to an engineering end of a software system, the software system further comprises a strategy end and a fusion engine in communication connection with the engineering end and the strategy end, the engineering end and the strategy end are written in different programming languages, the engineering end code refers to the code related to the application scenario, and the strategy end code refers to the core algorithm for realizing the application logic; the method comprises: in response to a use request triggered by a user, obtaining service request data provided by the user; generating an engine start request of the fusion engine, and sending the engine start request to the fusion engine; the engine start request instructs the fusion engine to start an engine process to provide a target service function corresponding to a space-time service interface to the engineering end; the target service function is one of at least one service function registered by the strategy end in the fusion engine; based on the space-time service interface, performing interaction corresponding to the service of the target service function between the strategy end.

8. The method of claim 7, wherein, the interaction corresponding to the service of the target service function between the strategy end based on the space-time service interface comprises: generating a service request for the target service function according to the service request data; sending the service request to the fusion engine through the space-time service interface; the service request data in the service request is obtained by the fusion engine to obtain the corresponding service result; obtaining the service result fed back by the fusion engine through the space-time service interface to output the service result for the user.

9. The method of claim 7 or 8, wherein, after the generation of the engine start request of the fusion engine to send the engine start request to the fusion engine, further comprising: receiving function information of a target service function in at least one service function provided by the fusion engine through the space-time service interface; determining the target service function corresponding to the function information.

10. A software running method, the method is applied to a strategy end of a software system, the software system further comprises an engineering end and a fusion engine in communication connection with the engineering end and the strategy end, the engineering end and the strategy end are written in different programming languages, the engineering end code refers to the code related to the application scenario, and the strategy end code refers to the core algorithm for realizing the application logic; the method comprises: sending a function registration request of at least one service function to the fusion engine; the registration request instructs the fusion engine to generate a space-time service interface based on at least one service function; the space-time service interface is used to provide function information of a target service function in at least one service function to the engineering end; based on the space-time service interface, performing interaction corresponding to the service of the target service function between the engineering end.

11. The method of claim 10, wherein, the interaction corresponding to the service of the target service function between the engineering end based on the space-time service interface comprises: receiving service request data sent by the fusion engine; the service request data corresponds to a target service function; transmitting the service request data to the target service function; running the target service function to obtain a service result corresponding to the service request data; feeding back the service result to the fusion engine.

12. A software system comprising: The engineering end, the strategy end, and the fusion engine in communication connection with the engineering end and the strategy end; The engineering end and the strategy end are written in different programming languages, the engineering end code refers to the code related to the application scenario, and the strategy end code refers to the core algorithm for realizing the application logic; The engineering end is configured to: in response to a use request triggered by a user, obtain service request data provided by the user; generating an engine start request of the fusion engine and sending the engine start request to the fusion engine; Based on the space-time service interface, the interaction between the engineering end and the strategy end corresponding to the service of the target service function is performed. The fusion engine is configured to: based on the engine start request sent by the engineering end, start an engine process corresponding to the fusion engine; The following operations are performed by using the engine process: obtaining at least one service function registered by the strategy end in the fusion engine; and generating a space-time service interface based on at least one service function; Based on the space-time service interface, the interaction between the engineering end and the strategy end corresponding to the service of the target service function is performed. The strategy end is configured to: send a function registration request of at least one service function to the fusion engine; Based on the space-time service interface, the interaction between the engineering end and the strategy end corresponding to the service of the target service function is performed.

13. A software running device, the device is located in a fusion engine, the fusion engine is in communication connection with an engineering end and a strategy end of a software system respectively, the engineering end and the strategy end are written in different programming languages, the engineering end code refers to the code related to the application scenario, and the strategy end code refers to the core algorithm for realizing the application logic; the device comprises: A process start unit configured to start an engine process corresponding to the fusion engine based on an engine start request sent by the engineering end; The following operations are performed by using the engine process: A function registration unit configured to obtain at least one service function registered by the strategy end in the fusion engine; An interface generation unit configured to generate a space-time service interface based on at least one service function; A first interaction unit configured to perform the interaction between the engineering end and the strategy end corresponding to the service of a target service function in at least one service function based on the space-time service interface.

14. The apparatus of claim 13, wherein, The first interaction unit comprises: An information feedback module configured to feed back function information of the target service in the space-time service interface to the engineering end; the space-time service interface is configured to obtain a service request initiated by the engineering end for a target service function in at least one service function; A request analysis module configured to obtain a service request provided by the space-time service interface and analyze service request data corresponding to the target service function in the service request; A data sending module configured to send the service request data to the strategy end, the service request data being configured to obtain a corresponding service result from the strategy end; The first feedback module is configured to feed back the service result to the engineering end by using the space-time service interface.

15. The apparatus of claim 13 or 14, wherein, The interface generation unit comprises: The information acquisition module is configured to acquire registration information of the at least one service function corresponding to the fusion engine respectively; The interface generation module is configured to generate the space-time service interface based on the registration information of the at least one service function corresponding to the fusion engine respectively.

16. The apparatus of claim 13 or 14, further comprising: The request receiving unit is configured to receive a function registration request sent by the policy end; The function registration unit is configured to obtain at least one service function provided by the policy end according to the function registration request of the policy end.

17. The apparatus of claim 16, wherein, The function registration unit comprises: The interface determination module is configured to determine a policy communication port of the policy end; The interface acquisition module is configured to acquire at least one service function registered by the policy end in the fusion engine through the policy communication port; The data sending module comprises: The data sending submodule is configured to send the service request data to the policy end through the policy communication port.

18. The apparatus of claim 14 or 17, wherein, The information feedback module comprises: The data acquisition submodule is configured to acquire service request data in the engine start request based on the engine start request; The target determination submodule is configured to determine a target service function from the at least one service function according to the service request data; The information feedback submodule is configured to feed back function information of the target service function to the engineering end through the space-time service interface.

19. A software running apparatus, the apparatus is located at an engineering end, a software system further comprises a policy end and a fusion engine in communication connection with the engineering end and the policy end, the engineering end and the policy end are written in different programming languages, the engineering end code refers to a code related to an application scenario, and the policy end code refers to a core algorithm for implementing application logic; the apparatus comprises: The request response unit is configured to receive service request data provided by a user in response to a use request triggered by the user; The engine generation unit is configured to generate an engine start request of the fusion engine, and send the engine start request to the fusion engine; The engine start request instructs the fusion engine to start an engine process to provide a target service function corresponding to a space-time service interface to the engineering end; The target service function is one of at least one service function registered by the policy end in the fusion engine; The second interaction unit is configured to perform interaction corresponding to the target service function between the policy end and the engineering end based on the space-time service interface.

20. The apparatus of claim 19, wherein, The second interaction unit comprises: The first generation module is configured to generate a service request for the target service function according to the service request data; The first sending module is configured to send the service request to the fusion engine through the space-time service interface; and the service request data in the service request is acquired by the fusion engine to obtain a corresponding service result; A result obtaining module is configured to obtain the service result fed back by the fusion engine through the space-time service interface, so as to output the service result for the user.

21. The apparatus of claim 19 or 20, further comprising: An information receiving unit is configured to receive function information of a target service function in at least one service function provided by the fusion engine through the space-time service interface; A function determining unit is configured to determine the target service function corresponding to the function information.

22. A software execution apparatus, said apparatus being located at a policy end of a software system, said software system further comprising: An engineering side and a fusion engine in communication connection with the engineering side and the policy side, the engineering side and the policy side being written in different programming languages, the engineering side code being a code related to an application scenario, and the policy side code being a core algorithm for implementing application logic; the apparatus comprises: A request registering unit is configured to send a function registering request of at least one service function to the fusion engine; the registering request instructs the fusion engine to generate a space-time service interface based on at least one service function; the space-time service interface is configured to provide function information of a target service function in at least one service function to the engineering side; A third interaction unit is configured to perform interaction corresponding to the target service function between the engineering side based on the space-time service interface.

23. The apparatus of claim 22, wherein, The third interaction unit comprises: A data receiving module is configured to receive service request data sent by the fusion engine; the service request data corresponds to a target service function; A data transmission module is configured to transmit the service request data to the target service function; A function running module is configured to run the target service function to obtain a service result corresponding to the service request data; A second feedback module is configured to feed back the service result to the fusion engine.

24. An electronic device, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6, 7-9, or 10-11.

25. A non-transitory computer readable storage medium having stored thereon computer instructions, wherein, The computer instructions are used to enable the computer to perform the method of any one of claims 1-6, 7-9, or 10-11.

26. A computer program product, comprising a computer program which, when executed by a processor, implements the steps of the method of any one of claims 1-6, 7-9, or 10-11.

Images