Information sending method, device, storage medium and server

Abstract

The present specification discloses an information sending method, device, storage medium and server, wherein the method comprises: receiving second description information of a target task sent by a task conversion module, the second description information being obtained by compressing the first description information of the received target task by the task conversion module, sending the second description information to a task organization corresponding to a task organization identifier, downloading an executable file to the task organization based on executable file information, and starting the executable file so that the executable file obtains input parameters from a database based on tags.

Description

Technical Field

[0001] The present invention relates to the field of computers, and more particularly to an information delivery method, device, storage medium and server. Background Art

[0002] With the introduction of various privacy protection laws, cross-institutional transactions and flows of data have been banned. At the same time, institutions themselves also have the need to protect data security and prevent data leakage. Therefore, multi-party secure computing technology (MPC) came into being. MPC technology can ensure that the joint training and prediction of the model can be completed without the original data of the institution leaving the domain, so it is adopted by more and more institutions. Summary of the invention

[0003] The embodiments of this specification provide a method, device, storage medium and server for sending information, which can compress the first description information to obtain the second description information, ensure that the size of the second description information is smaller than the size limit of the task scheduling platform, send the second description information, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information. The technical solution is as follows:

[0004] In a first aspect, an embodiment of the present specification provides an information delivery method, which is applied to a task scheduling platform, and the method includes:

[0005] Receive second description information of the target task sent by the task conversion module, the second description information is obtained by the task conversion module after compressing the first description information of the target task received, the first description information at least includes the task organization identifier, executable file information and input parameters, the second description information at least includes the task organization identifier, the executable file information and labels corresponding to the input parameters, and the labels and the input parameters are stored in a database;

[0006] Sending the second description information to the task organization corresponding to the task organization identifier;

[0007] The executable file is downloaded to the task mechanism based on the executable file information, and the executable file is started, so that the executable file obtains the input parameter from the database based on the tag.

[0008] In a second aspect, an embodiment of the present specification provides an information delivery method, which is applied to a task scheduling platform, and the method includes:

[0009] Acquire first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0010] Acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information, and the label;

[0011] The second description information is sent to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the label.

[0012] In a third aspect, an embodiment of this specification provides an information delivery device, which is applied to a task conversion module, and the method includes:

[0013] An information receiving module, used for receiving second description information of a target task sent by a task conversion module, wherein the second description information is obtained by compressing the first description information of the target task received by the task conversion module, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters, and the second description information at least includes the task organization identifier, the executable file information, and labels corresponding to the input parameters, and the labels and the input parameters are stored in a database;

[0014] An information sending module, used for sending the second description information to the task organization corresponding to the task organization identifier;

[0015] A parameter acquisition module is used to download the executable file to the task mechanism based on the executable file information, and start the executable file so that the executable file acquires the input parameter from the database based on the tag.

[0016] In a fourth aspect, an embodiment of the present specification provides an information delivery device, which is applied to a task conversion module, and the device includes:

[0017] A first information acquisition module, used to acquire first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0018] A second information acquisition module is used to acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information and the label;

[0019] A parameter acquisition module is used to send the second description information to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the label.

[0020] In a fifth aspect, an embodiment of the present specification provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0021] In a sixth aspect, an embodiment of the present specification provides a server, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0022] The beneficial effects brought by the technical solutions provided in the embodiments of this specification include at least:

[0023] According to the embodiment of the present specification, the second description information is obtained by compressing the first description information, and the second description information is sent to the corresponding task mechanism, and the executable file is started in the task mechanism to obtain the input parameters from the database, so as to execute the corresponding task. Therefore, the second description information is obtained by compressing the first description information, which can ensure that the size of the second description information is smaller than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 This is a system architecture diagram of an information delivery method provided by an embodiment of this specification;

[0026] Figure 2 This is a flow chart of a method for sending information provided by an embodiment of this specification;

[0027] Figure 3 This is an example schematic diagram of viewing input parameters provided in the embodiments of this specification;

[0028] Figure 4 This is an example schematic diagram of sending second description information provided by an embodiment of this specification;

[0029] Figure 5 This is an example diagram of obtaining input parameters provided in the embodiment of this specification.

[0030] Figure 6 This is a flow chart of information delivery provided by an embodiment of this specification;

[0031] Figure 7 This is an example schematic diagram of obtaining input parameters provided in an embodiment of this specification;

[0032] Figure 8 This is a flow chart of information delivery provided by an embodiment of this specification;

[0033] Fig. 9 This is an example schematic diagram of obtaining an executable file provided in an embodiment of this specification;

[0034] Fig.10 This is an example schematic diagram of outputting prompt information provided in an embodiment of this specification;

[0035] Fig.11 This is a flow chart of information delivery provided by an embodiment of this specification;

[0036] Fig.12 This is a flow chart of information delivery provided by an embodiment of this specification;

[0037] Fig.13 This is an example schematic diagram of outputting prompt information provided in an embodiment of this specification;

[0038] Fig.14 It is a structural diagram of an information sending device provided in an embodiment of this specification;

[0039] Fig.15 It is a structural diagram of a parameter acquisition module provided in an embodiment of this specification;

[0040] Fig.16 It is a structural diagram of an information sending device provided in an embodiment of this specification;

[0041] Fig.17 is a structural diagram of a second information acquisition module provided in an embodiment of this specification;

[0042] Fig.18 is a structural diagram of a label acquisition unit provided in an embodiment of this specification;

[0043] Fig.19It is a structural diagram of an information sending device provided in an embodiment of this specification;

[0044] Fig. 20 It is a structural diagram of a server provided in an embodiment of this specification;

[0045] Fig.21 It is a structural diagram of a server provided in an embodiment of this specification. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of this specification more clear, the implementation methods of this specification will be further described in detail below with reference to the accompanying drawings.

[0047] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Instead, they are only examples of devices and methods consistent with some aspects of this specification as detailed in the attached claims.

[0048] In the description of this specification, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in this specification can be understood according to the specific circumstances. In addition, in the description of this specification, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previously associated objects are in an "or" relationship.

[0049] At present, MPC tasks can be completed on the task scheduling platform (Kubernetes, K8s). K8s is an automated container orchestration and scheduling platform that can automatically manage the hardware resources of the organization's machines and automatically schedule training tasks and model prediction tasks to appropriate machines based on the idleness of the machines. However, due to system design reasons, K8s does not consider the scenario where the task description file exceeds 1MB. If the description information required for the task exceeds 1MB, K8s does not support it and cannot complete the submission.

[0050] In the prior art, to execute an MPC task based on K8s, the task description information needs to be saved as a separate file in advance and placed on the machine in advance. The K8s task description file only records the storage path of the file. After K8s starts the task, the executable file reads the external file according to the path in the description file to obtain the real task description information. If the external file is placed in the wrong path or is placed after the task is started, the task cannot be run.

[0051] Based on this, the embodiment of this specification provides an information sending method, which compresses the first description information to obtain the second description information, sends the second description information to the task mechanism, and starts the executable file in the task mechanism to obtain the input parameters from the database, so as to execute the corresponding task. Therefore, it can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and send the second description information, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0052] The present specification is described in detail below with reference to specific embodiments.

[0053] See also Figure 1 , which is a system architecture diagram of an information sending method provided in an embodiment of this specification.

[0054] like Figure 1 As shown, the figure includes a task conversion module, a database, a task scheduling platform and a task agency. The task conversion module can be a server or a service provided in a server, which is used to parse, compress and process the first description information submitted by the user to obtain the second description information, and at the same time obtain the label and store the input parameters and labels in the first description information in the database; the database can be of various types, such as a KV database, a relational database, a new non-relational database, an object storage system or Alibaba Cloud, etc., which is used to store data information such as labels and input parameters; the task scheduling platform can be a server or a cluster of multiple servers, including a task switching module and an execution node, the task switching module is used to receive and send files, and transmit the received second description information to the task agency, and the execution node is used to start the executable file in the task agency; the task agency can be an entity, such as a bank or an enterprise, etc., or it can be a terminal, such as a smart mobile terminal, a desktop computer, etc., which is used as an execution subject for executing tasks based on description information such as task parameters.

[0055] When a target task is to be performed, in step ①, the user submits first description information to the task conversion module, and the first description information includes at least the task organization identifier, executable file information and input parameters; the task conversion module executes step ② to compress the first description information to obtain second description information and send it to the task scheduling platform, and at the same time executes step ③ to store the tags generated during the compression process and the input parameters in the first description information in the database, and the second description information includes at least the task organization identifier, executable file information and tags corresponding to the input parameters; the tags are used to retrieve and obtain the input parameters in the database; the task scheduling platform executes step ④ to send the second description information to the task organization, and obtains the executable file in the task organization based on the executable file information and starts the executable file, so that the executable file executes step ⑤ to access the task conversion module based on the tag, the task conversion module executes step ⑥ to execute step ⑦ in the database based on the tag sent by the executable file to obtain the corresponding input parameters, and executes step ⑧ to send the input parameters to the task organization where the executable file is located.

[0056] By using the above method, the first description information is compressed to obtain the second description information, which can ensure that the size of the second description information is smaller than the size limit of the task scheduling platform. The second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0057] See also Figure 2 , is a flow chart of a method for sending information provided in an embodiment of this specification. This embodiment of this specification takes the task conversion module and the task scheduling platform as an example to describe the method for sending information, and the method may include the following steps:

[0058] S102, the task conversion module obtains first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0059] When performing a target task, the user submits the first description information of the target task to be executed to the task conversion module. The first description information obtained by the task conversion module includes the task organization identifier corresponding to the task organization that executes the task, executable file information, and input parameters corresponding to the target task.

[0060] Among them, the target task can be a unilateral computing task or a multi-party computing task. When executing a unilateral computing task, the user submits the task description information, and the task scheduling platform sends the task description information to the task agency, which then executes the target task; when executing a multi-party computing task, the user submits the task, and the task scheduling platform sends the task description information to the corresponding task agencies, and each task agency executes its own task to complete the execution of the target task.

[0061] Among them, the first description information corresponding to the target task submitted by the user may include at least the task organization identification, executable file information and input parameter files. The first description information may be in the form of a file, that is, a first description file, or in other forms, such as a string or a Json text. The form of the first description information is not limited here.

[0062] It should be noted that if the first description information includes multiple task organization identifiers, there will be a corresponding number of first description information in the first description information, that is, each task organization identifier corresponds to one first description information, so as to facilitate subsequent task allocation. Different first description information may be the same information except for the task organization identifier, or may be different information. Whether the information content is the same is not limited here.

[0063] It should be noted that in addition to submitting a task description file, the user can also submit a mirror file for executing the task. The mirror file includes at least the executable file and corresponding configuration parameters and other information. The mirror file can be stored in an independent database or in the database of the task agency. This is not specifically limited here. After the mirror file is stored, a table for recording tags and corresponding input parameters is generated. In addition to displaying the name of the mirror file, the mirror file identifier in the table can also be a link to jump to the specific content corresponding to the mirror file, such as Figure 3 As shown, after obtaining the permission to directly access the database data, the user can click the name of the image file on the database display page, and the content displayed on the database display page will directly jump to the page displaying the specific content of the input parameter.

[0064] The task agency identifier may be the name of the task agency or a code used to identify the task agency. The specific type of the identifier is not limited here.

[0065] Among them, the executable file information may include identification information for marking the image file corresponding to the execution target task, such as the name of the image file and the storage location of the image file, and may also include the path of the executable file in the image file, through which the executable file can be obtained in the image file.

[0066] The input parameters may be parameter information required to execute the target task, such as configuration information, etc. The format of the input parameters may be a file or a string, etc., and the format of the input parameters is not limited here.

[0067] S104, the task conversion module obtains a label corresponding to the input parameter, stores the label and the input parameter in a database, and obtains second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information, and the label;

[0068] After obtaining the first description information, further obtain the label corresponding to the input parameter in the first description information, store the label and the input parameter in the database, and then replace the input parameter with the obtained label to obtain the second description information. The obtained second description information can at least include the task organization identification, executable file information and label.

[0069] The method for obtaining the label corresponding to the input parameter can be that the task conversion module generates the corresponding label for the input parameter, or the label is submitted by the user himself. The origin of the label is not limited here. However, it should be noted that in order to ensure that the input parameter can be retrieved and obtained in the database through the label later, the uniqueness of the label needs to be guaranteed.

[0070] Among them, the method for storing the label and the input parameter in the database is to generate a record as shown in Table 1 to mark the relationship between the label and the input parameter after storing the label and the input parameter in the database, and the label is used as a retrieval key. The corresponding input parameter in the database can be retrieved through the label as a key, which facilitates subsequent retrieval and acquisition.

[0071] The method for obtaining the second description information may be to remove the input parameters in the first description information and add the obtained tags to the first description information, thereby completing the process of replacing the input parameters with tags to obtain the second description information.

[0072] Among them, the label can be a piece of text information used to identify the input parameter, such as 0132 in Table 1, and the input parameter corresponding to the label is the 0132.zip file. The label and the corresponding input parameter are stored in the database together. When it is necessary to obtain the input parameter "0132.zip" from the database, it can be retrieved through the label "0132" to obtain the input parameter.

[0073] Table 1

[0074] Serial number Label Input Parameters 1 0132 0132.zip … … …

[0075] S106, the task conversion module sends the second description information to the task scheduling platform;

[0076] After obtaining the second description information, the task conversion module sends the second description information to the task scheduling platform.

[0077] Among them, the method of sending the second description information can be various, for example, the second description information can be directly sent to the task scheduling platform, or the second description information can be packaged and then the packaged second description information is sent to the task scheduling platform. The method of sending the second description information is not limited here.

[0078] The method for encapsulating the second description information may be to compress the second description information to obtain a compressed file for easy transmission, or to encapsulate the second description information into a "class" to improve security.

[0079] The class may be a data type, including data and corresponding operation data. Encapsulating the second description information into a class can facilitate transmission while improving transmission security.

[0080] S108, the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier;

[0081] After receiving the second description information, the task scheduling platform identifies the second description information, and after identifying the task organization identifier in the second description information, sends the second description information to the task organization corresponding to the task organization identifier.

[0082] In one embodiment, after identifying the task organization identifier in the second description information, if there is only one task organization identifier, it means that there is only one task organization, and the second description information is sent to the task organization; if there is more than one task organization identifier in the second description information, it means that there is more than one task organization, such as Figure 4 As shown, Figure 4 The task scheduling platform sends each second description information in the figure to the corresponding first task agency and second task agency respectively through the task agency identifier, so that each task agency performs its own task. The contents of the two second description information can be the same information except for the task agency identifier, or they can be different information. Whether the information content is the same is not limited here.

[0083] S110, downloading the executable file to the task mechanism based on the executable file information, and starting the executable file, so that the executable file obtains the input parameter from the database based on the tag, and instructs the task conversion module to send the input parameter;

[0084] After the second description information is sent to the task agency, the execution node in the task scheduling platform downloads the image file from the database storing the image file through the marking information of the image file in the executable file information in the second description information in the task agency, and then obtains the executable file through the path of the executable file in the image file in the executable file information, and starts the executable file. After starting the executable file, the executable file accesses the task conversion module based on the label to obtain the input parameters required to execute the task. After receiving the label sent by the executable file, the task conversion module retrieves and obtains the input parameters corresponding to the label in the database, and returns the input parameters to the task agency where the executable file is located, so as to execute the task.

[0085] Among them, the executable file can be a process file used to execute a task. Various tasks can be executed through the executable file to achieve the desired effect of the target task. There are many types of executable files, such as ".exe", ".sys", ".com" or ".apk" file types, and the file type of the executable file is not limited here.

[0086] When the executable file accesses the task conversion module, it sends a request for obtaining input parameters, and the sent request carries the tag in the second description information, so that the task conversion module can retrieve the corresponding input parameter in the database through the tag.

[0087] In one embodiment, the method for the task conversion module to obtain the input parameter in the database based on the tag can be to find the input parameter corresponding to the tag in Table 1 through the tag, and download the input parameter from the database and send it to the task mechanism where the executable file is located. The method for sending the input parameter can be to directly send it to the corresponding task mechanism through the network; or Figure 5 As shown, Figure 5 The task scheduling platform places the input parameters on a web page, and then the executable file of the task organization obtains the input parameters on the web page. The method of generating input parameters for the task conversion module is not limited here.

[0088] By adopting the embodiment of this specification, the input parameters in the first description information of the target task submitted by the user are stored and replaced to obtain the second description information, and then the second description information is sent to the task agency, and the executable file is started in the task agency so that the executable file obtains the input parameters. After reducing the size of the description information, the description information is sent down to execute the corresponding task. Through the embodiment of this specification, the first description information is compressed to obtain the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0089] See also Figure 6 , is a flow chart of a method for sending information provided in an embodiment of this specification. This embodiment of this specification is described by taking a task scheduling platform as an example. The method for sending information may include the following steps:

[0090] S202, receiving second description information of the target task sent by the task conversion module, the second description information is obtained by the task conversion module after compressing the received first description information of the target task, the first description information at least includes the task organization identifier, the executable file information and the input parameters, the second description information at least includes the task organization identifier, the executable file information and the label corresponding to the input parameter, and the label and the input parameter are stored in a database;

[0091] The task switching module in the task scheduling platform receives the second description information sent by the task conversion module. The second description information can be obtained by compressing the first description information by the task conversion module.

[0092] Among them, the task scheduling platform can be a platform for receiving and issuing task description information, including two modules: a task switching module and an execution node. The task switching module is used to receive and issue description information, and the execution node is used to start the task in the task organization.

[0093] The task conversion module may be a server or a service provided by a server, and is used to extract the input parameters in the first description information, obtain the labels corresponding to the input parameters, and store the labels and the input parameters in a database. In addition, the task conversion module replaces the input parameters in the first description information with the labels to obtain the second description information, and sends the second description information to the task scheduling platform.

[0094] Wherein, obtaining the label corresponding to the input parameter may be generating the corresponding label for the input parameter, or the user may add the label by himself. It should be noted that in order to ensure that the corresponding input parameter can be obtained in the database through the label, the uniqueness of the label needs to be guaranteed. If the label is not a unique label, a prompt message may be output to prompt the user that the obtained label is not a unique label. The method of outputting the prompt message is not limited here.

[0095] The specific definitions of the task organization identifier, executable file information, and input parameters and tags in the first description information and the second description information can be found in step S102 and will not be described in detail here.

[0096] S204, sending the second description information to the task organization corresponding to the task organization identifier;

[0097] For details, please refer to step S108, which will not be described in detail here.

[0098] S206, downloading the executable file to the task mechanism based on the executable file information, and starting the executable file, so that the executable file obtains the input parameter from the database based on the tag.

[0099] In one embodiment, Figure 7 As shown, after the task scheduling platform sends the second description information to the corresponding task agency, the execution node of the task scheduling platform executes step ① in the task agency through the executable file information in the second description information, and then executes step ② to download the corresponding image file in the executable file information, and executes step ③ to determine after obtaining the image file Figure 7 The executable file path "xxx" in the executable file information is obtained, thereby executing step ④ to obtain the executable file and start the executable file, so that the executable file executes step 5 to access the task conversion module based on the label in the second description information, so that the task conversion module executes steps 6 and 7 to obtain the input parameters corresponding to the label in the database and executes step 8 to return to the executable file.

[0100] Among them, since the executable file information includes the identification information of the image file, the image file corresponding to the identification information is obtained in the database through the identification information. The specific path for obtaining the image file is determined according to the specific storage location of the image file. If the image file is stored in an independent database, it is downloaded from the database. If the image file is stored in the database of the task agency, it is obtained from the database of the task agency.

[0101] After the image file is obtained, the executable file is obtained based on the path of the executable file in the image file in the executable file information, and the executable file is started to obtain input parameters for executing the task.

[0102] By adopting the embodiment of this specification, the second description information is obtained by compressing the first description information, the second description information is sent to the corresponding task mechanism, and the executable file is started in the task mechanism to obtain the input parameters from the database, so as to execute the corresponding task. By adopting the embodiment of this specification, the first description information is compressed to obtain the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0103] See also Figure 8 , is a flow chart of a method for sending information provided in an embodiment of this specification. This embodiment of this specification is described by taking a task scheduling platform as an example. The method for sending information may include the following steps:

[0104] S302, receiving second description information of the target task sent by the task conversion module, the second description information is obtained by the task conversion module after compressing the received first description information of the target task, the first description information at least includes the task organization identifier, the executable file information and the input parameters, the second description information at least includes the task organization identifier, the executable file information and the label corresponding to the input parameter, and the label and the input parameter are stored in a database;

[0105] For details, please refer to step S202, which will not be described here in detail.

[0106] S304, sending the second description information to the task organization corresponding to the task organization identifier;

[0107] For details, please refer to step S204, which will not be described in detail here.

[0108] S306, the executable file information includes an image file identifier and a storage path of the executable file in the image file corresponding to the image file identifier, and the image file corresponding to the image file identifier is downloaded to the task mechanism;

[0109] After the second description information is sent to the task agency, the execution node of the task scheduling platform set up in the task agency downloads the corresponding image file to the task agency through the image file identifier of the executable file information in the second description information.

[0110] The image file can be downloaded by identifying the executable file information in the second description information, determining the identification information of the image file and the storage location of the image file, searching the storage location by the identification information based on the storage location and the identification information, and downloading the retrieved image file to the task mechanism. For example, the storage location of the image file is an independent database, and the execution node sends a request to the database, the request carries the identification information of the image file, and searches the database for the image file by the identification information, and downloads the image file to the task mechanism after the image file is retrieved from the database.

[0111] S308, obtaining the executable file in the image file based on the storage path;

[0112] After the task agency obtains the image file, it obtains the executable file from the image file based on the storage path of the executable file in the image file in the executable file information.

[0113] The method for obtaining the executable file based on the storage path is to directly decompress the executable file from the image file into a folder in the same path as the image file, such as Fig. 9 As shown, based on Fig. 9 The executable file path in the executable file information in the image file is determined, and the storage path of the executable file is determined in the image file, so as to obtain the executable file in the image file; or the entire image file can be compressed to obtain a folder, which includes all the contents in the image file, and then the executable file is obtained from the folder.

[0114] S310, starting the executable file so that the executable file obtains the input parameter from the database based on the tag;

[0115] In one embodiment, after the executable file is obtained, the executable file is started. The method for starting the executable file can be to start the executable file immediately after the executable file is obtained, or to output a prompt message to the user after receiving the executable file, indicating that the task agency has received the executable file and asking whether to start the startup. After receiving the instruction to confirm the startup, the executable file is started. After starting the executable file, the executable file is made to access the task conversion module based on the tag to initiate an acquisition request to obtain input parameters. After receiving the request sent by the executable file, the task conversion module searches the database according to the tag and sends the retrieved input parameters to the task agency where the executable file is located.

[0116] Among them, the method of outputting the prompt information can be output in the form of text, audio, image and video. A feasible method is as follows Fig.10As shown, a pop-up window with the text "Do you want to start XXX application" is displayed on the terminal display page of the task agency as a prompt message to ask the user whether to start the executable file.

[0117] Among them, after the task conversion module receives the request, the method for obtaining the input parameter based on the tag is to retrieve the tag in the database. For example, the tag is "0132" in Table 1. After retrieving the tag, the input parameter "0132.zip" corresponding to the tag and its corresponding storage path can be determined, and the input parameter can be obtained through the storage path.

[0118] Among them, the method of sending the input parameters to the executable file can be to return the input parameters to the executable file through the connection established when the executable file sends the request; or the input parameters can be sent to a web page, and after receiving the input parameters sent by the task conversion module, the web page sends a prompt message to the task organization where the executable file is located to prompt that the input parameters can be downloaded on the web page, and the executable file then obtains the input parameters on the web page. The method of returning the input parameters to the executable file by the task conversion module is not limited here.

[0119] According to the embodiment of the present specification, the second description information is obtained by compressing the first description information, and the second description information is sent to the corresponding task mechanism, and the executable file downloaded by the executable file information in the second description information is started in the task mechanism, and the executable file is made to access the task conversion module to initiate a request to obtain input parameters. After receiving the request, the task conversion module returns the input parameters to the executable file so as to execute the corresponding task. According to the embodiment of the present specification, the second description information is obtained by compressing the first description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0120] See also Fig.11 , is a flow chart of a method for sending information provided in an embodiment of this specification. This embodiment of this specification takes the task conversion module as an example to describe, and the method for sending information may include the following steps:

[0121] S402, obtaining first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0122] For details, please refer to step S102, which will not be described in detail here.

[0123] S404, obtaining a label corresponding to the input parameter, storing the label and the input parameter in a database, and obtaining second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information, and the label;

[0124] For details, please refer to step S104, which will not be described in detail here.

[0125] S406, sending the second description information to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the tag;

[0126] After obtaining the second description information, the second description information is sent to the task scheduling platform, which instructs the task scheduling platform to send the second description information to the corresponding task organization, download the executable file in the task organization, and start the executable file, so that the executable file accesses the task conversion module based on the label in the second description information to issue a request to obtain input parameters. After receiving the request, the task conversion module retrieves the corresponding input parameters in the database based on the label, and returns the input parameters to the executable file.

[0127] The process of obtaining the input parameters after the task scheduling platform downloads the executable file and starts the executable file can be referred to in step S108 and step S110, which will not be described in detail here.

[0128] By adopting the embodiment of this specification, by obtaining the first description information, after obtaining the label corresponding to the input parameter in the first description information, the label and the input parameter are stored in the database, and then the input parameter in the first description information is replaced with the label to obtain the second description information, and the second description information is sent to the task scheduling platform and then to the task agency, and the executable file is downloaded and started in the task agency, so as to access the task conversion module to obtain the input parameter in order to execute the corresponding task. Through the embodiment of this specification, the label corresponding to the input parameter in the first description information is obtained, and the label is replaced with the input parameter to generate the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0129] See also Fig.12 , is a flow chart of a method for sending information provided in an embodiment of this specification. This embodiment of this specification takes the task conversion module as an example to describe, and the method for sending information may include the following steps:

[0130] S502, receiving an uploaded description file of the target task, and extracting first description information from the description file;

[0131] A description file of a target task uploaded by a user is received, and first description information is extracted from the description file, and the first description information is used as basic information required for describing the execution of the target task.

[0132] Among them, the description file of the target task may include not only the basic content for describing the execution of the task, such as the task agency identification for determining the execution agency, the executable file information for obtaining the image file, and the input parameters for executing the file, but also other information such as the purpose of the task, the effect of the task, etc. The information required for the specific execution of the task is the task agency identification, the executable file information, and the input parameters, so it is extracted as the first description information, which is used to publish the task description file to complete the execution of the task.

[0133] S504, receiving the uploaded image file of the target task, and storing the image file in a database, wherein the image file includes at least an executable file;

[0134] Receive the image file corresponding to the target task transmitted by the user, store the image file in the database, and add the storage path of the image file in the database to the first description information.

[0135] The image file may be a compressed file including multiple files, and may be a file obtained by compressing multiple files including at least an executable file used as an execution subject and other functions required to run the executable file. The file type of the image file may be multiple, such as ".iso", ".mds", ".cdd" and other file types, and the file type of the image file is not limited here.

[0136] S506, obtaining first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0137] For details, please refer to step S102, which will not be described in detail here.

[0138] S508, generating a label corresponding to the input parameter;

[0139] After the first description information is acquired, a corresponding label is generated for the input parameter in the first description information, so that the corresponding input parameter can be determined through the label.

[0140] Among them, the method for generating the label can be to generate corresponding characters for the name of the input parameter. For example, if the name of the input parameter is "0132.zip" in Table 1, then "0132" can be generated as the label of the input parameter; the label can also be generated according to the function of the input parameter. For example, the function of the "0132.zip" input parameter is an input parameter of a mirror file used to perform statistical functions, then the generated label can be in the form of characters such as "tongji_0132" that reflect the function. The specific method of generating the label is not limited here.

[0141] S510, obtaining the uploaded tag, and establishing a corresponding relationship between the tag and the input parameter;

[0142] In addition to generating corresponding labels for input parameters by themselves, users can also directly upload a label to mark the input parameters, and establish a corresponding relationship between the uploaded label and the input parameter, so as to facilitate subsequent retrieval and acquisition of the input parameter through the label.

[0143] Among them, the label uploaded by the user can be any character or string that meets the system requirements. The specific requirements can be limited according to the system requirements. For example, some systems do not support the recognition of Chinese characters, so the uploaded label needs to be a non-Chinese character or string. For example, some systems do not support the recognition of special symbols, etc. Corresponding changes are made to the requirements of different systems to make the label meet the requirements of the system, so that the system detects the label and establishes the corresponding relationship between the label and the input parameter. The content of the uploaded label is not limited here.

[0144] S512, obtaining a label corresponding to the input parameter;

[0145] S514, determining whether the tag is unique;

[0146] The obtained label is compared with the labels already in the database to determine whether the label is different from all the labels already in the database and is unique.

[0147] It should be noted that in order to ensure that the corresponding input parameters can be retrieved in the database through the label, the label must be unique. Otherwise, if two identical labels exist in the database, it is impossible to determine which input parameter is the desired input parameter through the label, which will cause the management of the entire system to be in a chaotic state and affect the execution of the target task.

[0148] S516, if the tag is unique, storing the tag and the input parameter in the database;

[0149] If after comparison and judgment, it is determined that the tag is the only tag in the database and is unique, the tag and the corresponding input parameter are stored in the database, and a record is written in a table as shown in Table 1 to record the corresponding relationship between the tag and the input parameter.

[0150] Among them, when storing the label and input parameters in the database, in addition to outputting the corresponding records, the corresponding reading path of the label and input parameter is generated. When the label is retrieved, the storage path of the corresponding input parameter in the database can be obtained, so that the corresponding input parameter can be obtained through the label later.

[0151] S518, if the label is not unique, outputting an error prompt message, wherein the error prompt message is used to prompt updating of the label;

[0152] If the obtained label is compared with the existing labels in the database and it is found that the existing labels in the database have the same label as the obtained label, it means that the label is not a unique label and is not unique. Then a prompt message is output to prompt the user to change the label.

[0153] The method of outputting the prompt information may be in the form of text, image, audio or video. A feasible method is as follows: Fig.13 As shown, a pop-up window with a prompt message "Label already exists" is displayed on the display page of the task conversion module to prompt the user to change the label.

[0154] S520, replacing an input parameter in the first description information with the label to obtain second description information;

[0155] After determining that the tag is unique and storing the tag and the corresponding input parameters in the database, the tag replaces the input parameters in the first description information to obtain the second description information. Therefore, the first description information is transformed from the task organization identifier, executable file information and input parameters to the second description file including the task organization identifier, executable file information and the tag.

[0156] It should be noted that since the task scheduling platform has a size limit on the description information received and sent, and the size of the input parameters may be larger than the limit of the task scheduling platform, in order to ensure that the description information can be sent smoothly, the label replaces the input parameter to ensure that the size of the description information is smaller than the limit of the task scheduling platform.

[0157] S522, sending the second description information to the task scheduling platform, so that the task scheduling platform downloads the image file from the database to the task mechanism based on the executable file information, and starts the executable file in the image file, so that the executable file obtains the input parameter from the database based on the tag;

[0158] For details, please refer to step S406, which will not be described in detail here.

[0159] By adopting the embodiment of this specification, the first description information of the target task is obtained by extracting the description file of the target task uploaded by the user, and the image file uploaded by the user is stored in the database at the same time, and after obtaining the label corresponding to the input parameter in the first description information, the label and the input parameter are stored in the database, and the label is detected before storage to determine whether the label is unique to ensure the availability of the label, and then the label is replaced with the input parameter to generate the second description information, and the second description information is sent to the task scheduling platform, and then the task scheduling platform sends it to the task agency to start the executable file and obtain the input parameters, so as to execute the corresponding task. Through the embodiment of this specification, after ensuring the uniqueness of the label, the label and the input parameter are stored in the database, and the label is replaced with the input parameter to generate the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0160] See also Fig.14 , which shows a schematic diagram of the structure of an information sending device provided by an exemplary embodiment of this specification. The information sending device can be implemented by software, hardware or a combination of both to realize all or part of the terminal. The device 1 includes an information receiving module 11, an information sending module 12 and a parameter acquisition module 13.

[0161] An information receiving module 11 is used to receive second description information of a target task sent by a task conversion module, wherein the second description information is obtained by compressing the first description information of the target task received by the task conversion module, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters, and the second description information at least includes the task organization identifier, the executable file information, and labels corresponding to the input parameters, and the labels and the input parameters are stored in a database;

[0162] An information sending module 12 is used to send the second description information to the task organization corresponding to the task organization identifier;

[0163] The parameter acquisition module 13 is used to download the executable file to the task mechanism based on the executable file information, and start the executable file so that the executable file acquires the input parameter from the database based on the tag.

[0164] Optional, such as Fig.15 As shown, the parameter acquisition module 13 includes:

[0165] An image file downloading unit 131, used for downloading the image file corresponding to the image file identifier to the task mechanism;

[0166] A file acquisition unit 132, configured to acquire the executable file from the image file based on the storage path;

[0167] The file starting unit 133 is used to start the executable file.

[0168] By adopting the embodiment of this specification, the second description information is obtained by compressing the first description information, the second description information is sent to the corresponding task mechanism, and the executable file is started in the task mechanism to obtain the input parameters from the database, so as to execute the corresponding task. By adopting the embodiment of this specification, the first description information is compressed to obtain the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0169] See also Fig.16 , which shows a schematic diagram of the structure of an information sending device provided by an exemplary embodiment of this specification. The information sending execution device can be implemented by software, hardware or a combination of both to realize all or part of the terminal. The device 2 includes a first information acquisition module 21, a second information acquisition module 22 and a parameter acquisition module 23.

[0170] A first information acquisition module 21 is used to acquire first description information of a target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0171] A second information acquisition module 22 is used to acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information and the label;

[0172] The parameter acquisition module 23 is used to send the second description information to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the label.

[0173] Optional, such as Fig.17 As shown, the second information acquisition module 22 includes:

[0174] A label generating unit 221, configured to generate a label corresponding to the input parameter, and store the label and the input parameter in a database;

[0175] A second information acquisition unit 222, configured to replace an input parameter in the first description information with the label to obtain second description information;

[0176] or,

[0177] The tag acquisition unit 223 is used to acquire the uploaded tag, establish a corresponding relationship between the tag and the input parameter, and store the tag and the input parameter in a database;

[0178] The second information acquisition unit 222 is configured to replace the input parameter in the first description information with the label to obtain second description information.

[0179] Optional, such as Fig.18 As shown, the label acquisition unit 223 includes:

[0180] The label acquisition subunit 2231 is used to acquire the label corresponding to the input parameter;

[0181] The tag determination subunit 2232 is used to determine whether the tag is unique;

[0182] The tag storage subunit 2233 is used to store the tag and the input parameter in the database if the tag is unique;

[0183] The device also includes:

[0184] The error prompt subunit 2234 is used to output an error prompt message if the label is not unique, and the error prompt message is used to prompt to update the label.

[0185] Optionally, the first information acquisition module 21 is further used to:

[0186] The uploaded description file of the target task is received, and the first description information in the description file is extracted.

[0187] Optional, such as Fig.19 As shown, the information sending device 2 further includes:

[0188] An image file storage module 24, used for receiving the uploaded image file of the target task and storing the image file in the database, wherein the image file at least includes the executable file;

[0189] The parameter acquisition module 23 is also used for:

[0190] The second description information is sent to the task scheduling platform so that the task scheduling platform downloads the image file from the database to the task mechanism based on the executable file information, and starts the executable file in the image file so that the executable file obtains the input parameter from the database based on the label.

[0191] By adopting the embodiment of this specification, the first description information of the target task is obtained by extracting the description file of the target task uploaded by the user, and the image file uploaded by the user is stored in the database at the same time, and after obtaining the label corresponding to the input parameter in the first description information, the label and the input parameter are stored in the database, and the label is detected before storage to determine whether the label is unique to ensure the availability of the label, and then the label is replaced with the input parameter to generate the second description information, and the second description information is sent to the task scheduling platform, and then the task scheduling platform sends it to the task agency to start the executable file and obtain the input parameters, so as to execute the corresponding task. Through the embodiment of this specification, after ensuring the uniqueness of the label, the label and the input parameter are stored in the database, and the label is replaced with the input parameter to generate the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0192] It should be noted that the information sending device provided in the above embodiment only uses the division of the above functional modules as an example when executing the information sending method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the information sending device provided in the above embodiment and the information sending method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0193] The serial numbers of the embodiments of this specification are for description only and do not represent the advantages or disadvantages of the embodiments.

[0194] The present specification also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 1-Figure 13 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 1-Figure 13 The specific description of the illustrated embodiment will not be repeated here.

[0195] The present specification also provides a server, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor. Figure 1-Figure 13 The specific description of the illustrated embodiment will not be repeated here.

[0196] See also Fig. 20 , which is a schematic diagram of the structure of a server provided in the embodiment of this specification. Fig. 20 As shown, the server 1000 may include: at least one processor 1001 , at least one network interface 1004 , a user interface 1003 , a memory 1005 , and at least one communication bus 1002 .

[0197] The communication bus 1002 is used to realize the connection and communication between these components.

[0198] The user interface 1003 may include a display screen (Display) and a camera (Camera), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.

[0199] The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0200] Among them, the processor 1001 may include one or more processing cores. The processor 1001 uses various interfaces and lines to connect various parts of the entire server 1000, and executes various functions and processes data of the server 1000 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1005, and calling data stored in the memory 1005. Optionally, the processor 1001 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1001 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 1001, and it can be implemented separately through a chip.

[0201] Among them, the memory 1005 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 1005 includes a non-transitory computer-readable storage medium. The memory 1005 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1005 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 1005 may optionally be at least one storage device located away from the aforementioned processor 1001. As Fig. 20 As shown, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an information delivery application.

[0202] exist Fig. 20In the server 1000 shown, the user interface 1003 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 1001 can be used to call the information stored in the memory 1005 to send the application program, and specifically perform the following operations:

[0203] Receive second description information of the target task sent by the task conversion module, the second description information is obtained by the task conversion module after compressing the first description information of the target task received, the first description information at least includes the task organization identifier, executable file information and input parameters, the second description information at least includes the task organization identifier, the executable file information and labels corresponding to the input parameters, and the labels and the input parameters are stored in a database;

[0204] Sending the second description information to the task organization corresponding to the task organization identifier;

[0205] The executable file is downloaded to the task mechanism based on the executable file information, and the executable file is started, so that the executable file obtains the input parameter from the database based on the tag.

[0206] In one embodiment, when the processor 1001 executes the executable file information including the image file identifier and the storage path of the executable file in the image file corresponding to the image file identifier, downloads the executable file to the task mechanism based on the executable file information, and starts the executable file, the processor 1001 specifically performs the following operations:

[0207] Downloading the image file corresponding to the image file identifier to the task mechanism;

[0208] Acquire the executable file in the image file based on the storage path;

[0209] Launch the executable file.

[0210] In one embodiment, the processor 1001 further performs the following operations:

[0211] Acquire first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0212] Acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information, and the label;

[0213] The second description information is sent to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the label.

[0214] In one embodiment, when the processor 1001 obtains a label corresponding to the input parameter, stores the label and the input parameter in a database, and obtains the second description information of the target task based on the label, the processor 1001 specifically performs the following operations:

[0215] Generating a label corresponding to the input parameter, and storing the label and the input parameter in a database;

[0216] Replacing the input parameter in the first description information with the label to obtain second description information;

[0217] or,

[0218] Obtaining the uploaded label, establishing a corresponding relationship between the label and the input parameter, and storing the label and the input parameter in a database;

[0219] The label is used to replace the input parameter in the first description information to obtain the second description information.

[0220] In one embodiment, when the processor 1001 executes the acquisition of the label corresponding to the input parameter and stores the label and the input parameter in a database, the processor 1001 specifically performs the following operations:

[0221] Obtaining a label corresponding to the input parameter;

[0222] Determining whether the tag is unique;

[0223] If the tag is unique, storing the tag and the input parameter in the database;

[0224] The method further comprises:

[0225] If the label is not unique, an error prompt message is output, where the error prompt message is used to prompt the update of the label.

[0226] In one embodiment, when the processor 1001 executes the acquisition of the first description information of the target task, the processor 1001 specifically performs the following operations:

[0227] The uploaded description file of the target task is received, and the first description information in the description file is extracted.

[0228] In one embodiment, the processor 1001 further performs the following operations before obtaining first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters:

[0229] Receiving the uploaded image file of the target task, and storing the image file in the database, wherein the image file at least includes the executable file;

[0230] The sending of the second description information to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the tag, includes:

[0231] The task scheduling platform obtains the image file based on the executable file information to download the executable file.

[0232] By adopting the embodiment of this specification, the input parameters in the first description information of the target task submitted by the user are stored and replaced to obtain the second description information, and then the second description information is sent to the task agency, and the executable file is started in the task agency so that the executable file obtains the input parameters. After reducing the size of the description information, the description information is sent down to execute the corresponding task. Through the embodiment of this specification, the first description information is compressed to obtain the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0233] See also Fig.21 , which is a schematic diagram of the structure of a server provided in the embodiment of this specification. Fig.21 As shown, the server 2000 may include: at least one processor 2001 , at least one network interface 2004 , a user interface 2003 , a memory 2005 , and at least one communication bus 2002 .

[0234] The communication bus 2002 is used to realize the connection and communication between these components.

[0235] The user interface 2003 may include a display screen (Display) and a camera (Camera), and the optional user interface 2003 may also include a standard wired interface and a wireless interface.

[0236] The network interface 2004 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0237] Among them, the processor 2001 may include one or more processing cores. The processor 2001 uses various interfaces and lines to connect various parts in the entire server 2000, and executes various functions and processes data of the server 2000 by running or executing instructions, programs, code sets or instruction sets stored in the memory 2005, and calling data stored in the memory 2005. Optionally, the processor 2001 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 2001 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 2001, and it can be implemented separately through a chip.

[0238] Among them, the memory 2005 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 2005 includes a non-transitory computer-readable storage medium. The memory 2005 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 2005 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 2005 may also be optionally at least one storage device located away from the aforementioned processor 2001. As Fig.21 As shown, the memory 2005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and an information delivery application.

[0239] exist Fig.21 In the server 2000 shown, the user interface 2003 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 2001 can be used to call the information stored in the memory 2005 to send the application program, and specifically perform the following operations:

[0240] Acquire first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters;

[0241] Acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information, and the label;

[0242] The second description information is sent to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the label.

[0243] In one embodiment, when the processor 2001 obtains the label corresponding to the input parameter, stores the label and the input parameter in a database, and obtains the second description information of the target task based on the label, the processor 2001 specifically performs the following operations:

[0244] Generating a label corresponding to the input parameter, and storing the label and the input parameter in a database;

[0245] Replacing the input parameter in the first description information with the label to obtain second description information;

[0246] or,

[0247] Obtaining the uploaded label, establishing a corresponding relationship between the label and the input parameter, and storing the label and the input parameter in a database;

[0248] The label is used to replace the input parameter in the first description information to obtain the second description information.

[0249] In one embodiment, when the processor 2001 obtains the label corresponding to the input parameter and stores the label and the input parameter in a database, the processor 2001 specifically performs the following operations:

[0250] Obtaining a label corresponding to the input parameter;

[0251] Determining whether the tag is unique;

[0252] If the tag is unique, storing the tag and the input parameter in the database;

[0253] The method further comprises:

[0254] If the label is not unique, an error prompt message is output, where the error prompt message is used to prompt the update of the label.

[0255] In one embodiment, when executing the process of acquiring the first description information of the target task, the processor 2001 specifically performs the following operations:

[0256] The uploaded description file of the target task is received, and the first description information in the description file is extracted.

[0257] In one embodiment, the processor 2001 further performs the following operations:

[0258] Receiving the uploaded image file of the target task, and storing the image file in the database, wherein the image file at least includes the executable file;

[0259] The sending of the second description information to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the tag, includes:

[0260] The second description information is sent to the task scheduling platform so that the task scheduling platform downloads the image file from the database to the task mechanism based on the executable file information, and starts the executable file in the image file so that the executable file obtains the input parameter from the database based on the label.

[0261] By adopting the embodiment of this specification, the input parameters in the first description information of the target task submitted by the user are stored and replaced to obtain the second description information, and then the second description information is sent to the task agency, and the executable file is started in the task agency so that the executable file obtains the input parameters. After reducing the size of the description information, the description information is sent down to execute the corresponding task. Through the embodiment of this specification, the first description information is compressed to obtain the second description information, which can ensure that the size of the second description information is less than the size limit of the task scheduling platform, and the second description information is sent down, thereby avoiding the limitation of the task scheduling platform and achieving the purpose of sending the description information.

[0262] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0263] The above disclosure is only the preferred embodiment of this specification, which certainly cannot be used to limit the scope of rights of this specification. Therefore, equivalent changes made according to the claims of this specification are still within the scope covered by this specification.

Claims

1. A method for sending information, applied to a task scheduling platform, comprising: Receive second description information of the target task sent by the task conversion module, the second description information is obtained by the task conversion module after compressing the first description information of the target task received, the first description information at least includes the task organization identifier, executable file information and input parameters, the second description information at least includes the task organization identifier, the executable file information and labels corresponding to the input parameters, and the labels and the input parameters are stored in a database; Sending the second description information to the task organization corresponding to the task organization identifier; The executable file is downloaded to the task mechanism based on the executable file information, and the executable file is started so that the executable file obtains the input parameter from the database based on the tag. The executable file includes a mirror file in the executable file information, and the mirror file is stored in the database.

2. The method according to claim 1, wherein the executable file information includes an image file identifier and a storage path of the executable file in the image file corresponding to the image file identifier, and the downloading of the executable file to the task mechanism based on the executable file information and starting the executable file comprises: Downloading the image file corresponding to the image file identifier to the task mechanism; Acquire the executable file in the image file based on the storage path; Launch the executable file.

3. An information delivery method, applied to a task conversion module, comprising: Acquire first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters; Acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information, and the label; The second description information is sent to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the label, the executable file includes the image file in the executable file information, and the image file is stored in the database.

4. The method according to claim 3, wherein obtaining a label corresponding to the input parameter, storing the label and the input parameter in a database, and obtaining the second description information of the target task based on the label comprises: Generating a label corresponding to the input parameter, and storing the label and the input parameter in a database; Replacing the input parameter in the first description information with the label to obtain second description information; or, Obtaining the uploaded label, establishing a corresponding relationship between the label and the input parameter, and storing the label and the input parameter in a database; The label is used to replace the input parameter in the first description information to obtain the second description information.

5. The method according to claim 3 or 4, wherein obtaining a label corresponding to the input parameter and storing the label and the input parameter in a database comprises: Obtaining a label corresponding to the input parameter; Determining whether the tag is unique; If the tag is unique, storing the tag and the input parameter in the database; The method further comprises: If the label is not unique, an error prompt message is output, where the error prompt message is used to prompt the update of the label.

6. According to the method of claim 3, the obtaining of the first description information of the target task comprises: The uploaded description file of the target task is received, and the first description information in the description file is extracted.

7. The method according to claim 3, further comprising: Receiving the uploaded image file of the target task, and storing the image file in the database, wherein the image file at least includes the executable file; The sending of the second description information to the task scheduling platform, so that the task scheduling platform sends the second description information to the task organization corresponding to the task organization identifier, so that the task scheduling platform downloads the executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from the database based on the tag, includes: The second description information is sent to the task scheduling platform so that the task scheduling platform downloads the image file from the database to the task mechanism based on the executable file information, and starts the executable file in the image file so that the executable file obtains the input parameter from the database based on the label.

8. An information sending device, applied to a task scheduling platform, comprising: An information receiving module, used for receiving second description information of a target task sent by a task conversion module, wherein the second description information is obtained by compressing the first description information of the target task received by the task conversion module, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters, and the second description information at least includes the task organization identifier, the executable file information, and labels corresponding to the input parameters, and the labels and the input parameters are stored in a database; An information sending module, used for sending the second description information to the task organization corresponding to the task organization identifier; A parameter acquisition module is used to download an executable file to the task mechanism based on the executable file information, and start the executable file so that the executable file obtains the input parameter from the database based on the tag, the executable file includes a mirror file in the executable file information, and the mirror file is stored in the database.

9. An information sending device, applied to a task conversion module, comprising: A first information acquisition module, used to acquire first description information of the target task, wherein the first description information at least includes a task organization identifier, executable file information, and input parameters; A second information acquisition module is used to acquire a label corresponding to the input parameter, store the label and the input parameter in a database, and obtain second description information of the target task based on the label, wherein the second description information at least includes the task organization identifier, the executable file information and the label; A parameter acquisition module is used to send the second description information to a task scheduling platform, so that the task scheduling platform sends the second description information to a task organization corresponding to the task organization identifier, so that the task scheduling platform downloads an executable file to the task organization based on the executable file information, and starts the executable file, so that the executable file obtains the input parameter from a database based on the label, the executable file is included in the image file in the executable file information, and the image file is stored in the database.

10. A computer storage medium, characterized in that: The computer storage medium has a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps of any one of claims 1 to 2 or 3 to 7.

11. A server, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for the processor to load and execute the method steps as claimed in any one of claims 1 to 2 or 3 to 7.

Images