Task management method and apparatus, device and storage medium

Abstract

Embodiments of the present disclosure provide a task management method and apparatus, a device and a storage medium. The method comprises: receiving a creation instruction for a target task in a target application; determining task creation information of the target task on the basis of the creation instruction, wherein the task creation information at least indicates a trigger condition and at least one function required for executing the target task in the target application; and creating in the target application the target task for one or more users on the basis of the task creation information. Therefore, the user can flexibly and autonomously create tasks and manage the tasks in the target application.

Description

Method, apparatus, device and storage medium for task management

[0001] This application claims priority to the Chinese invention patent application entitled “Methods, devices, equipment and storage media for task management” and application number 2023115678149, filed on November 22, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for task management. Background Art

[0003] With the development of information technology, various terminal devices can provide people with a variety of services in work and life. Applications that provide these services can be deployed on these terminal devices. These terminal devices should be able to present different content to different users associated with the application's operations and enable interaction with these users. A rich application interaction interface is an important means of improving user experience.

[0004] Summary of the Invention

[0005] In a first aspect of the present disclosure, a method for task management is provided. The method comprises: receiving a creation instruction for a target task in a target application; determining task creation information for the target task based on the creation instruction, the task creation information indicating at least a triggering condition and at least one function required to execute the target task in the target application; and creating the target task for one or more users in the target application based on the task creation information.

[0006] In a second aspect of the present disclosure, a device for task management is provided. The device includes: an instruction receiving module configured to receive a creation instruction for a target task in a target application; an information determining module configured to determine task creation information for the target task based on the creation instruction, wherein the task creation information at least indicates a trigger condition and at least one function required to execute the target task in the target application; and a task creating module configured to create the target task for one or more users in the target application based on the task creation information.

[0007] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the electronic device to perform the method of the first aspect.

[0008] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the medium, and when the computer program is executed by a processor, the method of the first aspect is implemented.

[0009] It should be understood that the content described in this section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0011] FIG1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

[0012] FIG2 shows a schematic diagram of an example page for task management according to some embodiments of the present disclosure;

[0013] 3A to 3C are schematic diagrams showing some example pages for task management according to some embodiments of the present disclosure;

[0014] 4A and 4B are schematic diagrams showing other example pages for task management according to some embodiments of the present disclosure;

[0015] 5A to 5C are schematic diagrams showing further example pages for task management according to some embodiments of the present disclosure;

[0016] 6A to 6D are schematic diagrams showing further example pages for task management according to some embodiments of the present disclosure;

[0017] FIG7 illustrates a flow chart of a process for task management according to some embodiments of the present disclosure;

[0018] FIG8 shows a schematic structural block diagram of an apparatus for task management according to some embodiments of the present disclosure; and

[0019] FIG9 shows a block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION

[0020] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0021] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below.

[0022] Herein, unless explicitly stated otherwise, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.

[0023] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0024] It is understandable that before using the technical solutions disclosed in the various embodiments of the present disclosure, the type, scope of use, usage scenarios, etc. of the information involved in the present disclosure should be informed to relevant users and authorization should be obtained from relevant users in an appropriate manner in accordance with relevant laws and regulations. The relevant users may include any type of right holders, such as individuals, enterprises, and groups.

[0025] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly prompt the relevant user that the operation requested to be performed will require obtaining and using the information of the relevant user, so that the relevant user can independently choose whether to provide information to the software or hardware such as the electronic device, application, server or storage medium that executes the operation of the technical solution of the present disclosure based on the prompt message.

[0026] As an optional but non-limiting implementation, in response to receiving an active request from a relevant user, a prompt message may be sent to the relevant user in the form of a pop-up window, in which the prompt message may be presented in text form. Furthermore, the pop-up window may also include a selection control for the user to select "agree" or "disagree" to provide information to the electronic device.

[0027] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0028] As used herein, the term "model" can learn the association between corresponding inputs and outputs from training data, so that after training is completed, corresponding outputs can be generated for given inputs. The generation of the model can be based on machine learning technology. Deep learning is a machine learning algorithm that processes inputs and provides corresponding outputs by using multiple layers of processing units. A neural network model is an example of a model based on deep learning. In this article, "model" may also be referred to as "machine learning model", "learning model", "machine learning network" or "learning network", and these terms are used interchangeably in this article.

[0029] FIG1 illustrates a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Environment 100 includes an application management platform 110, which can support the creation and / or execution of applications. In some embodiments, the portion of application management platform 110 that supports application creation can also be referred to as an application creation portion. In some embodiments, the portion of application management platform 110 that supports application execution can also be referred to as an application execution portion.

[0030] As shown in Figure 1, the application creation part can provide a user 105 with an environment for creating and publishing applications. User 105 can be referred to as an application creation user or creator. In some embodiments, the application creation part can be a low-code platform that provides a collection of tools for application creation. The application creation part can support visual development of various types of applications, allowing developers to skip the manual coding process and speed up the application development cycle and cost. The application creation part can support any appropriate platform for users to develop one or more types of applications, for example, it can include a platform based on Application Platform as a Service (aPaaS). Such a platform can support users to efficiently develop applications and implement operations such as application creation and application function adjustment.

[0031] The application creation part can be deployed locally on the terminal device of user 105, and / or can be supported by a server-side device. For example, the terminal device of user 105 can run a client of the application creation part, which can support the interaction between the user and the application creation part provided by the server. In the case where the application creation part runs locally on the user's terminal device, user 105 can directly use the terminal device to interact with the local application creation part. In the case where the application creation part runs on the server-side device, the server-side device can realize the service provision of the client running in the terminal device based on the communication connection between the terminal device. The application creation part can present a corresponding page 130 to the user 105 based on the operation of the user 105 to output and / or receive information related to application creation to the user 105 and / or from the user 105.

[0032] In some embodiments, the application creation portion can be associated with a corresponding database, which stores the data or information required for the application creation process supported by the application creation portion. For example, the database can store the code and description information corresponding to each functional module used to make up the application. The application creation portion can also perform operations such as calling, adding, deleting, and updating the functional modules in the database. The database can also store operations that can be performed on different functional blocks. For example, in a scenario where an application is to be created, the application creation portion can call the corresponding functional blocks from the database to build the application.

[0033] In an embodiment of the present disclosure, a user 105 can create a target application 120 as needed on the application creation portion of the target management platform 110 and publish the target application 120. The target application 120 can be published to any appropriate application runtime portion, as long as the application runtime portion can support the operation of the target application 120. After publication, the target application 120 can be used to be operated by one or more users 145. The user 145 can be referred to as the end user of the target application 120. In some embodiments, the target application 120 may include or be implemented as a digital assistant 122.

[0034] The digital assistant 122 can be configured to have the ability of intelligent dialogue. In the example shown in Figure 1, the digital assistant 122 can be integrated into the target application 120 and assist in executing task processing within the target application 120 as part of the target application 120. In other examples, the digital assistant 122 can be configured as an independently running application, such as a web application or other types of applications. In such an example, the digital assistant 122 and the target application 120 can be regarded as the same application. The digital assistant 122 is provided to assist users in various task processing requirements in different applications and scenarios. During the interaction with the digital assistant 122, the user inputs an interactive message, and the digital assistant 122 provides a reply message in response to the user input. Typically, the digital assistant 122 can support users to input questions in natural language (for example, text questions or voice questions), and perform tasks and provide replies based on the understanding of natural language input and logical reasoning ability.

[0035] In some embodiments, digital assistant 122 can interact with user 145 as a contact. For example, digital assistant 122 can be implemented in an instant messaging (IM) application. Digital assistant 122 can interact with user 145 in a single chat session with user 145. In some embodiments, digital assistant 122 can interact with multiple users in a group chat session including multiple users.

[0036] For each user 145, the client of the application running portion can present an interaction window 142 of the target application 120 or the digital assistant 122 in the client interface, such as a conversation window with the digital assistant 122. The user 145 can enter a conversation message in the conversation window, and the target application 120 can determine a reply message of the digital assistant 122 based on the created configuration information and present it to the user in the interaction window 142. In some embodiments, depending on the configuration of the target application 120, the interaction message with the target application 120 can include messages in multimodal forms, such as text messages (e.g., natural language text), voice messages, image messages, video messages, etc.

[0037] Similar to the application creation part, the application running part can be deployed locally on the terminal device of each user 145, and / or can be supported by a server-side device. For example, the terminal device of user 145 can run a client with the application running part, which can support the interaction between the user and the application running part provided by the server. In the case where the application running part runs locally on the user's terminal device, the user 145 can directly use the terminal device to interact with the local application running part. In the case where the application running part runs on the server-side device, the server-side device can realize the service provision of the client running in the terminal device based on the communication connection between the terminal device. The application running part can present the corresponding application page to the user 145 based on the operation of the user 145, so as to output and / or receive information related to the use of the application to the user 145 and / or receive information from the user 145 from the user 145.

[0038] In some embodiments, at least some of the functionality of the target application 120 and / or at least some of the functionality of the digital assistant 122 in the target application 120 can be implemented based on a model. During the creation or execution of the target application 120, one or more models 155, such as the capabilities of the models 155, can be invoked. In the target application 120, the digital assistant 122 can utilize the models 155 to understand user input and provide responses to the user based on the output of the models 155.

[0039] During the creation process, the application management platform 110 tests the target application 120 using the model 155 to ensure that the target application 120's operating results meet expectations. During operation, in response to various user operation requests of the target application 120, the application execution component may need to use the model 155 to determine the user's response results.

[0040] Although shown as being independent of the application management platform 110, one or more models 155 can run on the application management platform 110 or other remote servers. In some embodiments, the model 155 can be a machine learning model, a deep learning model, a learning model, a neural network, etc. In some embodiments, the model can be based on a language model (LM). A language model can have question-answering capabilities by learning from a large amount of corpus. The model 155 can also be based on other appropriate models.

[0041] The application management platform 110 can run on appropriate electronic devices. The electronic devices here can be any type of device with computing capabilities, including terminal devices or server devices. The terminal device can be any type of mobile terminal, fixed terminal or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication systems (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio broadcast receivers, e-book devices, gaming devices or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. The server device can, for example, include a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, and the like. In some embodiments, the management platform 110 can be implemented based on cloud services.

[0042] It should be understood that the structure and functionality of the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure. For example, although FIG1 illustrates a single user interacting with the application creation portion and a single user interacting with the application execution portion, in practice multiple users may access the application management platform 110 to each create a digital assistant, and each digital assistant may be used to interact with multiple users.

[0043] In typical interactions with digital assistants, the primary form of interaction is instant messaging (IM). Messages often present text and images, making complex charts, forms, and other content difficult to carry. Currently, users expect applications deployed on their devices to provide more complex services, such as performing a range of tasks related to their work and daily lives. Limited by existing digital assistant-user interaction methods, these user demands are often difficult to meet.

[0044] According to an embodiment of the present disclosure, a solution for task management is provided. In this solution, the user of the target application can create, manage, and execute the user's desired tasks in the target application through interaction with the terminal device. Specifically, for the target application, the application running platform receives a creation instruction for the target task. Based on the creation instruction, the task creation information of the target task is determined. The task creation information at least indicates the triggering conditions and at least one function required to execute the target task in the target application. Based on the task creation information, the target task is created for one or more users in the target application. Thus, the user can implement operations related to task management on the target application through interaction with the terminal device, thereby enabling the user to flexibly create and manage tasks, thereby improving the richness of interaction between the user and the terminal device.

[0045] Some example embodiments of the present disclosure will be described in detail below with reference to the examples in the accompanying drawings. It should be understood that the pages shown in the accompanying drawings are merely examples, and a variety of page designs may exist. The various graphical elements in a page may have different arrangements and different visual representations, one or more elements may be omitted or replaced, and one or more other elements may also be present. The embodiments of the present disclosure are not limited in this respect.

[0046] The task management process described in the embodiments of the present disclosure can be implemented on an application management platform, a terminal device on which the application management platform is installed, and / or a server corresponding to the application management platform. In the examples below, for the purpose of discussion, the description is from the perspective of the application management platform, such as the application management platform 110 shown in Figure 1. The user interface presented by the application management platform 110 can be presented via the terminal device of user 105 or user 145, and the application management platform 110 can receive user input via the terminal device of user 105 or user 145. In some embodiments of the present disclosure, user 145 is the terminal user of the target application 120, and user 105 is the manager or maintainer of the target application 120.

[0047] Figure 2 shows an example page 200 for task management according to some embodiments of the present disclosure. After receiving a task management request for a target application 120 from a user 105, for example, if a selection of a control 210 at a function guide bar 201 of a target application 120 by the user 105 is received, the application management platform 110 may present the page 200 for task management shown in Figure 2.

[0048] A list 202 for task management is presented on page 200. As shown in FIG2 , list 202 may include multiple list items, such as task name, task type, function, start time, execution frequency, updater, status, and operation. It should be understood that list 202 may include more or fewer list items. The list shown in FIG2 is for illustrative purposes only and is not intended to limit the embodiments of the present disclosure.

[0049] In list 202, the list item "Task Name" represents a brief description of each task. The list item "Task Type" may represent the task trigger type. In some embodiments of the present disclosure, the list item "Task Type" may include timed triggering and conditional triggering. Timed triggering may be understood as triggering at predetermined time intervals. For example, for the task "regularly sending weekly attendance reports", the time interval for the timed trigger may be one week, while for the task "sending daily attendance statistics", the time interval for the timed trigger may be 24 hours. Conditional triggering may be understood as triggering the task only when a predetermined condition is met. For example, for the task "sending attendance exception records", the trigger condition may be "failing to clock in once" or "being late three times". If it is determined that the trigger condition is met, the task is triggered. In some embodiments, tasks with a certain specific trigger type may also be triggered manually.

[0050] In some other embodiments, the trigger condition may also include: when an update is detected for a data object associated with the target task, the execution of the corresponding target task is triggered. For example, the target task may be associated with a certain data object (e.g., a document, a data table, etc.), and the trigger condition of the target task may include executing the target task when the data object is updated. The target task here may be configured to, for example, notify the user of the update of the data object or other tasks defined by the user. The update of the data object may include different types of update operations such as deletion, modification, and addition of new content of the data object. The trigger condition of the target task may also be configured as a specific type of update operation. In this way, the user can be automatically helped to perform a specific task after the data object that the user is concerned about is updated.

[0051] In list 202, the item "Function" can be understood as the function required to perform a task. For example, the tasks shown in list 202 are all related to attendance. The function required to perform this task may be "HR Assistant".

[0052] The "Start Time" list item indicates the start time of each task. The "Execution Frequency" list item indicates the frequency and time of each task execution. For example, for the task "Regularly send weekly attendance reports", the execution frequency is "Every Friday", while for the task "Send daily attendance statistics", the execution frequency is "Every Day".

[0053] In addition, in list 202, the list item "Updater" indicates the person who created, modified, maintained, etc. the task, such as user 105. The list item "Status" indicates whether the current task is in an open state (such as status indication 203) or in a paused state (such as status indication 204).

[0054] In some embodiments, the "Operation" list item provides a control 205 for the user 105 to edit the task. By selecting the control 205, the user 105 can edit the existing task. In some other embodiments, the "Operation" list item also provides a control 206 for the user 105 to query the task history status, so that the user can query the history of the corresponding task.

[0055] 2 also presents a control 220 for the user 105 to enable the user to create a task. If the user 105 selects the control 220, the application management platform 110 may present the user 105 with a page for creating a task.

[0056] In the embodiment described above in conjunction with FIG. 2 , user 105's task management needs for target application 120 and user 105's needs for task creation are both achieved by inputting corresponding instructions on page 200, i.e., by selecting control 210 and / or control 220. It should be understood that user 105 may also implement the aforementioned operations by inputting other instructions, such as gestures or voice commands. The list shown in FIG. 2 is for illustrative purposes only and is not intended to limit the embodiments of the present disclosure.

[0057] As described above, after detecting the user 105's operation on the control 220, the application management platform 110 may present a page for creating a task to the user 105. Figures 3A to 3C illustrate schematic diagrams of example pages for creating a task according to some embodiments of the present disclosure.

[0058] 3A , after detecting the user 105's operation on the control 220, the application management platform 110 may present a page 300A for creating a task to the user 105. Various operation options associated with the task creation operation are presented in the function navigation bar 301 of the page 300A for creating a task.

[0059] The application management platform 110 may receive a creation instruction for a task in the target application 120 through the page 300A for creating a task and determine task creation information of the target task based on the creation instruction.

[0060] In some embodiments, the application management platform 110 can receive basic information input by the user 105 for creating a task in the target application 120 through the basic information receiving area 310 of the page 300A for creating a task. The basic information input by the user for creating a task in the target application 120 may include, for example, a task name, i.e., the list item "Task Name" corresponding to the list 202 shown in FIG. An entry 311 for receiving the task name input by the user 105 is presented on the page 300A. The user 105 can enter any task name that does not exceed a predetermined threshold number of characters through this entry 311.

[0061] The basic information entered by the user for creating a task in the target application 120 may include, for example, the task type, corresponding to the list item "Task Type" in list 202 shown in FIG2 . Page 300A presents entries 312 and 313 for receiving the user 105's selection of a task type. As shown in FIG3A , on page 300A, the task type selected by the user 105 is a timer-triggered task.

[0062] In addition, the basic information input by the user for creating a task in the target application 120 may include, for example, a usage function, which corresponds to the list item "Function" in the list 202 shown in FIG. The input of the usage function indicates which function of the target application 120 is to be executed by the task. Page 300A presents an entry 314 for receiving the user 105's selection of a usage function. For example, once the user 105 performs an operation on the entry 314, the entry 314 may present, for example, a drop-down menu (not shown) including a plurality of selectable usage functions.

[0063] In addition, basic information may include, for example, function parameters. Page 300A presents an entry 315 for receiving user 105's input regarding function parameters. For example, the function parameters may include template functions and custom functions. For custom functions, a parameter input form may be dynamically provided to the user based on the selected function.

[0064] In some embodiments, the application management platform 110 can receive execution information input by the user 105 for creating a task in the target application 120 through the execution information receiving area 320 in the page 300A for creating a task. As shown in Figure 3A, the task execution information input by the user 105 through the execution information receiving area 320 includes the time zone, which affects the following task execution start time and deadline; the task execution start time (e.g., including the start date and start time), which indicates the time when the function begins to be triggered; the task repetition frequency; the task repetition rule; and the task deadline (e.g., including the deadline date and deadline time). It should be understood that the user 105 can also choose not to expire the task.

[0065] In some embodiments, the application management platform 110 may provide the user 105 with a choice of pushing task information via a message push selection area 330 in the page 300A for creating a task. For example, the user 105 may select whether to push task information via an instant messaging application by operating an instant messaging application on / off control 331.

[0066] Furthermore, in the message push selection area 330, user 105 can add users associated with the task by operating control 332, thereby pushing messages associated with the task to the added users. As shown in FIG3B , after user 105 enters an instruction to add users associated with the task by operating control 332, message push selection area 330 provides user 105 with an entry 334 for searching for users to be added and a drop-down menu 335 presenting one or more candidate users to be added. For example, user 105 can select entry 336 in drop-down menu 336 to add the candidate user corresponding to entry 336 as a user to whom messages associated with the task will be pushed.

[0067] Returning to Figure 3A , in the message push selection area 330 , user 105 can add a group related to the task by operating control 333 , thereby pushing messages associated with the task to the added group. As shown in Figure 3C , after user 105 enters an instruction to add a group related to the task by operating control 333 , message push selection area 330 provides user 105 with an entry 337 for searching for groups to be added and a drop-down menu 338 presenting one or more candidate groups to be added. For example, user 105 can select entry 339 in drop-down menu 338 to add the candidate group corresponding to entry 339 as the group to which messages associated with the task will be pushed.

[0068] 3A to 3C and the detailed description above, after user 105 enters information associated with creating a task, the task creation request can be submitted by operating control 302 in page 300A. Although various information associated with creating a task that user 105 can enter is described above, it should be noted that the task creation information can at least indicate a task triggering condition and at least one function required to execute the task in target application 120.

[0069] Based on the task creation request and the task creation information input by the user, the application management platform 110 creates the task for the user 105 in the target application 120 .

[0070] After a task is created, the user 105 can also perform operations such as modifying, deleting, and browsing history records on the created task.

[0071] 4A and 4B illustrate schematic diagrams of example pages for deleting a created task according to some embodiments of the present disclosure.

[0072] As shown in Figure 4A, page 400A shows a list 410 presenting multiple created tasks and information associated therewith. For example, for the created task "Send today's attendance statistics", user 105 can edit the created task "Send today's attendance statistics" through the control 205 corresponding to the list item "Operation" belonging to the task.

[0073] If the user 105 operates the control 205, the application management platform 110 may present an edit option menu 401 for the created task. The edit option menu 401 may include, for example, a delete option and an immediate execution option.

[0074] If user 105 selects the delete option, application management platform 110 may determine whether the selected task can be deleted. In some embodiments, application management platform 110 may verify whether the user initiating the deletion request has permission to delete the task. For example, if the user initiating the deletion request is an end user and the end user is the creator of the task, application management platform 110 may determine that the task can be deleted. In some embodiments, the creator or maintainer of an application may be configured to have permission to delete one or more tasks created in the application.

[0075] In some other embodiments, the application management platform 110 may determine the execution status of the selected task, for example, whether the task is currently being executed. If it is determined that the task is not currently being executed, the application management platform 110 determines that the task can be deleted.

[0076] If the application management platform 110 determines that a created task can be deleted, as shown in FIG4B , the application management platform 110 presents a prompt 402 on page 400B requesting the user to confirm deletion of the created task. This prompt 402 may be presented, for example, in the form of a pop-up window, as shown in FIG4B . It should be understood that this prompt may also be provided to the user in other ways, such as via a voice prompt, instant message prompt, or the like.

[0077] If confirmation of the user 105 for deleting the created task is determined, for example, the user's operation on the control 403 for confirming deletion is detected, the application management platform 110 may delete the created task from the list 410 of the page 400A.

[0078] In addition, the user can also update the created task. Although not shown, it should be understood that the update operation of the created task is roughly the same as the deletion operation of the created task. For example, the user can initiate an update request for the created task. Upon receiving the request, the application management platform 110 can determine whether the selected task can be updated at this time. In some embodiments, the application management platform 110 can verify whether the user who initiated the update request has the authority to update the task. For example, if the terminal user who initiated the update request is the creator of the task, the application management platform 110 determines that the task can be updated.

[0079] In some other embodiments, the application management platform 110 may determine the execution status of the selected task, for example, whether the task is currently being executed. If it is determined that the task is not currently being executed, the application management platform 110 determines that the task can be updated.

[0080] If the application management platform 110 determines that the task can be updated, it may present a window for the user to input task update content. This window may be similar to the operation page 300A shown in FIG. 3A , which provides the user with an entry for modifying the data object associated with the task.

[0081] As described above, if the conditional triggering of the task includes triggering the execution of the target project when it is detected that the user updates the data object associated with the target task, the task selected for updating can be executed immediately after the updated data object takes effect.

[0082] Although, as described above, the user has already entered information associated with the task trigger, i.e., a timed trigger or a conditional trigger, during the task creation process, the application management platform 110 can also provide the user 105 with the ability to manually trigger a task. Figures 5A to 5C illustrate example pages for manually triggering a created task, according to some embodiments of the present disclosure.

[0083] As shown in Figure 5A, page 500A shows a list 510 presenting multiple created tasks and information associated therewith. For example, for the created task "Send today's attendance statistics", user 105 can edit the created task "Send today's attendance statistics" through the control 205 corresponding to the list item "Operation" belonging to the task.

[0084] If the user 105 operates the control 205, the application management platform 110 may present an edit option menu 501 for the created task. The edit option menu 501 may include, for example, a delete option and an immediate execution option.

[0085] If user 105 selects the "Execute immediately" option, as shown in FIG5B , application management platform 110 presents a prompt 502 on page 500B requesting the user to confirm that they want to immediately execute the created task. This prompt 502 may be presented, for example, in the form of a pop-up window, as shown in FIG5B . It should be understood that this prompt may also be provided to the user in other ways, such as via a voice prompt, instant message prompt, or the like.

[0086] If it is determined that the user 105 confirms that the created task will be executed immediately, for example, if the user operates the control 503 for confirming to execute the created task immediately, the application management platform 110 may immediately execute the created task once.

[0087] Once the application management platform 110 has executed the created task via manual triggering by the user, as shown in FIG5C , page 500C displays a prompt 504 indicating that the task has been successfully executed. This prompt 504 may also indicate that information associated with the execution is available for viewing in the execution history. It should be understood that manual triggering operations can only be performed on tasks that have scheduled triggering enabled.

[0088] As mentioned above, user 105 can browse and query the execution history of a created task. Figures 6A to 6D illustrate schematic diagrams of example pages for querying the execution history of a created task according to some embodiments of the present disclosure. The interactive process related to querying the execution history is further described in detail below in conjunction with Figures 6A to 6D.

[0089] The application management platform 110 can receive a request from user 105 to view the history of a created task. For example, if user 105 is detected to have operated on the view control 505 on page 500C of FIG. 5C , a window 601 displaying the execution history of the corresponding task "Regularly send weekly attendance reports" is presented to user 105 on page 600A of FIG. 6A . In some embodiments, in addition to triggering the view control, user 105 can also initiate a request to view the history of a created task by communicating with the digital assistant (e.g., sending a conversation message "View the execution history of XX task").

[0090] 6A , the execution history list 601 may include list items “Initiation Time” and “Execution Completion Time.” The list item “Time Consumed” indicates the time interval from the initiation time to the execution completion time of the task.

[0091] The "Execution Status" list item can indicate whether the task is "Completed," "In Progress," or "Exception." For example, if a function instance associated with the task is currently executing, the task status is "In Progress." For another example, if all function instances have completed execution and one has an "Exception" status, the task status is "Exception." If all function instances have completed execution and no function instance has an "Exception" status, the task status is "Completed."

[0092] List 601 may also include a list item “Initiator.” The initiator may be, for example, the creator of the task, a task operator with operation authority, or a downstream user.

[0093] List 601 may also include a list item "operation", which provides the user 105 with an entry to query logs related to the execution history of a specific task, such as control 603. If an operation of the user 105 on control 603 is detected, the application management platform 110 presents a window for displaying the log details.

[0094] 6B to 6D further illustrate windows 600B, 600C, and 600D presented for displaying the log details. Window 600B indicates that the current task status is "in progress" through prompt 611, window 600C indicates that the current task status is "completed" through prompt 621, and window 600D indicates that the current task status is "execution exception" through prompt 631.

[0095] As shown in FIG6B , window 600B may indicate the number of successful and abnormal executions of the function execution instances associated with the task via label 612. Although not shown, it should be understood that window 600B may also display the number of function execution instances currently pending for execution associated with the task. Similar labels are presented in window 600C of FIG6C and window 600D of FIG6D . Detailed descriptions are omitted here.

[0096] As shown in FIG6B and FIG6C , for a function instance that has been successfully executed, window 600B and window 600C display the function execution ID, the sending object (eg, the message push object selected by user 105 when creating the task), the start time, and the completion time.

[0097] As shown in FIG6D , for a function instance with an execution exception, a window 600D displays the function execution ID, the sending object (eg, the message push object selected by the user 105 when creating the task), and a description of the cause of the execution exception.

[0098] The above embodiment has described a process in which user 105 manages tasks using target application 120 by interacting with application management platform 110. It should be understood that, although the above description uses user 105 as an example of an administrator or maintainer of target application 120, the above task creation and management operations may also be performed by an end user of target application 120 (e.g., user 145).

[0099] Specifically, when creating a task, the application management platform 110 receives user input representing natural language from the user 145, and the user input may include a creation instruction for the target task. The user input may be text input, voice input, etc. On the user 145 side, an interaction page corresponding to the target application 120 may be provided, such as an interaction window 142 between the user 145 and the digital assistant 122. Through the interaction page or interaction window, the user 145 can freely input instructions, including instructions related to task creation. The application management platform 110 can use a machine learning model to determine task creation information based on user input. A machine learning model, such as model 155, can understand the user's intention to create a task from the user's natural language input, and determine the type of task to be created, trigger conditions, and other required information. In some embodiments, the task created in the target application can be associated with one or more functions in the target application to indicate that the created task will be executed by the associated one or more functions when the task is triggered.

[0100] In some embodiments, model 155 may be invoked and provided with user input and information related to one or more functions in the target application. The output of model 155 may indicate the task type matched by the user input and task creation information triggering conditions. Furthermore, the output of model 155 may indicate the selection of one or more functions in the target application, with the selected functions being associated with the task to be created.

[0101] For ease of understanding, let's take an example where an end user enters "Send me a summary of yesterday's business opportunities at 8:00 AM tomorrow" into the target application. Based on this user input, model 155 can be called to determine that a new task should be created in the target application. This task is a scheduled task, triggered by the time "8:00 AM tomorrow," and associated with the "Business Opportunity Summary" function in the target application. Leveraging model 155's ability to understand natural language, by providing appropriate information to model 155, model 155 can assist in task creation.

[0102] This allows end users to create specific tasks within the target application through simple natural language input, which can then be automatically triggered for execution. Within the target application, machine learning models can provide users with powerful intent understanding and task processing capabilities, providing users with efficient task management capabilities.

[0103] In addition, the end user can also manage previously created tasks by interacting with the digital assistant, including deleting tasks, modifying task creation information, etc. In some embodiments, the end user of the target application 120 can also access and view the page discussed above with respect to user 105 to perform task management. However, from the perspective of the end user, the tasks that can be viewed and managed are tasks related to the end user, such as tasks created by the end user.

[0104] For a target task that has been created, the target application 120 can detect whether the triggering condition of the target task has been met. For a timed task, the target application 120 can determine whether the triggering condition is met based on the arrival of the timed time. For a rule-based task, the target application 120 can determine whether one or more rules are met, thereby determining whether to trigger the corresponding task. In some embodiments, if the rules for triggering the target task are relatively complex, the target application 120 can use the model 155 to determine whether the rules are met. If the triggering condition of the target task is met, since the target task is associated with at least one function in the target application when it is created, the target task can be executed using the associated at least one function. After the target task is executed, a prompt of the execution result of the target task can be provided to one or more users related to the target task. For example, a prompt of the execution result can be provided to one or more users via a digital assistant 122 in the form of a conversation message.

[0105] In some embodiments, one or more functions in target application 120 are configured to schedule model 155 to implement their respective processing. When the trigger conditions of a target task are met and the target task is to be executed, at least one function associated with the target task may provide information related to the target task to model 155. After processing the received information, model 155 may provide the output of model 155 to target application 120. The output of model 155 may indicate the execution result of the target task. Thus, by obtaining the output from model 155, the execution result of the target task can be determined and notified to one or more users.

[0106] According to embodiments of the present disclosure, the administrator or end user of the target application can implement task management-related operations on the target application 120 by interacting with the terminal device, thereby enabling users to flexibly create and manage tasks, thereby enhancing the richness of interaction between users and the terminal device. Furthermore, in some embodiments, after a task is created, the task can be automatically executed for the user by detecting whether trigger conditions are met. During task execution, since the target application or a function within the target application is configured to be able to schedule a model to assist in task execution, this further improves task execution efficiency and accuracy.

[0107] 7 shows a flow chart of a process 700 for task management according to some embodiments of the present disclosure. The process 700 may be implemented at the application management platform 110. The process 700 is described below with reference to FIG1.

[0108] In block 710 , the application management platform 110 receives a creation instruction for a target task in a target application.

[0109] In block 720 , the application management platform 110 determines task creation information for the target task based on the creation instruction. The task creation information at least indicates a trigger condition and at least one function required to execute the target task in the target application.

[0110] In block 730 , the application management platform 110 creates the target task for one or more users in the target application based on the task creation information.

[0111] In some embodiments, process 700 further includes: in response to a trigger condition of the target task being met, executing the target task using the at least one function; and providing a prompt of the execution result of the target task to the one or more users.

[0112] In some embodiments, utilizing the at least one function to execute the target task includes: in response to the triggering condition of the target task being met, the at least one function provides information related to the target task to the machine learning model; obtaining the output of the machine learning model; and determining the execution result of the target task based on the output of the machine learning model.

[0113] In some embodiments, receiving the creation indication includes: receiving user input represented by natural language from an end user of the target application, the user input including a creation indication for the target task; and wherein determining the task creation information includes: utilizing a machine learning model to determine the task creation information based on the user input.

[0114] In some embodiments, receiving the creation indication includes: receiving a creation indication for the target task from an application creator of the target application, wherein determining the trigger condition and the at least one function includes: providing a task creation page in response to the creation indication; and receiving the task creation information of the target task via the task creation page.

[0115] In some embodiments, the task creation information further indicates at least one of the following: the name of the target task, the type of the target task, the one or more users targeted by the target task, and a method for providing a prompt of the execution result of the target task.

[0116] In some embodiments, process 700 also includes: presenting corresponding task information of multiple tasks created in the target application, the task information of the first task among the multiple tasks indicating at least one of the following: the type of the first task, the function required by the first task, the execution frequency of the first task, the time information of the first task, and the creator of the first task.

[0117] In some embodiments, process 700 further includes: receiving a history viewing request for a second task among the plurality of tasks; and; and presenting an execution record of the second task in response to the history viewing request.

[0118] In some embodiments, the execution record includes a log of the second task.

[0119] In some embodiments, process 700 further includes: in response to receiving a trigger for immediate execution of the target task created in the target application, executing the target task regardless of whether a trigger condition of the target task is satisfied.

[0120] In some embodiments, the trigger condition includes at least one of the following: a time-based trigger condition, a trigger condition based on at least one rule.

[0121] In some embodiments, the at least one rule includes at least: updating of a data object associated with the target task.

[0122] In some embodiments, process 700 further includes: receiving a deletion request or an update request for the target task; and executing the deletion or update of the target task based on at least one of the permissions of the user initiating the deletion request or the update request and the execution status of the target task.

[0123] In some embodiments, the user who initiates the deletion request or update request includes the terminal user of the target application, and performing the deletion or update of the target task includes: performing the deletion or update of the target task based on at least one of the following: whether the terminal user is the creator of the target task and / or whether the execution status of the target task is in an executing state.

[0124] 8 shows a schematic structural block diagram of an apparatus 800 for task management according to some embodiments of the present disclosure. The apparatus 800 may be implemented in or included in the application management platform 110. Each module / component in the apparatus 800 may be implemented by hardware, software, firmware, or any combination thereof.

[0125] As shown in the figure, the apparatus 800 includes an instruction receiving module 810 configured to receive a creation instruction for a target task in a target application. The apparatus 800 also includes an information determining module 820 configured to determine task creation information for the target task based on the creation instruction, wherein the task creation information at least indicates a trigger condition and at least one function required to execute the target task in the target application. The apparatus 800 also includes a task creating module 830 configured to create the target task for one or more users in the target application based on the task creation information.

[0126] In some embodiments, the device 800 also includes: a task execution module, configured to execute the target task using the at least one function in response to the triggering condition of the target task being met; and a result prompt module, configured to provide a prompt of the execution result of the target task to the one or more users.

[0127] In some embodiments, the task execution module includes: a model calling module, configured to provide information related to the target task to the machine learning model by the at least one function in response to the trigger condition of the target task being met; an output acquisition module, configured to obtain the output of the machine learning model; and a result determination module, configured to determine the execution result of the target task based on the output of the machine learning model.

[0128] In some embodiments, the indication receiving module 810 is configured to: receive user input represented in natural language from an end user of the target application, wherein the user input includes a creation instruction for the target task; and wherein the information determination module 820 is further configured to utilize a machine learning model to determine the task creation information based on the user input.

[0129] In some embodiments, the indication receiving module 810 is configured to: receive a creation indication for the target task from the application creator of the target application, wherein the information determination module 820 is also configured to provide a task creation page in response to the creation indication; and receive the task creation information of the target task via the task creation page.

[0130] In some embodiments, the task creation information further indicates at least one of the following: the name of the target task, the type of the target task, the one or more users targeted by the target task, and a method for providing a prompt of the execution result of the target task.

[0131] In some embodiments, the device 800 also includes: a task information presentation module, configured to present corresponding task information of multiple tasks created in the target application, the task information of the first task among the multiple tasks indicates at least one of the following: the type of the first task, the function required by the first task, the execution frequency of the first task, the time information of the first task, and the creator of the first task.

[0132] In some embodiments, the device 800 also includes: a history viewing request receiving module configured to receive a history viewing request for a second task among the multiple tasks; and an execution record presenting module configured to present the execution record of the second task in response to the history viewing request.

[0133] In some embodiments, the execution record includes a log of the second task.

[0134] In some embodiments, the apparatus 800 further includes a target task execution module configured to execute the target task in response to receiving a trigger for immediate execution of the target task created in the target application, regardless of whether the triggering condition of the target task is met.

[0135] In some embodiments, the trigger condition includes at least one of the following: a time-based trigger condition, and a trigger condition based on at least one rule.

[0136] In some embodiments, the at least one rule includes at least: updating of a data object associated with the target task.

[0137] In some embodiments, the device 800 also includes: a request receiving module, configured to receive a deletion request or an update request for the target task; and a request execution module, configured to execute the deletion or update of the target task based on the authority of the user initiating the deletion request or the update request and at least one of the execution status of the target task.

[0138] In some embodiments, the user who initiates the deletion request or update request includes the terminal user of the target application, and the request execution module is also configured to execute the deletion or update of the target task based on at least one of the following: whether the terminal user is the creator of the target task and / or whether the execution status of the target task is in an executing state.

[0139] FIG9 shows a block diagram of an electronic device 900 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 900 shown in FIG9 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 900 shown in FIG9 may include or be implemented as the application creation platform 110, the application management platform 110 of FIG1 , or the apparatus 600 of FIG6 .

[0140] As shown in FIG9 , electronic device 900 is a general-purpose electronic device. Components of electronic device 900 may include, but are not limited to, one or more processors or processing units 910, memory 920, storage device 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. Processing unit 910 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 920. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capabilities of electronic device 900.

[0141] The electronic device 900 typically includes a plurality of computer storage media. Such media can be any accessible media that the electronic device 900 can access, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 920 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 930 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 900.

[0142] The electronic device 900 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 9 , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 920 may include a computer program product 925 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0143] The communication unit 940 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 900 can be implemented as a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 900 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0144] The input device 950 may be one or more input devices, such as a mouse, keyboard, or trackball. The output device 960 may be one or more output devices, such as a display, a speaker, or a printer. The electronic device 900 may also communicate with one or more external devices (not shown) via the communication unit 940 as needed, such as a storage device, a display device, or the like, with one or more devices that allow a user to interact with the electronic device 900, or with any device that allows the electronic device 900 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0145] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0146] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0147] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0148] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0149] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0150] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for task management, comprising: receiving a creation instruction for a target task in a target application; Based on the creation instruction, determining task creation information of the target task, the task creation information at least indicating a trigger condition and at least one function required to execute the target task in the target application; as well as Based on the task creation information, the target task is created for one or more users in the target application.

2. The method according to claim 1, further comprising: In response to a trigger condition of the target task being met, using the at least one function to execute the target task; as well as Providing a prompt of the execution result of the target task to the one or more users.

3. The method according to claim 2, wherein utilizing the at least one function to perform the target task comprises: In response to a trigger condition of the target task being met, the at least one function provides information related to the target task to the machine learning model; obtaining an output of the machine learning model; and The execution result of the target task is determined based on the output of the machine learning model.

4. The method of claim 1 , wherein receiving the creation indication comprises: receiving a user input represented by natural language from a terminal user of the target application, wherein the user input includes a creation instruction for the target task; and Determining the task creation information includes: The task creation information is determined based on the user input using a machine learning model.

5. The method of claim 1 , wherein receiving the creation indication comprises: receiving a creation instruction for the target task from an application creator of the target application; and Wherein determining the trigger condition and the at least one function comprises: In response to the creation instruction, providing a task creation page, and The task creation information of the target task is received via the task creation page.

6. The method according to claim 1, wherein the task creation information further indicates at least one of the following: The name of the target task, The type of the target task, the one or more users to which the target task is directed, A method for providing a prompt of the execution result of the target task.

7. The method according to claim 1, further comprising: Present corresponding task information of multiple tasks created in the target application, wherein the first The task information of a task indicates at least one of the following: the type of the first task, The functionality required by the first task, the execution frequency of the first task, time information of the first task, The creator of the first task.

8. The method according to claim 7, further comprising: receiving a history viewing request for a second task among the plurality of tasks; as well as In response to the history viewing request, the execution record of the second task is presented. The method of claim 8 , wherein the execution record comprises a log of the second task.

10. The method according to claim 1, further comprising: In response to receiving a trigger for immediate execution of the target task that has been created in the target application, the target task is executed regardless of whether a trigger condition of the target task is satisfied.

11. The method according to claim 1, wherein the trigger condition comprises at least one of the following: Time-based trigger conditions, A trigger condition based on at least one rule.

12. The method according to claim 11, wherein the at least one rule comprises at least: The data object associated with the target task is updated.

13. The method according to claim 1, further comprising: receiving a deletion request or an update request for the target task; as well as The target task is deleted or updated based on at least one of the authority of the user who initiates the deletion request or the update request and the execution status of the target task.

14. The method of claim 13, wherein the user initiating the deletion request or the update request comprises an end user of the target application, and wherein executing the deletion or update of the target task comprises: Deleting or updating the target task is performed based on at least one of the following: Whether the terminal user is the creator of the target task, Whether the execution status of the target task is in the executing state.

15. A device for task management, comprising: An instruction receiving module is configured to receive a creation instruction for a target task in a target application; an information determination module, configured to determine task creation information of the target task based on the creation instruction, wherein the task creation information at least indicates a trigger condition and at least one function required to execute the target task in the target application; as well as The task creation module is configured to create the target task for one or more users in the target application based on the task creation information.

16. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 14 when executed by the at least one processing unit.

17. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 14.

Images