Remote control quantization process starting method, electronic equipment and storage medium

Abstract

The invention discloses a remote control quantitative process starting method, electronic equipment and a storage medium. The method comprises the steps that a quantitative cloud system creates and operates a plurality of containers in a container cluster management system in advance; wherein each container is used for operating a quantification strategy of a user, and each container comprises a named pipeline; the quantization cloud system selects a target container from a plurality of containers under the condition that a quantization strategy of a user needs to be operated, and sends a quantization starting command to a named pipeline in the target container; and the target container receives the quantization starting command through the named pipeline, and starts a quantization process based on the quantization starting command so as to run a quantization strategy of the user by using the quantization process. In this way, starting of the quantization process can be remotely controlled.

Description

Technical Field

[0001] This application relates to the field of quantitative cloud technology, and in particular to a method for remotely controlling the initiation of a quantitative process, an electronic device, and a storage medium. Background Technology

[0002] Quantitative strategies, also known as quantitative trading strategies, refer to the use of tools such as computers to simulate, analyze, judge, and trade financial markets.

[0003] With the increasing popularity of quantitative trading among individual investors, providing convenient and stable quantitative trading tools has become an important development direction for fintech platforms. Currently, the quantitative trading functions of these platforms primarily rely on users' local devices (i.e., the client) to execute their quantitative strategies. In this local operation mode, users install specific quantitative trading software on their local devices, which includes a built-in engine for editing, backtesting, and executing quantitative strategies (collectively referred to as "quantitative components"). When a user starts a quantitative strategy, all computational tasks, such as the strategy's logical judgment, market data reception, and trading instruction generation, are completed on the local device. However, this architecture, which relies on local devices, has significant drawbacks and limitations (e.g., users must always keep their local devices online and are limited by the stability of local computing resources and network environment), severely impacting user experience and restricting the expansion of product functionality. Summary of the Invention

[0004] The main technical problem addressed by this application is to provide a method, electronic device, and storage medium for remotely controlling the initiation of a quantization process, which enables the remote control of the initiation of the quantization process.

[0005] To address the aforementioned technical problems, the first aspect of this application provides a method for remotely controlling the initiation of a quantization process. This method includes: a quantization cloud system pre-creating and running several containers in a container cluster management system; each container is used to run a user's quantization strategy, and each container contains a named pipe; when a user's quantization strategy needs to be run, the quantization cloud system selects a target container from the several containers and sends a quantization start command to the named pipe within the target container; the target container receives the quantization start command through the named pipe and, based on the quantization start command, starts the quantization process to run the user's quantization strategy.

[0006] The quantitative cloud system pre-creates and runs several containers in the container cluster management system, including: the quantitative cloud system pre-creates several scheduling units in the container cluster management system; pulls the container image corresponding to each scheduling unit to initialize the running environment of each scheduling unit; and the quantitative process and the named pipes corresponding to the containers are packaged in the corresponding container image.

[0007] The process of sending the quantization startup command to the named pipe within the target container includes: generating a shell command; wherein the shell command is used to instruct the quantization startup command to be written to the named pipe of the target container; and calling the command execution API interface within the container cluster management system to remotely send the shell command to the target container for execution.

[0008] The shell commands include the quantized startup command, the container identifier of the target container, and the pipe identifier of the named pipe in the target container.

[0009] The target container receives the quantization start command through a named pipe, which includes: the target container reading the quantization start command written in the named pipe through a shell script; and starting the quantization process based on the quantization start command.

[0010] The shell script is packaged in the container image used during the initialization of the target container.

[0011] The remote control quantization process startup method, after reading the quantization start command written in the named pipe, also includes: checking whether the quantization start command is empty; if so, exiting the shell script; if not, executing the quantization process based on the quantization start command.

[0012] When the target container runs, the shell script is used as the main process. The target container starts the quantization process as a foreground process. During the quantization process startup, the shell script is blocked on the quantization start command until the quantization process exits.

[0013] The quantization start command includes parameter information required to run the user's quantization strategy; and / or, based on the quantization start command, the quantization process is started, including: passing the quantization start command as a start parameter to the quantization process to start the quantization process.

[0014] The process of selecting a target container from several containers includes: randomly selecting one container from several containers as the target container.

[0015] To address the aforementioned technical problems, a second aspect of this application provides a method for remotely controlling the initiation of a quantization process. This method includes: a quantization cloud system pre-creating and running several containers in a container cluster management system; each container is used to run a user's quantization strategy, and each container contains a named pipe; when a user's quantization strategy needs to be run, a target container is selected from the several containers, and a quantization initiation command is sent to the named pipe within the target container, so that the target container receives the quantization initiation command through the named pipe and, based on the quantization initiation command, starts the quantization process to run the user's quantization strategy.

[0016] To address the aforementioned technical problems, a third aspect of this application provides a method for remotely controlling the initiation of a quantization process. The method includes: a target container receiving a quantization initiation command via a named pipe; wherein the target container is selected by the quantization cloud system from several containers when a user's quantization strategy needs to be run; the quantization initiation command is a named pipe sent by the quantization cloud system to the target container; the several containers are pre-created and run by the quantization cloud system in a container cluster management system; each container is used to run the user's quantization strategy; and each container contains a named pipe; based on the quantization initiation command, the quantization process is started to run the user's quantization strategy.

[0017] To address the aforementioned technical problems, a fourth aspect of this application provides an electronic device comprising a memory and a processor. The memory stores program instructions, and the processor executes the program instructions to implement the method performed by the aforementioned quantization cloud system, and / or to execute the program instructions to implement the method performed by the aforementioned target container.

[0018] To address the aforementioned technical problems, a fifth aspect of this application provides a computer-readable storage medium for storing program instructions that can be executed to implement the methods performed by the aforementioned quantization cloud system, and / or can be executed to implement the methods performed by the aforementioned target container.

[0019] The above technical solution allows the quantitative cloud system to select a target container from a set of containers pre-created and running in the container cluster management system when it needs to run a user's quantitative strategy. Since these containers are pre-deployed by the quantitative cloud system within the container cluster management system, it can directly select the target container from this pre-deployed set and utilize it to run the user's quantitative strategy, thus shortening the startup time and improving the startup speed of the user's quantitative strategy.

[0020] The quantitative cloud system sends a quantization start command to a named pipe within the target container. The target container receives the command through the named pipe and, based on the command, starts the quantization process to run the user's quantization strategy. In other words, the quantization cloud system communicates with the quantization process within the container via a named pipe to remotely control its startup. Once started, the quantization process runs the user's quantization strategy. Therefore, the quantization cloud system can remotely control the startup of the user's quantization strategy by communicating with the quantization process within the container via a named pipe. Since this communication does not require the container to be exposed to the network, it achieves communication between the quantization cloud system and the process within the container while maintaining network isolation, thus preventing external access to the container and ensuring security.

[0021] In addition, each user's quantitative strategy runs in its own independent container. The quantitative strategies of different users do not affect each other during operation. Even if a user's quantitative strategy fails or malfunctions, it will not affect the quantitative strategies running in other containers or the stability of the entire quantitative cloud system, thus ensuring the security and stability of the user's quantitative strategy. Attached Figure Description

[0022] Figure 1 This is a flowchart illustrating an embodiment of the remote control quantization process initiation method provided in this application; Figure 2 yes Figure 1 The flowchart of step S11 shown is a schematic diagram of one embodiment. Figure 3 This is a schematic flowchart of an embodiment of sending a quantization start command to a named pipe in a target container, as provided in this application. Figure 4 This is a flowchart illustrating another embodiment of the remote control quantization process initiation method provided in this application; Figure 5 This is a flowchart illustrating another embodiment of the remote control quantization process initiation method provided in this application; Figure 6 This is a schematic diagram of the structure of an embodiment of the electronic device provided in this application; Figure 7 This is a schematic diagram of an embodiment of the computer-readable storage medium provided in this application. Detailed Implementation

[0023] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0024] In the following description, specific details such as particular system architectures, interfaces, and technologies are presented for illustrative purposes rather than for limiting purposes, in order to provide a thorough understanding of this application.

[0025] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0026] Please see Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the remote control quantization process initiation method provided in this application. It should be noted that if substantially the same result is achieved, this embodiment does not necessarily reflect that outcome. Figure 1 The illustrated process sequence is limited. For example... Figure 1 As shown, this embodiment includes: Step S11: The quantitative cloud system pre-creates and runs several containers in the container cluster management system.

[0027] In this embodiment, the quantitative cloud system pre-creates and runs several containers in the container cluster management system (Kubernetes, K8s). By pre-creating these containers, the quantitative cloud system can directly select a target container from the pre-created and running containers to run the user's quantitative strategy when it is needed to run the strategy later. In other words, by pre-deploying several containers in the container cluster management system, the quantitative cloud system can readily accept new quantitative strategy execution tasks, improving the startup speed and shortening the startup time of the user's quantitative strategy.

[0028] Containers can be used to run quantization strategies. Specifically, the code required to run the quantization strategy can be packaged into a quantization process, and the executable file corresponding to the quantization process can be packaged into a container image. After the container cluster management system (Kubernetes, K8s) obtains a pod, the runtime environment of the pod can be initialized through the container image to complete the deployment.

[0029] It should be noted that the scheduling unit of the container cluster management system is the Pod. One or more containers can run within a Pod. The pre-created containers in this application run in their respective Pods, that is, one container runs within one Pod. By deploying a container for running quantization strategies within a Pod, the containers are isolated from each other. Subsequently, each user's quantization strategy runs in its own independent container. Quantization strategies of different users do not affect each other during operation, and different quantization strategies under a single user do not affect each other during operation. Even if a quantization strategy fails or malfunctions, it will not affect the quantization strategies running in other containers or the stability of the entire quantization cloud system, thus ensuring the operational security and stability of the user's quantization strategy.

[0030] In addition, the quantitative cloud system is the business platform, while the container cluster management system is the underlying infrastructure. Specifically, the container cluster management system provides generalized resource management and scheduling for containers. That is, the container cluster management system is responsible for creating, running, restarting, or destroying containers on physical machines or virtual machines (nodes) in the cluster. The quantitative cloud system manages and uses the containerized resources provided by the container cluster management system by calling its API to achieve specific business functions (the operation of quantitative strategies). There is no need for the container cluster management system to develop external networks, avoiding connections or access between external networks and containers in the container cluster management system, effectively isolating the container cluster management system from the network and effectively improving security.

[0031] Furthermore, in this embodiment, the quantitative cloud system pre-creates and runs several containers within the container cluster management system, each containing named pipes. Subsequently, the quantitative cloud system can communicate with the processes within these containers via these named pipes to remotely control the activation of the user's quantitative strategy. That is, while maintaining container network isolation, communication between the quantitative cloud system and the processes within the containers is achieved to remotely control the activation of the user's quantitative strategy. Additionally, because the communication between the quantitative cloud system and the processes within the containers occurs under container network isolation, external access to the containers is prevented, ensuring security.

[0032] Step S12: When the user's quantization strategy needs to be run, the quantization cloud system selects the target container from several containers and sends the quantization start command to the named pipe in the target container.

[0033] In this embodiment, when a user's quantitative strategy needs to be run, the quantitative cloud system selects a target container from a pool of containers. The system selects the target container from a pool of containers that it has pre-created and is running in the container cluster management system, and utilizes this target container to run the user's quantitative strategy. Since these containers are pre-deployed by the quantitative cloud system in the container cluster management system, when the system needs to run a user's quantitative strategy, it can directly select the target container from the pre-deployed containers and utilize it to run the user's quantitative strategy, shortening the startup time and improving the startup speed. Furthermore, subsequent user quantitative strategies run in their own independent containers, and the quantitative strategies of different users do not affect each other during operation. Even if a user's quantitative strategy malfunctions or becomes abnormal, it will not affect the quantitative strategies running in other containers or the stability of the entire quantitative cloud system, ensuring the operational security and stability of the user's quantitative strategy.

[0034] Furthermore, in this embodiment, the quantization start command is sent to a named pipe within the target container. The target container then receives the quantization start command through the named pipe and, based on this command, starts the quantization process to run the user's quantization strategy. In other words, the quantization cloud system communicates with the quantization process within the container via a named pipe to remotely control the start of the quantization process. Once started, the quantization process runs the user's quantization strategy. Therefore, the quantization cloud system can remotely control the start of the user's quantization strategy by communicating with the quantization process within the container via a named pipe. Since the quantization cloud system communicates with the quantization process within the container via a named pipe without exposing the container to the network, it achieves communication between the quantization cloud system and the process within the container to remotely control the start of the user's quantization strategy while maintaining container network isolation. This avoids external access to the container and ensures security.

[0035] It's important to note that quantitative trading refers to the process of using computer technology to complete trades based on pre-defined quantitative strategies. Quantitative trading significantly reduces the impact of investor sentiment fluctuations, avoiding irrational investment decisions made during periods of extreme market euphoria or pessimism. A quantitative strategy specifically includes the trading target, pre-defined trading conditions, and the trading actions triggered when these conditions are met. Trading conditions include, but are not limited to, the requirement that market data and / or related technical indicators of the trading target meet specific criteria. Trading actions include, but are not limited to, order placement and order cancellation. For example, the logic of a quantitative strategy might be: when the technical indicators of the trading target specified in the quantitative strategy meet the preset conditions, an order is placed on the trading target. Specifically, taking a moving average golden cross entry strategy as an example, when the moving averages of the trading target specified in the quantitative strategy form a golden cross within a certain period, a buy order is placed on the trading target. This helps investors better seize trading opportunities, achieve more precise and efficient trading operations, and improve trading efficiency and speed.

[0036] Investors can define the strategy logic of preset quantitative strategies based on the visual interactive interface provided by the client front-end. That is, investors can directly specify preset trading conditions and the trading operations to be executed after the preset trading conditions are met through the visual interactive interface provided by the client front-end. Specifically, the visual interactive interface provided by the client front-end may include a quantitative strategy canvas, which provides card controls, including start card controls, condition card controls, and event card controls. Users can edit the card controls provided by the quantitative strategy canvas to construct the quantitative trading strategy canvas. For example, users can edit the condition card controls to set the trading conditions of the quantitative strategy, and edit the event card controls to set the trading operations of the quantitative strategy.

[0037] After a quantitative strategy is built and generated on the client-side frontend, it is sent to the quantitative cloud system. The quantitative cloud system receives and stores the quantitative strategy sent by the client-side frontend. In this case, it can be considered that the quantitative cloud system needs to run the user's quantitative strategy. Alternatively, the user starts a quantitative strategy on the client-side frontend. The client-side frontend generates a quantitative strategy start command and sends it to the quantitative cloud system. The quantitative cloud system receives the quantitative strategy start command from the client-side frontend and executes the selection of the target container from several containers and subsequent steps. Therefore, when the quantitative cloud system receives the quantitative strategy start command from the client-side frontend, it can also be considered that the quantitative cloud system needs to run the user's quantitative strategy.

[0038] During the execution of a quantitative strategy, the container running the user's quantitative strategy can acquire market data of the trading object in real time. After receiving the market data of the trading object, it performs calculations and judgments based on the loaded user quantitative strategy to determine whether the specified preset trading conditions are met. If the specified preset trading conditions are met, it generates the corresponding trading instructions (such as placing an order or canceling an order) and sends a trading request to the trading server of the brokerage or exchange to realize the transaction.

[0039] In one embodiment, selecting a target container from a plurality of containers specifically involves randomly selecting one container from the plurality of containers as the target container. Randomly selecting a container as the target container avoids always prioritizing certain specific containers, making the resource utilization of each container more balanced; that is, random selection allows each container to have the opportunity to undertake the task of running the quantization strategy, making full use of the computing, memory and other resources of all containers, and improving the overall resource utilization rate.

[0040] Step S13: The target container receives the quantization start command through the named pipe and starts the quantization process based on the quantization start command to run the user's quantization strategy.

[0041] In this embodiment, the target container receives a quantization start command via a named pipe and, based on this command, starts a quantization process to run the user's quantization strategy. In other words, the quantization process within the target container communicates with the quantization cloud system via a named pipe within the container, enabling the quantization cloud system to remotely control the start of the target container. Once started, the container runs the user's quantization strategy. Therefore, the communication between the quantization process within the target container and the quantization cloud system via a named pipe allows the quantization cloud system to remotely control the start of the user's quantization strategy. Since communication between the quantization process within the target container and the quantization cloud system via a named pipe does not require the container to expose its network, this achieves communication between the quantization process within the target container and the quantization cloud system to remotely control the start of the user's quantization strategy while maintaining container network isolation. This avoids external access to the container and ensures security.

[0042] It should be noted that in existing technologies, user quantization strategies primarily rely on local device operation. This approach has many inconveniences and limitations, such as the requirement for users to keep their local devices constantly online and limitations imposed by local computing resources and network stability. This application, however, runs the user's quantization strategy within a container, enabling offline quantization. Furthermore, after starting the quantization process, the user's quantization strategy is retrieved from a remote server and executed, thus utilizing the quantization process to run the user's quantization strategy.

[0043] In one embodiment, the quantization initiation command includes parameter information required to run the user's quantization strategy. However, the parameter information required to run the user's quantization strategy is not limited to, for example, the user's quantization strategy ID.

[0044] In one embodiment, the quantization process is started based on the quantization start command. Specifically, the quantization start command is passed as a start parameter to the quantization process to initiate the quantization process. The quantization start command contains the parameter information required for the quantization strategy to run. Passing it as a start parameter to the quantization process is like sending the quantization process a detailed "running guide," letting the quantization process know how to start and execute the quantization strategy. This allows the quantization process to start according to the start parameters, enabling the quantization process to run the quantization strategy and achieving automatic start and operation of the quantization strategy.

[0045] Please see Figure 2 , Figure 2 yes Figure 1 The flowchart shown is a schematic diagram of one embodiment of step S11. It should be noted that if substantially the same result is achieved, this embodiment does not necessarily follow the same pattern. Figure 2 The illustrated process sequence is limited. For example... Figure 2 As shown, this embodiment includes: Step S21: The quantitative cloud system pre-creates several scheduling units in the container cluster management system.

[0046] In this embodiment, the quantitative cloud system pre-creates several scheduling units in the container cluster management system. That is, the quantitative cloud system pre-creates several scheduling units in the container cluster management system; however, the number of scheduling units created is not limited and can be set according to actual usage needs.

[0047] Step S22: Pull the container images corresponding to each scheduling unit to initialize the runtime environment of each scheduling unit.

[0048] In this embodiment, container images corresponding to each scheduling unit are pulled to initialize each scheduling unit. The quantitative process and the named pipes corresponding to the containers are packaged within their respective container images. A container image is a lightweight, independent executable software package containing the complete software environment required to run the quantitative strategy, including the operating system, dependency libraries, and the quantitative trading framework. By pulling the container images corresponding to the scheduling units, a clean and minimal operating system environment is prepared within each scheduling unit, pre-installed with all necessary software dependencies and executable files, thus initializing the runtime environment of the scheduling unit.

[0049] Specifically, packaged container images can be pulled from the image repository to initialize the runtime environment of the scheduling unit.

[0050] In one embodiment, the steps for obtaining the container image corresponding to the container include: Step 1: Packaging the code required to run the quantization strategy into a quantization process; Step 2: Packaging the quantization process into the container image.

[0051] Please see Figure 3 , Figure 3 This is a schematic flowchart illustrating an embodiment of sending a quantization start command to a named pipe within a target container, as provided in this application. It should be noted that if substantially the same result is achieved, this embodiment does not necessarily require further elaboration. Figure 3 The illustrated process sequence is limited. For example... Figure 3 As shown, this embodiment includes: Step S31: Generate shell commands.

[0052] In this embodiment, a shell command is generated; wherein, the shell command is used to instruct the quantization start command to be written to the named pipe of the target container.

[0053] In one implementation, the shell command includes a quantization start command, a container identifier for the target container, and a pipe identifier for a named pipe within the target container. The container identifier for the target container can be the container name of the target container, and the pipe identifier for the named pipe within the target container can be the name of the named pipe. Additionally, the quantization start command may include parameter information required to run the user's quantization strategy, such as the ID of the user's quantization strategy.

[0054] Step S32: Call the command execution API interface within the container cluster management system to remotely send shell commands to the target container for execution.

[0055] In this implementation, the command execution API interface within the container cluster management system is invoked to remotely send a shell command to the target container for execution. Since the shell command instructs the quantization startup instruction to be written to the target container's named pipe, what is remotely sent, or transmitted, is a shell command written to the named pipe. Executing this shell command in the target container achieves the remote writing of the quantization startup instruction to the target container's named pipe. In other words, the quantization startup instruction is packaged into a shell command using a shell command, and then transmitted by executing the shell command in the target container.

[0056] Alternatively, it can be done by calling the command execution API interface within the container cluster management system to remotely send shell commands to the target container for execution. Therefore, the target container's network does not need to be open; that is, the target container's network remains isolated, preventing external access to the container and ensuring security.

[0057] In one implementation, the command execution API interface within the container cluster management system is the exec interface; that is, the exec interface is an API interface provided by the container cluster management system. Calling the API Server through the container cluster management system eliminates the need for the target container to expose its network, achieving network isolation of the target container and thus preventing external access to the target container, ensuring security.

[0058] Furthermore, during the process of the quantitative cloud system accessing the API Server of the container cluster management system to call command execution API interfaces, the container cluster management system can authenticate the quantitative cloud system with a key. By configuring the key in the quantitative cloud system, the key cannot be obtained from outside, that is, outside cannot access the target container through the API Server's exec command like the quantitative cloud system.

[0059] In one implementation, the target container receives a quantization start command via a named pipe. Specifically, the target container reads the quantization start command written to the named pipe via a shell script; based on the quantization start command, it starts the quantization process. The shell script in the target container continuously listens to the named pipe, and upon receiving the quantization start command from the named pipe, it starts the quantization process to run the user's quantization strategy. In other words, the target container receives the quantization start instruction via a shell script and controls the quantization process to start based on the quantization start instruction, thereby running the user's quantization strategy.

[0060] In one specific implementation, the shell script is packaged within the container image used during the initialization of the target container. By including the shell script within this image, the shell script can be directly used within the container after the container's runtime environment is initialized by pulling the corresponding container image. Therefore, when a subsequent container is selected as the target container, the shell script can continuously monitor the named pipe to promptly read the quantization start command and initiate the quantization process accordingly. This allows for timely execution of the user's quantization strategy, shortening the startup time and improving the startup speed of the quantization strategy.

[0061] In one specific implementation, when the target container runs, a shell script acts as the main process. The target container starts the quantization process as a foreground process. During the quantization process startup, the shell script is blocked on the quantization start command until the quantization process exits. A main process is required for the target container to run; this main process is a shell script. The shell script continuously listens to a named pipe. When it reads the quantization start command from the named pipe, it starts the quantization process to execute the user's quantization strategy. Furthermore, because the shell script is blocked on the quantization start command—that is, blocked on the execution of the quantization process—it will not continue executing subsequent code (i.e., it will not execute until the script ends) as long as the quantization process does not exit, thus maintaining the running state of the main process. Moreover, because the main process remains running (blocked by the quantization process), the target container also continues to run and will not be terminated when the main process ends, providing a stable running environment for the quantization process, enabling it to continuously execute the user's quantization strategy within the target container.

[0062] In one specific implementation, if the quantization process exits abnormally, the shell script will also end its blocking and exit. At this time, the target container will also become abnormal due to the main process's exit. The quantization cloud system will check the status of the target container, and if an abnormality is detected, it will enter the exception handling process. Therefore, the shell script starts the quantization process as a foreground process to achieve the purpose of exception checking and timely detection of the abnormal exit of the quantization process.

[0063] In other words, if the quantization process exits abnormally for some reason (such as code errors, insufficient resources, network problems, etc.), the shell script blocked on the quantization process will be immediately unblocked and continue executing subsequent code. Since the shell script, as the main process, has exited, the quantization cloud system will detect the termination of the target container's main process. The quantization cloud system will check the status of the target container, and once an anomaly is detected, it will enter the anomaly handling process, such as restarting the target container or sending alarm notifications, to ensure that the quantization strategy can resume operation as soon as possible.

[0064] In one specific implementation, after reading the quantization start command written to the named pipe, it also checks whether the quantization start command is empty; if so, the shell script exits; otherwise, it executes the quantization process based on the quantization start command. Upon reading the quantization start command, it checks whether the command is an empty string. If the quantization start command is empty, it indicates that the quantization cloud system may not have sent the quantization start command correctly, or that a problem occurred during the sending process. In this case, the shell script exits and terminates immediately to prevent the shell script from continuing to execute under invalid input, thus preventing unpredictable errors during subsequent quantization process startup. If the quantization start command is not empty, it indicates that the quantization cloud system has successfully sent a valid quantization start command. Then, it executes subsequent quantization process startup operations to promptly start the quantization process based on the quantization start command, thereby utilizing the quantization process to run the user's quantization strategy in a timely manner, shortening the startup time of the user's quantization strategy, and improving the startup speed of the user's quantization strategy.

[0065] Please see Figure 4 , Figure 4 This is a flowchart illustrating another embodiment of the remote control quantization process initiation method provided in this application. It should be noted that if substantially the same result is achieved, this embodiment does not necessarily reflect that outcome. Figure 4 The illustrated process sequence is limited. For example... Figure 4 As shown, this embodiment includes: Step S41: The quantitative cloud system pre-creates and runs several containers in the container cluster management system; each container is used to run the user's quantitative strategy and contains named pipes.

[0066] Step S41 is similar to step S11, and will not be described again here.

[0067] Step S42: When the user's quantization strategy needs to be run, select a target container from several containers and send the quantization start command to the named pipe in the target container so that the target container receives the quantization start command through the named pipe and starts the quantization process based on the quantization start command to run the user's quantization strategy.

[0068] Step S42 is similar to steps S12-S13, and will not be described again here.

[0069] Please see Figure 5 , Figure 5 This is a flowchart illustrating another embodiment of the remote control quantization process initiation method provided in this application. It should be noted that if substantially the same result is achieved, this embodiment does not necessarily reflect that outcome. Figure 5 The illustrated process sequence is limited. For example... Figure 5 As shown, this embodiment includes: Step S51: The target container receives the quantization start command through a named pipe; wherein, the target container is selected by the quantization cloud system from several containers when the user's quantization strategy needs to be run, the quantization start command is a named pipe sent by the quantization cloud system to the target container, the several containers are pre-created and run by the quantization cloud system in the container cluster management system, each container is used to run the user's quantization strategy, and each container contains a named pipe.

[0070] Step S51 is similar to steps S11-S12, and will not be described again here.

[0071] Step S52: Based on the quantization start command, start the quantization process to run the user's quantization strategy.

[0072] Step S52 is similar to step S13, and will not be described again here.

[0073] Please see Figure 6 , Figure 6 This is a schematic diagram of an embodiment of the electronic device provided in this application. The electronic device 60 includes a memory 61 and a processor 62 coupled to each other. The processor 62 is used to execute program instructions stored in the memory 61 to implement the steps of any of the above-described embodiments of the remote control quantization process initiation method. In a specific implementation scenario, the electronic device 60 may include, but is not limited to, a microcomputer or a server. In addition, the electronic device 60 may also include mobile devices such as laptops and tablets, which are not limited here.

[0074] Specifically, processor 62 controls itself and memory 61 to implement the steps of any of the above-described remote control quantization process initiation method embodiments. Processor 62 can also be referred to as a CPU (Central Processing Unit). Processor 62 may be an integrated circuit chip with signal processing capabilities. Processor 62 can also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. A general-purpose processor can be a microprocessor or any conventional processor. Furthermore, processor 62 can be implemented using integrated circuit chips.

[0075] It should be noted that the processor 62 executes the program instructions stored in the memory 61 to implement the steps of any of the above-described remote control quantization process initiation method embodiments. This can be understood as the processor 62 being used to execute program instructions to implement the steps or methods executed by the above-described quantization cloud system, and / or to execute program instructions to implement the steps or methods executed by the above-described target container.

[0076] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of an embodiment of the computer-readable storage medium provided in this application. The computer-readable storage medium 70 of this application embodiment stores program instructions 71. When executed, these program instructions 71 implement the methods provided in any embodiment and any non-conflicting combination of the remote control quantization process initiation method of this application. The program instructions 71 can form a program file and be stored in the aforementioned computer-readable storage medium 70 in the form of a software product, so that a computer device (which may be a personal computer, server, or network device, etc.) can execute all or part of the steps of the methods of various embodiments of this application. The aforementioned computer-readable storage medium 70 includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, or terminal devices such as computers, servers, mobile phones, and tablets.

[0077] It should be noted that when program instruction 71 is executed, it implements any embodiment of the remote control quantization process startup method of this application. This can be understood as program instruction 71 being executed to implement the steps or methods performed by the above-mentioned quantization cloud system, and / or program instruction 71 being executed to implement the steps or methods performed by the above-mentioned target container.

[0078] If the technical solution of this application involves personal information, the product using this technical solution has clearly informed the user of the personal information processing rules and obtained the user's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using this technical solution has obtained the user's separate consent before processing the sensitive personal information, and also meets the requirement of "express consent". For example, at personal information collection devices such as cameras, clear and prominent signs are set up to inform users that they have entered the scope of personal information collection and that personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed that they have agreed to the collection of their personal information; or on the personal information processing device, with clear signs / information informing users of the personal information processing rules, authorization is obtained from the individual through pop-up information or by asking the individual to upload their personal information; wherein, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the types of personal information processed.

[0079] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for remotely controlling the initiation of a quantization process, characterized in that, The method includes: The quantitative cloud system pre-creates and runs several containers in the container cluster management system; each container is used to run the user's quantitative strategy and contains named pipes. When the user's quantization strategy needs to be run, the quantization cloud system selects a target container from the plurality of containers and sends the quantization start command to the named pipe in the target container; The target container receives the quantization start command through the named pipe and starts the quantization process based on the quantization start command to run the user's quantization strategy using the quantization process.

2. The method according to claim 1, characterized in that, The quantitative cloud system pre-creates and runs several containers in the container cluster management system, including: The quantitative cloud system pre-creates several scheduling units in the container cluster management system; Pull the container images corresponding to each scheduling unit to initialize the runtime environment of each scheduling unit; wherein, the quantization process and the named pipe corresponding to the container are packaged in the corresponding container image.

3. The method according to claim 1, characterized in that, Sending the quantization start command to the named pipe within the target container includes: Generate a shell command; wherein the shell command is used to instruct the quantization startup command to be written into the named pipe of the target container; The command execution API interface within the container cluster management system is invoked to remotely send the shell command to the target container for execution.

4. The method according to claim 3, characterized in that, The shell command includes the quantization start command, the container identifier of the target container, and the pipe identifier of the named pipe in the target container.

5. The method according to claim 1, characterized in that, The target container receives the quantized start command through the named pipe, including: The target container reads the quantized start command written to the named pipe via a shell script; Based on the quantization start command, the quantization process is started.

6. The method according to claim 5, characterized in that, The shell script is packaged in the container image used during the initialization of the target container.

7. The method according to claim 5, characterized in that, After reading the quantization start command written to the named pipe, the method further includes: Check if the quantization start command is empty; If so, exit the shell script; If not, then execute the quantization start command to start the quantization process.

8. The method according to claim 5, characterized in that, When the target container runs, the shell script is used as the main process. The target container starts the quantization process as a foreground process. During the start of the quantization process, the shell script is blocked on the quantization start command until the quantization process exits.

9. The method according to claim 1, characterized in that, The quantization start command includes the parameter information required to run the user's quantization strategy; And / or, the step of initiating the quantization process based on the quantization initiation command includes: The quantization start command is passed as a start parameter to the quantization process to start the quantization process.

10. The method according to claim 1, characterized in that, The step of selecting a target container from the plurality of containers includes: One of the containers is randomly selected from the plurality of containers as the target container.

11. A method for remotely controlling a quantization process initiation, characterized in that, The method includes: The quantitative cloud system pre-creates and runs several containers in the container cluster management system; each container is used to run the user's quantitative strategy and contains named pipes. When a user's quantization strategy needs to be run, a target container is selected from the plurality of containers, and a quantization start command is sent to a named pipe in the target container, so that the target container receives the quantization start command through the named pipe and starts the quantization process based on the quantization start command, so as to run the user's quantization strategy using the quantization process.

12. A method for remotely controlling a quantization process initiation, characterized in that, The method includes: The target container receives the quantization start command through a named pipe; wherein, the target container is selected by the quantization cloud system from several containers when the user's quantization strategy needs to be run, the quantization start command is sent by the quantization cloud system to the named pipe in the target container, the several containers are created and run in advance by the quantization cloud system in the container cluster management system, each container is used to run the user's quantization strategy, and each container contains a named pipe. Based on the quantization start command, the quantization process is started to run the user's quantization strategy.

13. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory being used to store program instructions, and the processor being used to execute the program instructions to implement the method performed by the quantization cloud system as claimed in any one of claims 1-12, and / or to execute the program instructions to implement the method performed by the target container as claimed in any one of claims 1-12.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store program instructions that can be executed to implement the method performed by the quantization cloud system as claimed in any one of claims 1-12, and / or can be executed to implement the method performed by the target container as claimed in any one of claims 1-12.

Images