RU2774320C2 - Device and method for simplifying the re-execution of a previously performed task based on the context of a mobile device - Google Patents

Abstract

FIELD: mobile communications.

SUBSTANCE: invention relates to the performance of tasks in the application. The result is achieved due to the fact that the use of the application to perform the task using a mobile device is monitored, the configuration parameters of the task are determined through the UI associated with the use of the application, the context of the mobile device is identified, including one or more mobile device conditions under which the application was activated to perform the task, the current context of the mobile device the device is monitored, including one or more conditions under which the mobile device is functioning, and the relevance between the context and the current context is determined, in response to a certain relevance, the mobile UI is presented through a mobile device to ensure the repetition of the task with configuration parameters without activating at least one of the UI associated with the use of the application.

EFFECT: ensuring that the previously performed task can be repeated in the application based on the current context of the mobile device.

17 cl, 14 dwg

Description

RELATED APPLICATION

[0001] This application is a division of Patent Application 2020117419, filed May 27, 2020, which is a national phase translation of International Patent Application PCT/CN2018/109873, filed October 11, 2018, which claims priority to U.S. Non-Provisional Application No. 15/798,013, filed October 30, 2017, titled “apparatus and method for simplifying repeat performance of a prior performed task based on a context of a mobile device”, which are included to this document by reference, as if reproduced in its entirety.

FIELD OF TECHNOLOGY TO WHICH THE INVENTION RELATES

[0002] The present invention relates to the execution of tasks in an application and, in particular, to user interfaces (UIs) that make application tasks available to users to initiate their execution.

State of the art

[0003] Typically, when a user of a mobile device wants to perform a specific task in an application, the user must navigate (navigate) the user interfaces dedicated to the application to access the specific application user interface through which the user can configure and run the task. . For example, the user may need to first select an icon in the mobile user interface of the mobile device that represents the application in order to first open the user interface of the application's home page on the user's mobile device. The user may then be required to select a menu item or link in the home page user interface to navigate to a specific application user interface through which the user can configure and run the task. This menu item or link selection may also need to be repeated for multiple application UIs to navigate to a specific application UI through which the user can configure and run a task.

[0004] Thus, the user typically has to repeat the aforementioned navigation through the application's user interfaces whenever the user wants to run a task. In addition, even when a user wishes to repeat a task with the same configuration, he may be required to enter configuration information for the task through a particular user interface before starting the task.

SUMMARY OF THE INVENTION

[0005] An apparatus is provided for enabling a previously completed task to be repeated in an application based on the current mobile device context. It includes a long-term storage containing instructions and one or more processors interacting with said memory, the one or more processors executing instructions to monitor the use of an application to perform a task via a mobile device. The one or more processors further execute instructions for determining task configuration parameters via user interfaces (UIs) associated with the use of the application, the task being executed with the configuration parameters set in accordance with the UI. The one or more processors further execute instructions to identify a mobile device context, the context including one or more mobile device conditions under which the application has been activated to perform a task by the mobile device user. The one or more processors further execute instructions for keeping track of the current context of the mobile device, the current context including one or more conditions under which the mobile device is operating, and determining the relevance between the context and the current context. Additionally, one or more processors execute instructions to present, in response to the determined relevance, the mobile UI via the mobile device, so that the mobile UI causes the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

[0006] A machine-implementable method is also provided for enabling a previously completed task in an application to be re-executed based on the current context of the mobile device. Monitors the use of the application to complete a task through a mobile device. Task configuration parameters are determined via user interfaces (UIs) associated with the use of the application, and the task is executed with the configuration parameters specified in accordance with the UI. A mobile device context is identified, the context including one or more mobile device conditions under which the application was activated to perform a task by the mobile device user. The current context of the mobile device is tracked, wherein the current context includes one or more conditions under which the mobile device operates, and the relevance between the context and the current context is determined. In response to the determined relevance, the mobile UI is presented via the mobile device so that the mobile UI allows the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

[0007] Additionally, a durable computer-readable medium is provided that stores computer instructions that, when executed by one or more processors, cause one or more processors to perform steps to enable the application to re-execute a previously performed task based on the current mobile device context. The steps include monitoring the use of an application to complete a task via a mobile device. The steps further include determining task configuration parameters via user interfaces (UIs) associated with using the application, wherein the task is executed with the configuration parameters set in accordance with the UI. The steps further include identifying a mobile device context, the context including one or more mobile device conditions under which the application has been activated to perform a task by the mobile device user. The steps include keeping track of the current context of the mobile device, where the current context includes one or more conditions under which the mobile device is operating, and determining the relevance between the context and the current context. Additionally, the steps include presenting, in response to the determined relevance, the mobile UI via the mobile device, such that the mobile UI is configured to repeat the task with the configuration parameters without activating at least one of the UIs associated with using the application.

[0008] Optionally, in any of the previous embodiments, the application is a mobile application installed on a mobile device.

[0009] Optionally, in any of the previous embodiments, the application is one of: a messaging application, a media player, a convenience store, and a travel booking application.

[0010] Optionally, in any of the previous embodiments, the UIs associated with using the application are the UIs of the application that the user navigates to set the configuration settings and start executing the task with the configuration settings.

[0011] Optionally, in any of the previous embodiments, the task indication is stored with the configuration parameters and the mobile device context in a profile for the user, where the user profile is accessed to identify the context to determine the relevance between the context and the current mobile device context.

[0012] Optionally, in any of the previous embodiments, the mobile device context includes one of: the location of the mobile device and the time specified by the mobile device.

[0013] Optionally, in any of the previous embodiments, determining the relevance between the context and the current context includes determining whether the current context is within a predetermined threshold difference with the context, and when the current context is within a predetermined threshold difference with context, the mobile UI is presented through the mobile device.

[0014] Optionally, in any of the previous embodiments, the mobile user interface is presented on the home screen of the mobile device.

[0015] Optionally, in any of the previous embodiments, the mobile UI presented via the mobile device is an icon that, when selected by the user, causes the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

[0016] Optionally, in any of the previous embodiments, the use of the additional application is monitored to perform an additional task via a mobile device, the configuration parameters of the additional task are determined through additional user interfaces (UI) associated with the use of the additional application, while the additional task is executed with configuration parameters set in accordance with additional UI. Further, an additional mobile device context is identified, the additional context including one or more mobile device conditions under which the additional application has been activated to perform the additional task by the mobile device user. In addition, additional relevance between the additional context and the current context is determined. Additionally, in conjunction with the mobile UI and in response to certain additional relevancy, the additional mobile UI is presented via the mobile device so that the additional mobile UI allows the additional task to be repeated with the configuration parameters of the additional task without activating at least one of the additional UIs associated with the use of the additional application. .

[0017] To this end, in some optional embodiments, one or more of the aforementioned features of the aforementioned device and/or method may facilitate re-execution of a previously performed task based on the current context of the mobile device. In particular, a specific mobile UI providing repetition of the same previously performed task may only be provided if the task is relevant to the current mobile device context. This can ensure that the mobile UI intended for this task is presented to the user at the appropriate time. In addition, by presenting the mobile UI to allow repetition of the same previously completed task, the user can start a repetition of the same previously completed task without having to use one or more or all of the application's user interfaces again to configure and/or start the task. In this way, the mobile UI can simplify the actions a user must take to repeat a task. It should be noted that the aforementioned potential benefits are for illustrative purposes only and should not be construed as limiting in any way.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] FIG. 1 illustrates a method for enabling a previously completed task in an application to be re-executed based on the current mobile device context, in accordance with one embodiment.

[0019] FIG. 2A illustrates a system for enabling a previously completed task in an application to be re-executed based on the current mobile device context, in accordance with one embodiment.

[0020] FIG. 2B illustrates a mobile device architecture including a recommender application for enabling the application to re-execute a previously performed task based on the current context of the mobile device, in accordance with one embodiment.

[0021] FIG. 3 illustrates an interaction diagram including inputs and outputs of a recommender application that enables a previously performed task to be reexecuted in a user application, in accordance with another embodiment.

[0022] FIG. 4 illustrates a mobile device home screen presenting mobile user interfaces to enable repetition of previously performed tasks that are relevant to the current context of the mobile device, in accordance with another embodiment.

[0023] FIG. 5 illustrates a recommender user interface that provides details on one of the mobile user interfaces of FIG. 4 in accordance with another embodiment.

[0024] FIG. 6 illustrates a dynamic user profile in accordance with another embodiment.

[0025] FIG. 7 illustrates a flowchart for monitoring the use of a user application to perform a task, in accordance with another embodiment.

[0026] FIG. 8 illustrates an interaction diagram including inputs and outputs of a recommender application that enables re-execution of a previously completed task in a user application associated with a web service, in accordance with yet another embodiment.

[0027] FIG. 9 illustrates a flowchart of a use case for enabling a previously performed task in a user application to be reexecuted based on the current mobile device context, in accordance with one embodiment.

[0028] FIG. 10 illustrates a flowchart of a use case for enabling a previously performed task in a user application to be reexecuted based on the current mobile device context, in accordance with one embodiment.

[0029] FIG. 11 illustrates a flowchart for enabling a previously performed task in a user application to be reexecuted based on the current mobile device context, in accordance with one embodiment.

[0030] FIG. 12 is a diagram of a network architecture in accordance with one embodiment.

[0031] FIG. 13 is a diagram of an exemplary system in accordance with one embodiment.

DETAILED DESCRIPTION

[0032] FIG. 1 illustrates a method 100 for enabling a previously completed task in an application to be reexecuted based on the current mobile device context, in accordance with one embodiment. In one embodiment, method 100 may be performed by a mobile device. For example, method 100 may be performed with a recommender application installed and running on a mobile device, such as the recommender described in more detail below with reference to the following figures.

[0033] As shown in step 102, the use of an application to perform a task via a mobile device is monitored. In the context of the present description, the application is separate from the recommended application mentioned above. In one embodiment, the application may be a mobile application (eg, a third party application) or a system application installed on a mobile device. In another embodiment, the application may be a web application located in the cloud remote from the mobile device, where the ability to use the web application to perform a task through the mobile device is provided using a network.

[0034] In some exemplary embodiments, an application may be a messaging application (eg, email, short message service (SMS), etc.), a media player (eg, for playing video and/or audio), a shopping a service business (for example, to purchase products and/or services), a travel booking application (for example, to book a trip), etc. Thus, it is possible to observe the use of these applications for various tasks such as sending a message, playing media, making a purchase, booking a trip, etc.

[0035] In addition, as shown in step 104, the configuration parameters of the task are determined through the user interfaces (UI) associated with the use of the application, and the task is executed with the configuration parameters set in accordance with the UI. In particular, the user may set configuration parameters for the task through the UI associated with the use of the application, and the task may be performed with these specified configuration parameters. The configuration parameters may be determined by monitoring the use of the application described in relation to step 102.

[0036] In one embodiment, UIs associated with using an application may be application user interfaces that a user navigates (navigates) to set configuration parameters for a task and optionally trigger execution of a task with configuration parameters. The configuration parameters may be entirely dependent on the task itself and may be entered by the user through configurable parameters, settings, etc. included in the user interfaces to allow the user to customize the operation of the task.

[0037] For example, when the application is a trip booking application and the task is to book taxi services, the configuration parameters may include pickup location, pickup time, drop off location, type of vehicle being booked, and so on. As another example, when the application is a messaging application and the task sends a message (eg, an SMS message), the configuration parameters may include a message recipient ID, and so on. As another example, when the application is a media player and the task is to play a video, the configuration parameters may include selecting a particular video to play.

[0038] In addition, as shown at 106, a mobile device context is identified, the context including one or more mobile device conditions under which the application was activated to perform a task by the mobile device user. Thus, the mobile device context may be identified at the same time that the application was activated to perform a task by the mobile device user, and may optionally be identified in conjunction with monitoring application usage described with respect to step 102.

[0039] As noted above, the mobile device context that is identified includes one or more mobile device conditions. These conditions may be specific types that the method 100 has been pre-configured to identify. For example, the types of conditions to be identified may include the location of the mobile device, the time of day, the day of the week, the concurrent use of additional applications, the role of the user using the mobile device, and so on. With respect to these examples, one or more conditions of the mobile device under which the application was activated to perform a task may include the specific location of the mobile device when the application was activated to perform the task, the time of day and/or day of the week specified by the mobile system. devices when the application was activated to perform a task, additionally applications used via a mobile device (eg by a user) when an application was activated to perform a task, etc.

[0040] Optionally, once the task execution, configuration parameters for the task, and associated mobile device context are identified in steps 102-106, method 100 may store a task indication with configuration parameters and mobile device context in a profile for the user. The profile may be dynamic in the sense that the profile may be updated to store the above information after it has been identified. In addition, the profile may be located in the local memory of the mobile device.

[0041] However, as shown at step 108, the current context of the mobile device is tracked, and the current context includes one or more conditions under which the mobile device operates. In particular, the current context may be tracked to identify, at a point in time after the application has been used to perform a task, as noted at step 102, one or more conditions under which the mobile device is operating. These conditions may be of the same type as described above with respect to step 106, and in particular, method 100 may be pre-configured to monitor these types of conditions under which the mobile device operates. To this end, at the output of step 108, one or more conditions under which the mobile device operates can be identified.

[0042] In addition, as shown at step 110, the relevance between the context and the current context is determined. Optionally, if the context has been stored in the user's profile, the user's profile may be accessed to identify the context to determine the relevance between the context and the current context of the mobile device. Of course, the context can be identified or retrieved from any storage location to determine its relevance to the current context of the mobile device.

[0043] It should be noted that relevance can be determined using any desired algorithm or computer process capable of comparing context and current context to determine that there is a predetermined degree of similarity between context and current context. For example, in one embodiment, determining the relevance between the context and the current context may include determining that the current context is within a predetermined threshold difference with the context.

[0044] In addition, as shown in step 112, in response to a certain relevance, the mobile UI is presented through the mobile device so that the mobile UI allows the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application. For example, the mobile UI may be an icon that, when selected by the user, causes a task to be repeated with configuration parameters. Thus, a re-execution of a task with configuration parameters can be initiated by the user through the mobile UI and thus without the user activating (eg, opening, accessing, interacting, etc.) at least one or all of its associated user interfaces. associated with the use of the application.

[0045] For example, a user may initially configure and start a task by using the UI associated with the application (eg, by opening, accessing, and interacting with the UI). This usage can be observed at step 102. The mobile UI can then, when presented at step 112, act as a shortcut to the task with configuration parameters so that the user can start the task via the mobile UI instead of having to use at least one again. or all of the UIs associated with the application.

[0046] In one embodiment, a mobile UI may be presented on a home screen (UI) of a mobile device. Of course, the mobile UI can be presented on any other screen (UI) that is different from the UI associated with using the application. Accordingly, the mobile UI may optionally be presented without activating any of the application's user interface (i.e., any user interface included as part of the application), and in any case may allow the user to repeat a certain task without having to navigate through the same user interfaces again. application interfaces associated with the previous execution of the task.

[0047] To this end, in some optional embodiments, one or more of the aforementioned features of the aforementioned device and/or method may enable a previously performed task in the application to be reexecuted based on the current mobile device context. In particular, as described above, a specific mobile UI for repeating the same previously completed task (without re-traversing the application's user interfaces) can only be provided if it is relevant to the current mobile device context. This can ensure that the mobile UI intended for this task is presented at the appropriate time for the user. In addition, by presenting the mobile UI to allow the same previously completed task to be repeated, the user can start a repetition of the same previously completed task without having to use the application's user interfaces again to configure and/or start the task. It should be noted that the aforementioned potential benefits are for illustrative purposes only and should not be construed as limiting in any way.

[0048] In addition, in some embodiments, the implementation of the method 100 can be repeated for many different applications. For example, the use of an additional application to perform an additional task via a mobile device may be monitored (eg, as described above in relation to step 102). In addition, additional task configuration parameters may be defined via additional user interfaces (UIs) associated with the use of the additional application, wherein the additional task is executed with the configuration parameters set in accordance with the additional UIs (for example, as described above with respect to step 104). In addition, an additional mobile device context may be identified, where the additional context includes one or more mobile device conditions under which the additional application has been activated to perform an additional task by the mobile device user (e.g., as described above in relation to step 106) , and additional relevance between the additional context and the current context can be determined (eg, as described above in relation to step 108). Further, in response to certain additional relevancy, the additional mobile UI may be presented via the mobile device in conjunction with the mobile UI presented in step 110 so that the additional mobile user interface allows the additional task to be repeated with the additional task configuration parameters without activating at least one of the additional UIs associated with the use of the additional application (eg, as described above with respect to step 110).

[0049] More illustrative information will now be set forth regarding various optional architectures and applications in which the aforementioned method 100 may or may not be implemented in accordance with the desires of the user. For example, various embodiments will be described that can further enhance the aforementioned method 100 to enable re-execution of a previously performed task in an application based on the current mobile device context.

[0050] FIG. 2A illustrates a system 200 for allowing a previously completed task to be re-executed in an application based on the current mobile device context, in accordance with one embodiment. Optionally, system 200 may be implemented with one or more features of any one or more of the embodiments set forth in any previous and/or subsequent drawing(s) and/or description thereof. However, it should be understood that system 200 may be implemented in other suitable environments.

[0051] As shown, the application usage monitor in the form of the application usage monitor 202 is for monitoring the usage of the application to perform a task through the mobile device, to determine the configuration parameters of the task through the user interfaces (UIs) associated with the usage of the application, when In this case, the task is executed with the configuration parameters specified in accordance with the user interfaces and to identify the context of the mobile device, wherein the context includes one or more mobile device conditions under which the application was activated to perform the task by the user of the mobile device (for example, see steps 102-106 in Fig. 1). In various embodiments, application usage monitoring module 202 may include, but is not limited to, at least one processor (to be described below) and any software controlling it, and/or any other circuitry implemented with the above functionality.

[0052] Also included is a relevancy determiner in the form of a relevancy determination module 204 associated with the application usage monitoring module 202 for keeping track of the current context of the mobile device, the current context including one or more conditions under which the mobile device is operating, and for determining relevance between the context and the current context (eg, see steps 108-110 in FIG. 1). In various embodiments, the relevance determination module 204 may include, but is not limited to, at least one processor (to be described below) and any software controlling it, and/or any other circuit implemented with the above functionality.

[0053] Further included is a mobile UI presenter in the form of a mobile UI presenter 206 associated with a relevancy determination module 204 for presenting, in response to a certain relevance, a mobile UI via a mobile device, so that the mobile UI allows the task to be repeated with the configuration parameters without activation of at least one of the UI associated with the use of the application (for example, see step 112 in Fig.1). In various embodiments, the relevance determination module 204 may include, but is not limited to, at least one processor (to be described below) and any software controlling it, and/or any other circuit implemented with the above functionality.

[0054] More information will now be set forth regarding one possible example of the various inputs/outputs of the various components described above.

[0055] FIG. 2B illustrates the architecture of a mobile device 250 having an intelligent offline content manager for managing offline (offline) accessibility to online content, in accordance with one embodiment. Optionally, mobile device 250 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or description thereof.

[0056] In the illustrated embodiment, mobile device 250 includes means in the form of mobile device components, which are described below. In various embodiments, components may include, but are not limited to, at least one processor (to be described later) and any software that manages the same, memory, and/or any other circuit implemented with the functionality described herein. .

[0057] The mobile device 250 may be any of the user devices described below with reference to FIGS. 12 and 13. As shown, the components of the mobile device 250 include a recommender application 252. The recommender application 252 is software that runs on a mobile device. device 250 for performing the method 100 of FIG. For example, recommender application 252 may include the modules described above with reference to FIG. 2A. The mobile device 250 may be configured to execute the recommender application 252 automatically when the mobile device is powered on, or the mobile device 250 may be configured to execute the recommender application 252 at the command of the user of the mobile device 250.

[0058] The components of mobile device 250 further include user applications 254A-N, each of which can be used by a user of mobile device 250 to perform a task as described above with respect to method 100 of FIG. For example, user applications 254A-N include user interfaces with which a user can set configuration parameters for a task and can run a task with the specified configuration parameters. In response to starting a task via the UI of one of the user applications 254A-N, the user application 254A-N may then execute the task in accordance with the specified configuration parameters.

[0059] It should be noted that although user applications 254A-N are shown in the present embodiment as components of mobile device 250, other embodiments are contemplated in which one or more user applications 254A-N can be installed, and executed, in an environment cloud computing (eg, on a server located remotely from mobile device 250). In one embodiment, where one or more user applications 254A-N are running in a cloud computing environment, mobile device 250 may include components that are interfaces (eg, user interfaces, APIs, web interfaces, etc.) for these remotely located user applications 254A-N.

[0060] As further shown, the components of mobile device 250 include a repository 256 that stores a user profile. Repository 256 may be a database, a text file, or any other memory location capable of storing structured data representing a user profile. As shown, the user profile specifies specific tasks performed by user applications 254A-N and may include configuration parameters set for these tasks by the user. As also shown, for each specified task, the user profile stores the corresponding mobile device context 250 in which the mobile device was activated to perform the task.

[0061] To this end, the user profile may store a history of previous tasks launched by the user using user applications 254A-N, along with the corresponding context of the mobile device 250. Recommender application 252 may be configured to monitor the use of user applications 254A-N by the user through mobile device 250 (i.e., to identify the tasks performed by these user applications 254A-N and the user-specified configuration parameters of those tasks) and can be further configured to track the context of the mobile device 250 (i.e., to identify the specific context in which each task was completed). The recommender application 252 may then store the identified tasks with the appropriate configuration settings and the appropriate mobile device context in the user's profile.

[0062] In another embodiment, the user profile may also store a history of previous tasks launched by other users, possibly via other mobile devices (not shown), particularly when one or more user applications 254A-N are running in the cloud computing environment mentioned above. In this embodiment, other mobile devices may be configured in the same manner as shown in the present system 250 and thus may function in the same manner as disclosed herein. Other mobile devices can then share with the mobile device 250 of the present disclosure (via a network) the contents of their user profiles (ie, the history of previous tasks started by other users).

[0063] FIG. 3 illustrates an interaction diagram 300 including recommender application inputs and outputs that enables the user application to re-execute a previously completed task in accordance with another embodiment. Optionally, interaction scheme 300 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or description thereof.

[0064] As shown, the recommending application 302 makes content and services 304 available to the user 312 through the user applications 305. The content may be web content such as video, news, music, etc., and/or content stored locally on the user's mobile device, such as contact information. In addition, the services may be a web service such as a travel booking service and/or a service that may be provided locally by the user's mobile device. In addition, the user applications 305 in the examples shown include a phone call application, a messaging application, and a taxi service application.

[0065] The recommender application 302 allows the user 312, through the user's mobile device, to repeat a specific task in these user applications 305 to access content and services 304 as described above with reference to the previous FIGS. 1-2. The recommender application 302 defines tasks 308A-C with specific configuration parameters that have previously been performed through the user applications 305 and that are relevant to the user 312's current mobile device context in order to recommend those tasks 308A-C to the user 312. The recommender application 302 then presents for each of the tasks 308A-C mobile UI to ensure the repetition of task 308A-C. The mobile UI is distinct from user interfaces otherwise associated with the use of user applications 305.

[0066] In the specific examples shown, the recommender application 302 determines, based on the current context of the mobile device (eg, time of day, etc.), to recommend to the user 312 the first task 308A of the first user application of the user applications. 305 where the first task 308A is to make a phone call to a specific contact. As an example, the recommender application 302 may determine that the user 312 regularly performs the first task 308A during a specific period of time on a specific day of the week. Thus, on that particular day of the week and for a particular period of time, the recommending application 302 may recommend the first task 308A to the user 312.

[0067] The first task 308A is recommended by being presented by the recommending application 302 to the user 312 via the first mobile UI. The first mobile UI may be presented on the home screen of the mobile user interface in one embodiment. When the user 312 selects the first mobile UI presented by the recommender application 302 via the mobile device, the first task 308A is automatically started in the first user application.

[0068] In the illustrated embodiment, running the first task 308A in the first user application includes allowing the user 312 to provide the first input 310A, namely the selection of the contact's phone number stored by the mobile device and needed to perform the first task 308A. Once the first input 310A is provided, the first task 308A may be performed by the mobile device through the first user application. Of course, as another option, the first task 308A could be started automatically without the need for any additional input from the user 312, so that after the user 312 selects the first mobile UI, the mobile device can make a phone call to a specific contact. In any case, the use of the first mobile user interface by the user 312 to perform the first task 308A allows the user 312 to bypass navigating the first user application, including the initial user interface 306A of the first user application, to launch the first task 308A.

[0069] In another specific example shown, the recommender application 302 determines, based on the current mobile device context (e.g., time of day, etc.), to recommend to the user 312 the second task 308B of the second user application of the user applications 305, where the second task 308B is to send a message to a specific contact. As an example, recommender application 302 may determine that user 312 regularly performs second task 308B during a specific time period on a specific day of the week. Thus, on that particular day of the week and for a certain period of time, recommender application 302 may recommend second task 308B to user 312.

[0070] The second task 308B is recommended by being presented by the recommending application 302 to the user 312 via the second mobile UI. The second mobile UI may be presented on the home screen of the mobile user interface (eg, with the first mobile user interface) in one embodiment. When the user 312 selects the second mobile UI represented by the recommender application 302 via the mobile device, the second task 308B is automatically started in the second user application.

[0071] In the illustrated embodiment, starting a second task 308B in a second user application includes allowing the user 312 to provide a second input 310B, namely content (eg, text) needed to perform the second task 308B. Once the second input 310B is provided, the second task 308B can be performed by the mobile device via the second user application. Of course, as another option, the second task 308B can be automatically started without the need for any further input by the user 312, so that after the user 312 selects the second mobile UI, the mobile device can send a message to a specific contact with the content specified through the predefined configuration parameters for the second tasks 308B. In any case, the use of the second mobile user interface by the user 312 to perform the second task 308B allows the user 312 to bypass navigating the second user application, including the initial user interface 306B of the second user application, to start the second task 308B.

[0072] In yet another specific example shown, the recommender application 302 determines, based on the current mobile device context (e.g., time of day, etc.), to recommend to the user 312 the third task 308C of the third user application of the user applications 305, where the third task 308C is a taxi booking service. As an example, the recommender application 302 may determine that the user 312 regularly performs the third task 308C during a specific period of time on a specific day of the week. Thus, on that particular day of the week and for a particular period of time, recommender application 302 may recommend third task 308C to user 312.

[0073] The third task 308C is recommended by being presented by the recommending application 302 to the user 312 via the third mobile user interface. A third mobile UI may be presented on a mobile user interface home screen (eg, with a first and/or second mobile user interface) in one embodiment. When the user 312 selects the third mobile UI represented by the recommender application 302 via the mobile device, the third task 308C is automatically launched in the third user application.

[0074] In the illustrated embodiment, running a third task 308C in a third user application includes allowing the user 312 to provide a third input 310C, namely the desired vehicle type required to complete the third task 308C. Once the third input 310C is granted, the third task 308C may be performed by the mobile device via the third user application. Of course, as another option, the third task 308C can be automatically started without the need for any additional input from the user 312, so that after the third mobile UI is selected by the user 312, the mobile device can make a booking for a taxi service using the vehicle type specified using the predefined configuration parameters. parameters for the third task 308C. In any case, the use of the third mobile user interface by the user 312 to perform the third task 308C allows the user 312 to bypass navigation through the third user application, including the initial user interface 306C of the third user application, to start the third task 308C.

[0075] FIG. 4 illustrates a mobile device home screen 400 presenting mobile user interfaces for enabling repetition of previously performed tasks that are relevant to the current mobile device context, in accordance with another embodiment. Optionally, the initial screen 400 may be implemented in the context of any one or more of the embodiments set forth in any previous and/or subsequent figure(s) and/or their description. For example, the home screen 400 may represent the mobile user interfaces described above with reference to FIG.

[0076] As shown, the home screen 400 of the mobile device presents exemplary user interfaces 402 or selectable icons for a variety of user applications available through the mobile device. The mobile device may be installed (and thus executable) on the user device, or may be a web application executed in the cloud by being launched by the user device. In the examples shown, exemplary user interfaces 402 are for the messaging app, phone app, internet browser, e-mail app, and a user interface for accessing additional (not shown on home screen 400) exemplary user interfaces for other user applications.

[0077] The user of the mobile device can access user applications for use through exemplary user interfaces 402. In particular, when the user of the mobile device selects one of the representative UIs 402, the mobile device presents the user with the home page UI of the presented user application. The user can then navigate from the home page user interface to the task specific user interface of the presented user application to configure and run the specific task. This movement may be similar to that described above with respect to Figure 3, which was bypassed when the user accesses the task through the mobile UI presented through the recommender application.

[0078] As also shown, the mobile device home screen 400 presents mobile user interfaces 404 corresponding to a set of tasks (with predefined configuration parameters) that are recommended by the recommending application based on the current context of the mobile device. When the user of the mobile device selects one of the mobile UI 404, the mobile device launches the corresponding task through the corresponding user application. Mobile user interfaces 404 thus differ from typical user interfaces 402 for user applications and may be presented by a recommender application on the home screen 400 of the mobile device. In the examples shown, mobile user interfaces 404 may provide for initiating tasks such as calling a specific contact, sending a message to a specific contact, booking a taxi service, and playing a music playlist.

[0079] FIG. 5 illustrates a recommender user interface 500 that provides details about one of the mobile user interfaces 404 of FIG. 4 in accordance with another embodiment. The recommender user interface 500 may be presented via a mobile device when a user of the mobile device right-clicks on one of the mobile interfaces 404 to display a dropdown menu and selects an item from the dropdown menu to view the recommender user interface 500. The recommender user interface 500 provides information about the task presented by the mobile user interface 404 selected by the user.

[0080] The information may include the conditions under which the mobile device is operating that dictated the presentation of the mobile UI 404. The information may also include set configuration parameters for the task. In addition, the information may include alternative configuration parameters for the task, which may be selected by the user.

[0081] In the example shown, when a mobile device user right-clicks on the mobile UI 404 of FIG. 4, which represents a specific taxi booking task, and selects an item from the resulting drop-down list to view the recommending user interface 500 for the specific task , then the recommending UI 500 is presented via the mobile device. This recommender UI 500 provides information about the taxi booking task, indicating the conditions 502 under which the mobile device is operating, which mandated the presentation of the mobile UI 404.

[0082] The information provided by the recommender user interface 500 also indicates the configuration parameters 504 for the task. These configuration parameters include the configured task configuration parameter (i.e., which, in this example shown, is the first taxi service or service provider recommended via the mobile interface 404), as well as the alternative task configuration parameter (i.e., which in the present example shown is the second taxi service (or service provider) that the user can select via the recommending user interface 500 as an alternative to the configuration parameter set. %) for the installed and alternative configuration settings, where the trust scores are based on the amount that the corresponding configuration settings have been used by the user in the past for a given task (and possibly other users) and/or the availability of web services required by the user application zheniya to complete the task. The set configuration parameter may be a configuration parameter with a higher trust rating, while the alternative configuration parameter may be a configuration parameter with a lower trust rating.

[0083] FIG. 6 illustrates a dynamic user profile 600 in accordance with another embodiment. Optionally, dynamic user profile 600 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or description thereof. For example, a dynamic user profile 600 may be generated or otherwise received by the recommender application.

[0084] As shown, a dynamic user profile 600 is generated from various inputs that can be identified by monitoring a variety of different data sources through a mobile device. Thus, the entries in the dynamic user profile 600 shown in element 256 in FIG. 2B can be derived from the original data. The dynamic user profile 600 may be continuously or periodically updated based on new data from these different sources. In addition, although the original data is described with reference to the user for whom the dynamic user profile 600 is created, other embodiments are contemplated in which the original data can also be collected based on the actions of other users.

[0085] In one embodiment, the source data may include the use of a telephone application. For example, a dynamic user profile 600 may store an indication of the tasks that the phone application was previously activated to perform by the user, as well as the configuration settings for those tasks set by the user, and further, the mobile device context in which the tasks were performed. These tasks may include, for example, making phone calls to specific contacts.

[0086] In another embodiment, the source data may include content sharing patterns. For example, a dynamic user profile 600 may store an indication of the tasks that content sharing applications (eg, social networking applications) were previously enabled by the user to perform, as well as the configuration settings for those tasks set by the user, and optionally the mobile device context under which the tasks. These tasks may include sharing (e.g. posting, transmitting, etc.) content for access to specific groups of users (e.g. via Facebook, etc.) or for access by specific users (e.g. via SMS, WeChat etc.), for example.

[0087] In yet another embodiment, the source data may include browsing history. For example, a dynamic user profile 600 may store an indication of the tasks that the user has previously activated with an Internet browser, as well as the configuration settings for those tasks set by the user, and, in addition, the mobile device context under which the tasks were performed. These tasks may include, for example, accessing specific web pages.

[0088] In another embodiment, the input data includes usage of app notifications, app install/uninstall actions, and app placement and screen position. For example, the dynamic user profile 600 may weight the aforementioned tasks differently based on these inputs. The weights can then be used to prioritize which tasks are recommended to the user through the recommender application. As an example, tasks performed through user applications having a distinctive user interface on the home screen of the mobile device, as described with reference to FIG. 4, can be given more weight than other user applications without a distinctive user interface on the home screen of the mobile device. . As another example, tasks for user applications that have been removed from the mobile device may be removed from the user's dynamic profile 600. As another example, when a user configures a mobile device to provide notifications of specific activity in specific user applications (e.g., inboxes, etc.), then the tasks of those specific user applications can be given a higher weighting factor than those of other applications. .

[0089] FIG. 7 shows a flowchart 700 for monitoring the use of a user application to perform a task, in accordance with another embodiment. Optionally, flowchart 700 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or description thereof. For example, flowchart 700 may be implemented to store information in dynamic user profile 600 of FIG.

[0090] As shown, a mobile device user 702 can access an application map 704 present on the mobile device to perform a user application task 706. Application card 704 may be a third-party application user interface that statically represents a task 706 for the user to select to activate the user application to present an application user interface for use by the user when configuring and running task 706. For example, application card 704 may be presented on the home screen of a mobile device or on any other screen of the mobile device, as configured by the user.

[0091] In another embodiment, the user 702 may perform the task 710 through a notification 708 generated and presented by the mobile device. For example, the mobile device may be configured by the user to generate and present a notification for a particular user application activity, such as a message received via a messaging application. User 702 can select a notification to open a user application user interface that allows the user to configure and run task 710.

[0092] In yet another embodiment, the user 702 may perform task 710 via the user application homepage UI 712. For example, the user 702 may select a typical user interface for the user application to open the user interface 712 of the user application home page. The user can then navigate through the user application user interfaces to open the user application user interface described above, which allows the user to configure and run task 710.

[0093] When a task 706, 710 is executed, information indicating the task is stored in the dynamic user profile 714. This information may include an indication of the task, configuration parameters for the task, and the context of the mobile device under which the task was performed. Optionally, an indication of which user interface 704, 708, 712 was used to run the task may also be specified in the dynamic user profile 714, for example, to determine the weight of the task for prioritization purposes.

[0094] FIG. 8 illustrates an interaction diagram 800 including inputs and outputs of a recommender application that enables re-execution of a previously performed task in a user application associated with a web service, in accordance with yet another embodiment. Optionally, interaction scheme 800 may be implemented in the context of any one or more of the embodiments set forth in any previous and/or subsequent figure(s) and/or description thereof. For example, interaction scheme 800 may be implemented through a mobile device and a cloud computing environment.

[0095] As shown, a recommender application 802 running on a mobile device receives input from the mobile device in the form of data from the dynamic user profile 804 as well as the current mobile device context. In one embodiment, the recommender application 802 can search the dynamic user profile 804 using the current mobile device context to determine if any task specified in the dynamic user profile 804 is relevant to the current mobile device context.

[0096] The recommending application 802 also receives input from the cloud computing environment, and in particular from the service provider proxy 808 indicating the availability of various services provided by various service providers 810A-C through the cloud computing environment and through which certain a task. In one embodiment, for tasks identified by recommender application 802 as relevant to the current mobile device context, recommender application 802 can query service provider proxy 808 for service availability from different service providers 810A-C through which the task can be performed.

[0097] Based on the service availability indication received by the recommending application 802 from the service provider proxy 808, the recommending application 802 determines a trust score 812 for the various services through which the task can be performed. The trust score may also be determined based on other information indicated by the user's dynamic profile 804, such as the degree of relevance of the task to the current mobile device context, the frequency with which the user has used various services to complete the task, and/or the characteristics of the service (e.g., the timeliness of the task). , the cost of completing the task, etc.).

[0098] The recommender application 802 may then recommend the task to the user using a mobile UI through which the user can initiate the task. The mobile UI may be configured to trigger the execution of a task through the user application using the service with the highest level of trust. As described above with reference to FIG. 5, the user can also access other available services with lower trust scores through the mobile user interface information.

[0099] FIG. 9 shows a flowchart 900 of a use case for enabling a previously performed task in a user application to be re-executed based on the current mobile device context, in accordance with one embodiment. Optionally, flowchart 900 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or description thereof. For example, flowchart 900 may be implemented using the recommender application described above.

[00100] As shown at block 902, the user is using the first user application (APP_01) for a task (ie, making purchases). The recommending application then recommends at a later point in time through the mobile interface of the second user application (APP_02) to make purchases, as shown in block 904. In decision block 906, it is determined whether the user rejects the recommendation made in block 904. If it is determined that the user does not reject the recommendation (that is, the user approves or selects the recommendation to complete the shopping task), the user is redirected to the shopping task user interface in the second user application, as shown in step 908. In addition, the user's dynamic profile is updated, as shown in step 910 to reflect approval of the recommendation (for example, increase the weight of the second user application to complete the task).

[00101] However, if it is determined that the user rejects the recommendation (i.e., the user does not approve or select the recommendation within a specific time period, or the user selects an alternative configuration parameter for a task to use the first user application), the user's dynamic profile is updated as shown at block 910. In particular, the dynamic user profile may be updated to increase the weight given to the first user application. In addition, when it is determined that the user rejects the recommendation, the recommending application at a later point in time and based on the updated dynamic user profile then recommends the first user application for shopping, as shown in block 912.

[00102] In addition, as shown at decision block 914, it is determined whether the user approves the recommendation made at block 912. If it is determined that the user approves the recommendation, the user is transferred to the shopping task user interface in the first user application, as shown in step 908. In addition, the dynamic user profile is updated, as shown at 910, to reflect approval of the recommendation (eg, increase the weight of the first user application to complete the task). However, if it is determined that the user does not approve of the recommendation, the dynamic user profile is updated as shown at 910 (eg, to reduce the weight given to the first user application).

[00103] FIG. 10 shows a flowchart 1000 of a use case for enabling a previously completed task in a user application to be re-executed based on the current mobile device context, in accordance with one embodiment. Optionally, flowchart 1000 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or their descriptions. For example, flowchart 1000 may be implemented using the recommender application described above.

[00104] As shown in step 1002, the user is using the first user application (APP_01) for a task (ie booking a taxi service). The recommending application then recommends at a later point in time via the user's mobile UI a second user application (APP_02) for booking taxi services, as shown in step 1004. In decision block 1006, it is determined whether the user rejects the recommendation made in block 1004. If determined, that the user does not reject the recommendation (i.e., the user approves or selects the recommendation to make a taxi booking), the user is redirected to the taxi booking user interface in the second user application, as shown in step 1008. In addition, the dynamic user profile is updated, as shown at block 910 to reflect approval of the recommendation (eg, increase the weight of the second user application to complete the task).

[00105] However, if it is determined that the user rejects the recommendation (i.e., the user does not approve or select the recommendation within a specific time period, or the user selects an alternative configuration parameter for a task to use the first user application), the user's dynamic profile is updated as shown at block 1010. In particular, the dynamic user profile may be updated to increase the weight given to the first user application. In addition, when it is determined that the user rejects the recommendation, the recommending application at a later point in time and based on the updated dynamic user profile then recommends the first user application and the second taxi booking user application, as shown in step 1012. This may occur when the trust rating for both user apps is the same. For example, step 1012 may be performed by presenting two separate mobile UIs, one for each respective user application.

[00106] In addition, as shown in step 1014, the user selects one of the recommendations presented in step 1012. In response, the user navigates to the user interface of the taxi booking task in the selected user application. The dynamic user profile is then updated, as shown at 1010, to reflect the user's choice.

[00107] FIG. 11 illustrates a flowchart 1100 for enabling a user application to re-execute a previously completed task based on the current mobile device context, in accordance with one embodiment. Optionally, flowchart 1100 may be implemented in the context of any one or more of the embodiments set forth in any preceding and/or subsequent figure(s) and/or their description. For example, flowchart 1100 may be implemented using the recommender application described above.

[00108] As shown in step 1102, user data is collected, such as application usage data. The user data is then stored in the dynamic user profile, as shown in block 1104. In particular, the tasks performed by using the applications are stored in the dynamic user profile along with the configuration settings of those tasks and the context of the mobile device under which those tasks were performed.

[00109] In addition, as shown in step 1106, the recommendation decision is made using a dynamic user profile. The recommendation decision includes determining which, if any, task in the dynamic user profile is relevant to the current mobile device context. Each task identified from the recommendation decision is then recommended to the user of the mobile device, as shown in step 1108. In particular, each task is recommended as a selectable mobile user interface presented via the mobile device. When the user selects one of the mobile UIs, as shown in block 1110, the mobile device repeats the task presented by the selected mobile UI in accordance with the associated configuration settings specified in the dynamic user profile. The task selection indication is then returned back to the dynamic user profile to store the selection indication (block 1104).

[00110] The embodiments described above can intelligently and automatically predict which user application tasks a mobile device user will want to perform based on historical data stored in a dynamic user profile and the current context of the mobile device, including identification of past tasks performed by the user that relevant to the current mobile device context. In addition, the embodiments described above can intelligently and automatically select one service from a variety of possible services to be used to perform each of the predicted tasks, according to the availability of various services, the past use of these services, as indicated in the dynamic user profile, etc.

[00111] The embodiments described above may recommend predictive tasks to the user via mobile user interfaces that are presented to the user without activating user applications. For example, mobile user interfaces, when selected by a user, may redirect the user directly to the user interface of the respective user application through which the user can initiate a task. As another example, the task may be automatically completed when the user selects the mobile UI representing the task.

[00112] When the user starts the recommended task, it can be performed using the selected service. Thus, the task can be accomplished by integrating the services of different service providers. In addition, the embodiments described above may provide a unified user interface for all service providers providing similar tasks through user applications. Optionally, the embodiments described above may further include a consent feature for one or more tasks that the recommending application would otherwise recommend to the user. This opt-in feature, when enabled by the user for a specific task, can cause the recommender app to automatically start the task when the recommender app determines it is relevant to the current mobile device context. In one embodiment, the opt-in feature may be provided to the user the first time a task is recommended to the user via the mobile UI, such as in the recommending user interface described in FIG. 5 above.

[00113] FIG. 12 is a diagram of a network architecture 1200, in accordance with one embodiment. As shown, at least one network 1202 is provided. In various embodiments, any one or more components/features set forth in the description of any previous figure(s) may be implemented in conjunction with any one or more components of at least one network 1202.

[00114] In the context of the present network architecture 1200, the network 1202 may take any form, including, but not limited to, a telecommunications network, a local area network (LAN), a wireless network, a wide area network (WAN) such as the Internet, a peer-to-peer network, a cable network, etc. .d. Although only one network is shown, it should be understood that two or more of the same or different networks 1202 may be provided.

[00115] A plurality of devices are connected to the network 1202. For example, server computer 1212 and computer 1208 may be associated with network 1202 for communication purposes. Such computer 1208 may include a desktop computer, a laptop computer, and/or any other type of logic. However, various other devices may be connected to network 1202, including personal digital assistant (PDA) device 1210, mobile phone device 1206, television 1204, and so on.

[00116] FIG. 13 is a diagram of an exemplary system 1300 in accordance with one embodiment. Optionally, system 1300 may be implemented in the context of any of the devices in network architecture 1200 of FIG. However, it should be understood that system 1300 may be implemented in any desired environment.

[00117] As shown, a system 1300 is provided including at least one processor 1302 that is coupled to a bus 1312. System 1300 also includes a memory 1304 [e.g., hard drive, solid state drive, random access memory (RAM), etc. .d.]. Memory 1304 may include one or more memory components and may even include various types of memory. System 1300 also includes a display 1310 in the form of a touch screen, separate display, or the like. Additionally included is a graphics processor 1308 coupled to a display 1310.

[00118] System 1300 may also include secondary storage 1306. Secondary storage 1306 includes, for example, a hard disk drive and/or a removable storage device such as a floppy drive, a tape drive, a CD drive, etc. .d. The removable storage device reads and/or writes to the removable storage unit in a well known manner.

[00119] In this regard, computer programs or computer logic control algorithms may be stored in memory 1304, secondary storage 1306, and/or any other memory. Such computer programs, when executed, allow the system 1300 to perform various functions (eg, as described above). Memory 1304, secondary storage 1306, and/or any other storage contain non-volatile computer-readable media.

[00120] It should be noted that the techniques described herein are, in one aspect, embodied in executable instructions stored on a computer-readable medium for use with or in conjunction with a machine, equipment, or device for executing instructions, such as a computer-based or processor-containing machine. , equipment or device. Those skilled in the art will appreciate that, for some embodiments, other types of computer-readable media that can store computer-accessible data are included, such as magnetic cassettes, flash memory cards, digital video discs, Bernoulli cartridges, random access memory (RAM) , Read Only Memory (ROM), and the like.

[00121] As used herein, a "computer-readable medium" includes one or more of any suitable media for storing executable instructions of a computer program such that a machine, system, equipment, or instruction executing device can read (or retrieve) instructions from the computer-readable medium and execute instructions for performing the described methods. Suitable storage formats include one or more of electronic, magnetic, optical, and electromagnetic formats. A non-exhaustive list of conventional exemplary computer-readable media includes: a portable computer diskette; RAM; ROM; erasable programmable read only memory (EPROM or flash memory); optical storage devices including portable compact disc (CD), portable digital video disc (DVD), high definition DVD (HD-DVD™), BLU-RAY disc; or the like.

[00122] It should be understood that the arrangement of the components shown in the described drawings is exemplary and that other arrangements are possible. It should also be understood that the various system components defined by the claims described below and illustrated in the various block diagrams represent logical components in some systems configured in accordance with the invention disclosed herein.

[00123] For example, one or more of these system components (and tools) may be implemented, in whole or in part, by at least some of the components illustrated in the diagrams shown in the described figures. Furthermore, while at least one of these components is implemented at least in part as an electronic hardware component and therefore is a machine, other components may be implemented in software which, when included in a runtime environment, is a machine. , hardware, or a combination of software and hardware.

[00124] More specifically, at least one component defined by the claims is implemented at least in part as an electronic hardware component, such as an instruction execution engine (e.g., a processor-based machine or a machine containing a processor) and/or as specialized circuits or circuits (for example, discrete logic gates interconnected to perform a specialized function). Other components may be implemented in software, hardware, or a combination of software and hardware. Moreover, some or all of these other components may be combined, some may be omitted altogether, and additional components may be added while still achieving the functionality described herein. Thus, the invention described herein may be embodied in many different variations, and all such variations are intended to be within the scope of the claims.

[00125] In the above description, the subject matter has been described with reference to acts and symbolic representations of operations that are performed by one or more devices, unless otherwise noted. Thus, it should be understood that such acts and operations, which are sometimes referred to as being performed by a computer, involve manipulation of a data processor in a structured manner. This manipulation transforms or maintains data in locations in the computer's memory system that reconfigures or otherwise changes device operation in a manner well understood by those skilled in the art. Data is stored in physical memory locations as data structures that have certain properties defined by the data format. However, while the subject matter has been described in the foregoing context, it is not intended to be limiting as those skilled in the art will appreciate that the various acts and operations described below may also be implemented in hardware.

[00126] To facilitate understanding of the subject matter described here, many aspects are described in terms of sequences of actions. At least one of these aspects defined by the claims is performed by the electronic equipment component. For example, it will be understood that various actions may be performed by specialized circuits or circuits, by software instructions executed by one or more processors, or by a combination of both. The description of any sequence of actions given here does not imply that the specific order described for performing that sequence must be followed. All of the methods described herein may be performed in any suitable order, unless otherwise specified herein or otherwise clearly contradicts the context.

[00127] The use of terms in the singular in the context of the description of the subject matter (especially in the context of the following claims) should be construed as covering both the singular and the plural, unless otherwise specified herein or clearly contrary to the context. The listing of ranges of values in this document is simply intended to serve as a shorthand way of individually referring to each individual value falling within that range, unless otherwise noted here, and each individual value is included in the description as if it were separately listed here. Furthermore, the foregoing description is for illustrative purposes only and not for the purpose of limitation, as the scope of the protection claimed is defined by the claims set forth below, together with any equivalents thereof that appear to be valid. The use of any and all examples or exemplary language (eg, "such as") provided herein is merely intended to better illustrate the subject matter of the invention and is not intended to limit the scope of the invention unless otherwise stated. The use of the term "based on" and other similar phrases denoting a condition for achieving a result, either in the claims or in the written description, is not intended to exclude any other conditions that lead to such a result. No language in the specification is to be construed as indicating any unclaimed element as essential to the practice of the invention as claimed.

[00128] The embodiments described herein include one or more modes known to the inventor for carrying out the claimed invention. It should be appreciated that variations of these embodiments will become apparent to those skilled in the art upon reading the foregoing description. The inventor expects those skilled in the art to make use of such variations as the case may be, and the inventor intends to practice the claimed invention in a manner other than specifically described herein. Accordingly, this claimed invention includes all modifications and equivalents of the invention set forth in the appended claims, as provided by applicable law. Moreover, any combination of the above described elements in all their possible variants is covered, unless otherwise specified in this document or otherwise clearly contradicts the context.

Statement 1. A device comprising:

long-term storage containing instructions; and

one or more processors interacting with said memory, wherein one or more processors execute instructions for:

monitoring the use of the application to complete a task through a mobile device;

determining task configuration parameters via user interfaces (UIs) associated with using the application, the task being executed with the configuration parameters set in accordance with the UI;

identifying a mobile device context, the context including one or more mobile device conditions under which the application was activated to perform a task by the mobile device user;

keeping track of the current context of the mobile device, the current context including one or more conditions under which the mobile device operates;

determining relevance between said context and the current context; and

presenting, in response to this determined relevancy, the mobile UI through the mobile device, so that the mobile UI allows the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

Clause 2. A device under Clause 1, in which the application is a mobile application installed on a mobile device.

Statement 3. A device under Statement 1 in which the application is one of:

messaging apps,

media player,

shop of a trade and service enterprise and

travel booking apps.

Statement 4. The device according to Statement 1, in which the UIs associated with the use of the application are the UIs of the application on which the user navigates to set the configuration parameters and start the execution of the task with the configuration parameters.

Claim 5. The apparatus of Claim 1, further comprising storing a task indication with configuration parameters and a mobile device context in a profile for the user, wherein the user profile is accessed to identify the context to determine the relevance between the context and the current mobile device context.

Claim 6. The device according to Claim 1, where the mobile device context includes one of:

mobile device location and

time specified by the mobile device.

Claim 7. The apparatus of Claim 1 wherein said determination of relevance between a context and the current context includes determining that the current context is within a predetermined threshold difference with the context.

Statement 8. A device under Statement 1 in which the mobile UI is presented on the home screen of the mobile device.

Claim 9. The device according to Claim 1, wherein the mobile UI presented via the mobile device is an icon that, when selected by the user, causes the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

Claim 10. A Claim 1 device in which one or more processors additionally execute instructions for:

monitoring the use of an additional application to perform an additional task through a mobile device;

determining configuration parameters of the additional task through additional user interfaces (UIs) associated with the use of the additional application, wherein the additional task is executed with the configuration parameters set in accordance with the additional UIs;

identifying an additional mobile device context, the additional context including one or more mobile device conditions under which the additional application has been activated to perform the additional task by the user of the mobile device;

determining additional relevance between the additional context and the current context; and

presenting, in conjunction with the mobile UI, and in response to this particular additional relevancy, the additional mobile UI via the mobile device, so that the additional mobile UI allows the additional task to be repeated with the configuration parameters of the additional task without activating at least one of the additional UIs associated with the use of the additional applications.

Provision 11. Machine-implemented method, containing the steps in which:

monitor the use of the application to complete the task through the mobile device;

determining task configuration parameters via user interfaces (UIs) associated with using the application, the task being executed with the configuration parameters set in accordance with the UI;

identifying a mobile device context, the context including one or more mobile device conditions under which the application was activated to perform a task by the mobile device user;

keeping track of the current context of the mobile device, and the current context includes one or more conditions under which the mobile device operates;

determining the relevance between said context and the current context; and

presenting, in response to this determined relevance, the mobile UI via the mobile device, so that the mobile UI allows the execution of the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

Claim 12. A machine-implemented method according to Claim 11, wherein the application is a mobile application installed on a mobile device.

Statement 13. A machine-implementable method according to Statement 11, wherein the application is one of:

messaging apps,

media player,

shop of a trade and service enterprise and

travel booking apps.

Statement 14. A computer-implemented method according to Statement 11, wherein the UIs associated with the use of the application are the UIs of the application through which the user navigates to set configuration parameters and start executing a task with the configuration parameters.

Statement 15. The computer-implemented method according to Statement 11, further comprising storing a task indication with configuration parameters and a mobile device context in a profile for the user, wherein the user profile is accessed to identify the context to determine the relevance between the context and the current mobile device context .

Claim 16. A computer-implemented method according to Claim 11, wherein the mobile device context includes one of:

mobile device location and

the time specified by the mobile device.

Statement 17. The computer-implemented method according to Statement 11 wherein said determination of relevance between a context and a current context includes determining that the current context is within a predetermined threshold difference with the context.

Statement 18. A computer-implemented method according to Statement 11, in which the mobile UI is presented on the home screen of the mobile device.

Statement 19. A computer-implemented method according to Statement 11, wherein the mobile UI presented via the mobile device is an icon that, when selected by the user, causes the execution of a task with configuration parameters to be repeated without activating at least one of the UIs associated with the use of the application.

Statement 20. A machine-implementable method according to Statement 11, further comprising the steps of:

monitor the use of an additional application to perform an additional task through a mobile device;

determining additional task configuration parameters via additional user interfaces (UIs) associated with the use of the additional application, wherein the additional task is executed with the configuration parameters set in accordance with the additional UIs;

identifying an additional mobile device context, the additional context including one or more mobile device conditions under which the additional application has been activated to perform the additional task by the mobile device user;

determining additional relevance between the additional context and the current context; and

represent, in conjunction with the mobile UI and in response to this defined additional relevancy, an additional mobile UI via the mobile device, so that the additional mobile UI allows the additional task to be repeated with the configuration parameters of the additional task without activating at least one of the additional UIs associated with the use of the additional applications.

Provision 21 A non-volatile computer-readable medium that stores computer instructions which, when executed by one or more processors, cause one or more processors to perform the steps of:

monitoring the use of the application to complete a task through a mobile device;

determining task configuration parameters via user interfaces (UIs) associated with using the application, the task being executed with the configuration parameters set in accordance with the UI;

identifying a mobile device context, the context including one or more mobile device conditions under which the application was activated to perform a task by the mobile device user;

keeping track of the current context of the mobile device, the current context including one or more conditions under which the mobile device operates;

determining relevance between said context and the current context; and

presenting, in response to this determined relevancy, the mobile UI through the mobile device, so that the mobile UI allows the task to be repeated with the configuration parameters without activating at least one of the UIs associated with using the application.

Claim 22. A machine-implemented method according to Claim 21, wherein the application is a mobile application installed on a mobile device.

Statement 23. A machine-implementable method according to Statement 21, in which the application is one of:

messaging apps,

media player,

shop of a trade and service enterprise and

travel booking apps.

Statement 24. A computer-implemented method according to Statement 21, wherein the UIs associated with the use of an application are the UIs of an application that the user navigates to set configuration parameters and start executing a task with the configuration parameters.

Statement 25. The computer-implemented method according to Statement 21, further comprising storing a task indication with configuration parameters and a mobile device context in a profile for the user, wherein the user profile is accessed to identify the context to determine the relevance between the context and the current mobile device context .

Claim 26. A computer-implemented method according to Claim 21, wherein the mobile device context includes one of:

mobile device location and

the time specified by the mobile device.

Statement 27. A computer-implemented method according to Statement 21 wherein said determination of relevance between a context and a current context includes determining that the current context is within a predetermined threshold difference with the context.

Claim 28. A computer-implemented method according to Claim 21, in which the mobile UI is presented on the home screen of the mobile device.

Statement 29. A computer-implemented method according to Statement 21, wherein the mobile UI presented via the mobile device is an icon that, when selected by the user, causes the task to be repeated with the configuration parameters without activating at least one of the UIs associated with the use of the application.

Statement 30. A machine-implementable method according to Statement 21, further comprising the steps of:

monitor the use of an additional application to perform an additional task through a mobile device;

determining additional task configuration parameters via additional user interfaces (UIs) associated with the use of the additional application, the additional task being executed with the configuration parameters set in accordance with the additional UIs;

identifying an additional mobile device context, the additional context including one or more mobile device conditions under which the additional application has been activated to perform the additional task by the mobile device user;

determining additional relevance between the additional context and the current context; and

represent, in conjunction with the mobile UI and in response to this defined additional relevancy, an additional mobile UI via the mobile device, so that the additional mobile UI allows the additional task to be repeated with the configuration parameters of the additional task without activating at least one of the additional UIs associated with the use of the additional applications.

Claims (40)

1. A computer-implemented method for performing an application task by means of a mobile device configured to install a recommending application and said application, the method comprising the steps of: in response to the input of user settings, by means of the recommending application, determining the configuration parameters of the task through the user interfaces (UI) associated with the use of said application, and the task is performed with these specific configuration parameters set in accordance with said UI; when said application is activated to perform a task with said specific configuration parameters by a mobile device through a user operation, a mobile device context is identified by the recommending application, the context including one or more mobile device conditions in which said application was activated to perform a task with said certain configuration parameters, while using the recommending application additionally monitor the use of said application that performs the task; the recommender application keeps track of the current context of the mobile device, the current context including one or more conditions under which the mobile device operates; by means of a recommending application, determining the relevance between said context and the current context; and by means of the recommending application, in response to this determined relevance, a mobile UI is presented via the mobile device, wherein, through the mobile UI, a task can be initiated with said certain configuration parameters without activating at least one or all of said application-related UIs. 2. The computer-implemented method according to claim 1, wherein said application is a third-party application or a system application installed on the mobile device, and said application is different from the recommending application. 3. A computer-implemented method according to claim 1 or 2, wherein said presentation by a recommender application of a mobile UI through a mobile device is performed without activating any UI of said application. 4. A computer-implemented method according to any one of claims 1 to 3, wherein said presenting by means of a recommending mobile UI application via the mobile device causes the execution of a task previously performed via the mobile UI to be repeated without using said application UI to initiate the task. 5. A computer-implemented method according to any one of claims 1 to 4, further comprising the step of initiating a task through said application in response to a user selecting a mobile UI by a mobile device. 6. The computer-implemented method of claim 5, wherein said initiating, in response to a user selecting a mobile UI by a mobile device, tasks through an application comprises the steps of: in response to the user selecting the mobile UI by the mobile device, approving the user input provided by the user; and initiating a task in said application according to user input. 7. The computer-implemented method according to claim 6, wherein said application is a phone call application, wherein the task is to make a phone call to a particular contact, and the user input is the phone number of that particular contact; or said application is a messaging application, wherein the task is to send a message to a specific contact, and the user input is the content of the message; or said application is a trip booking application, where the task is to book a taxi service, and the user input is a desired vehicle type. 8. A computer-implemented method according to any one of claims 1-6, wherein said application is one of: phone call apps, messaging apps, media player, shop of a trade and service enterprise and travel booking apps. 9. A computer-implemented method according to any one of claims 1-8, wherein said UIs associated with using an application are UIs of said application through which a user navigates to set configuration parameters and initiate a task execution with those configuration parameters. 10. A computer-implemented method according to any one of claims 1-9, further comprising storing a task indication with said configuration parameters and a mobile device context in a profile for the user, wherein the user profile is accessed to identify the context to determine the relevance between said context and the current context of the mobile device. 11. A computer-implemented method according to any one of claims 1-10, wherein said mobile device context includes one of: mobile device location and the time specified by the mobile device. 12. A computer-implemented method according to any one of claims 1-11, wherein said determination of relevance between a context and the current context includes determining that the current context is within a predetermined threshold difference with said context. 13. A computer-implemented method according to any one of claims 1-12, wherein the mobile UI is presented by the recommending application on the home screen of the mobile device. 14. A computer-implemented method according to any one of claims 1 to 13, wherein the mobile UI presented by the mobile device is an icon that, when selected by the user, causes a task to be repeated with said configuration parameters without activating at least one or all of the mentioned UIs related to using the application. 15. A computer-implemented method according to any one of claims 1-14, further comprising performing an additional task of an additional application by a mobile device, the mobile application being configured to install this additional application, the method further comprising the steps of: in response to the input of user settings, by means of the recommending application, additional configuration parameters of the additional task are determined through additional user interfaces (UI) associated with the use of the additional application, and the additional task is performed with these additional configuration parameters set in accordance with said additional UI; when an additional application is activated to perform an additional task by a mobile device through a user operation, an additional mobile device context is identified by the recommending application, and the additional context includes one or more conditions of the mobile device in which the additional application was activated to perform an additional task, while by means of the recommending application, additionally monitoring the use of the additional application performing the additional task; by means of a recommending application, additional relevance between the additional context and the current context is determined; and by means of the recommending application, in conjunction with the mobile UI and in response to this certain additional relevancy, an additional mobile UI by means of a mobile device is presented, whereby through the additional mobile UI an additional task can be initiated with said additional additional task configuration parameters, without activating at least one or all of the additional UIs associated with the additional application. 16. A mobile device configured to perform an application task, wherein the mobile device contains: a long-term storage device containing instructions; and one or more processors in communication with the storage device, wherein the one or more processors are configured to execute instructions for performing the method according to any one of claims 1-15. 17. A computer-readable medium that stores program instructions that, when executed by the processor of the mobile device, cause the mobile device to perform the method of any one of claims 1-15.

Images