Disclosure of Invention
In view of the foregoing, it is desirable to provide a hardware resource scheduling method, system, computer device, computer-readable storage medium, and computer program product that can improve the utilization of hardware resources.
In a first aspect, the present application provides a method for scheduling hardware resources. The method comprises the following steps:
The method comprises the steps of responding to an execution command sent by a development machine and aiming at a target task, determining a target physical machine, wherein the target physical machine is used for providing special hardware resources required by executing the target task;
starting a first proxy program on a target physical machine, and mounting a root directory of a development machine for starting file sharing service to a target mounting point of the target physical machine through the first proxy program;
starting a target container through a first proxy program, and replacing a root directory of the target container with a target mounting point of a target physical machine;
and executing the target task through the target container to obtain a target task execution result.
In some embodiments, the method further comprises:
The file sharing service is used for realizing file sharing between the development machine and the target physical machine. In some embodiments, the magnetic disk includes a system disk and a data disk.
In some embodiments, the method further comprises:
after the execution of the target task is finished, destroying the target container through a first proxy program to recover the target physical machine;
The file sharing service is closed by the second agent.
In some embodiments, determining the target physical machine in response to an execution command for the target task sent by the development machine includes:
Responding to an execution command aiming at a target task and sent by a development machine, and analyzing the execution command to obtain special hardware resource demand information;
And determining the target physical machine from the physical machine cluster according to the special hardware resource demand information.
In some embodiments, after the target task is executed by the target container and the target task execution result is obtained, the method further includes:
forwarding a target task execution result to a second agent program on the development machine through the first agent program;
and the terminal receiving service started by the second agent program receives the target task execution result so as to output and display the target task execution result in the development machine.
In some embodiments, the method further comprises:
displaying a command line interface on a development machine;
according to the execution command code input in the command line interface, sending an execution command aiming at the target task to a server;
Responding to an execution command for a target task sent by a development machine, determining a target physical machine comprises the following steps:
The server side extracts the developer identification in the execution command and distributes a corresponding target physical machine for the developer uniquely represented by the developer identification.
In a second aspect, the application also provides a hardware resource scheduling system. The system comprises a server and a target physical machine;
The system comprises a development machine, a server side, a target physical machine and a development machine, wherein the development machine is used for developing a target task, and the development machine is used for developing a target physical machine;
The target physical machine is used for starting a first proxy program on the target physical machine, mounting a root directory of a development machine for starting file sharing service to a target mounting point of the target physical machine through the first proxy program, starting a target container through the first proxy program, replacing the root directory of the target container with the target mounting point of the target physical machine, and executing a target task through the target container to obtain a target task execution result.
In some embodiments, the system further comprises:
The development machine is used for starting file sharing service for a disk on the development machine through a second agent program on the development machine, wherein the file sharing service is used for realizing file sharing between the development machine and the target physical machine.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the steps of the above-described method embodiments when the processor executes the computer program.
In a fourth aspect, the present application also provides a computer-readable storage medium. A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method embodiments described above.
In a fifth aspect, the present application also provides a computer program product. Computer program product comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
When executing a target task requiring special hardware resources, determining a target physical machine with the special hardware resources through an execution command sent by a development machine aiming at the target task, mounting a root directory of the development machine for starting file sharing service to a target mounting point of the target physical machine and starting a target container through a first proxy program, replacing the root directory of the target container with the target mounting point of the target physical machine, and finally executing the target task through the target container to obtain a target task execution result. The root directory of the development machine is automatically mounted to the root directory of the target container through the first proxy program and the file sharing service, and the target task is executed through the target container, so that the consistency of the development environment and the running environment of the target task is ensured, the cost of the additional configuration environment of the development personnel is reduced, the debugging time for combining the development machine with the special hardware resources is saved, the idle time after the special hardware resources are distributed to the development personnel is reduced, and the utilization rate of the special hardware resources is further improved.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The hardware resource scheduling method provided by the embodiment of the application can be applied to an application environment shown in figure 1. When executing a target task requiring a special hardware resource, the development machine 101 requests the special hardware resource from the server 102, and the server 102 determines a target physical machine 1031 for executing the target task from the physical machine cluster 103. The server refers to a cluster manager for managing a physical machine cluster. The server is a main coordinator and manager of the whole physical machine cluster and is responsible for making an allocation strategy of the target physical machine and scheduling special hardware resources of the physical machine cluster. It should be noted that, the server may exist independently of the physical machine cluster, or may be disposed inside a certain physical machine in the physical machine cluster. It will be understood that the server and the physical machine cluster for providing the special hardware resources are devices in the background, i.e. the server and the physical machine cluster are regarded as one background device for performing the steps of the method embodiment.
Illustratively, the server 102 determines a target physical machine 1031 in response to an execution command for a target task sent by the development machine 101, where the target physical machine 1031 is configured to provide special hardware resources required for executing the target task. The first proxy program on the target physical machine 1031 is started, and the target physical machine 1031 mounts the root directory of the development machine 101 that starts the file sharing service to the target mount point of the target physical machine 1031 through the first proxy program. The target physical machine 1031 starts the target container through the first proxy program, and replaces the root directory of the target container with the target mount point of the target physical machine 1031. The target physical machine 1031 executes the target task through the target container, and obtains a target task execution result.
In some embodiments, as shown in fig. 2, a method for scheduling hardware resources is provided, where the method may be implemented through interaction between the server 102 and the target physical machine 1031 in fig. 1, or may be implemented through interaction between the server 102, the developer 101, and the target physical machine 1031, and the method includes, without limitation, the following steps:
and step 201, determining a target physical machine in response to an execution command for the target task sent by the development machine, wherein the target physical machine is used for providing special hardware resources required for executing the target task.
The development machine is a hardware environment for development and configuration. The developer configures the desired code environment on the developer. It is understood that virtual machines may be used as development machines.
Target tasks refer to code that a developer designs to achieve a certain purpose or solve a certain problem. And inputting a code execution command corresponding to the target task, namely, the execution command of the target task, so that code operation can be completed.
A physical machine is a name for a physical computer, and is a host that can provide special hardware resources. A particular hardware resource is a hardware resource that is difficult or expensive to obtain relative to a common hardware resource (e.g., memory). For example, the special hardware resources include at least one of GPU (Graphics Processing Unit, graphics processor) and FPGA (Field Programmable GATE ARRAY ), etc.
When executing a target task requiring special hardware resources, the server responds to an execution command for the target task sent by the developer, analyzes the execution command of the target task, and determines a target physical machine according to the analysis result.
Step 202, starting a first proxy program on a target physical machine, and mounting a root directory of a development machine for starting file sharing service to a target mounting point of the target physical machine through the first proxy program.
The first agent refers to an agent running on the target physical machine. It will be appreciated that the first agent is an agent with a completely new function proposed by the present application, that is, the first agent is an agent for implementing automatic directory mounting between the developer and the target physical machine, and for starting the container. It should be noted that the functions of the first proxy program include, but are not limited to, this. It will be appreciated that agents are agents.
The file sharing service refers to an NFS (Network FILE SYSTEM ) service. By using the file sharing service, users can access files on the remote system as local files so that the nodes of each computer can use the resources on the network as conveniently as local resources.
The target mount point is a directory of the disk that the physical machine uses to mount the development machine. It will be appreciated that any directory on the physical machine may be used as the target mount point, and this embodiment is not limited herein.
After the target physical machine is allocated by the server to execute the target task, a first proxy program on the target physical machine is started, a certain file directory on the target physical machine is set as a target mounting point through the first proxy program, and after the developer starts the file sharing service, the root directory of the developer which starts the file sharing service is mounted to the target mounting point of the target physical machine through the first proxy program.
It can be appreciated that after the root directory of the development machine is mounted to the target mounting point of the target physical machine, the files on the development machine can be accessed by accessing the target mounting point of the target physical machine.
In some embodiments, a specified file directory on the target physical machine may be used as the target mount point, or any file directory on the target physical machine may be used as the target mount point. This is not limited.
In some embodiments, the file sharing service on the development machine may be turned on all the time without waiting for the target physical machine to be assigned by the server for performing the target task, while ensuring the absolute security of the development machine. In other embodiments, the file sharing service may not always be turned on by default, but may be triggered to be turned on under certain conditions.
Step 203, starting the target container through the first proxy program, and replacing the root directory of the target container with the target mounting point of the target physical machine.
Wherein the target container is a container created on the target physical machine. It will be appreciated that containers created on the target physical machine can use specific hardware resources of the target physical machine. The target container is used for isolating various resources required by executing the tasks, so that a plurality of tasks are supported to run on the same target physical machine to use special hardware resources of the target physical machine, and the aim of maximizing the utilization rate of the resources can be achieved.
Illustratively, after the root directory of the development machine is successfully mounted to the target mounting point of the target physical machine, the target physical machine starts the target container through the first proxy program, and replaces the root directory of the target container with the target mounting point of the target physical machine.
And 204, executing the target task through the target container to obtain a target task execution result.
The target task execution result is a result output in the process of executing the target task, namely an operation result of the operation code.
The target physical machine executes the target task through the target container to obtain a target task execution result.
In some embodiments, the target physical machine may send the target task execution result to the development machine, so that the development machine outputs and displays the target task execution result.
In some embodiments, after the target task execution ends, the target physical machine may destroy the created target container to reclaim the special hardware resources occupied by the target container.
In some embodiments, after the target task is executed, the developer may close the file sharing service, thereby improving security. In other embodiments, after the execution of the target task is finished, the development machine can keep the file sharing service in an on state all the time under the safe condition, so that when special hardware resources are needed to be used later, the task can be executed directly based on the file sharing service in the on state all the time by using the special hardware resources, and the execution efficiency of the task is improved.
In the hardware resource scheduling method, the root directory of the development machine is automatically mounted to the root directory of the target container through the first proxy program and the file sharing service, and the target task is executed through the target container, so that the consistency of the development environment and the running environment of the target task is ensured, the cost of the additional configuration environment of the development machine is reduced, the debugging time for combining the development machine with the special hardware resource is saved, the idle time after the special hardware resource is distributed to the development machine is reduced, and the utilization rate of the special hardware resource is further improved.
In some embodiments, the method further comprises:
The file sharing service is used for realizing file sharing between the development machine and the target physical machine.
Wherein the second agent refers to an agent running on the developer. When the execution command of the target task is monitored, the second agent program is awakened to start. It can be understood that in this embodiment, the second agent has a function of controlling the opening of the file sharing service, that is, the second agent can autonomously control the opening of the file sharing service.
The second agent program is pre-run on the development machine, and when the development machine sends an execution command for the target task to the server, the development machine wakes up to start the second agent program on the development machine, and the development machine starts file sharing service for a disk on the development machine through the second agent program on the development machine.
In some embodiments, the disk includes a system disk and a data disk, and the second agent on the development machine may open a file sharing service for both the system disk and the data disk on the development machine. It can be understood that the first proxy program on the target physical machine can mount the system disk and the data disk of the developing machine for starting the file sharing service, so as to mount the root directory of the developing machine to the target mounting point of the target physical machine. It will be appreciated that sharing of data disks and system disks can be achieved by the method of the present application.
The starting sequence of the first agent program and the second agent program may be changed, and may be determined according to the requirement, and the embodiment is not limited herein.
In the above embodiment, when the execution command of the target task is monitored, the file sharing service on the development machine is started through the second agent program, so that the root directory local to the development machine can be accessed by the target physical machine, and the storage space local to the target physical machine can be saved.
In some embodiments, the method further comprises destroying the target container by the first agent to reclaim the target physical machine after execution of the target task is completed, and closing the file sharing service by the second agent.
The method includes the steps of distributing the root directory of a development machine for starting file sharing service to a target mounting point of a target physical machine through a first proxy program, starting a target container, replacing the root directory of the target container with the target mounting point of the target physical machine, and executing the target task through the target container. After the target task is executed, destroying the target container by the first agent program to recycle the target physical machine, and closing the file sharing service by the second agent program.
In the embodiment, the target container is destroyed by the first proxy program after the target task is executed, so that the target physical machine is recovered, the waste of special hardware resources of the target physical machine can be avoided, meanwhile, the file sharing service is closed after the target task is executed, and the safety of data resources on the development machine and the target physical machine is ensured.
In some embodiments, determining the target physical machine in response to the execution command for the target task sent by the development machine includes resolving the execution command to obtain special hardware resource requirement information in response to the execution command for the target task sent by the development machine, and determining the target physical machine from the physical machine cluster according to the special hardware resource requirement information.
The special hardware resource requirement information refers to information of special hardware resources required for executing the target task. The special hardware resource requirement information includes the type, size, and number of special hardware resources.
A physical machine cluster refers to a group of physical computers with special hardware resources that the physical machine cluster provides to a developer as a whole.
When executing the target task requiring the special hardware resource, the server side responds to the execution command for the target task sent by the developer, analyzes the execution command to obtain the special hardware resource requirement information, and determines the target physical machine from the physical machine cluster according to the special hardware resource requirement information.
It can be understood that the server may select, from the physical machine cluster, a physical machine that meets the special hardware resource condition required by the special hardware resource requirement information as the target physical machine.
In some embodiments, the server configures the size and the number of the special hardware resources required for executing the target task according to the special hardware resource requirement information, and uses the physical machines capable of meeting the size and the number of the special hardware resources as target physical machines from the physical machine cluster according to the sorting algorithm.
In the above embodiment, the special hardware resource requirement information is determined according to the execution command of the target task, and the target physical machine meeting the special hardware resource requirement information is allocated, so that the special hardware resource is prevented from being wasted by adopting an on-demand allocation mode.
In some embodiments, after the target task is executed through the target container and the target task execution result is obtained, the method further comprises the steps of forwarding the target task execution result to a second agent program on the development machine through the first agent program, and receiving the target task execution result through a terminal receiving service started by the second agent program so as to output and display the target task execution result in the development machine.
The terminal receiving service refers to a system service component capable of transmitting input of a client to a background and transmitting output of the background back to the client. It can be understood that after the terminal is started to receive the service, the output of the background can be forwarded to the client, that is, the output log of the background can be forwarded to the client, so that the output of the background can be seen at the client.
Illustratively, after the developer sends the execution command for the target task, the developer opens the terminal to receive the service through the second agent, and after the target physical machine executes the target task through the target container, the developer obtains the execution result of the target task, the target physical machine forwards the target task execution result to a second agent program on the development machine through the first agent program, and the development machine receives the target task execution result through a terminal started by the second agent program, so that the target task execution result is output and displayed in the development machine.
In the above embodiment, the second agent is further configured to perform an agent docking function for forwarding communications between the developer and the physical machine, and by opening the terminal to receive the service, communication is set up between the first agent and the second agent, and the developer can see the target task execution result in the developer without performing additional operations, for example, without performing additional operations such as opening a web page or inputting a command, and can see the target task execution result in the developer, so that the developer can see the target task execution result.
In some embodiments, the method further comprises the steps of displaying a command line interface on the development machine, sending an execution command for the target task to the server according to an execution command code input on the command line interface, and determining the target physical machine in response to the execution command for the target task sent by the development machine, wherein the step of extracting the development machine identification in the execution command by the server comprises the step of distributing a corresponding target physical machine for the development machine uniquely represented by the development machine identification.
Among them, command line interface (CLI, command-LINE INTERFACE) is the most widely used user interface before the graphic user interface is popularized, usually does not support a mouse, and a user inputs an instruction through a keyboard, and the computer receives the instruction and then executes the instruction.
The developer identification is a uuid (Universally Unique Identifier, universal unique identification code) pre-stored on the developer. The developer identification is used to uniquely identify the developer.
Illustratively, a developer invokes a command line interface of the developer to cause the command line interface to be displayed on the developer, and the developer sends an execution command for a target task to the server according to an execution command code input by the developer on the command line interface. It will be appreciated that the execution command code includes a developer identifier, and therefore, the generated execution command for the target task also includes a developer identifier. The server side responds to an execution command aiming at a target task and sent by the development machine, extracts the development machine identification in the execution command, and distributes a corresponding target physical machine for the development machine uniquely represented by the development machine identification.
In the above embodiment, the target physical machine is allocated to the development machine uniquely characterized by the development machine identifier by extracting the development machine identifier in the execution command, so that the target physical machine is accurately allocated to the development machine.
In some embodiments, as shown in fig. 3, a flowchart of a method for scheduling hardware resources is provided, where the method is implemented through interaction among a server, a target physical machine, and a developer, and includes the following steps:
And 301, the development machine displays a command line interface, and the development machine sends an execution command aiming at the target task to the server according to the execution command code input in the command line interface.
And 302, the server side responds to an execution command aiming at a target task and sent by the development machine, analyzes the execution command to obtain special hardware resource demand information, and determines a target physical machine from a physical machine cluster according to the special hardware resource demand information.
The target physical machine is used for providing special hardware resources required for executing the target task.
Step 303, the server side extracts the developer identifier in the execution command of the target task, and allocates a corresponding target physical machine to the developer uniquely represented by the developer identifier.
Step 304, the second agent on the development machine is awakened and started, and the file sharing service is started for the system disk and the data disk on the development machine through the second agent on the development machine.
The file sharing service is used for realizing file sharing between the development machine and the target physical machine.
Step 305, starting a first proxy program on the target physical machine, and mounting the root directory of the development machine for starting the file sharing service to a target mounting point of the target physical machine through the first proxy program.
The starting sequence of the first agent program and the second agent program may be changed, and may be determined according to the requirement, and the embodiment is not limited herein.
And 306, the developer starts the target container through the first proxy program and replaces the root directory of the target container with the target mounting point of the target physical machine.
In step 307, the target physical machine executes the target task through the target container, and a target task execution result is obtained.
And 308, the target physical machine forwards the target task execution result to a second agent program on the development machine through the first agent program, and the development machine receives the target task execution result through a terminal receiving service started by the second agent program so as to output and display the target task execution result in the development machine.
And 309, after the target task is executed, destroying the target container by the target physical machine through the first agent program to recycle the target physical machine, and closing the file sharing service by the development machine through the second agent program.
In this embodiment, the root directory of the development machine is automatically mounted to the root directory of the target container through the first proxy program and the file sharing service, and the target task is executed through the target container, so that the consistency of the development environment and the running environment of the target task is ensured, the cost of the additional configuration environment of the development machine is reduced, the debugging time for combining the development machine with the special hardware resource is saved, the idle time after the special hardware resource is allocated to the development machine is reduced, and the utilization rate of the special hardware resource is further improved.
It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a hardware resource scheduling system for realizing the above related hardware resource scheduling method. The implementation of the solution provided by the system is similar to the implementation described in the above method, so the specific limitation in the embodiments of the hardware resource scheduling system provided below may refer to the limitation of the hardware resource scheduling method hereinabove, and will not be repeated herein.
In some embodiments, as shown in FIG. 4, a block diagram of a hardware resource scheduling system is provided, the system comprising a server 401 and a target physical machine 402.
The server 401 is configured to determine a target physical machine in response to an execution command for a target task sent by the developer, where the target physical machine is configured to provide special hardware resources required for executing the target task.
The target physical machine 402 is used for starting a first proxy program on the target physical machine, mounting a root directory of a development machine for starting file sharing service to a target mounting point of the target physical machine through the first proxy program, starting a target container through the first proxy program, replacing the root directory of the target container with the target mounting point of the target physical machine, and executing a target task through the target container to obtain a target task execution result.
In the hardware resource scheduling system, the root directory of the development machine is automatically mounted to the root directory of the target container through the first proxy program in the target physical machine and the file sharing service started on the development machine, and the target task is executed through the target container, so that the consistency of the development environment and the running environment of the target task is ensured, the debugging time for combining the development machine with the special hardware resource is saved, the idle time after the special hardware resource is distributed to the development personnel is reduced, and the utilization rate of the special hardware resource is further improved.
In some embodiments, as shown in FIG. 5, the system further includes a developer 403.
The development machine 403 is used for opening a file sharing service for a disk on the development machine 403 through a second agent program on the development machine 403, and the file sharing service is used for realizing file sharing between the development machine 403 and the target physical machine 402.
In some embodiments, the target physical machine 402 is configured to destroy the target container by the first agent after the target task is executed, to recycle the target physical machine 402, and the developer 403 is configured to close the file sharing service by the second agent.
In some embodiments, the server 401 is further configured to respond to an execution command for the target task sent by the developer 403, parse the execution command to obtain special hardware resource requirement information, and determine the target physical machine from the physical machine cluster according to the special hardware resource requirement information.
In some embodiments, after the target task is executed through the target container and the target task execution result is obtained, the target physical machine 402 is further configured to forward the target task execution result to a second agent on the developer through the first agent, and the developer 403 is further configured to receive the target task execution result through a terminal receiving service started by the second agent, so as to output and display the target task execution result.
In some embodiments, the development machine 403 is further configured to display a command line interface, and send an execution command for the target task to the server 401 according to the execution command code input in the command line interface. The server 401 is further configured to extract a developer identifier in the execution command, and allocate a corresponding target physical machine 402 to a developer 403 uniquely represented by the developer identifier.
In some embodiments, a computer device is provided, which may be a server or a target physical machine, and an internal structure diagram thereof may be as shown in fig. 6. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to perform at least part of the steps of a method for scheduling hardware resources.
In some embodiments, a computer device is provided, which may be a development machine, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to perform at least part of the steps of a method for scheduling hardware resources. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in FIG. 7 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components. In some embodiments, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.
In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the method embodiments described above.
In some embodiments, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.
Those skilled in the art will appreciate that implementing all or part of the above-described methods may be accomplished by way of a computer program, which may be stored on a non-transitory computer readable storage medium and which, when executed, may comprise the steps of the above-described embodiments of the methods. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.