CN117130684A

CN117130684A - Task processing method, proxy end creation method and device, and electronic equipment

Info

Publication number: CN117130684A
Application number: CN202311089282.2A
Authority: CN
Inventors: 张学舟; 谷俊; 宫婉钰; 陈建军
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-08-25
Filing date: 2023-08-25
Publication date: 2023-11-28

Abstract

The disclosure provides a task processing method, a proxy end creation method and device, and electronic equipment, which can be applied to the fields of computer technology, internet technology, artificial intelligence technology, task processing technology and finance. The service processing method comprises the following steps: responding to the monitoring task processing request, and matching the object identification to be matched in the task processing request according to the object identification corresponding to the proxy end to obtain an object identification matching result; under the condition that the object identification matching result represents that the object identification to be matched is matched with the object identification, determining a plug-in identification and a parameter verification rule according to the task information to be processed; according to the parameter verification rule, verifying the task parameters to be verified to obtain a task parameter verification result; and responding to the task parameter verification result to represent that the task parameter to be verified passes the verification, and processing the task to be processed corresponding to the task processing request by utilizing the plug-in corresponding to the plug-in identification to obtain a task processing result.

Description

Task processing method, proxy end creation method and device, and electronic equipment

Technical Field

The present disclosure relates to the fields of computer technology, internet technology, artificial intelligence technology, task processing technology, and finance, and more particularly, to a task processing method and apparatus, agent end creation method and apparatus, electronic device, computer-readable storage medium, and computer program product.

Background

With the development of computer, distributed and big data technologies, various task processing platforms have been developed, and users can use the task processing platforms to perform task processing.

A task processing platform may refer to a platform that can be used to create, schedule, execute, terminate, etc., a task. In the process of processing tasks by using the task processing platforms, the operation needs to be performed according to the using methods of different task processing platforms. However, because the functions of different task processing platforms are more numerous and the operation flow is more complex, the user needs to learn the use methods of the different task processing platforms before using the task processing platforms, which results in higher use cost of the task processing platforms.

In the process of implementing the disclosed concept, the inventor finds that at least the following problems exist in the related art: the efficiency and accuracy of task processing cannot be well guaranteed by adopting the related technology.

Disclosure of Invention

In view of this, a task processing method, agent creation method and apparatus, electronic device, computer-readable storage medium, and a computer program product.

According to one aspect of the present disclosure, there is provided a task processing method including:

responding to a task processing request, and matching object identifiers to be matched in the task processing request according to object identifiers corresponding to the proxy end to obtain an object identifier matching result, wherein the task processing request further comprises task information to be processed and task parameters to be checked;

determining a plug-in identification and a parameter verification rule according to the task information to be processed under the condition that the object identification to be matched is matched with the object identification by the object identification matching result;

according to the parameter verification rule, verifying the task parameters to be verified to obtain a task parameter verification result; and

and responding to the task parameter verification result to represent that the task parameter to be verified passes verification, and processing the task to be processed corresponding to the task processing request by utilizing the plug-in corresponding to the plug-in identification to obtain a task processing result.

According to an embodiment of the present disclosure, when the object identifier matching result indicates that the object identifier to be matched matches the object identifier, determining, according to the task information to be processed, a plug-in identifier and a parameter verification rule includes:

performing field matching processing on the task information to be processed according to the task type field to obtain task type information;

performing field matching processing on the task information to be processed according to the operation behavior field to obtain an operation behavior identification;

determining the plug-in identification in M candidate plug-in identifications according to the task type information and the operation behavior identification, wherein M is a positive integer; and

and determining the parameter verification rule in P candidate parameter verification rules according to the task type information and the operation behavior identification, wherein P is a positive integer.

According to an embodiment of the present disclosure, the parameter verification rules include a basic parameter verification rule and an auxiliary parameter verification rule;

and verifying the task parameters to be verified according to the parameter verification rule, wherein the task parameter verification result obtaining comprises the following steps:

according to the basic parameter verification rule, performing basic parameter verification on the parameter to be verified to obtain a basic parameter verification result;

Responding to the basic parameter verification result to represent that the task parameter to be verified passes basic parameter verification, and carrying out auxiliary parameter verification on the parameter to be verified according to the auxiliary parameter verification rule to obtain an auxiliary parameter verification result; and

and responding to the auxiliary parameter verification result to represent that the task parameter to be verified passes through auxiliary parameter verification, and obtaining the task parameter verification result representing that the task parameter to be verified passes through verification.

According to an embodiment of the present disclosure, the responding to the task parameter verification result to characterize the task parameter to be verified, through verification, processing the task to be processed corresponding to the task processing request by using a plug-in corresponding to the plug-in identifier, where obtaining a task processing result includes:

acquiring target task data corresponding to the task to be processed according to the task type information and the operation behavior identification; and

and performing format conversion processing on the target task data to obtain the task processing result.

According to an embodiment of the present disclosure, in a case where the task type information is a database task, the task parameter to be verified includes a database identifier and a task data identifier corresponding to the database identifier;

The obtaining target task data corresponding to the task to be processed according to the task type information and the operation behavior identifier includes:

according to the database identifier, a first communication connection between the proxy end and a database corresponding to the database identifier is established; and

and acquiring the target task data according to the task data identifier based on the first communication connection.

According to an embodiment of the present disclosure, in a case where the task type information is a terminal task, the task parameter to be verified includes a terminal identifier and a task data identifier corresponding to the terminal identifier;

establishing a second communication connection between the proxy end and a remote terminal server by using a terminal corresponding to the terminal identifier; and

and acquiring the target task data according to the task data identifier based on the second communication connection.

According to an embodiment of the present disclosure, in a case where the task type information is an interface task, the task parameter to be verified includes an interface identifier and an element identifier corresponding to the interface identifier;

generating a simulation interface corresponding to the interface identifier according to the interface identifier by using a simulation browser, wherein the simulation interface comprises at least one simulation element; and

and responding to the trigger of the simulation element corresponding to the element identifier in the simulation interface, and acquiring the target task data.

According to an embodiment of the present disclosure, the performing format conversion processing on the target task data to obtain the task processing result includes:

determining a target data format according to the task type information and the operation behavior identification; and

and carrying out format conversion processing on the target task data according to the target data format to obtain the task processing result.

According to an embodiment of the present disclosure, the method further includes:

determining the calling times corresponding to the object identification to be matched under the condition that the object identification to be matched is not matched with the object identification by the object identification matching result; and

and sending an authentication request to the proxy end corresponding to the object identification to be matched in response to the calling times meeting a preset condition.

According to another aspect of the present disclosure, there is provided a proxy creation method, applied to a server, including:

in response to receiving a registration request, acquiring reference object information corresponding to an object identifier according to the object identifier in the registration request, wherein the registration request further comprises the object information to be verified and at least one permission platform identifier; and

responding to the matching of the object information to be verified and the reference object information, and creating a proxy end corresponding to the object identifier according to the object identifier and the at least one permission platform identifier;

the proxy end is used for executing the task processing method of any embodiment.

According to another aspect of the present disclosure, there is provided a task processing device, applied to an agent, including:

the matching module is used for responding to the task processing request, matching the object identifier to be matched in the information processing request according to the object identifier corresponding to the proxy end to obtain an object identifier matching result, wherein the task processing request also comprises task information to be processed and task parameters to be checked;

the determining module is used for determining a plug-in identification and a parameter verification rule according to the task information to be processed under the condition that the object identification to be matched is matched with the object identification represented by the object identification matching result;

The verification module is used for verifying the task parameters to be verified according to the parameter verification rule to obtain a task parameter verification result; and

and the processing module is used for responding to the task parameter verification result to represent that the task parameter to be verified passes the verification, and processing the task to be processed corresponding to the task processing request by utilizing the plug-in corresponding to the plug-in identification to obtain a task processing result.

According to another aspect of the present disclosure, there is provided a proxy creation apparatus applied to a server, including:

the acquisition module is used for responding to a received registration request and acquiring reference object information corresponding to the object identification according to the object identification in the registration request, wherein the registration request also comprises the object information to be verified and at least one permission platform identification; and

the creation module is used for responding to the matching of the object information to be verified and the reference object information, and creating a proxy end corresponding to the object identifier according to the object identifier and the at least one permission platform identifier;

the agent end is applied to the task processing device provided by the other aspect of the disclosure.

According to another aspect of the present disclosure, there is provided an electronic device including:

one or more processors;

a memory for storing one or more instructions,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement a method as described in the present disclosure.

According to another aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement a method as described in the present disclosure.

According to another aspect of the present disclosure, there is provided a computer program product comprising computer executable instructions which, when executed, are adapted to carry out the method as described in the present disclosure.

According to the embodiment of the disclosure, as the task parameter verification result is obtained by verifying the task parameter to be verified according to the parameter verification rule, and the parameter verification rule is determined according to the task information to be processed when the object identification matching result indicates that the object identification to be matched is matched with the object identification, the task parameter verification result can be used for indicating whether the task parameter to be verified passes the verification or not, and further the safety and the legality of the parameter in the task processing process of the agent end are ensured. On the basis, the task processing result is obtained by processing the task to be processed corresponding to the task processing request by using the plug-in corresponding to the plug-in identification under the condition that the task parameter to be checked passes the check, so that the technical problem that the efficiency and the accuracy of task processing cannot be well ensured in the related technology can be at least partially overcome, and the operation complexity of a user in the process of using a task processing platform can be reduced by configuring the proxy end capable of executing the task processing method, so that the efficiency and the accuracy of task processing are improved.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings in which:

FIG. 1 schematically illustrates a system architecture to which a task processing method and a proxy creation method may be applied, according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a task processing method according to an embodiment of the disclosure;

FIG. 3 schematically illustrates a flow chart of a business processing method according to another embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of a method of processing database class tasks, according to an embodiment of the disclosure;

FIG. 5 schematically illustrates a flow chart of a method of processing a terminal class target task according to an embodiment of the disclosure;

FIG. 6 schematically illustrates a flow chart of a method of processing proxy end tasks according to an embodiment of the disclosure;

FIG. 7 schematically illustrates a flow chart of a proxy creation method according to an embodiment of the disclosure;

FIG. 8 schematically illustrates a schematic diagram of a task processing method system according to an embodiment of the present disclosure;

FIG. 9 schematically illustrates a block diagram of a task processing device according to an embodiment of the disclosure;

FIG. 10 schematically illustrates a block diagram of a proxy creation apparatus according to an embodiment of the disclosure; and

Fig. 11 schematically illustrates a block diagram of an electronic device adapted to implement a task processing method and a proxy segment creation method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related personal information of the user all conform to the regulations of related laws and regulations, necessary security measures are taken, and the public order harmony is not violated.

In the technical scheme of the disclosure, the authorization or consent of the user is obtained before the personal information of the user is obtained or acquired.

With the rise of technologies such as distributed, cloud native, big data and the like, a plurality of enterprises and related scientific research institutions introduce research and development technology platforms popular in the industry, but the research and development platforms bring technical bonus for the development of company business and simultaneously bring new challenges for first-line research and development personnel. It is counted that a developer needs to log in and operate more than 20 technical platforms on average in daily work, for example: a container console, a soft load console, a cache console, a unified monitoring platform, a continuous integrated assembly line platform, a code auditing platform, an internal technical forum, a work order system, various server terminals and the like. These platforms are of a wide variety, discrete entrances, and cumbersome to use, making routine operations very time and effort consuming for the developer.

In order to at least partially solve the technical problems existing in the related art, the present disclosure provides a task processing method and a proxy end creation method.

It should be noted that, the task processing method and the proxy creating method provided by the embodiments of the present disclosure may be used in the field of artificial intelligence. The task processing method and the proxy creating method provided by the embodiment of the disclosure can also be applied to any field except the artificial intelligence field, for example, the computer field, the internet technology, the task processing technical field and the financial field. The application fields of the task processing method and the proxy end creation method provided by the embodiments of the present disclosure are not limited.

Fig. 1 schematically illustrates a system architecture to which a task processing method and a proxy creation method may be applied according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a proxy end 104, and a server 105. The proxy 104 is a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103 and the server 105. Proxy 104 may be created by server 105.

The user may interact with the server 105 through the proxy 104 using at least one of the first terminal device 101, the second terminal device 102, and the third terminal device 103, to achieve task processing. Various communication client applications, such as a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only) may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103.

The first terminal device 101, the second terminal device 102, the third terminal device 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that, the proxy creation method provided in the embodiments of the present disclosure may be generally executed by the server 105. Accordingly, the proxy creation apparatus provided by the embodiments of the present disclosure may be generally provided in the server 105. The proxy creation method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105. Accordingly, the proxy creation apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105.

Alternatively, the task processing method provided by the embodiment of the present disclosure may also be performed by the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may also be performed by other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103. Accordingly, the task processing device provided by the embodiment of the present disclosure may also be provided in the first terminal device 101, the second terminal device 102, or the third terminal device 103, or in other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103.

It should be understood that the number of terminal devices, proxy ends and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, proxy ends and servers, as desired for implementation.

It should be noted that the sequence numbers of the respective operations in the following methods are merely representative of the operations for the purpose of description, and should not be construed as representing the order of execution of the respective operations. The method need not be performed in the exact order shown unless explicitly stated.

Fig. 2 schematically illustrates a flow chart of a task processing method according to an embodiment of the present disclosure.

As shown in fig. 2, the task processing method flow 200 includes operations S210 to S240.

In operation S210, in response to the monitoring of the task processing request, matching the object identifier to be matched in the task processing request according to the object identifier corresponding to the proxy end, to obtain an object identifier matching result, where the task processing request further includes the task information to be processed and the task parameter to be checked.

In operation S220, in the case that the object identifier matching result indicates that the object identifier to be matched matches the object identifier, the plug-in identifier and the parameter verification rule are determined according to the task information to be processed.

In operation S230, the task parameters to be checked are checked according to the parameter check rule, and a task parameter check result is obtained.

In operation S240, the task to be checked is characterized by the task parameter to be checked through checking in response to the task parameter checking result, and the plug-in corresponding to the plug-in identifier is utilized to process the task to be processed corresponding to the task processing request, so as to obtain a task processing result.

The task processing method 200 can be applied to the proxy end. The agent determines the task to be processed according to the task information to be processed, for example, the task information to be processed may include at least one of the following: invoking a program execution log, querying the specific content of an item, deleting the data of a database, etc.

According to the embodiment of the disclosure, the agent end can monitor a task processing request through an application program interface provided by the instant messaging tool, and after a user sends information containing the task processing request through the instant messaging tool, the agent end responds to the task processing request generated by the instant messaging tool to match an object identifier to be matched included in the task processing request with an object identifier stored in the agent end, so that a corresponding matching result is obtained, and subsequent operation is facilitated.

According to the embodiment of the disclosure, the terminal device may store a script for generating a task processing request in advance, and in response to detecting that a user initiates a task processing operation, may acquire an object identifier to be matched and task information to be processed, which correspond to the task processing operation, and determine task parameters to be checked according to the task information to be processed. On the basis, the terminal equipment can run the script, and generates a task processing request message corresponding to the task processing operation according to the object identification to be matched, the task information to be processed and the task parameter to be checked. The agent end can monitor the task processing request sent by the terminal equipment in real time. The task processing request message may include information that the user requests task processing, for example, the task processing request message may include at least one of: object identification to be matched, task information to be processed and task parameters to be checked.

The terminal device may send the task processing request through the agent end of the instant communication platform, and specifically, the form of task processing operation may include at least one of the following: natural language and fixed modes, for example, a user may initiate a task processing operation in a natural language form, in which case the task processing request message may include "a assistant please help me restart all containers in a certain test environment," it should be understood that "a assistant" in this example is a proxy name to which the user may apply, and "a certain test environment" may be specific to a test environment of a specific project.

The object identification is used for uniquely distinguishing users monitoring the task processing request, and the object identification to be matched is the identification which is contained in the task processing request and uniquely distinguishes different users. The object identification to be matched and the object identification can be used for distinguishing the source of the object identification, and the object identification to be matched is the object identification in the task processing request.

The task parameters to be checked are specific task parameters included in the task information to be processed, and specific forms of the task information to be processed can be set according to actual service requirements, which are not limited herein. For example, the task information to be processed may include a table or text for ensuring the correctness of the task processing. For example, if the task information to be processed is a running log of the downloading program, the task parameters to be checked may include an interface to be called in the downloading process.

According to an embodiment of the present disclosure, a plug-in identifies an execution body for uniquely identifying task processing, where the execution body may be a plug-in or a component that is required to be used in the task execution process. The form of the plug-in identification may include at least one of: character string identification, number identification and combination marking. For example, in querying data in a database, the plug-in identifier may be a plug-in identifier of the database, and in a relational database management system (i.e. MySQL), the plug-in identifier may be a string, typically including the name of the plug-in.

The parameter check rules, i.e. the check functions within the plug-ins, may differ from one plug-in to another, i.e. the parameter check rules are related to the plug-ins used. For example, the parameter verification rule may include at least one of: checkInputs (), checklimits (), checkResources (), checkcompatibilities (), and the like.

The method comprises the steps of pre-configuring at least one candidate task information and processing methods corresponding to the at least one candidate task information and used for processing the candidate task information, storing the at least one candidate task information and the processing methods corresponding to the at least one candidate task information in a proxy in a correlated mode, and after the proxy monitors a task processing request, respectively matching the at least one candidate task information according to the task information to be processed so as to determine the candidate task information matched with the task information to be processed, and calling the processing methods corresponding to the candidate task information for subsequent operation.

According to an embodiment of the present disclosure, a matching method used in a process of matching an object identifier to be matched with an object identifier may include: regular expressions, string matching, pattern recognition, machine learning, etc. The task information to be processed may include an operation object in a task processing process and specific content of a processing task, for example, the task information to be processed is "call an access log of a website in a certain period of time", in this case, the operation object in the task information to be processed is a certain website, and the specific content of the processing task is "call an access log". Under the condition that the object identification to be matched is matched with the object identification, the proxy end can determine plug-in identification which can be used in the process of calling the website access log according to the preset flow of calling the website access log in the program through the related content of a website and the call access log contained in the task information to be processed.

According to an embodiment of the present disclosure, the task parameter verification result includes a verification pass and a verification fail. The task parameter checking result is used for checking whether the instruction parameters provided in the task processing meet the requirements of legitimacy and safety. For example, checking whether the name format of the database to be accessed in the task information to be processed is correct or not, it should be clear that the task parameters to be checked include more than the content in the above example, and the task parameters to be checked are determined with the task processing request to be responded.

Specifically, for example, in the case that the agent performs a task processing request for querying a certain piece of data in the database, the process required for verification may include: firstly, determining a parameter verification rule for checking compatibility of a database access plug-in unit of an agent terminal and a database interface; then, determining whether the names of the databases to be accessed are matched with the names of all databases which can be accessed by the proxy end currently, namely, checking whether the names of the databases are correct.

According to the embodiment of the disclosure, if the task parameter verification result indicates that the task parameter to be verified passes the verification, the corresponding plug-in can be identified according to the plug-in identifier, the task processing request is processed by using the identified plug-in, and finally the task processing result for executing the task processing request is obtained. The task processing result may be data obtained by executing the task processing request at the proxy end. The number of the plug-ins needed in the task processing request execution process can be multiple. For example, in retrieving a certain item of data in a database, the database plug-in used includes a database connection plug-in, a query parsing and forwarding plug-in, a data cache plug-in, and the like.

According to an embodiment of the present disclosure, when an object identifier matching result indicates that an object identifier to be matched matches an object identifier, determining, according to task information to be processed, a plug-in identifier and a parameter verification rule includes: according to the task type field, performing field matching processing on the task information to be processed to obtain task type information; according to the operation behavior field, performing field matching processing on the task information to be processed to obtain an operation behavior identification; determining plug-in identification in M candidate plug-in identifications according to task type information and operation behavior identification, wherein M is a positive integer; and determining a parameter verification rule in the P candidate parameter verification rules according to the task type information and the operation behavior identification, wherein P is a positive integer.

According to embodiments of the present disclosure, the task type field may be used to characterize the type of task to be processed, wherein the task type may include at least one of: interface class, terminal class and database class. The task processing request of the interface class is used for realizing the behavior of simulating the user to log in the technical platform interface to complete a series of customization operations, such as: start-stop container/download container log, soft load running inspection, search specifications, etc. The task processing request of the terminal class is used for executing shell scripts, such as: acquiring the resource use condition of the server, downloading logs and the like. The task processing requests of the database class are used to execute structured query language (Structured Query Language, SQL) statements in the database, such as: acquiring a character set of a certain library, querying data of a certain table, and the like. The operational behavior field may be used to characterize a particular operational behavior of a processing task. For example, the operational behavior field may include soft-load running inspection, boot container, download log, and the like.

The method comprises the steps that the type of a task to be processed is determined by matching a task processing type contained in task information to be processed with a task type field, and task type information is further determined and used for representing a specific task type; the agent end matches specific operation and operation behavior fields contained in the task information to be processed to obtain operation behavior identification which can be used for identifying specific operation behaviors.

Analyzing the task information to be processed, matching task type information obtained from task type fields in the task information to be processed, matching operation behavior fields in the task information to be processed to obtain operation behavior identifiers, determining plug-in unit identifiers related in the task processing process, and determining parameter verification rules in the task processing process according to the task type information and the operation behavior identifiers. Optionally, the parameter verification rule in the task processing can also be determined through the plug-in identification.

According to the embodiment of the disclosure, the task information to be processed is analyzed, and the analyzed task information is matched with the task type field and the operation behavior field to obtain the task type to be executed and the operation behavior identification, so that the plug-in unit used in the task execution process and the parameter verification rule corresponding to the plug-in unit can be determined, further, the fact that the agent end is matched with the plug-in unit suitable for the task processing request can be ensured, and the accuracy of subsequent task processing is improved.

According to an embodiment of the present disclosure, the parameter verification rules include a base parameter verification rule and an auxiliary parameter verification rule; according to the parameter verification rule, verifying the task parameters to be verified, and obtaining the task parameter verification result comprises the following steps: according to the basic parameter verification rule, performing basic parameter verification on the parameter to be verified to obtain a basic parameter verification result; responding to the basic parameter verification result to represent that the task parameters to be verified pass through basic parameter verification, and carrying out auxiliary parameter verification on the parameters to be verified according to auxiliary parameter verification rules to obtain auxiliary parameter verification results; and responding to the auxiliary parameter verification result to represent that the task parameter to be verified passes through auxiliary parameter verification, and obtaining a task parameter verification result representing that the task parameter to be verified passes through verification.

According to embodiments of the present disclosure, the basic parameter verification rule is used to verify the validity of the parameter type, for example, to verify whether the number of parameters is correct or not, whether the values of the parameters are in compliance with a predetermined range, and the like. The auxiliary parameter checking rule is used for checking the rationality of the parameter, for example, whether the parameter includes an instruction which causes destructive damage to the system on the server, specifically, if the task processing request includes information for completely clearing the data in the database, the parameter in the task processing request does not meet the rationality requirement according to the auxiliary parameter checking rule.

If the basic parameter verification rule result indicates that the verification result does not pass, directly returning a client result to inform that the parameter in the task processing request submitted by the client has an error, and suggesting to re-submit the task processing request; if the parameter to be checked passes the basic parameter checking rule, checking the parameter to be checked according to the auxiliary parameter checking rule, and if the auxiliary parameter checking result indicates that the checking is passed, the parameter to be checked passes the task parameter checking.

According to the embodiment of the disclosure, by setting the basic parameter verification rule and the auxiliary parameter verification rule to verify the parameters in the task processing request in more detail, the correctness of the parameters in the task processing request can be ensured under the condition of avoiding damage to hardware equipment or a software platform at a server side.

According to an embodiment of the present disclosure, responding to a task parameter verification result to characterize a task parameter to be verified, by verifying, processing a task to be processed corresponding to a task processing request by using a plug-in corresponding to a plug-in identifier, where obtaining a task processing result includes: acquiring target task data corresponding to a task to be processed according to the task type information and the operation behavior identification; and performing format conversion processing on the target task data to obtain a task processing result.

According to the embodiment of the disclosure, the proxy end obtains a plug-in unit required by task processing by analyzing task information to be processed in a task processing request, and executes a task to be processed by calling the plug-in unit to obtain target task data corresponding to the task to be processed, wherein the format of the target task data may include at least one of the following: text, images, audio, video, documents, etc.

After the agent end obtains the target task data in the task processing process, the target task data can be converted by the following modes: firstly, determining the file type of target task data; then, selecting a target file format according to the requirements of a user and the file format supported by a platform for receiving the task processing result by the client; on the basis, a format conversion mode can be determined according to the format of the target file and the file type of the target task data, and the target task data is converted based on the format conversion mode. The format conversion means may include at least one of: the target task data is converted into data different from the current format, and the target task data is converted into data different from the current data in size. For example, if the platform receiving the task processing result cannot receive the data in the picture format, the data of the picture type is converted into the data of the text type. Alternatively, if the platform receiving the task processing result cannot receive the file with the size larger than 5MB, the various sizes of the file may be modified into the file with the smaller format.

If the task to be processed is to query a certain data or search a certain page, but the proxy end does not query the corresponding data or page, the information containing the data or page which cannot be searched can be transmitted back to the client end in the form of text, so that the user is informed that the user does not query the certain data or search the certain page.

According to the embodiment of the disclosure, the target task data is obtained according to the task type information and the operation behavior identifier, and the target task data is converted according to the requirement, so that a final task processing result is obtained, the data obtained by the proxy end can be adapted to the application of the client end, the situation that the task data obtained by the proxy end cannot be transmitted to a user can be avoided, and the effectiveness of task processing is improved.

Fig. 3 schematically illustrates a flow chart of a business processing method according to another embodiment of the present disclosure.

As shown in fig. 3, in a flowchart 300 of a service processing method according to another embodiment of the present disclosure, an agent may match an object identifier 301 to be matched in a task processing request according to an object identifier 302 corresponding to the agent, so as to obtain an object identifier matching result 303. After the object identification matching result 303 is obtained, operation S310 may be performed.

In operation S310, it may be determined whether the object identification matching result is characterized by?

If so, field matching processing may be performed on the task information to be processed 305 according to the task type field 304, to obtain task type information 307. According to the operation behavior field 306, field matching processing is performed on the task information to be processed 305, and an operation behavior identifier 308 is obtained. The plug-in identification 309 may be determined from the task type information 307 and the operational behavior identification 308 among M candidate plug-in identifications, and the parameter check rule 310 among P candidate parameter check rules. On this basis, the plug-in 312 can be determined through the plug-in identifier 309, the parameter verification result 311 is determined according to the parameter verification rule 310, and in the case that the parameter verification result 311 indicates that verification is passed, the task can be processed through the plug-in 312, so as to obtain a task processing result 313. If not, the flow may end.

According to the embodiment of the disclosure, in the case that the task type information is a database task, the task parameter to be checked includes a database identifier and a task data identifier corresponding to the database identifier; according to the task type information and the operation behavior identification, acquiring target task data corresponding to the task to be processed comprises the following steps: according to the database identification, establishing a first communication connection between the proxy end and a database corresponding to the database identification; and acquiring target task data according to the task data identification based on the first communication connection.

According to an embodiment of the present disclosure, the task type information is a database task, i.e. the task type field characterizes the task type as a database class. The database identification includes a name, server address, port number, user name, etc. for distinguishing the database. The task data identification corresponding to the database may include SQL statements for performing database operations.

For example, the connection between the database and the proxy end can be established through an application program interface of the database, or the connection between the database and the proxy end can be established through the transmission of link characters, and after the connection is successfully established, the target task data can be obtained through calling functions in the database and/or executing SQL sentences.

Fig. 4 schematically illustrates a flowchart of a method of processing database class tasks according to an embodiment of the disclosure.

As shown in fig. 4, in this embodiment, the process of processing the database class task is illustrated by taking the information of the task to be processed of the database class as "acquiring the character set of the a-library under the a instance in Oracle". The process flow 400 of the database class task may include operations S401 to S404.

In operation S401, the proxy establishes a connection with an instance of the Oracle Database a through a function library of the Oracle Database (Oracle Database, oracle db).

For database operation class tasks, some instance of the remote Oracle database may be accessed through the function library of the Oracle db in node. The proxy end is used for calling a function library of the Oracle DB, inputting the connection character string, the user name and the password information of the database, and calling a getConnection method to establish a connection instance corresponding to the Oracle database.

In operation S402, the proxy executes the SQL statement through the connection to acquire character set information of the a library. For example, the SQL statement may be a select parameter, value FROM nls_database_parameters.

The proxy terminal calls its execution method to execute specified SQL statement (value FROM nls_database_parameters) through the database connection instance to obtain character set information of a certain library.

In operation S403, the proxy disconnects the a instance in the corresponding Oracle database.

After the inquiry is completed, the proxy operates the Oracle database connection instance, and calls a close method thereof to disconnect the database connection.

In operation S404, the agent returns the searched character set result and returns the searched character set result to the message processing module.

According to the embodiment of the disclosure, under the condition that the task type information is a terminal task, the task parameters to be checked comprise a terminal identifier and a task data identifier corresponding to the terminal identifier; according to the task type information and the operation behavior identification, acquiring target task data corresponding to the task to be processed comprises the following steps: establishing a second communication connection between the proxy end and the remote terminal server by using the terminal corresponding to the terminal identifier; and acquiring target task data according to the task data identification based on the second communication connection.

According to an embodiment of the present disclosure, the task type information is a terminal task, i.e. the task type field characterizes the task type as a terminal class. The terminal identification includes a name, an application program interface, a port number, a uniform resource locator, etc. for distinguishing the terminal. The terminals corresponding to the terminal identifiers may include local terminals, remote terminals, terminal simulators, web terminals, and the like.

Fig. 5 schematically illustrates a flowchart of a method of processing a terminal class target task according to an embodiment of the present disclosure.

As shown in fig. 5, in the embodiment of the present disclosure, a process of processing a terminal class task is illustrated with the information of the task to be processed of the terminal class as "download program running log". The flow 500 of processing the terminal-like task includes operations S501 to S505.

In operation S501, the proxy starts an sftp client for accessing a remote terminal server through a ssh2-sftp-client function library.

For the terminal operation class task, the remote terminal server can be accessed through ssh2-sftp-client function library in node. Js. The proxy end calls the ssh2-sftp-client function library to newly establish an sftp client instance.

In operation S502, the proxy establishes an sftp connection with the remote terminal server through the sftp client.

In order to acquire the log on the remote terminal server, the proxy end needs to operate an sftp client instance, input the IP address, port number (sftp default 22 port), user name and password information of the server, and call the connect method to establish sftp connection with the server.

In operation S503, the proxy downloads all program running log files in the specified directory under the remote terminal server to the local through the sftp client.

The proxy operates the sftp client instance and invokes its downloadDir method to download all log files in the specified directory in the remote terminal server to the local directory.

In operation S504, the proxy disconnects the sftp connection with the remote terminal server through the sftp client.

And after the downloading is completed, the proxy operates the sftp client instance, and calls an end method to disconnect the sftp connection.

In operation S505, the agent compresses the downloaded program running log file and returns the compressed file.

The agent terminal compresses and packages a series of log files obtained by local downloading, and returns the log files to the client terminal as a compressed file.

According to the embodiment of the disclosure, in the case that the task type information is an interface task, the task parameters to be checked include an interface identifier and an element identifier corresponding to the interface identifier; according to the task type information and the operation behavior identification, acquiring target task data corresponding to the task to be processed comprises the following steps: generating a simulation interface corresponding to the interface identifier according to the interface identifier by using a simulation browser, wherein the simulation interface comprises at least one simulation element; and responding to the trigger of the simulation element corresponding to the element identifier in the simulation interface, and acquiring target task data.

For example, the processing of the interface class target task may include: firstly, the proxy end decrypts the unified authentication account number and the password of the user, and completes identity authentication through the unified authentication platform. Specifically, in order to log in each technical platform in the company, the identity authentication can be finished through a unified authentication platform in the company. The proxy end obtains the unified authentication account number and the password of the user stored in an encrypted form during the previous activation from the local, decrypts the password, accesses the Web application program interface of the unified authentication platform to perform identity authentication, and obtains a Token after the authentication passes.

Then, the proxy starts a Headless Chromium browser for simulating access to the science and technology management platform page through the Puppeterer function library. Specifically, for the interface operation task, the Headless Chromium browser can be operated through the Puppeterer function library in the node. Js, so that the behavior of simulating the user to log in the technical platform interface to complete a series of customization operations is realized. In order to simulate the user to access the science and technology management platform page later, the proxy end calls the Puppeterer function library and starts a Headless Chromium browser instance.

The proxy terminal operates the browser and simulates and accesses a search page of the science and technology management platform. Specifically, the proxy operates the newly started Chromium browser instance through the Puppeterer function library, newly builds an access page instance, and the corresponding jump website is the hypertext transfer protocol (Hypertext Transfer Protocol, HTTP) address of the search page in the science and technology management platform so as to simulate the user to access the target page.

The proxy end waits for the completion of the search page loading. Specifically, in order to acquire corresponding webpage elements in the target page to complete subsequent operations, the proxy end needs to wait for the whole search page to be loaded, which is achieved by operating the Chromium browser instance through the Puppeterer function library and simulating the occurrence of a specific Selector (i.e. a Selector) element in the blocking waiting webpage of the user.

The proxy end simulates clicking a 'technical specification' tab in the search page, and switches to the tab. Specifically, in order to switch to a target tab to be accessed, the proxy end needs to operate the Chromium browser instance through the Puppeterer function library, locate to a selector corresponding to the "technical specification" tab in the search page, and simulate the user to click on the "technical specification" tab in the search page.

The proxy end locates to the search box in the search page and simulates input search content. Specifically, the proxy end needs to operate the Chromium browser instance through the Puppeterer function library, locate to the selector corresponding to the search box under the "technical specification" page sign, and simulate the user to input a string of keywords to be searched.

The proxy end simulates clicking a search button in a search page to trigger search behavior. Specifically, to trigger the actual searching behavior, the proxy end needs to operate the Chromium browser instance through the puppeter function library, locate the selector corresponding to the "search" button on the right side of the "technical specification" tab, and simulate the user to click the "search" button.

The proxy end waits for the completion of the loading of the search result page. Specifically, in order to obtain the complete search result, the proxy end needs to wait for the whole search result page to be loaded, which is realized by operating the Chromium browser instance through the Puppeterer function library and simulating the user to block and wait for the specific selector element in the webpage to appear.

The proxy end locates to the result list in the search result page and acquires the whole list content. Specifically, in order to obtain the search result, the proxy end needs to operate the Chromium browser instance through the puppeterer function library, locate a selector corresponding to the result list, and access the selector to obtain the complete embedded text therein.

On the basis, the proxy traverses the result list, extracts a piece of result content for formatting, and returns the result content after the completion of assembly. Specifically, the acquired embedded text representing the search result list is analyzed, one piece of search result content in the list is extracted, formatting is carried out, and a complete execution result is assembled and returned to the message processing module.

According to an embodiment of the present disclosure, performing format conversion processing on target task data, where obtaining a task processing result includes: determining a target data format according to the task type information and the operation behavior identification; and performing format conversion processing on the target task data according to the target data format to obtain a task processing result.

According to the embodiment of the disclosure, the agent determines a target data format included in a task processing result through task type information and operation behavior identification of a required processing task, and converts the obtained data according to the target data format to obtain a final task processing result. For example, the task type information of the task to be processed is a database type task, and the operation behavior identification represents that under the condition of executing the query type operation, the proxy executes the content of the query database, after obtaining the query result, converts the data in the database into a format which can be used for more effectively representing the task processing result, such as a text format, and returns the data in the text format as the task processing result to the client.

Different target data formats may be suitable for use in different scenarios. For example, if the task information to be processed is a container restart, the task processing results may include whether the restart was successful, preferably, a plain text format representation may be used; if the task information to be processed is a search specified question, the task processing result may include an answer to the search question, preferably, may be represented using a rich text format; if the task information to be processed is a resource occupation query, the task processing result can include detailed data and diagrams (dashboards, bar charts and the like) of each dimension for representing the resource occupation, and preferably, a picture format is selected for representation; if the task information to be processed is a log download class instruction, the task processing result may include a plurality of log files, preferably, represented by using an attachment format.

According to the embodiment of the disclosure, the data format which is most important to return to the client is obtained through the task type information and the operation behavior identification, and the data format is converted into the data format corresponding to the task scene, so that the task processing result can be presented to the user in a more visual mode, and the use experience of the user is improved.

According to an embodiment of the present disclosure, the task processing method further includes: under the condition that the object identification matching result represents that the object identification to be matched is not matched with the object identification, determining the calling times corresponding to the object identification to be matched; and sending an authentication request to the proxy end corresponding to the object identification to be matched in response to the fact that the calling times meet the preset conditions.

According to an embodiment of the present disclosure, the preset condition may include a preset number of calls, for example, the preset condition may include determining whether the historical number of calls of the object identifier to be matched satisfies a preset value.

Specifically, the object identifier of the first user is used as a first object identifier, and the object identifier to be matched of the first user is used as a first object identifier to be matched; the object identifier of the second user is a second user identifier, and the object identifier to be matched of the second user is a second object identifier to be matched, which is taken as an example, and a process of judging whether the preset condition is met is described.

For example, the first user invokes the proxy end of the second user, and the proxy end can determine the number of times of invoking the proxy end of the second user by searching the history invoking log under the condition that the first object identifier to be matched and the second user identifier match result representation are not passed. If the first user calls the proxy end of the second user for the first time, the called proxy end of the second user sends call request information to the second user to remind the second user to grant the use right of the proxy end of the second user to the first user.

According to the embodiment of the disclosure, when the preset condition is met, the authentication request is sent to the proxy end corresponding to the object identifier, so that the user can call the proxy end of other users under the condition of obtaining the permission of other users, and the flexibility of calling among the proxy ends is improved.

Fig. 6 schematically illustrates a flow chart of a method of handling proxy-side tasks according to an embodiment of the disclosure.

As shown in fig. 6, the proxy task processing method 600 includes operations S601 to S607.

In operation S601, a user logs in to an active agent at a server.

The user inputs the registered account number and password through the management interface of the login server, and activates the proxy end of the user. After each activation, the proxy end can reside on a server deployed by the platform in the activation validity period in the form of a thread, and waits for receiving a task processing request and executing the task processing request.

In operation S602, the proxy end monitors, in real time, the group chat where the corresponding user is located.

The agent monitors the information in all group chat of the corresponding user through the application program interface opened by the instant communication tool in the company.

In operation S603, the proxy monitors that a task processing request calling the proxy exists in a group chat.

The proxy only focuses on the task processing request message of the calling robot in the group chat, and intercepts the message with the assistant word of "@ xxx for analysis.

In operation S604, it is determined whether the object identifier to be matched matches the object identifier.

For example, if "xxx" in the "@ xxx assistant" typeface refers to the user name of the user of the agent, it will continue to execute the task processing request. Otherwise, continuing to monitor group chat information.

In the case that the matching is represented and passed in operation S604, in operation S605, the agent end parses the task processing request, matches the corresponding plugin, and verifies the validity and security of the task processing request parameter list.

After confirming that the object identification to be matched is matched with the object identification, the agent end analyzes the task processing request in the modes of regular expression, keyword extraction, natural language processing and the like, and matches with a plug-in suitable for processing the task processing request. In addition, the validity and the safety of the task parameters to be checked of the task processing request provided by the call are checked through the checking function defined in the plug-in.

In the case where the characterization of operation S604 does not pass, operation S603 is returned.

In operation S606, it is determined whether the task parameters to be checked pass the parameter check rule.

If the task processing request provided by the call meets the requirements of the basic parameter verification rule and the auxiliary parameter verification rule after the task parameters to be verified are verified, the task processing request is continuously executed. Otherwise, continuing to monitor group chat information.

If the matching is not passed in operation S606, the process returns to operation S603.

If the parameter verification rule is passed, operation S607 is executed, and in operation S607, the proxy end invokes the corresponding plug-in to execute the task processing request.

After the task processing request is checked, the proxy end can call the corresponding simulation plug-in to complete the tasks of interface operation class, terminal operation class and database operation class, and the execution result is returned to the client end.

Fig. 7 schematically illustrates a flowchart of a proxy creation method according to an embodiment of the present disclosure.

As shown in fig. 7, the task agent creation method 700 includes operations S710 to S720.

In response to receiving the registration request, reference object information corresponding to the object identifier is obtained according to the object identifier in the registration request, where the registration request further includes the object information to be verified and at least one license platform identifier.

In operation S720, in response to the matching of the object information to be verified and the reference object information, creating a proxy corresponding to the object identifier according to the object identifier and the at least one license platform identifier; the proxy end is used for executing the task processing method of any embodiment.

According to an embodiment of the present disclosure, the task proxy creation method 700 is applied to a server. The reference object information may include a user password set in the registration process. The object information to be verified can comprise a user password input by a user, and the object information to be verified can also comprise a verification code updated in real time. License platforms identification is used to uniquely distinguish between different platforms, and a licensed platform may include a website, software, and specifically, for example, a licensed platform may include a scientific platform.

For example, a user sends a registration request through a client, the registration request comprises a user name and a password of the user and at least one platform for executing tasks through a proxy, the server responds to the registration request, and creates a corresponding proxy according to the user name, the password and platform information contained in the registration request, wherein the scope of the created proxy for assisting the user in processing the tasks is limited by the platform, the tasks processed by the proxy can comprise all operations which can be related on the platform, and the operations of other platforms can be called through the platform. While for platforms where license platform identification is not included in the registration request at the beginning of creation of the proxy, the proxy may be invoked indirectly by means of the current platform. For example, if a certain operation link of other platforms is included on a certain scientific and technical platform, the agent end can execute the operation of the present application belonging to the other platforms by means of the link on the platform.

According to the embodiment of the disclosure, the user can create the proxy end belonging to the user by sending the request to the server end, so that each user can create and use the proxy end in time, and the capability of performing task processing by using the proxy end subsequently can be improved.

Fig. 8 schematically illustrates a schematic diagram of a task processing system according to an embodiment of the present disclosure.

As shown in fig. 8, the task processing system 800 may include: channel access module 810, message processing module 820, instruction processing module 830, operation base module 840, log processing module 850, timing scheduling module 860.

The channel access module 810 enables research and development personnel to interact with the agent end through group chat of the instant messaging tool as a channel. The channel access module 810 can monitor the message in the appointed group chat through the interface opened by the instant messaging tool, and call the message processing module 820 and the instruction processing module 830 in sequence to process, and finally output the result of executing the task information to be processed to the group chat.

Message processing module 820 is primarily responsible for the functions of message preprocessing and reply message processing.

The message pretreatment is to analyze the monitored messages in group chat, namely to identify the messages by means of regular expressions, keyword extraction, natural language processing and the like. The former two ways have strict requirements on the form of input information of research personnel, and need to meet the mode of 'the assistant pending task information name of xxx and the parameter list of the pending task information', otherwise, the matching failure of the pending task information may occur. The natural language processing mode can be used for intention recognition, so that a researcher is allowed to input a message such as '@xxx assistant help me restart all containers of the B module in the function test environment A', and the method is more in line with daily language expression habits of people.

And the reply message processing is to package the execution result of the task information to be processed into a proper format and return the execution result to the group chat, wherein the execution result comprises four formats of plain text, rich text, pictures and attachments. The applicable scenarios for various formats are different, such as: for the task information to be processed of the container restarting, whether the restarting is successful or not is returned, and the task information is preferably represented by a plain text format; for searching task information to be processed of a specified problem, returning an answer of the search problem, and preferably representing the answer in a rich text format; for inquiring task information to be processed by the resource occupation, returning detailed data and diagrams (dashboards, bar charts and the like) of each dimension of the resource occupation, which are preferably represented by a picture format; for the task information to be processed of the log downloading class, the returned result is a plurality of log files, and the log files are preferably represented in an accessory format.

The instruction processing module 830 is mainly responsible for executing the task information to be processed identified by the message processing module 820, completing the tasks of interface operation class, terminal operation class and database operation class by calling the simulation tool, and returning the execution result to the message processing module 820.

In the task information mechanism to be processed, the task information to be processed matching is to match the information of the task information to be processed identified by the information processing module 820 with a plug-in unit responsible for execution, and to check the validity and safety of the parameter list of the task information to be processed; the task information to be processed is the task information to be processed which is matched by calling the plug-in to be executed; the help content is a prompt of a to-be-processed task information calling mode, and a researcher can send a message of an assistant help to-be-processed task information name like "@ xxx to acquire the help prompt of the to-be-processed task information calling mode; when the identity authentication is to execute an interface operation task, a corresponding simulation tool can simulate a corresponding technical platform by using a unified authentication account number and a password of a research and development personnel (namely a host at the proxy end) in a company in advance to complete the identity authentication, and then a series of customized operations can be executed; the hot updating of the plug-in is to support the dynamic replacement or the new addition of the plug-in for executing the task information to be processed in the operation period of the proxy end, so that the effect that the use of a user is not interrupted in the function upgrading process is realized; the transfer authorization means that when a developer calls the proxy end of other colleagues for the first time, the dispatched proxy end reminds the owner of the developer to execute the transfer authorization so as to allow the colleagues initiating the call to execute the current and subsequent task information to be processed.

In the simulation processing, the corresponding function library in node. Js is mainly called, and the user operation behavior is simulated in a simulation mode to finish the tasks of interface operation class, terminal operation class and database operation class.

The base module 840 is operated, and is mainly responsible for managing daily operations of agent ends corresponding to the research personnel and dispatching new tasks to be processed.

Before using the agent, the developer needs to log in the management interface of the agent platform in advance, input the unified authentication account number and the password of the agent platform in the company, and select a plurality of technical platforms which allow the agent to access, so that the operation of the agent can be formally activated. After each activation, its proxy will reside on the deployed server for a period of time called the active lifetime. During this period, the developer can directly use his agent without logging in again until the expiration date expires. In addition, the research and development personnel can log in the management interface of the proxy end platform to select to exit operation and actively end the service of the proxy end in advance.

When the newly generated piece of task information to be processed is matched, the operation base module 840 may assign the task information to be processed to the agent end of the corresponding developer for execution.

The log processing module 850 is mainly responsible for recording system-level logs, logs of task information to be processed and user access logs, and can count the execution condition of the task information to be processed based on the user access logs, so that the subsequent operation and optimization are facilitated.

The timing scheduling module 860 is mainly used for timing task scenes, and a developer can execute task information to be processed periodically by setting time, for example: periodically inspecting the environment, reminding research and development tasks regularly, and the like.

Fig. 9 schematically illustrates a block diagram of a task processing device according to an embodiment of the disclosure.

As shown in fig. 9, the task processing device 900 may include: a matching module 910, a determining module 920, a checking module 930, and a processing module 940.

The matching module 910 is configured to, in response to monitoring a task processing request, match an object identifier to be matched in the information processing request according to an object identifier corresponding to the proxy end, so as to obtain an object identifier matching result, where the task processing request further includes task information to be processed and task parameters to be checked.

The determining module 920 is configured to determine, according to the task information to be processed, a plug-in identifier and a parameter verification rule when the object identifier matching result indicates that the object identifier to be matched matches the object identifier.

And the verification module 930 is configured to verify the task parameters to be verified according to the parameter verification rule, so as to obtain a task parameter verification result.

And the processing module 940 is used for responding to the task parameter verification result to represent that the task parameter to be verified passes the verification, and processing the task to be processed corresponding to the task processing request by utilizing the plug-in corresponding to the plug-in identification to obtain a task processing result.

According to an embodiment of the present disclosure, the determining module 920 includes: the first, second, third and fourth determining sub-modules.

And the first determination submodule is used for carrying out field matching processing on the task information to be processed according to the task type field to obtain the task type information.

And the second determining submodule is used for carrying out field matching processing on the task information to be processed according to the operation behavior field to obtain an operation behavior identifier.

And the third determining submodule is used for determining the plug-in identification in M candidate plug-in identifications according to the task type information and the operation behavior identification, wherein M is a positive integer.

And the fourth determining submodule is used for determining a parameter checking rule in P candidate parameter checking rules according to the task type information and the operation behavior identification, wherein P is a positive integer.

According to an embodiment of the present disclosure, the parameter check rules include a base parameter check rule and an auxiliary parameter check rule.

The verification module 930 includes: and the fifth determining sub-module, the first response sub-module and the second response sub-module.

And the fifth determining submodule is used for carrying out basic parameter verification on the parameter to be verified according to the basic parameter verification rule to obtain a basic parameter verification result.

The first response sub-module is used for responding to the basic parameter verification result to represent that the task parameter to be verified passes through basic parameter verification, and carrying out auxiliary parameter verification on the parameter to be verified according to an auxiliary parameter verification rule to obtain an auxiliary parameter verification result.

And the second response sub-module is used for responding to the auxiliary parameter verification result to represent that the task parameter to be verified passes the auxiliary parameter verification and obtaining a task parameter verification result representing that the task parameter to be verified passes the verification.

According to an embodiment of the present disclosure, the processing module 940 includes: a sixth determination sub-module and a seventh determination sub-module.

And the sixth determining submodule is used for acquiring target task data corresponding to the task to be processed according to the task type information and the operation behavior identification.

And the seventh determining submodule is used for carrying out format conversion processing on the target task data to obtain a task processing result.

According to an embodiment of the disclosure, in the case that the task type information is a database task, the task parameter to be checked includes a database identifier and a task data identifier corresponding to the database identifier.

The sixth determination submodule includes: the device comprises a first connection unit and a first acquisition unit.

The first connection unit is used for establishing a first communication connection between the proxy end and the database corresponding to the database identifier according to the database identifier.

The first acquisition unit is used for acquiring target task data according to the task data identification based on the first communication connection.

According to the embodiment of the disclosure, in the case that the task type information is a terminal task, the task parameter to be checked includes a terminal identifier and a task data identifier corresponding to the terminal identifier.

The sixth determination submodule includes: the second connecting unit and the second acquiring unit.

And the second connection unit is used for establishing a second communication connection between the proxy end and the remote terminal server by using the terminal corresponding to the terminal identifier.

The second acquisition unit is used for acquiring target task data according to the task data identification based on the second communication connection.

According to the embodiment of the disclosure, in the case that the task type information is an interface task, the task parameter to be checked includes an interface identifier and an element identifier corresponding to the interface identifier.

The sixth determination submodule includes: generating unit, response unit.

And the generation unit is used for generating a simulation interface corresponding to the interface identifier according to the interface identifier by using the simulation browser, wherein the simulation interface comprises at least one simulation element.

And the response unit is used for responding to the trigger of the simulation element corresponding to the element identifier in the simulation interface to acquire the target task data.

According to an embodiment of the present disclosure, the seventh determination submodule includes: the device comprises a first determining unit and a second determining unit.

And the first determining unit is used for determining a target data format according to the task type information and the operation behavior identification.

And the second determining unit is used for carrying out format conversion processing on the target task data according to the target data format to obtain a task processing result.

According to an embodiment of the present disclosure, the task processing device further includes: and calling a determining module and an authentication sending module.

And the call determining module is used for determining the call times corresponding to the object identification to be matched under the condition that the object identification to be matched is characterized by the object identification matching result and the object identification are not matched.

And the authentication sending module is used for responding to the fact that the calling times meet the preset conditions and sending an authentication request to the proxy end corresponding to the object identification to be matched.

Fig. 10 schematically illustrates a block diagram of a proxy creation apparatus according to an embodiment of the present disclosure.

As shown in fig. 10, the agent creation apparatus 1000 may include: an acquisition module 1010 and a creation module 1020.

And an obtaining module 1010, configured to obtain, in response to receiving the registration request, reference object information corresponding to the object identifier according to the object identifier in the registration request, where the registration request further includes the object information to be verified and at least one license platform identifier.

And the creating module 1020 is used for responding to the matching of the object information to be verified and the reference object information, and creating a proxy end corresponding to the object identifier according to the object identifier and the at least one license platform identifier. The agent end is applied to the task processing device provided by the other aspect of the disclosure.

Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.

For example, any of the matching module 910, the determining module 920, the verifying module 930, and the processing module 940 may be combined in one module/unit/sub-unit, or any of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments of the present disclosure, at least one of the matching module 910, the determination module 920, the verification module 930, and the processing module 940 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging the circuitry, or in any one of or a suitable combination of any of the three implementations of software, hardware, and firmware. Alternatively, at least one of the matching module 910, the determining module 920, the verifying module 930, and the processing module 940 may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any number of the acquisition module 1010 and creation module 1020 may be combined in one module/unit/sub-unit or any number of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments of the present disclosure, at least one of the acquisition module 1010 and creation module 1020 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging the circuits, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the acquisition module 1010 and the creation module 1020 may be at least partially implemented as a computer program module which, when executed, may perform the corresponding functions.

It should be noted that, in the embodiment of the present disclosure, the task processing device portion corresponds to the task processing method portion in the embodiment of the present disclosure, the proxy end creating device portion in the embodiment of the present disclosure corresponds to the proxy end creating method portion in the embodiment of the present disclosure, the description of the task processing device portion specifically refers to the task processing method portion, and the description of the proxy end creating device portion specifically refers to the proxy end creating method portion, which is not described herein again.

The electronic device shown in fig. 11 is merely an example, and should not impose any limitations on the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 11, a computer electronic device 1100 according to an embodiment of the present disclosure includes a processor 1101 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1102 or a program loaded from a storage section 1109 into a Random Access Memory (RAM) 1103. The processor 1101 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 1101 may also include on-board memory for caching purposes. The processor 1101 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flow according to embodiments of the present disclosure.

In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are stored. The processor 1101, ROM 1102, and RAM 1103 are connected to each other by a bus 1104. The processor 1101 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1102 and/or the RAM 1103. Note that the program may be stored in one or more memories other than the ROM 1102 and the RAM 1103. The processor 1101 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the disclosure, the electronic device 1100 may also include an input/output (I/O) interface 1105, the input/output (I/O) interface 1105 also being connected to the bus 1104. The electronic device 1100 may also include one or more of the following components connected to an input/output (I/O) interface 1105: an input section 1106 including a keyboard, a mouse, and the like; an output portion 1107 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1108 including a hard disk or the like; and a communication section 1109 including a network interface card such as a LAN card, a modem, and the like. The communication section 1109 performs communication processing via a network such as the internet. The drive 1110 is also connected to an input/output (I/O) interface 1105 as required. Removable media 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed as needed in drive 1110, so that a computer program read therefrom is installed as needed in storage section 1108.

According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1109, and/or installed from the removable media 1111. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1101. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 1102 and/or RAM 1103 described above and/or one or more memories other than ROM 1102 and RAM 1103.

Embodiments of the present disclosure also include a computer program product comprising a computer program comprising program code for performing the methods provided by the embodiments of the present disclosure, the program code for causing an electronic device to implement the task processing methods and agent creation methods provided by the embodiments of the present disclosure when the computer program product is run on the electronic device.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1101. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program can also be transmitted, distributed over a network medium in the form of signals, downloaded and installed via the communication portion 1109, and/or installed from the removable media 1111. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. A task processing method is applied to an agent end and comprises the following steps:

determining a plug-in identification and a parameter verification rule according to the task information to be processed under the condition that the object identification to be matched is characterized by the object identification matching result and the object identification to be matched is matched;

2. The method according to claim 1, wherein, in the case that the object identification matching result indicates that the object identification to be matched matches the object identification, determining a plug-in identification and a parameter verification rule according to the task information to be processed includes:

3. The method of claim 1, wherein the parameter verification rules include a base parameter verification rule and an auxiliary parameter verification rule;

And verifying the task parameters to be verified according to the parameter verification rule, wherein the obtaining the task parameter verification result comprises the following steps:

4. A method according to any one of claims 1 to 3, wherein said responding to the task parameter verification result to characterize the task parameter to be verified by verification, processing the task to be processed corresponding to the task processing request with a plug-in corresponding to the plug-in identification, and obtaining a task processing result includes:

5. The method according to claim 4, wherein in the case that the task type information is a database task, the task parameter to be checked includes a database identifier and a task data identifier corresponding to the database identifier;

the step of obtaining target task data corresponding to the task to be processed according to the task type information and the operation behavior identification comprises the following steps:

6. The method according to claim 4, wherein in the case that the task type information is a terminal task, the task parameter to be checked includes a terminal identifier and a task data identifier corresponding to the terminal identifier;

7. The method according to claim 4, wherein in the case that the task type information is an interface task, the task parameter to be checked includes an interface identifier and an element identifier corresponding to the interface identifier;

8. The method of claim 4, wherein the performing format conversion processing on the target task data to obtain the task processing result includes:

9. A method according to any one of claims 1 to 3, further comprising:

and responding to the calling times meeting a preset condition, and sending an authentication request to the proxy end corresponding to the object identification to be matched.

10. A proxy end creation method is applied to a server end and comprises the following steps:

responding to the matching of the object information to be verified and the reference object information, and creating a proxy end corresponding to the object identifier according to the object identifier and the at least one license platform identifier;

wherein the proxy end is used for executing the task processing method according to any one of claims 1 to 9.

11. A task processing device, applied to an agent, comprising:

the matching module is used for responding to the monitoring task processing request, matching the object identifier to be matched in the information processing request according to the object identifier corresponding to the proxy end to obtain an object identifier matching result, wherein the task processing request further comprises task information to be processed and task parameters to be checked;

The determining module is used for determining a plug-in identification and a parameter verification rule according to the task information to be processed under the condition that the object identification to be matched is matched with the object identification by the object identification matching result;

12. A proxy end creation device is applied to a server end and comprises:

the acquisition module is used for responding to a received registration request and acquiring reference object information corresponding to an object identifier according to the object identifier in the registration request, wherein the registration request also comprises the object information to be verified and at least one license platform identifier; and

Wherein the proxy is configured to execute the task processing device of claim 11.

13. An electronic device, comprising:

one or more processors;

a memory for storing one or more instructions,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1 to 9 or claim 10.

14. A computer readable storage medium having stored thereon executable instructions which when executed by a processor cause the processor to implement the method of any one of claims 1 to 9 or claim 10.

15. A computer program product comprising computer executable instructions for implementing the method of any one of claims 1 to 9 or claim 10 when executed.