CN113360060A

CN113360060A - Task implementation method and device and electronic equipment

Info

Publication number: CN113360060A
Application number: CN202110560134.9A
Authority: CN
Inventors: 孙一鸣
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-05-21
Filing date: 2021-05-21
Publication date: 2021-09-07
Anticipated expiration: 2041-05-21
Also published as: CN113360060B; WO2022242641A1

Abstract

The application discloses a task implementation method and device and electronic equipment, and belongs to the technical field of communication. The method comprises the following steps: receiving a first input aiming at a target control, wherein the target control is used for triggering execution of M functions according to a target execution sequence, the M functions are functions in at least one application of the electronic equipment, and M is an integer greater than 1; in response to a first input, executing the M functions in a target execution order; the input data of the first function comprises output data of the second function, the first function and the second function are all functions in M functions, and the execution sequence of the second function is before the execution sequence of the first function.

Description

Task implementation method and device and electronic equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a task implementation method and device and electronic equipment.

Background

Currently, electronic devices can work cooperatively through a plurality of functions to realize some tasks (hereinafter, referred to as cooperative tasks).

Illustratively, when the electronic device receives an image (hereinafter referred to as image 1) through the communication application, the user may first trigger the electronic device to save the image 1 to the gallery, and open the image 1 stored in the gallery through the image processing application, so as to process the image 1 through the image processing application, and save the processed image 1. The user may then trigger the electronic device to send the processed image 1 to the friend through the communication application. Therefore, the cooperative tasks of receiving, processing and sending the image 1 can be realized through the cooperative work among the transceiving function of the communication application, the storage function of the gallery and the image processing function of the image processing application.

However, according to the above method, since the electronic device can be triggered to implement the cooperative task through the different functions after the input of the functions, the operation process of implementing the task through the cooperative work of the functions is complicated.

Disclosure of Invention

The embodiment of the application aims to provide a task implementation method, a task implementation device and electronic equipment, and the problem that the operation process of implementing a task through cooperative work of a plurality of functions is complex can be solved.

In a first aspect, an embodiment of the present application provides a task implementing method, where the method includes: receiving a first input aiming at a target control, wherein the target control is used for triggering execution of M functions according to a target execution sequence, the M functions are functions in at least one application of the electronic equipment, and M is an integer greater than 1; in response to the first input, executing the M functions in the target execution order; wherein the input data of the first function comprises output data of the second function, the first function and the second function are both functions of the M functions, and the execution order of the second function is before the execution order of the first function.

In a second aspect, an embodiment of the present application provides a task implementing apparatus, where the apparatus includes: a receiving module and an executing module; the receiving module is configured to receive a first input for a target control, where the target control is configured to trigger execution of M functions according to a target execution order, where the M functions are functions in at least one application of the electronic device, and M is an integer greater than 1; the execution module is used for responding to the first input received by the receiving module and executing the M functions according to the target execution sequence; wherein the input data of the first function comprises output data of the second function, the first function and the second function are both functions of the M functions, and the execution order of the second function is before the execution order of the first function.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

In this embodiment of the present application, a first input for a target control may be received, where the target control is configured to trigger execution of M functions according to a target execution order, where the M functions are functions in at least one application of an electronic device, and M is an integer greater than 1; and in response to a first input, executing the M functions in a target execution order; the input data of the first function is output data of the second function, the first function and the second function are all functions in the M functions, and the execution sequence of the second function is before the execution sequence of the first function. According to the scheme, when a certain task is required to be realized in a manner that a plurality of functions (for example, the M functions) are coordinated, the electronic device is triggered to execute the M functions according to an execution sequence (for example, a target execution sequence) capable of realizing the task through the input of the target control, so that the task can be realized after the M functions are executed according to the target execution sequence. Therefore, compared with a scheme that a series of inputs are required to be performed on different functions in the prior art, the task implementation method provided by the embodiment of the application can simplify the operation process of implementing the task through the cooperative work of a plurality of functions.

Drawings

Fig. 1 is a schematic diagram of a task implementation method provided in an embodiment of the present application;

fig. 2 is a schematic diagram of data transmission directions of M functions in a task implementation method according to an embodiment of the present application;

fig. 3 is a second schematic diagram illustrating data transmission directions of M functions in the task implementation method according to the embodiment of the present application;

fig. 4 is one of interface diagrams of a task implementation method application provided in an embodiment of the present application;

fig. 5 is a second schematic interface diagram of an application of the task implementation method according to the embodiment of the present application;

fig. 6 is a third schematic interface diagram of an application of the task implementation method according to the embodiment of the present application;

fig. 7 is a schematic diagram of a target control in a task implementation method application provided in an embodiment of the present application;

FIG. 8 is a fourth schematic interface diagram of an application of the task implementation method according to the embodiment of the present application;

fig. 9 is a fifth schematic interface diagram of an application of the task implementation method according to the embodiment of the present application;

FIG. 10 is a sixth schematic interface diagram of an application of the task implementation method according to the embodiment of the present application;

fig. 11 is a seventh schematic interface diagram of an application of the task implementation method according to the embodiment of the present application;

FIG. 12 is a schematic diagram of a task implementation device in an embodiment of the present application;

FIG. 13 is a schematic view of an electronic device in an embodiment of the present application;

fig. 14 is a hardware schematic diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

Some of the nouns or terms referred to in the claims and the specification of the present application will be explained first.

Script (Script): is an executable file written according to a certain format using a specific descriptive language (i.e., a scripting language). A scripting language, also known as a build-out language, or dynamic language, is a programming language used to control software applications, and scripts are usually stored in text (ascii) and are only interpreted or compiled when called.

It should be noted that when the script is executed, a computer (for example, the task implementation device in the embodiment of the present application) executes a series of operations. For example, the task implementing device may set an execution order of the M functions to a target execution order described below by executing one script, and generate a target control for triggering execution of the M functions in the target execution order.

The task implementation method, the task implementation device, and the electronic device provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

At present, when some tasks are realized, a plurality of functions are often needed, for example, output data of one function is used as input data of another function; therefore, when the functional application is required to cooperatively work to realize the task, the user needs to trigger the electronic device to switch back and forth among the plurality of functions, so that the operation process of cooperatively working through the plurality of functions to realize the task is very complicated.

Further, since the processing results (i.e. output data) of different functions may be stored in different folders, the process of searching for the processing results of different functions is also cumbersome.

In order to solve the above technical problem, the task implementation method provided in the embodiment of the present application expands the desktop design concept as follows:

1) some functions in the control application (e.g., the reverse function, the flip function, etc. in the video processing application) independently provide services, e.g., a function component that sets the indication function. After providing a desired input (e.g., an image) to a function, the electronic device processes the image via the function and outputs the processed result.

2) A special type of interface (for example, a first interface described below) is provided, and a functional component indicating the function in 1) above may be included in the first interface. The function indicated by the functional components can be rapidly triggered and executed through the functional components.

3) In the component interface in 2) above, if the data type of the output data of the function (hereinafter referred to as function 1) indicated by one functional component is compatible with the data type of the input data of the function (hereinafter referred to as function 2) indicated by another functional component, the connection of function 1 and function 2 can be achieved by connecting the output terminal of the one functional component with the input terminal of the other functional component. After function 1 is connected with function 2, the electronic device may directly transmit output data of function 1 to function 2 as input data of function 2. This allows some more complex tasks to be performed by function 1 and function 2 in sequence.

It should be noted that, in the embodiment of the present application, a user may trigger to connect two or more functional components by inputting a functional component in a first interface; alternatively, the at least two functional components may be connected by running a script that instructs the at least two functional components to be connected. The method can be determined according to actual use requirements, and the embodiment of the application is not limited.

Optionally, in this embodiment of the application, the script may be obtained from a server, may also be stored locally by the electronic device, and may also be received through a communication application, which may specifically be determined according to an actual use requirement, and this embodiment of the application is not limited.

In the embodiment of the present application, a plurality of connected functional components in the component interface are collectively referred to as a functional control (which may also be referred to as a function in spoken language). It will be appreciated that each functionality control indicates two or more functionalities. It is understood that a user can trigger to execute all functions indicated by a function control according to a certain execution sequence (for example, a target execution sequence described below) through input of the function control, and after all functions indicated by the function control are executed, a task cooperatively realized through the functions can be realized. Therefore, the functions can be directly triggered to be executed according to a certain sequence by directly inputting the function controls which indicate a plurality of functions capable of cooperatively finishing a cooperative task, and after the functions are executed, a task cooperatively realized through the functions is realized; one or more inputs are not required to be sequentially carried out on different functions, and output data of each function is not required to be searched, so that the operation process of completing tasks through cooperation of the functions can be simplified.

As shown in fig. 1, an embodiment of the present application provides a task implementation method, which may include

steps

101 and 102 described below. The following is an exemplary description of the task implementation method.

Step 101, a task implementation device receives a first input of a user for a target control.

The target control may be configured to trigger execution of M functions according to a target execution order, where the M functions are functions in at least one application of the electronic device, and M is an integer greater than 1.

It can be understood that the M functions may be functions in the same application, or functions in different applications, and may be determined specifically according to actual use requirements, and the embodiment of the present application is not limited.

Optionally, in this embodiment of the application, the target control may be set by the user triggering the task implementing device, or may be set by the task implementing device based on a downloaded or received script. The method can be determined according to actual use requirements, and the embodiment of the application is not limited. For the description of the script, reference may be made to the related description of the script in the above noun explanation section, and details are not repeated here to avoid repetition.

Optionally, in this embodiment of the application, the task implementation device may display at least one function control on the second interface, where the at least one function control includes a target control.

Optionally, in this embodiment of the application, the second interface may be a desktop of the electronic device, and may also be a first interface described below, where the first interface is an interface for setting a function control in the electronic device.

In the embodiment of the application, the first interface can also be called a component page, and the two interfaces have the same meaning and can be interchanged.

Optionally, in this embodiment of the application, a first identifier indicating the first interface may be set on the third interface, and the user may trigger the task implementing device to display the first interface by inputting the first identifier, for example, clicking on the first identifier.

Optionally, in this embodiment of the application, the third interface may be a notification bar interface or a status bar interface (which may also be referred to as an application drawer).

Optionally, in this embodiment of the application, the first input may be an input of a target control in the second interface by a user, or the first input may be an input of acquiring data through an application, for example, the first input may be an input of selecting an image from a gallery.

Optionally, in this embodiment of the application, the first input may be any possible input such as a touch input, an input to an entity key, a facial recognition input, a fingerprint input, an empty gesture input, and the like, which may be determined specifically according to an actual use requirement, and this embodiment of the application is not limited.

It is understood that in the embodiment of the present application, the user may trigger the task implementation device to perform step 102 described below in the first interface, the desktop, or the application interface.

Step 102, the task implementing device responds to the first input and executes M functions according to the target execution sequence.

The input data of the first function is output data of the second function, the first function and the second function are functions with different execution orders in the M functions, and the execution order of the second function is before the execution order of the first function. The data type of the input data of the first function may be compatible with the data type of the output data of the first function, i.e. the output data of one function is used as the input data of another function on the premise that: the data type of the input data of the further function may be compatible with the data type of the output data of the one function.

For example, assuming that the type of the output data of one function is type 1 and the types of the input data of another function include type 1, type 2, and type 3, the output data of the one function can be used as the input data of the another function, i.e., the data type of the output data of the another function is compatible with the data type of the input data of the one function.

Optionally, in this embodiment of the present application, the data type of the input data and the output data of the function may include at least one of the following: application data class (i), application behavior class (ii), user input class (iii), or any possible data type such as user-customizable data type (iiii).

The above-mentioned i, ii, iii and iiii are described in detail below, respectively.

i, the data of the application dataclass may include at least one of: text, image, video, audio, application information (e.g., application name).

ii, the data of the application behavior class may include any possible application behaviors such as a behavior of calling an application, a behavior of adjusting application parameters, a behavior of sharing application data, and the like.

iii, the data of the user input class comprises at least one of: the input form of the user input and the input object of the user input.

Optionally, in this embodiment of the present application, the input form of the user input may be a contact form or a non-contact form, and the contact form includes any possible contact form such as a single click, a double click, multiple clicks, a slide, a drag, a double press, or a long press. The non-contact form includes biometric information recognition (e.g., fingerprint recognition, iris recognition) or spaced-apart gestures, etc.

Optionally, in this embodiment of the application, if the input form of the user input is a contact form, the user input may be input to a physical button, a virtual control, a virtual identifier, or an interface, and may be specifically determined according to actual use requirements.

iiii, a user definable data type means that a form can be provided to a user, making the user customizable data form, and using these customized data forms for input and output. The user definable data type may be a template used to represent a certain type of data, such as a user prefers a certain type of music that can be broken down into several different forms of features (i.e., different members), such as text (lyrics, names, etc.), images (cover art), audio (timbre, melody, etc.). A user-definable data type may also serve as a data that conveys a concept to effect some type of operation.

In the embodiment of the present application, data of which the data type is a user-definable data type may be used as input data and/or output data of the function.

Illustratively, with the user-definable data type as class A music, the task force can filter, merge, and disassemble members of the class A music through the adapter component. Thus, when a user requires class A music for some processing, a collaborative task is achieved by connecting the adapter component with components of other basic functions.

In the embodiment of the present application, when the task implementing device executes M functions, the M functions are executed according to the execution order of the M functions.

Optionally, in this embodiment of the application, the first function may include at least one of the M functions, and the second function may also include at least one of the M functions.

Optionally, in this embodiment of the present application, the output data of one of the second functions may be used as the input data of one or more of the first functions; the output data of a plurality of functions of the second function may also be used as input data of one function of the first function. The method can be determined according to actual use requirements, and the embodiment of the application is not limited.

Exemplarily, as shown in fig. 2, assuming that the arrows in fig. 2 indicate the transmission direction of the output data of the function, then: as shown in fig. 2 (a), the second function 21 includes a function a, the first function includes a function B and a function C, and output data of the function a is input data of the function B and the function C, that is, output data of one of the second functions is input data of a plurality of the first functions. As shown in fig. 2 (b), the second function 22 includes a function D and a function E, the first function includes a function F, and output data of the function D and the function E are input data of the function F, that is, output data of a plurality of functions in the second function is input data of one function in the first function.

Optionally, in this embodiment of the present application, the execution order of at least one of the first functions may be the same or different. At least one of the second functions may be executed in the same order or in a different order, which may be determined according to actual usage requirements, and the embodiments of the present application are not limited.

Illustratively, assume that the M functions include 3 functions, the 3 functions being arranged in the order of execution: function a, function B, and function C; as shown in fig. 3, the output data of function a may be the input data of function B, and both the output data of function a and the output data of function B are the input data of function C. As can be seen from fig. 3, although the execution order of the function a and the function B is different, the output data of the function a and the output data of the function B can be simultaneously used as the input data of the function C. That is, in the embodiment of the present application, output data of a function executed earlier may be used as input data of a function executed later.

It should be noted that, in the embodiment of the present application, after the task implementing device executes M functions according to the target execution order, a task (hereinafter referred to as task 1) that can be implemented only when the M functions are required to cooperate with each other can be implemented. That is, the process of executing M functions, i.e., the process of controlling the M functions to cooperate to complete task 1, is performed in the target execution order.

Optionally, in this embodiment of the application, in an actual implementation, the task implementing device may execute at least part of the M functions according to a target execution order; that is, the task implementing device does not need to start execution from the function of the first execution order among the M functions. For example, assume that M functions include 4 functions, and the execution order (i.e., target execution order) of the 4 functions is: function 1 → function 2 and function 3 (i.e., function 2 and function 3 are performed in the same order) → function 4; then, the task implementing device executes the function 1, the function 2, the function 3 and the function 4 according to the target execution sequence; function 2 and function 3, function 4 may also be executed in the target execution order; the functions 4 may also be performed in the target execution order.

In the task implementation method provided in the embodiment of the present application, when a certain task is required to be implemented in a manner that multiple functions (for example, the M functions) are coordinated, the electronic device may be triggered to execute the M functions according to an execution sequence (for example, a target execution sequence) capable of implementing the task by inputting a target control indicating the M functions, so that the task may be implemented after the M functions are executed according to the target execution sequence. Therefore, compared with a scheme that a series of inputs are required to be performed on different functions in the prior art, the task implementation method provided by the embodiment of the application can trigger the task to be completed cooperatively through a plurality of functions through one input, so that the cooperative work through a plurality of functions can be simplified, and the operation process of the task can be realized.

Optionally, in this embodiment of the present application, for a function including multiple input data, it is necessary to wait for all the input data to arrive before executing the function.

Alternatively, in this embodiment, if the function 1 outputs a plurality of output data (e.g. when a plurality of photos are taken continuously), and the plurality of output data are respectively taken together with the output data of the function 2 as the input data of the function 3, the plurality of output data may form an input queue, and respectively taken together with the output data of the other function as the input data of the third function. Wherein function 1, function 2 and function 3 are different functions among the M functions.

Optionally, in this embodiment of the present application, when there is input data to be processed for a function, a prompt identifier (for example, a number) is displayed on the functional component indicating the function to inform the user of the number of inputs waiting on the current path. The user may click on the prompt to open an input details float window in which the user may view the input summary information (e.g., as a thumbnail) and click on the summary information may view the input details and data (e.g., as an image). The user can trigger to adjust the arrangement sequence of the input data in the queue or delete part of the input data through input. For the description of the functional components, reference may be made to the description of the functional components in the foregoing embodiments, and details are not repeated here to avoid repetition.

Alternatively, in this embodiment of the application, the step 102 may be specifically implemented by a step 102a described below.

Step 102a, the task implementing device executes the M functions from the initial function of the M functions according to the target execution order and the initial input data.

Wherein the initial input data may be input data of an initial function, and the initial function may be any one of the following (1) to (4):

(1) a preset function; (2) a function determined according to a data type of the initial input data; (3) a function determined according to a user input; (4) the function of the first order is performed.

In this embodiment, the initial function is a function that is executed first after the task implementing device receives the first input.

Optionally, in this embodiment of the application, the number of the initial functions may be one or multiple.

In the embodiment of the present application, after the task implementing device receives the first input, the initial function of the M functions and the functions whose execution order is after the execution order of the initial function may be executed, and the functions whose execution order is before the execution order of the initial function may not be executed.

Alternatively, in this embodiment of the application, the task implementation device may determine the initial function first, and then obtain the initial input data based on the determined initial function, for example, the above-mentioned (1), (3), and (4). Alternatively, initial input data may be obtained and then the initial function may be determined based on the initial input parameters, such as (2) above.

Optionally, in this embodiment of the application, in (1), (3) and (4) above, the first input is an input of a target control in the second interface by a user; in the above (2), the first input is an input for acquiring data by an application.

The above (1), (2) and (3) are described in detail below, respectively.

(1) The initial function is a preset function among the M functions.

Optionally, in this embodiment of the application, before the user performs the first input, the task implementation device may be triggered to set an initial function by the input.

(2) The initial function is a function determined according to a data type of initial input data among the M functions.

In the embodiment of the application, the task implementation device can bind the target control with the operation of acquiring the application data in the application. For example, when a user triggers and selects data such as text or pictures in an application, the task implementation device may display a floating menu, where the floating menu includes a plurality of function controls, and functions indicated by the plurality of function controls include a function (hereinafter referred to as function X) for inputting a data type that is compatible with the data type of the data, and when the user selects a target control of the plurality of function controls, the task implementation device may send the data to the target control, and execute the functions indicated by the target control according to a target execution order.

It is understood that the task implementation device may also bind the target control with the operations of screen capture, audio recording, video, game, etc. to automatically perform at least some of the M functions described above after receiving the operations.

Optionally, in this embodiment of the application, the initial function may be a first function, in which a data type of output data is compatible with initial input data, of M functions arranged in the target execution order. Of course, the data type of the output data may be compatible with the first function of the initial input data among the M functions arranged in the target execution order. The binding requirement can be specifically determined.

(3) The initial function is a function determined according to a user input among the M functions.

Optionally, in this embodiment of the present application, before the step 102a, the task implementation method provided in this embodiment of the present application may further include the following step 103 and step 104.

And 103, responding to the first input by the task realization device, and displaying at least two first options.

Wherein the first option indicates all of the M functions in the same execution order.

And 104, the task implementation device receives a fourth input of a target option in the at least two first options.

Optionally, in this embodiment of the application, the fourth input may be a touch input to the target option, for example, the fourth input is a click, a long press, or a re-press input of the user on the target option.

And step 105, the task implementation device responds to the fourth input and determines that the initial function is the function indicated by the target option.

In the embodiment of the application, the task implementation device can execute the M functions from the initial function of the M functions according to the target execution sequence and the initial input data, and the initial function is a preset function, a function determined according to the data type of the initial input data, a function determined according to the user input, or a function with the first execution sequence, so that the flexibility of implementing the task can be improved on the basis of simplifying the operation process of implementing the task through the cooperative work of a plurality of functions.

Optionally, in this embodiment of the application, when the target control is displayed on the first interface, and the first interface further includes at least one data identifier, each data identifier indicates at least one data; the first input may be an input for moving a first data identifier of the at least one data identifier to the target control; the initial input data is data indicated by the first data identifier, and the initial function is a function determined according to the data type of the initial input data in the M functions, or a function with a first execution order.

It should be noted that, in actual implementation, the first interface may further include N functional components, each functional component has a function, and the user may further move the data identifier to one functional component of the N functional components, so as to trigger the task implementation device to process the data indicated by the data identifier through the function indicated by the functional component. The N functions indicated by the N functional components may include a function of the M functions, or may not include a function of the M functions.

For example, assuming that the first interface includes at least one interface, the user may drag one or more data identifications in the at least one interface onto a functional component indicating a sending function in the at least one interface to trigger the task implementation device to send the data.

Optionally, in this embodiment of the application, the task implementation device may display the data identifier of the output data of the function at a position adjacent to the function component or the function control indicating the function in the first interface, for example, at an output end of the function component or the function control. If a function outputs a plurality of data, the data identifications of the data can be displayed in a folder.

Optionally, in this embodiment of the application, the data type of the data indicated by the at least one data identifier may be any possible data type, such as an application data type, an application behavior type, a user input type, and a user-customizable data type.

Optionally, in the embodiment of the present application, in the above (2), as shown in fig. 4, the first interface 40 includes a target control 41, where the target control is used to trigger execution of the function 1, and the function 3, the function 4, that is, according to a target execution order, to execute M functions; the target control 41 may include an input area 42, and the first input may specifically be an input of the user moving the first data identifier 43 onto the input area 42, so that the task implementing device may execute the M functions in response to the first input, starting with a function of a data type of which the input data type includes data indicated by the first data identifier, in the target execution order and the data indicated by the first data identifier.

It can be understood that, in the embodiment of the present application, the at least one piece of data is identified as a shortcut entry of data in the electronic device.

Optionally, in this embodiment of the application, a plurality of data identifiers on the first interface may be categorized into one data folder, and the user may click on the data folder to trigger the task implementation device to display the expansion interface of the data folder, and display the plurality of data identifiers on the expansion interface.

Optionally, in this embodiment of the application, the data indicated by the at least one data identifier may be stored in a storage space (hereinafter, referred to as a target storage space) corresponding to the first interface, and of course, may also be stored in any storage space other than the target storage space in the electronic device, for example, in a storage corresponding to an application. The method can be determined according to actual use requirements, and the embodiment of the application is limited.

Optionally, in this embodiment of the application, a user may send data in a desktop or an application to the target storage space through input triggering, and display a data identifier of the data on the first interface.

Illustratively, as shown in fig. 5 (a), when a user selects one data from the interface 50 of an application (hereinafter referred to as application 1), the task implementation device may display an option of "send to component interface (i.e. first interface)", and when the user selects to send to a component page, if the application 1 supports sending the data therein to the first interface, the task implementation device may send the data into the target storage space; if the application 1 does not support sending the data therein to the first interface, the user may copy or cut the selected data and paste it in the target storage space. After the task implementing device saves the selected data in the target storage space, as shown in (b) of fig. 5, a data identifier 52 of the data may be displayed on the first interface 51.

It can be understood that, when a user inputs an application interface to trigger the task implementing device to obtain data through an application where the application interface is located, such as downloading a file, taking a picture, and the like, the user may also trigger the task implementing device to store the data in the target storage space.

Further exemplarily, as shown in fig. 5 (b), a data adding control 53 may be included on the first interface, and the user may trigger the task implementing device to add data in the target storage space by inputting to the data adding control 53, and display a data identifier of the added data on the first interface.

Optionally, in this embodiment of the application, the task implementation device may display the newly created data identifier in an empty area on the first interface, and if the empty area on the first interface is located, may newly create an interface and then display the newly created data identifier.

Optionally, in this embodiment of the application, in the process that the task implementing device executes the M functions according to the target execution order, the output data of each function may be cached, for example, the output data of each function is cached for a preset time duration.

In the embodiment of the application, the data identifier of the data can be set on the first interface, so that a user can directly select the data meeting the requirement on the first interface without manually entering the folder to select the data, and the operation process can be further simplified.

Optionally, in this embodiment of the application, the data types of the input data of the initial input function are different, and the method for the task implementing device to obtain the initial input data may also be different.

The following describes in detail a method for the task implementation device to obtain the initial input data, taking the data types of the input data of the initial input function as i (i.e., application data class), ii (i.e., application behavior class), and iii (i.e., user input class) as examples.

Optionally, in this embodiment of the application, in the above i, that is, the data type of the input data of the initial input function is an application data class, after the task implementing device receives the first input for the target control, an interface including a data identifier of the application data may be displayed first, and a user may trigger the task implementing device to obtain the application data corresponding to the selection input through selection input of the data identifier.

Optionally, in this embodiment of the application, in the above ii, that is, after the task implementing device receives the first input to the target control, if the monitoring right of the application behavior of one application is allowed to monitor, the task implementing device may monitor the application behavior of the application, and use the monitored application behavior as the input data of the initial function; if the permission of the application behavior of one application is not allowed to monitor, the task implementation device may first prompt the user to set the monitoring permission of the application behavior of the application to be allowed to monitor, and then obtain the application behavior of the application.

Optionally, in the embodiment of the present application, in the above iii, that is, the data type of the input data of the initial input function (i.e., the initial input data) is a user input class, and the initial input data is obtained through a first target input of a user on one interface (hereinafter, referred to as a target interface), after the task implementing device receives the first input, the target interface may be displayed first, and when the first target input of the user on the target interface is received, the task implementing device may obtain the initial input data and execute the initial function according to the initial input data.

For example, assuming that the initial function is a photographing function, the task implementation device may run a camera application after the user clicks on the target control 60 as shown in (a) of fig. 6, and may display a photographing preview interface 61 (i.e., a target interface) as shown in (b) of fig. 6; when the task implementation device can receive a user click input (i.e., a first target input) on the shooting control 62 on the shooting preview interface, the task implementation device can control the shooting function to shoot and output a shot image.

Further exemplarily, assuming that the initial function is a handwriting input function (or an electronic signature function), after the user clicks on the target control, the task implementation device may display a handwriting input interface (i.e., a target interface), which includes a cancel control, a confirm control, and a handwriting area; when the task implementation device receives the handwriting input of the user in the handwriting area and the click input (namely, the first target input) to the confirmation control, the task implementation device may generate a handwriting identifier according to the input parameters of the handwriting input, where the handwriting identifier may be a pattern, a character, or the like.

Further, assuming that the initial function includes a handwriting function and a receiving function of the communication application, and both the output data of the handwriting input function and the output data of the receiving function are input data of a batch signing function, the task implementing device may send a handwriting identifier output by the handwriting function and a plurality of documents received by the receiving function to the signing function, and the signing function signs the handwriting identifier to each document of the plurality of PDFs.

Further exemplarily, assuming that the initial function is a recording function, after the user clicks on the target control, the task implementation device may display a recording interface, where the recording interface includes a start recording control, a pause recording control, and an end recording control, and when the task implementation device receives a click input of the start recording control from the user, the task implementation device may control the recording function to start recording and output recorded audio data.

In the embodiment of the application, the initial input data can be acquired in various ways, so that the operation flexibility can be further improved, and the human-computer interaction performance can be improved.

Optionally, in this embodiment of the present application, before the step 101, the task implementation method provided in this embodiment of the present application may further include the following step 106 and step 107.

And 106, receiving second input of the user for the M functional components in the first interface by the task implementation device.

And step 107, responding to the second input, and connecting the M functional components through at least one connecting component according to the target execution sequence by the task implementation device.

Wherein each functional component indicates one of the M functions described above, the second input may be used to trigger setting of the execution order of the M functions as the target execution order. The target control is determined by the connected M functional components.

Optionally, in this embodiment of the application, the target control may be displayed in a first form or in a second form, specifically, as shown in fig. 7 (a) is a schematic diagram of the target control displayed in the first form, it can be seen that the target control displayed in the first form is a thumbnail or a simplified diagram of the M connected functional components; alternatively, as shown in fig. 7 (b) which is a target control displayed in the second form, it can be seen that the target control displayed in the first form includes M functional components and a connecting component for connecting the M components, that is, includes M functional components in a connected state.

It is to be understood that, in the embodiment of the present application, when the target control is a thumbnail of the M connected function components, the user may input on the target control displayed in the first form as shown in (a) in fig. 7 (different from the first input described above) to trigger the task implementation device to display the target control displayed in the second form as shown in (b) in fig. 7.

It can be understood that, in the embodiment of the present application, the target execution order is any execution order capable of meeting the actual use requirement of the user.

Optionally, in this embodiment of the present application, each functional component includes a data input port and a data output port, and the data input port and the data output port may be in a display state or a hidden state.

For example, when the data input port and the data output port of one functional component are in a display state, the data input port and the data output port of the functional component may be represented by a dotted frame or a warning symbol (e.g., "x" in fig. 2).

Optionally, in this embodiment of the application, it is assumed that the at least two connection assemblies are two connection assemblies, and the task implementing device connects the two function assemblies through one connection assembly, specifically, the task implementing device may connect a data output port of one function assembly with a data input port of another function assembly through the connection assembly; to instruct to take the output data of the function instructed by the one functional component as the input data of the function instructed by the other functional component.

It is understood that in practical implementation, the data input port of each functional component may be connected to the data output port of at least one functional component; the data output port data of each functional component may be connected to the data input port of at least one functional component.

It is to be understood that, in the embodiments of the present application, the functions indicated by the at least two functional components include at least two functions that are executed in different orders.

Optionally, in the embodiment of the present application, the connecting assembly may be a pipe assembly (e.g., the pipe assembly 30 in fig. 3), a flow dividing assembly (e.g., the flow dividing assembly 31 in fig. 3), or a converging assembly (e.g., the converging assembly 44 in fig. 4), wherein the pipe assembly may connect two functional assemblies; the shunting component and the convergence component can be connected with at least three functional components, the shunting component is used for taking output data of one function as input data of a plurality of functions, and the convergence component is used for taking output data of a plurality of functions as input data of one functional component.

Optionally, in this embodiment of the present application, the second input may be any input that can set an execution order for the M functions.

Specifically, the second input may be a user input for moving the M function components (first implementation), a user input for an option menu of the M function components (second implementation), or an input for at least one connection component (third implementation).

The three implementations described above will be described in detail below with M ═ 2 as an example.

The first implementation mode comprises the following steps: the second input is user movement input to the M functionality controls.

Illustratively, as shown in fig. 8 (a), a function component 1 and a function component 2 are included on the first interface, the function component 1 indicates a function g1, and the function component 2 indicates a function g2 that a user can press the function component 1 for a long time and drag the function component 1 to the function component 2; when the function component 1 partially coincides with the function component 2, as shown in (b) in fig. 8, if the data type of the input data of the function g1 is compatible with the data type of the output data of the function g2, this indicates that the output data of the function component 2 can be taken as the input data of the function indicated by the function component 1, so that the task implementing device can connect the data input port of the function component 1 with the data output port of the function component 2 when the function component 1 is dropped, that is, when it means leaving the screen, as shown in (c) in fig. 8; if the data type of the input data of the function g1 is not compatible with the data type of the output data of the function g2, it means that the output data of the function component 2 cannot be used as the input data of the function indicated by the function component 1, so that when the function component 1 is dropped, that is, the user's finger leaves the screen, the task implementation apparatus does not connect the function component 1 and the function component 2, and outputs the prompt information that cannot be connected. It is to be understood that, in the present example, the second input is an input of dragging the functional component 1 onto the functional component 2.

Alternatively, in this embodiment of the application, if the output data of the function component 2 can be used as the input data of the function indicated by the function component 1, a connection identifier (such as a connection identifier 81 shown in (b) of fig. 8) may be displayed to prompt the user that the data output port of the function component 2 can be connected to the data input port of the function component 2. Otherwise, a prompt message may be output to prompt the user that the data output port of the functional component 2 cannot be connected to the data input port of the function 2.

Optionally, in this embodiment of the application, during the process of dragging the functional component 1, the task implementation device may display a position prompt identifier (e.g., a position prompt identifier 82 shown in (b) in fig. 8) on the first interface, where the position prompt identifier 82 is used to prompt a display area of the functional component 1 when the functional component 1 is released. It is understood that the display area is determined according to the size of the functional component 1 and the current position of the functional component 1, and specifically, the display area is an empty area which is closest to the current position of the functional component 1 in the first interface and has a size larger than or equal to the size of the functional component.

Optionally, in this embodiment of the application, if the connection identifier is displayed, the task implementing device may display the functional component 1 on the right side of the functional component 2 and in an area adjacent to the functional component 2, and then connect the data input port of the functional component 1 with the data output port of the functional component 2. If the connection identifier is not displayed, the task implementation apparatus may drag the display area of the functional component 1 before the functional component 1 to display the functional component 1, i.e., keep the display area of the functional component 1 unchanged.

The second implementation mode comprises the following steps: the second input is user input to a menu of options for the M functional components.

Further exemplarily, as shown in fig. 9 (a), the first interface includes a function component 1 and a function component 2, the function component 1 indicates a function g1, the user can press the function component 1 for a long time, as shown in fig. 9 (b), the task implementation apparatus can display an option menu 91 of the function component 1, the option menu 91 includes a connection panel 92, the connection panel includes 4 connection keys (i.e., 4 black triangles shown in fig. 9 (b)), and then the user can click on any one of the connection keys to trigger the first function component located in the direction indicated by the connection key in the first interface to be connected to the function component 1; for example, as shown in (b) of fig. 9, if the user clicks a connection key pointing to the functional component 2, the task implementation apparatus may connect the data input port of the functional component 1 with the data output port of the functional component 2 located at the left side of the functional component 1 through the connection component, as shown in (c) of fig. 9.

Optionally, in this embodiment of the application, the task implementing device may preset a connection manner, for example, preset that a data input port of a functional component to which the connection key belongs is connected to a data output port of a first functional component in a direction indicated by the connection key; therefore, after the user inputs one connecting key, the task implementation device can connect the functional component to which the connecting key belongs and the functional component selected by the connecting key according to the preset connecting mode. Or, after the user inputs a connection key, the task implementing device may display a selection box, where the selection box includes a third option and a fourth option, the third option is "connected to the data input port of the selected functional component", and the fourth option is "connected to the data output port of the selected functional component", so that the user may trigger the task implementing device to connect the functional component to which the connection key belongs and the functional component selected by the connection key according to the connection mode selected by the user by inputting the third option or the fourth option. Or, after the user inputs a connection key, the task implementing device may automatically determine the connection mode according to the data compatibility between the functional component to which the connection key belongs and the functional component selected through the connection key.

In a third implementation, the second input is a user input to the at least one connection component.

Optionally, in this embodiment of the application, the first interface may further include a connection assembly, and a user may drag two ends of one connection assembly to connect two ends of the connection assembly with different functional assemblies respectively.

For example, a user may connect one end of one connection component to a data input port of one functional component and the other end of the connection component to a data output port of another functional component.

Optionally, in this embodiment of the present application, the connection component may be an identifier with an arrow, and a direction of the arrow indicates a data transmission direction between the functional components connected to the connection component.

In the embodiment of the present application, in the three implementation manners, on the premise that data compatibility is satisfied, the data input port of one functional component can be connected to the data output port of another functional component.

It can be understood that, in the embodiment of the present application, the example that the task implementing device connects the two functional components is taken as an example for illustration, and for the description that the task implementing device connects the M functional components, reference may be specifically made to the related description that the task implementing device connects the two functional components.

Optionally, in this embodiment of the application, after the M functional components are connected, if the display position of at least one functional component of the M functional components is adjusted, the task implementation device may keep the connection between the M functional components unchanged, that is, the connection between the functional component and the connection component is not disconnected.

In the embodiment of the application, the target execution order is set for the M functions by the user through the second input trigger task implementation device, so that the task implemented by the task implementation device after executing the M functions according to the target execution order can be ensured to meet the actual requirements of the user.

Further, since the user can trigger the task realization device to set the execution order of the functions by input, the flexibility of realizing the task by a plurality of functions can be improved.

Optionally, in this embodiment of the application, if the M functions include a third function and at least two fourth functions, and output data of the at least two fourth functions is input data of the third function, after the step 107, the task implementation method provided in this embodiment of the application may further include the following step 108.

And step 108, the task realization device displays the synchronous identification on the first connection component.

Wherein the first connecting component is a connecting component connected with functional components indicating a third function and at least two fourth functions. The synchronization identifier (e.g., the synchronization identifier shown in dashed lines in fig. 3) may be used to: a, indicating that after the execution of at least two fourth functions is completed, a third function is executed, namely the synchronous execution progress; and/or b, the synchronization identifier may be used to trigger re-executing the M functions from a fifth function of the M functions, that is, to rollback the execution progress, where the execution order of the fifth function is smaller than the execution order of the third function.

It is to be understood that, in the embodiment of the present application, the third function may be a function in the first function, and the at least two fourth functions may be functions in the second function.

Optionally, in this embodiment of the application, the first connecting assembly may be one connecting assembly, or may be a plurality of connecting assemblies. For example, assuming that the number of the at least two fourth functions is 2, the first connecting assembly may be two pipe assemblies; alternatively, the first connection assembly may be 1 shunt assembly.

Optionally, in this embodiment of the present application, in the above a, the synchronization component is used to separate and synchronize the functional components. For example, as shown in FIG. 3, after the task implementation device determines that both the output data of function A and the output data of function B reach function C, the task implementation device may perform function C; otherwise, function C is not performed.

Optionally, in this embodiment of the present application, the task implementing device may further configure the synchronization component, where the configuring of the synchronization component includes: after the execution of at least two fourth functions is completed, automatically executing a third function; or after the execution of at least two fourth functions is completed and the input of the user for triggering the continuous execution is received, executing the third function. When the synchronization identifier is configured to execute the third function after the execution of the at least two fourth functions is completed and after an input that the user triggers the continued execution is received, the task implementing device may display a floating key for the user to operate after the execution of the at least two fourth functions is completed.

Optionally, in this embodiment of this application, in the above b, the task implementing device may buffer input data of each of the M functions, so that when the user inputs to the synchronization component, triggers the fifth function to start, and re-executes the M functions, the task implementing device may re-execute the fifth function directly according to the buffered input data of the fifth data, and execute, according to the target execution order, a function subsequent to the fifth function in the execution order of the M functions.

In the embodiment of the application, when the input data of one function is the output data of a plurality of functions, the task implementation device may display the synchronization component on the connection component between the functional component of the one function and the functional components of the plurality of functions, and the synchronization component may be used to synchronize the execution progress and/or rollback the execution progress, so that the operation accuracy and flexibility may be further improved on the basis of simplifying the operation process of implementing the task through the cooperative work of the plurality of functions.

Optionally, in this embodiment of the present application, after the step 106, the task implementation method provided in this embodiment of the present application may further include the following step 109 and step 110.

Step 109, the task implementing device receives a third input from the user.

For the description of the first interface, reference may be specifically made to the description of the first interface in the foregoing embodiment, and details are not repeated here to avoid repetition.

And step 110, the task implementation device responds to the third input and executes the target operation corresponding to the third input.

Wherein the target operation may be any one of the following (one), (two), (three), (four) and (five):

and (I) adding at least one functional component in the first interface.

Optionally, in this embodiment of the application, a user may trigger addition of at least one functional component on the first interface by inputting an icon in the desktop; or 2, the user can trigger the addition of at least one functional component in the first interface by adding a control input to the component in the first interface.

Illustratively, as shown in (a) of fig. 10, a user may click on a left region of one application icon 101 of the desktop 100, as shown in (b) of fig. 10, the task implementing device may display N function components 102 and a first interface 103, the N function components 102 being function components of at least part of functions in an application indicated by the application icon 101; the user can drag at least one of the N functional components 102 to the first interface according to the actual usage requirement of the user, so as to add the at least one functional component to the first interface. It can be seen that the third input comprises an input to an icon in the desktop and a movement input to the at least one functional component. It is to be understood that, in this example, the function indicated by the at least one functional component is a function in the same application, and N is a positive integer.

Optionally, in this embodiment of the application, after the user clicks on a left area of an application icon on the desktop, the task implementation device may display the N functional components first, and after the user presses any one of the N functional components for a long time, the task implementation device keeps displaying the N functional components and displays the first interface.

Alternatively, in this example, as shown in (b) of fig. 10, when the first interface includes a plurality of sub-interfaces, the task implementation apparatus may display the sub-interfaces in the form of thumbnails, respectively, and the user may drag at least one functional component to any one of the sub-interfaces.

Further illustratively, as shown in fig. 11 (a), the user may input a component addition control 111 in the first interface 110, and as shown in fig. 11 (b), the task implementing device may display a functional component list interface 112 in which functional components of functions in the plurality of applications may be included. Then, the user can select the at least one functional component in the functional component list interface according to the actual use requirement. It is to be understood that, in the present example, the functions indicated by the at least one functional component may be functions in one or more applications.

Alternatively, in this embodiment of the present application, the functional components in the functional component list interface may be ordered in various manners such as by initials, function types (e.g., video processing category, music processing category), and the like.

(II) deleting at least one object from the first interface.

Optionally, in this embodiment of the application, the third input is a touch input of the user to at least one object in the first interface.

Optionally, in this embodiment of the application, for each object in the at least one object, one object may be one function component or one function control.

Optionally, in this embodiment of the application, the first interface includes a delete control, and the user may trigger to delete the functional component or the functional control from the first interface by deleting an input to the component.

And (III) adjusting the display parameters of at least one object in the first interface.

Optionally, in this embodiment of the application, the display parameter of the object may include at least one of a display position of the object, a display size of the object, and an arrangement structure of the object.

Optionally, in this embodiment of the application, if a user needs to adjust a display parameter of an object, the user may first press on the object for a long time to trigger the object to be in a parameter adjustment mode. Specifically, the task implementation device may display a size adjustment box around the object, and the user may trigger the adjustment of the display parameter of the object by dragging the input of the size adjustment box. After the adjustment is completed, the user can click on the blank of the first interface to trigger the task implementation device to exit the parameter adjustment mode.

Optionally, in this embodiment of the application, if an object is a functional component, the display parameter of the object may include an arrangement structure of the object. The arrangement structure of the object refers to an arrangement structure between the functional components in the functional control.

For example, assuming that the plurality of function components in the function control are in a linear configuration before the third input is received, the user can adjust the arrangement of the plurality of function components to a triangular configuration by the third input.

And (IV) adjusting the function parameters of the function indicated by the target function component.

Optionally, in this embodiment of the application, the third input is a touch input of the user to the target function component in the first interface.

Optionally, in this embodiment of the application, the target function component may be a function component in the first interface, or a function component in a function control of the first interface.

Optionally, in this embodiment of the application, the function parameter of the function may be determined according to the function, for example, if the target function component indicates the image processing function, the function parameter of the image processing function may be: brightness, contrast, gray scale, exposure, etc.; if the target function component indicates a handwriting input function, the function parameters of the handwriting input function may include: line color, line width, etc.

Optionally, in this embodiment of the application, if a user needs to adjust a function parameter of a function indicated by the target function component, the user may first press on the target function component for a long time to trigger and display an option menu of the target function component, where the option menu includes a parameter adjustment identifier for adjusting the function parameter of the target function component, and the user may trigger and adjust the function parameter of the function indicated by the target function component by inputting the parameter adjustment identifier.

The parameter adjustment identifier may be, for example, a slider for adjusting a parameter of the value range class or a key for adjusting a parameter of the switch type.

And (V) adjusting the data transmission direction between the two functional components.

Optionally, in this embodiment of the application, the third input is a touch input of the user to the two functional components in the first interface.

In the embodiment (v), the two functional components are connected to each other.

Optionally, in this embodiment of the application, if a user needs to adjust a data transmission direction between at least two functional components, the user may first trigger the task implementation device to display an option menu of any one of the at least two functional components, then input the option menu, and then input the option menu through a connection panel in the option menu, so as to trigger the task implementation device to adjust the data transmission direction between the at least two functional components.

It should be noted that, in the above embodiment, it is exemplified that step 109 and step 110 are executed after step 106, and in an actual implementation, step 109 and step 110 may be executed as long as the task implementation apparatus displays the first interface, for example, step 109 and step 110 may be executed before step 101 or step 106.

In the embodiment of the application, because the user can trigger the task implementation device to add at least one functional component in the first interface, delete at least one object from the first interface, adjust the display parameter of at least one object in the first interface, adjust the functional parameter of the function indicated by the target functional component, or adjust the data transmission direction between two functional components through the third input, the operational flexibility of implementing the task through the cooperative work of multiple functions can be further improved.

Optionally, in this embodiment of the application, the task implementation device may classify the functional components according to the types of the functions indicated by the functional components, and display different types of functional components in different areas of the first interface.

Optionally, in this embodiment of the application, the first interface may be divided into a plurality of regions, each region includes one window, and each window is used for displaying one type of functional component. The user can trigger the task realization device to switch the functional components through sliding input on the window. For example, a functional component a is displayed in a window, and the user can slide to the left on the window to trigger the task implementation device to display a functional component b, wherein the types of the functions indicated by the functional component a and the functional component b are the same.

It should be noted that, in the task implementation method provided in the embodiment of the present application, the execution main body may be a task implementation device, or a control module in the task implementation device, configured to execute the task implementation method. In the embodiment of the present application, a task implementation method executed by a task implementation device is taken as an example to describe the task implementation device provided in the embodiment of the present application.

As shown in fig. 12, an embodiment of the present application provides a task implementing device 120, where the task implementing device 120 may include: a receiving module 121 and an executing module 122. A receiving module 121, configured to receive a first input for a target control, where the target control may be configured to trigger execution of M functions according to a target execution order, where the M functions are functions in at least one application of an electronic device, and M is an integer greater than 1; an executing module 122, configured to execute the M functions according to the target execution order in response to the first input received by the receiving module 121; the input data of the first function comprises output data of the second function, the first function and the second function are all functions in the M functions, the execution sequence of the second function is before the execution sequence of the first function, and the data type of the input data is compatible with the data type of the output data.

Optionally, in this embodiment of the application, the executing module 122 may be specifically configured to execute the M functions from an initial function of the M functions according to a target execution order and initial input data;

wherein the initial input data is input data of an initial function, and the initial function is any one of the following functions: a preset function, a function determined according to a data type of initial input data, a function determined according to a user input, a function whose execution order is first.

Optionally, in this embodiment of the application, the target control is displayed on the first interface, where the first interface further includes at least one data identifier, and each data identifier indicates at least one piece of data;

the first input is input for moving a first data identifier in the at least one data identifier to the target control;

wherein the initial input data is data indicated by the first data identifier, and the initial function is first in the execution order or determined according to the data type of the initial input data.

Optionally, in this embodiment of the present application, the task implementing device may further include a connection module; the receiving module 121 may be further configured to, before receiving the first input for the target control, receive a second input for M function components in the first interface, where each function component indicates one function in the M functions, and the second input is used to trigger setting of an execution order of the M functions to a target execution order;

a connecting module, which may be configured to connect the M functional components through at least one connecting component in the target execution order in response to the second input received by the receiving module 121;

wherein, the target control is determined by the M connected functional components; each connecting component is connected with at least two functional components in the M functional components, and the connecting components are used for indicating the data transmission direction between the functions indicated by the at least two functional components.

Optionally, in this embodiment of the application, the M functions include a third function and at least two fourth functions, and output data of the at least two fourth functions is input data of the third function; the device also comprises a display module;

a display module, configured to display a synchronization identifier on a first connection component after the connection module connects the M function components, where the first connection component is a connection component connected to a function component indicating a third function and at least two fourth functions;

wherein the synchronization identifier is for:

instructing to perform the second function after performing at least two fourth functions; and/or the presence of a gas in the gas,

the trigger starts from a fifth function of the M functions, which is executed in an order prior to the order of execution of the third function, and the M functions are re-executed.

Optionally, in this embodiment of the application, the receiving module 121 may be further configured to receive a third input;

the executing module 122 may be further configured to, in response to the third input received by the receiving module 121, execute a target operation corresponding to the third input, where the target operation is any one of:

adding at least one functional component in the first interface, deleting at least one object from the first interface, adjusting the display parameter of the at least one object in the first interface, adjusting the functional parameter of the function indicated by the target functional component, and adjusting the data transmission direction between the two functional components; the target function component may be a function component in the first interface or a function component in a function control of the first interface.

In the task implementing apparatus provided in the embodiment of the present application, when a task needs to be implemented in a manner that a plurality of functions (for example, the M functions) are coordinated, the electronic device may be triggered to execute the M functions according to an execution sequence (for example, a target execution sequence) capable of implementing the task through input of the target control, so that the task may be implemented after the M functions are executed according to the target execution sequence. Therefore, compared with a scheme that a series of inputs are required to be performed on different functions in the prior art, the task implementation method provided by the embodiment of the application can simplify the operation process of implementing the task through the cooperative work of a plurality of functions.

The beneficial effects of the various implementation manners in this embodiment may specifically refer to the beneficial effects of the corresponding implementation manners in the above method embodiments, and are not described herein again to avoid repetition.

The task implementation device in the embodiment of the present application may be a device, and may also be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiments of the present application are not particularly limited.

The task implementation device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The task implementation device 120 provided in this embodiment of the application can implement each process implemented by the task implementation method in the method embodiments of fig. 1 to fig. 11, and is not described here again to avoid repetition.

As shown in fig. 13, an electronic device 200 according to an embodiment of the present application is further provided, which includes a processor 202, a memory 201, and a program or an instruction stored in the memory 201 and executable on the processor 202, where the program or the instruction is executed by the processor 202 to implement each process of the task implementation method embodiment, and can achieve the same technical effect, and no further description is provided herein to avoid repetition.

It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and the non-mobile electronic devices described above.

Fig. 14 is a schematic hardware structure diagram of an electronic device implementing an embodiment of the present application.

The electronic device 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

Those skilled in the art will appreciate that the electronic device 1000 may further comprise a power source (e.g., a battery) for supplying power to various components, and the power source may be logically connected to the processor 1010 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The electronic device structure shown in fig. 14 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is not repeated here.

The user input unit 1007 may be configured to receive a first input for a target control, where the target control may be configured to trigger execution of M functions according to a target execution order, where the M functions are functions in at least one application of the electronic device, and M is an integer greater than 1; a processor 1010 for executing the M functions in a target execution order in response to a first input received by the user input unit 1007; the input data of the first function comprises output data of the second function, the first function and the second function are all functions in the M functions, and the execution sequence of the second function is before the execution sequence of the first function.

Optionally, in this embodiment of the present application, the processor 1010 may be specifically configured to execute the M functions from an initial function of the M functions according to a target execution order and initial input data; wherein the initial input data is input data of an initial function, and the initial function is any one of the following functions: a preset function, a function determined according to a data type of initial input data, a function determined according to a user input, and a function whose execution order is the top.

the first input is input for moving a first data identifier in the at least one data identifier to the target control; wherein the initial input data is data indicated by the first data identifier, and the initial function is first in the execution order or determined according to the data type of the initial input data.

Optionally, in this embodiment of the present application, the user input unit 1007 may be further configured to receive, before receiving the first input for the target control, a second input for M function components in the first interface, where each function component indicates one function in the M functions, and the second input is used to trigger setting of the execution order of the M functions to the target execution order; a processor 1010, which may be configured to connect the M functional components through at least one connection component in a target execution order in response to a second input received by the user input unit 1007; wherein, the target control is determined by the M connected functional components; each connecting component is connected with at least two functional components in the M functional components, and the connecting components are used for indicating the data transmission direction between the functions indicated by the at least two functional components.

Optionally, in this embodiment of the application, the M functions include a third function and at least two fourth functions, and output data of the at least two fourth functions is input data of the third function; the apparatus further comprises a display unit 1006; a display unit 1006, which may be configured to display a synchronization identifier on a first connection component after the processor 1010 connects the M functional components, where the first connection component is a connection component connected to a functional component indicating a third function and at least two fourth functions;

wherein the synchronization identifier is for: instructing to perform the second function after performing at least two fourth functions; and/or triggering the M functions to be executed again from a fifth function in the M functions, wherein the execution order of the fifth function is smaller than that of the third function.

Optionally, in this embodiment of the application, the user input unit 1007 may be further configured to receive a third input; the processor 1010 may be further configured to execute a target operation corresponding to the third input in response to the third input received by the user input unit 1007, where the target operation is any one of:

In the electronic device provided in the embodiment of the present application, when a task is required to be implemented in a manner that a plurality of functions (for example, the M functions) are coordinated, the electronic device may be triggered to execute the M functions according to an execution sequence (for example, a target execution sequence) capable of implementing the task through input of the target control, so that the task may be implemented after the M functions are executed according to the target execution sequence. Therefore, compared with a scheme that a series of inputs are required to be performed on different functions in the prior art, the task implementation method provided by the embodiment of the application can simplify the operation process of implementing the task through the cooperative work of a plurality of functions.

It should be understood that in the embodiment of the present application, the input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, and the Graphics Processing Unit 10041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein. The memory 1009 may be used to store software programs as well as various data, including but not limited to application programs and operating systems. Processor 1010 may integrate an application processor that handles primarily operating systems, user interfaces, applications, etc. and a modem processor that handles primarily wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the embodiment of the task implementing method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is a processor in the electronic device in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement each process of the task implementation method embodiment, and the same technical effect can be achieved.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for task implementation, the method comprising:

receiving a first input aiming at a target control, wherein the target control is used for triggering execution of M functions according to a target execution sequence, the M functions are functions in at least one application of electronic equipment, and M is an integer greater than 1;

in response to the first input, executing the M functions in the target execution order;

wherein the input data of a first function comprises output data of a second function, the first function and the second function are both functions of the M functions, and the execution order of the second function precedes the execution order of the first function.

2. The method of claim 1, wherein said executing said M functions in said target execution order comprises:

executing the M functions starting from an initial function of the M functions according to the target execution order and initial input data;

wherein the initial input data is input data of the initial function, and the initial function includes any one of: a preset function, a function determined according to a data type of the initial input data, a function determined according to a user input, and a function of which an execution order is first.

3. The method of claim 2, wherein the target control is displayed on a first interface, the first interface further comprising at least one data identifier therein, each data identifier indicating at least one data;

the first input is an input of moving a first data identifier of the at least one data identifier onto the target control;

wherein the initial input data is the data indicated by the first data identifier, and the initial function is first in execution order or determined according to the data type of the initial input data.

4. The method of any of claims 1-3, wherein prior to the receiving the first input for the target control, the method further comprises:

receiving second inputs for M functional components in a first interface, each functional component indicating one of the M functions, the second inputs for triggering setting of an execution order of the M functions to the target execution order;

in response to the second input, connecting the M functional components by at least one connection component in the target execution order;

wherein the target control is determined by the M connected functional components; each connecting assembly is connected with at least two functional assemblies in the M functional assemblies, and the connecting assemblies are used for indicating the data transmission direction between the functions indicated by the at least two functional assemblies.

5. The method according to claim 4, wherein the M functions include a third function and at least two fourth functions, and output data of the at least two fourth functions is input data of the third function;

after the M functional components are connected by at least one connection component in the target execution order, the method further includes:

displaying a synchronization mark on a first connection component, the first connection component being a connection component connected to a function component indicating the third function and the at least two fourth functions;

wherein the synchronization identifier is configured to:

instructing to perform the second function after performing the at least two fourth functions is completed; and/or the presence of a gas in the gas,

triggering the re-execution of the M functions starting from a fifth function of the M functions, the execution order of the fifth function being before the execution order of the third function.

6. The method of claim 4, further comprising:

receiving a third input;

responding to the third input, and executing a target operation corresponding to the third input, wherein the target operation is any one of the following operations:

adding at least one functional component in the first interface, deleting at least one object from the first interface, adjusting display parameters of at least one object in the first interface, adjusting functional parameters of a function indicated by a target functional component, and adjusting a data transmission direction between the two functional components; the target functional component may be: and the function component in the first interface or the function component in the function control of the first interface.

7. A task implementation apparatus, characterized in that the apparatus comprises: a receiving module and an executing module;

the receiving module is configured to receive a first input for a target control, where the target control is configured to trigger execution of M functions according to a target execution order, where the M functions are functions in at least one application of the electronic device, and M is an integer greater than 1;

the execution module is configured to execute the M functions according to the target execution order in response to the first input received by the receiving module;

8. The apparatus according to claim 7, wherein the execution module is specifically configured to execute the M functions starting from an initial function of the M functions in the target execution order and initial input data;

wherein the initial input data is input data of the initial function, and the initial function is any one of the following: a preset function, a function determined according to a data type of the initial input data, a function determined according to a user input, and a function of which an execution order is first.

9. The apparatus of claim 8, wherein the target control is displayed on a first interface, the first interface further comprising at least one data identifier therein, each data identifier indicating at least one data;

10. The apparatus of any one of claims 7 to 9, further comprising a connection module;

the receiving module is further configured to receive, before the receiving of the first input for the target control, second inputs for M function components in the first interface, each function component indicating one function of the M functions, the second inputs being used to trigger setting of an execution order of the M functions to the target execution order;

the connecting module is used for responding to the second input received by the receiving module and connecting the M functional components through at least one connecting component according to the target execution sequence;

11. The apparatus according to claim 10, wherein the M functions include a third function and at least two fourth functions, and output data of the at least two fourth functions is input data of the third function; the device also comprises a display module;

the display module is configured to display a synchronization identifier on a first connection component after the connection module connects the M function components, where the first connection component is a connection component connected to a function component indicating the third function and the at least two fourth functions;

wherein the synchronization identifier is configured to:

12. The apparatus of claim 10,

the receiving module is further used for receiving a third input;

the executing module is further configured to, in response to the third input received by the receiving module, execute a target operation corresponding to the third input, where the target operation is any one of:

13. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the task implementation method of any one of claims 1 to 6.

14. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of a task implementation method according to any one of claims 1 to 6.