Task creation method, device and equipment and computer storage medium

Abstract

The invention provides a task creation method, device and equipment and a computer storage medium, can be applied to the technical field of computers, and is used for improving the processing efficiency of repeatedly appearing tasks. The method at least comprises the steps of presenting a task interface, wherein the task interface comprises a timing control corresponding to a to-be-created task; in response to a time configuration operation triggered for the timing control, switching from the task interface to a timing interface, the timing interface comprising time information for controlling the to-be-created task to be repeatedly executed; in response to an information confirmation operation triggered for the time information, switching from the timing interface to a task interface, the task interface further comprising content information corresponding to the to-be-created task; and in response to a task submission operation triggered for the content information, presenting creation completion information of the to-be-created task. According to the method, repetition frequency configuration is provided through the timing control, information of repeated execution is recorded in the one-time creation process of the task, and the processing efficiency of the repeatedly occurring task is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and specifically to a method, apparatus, and device for task creation, as well as a computer storage medium. Background Technology

[0002] With the continuous development of science and technology and society, internet technology has provided greater convenience to more and more people. Users can utilize internet-based goods delivery platforms to obtain specialty products from different regions, receive food delivered to their homes from various locations without leaving their houses, and use errand-running services to complete tasks that are inconvenient to do personally.

[0003] Taking the errand-running function used by an object as an example, its use case is usually that the object is unable to complete a task personally due to its own environmental conditions, so it needs someone else to do it for it. However, since the object's environmental conditions are not easily changed, for some tasks that need to be done repeatedly, the object has to repeatedly and actively use the errand-running function to create the corresponding tasks every time they are needed.

[0004] For example, a user needs to pick up medicine from a traditional Chinese medicine store at a fixed time each week. However, since the time for picking up the medicine coincides with the user's working hours, the user needs to repeatedly and proactively use the errand-running function to create corresponding tasks in order to complete the process of picking up the medicine.

[0005] Given the above situation, users can currently only create tasks using the errand-running function when a need arises. However, due to unfavorable environmental conditions, users may be unable to create tasks in a timely manner, thus failing to meet their needs promptly. Furthermore, repeatedly using the errand-running function to create tasks may lead to errors in task parameter input, resulting in a degraded user experience.

[0006] On the other hand, the server that receives tasks created using objects also needs to continuously store the relevant information of the received tasks, which will occupy a lot of the server's storage space. In addition, the server needs to perform calculations and processing on the same task every time, which will also waste a lot of the server's computing resources.

[0007] Therefore, how to improve the processing efficiency of repetitive tasks is a technical problem that urgently needs to be solved. Summary of the Invention

[0008] This application provides a method, apparatus, device, and computer storage medium for task creation, which improves the processing efficiency of repetitive tasks.

[0009] Firstly, a method for task creation is provided, including:

[0010] A task interface is presented, which includes a timer control corresponding to the task to be created.

[0011] In response to a time configuration operation triggered by the timer control, the task interface is switched to the timer interface, which includes time information for controlling the repeated execution of the task to be created.

[0012] In response to an information confirmation operation triggered by the time information, the system switches from the timed interface to the task interface, which further includes: content information corresponding to the task to be created;

[0013] In response to a task submission operation triggered by the content information, the creation completion information of the task to be created is displayed.

[0014] Secondly, a task creation apparatus is provided, comprising:

[0015] First display unit: used to present the task interface, which includes: a timer control corresponding to the task to be created;

[0016] The second display unit is used to switch from the task interface to the time interface in response to a time configuration operation triggered by the timer control. The timer interface includes time information for controlling the repeated execution of the task to be created.

[0017] The third display unit is used to switch from the timed interface to the task interface in response to an information confirmation operation triggered by the time information. The task interface also includes: content information corresponding to the task to be created.

[0018] The fourth display unit is used to respond to a task submission operation triggered by the content information and present the creation completion information of the task to be created.

[0019] Optionally, the second display unit is used to switch from the task interface to the timer interface, specifically for:

[0020] The user switches from the task interface to the timing interface, where a repetition frequency configuration area is displayed.

[0021] The repetition frequency configuration area includes: frequency information that controls the repetition frequency of the task to be created, within the time information.

[0022] Optionally, the second display unit is further used for:

[0023] In response to a frequency configuration operation triggered for the repetition frequency configuration area, the system switches from the timing interface to the frequency interface, the frequency interface including: at least one time period; wherein the at least one time period includes at least one of the following: a first time period with a calendar day as the time unit; a second time period with a working day as the time unit; a third time period with a week as the time unit; and a fourth time period with a month as the time unit.

[0024] In response to a periodic confirmation operation triggered for a target time period, the system switches from the frequency interface to the timing interface and displays the configured frequency information in the timing interface; wherein the target time period is any one of the at least one time period and is negatively correlated with the frequency information.

[0025] Optionally, the second display unit, in response to a periodic confirmation operation triggered for a target time period, when switching from the frequency interface to the timing interface, is specifically used for:

[0026] In response to a period confirmation operation triggered for the target time period, the frequency interface is switched to a period selection interface, which includes at least one time point within a preset time range.

[0027] In response to a time point confirmation operation triggered for a target time point, the system switches from the period selection interface to the timing interface; the target time point is any one of the at least one time point.

[0028] Optionally, the timing interface further includes: an end time configuration area and an execution time configuration area; wherein,

[0029] The end time configuration area includes: end information that controls the end time of the task to be created in the time information;

[0030] The execution time configuration area includes: execution information that controls the execution time of the task to be created, within the time information.

[0031] Optionally, the second display unit is further used for:

[0032] In response to an end time configuration operation triggered for the end time configuration area, an end time interface is presented in the timed interface as a sub-interface, the end time interface including: a time confirmation control and a count confirmation control;

[0033] In response to an end time confirmation operation triggered by the time confirmation control, the system switches from the end time interface to the timer interface; or, in response to an end count confirmation operation triggered by the count confirmation control, the system switches from the end time interface to the timer interface.

[0034] Optionally, after presenting the creation completion information of the task to be created, the fourth display unit is further configured to:

[0035] The task interface is presented, and the task interface also includes: created controls;

[0036] In response to a control confirmation operation triggered for the created control, the interface switches from the task interface to the management interface, which includes at least one created task that is being repeatedly executed.

[0037] In response to a task closure operation triggered for a target created task, task completion information corresponding to the target created task is presented; wherein the target created task is any one of the at least one created task.

[0038] Optionally, the creation completion information includes: the task identifier corresponding to the task to be created; then, after presenting the creation completion information of the task to be created, the fourth display unit is further used for:

[0039] Based on the time information corresponding to the task to be created, the following operations are performed each time the task to be created is executed:

[0040] Based on the task identifier and the next execution time corresponding to the task to be created, the execution identifier corresponding to the current execution of the task to be created is obtained; wherein, the execution identifier is used to: uniquely identify the execution record information of the current execution of the task to be created;

[0041] Based on the execution identifier, the corresponding task execution distributed lock is acquired so that the task to be created is executed by a single thread during this execution.

[0042] After the single thread completes the task to be created, the task execution distributed lock is released.

[0043] Thirdly, a computer program product is provided, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0044] Fourthly, a computer device is provided, comprising:

[0045] Memory, used to store program instructions;

[0046] A processor is configured to invoke program instructions stored in the memory and execute the method described in the first aspect according to the obtained program instructions.

[0047] Fifthly, a computer-readable storage medium is provided, the computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method as described in the first aspect.

[0048] In this embodiment, a timer control is presented in the task interface. Using this timer control, time information for controlling the repeated execution of the task to be created is obtained. After obtaining the corresponding content information of the task to be created, the task creation process for that task can be completed. In this process, the task to be created, which needs to be executed repeatedly, is created only once. When creating a task using an object, only a one-time task information input operation is required, simplifying the task creation process using objects and avoiding potential information input errors when repeatedly creating tasks using objects.

[0049] On the other hand, the server receiving information about the task created by the object only needs to store information for this single creation process, saving resources by conserving server storage space. Furthermore, the server only needs to perform a single calculation for this task, which also saves significant computing resources compared to multiple repetitive calculations. Moreover, by utilizing the time information in the task details, the server can repeatedly execute the task created by the object at the corresponding time points, allowing the user to seamlessly experience the repeated execution of the task. This ensures that the user's needs are met and improves the user experience. Attached Figure Description

[0050] Figure 1 A schematic diagram of the principle of a method for task creation in related technologies. Figure 1 ;

[0051] Figure 2 A schematic diagram of the principle of a method for task creation in related technologies. Figure 2 ;

[0052] Figure 3 A schematic diagram of a scenario for a task creation method provided in an embodiment of this application;

[0053] Figure 4 A flowchart illustrating a method for creating a task provided in an embodiment of this application. Figure 1 ;

[0054] Figure 5 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 1 ;

[0055] Figure 6 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 ;

[0056] Figure 7 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 ;

[0057] Figure 8 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 4 ;

[0058] Figure 9 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 5 ;

[0059] Figure 10 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 6 ;

[0060] Figure 11 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 7 ;

[0061] Figure 12 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 8 ;

[0062] Figure 13 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 9 ;

[0063] Figure 14 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 ;

[0064] Figure 15 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 one;

[0065] Figure 16 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 two;

[0066] Figure 17 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 three;

[0067] Figure 18 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10Four;

[0068] Figure 19 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 five;

[0069] Figure 20 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 six;

[0070] Figure 21 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 seven;

[0071] Figure 22 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 eight;

[0072] Figure 23 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 10 Nine;

[0073] Figure 24 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 ten;

[0074] Figure 25 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 eleven;

[0075] Figure 26 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 twelve;

[0076] Figure 27 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 Thirteen;

[0077] Figure 28 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 fourteen;

[0078] Figure 29 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 fifteen;

[0079] Figure 30 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 sixteen;

[0080] Figure 31A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 Seventeen;

[0081] Figure 32 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 eighteen;

[0082] Figure 33 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 2 nineteen;

[0083] Figure 34 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 ten;

[0084] Figure 35 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 eleven;

[0085] Figure 36 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 twelve;

[0086] Figure 37 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 Thirteen;

[0087] Figure 38 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 fourteen;

[0088] Figure 39 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 fifteen;

[0089] Figure 40 A schematic diagram of a task creation method provided in an embodiment of this application;

[0090] Figure 41 A flowchart illustrating a method for creating a task provided in an embodiment of this application. Figure 2 ;

[0091] Figure 42 A schematic diagram of the task creation method provided in the embodiments of this application. Figure 3 sixteen;

[0092] Figure 43 A schematic diagram of the apparatus for task creation provided in the embodiments of this application. Figure 1 ;

[0093] Figure 44 A schematic diagram of the apparatus for task creation provided in the embodiments of this application. Figure 2 . Detailed Implementation

[0094] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0095] It should be noted that in the embodiments of this application, data such as the content information and location information of the task are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0096] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0097] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0098] (1) Application, i.e., application program:

[0099] A computer program that can perform one or more tasks is generally an application. It has a visual interface and can interact with the user. Examples include electronic maps and calendars. Some applications require the user to install them on the terminal device they are using, while others do not require installation. Examples include mini-programs and web pages in some social applications. Mini-programs can be used without downloading or installing; the user can open the application by scanning a QR code or searching for it.

[0100] (2) Goods transportation platform:

[0101] This typically refers to online platforms that provide logistics services. They connect providers, transporters, and recipients of goods via internet technology to achieve fast and efficient transportation. These platforms usually offer fast parcel delivery, drop-off services, or instant or same-day delivery. By integrating resources and optimizing logistics processes, these platforms improve logistics efficiency, reduce costs, and provide users with more convenient and faster logistics services.

[0102] (3) Errand running function:

[0103] It is an on-demand logistics solution based on location-based services (LBS), involving the following key concepts and components: demand response, which is to quickly respond to the immediate needs initiated by users and assign them to appropriate service providers; geographic information system, which is used to store and analyze data related to geographic distribution, helping to determine the geographic relationship between service providers and users, as well as the optimal delivery route; and real-time monitoring, which uses GPS and other sensor technologies to achieve real-time acquisition of service provider locations and monitoring of delivery status.

[0104] (4) User interface:

[0105] An application interface is a user-oriented medium for interaction and information exchange between the application system and its users. It converts information from its internal form to a human-readable format, enabling users to operate the application conveniently and efficiently for two-way interaction and to complete the tasks they wish to accomplish using the application. Different applications use different interfaces to display different content to users, facilitating various information interactions between them.

[0106] The application areas of the task creation method provided in the embodiments of this application will be briefly introduced below.

[0107] With the continuous development of science and technology and society, internet technology has provided greater convenience to more and more people. Users can utilize goods delivery platforms to obtain specialty products from different regions, receive food delivered to their homes from various locations without leaving their houses, and use errand-running functions to complete tasks that are inconvenient to do personally.

[0108] Taking the errand-running function used by an object as an example, its use case is usually that the object is unable to complete a task personally due to its own environmental conditions, so it needs someone else to do it for it. However, since the object's environmental conditions are not easily changed, for some tasks that need to be done repeatedly, the object has to repeatedly and actively use the errand-running function to create the corresponding tasks every time they are needed.

[0109] Given the above situation, the current users can only be as follows: Figure 1 As shown, tasks are created using the errand-running function only when a need arises. However, due to unfavorable environmental conditions affecting the user, they may be unable to create tasks using the errand-running function in a timely manner, thus preventing their needs from being met promptly. Moreover, repeatedly using the errand-running function to create tasks may lead to issues such as… Figure 2 As shown, the user experience was reduced due to incorrect input of task parameters caused by a mistake.

[0110] On the other hand, the server that receives tasks created using objects also needs to continuously store the relevant information of the received tasks, which will occupy a lot of the server's storage space. In addition, the server needs to perform calculations and processing on the same task every time, which will also waste a lot of the server's computing resources.

[0111] In view of this, this application provides a task creation method to improve the processing efficiency of repetitive tasks. This application adds a repetition frequency setting stage to the task creation process. Using a timer control presented in the task interface, it obtains the time information corresponding to the task to be created, and controls the repeated execution of the task based on this time information. In addition to obtaining the time information, it also obtains the content information corresponding to the task to be created, such as location information and item information required for the task to be executed, thus completing the acquisition of the necessary information for the execution of the task and successfully creating it. Therefore, after receiving task creation information, the executor of the task can calculate the resources and costs required for the repeated execution of the task based on the time information, thereby quickly completing the configuration of the basic information for the repetitive task.

[0112] The following describes the application scenarios of the task creation method provided in this application.

[0113] Please refer to Figure 3 This is a schematic diagram illustrating an application scenario of the task creation method provided in this application. The application scenario includes a server 301 and a terminal 302, which can communicate with each other. The communication method can be wired, such as through a network cable or serial cable; or wireless, such as through Bluetooth or Wi-Fi. No specific limitation is imposed.

[0114] Terminal 302 generally refers to devices that can present an interface, such as terminal devices, third-party applications accessible by terminal devices, or web pages accessible by terminal devices. Terminal devices include, but are not limited to, mobile phones, computers, smart medical devices, smart home appliances, vehicle terminals, or aircraft. Server 301 generally refers to devices that can run program packages, such as terminal devices or servers. Servers include, but are not limited to, cloud servers, local servers, or associated third-party servers. A server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0115] Both server 301 and terminal 302 can use cloud computing to reduce the use of local computing resources; similarly, they can also use cloud storage to reduce the use of local storage resources.

[0116] As one embodiment, the server 301 and the terminal 302 can be the same device, or they can be different devices, or they can be different devices with some modules shared, etc., and there are no specific restrictions.

[0117] It should be noted that the task creation method in each embodiment of this application can be executed by an electronic device, which can be a terminal device or a server. That is, the method can be executed by the terminal 302 alone, or by the terminal 302 and the server 301 together.

[0118] For example, taking terminal 302 as a terminal device, when creating a task, the terminal device can first present a task interface, which includes a timer control corresponding to the task to be created. In response to the time configuration operation of the timer control, the terminal device can switch the task interface to the timer interface and present the corresponding time information for controlling the repeated execution of the task to be created in the interface.

[0119] Furthermore, in response to a confirmation operation triggered by time information, the terminal device can switch from the timed interface to the task interface, and simultaneously display the content information corresponding to the task to be created in the task interface. Thus, when the terminal device responds to a task submission operation triggered by the content information, it can display the creation completion information of the task to be created, thereby completing the task creation operation for the task to be created.

[0120] The following is based on Figure 3The method for creating tasks provided in the embodiments of this application will be described in detail below. Please refer to... Figure 4 This is a flowchart illustrating a method for creating a task provided in an embodiment of this application.

[0121] Step S41: Present the task interface, which includes a timer control corresponding to the task to be created.

[0122] The task to be created can be the aforementioned task that the user expects to transport goods on the goods transportation platform. During the creation of this task, the user needs to provide the goods transportation platform with information about the goods to be transported, as well as the location information of the goods or the receiving goods. Then, the goods transportation platform provides goods transportation services to the user based on this information related to the task to be created.

[0123] The task interface can be the operation interface presented to the user object by the goods transportation platform when the user object expects to create a task. Through this interface, the user object can interact with the terminal device and input relevant information of the task to be created into the terminal device.

[0124] The task interface can be presented in several different ways. For example, in one approach, the task interface can be presented through an interface within an application corresponding to the goods transportation platform. This application could be a dedicated application developed for the goods transportation platform with specific functions, or it could be a multi-functional application that integrates the goods transportation functions provided by the platform. Another example is that the task interface can be presented through a webpage on a website that is part of the goods transportation platform.

[0125] Taking the errand-running function as an example, when creating a corresponding errand-running task, such as Figure 5 As shown, the terminal device can provide a corresponding task interface to the user through a specific application that provides errand-running functions, or, as... Figure 6 As shown, the terminal device can provide the user with a corresponding task interface through a map application or a shopping application interface.

[0126] After the task interface is displayed on the terminal device, such as Figure 7 As shown, the task interface may include a timer control corresponding to the task to be created. The timer control provides the task with the appropriate time information for task execution. Optionally, the timer control can be presented as follows: Figure 7 As shown, it is fixedly displayed in a designated location on the task interface, or it can be as follows: Figure 8 As shown, it appears as a floating element on top of the task interface, and its position can be adjusted freely by the user.

[0127] Step S42: In response to a time configuration operation triggered by a timer control, switch from the task interface to the timer interface, which includes time information for controlling the repeated execution of the task to be created.

[0128] Using an object, you can trigger a corresponding time configuration operation on the terminal device based on a defined control presented in the task interface. In response to this time configuration operation, the terminal device will switch from the task interface to the timed interface. Figure 9 As shown, this timing interface includes time information for controlling the repeated execution of tasks to be created. This time information can display different content depending on the specific operational details within the time configuration.

[0129] For example, the time information could include: the task will be executed at 5 PM every day, or at 9 AM every weekday, or on Tuesdays and Wednesdays every weekday, or on the 1st, 7th, and 19th of every month, and so on. This information is displayed on the terminal device's timer interface through time configuration to control the repetitive execution time of the tasks to be created.

[0130] Step S43: In response to the information confirmation operation triggered by the time information, switch from the timed interface to the task interface, which also includes the content information corresponding to the task to be created.

[0131] After the terminal device presents the time information, including the time interface, to the user, the user can trigger a corresponding confirmation operation based on that time information. In response to this confirmation operation, the terminal device can then... Figure 10 As shown, the user switches from the timed interface to the task interface, where the content information corresponding to the task to be created is displayed. It should be noted that the terminal device can acquire this content information either before or after the acquisition of the time information; this application does not impose any restrictions on this. Furthermore, the specific content included in the content information can be determined based on the actual type of the task to be created.

[0132] For example, if the task to be created is an errand-running task created by the user based on the errand-running function, the content information in the task to be created may include: the location information of the obtained item, the location information of the received item, the item information (including the item type, item weight, item volume, etc.), and the contact information of the person who will receive the item.

[0133] For example, if the task to be created is a delivery task created by the user based on the resource exchange function, the content information in the task to be created may include: the location information of the item to be collected, the contact information of the item collection person, etc.

[0134] Step S44: In response to the task submission operation triggered by the content information, present the creation completion information of the task to be created.

[0135] The terminal device displays the content information corresponding to the task to be created on the task interface. After the user confirms that the content information is correct, they can trigger the corresponding task submission operation based on that content information. The terminal device responds to the task submission operation as follows: Figure 11 As shown, the creation completion information for the task to be created is displayed. This creation completion information can be presented in various ways, such as... Figure 11 As shown, it can be presented on top of the task interface as a sub-interface, or it can be like... Figure 12 As shown, the task interface redirects to a new completion interface, which displays the creation completion information.

[0136] The above describes a task creation method proposed in this application. In this method, a timer control is presented in the task interface. This timer control is used to obtain the time information for controlling the repeated execution of the task to be created. After obtaining the corresponding content information of the task to be created, the task creation process for that task can be completed. In this process, the task to be created only needs to be created once for tasks that require repeated execution. When creating tasks using objects, only a one-time task information input operation is required, simplifying the task creation process using objects and avoiding potential information input errors when repeatedly creating tasks using objects.

[0137] On the other hand, the server receiving information about the task created by the object only needs to store information for this single creation process, saving resources by conserving server storage space. Furthermore, the server only needs to perform a single calculation for this task, which also saves significant computing resources compared to multiple repetitive calculations. Moreover, by utilizing the time information in the task details, the server can repeatedly execute the task created by the object at the corresponding time points, allowing the user to seamlessly experience the repeated execution of the task. This ensures that the user's needs are met and improves the user experience.

[0138] The above describes the method for creating tasks provided in this application. The following will elaborate on possible implementation methods associated with the timer control:

[0139] Regarding the time information for controlling the repeated execution of tasks to be created, the methods of obtaining and presenting it vary depending on the different divisions of time units in general knowledge.

[0140] Specifically, in one possible implementation, when the terminal device switches from the task interface to the timer interface in response to a time configuration operation triggered by the timer control, the terminal device may also perform the following operations:

[0141] like Figure 13 As shown, the terminal device can switch from the task interface to the timing interface, where a repetition frequency configuration area is displayed. This repetition frequency configuration area includes, within the time information, frequency information that controls the repetition frequency of the task to be created.

[0142] In this method, when configuring the response time, the terminal device can first switch from the task interface to the timing interface, where a repetition frequency configuration area is displayed. In this area, the user can configure frequency information related to the repetition frequency. For example, time information related to the repetition frequency can be configured, such as daily repetition or weekly repetition. The repetition frequency can also be configured for the corresponding number of repetitions, such as repeating 3 times a week or repeating 5 times a month.

[0143] On the other hand, regarding this timing interface, the way the terminal device presents the timing interface can be as follows: Figure 13 The complete interface switching method shown can also be as follows: Figure 14 As shown, this is how the task interface is presented as a sub-interface.

[0144] In this approach, the frequency information in the time information of the task to be created is presented by repetitive evaluation configuration area, which refines the granularity of time information configuration, improves the time accuracy when the task to be created is executed, and enhances the feasibility of this solution.

[0145] Furthermore, when the user performs frequency information configuration operations for the aforementioned repetition rate configuration area, the terminal device may also execute the following possible implementation methods:

[0146] like Figure 15 As shown, in response to a frequency configuration operation triggered for a repetition frequency configuration area, the terminal device switches from a timing interface to a frequency interface, which includes at least one time period.

[0147] When the user needs to perform further configuration operations on the repetition frequency information, the corresponding frequency configuration operation can be triggered in the repetition frequency configuration area of ​​the timing interface. At this time, the terminal device will switch from the timing interface to the frequency interface in response to the frequency configuration operation. Figure 15 As shown, the frequency interface includes at least one time period.

[0148] Optionally, for these time periods, at least one of the following is included:

[0149] The first time period, with the calendar day as the unit of time;

[0150] The second time period, using the workday as the unit of time;

[0151] The third time cycle, with the week as the unit of time;

[0152] The fourth time cycle with months as the unit of time.

[0153] In this way, when performing frequency configuration operations, the user can select a desired time period as the target time period based on the different time periods presented in the frequency interface, and configure the corresponding frequency information.

[0154] After configuring the frequency information, the user object can trigger a periodic confirmation operation for the corresponding target time period, and the terminal device can then perform the following actions: Figure 16 As shown, in response to the periodic confirmation operation, the interface switches from the frequency interface to the timing interface, and the configured frequency information is displayed in the timing interface. The target time period is any one of at least one time period and is negatively correlated with the frequency information.

[0155] In one possible implementation, when the terminal device responds to a period confirmation operation triggered for a target time period in at least one time period, it may first switch from the frequency interface to the period selection interface, which includes at least one time point within a preset time range.

[0156] In this way, when faced with these time points, the user can select a target time point and trigger a confirmation operation for that time point, and the terminal device can then... Figure 17 As shown, switch from the period selection interface to the timer interface.

[0157] In this way, the terminal device can directly and quickly obtain the frequency information corresponding to the task to be created based on the target time point selected by the user, and present it in the timing interface.

[0158] Furthermore, as mentioned above, at least one time period can include multiple different time periods. Thus, when presenting the corresponding period selection interface for different time periods as target time periods, the content included can also be presented in multiple forms.

[0159] In Format 1, assuming the target time period is the aforementioned first time period, the period selection interface presented by the terminal device can be as follows: Figure 18 As shown, within a preset time range, at least one point in time is presented, using natural days as the unit of time; the specific number of time points included can be set according to actual application needs, and this application does not impose any restrictions on this. Figure 18 The example of 30 time points is used only for illustration and is not intended to be limiting.

[0160] For example Figure 18 The multiple time points shown allow users to select the desired target time point. For example, they can choose to select every day, every 3 days, or every 29 days. This way, starting from the first execution of the task to be created, the task can be executed once a day, every 3 days, or every 29 days.

[0161] In the second scenario, assuming the target time period is the second time period mentioned above, the period selection interface presented by the terminal device can be as follows: Figure 19 As shown, within a preset time range, at least one point in time is presented, using the calendar day as the unit of time. For example... Figure 19 The multiple time points shown allow users to select the desired target time point by sliding their fingers. For example, they can select every working day, every 3 working days, or every 10 working days. This way, starting from the first execution of the task to be created, the task can be executed once every working day, every 3 working days, or every 10 working days.

[0162] In the third scenario, assuming the target time period is the third time period mentioned above, the period selection interface presented by the terminal device can be as follows: Figure 20 As shown, within a preset time range, at least one point in time is presented, using weeks as the time unit; the specific number of time points included can be set according to actual application requirements, and this application does not impose any restrictions on this. Figure 20 The example of 12 time points is used only for illustration and is not intended to be limiting.

[0163] For example Figure 20The user can first select the time point in a week by sliding the slider. Then, in the period selection interface of the terminal device, multiple time points in a week are also displayed in calendar days (usually including: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday). The user can then select the time point in a calendar day according to their actual needs.

[0164] In this way, through two selection operations, the object is configured with the corresponding frequency information, and the terminal device can also obtain the exact configured frequency information.

[0165] Format four: Assuming the target time period is the fourth time period mentioned above, the period selection interface presented by the terminal device can be as follows: Figure 21 As shown, within a preset time range, at least one point in time is presented, using months as the unit of time; the specific number of time points included can be set according to actual application needs, and this application does not impose any restrictions on this. Figure 21 The example of 12 time points is used only for illustration and is not intended to be limiting.

[0166] For example Figure 21 As shown in Form 4, users can select the target time point through two selections. For example, first, they can select the time point with a month as the time unit by sliding; then, since the period selection interface of the terminal device also displays multiple time points within a month with natural days as the time unit (usually presented in the form of a calendar), users can select the time point with natural days as the time unit according to their actual needs.

[0167] It should be noted that the various forms of the cycle selection interface described above can be presented independently in different interfaces, or they can be presented through methods such as... Figure 22 As shown, it is integrated into a cycle selection interface.

[0168] Furthermore, such as Figure 23 As shown, in the period selection interface, when the user is selecting a target time point, the terminal device can also display the frequency information of the currently selected time point in real time.

[0169] In this approach, the terminal device presents a specific period selection interface, providing users with a precise time point selection interface. This allows the terminal device to quickly and efficiently obtain accurate frequency information, improving the feasibility and reliability of the solution.

[0170] In one possible implementation, in addition to the above-described configuration method for frequency information, when the terminal device presents the frequency interface, the content it contains can also be presented in the following manner:

[0171] like Figure 24 As shown, in the frequency interface, users can directly input the frequency information of the task to be created via a dialog box, using peripheral devices or handwriting input. The terminal device can then extract frequency-related information from the user's input using keyword extraction or a natural language processing model, and use this information as the corresponding frequency information. For example, a user can input in the dialog box: "Execute the errand task every Wednesday at 5 PM." The terminal device can then extract the corresponding frequency information from this input, namely: "Every Wednesday - 5 PM." Thus, the terminal device can... Figure 25 As shown, frequency information is displayed in this frequency interface.

[0172] Once the user obtains the frequency information in the frequency interface, it can also trigger a corresponding confirmation operation based on that frequency information, causing the terminal device to switch from the frequency interface to the timing interface, where the configured frequency information will be displayed.

[0173] In this way, users can directly input frequency information into the terminal device based on their own needs, without having to select the desired time point from multiple time points, reducing the user's operational costs and improving the user experience. On the other hand, using a natural language model to identify and extract the corresponding frequency information from the natural language input by the user also conforms to the user's living habits, further improving the user experience.

[0174] Furthermore, in the frequency interface, such as Figure 26 As shown, in addition to at least one time period, it may further include: a non-repeating control, and a non-repeating confirmation operation triggered by the non-repeating control can enable the terminal device to directly respond to the non-repeating confirmation operation, switch from the frequency interface to the timer interface, and determine that the task to be created does not need to be executed repeatedly.

[0175] In one possible implementation, the timing interface presented by the terminal device may further include, in addition to the repetition frequency configuration area, an end time configuration area and / or an execution time configuration area.

[0176] like Figure 27 As shown, in the timing interface, the end time configuration area, the execution time configuration area, and the repetition frequency configuration area can all be presented side by side. Figure 27The method shown is merely for illustration. In practical applications, the repetition frequency configuration area, the end time configuration area, and the execution time configuration area can all be selectively presented in the timing interface according to actual needs.

[0177] The end time configuration area includes: the end information that controls the end time of the task to be created, as mentioned above;

[0178] The execution time configuration area includes: the end information that controls the execution time of the task to be created, as mentioned above.

[0179] Optionally, when the user triggers an end-time configuration operation for the end-time configuration region, the terminal device may respond to the end-time configuration operation by performing the following actions:

[0180] Specifically, such as Figure 28 As shown, in response to the end time configuration operation triggered for the end time configuration area, the terminal device presents the end time interface as a sub-interface in the timing interface. The end time interface includes a time confirmation control and a count confirmation control.

[0181] The time confirmation control is used to configure the end time of the task to be created. Specifically, the configuration interface and process for the end time can refer to the configuration process for at least one time period described above. The terminal device can present the corresponding selection content through the period selection interface corresponding to the first or second time period, allowing the user to select whether to end the execution of the task to be created in 7 days or 10 calendar days; or, through the period selection interface corresponding to the third or fourth time period, allowing the user to select whether to end the execution of the task to be created on the Saturday of 4 weeks later or the 15th of 2 months later; or, through a dialog box, the user can directly input that the task to be created will end on February 2, 2022, etc. This application will not elaborate on or limit these options.

[0182] The execution count confirmation control is used to configure the number of times the task to be created will be executed, and this number of executions controls the end time of the task. For example, such as... Figure 29 As shown, for the count confirmation control, the terminal device can switch from the end time interface to the count configuration interface in response to the trigger operation of the count confirmation control. In the count configuration interface, the user can select a target count that meets the user's expectations from the preset count range by sliding. Alternatively, in the count configuration interface, the user can also directly input the expected target count into the terminal device through a dialog box for the terminal device to obtain.

[0183] Thus, after the above configuration operations regarding the technical time, the terminal device can be used as follows: Figure 30 As shown, in response to an end time confirmation operation triggered by the time confirmation control, the device switches from the end time interface to the timer interface; alternatively, the terminal device can... Figure 31 As shown, in response to the end count confirmation operation triggered by the count confirmation control, the interface switches from the end time interface to the timer interface.

[0184] In this way, by configuring the end time through the above methods, the information on the repeated execution of the task to be created can be configured flexibly and accurately, thereby meeting the actual needs of the users and providing the corresponding information basis for server resource configuration, thus improving the effectiveness of server resource configuration.

[0185] On the other hand, the terminal device can also perform an execution time confirmation process in response to an execution time configuration operation targeting the execution time configuration region. For example, such as... Figure 32 As shown, the terminal device can respond to the execution time configuration operation by presenting the execution time interface as a sub-interface in the timing interface, allowing the user to configure the corresponding execution time in this interface. For example, the user can configure the execution time to 15:00 on the execution day. In this way, each time the task to be created is repeatedly executed, the operation on the task to be created can be precisely performed at 15:00 on the execution day.

[0186] The above describes the relevant content of the timer control in the task creation process provided in this application. The following will continue to introduce other steps in the task creation process:

[0187] For a task to be created, in addition to the time information for the repeated execution of the task, it will also include the content information corresponding to the task. As mentioned earlier, the content information may include item information, location information, contact information, etc.

[0188] Therefore, in one possible implementation, when the terminal device switches from the timed interface to the task interface in response to an information confirmation operation triggered by time information, the following method can also be executed:

[0189] like Figure 33 As shown, when the terminal device switches from the timed interface to the task interface, a content configuration interface can be presented in the form of a sub-interface in the task interface. The content configuration interface includes: at least one type of item to be configured, and the corresponding content information.

[0190] Before the content configuration interface is displayed, users can first select the types of items related to the task to be created in the task interface according to their own needs. For example, Figure 34 As shown, the terminal device can present different types of items on the task interface, such as: food, documents, daily necessities, clothing, cakes, flowers, fresh fruits, medicine, digital products, furniture, auto parts, and others. After the user selects at least one item type, the terminal device can present a corresponding content configuration interface in the form of a sub-interface based on the user's selection. In this content configuration interface, options can be selected as follows: Figure 35 As shown, at least one type of item to be configured is presented using the object selection, and its corresponding content information, including volume, weight, etc.

[0191] Once the user has completed the configuration of the content information, they can perform a content confirmation operation triggered for the target item type, switching from the content configuration interface to the task interface.

[0192] In this way, once the terminal device obtains the time and content information of the task to be created, it can complete the task creation process corresponding to the task to be created.

[0193] In one possible implementation, to improve the user experience and enable users to experience the repetitive execution of the task to be created more seamlessly, the terminal device may further perform the following operations:

[0194] Before presenting the creation completion information of the task to be created, the terminal device may also present a resource conversion confirmation interface, which includes: resource conversion information that the task to be created needs to perform each time it is executed.

[0195] like Figure 36 As shown, the resource conversion confirmation interface displayed on the terminal device provides users with resource conversion information that needs to be performed each time a task to be created is executed. Users can choose to have resource conversion performed automatically each time the task is executed, or they can choose to confirm the resource conversion themselves each time.

[0196] Once the terminal device receives a confirmation operation triggered by the resource conversion information, it can respond to the confirmation operation and present the creation completion information of the task to be created.

[0197] In this way, when the user selects to automatically perform resource conversion, the terminal device can automatically repeat the above-mentioned task to be created multiple times and provide the user with a seamless user experience, thereby avoiding the tedious operation of the user having to create the same task multiple times.

[0198] Using the above methods, the terminal device can complete the creation process for the task to be created. Furthermore, when the user needs to stop a repetitive task midway, the terminal device can perform the following operations.

[0199] Specifically, such as Figure 37 As shown, the terminal device can present a task interface, which also includes: created controls; then, in response to a space confirmation operation triggered for the created controls, the terminal device switches from the task interface to a management interface, which includes: at least one created task that is being repeatedly executed.

[0200] For created tasks that are currently being executed repeatedly, the user object can select one or more of them to stop execution based on its own needs. Once the user object makes its selection, the terminal device can respond to the task shutdown operation triggered for the target created task, such as... Figure 38 As shown, the task completion information corresponding to the target created task is displayed. The target created task refers to any one of at least one created task. It should be noted that when the completion operation for a created task is completed, the resource conversion associated with that created task will also be closed simultaneously.

[0201] In this way, the terminal device can complete the termination operation for the created task. Based on this operation, the user can stop the repetitive execution of the created task at any time according to their own needs, thus improving the reliability of the solution.

[0202] The above describes several possible implementation methods for the creation and termination of tasks to be created. Furthermore, during the repeated execution of already created tasks, the terminal device can also perform the following operations:

[0203] In one possible implementation, the terminal device can present a corresponding reminder message to the user during a preset time period before each execution of a created task, reminding the user that the task will be executed at the predetermined time. For example, the terminal device can choose from various methods to present the reminder message, such as... Figure 39 As shown, notifications can be sent via SMS, email, or app message.

[0204] On the other hand, when terminal devices or servers execute the aforementioned tasks that need to be repeated, these devices can do so in the following ways.

[0205] Taking errand-running functionality as an example, when a terminal device or server needs to provide a convenient way for users to periodically perform errand-running tasks, the terminal device or server can be based on, for example... Figure 40The diagram shown illustrates the implementation of this errand-running function.

[0206] The architecture includes business service layers, public middleware services, designated public services, middleware, infrastructure, R&D platform, and service providers.

[0207] The business service layer includes a core service and a errand-running provider access service. The core service is used to implement the core logic of the errand-running function, while the errand-running provider access service is used to adapt and normalize the interfaces of different providers.

[0208] The public middleware service includes: identifier generation service, outreach service, gateway, authorization, account service, mini-program gateway, etc., which are used to provide the basic functions required for the implementation of the errand-running function.

[0209] The designated public services include map open platforms, resource exchange services, and SMS services, which are used to obtain the current location and perform functions such as route calculation.

[0210] The middleware includes message queue components, databases, cache components, etc., to implement core data storage, business data caching, distributed locks and other functions.

[0211] In one possible implementation, when the terminal device repeatedly executes the task to be created after the completion of task creation, it can be done in the following way:

[0212] First, it should be noted that when the terminal device presents the creation completion information corresponding to the task to be created, the creation completion information may include: the task identifier corresponding to the task to be created; wherein, the task identifier can be represented by a string or by a numeric symbol, and this application does not limit it in this regard.

[0213] After the terminal device completes the task creation for the task to be created, the time and content information related to the task to be created can be stored in the database. Then, distributed scheduled tasks and message queues can be used to manage the execution of the task, and the system performance overhead can be reduced by delaying messages.

[0214] Specifically, based on the time information corresponding to the task to be created, the following operations can be performed each time the task to be created is executed:

[0215] See Figure 41 This is a flowchart illustrating a task creation method provided in an embodiment of this application. Figure 2 ,like Figure 41 As shown, the specific steps of this method are as follows:

[0216] Step S4101: Based on the task identifier corresponding to the task to be created and the next execution time corresponding to the task to be created, obtain the execution identifier corresponding to the current execution of the task to be created; wherein, the execution identifier is used to: uniquely represent the execution record information of the task to be created.

[0217] Since the task to be created needs to be executed repeatedly, in order to ensure that the task to be created will only be executed once within a repetition cycle, the execution identifier corresponding to the execution record information can be obtained first, as shown in step S4101.

[0218] For example, the terminal device can obtain the execution identifier in the following way: obtain the task identifier corresponding to the task to be created (assuming that the task identifier is a string of a fixed length) and the time when the task will be executed again (e.g., 2022.02.09.17:00), then perform a hash operation on the sum of the two strings to obtain the corresponding digest value, and use the digest value as the execution identifier.

[0219] Thus, the execution identifier can uniquely identify the execution record information of the task to be created in this execution.

[0220] Step S4102: Based on the execution identifier, acquire the corresponding task execution distributed lock so that the task to be created is executed by a single thread during this execution.

[0221] By using the execution identifier that uniquely identifies the execution record information for this execution, the terminal device can acquire the corresponding task execution distributed lock, so that the current execution process of the task to be created can be executed by a unique thread on a unique machine in the global scope, thereby ensuring that the task is executed only once at the same time in the global scope.

[0222] Step S4103: After the single thread finishes executing the task to be created, release the task execution distributed lock.

[0223] Once this execution is complete, the distributed lock for the task execution can be released, so that the task to be created can be executed again next time.

[0224] By using the above methods, we can ensure that tasks that need to be executed repeatedly can be executed only once globally at any given time, thus ensuring the uniqueness of task execution.

[0225] The following example illustrates the process of executing a task created using the above method.

[0226] For example, the terminal device or server can first acquire a distributed lock for task execution, and then scan to obtain the task execution record table of those tasks that are about to be executed. In this way, when re-executing an already created task, the following operations can continue:

[0227] First, an execution identifier corresponding to the execution record information is generated. This execution record information is used to record the steps and data when the terminal device executes the created task. Based on the execution identifier, the corresponding task execution distributed lock is obtained to ensure that the task is executed by a single thread.

[0228] Next, it is determined whether the execution record information corresponding to the above-generated execution identifier exists in the task execution record table. If it exists, the current execution ends; if it does not exist, the task corresponding to the current task execution record continues to be executed.

[0229] During this task execution, the terminal device can initialize the execution record information corresponding to this execution, then update the next execution time of the task in the task execution record table, and then send the execution record information to the message queue to obtain the execution status of the task;

[0230] Finally, based on the execution status of the task, the execution status in the task execution record table is updated. When the execution status indicates that the task has been successfully executed, the previously acquired task execution distributed lock can be released, thereby completing the execution of this recurring task.

[0231] Thus, by using a unique identifier that can uniquely represent the task execution record, along with the record's execution status and update time, the terminal device or server can ensure idempotency when the task is executed repeatedly. In other words, it can ensure that the result is the same each time the task is executed repeatedly. On the other hand, using a distributed lock ensures that the task is executed only once globally at any given time, avoiding errors such as abnormal repeated execution. Furthermore, using a task execution record table to record the task's execution status ensures that the scheduled task settings and the status of the task execution record are correct during task execution, preventing erroneous task execution.

[0232] Furthermore, when a near-delayed task is delivered to the message queue, the terminal device or server can view the delayed messages in the message queue to obtain relevant information records about task execution.

[0233] Specifically, when a message related to a nearby delayed task is received in the message queue, the system can determine whether the task is valid and whether it is in an executable state based on the contents of the task execution record table corresponding to the execution record information. If it is determined to be valid and executable, the task corresponding to the execution record information can be executed, and the execution result feedback can be received.

[0234] When the received result feedback indicates that the execution was successful, the task execution status recorded in the task execution record table can be updated, and then the corresponding confirmation information can be sent so that the terminal device can release the task execution distributed lock based on the confirmation information.

[0235] When the received feedback indicates that the execution has failed, the terminal device or server can re-execute the task until the feedback indicates that the execution has succeeded, or the number of re-executions exceeds the preset number.

[0236] The above describes the task creation method proposed in this application and its various possible implementation methods. It should be noted that the above-mentioned various possible implementation methods can be implemented in different combinations. For ease of understanding, an example will be used below to introduce one possible combination method.

[0237] like Figure 42 As shown, when a user needs to create a recurring errand-running task, the terminal device can present a task interface for the user to configure time and content information. Then, in response to an operation triggered by the timer control, a timer interface is presented, and in response to a frequency configuration operation triggered by the user targeting the repetition frequency configuration area, a frequency interface is presented. In the frequency interface, the user can trigger an operation targeting a third time period, causing the terminal device to present a period selection interface. This allows the user to select the target time point and complete the frequency information configuration.

[0238] Furthermore, the user object can be configured with end time and execution time, and then with the content information of the task to be created, so as to complete the creation of the task.

[0239] Based on the same inventive concept, embodiments of this application provide a task creation apparatus capable of implementing the functions corresponding to the aforementioned task creation method. Please refer to... Figure 43 The device includes a first display unit 4301, a second display unit 4302, a third display unit 4303, and a fourth display unit 4304, wherein:

[0240] First display unit 4301: used to present the task interface, which includes: a timer control corresponding to the task to be created;

[0241] Second display unit 4302: In response to a time configuration operation triggered by a timer control, switch from the task interface to the timer interface. The timer interface includes: time information for controlling the repeated execution of the task to be created.

[0242] The third display unit 4303 is used to switch from the timed interface to the task interface in response to the information confirmation operation triggered by the time information. The task interface also includes the content information corresponding to the task to be created.

[0243] The fourth display unit 4304 is used to respond to the task submission operation triggered by the content information and present the creation completion information of the task to be created.

[0244] In one possible embodiment, the second display unit is used to switch from the task interface to the timing interface, specifically for:

[0245] Switch from the task interface to the timer interface, where the repetition frequency configuration area is displayed;

[0246] The repetition frequency configuration area includes: frequency information within the time information, which controls the repetition frequency of the task to be created.

[0247] In one possible embodiment, the second display unit is further configured to:

[0248] In response to a frequency configuration operation triggered for a repetition frequency configuration area, the system switches from a timing interface to a frequency interface, the frequency interface including: at least one time period; the at least one time period including at least one of the following: a first time period with a calendar day as the time unit; a second time period with a working day as the time unit; a third time period with a week as the time unit; a fourth time period with a month as the time unit;

[0249] In response to a periodic confirmation operation triggered for a target time period, the system switches from the frequency interface to the timing interface and displays the configured frequency information in the timing interface; wherein the target time period is any one of at least one time period and is negatively correlated with the frequency information.

[0250] In one possible embodiment, the second display unit, in response to a periodic confirmation operation triggered for a target time period, switches from the frequency interface to the timing interface, specifically for:

[0251] In response to a periodic confirmation operation triggered for a target time period, the frequency interface is switched to the period selection interface, which includes at least one time point within a preset time range.

[0252] In response to a time confirmation operation triggered for a target time point, switch from the period selection interface to the timer interface; the target time point can be any one of at least one time point.

[0253] In one possible embodiment, the timing interface further includes: an end time configuration area and an execution time configuration area; wherein,

[0254] The end time configuration area includes: end information within the time information section, which controls the end time of the task to be created;

[0255] The execution time configuration area includes: execution information that controls the execution time of the task to be created.

[0256] In one possible embodiment, the second display unit is further configured to:

[0257] In response to an end time configuration operation triggered for the end time configuration area, the end time interface is presented as a sub-interface in the timer interface. The end time interface includes: time confirmation control and count confirmation control.

[0258] In response to an end time confirmation operation triggered by a time confirmation control, switch from the end time interface to the timer interface; or, in response to an end count confirmation operation triggered by a count confirmation control, switch from the end time interface to the timer interface.

[0259] In one possible embodiment, after presenting the creation completion information of the task to be created, the fourth display unit is further configured to:

[0260] The task interface is displayed, which also includes: created controls;

[0261] In response to a control confirmation operation triggered for a created control, the interface switches from the task interface to the management interface, which includes at least one created task that is being executed repeatedly.

[0262] In response to a task closure operation triggered for a target created task, the task completion information corresponding to the target created task is presented; wherein, the target created task is any one of at least one created task.

[0263] In one possible implementation, the creation completion information includes: a task identifier corresponding to the task to be created; then, after presenting the creation completion information of the task to be created, the fourth display unit is further used for:

[0264] Based on the time information corresponding to the task to be created, perform the following operations each time the task to be created is executed:

[0265] Based on the task identifier and the next execution time corresponding to the task to be created, obtain the execution identifier corresponding to the task to be created in this execution; wherein, the execution identifier is used to: uniquely identify the execution record information of the task to be created in this execution;

[0266] Based on the execution identifier, acquire the corresponding task execution distributed lock so that the task to be created is executed by a single thread during this execution.

[0267] After the single thread finishes executing the task to be created, the task execution distributed lock is released.

[0268] Please refer to Figure 44 This is a computer device 4400 provided in the embodiments of this application. The computer device 4400 can, for example, be... Figure 3 The terminal 301 or server 302 in the system. The current and historical versions of the data storage program and the application software corresponding to the data storage program can be installed on the computer device 4400, which includes a processor 4480 and a memory 4420. In some embodiments, the computer device 4400 may include a display unit 4440, which includes a display panel 4441 for displaying a user-interactive interface, etc.

[0269] In one possible embodiment, the display panel 4441 may be configured in the form of a liquid crystal display (LCD) or an organic light-emitting diode (OLED).

[0270] The processor 4480 is used to read a computer program and then execute the methods defined by the computer program. For example, the processor 4480 reads a data storage program or file, thereby running the data storage program on the computer device 4400 and displaying the corresponding interface on the display unit 4440. The processor 4480 may include one or more general-purpose processors, and may also include one or more DSPs (Digital Signal Processors) for performing related operations to implement the technical solutions provided in the embodiments of this application.

[0271] The memory 4420 generally includes main memory and secondary storage. Main memory can be random access memory (RAM), read-only memory (ROM), and cache, etc. Secondary storage can be a hard disk, optical disk, USB flash drive, floppy disk, or tape drive, etc. The memory 4420 is used to store computer programs and other data. The computer programs include applications corresponding to each client, and other data may include data generated after the operating system or applications are run, including system data (e.g., operating system configuration parameters) and user data. In this embodiment, the computer program is stored in the memory 4420, and the processor 4480 executes the computer program in the memory 4420 to implement any of the methods described in the preceding figures.

[0272] The aforementioned display unit 4440 is used to receive input digital information, character information, or contact touch operations / non-contact gestures, and to generate signal inputs related to user settings and function control of the computer device 4400. Specifically, in this embodiment, the display unit 4440 may include a display panel 4441. The display panel 4441, for example, is a touch screen, which can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or on the display panel 4441), and drive corresponding connection devices according to a pre-set program.

[0273] In one possible embodiment, the display panel 4441 may include two parts: a touch detection device and a touch controller. The touch detection device detects the player's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 4480. It can also receive and execute commands from the processor 4480.

[0274] The display panel 4441 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the display unit 4440, in some embodiments, the computer device 4400 may also include an input unit 4430. The input unit 4430 may include an image input device 4431 and other input devices 4432, wherein the other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick.

[0275] In addition to the above, the computer device 4400 may also include a power supply 4490 for powering other modules, an audio circuit 4460, a near-field communication module 4470, and an RF circuit 4410. The computer device 4400 may also include one or more sensors 4450, such as an accelerometer, a light sensor, a pressure sensor, etc. The audio circuit 4460 specifically includes a speaker 4461 and a microphone 4462, for example, the computer device 4400 can use the microphone 4462 to collect the user's voice and perform corresponding operations.

[0276] As one embodiment, the number of processors 4480 can be one or more, and the processors 4480 and the memory 4420 can be coupled together or relatively independent.

[0277] As one example, Figure 44 The processor 4480 in the middle can be used to implement, for example Figure 43The functions of the first display unit 4301, the second display unit 4302, the third display unit 4303, and the fourth display unit 4304.

[0278] As one example, Figure 44 The processor 4480 in the document can be used to implement the functions of the server or terminal devices discussed above.

[0279] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by a computer program. The aforementioned computer program can be stored in a computer-readable storage medium. When the computer program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0280] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to the prior art, can be embodied in the form of software products, for example, through computer program products. These computer program products are stored in a storage medium and include computer programs used to cause a computer device to execute all or part of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0281] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for creating a task, characterized in that, The method includes: A task interface is presented, which includes a timer control corresponding to the task to be created. In response to a time configuration operation triggered by the timer control, the task interface is switched to the timer interface, which includes time information for controlling the repeated execution of the task to be created. In response to an information confirmation operation triggered by the time information, the system switches from the timed interface to the task interface, which further includes: content information corresponding to the task to be created; In response to a task submission operation triggered by the content information, the creation completion information of the task to be created is displayed.

2. The method as described in claim 1, characterized in that, The switching from the task interface to the timed interface includes: The user switches from the task interface to the timing interface, where a repetition frequency configuration area is displayed. The repetition frequency configuration area includes: frequency information that controls the repetition frequency of the task to be created, within the time information.

3. The method as described in claim 2, characterized in that, The method further includes: In response to a frequency configuration operation triggered for the repetition frequency configuration area, the system switches from the timing interface to the frequency interface, the frequency interface including: at least one time period; wherein the at least one time period includes at least one of the following: a first time period with a calendar day as the time unit; a second time period with a working day as the time unit; a third time period with a week as the time unit; and a fourth time period with a month as the time unit. In response to a periodic confirmation operation triggered for a target time period, the system switches from the frequency interface to the timing interface and displays the configured frequency information in the timing interface; wherein the target time period is any one of the at least one time period and is negatively correlated with the frequency information.

4. The method as described in claim 3, characterized in that, In response to a periodic confirmation operation triggered for a target time period, switching from the frequency interface to the timing interface includes: In response to a period confirmation operation triggered for the target time period, the frequency interface is switched to a period selection interface, which includes at least one time point within a preset time range. In response to a time point confirmation operation triggered for a target time point, the system switches from the period selection interface to the timing interface; the target time point is any one of the at least one time point.

5. The method as described in claim 2, characterized in that, The timing interface further includes: an end time configuration area and an execution time configuration area; wherein... The end time configuration area includes: end information that controls the end time of the task to be created in the time information; The execution time configuration area includes: execution information that controls the execution time of the task to be created, within the time information.

6. The method as described in claim 5, characterized in that, The method further includes: In response to an end time configuration operation triggered for the end time configuration area, an end time interface is presented in the timed interface as a sub-interface, the end time interface including: a time confirmation control and a count confirmation control; In response to an end time confirmation operation triggered by the time confirmation control, the system switches from the end time interface to the timer interface; or, in response to an end count confirmation operation triggered by the count confirmation control, the system switches from the end time interface to the timer interface.

7. The method according to any one of claims 1-6, characterized in that, After presenting the creation completion information of the task to be created, the method further includes: The task interface is presented, and the task interface also includes: created controls; In response to a control confirmation operation triggered for the created control, the interface switches from the task interface to the management interface, which includes at least one created task that is being repeatedly executed. In response to a task closure operation triggered for a target created task, task completion information corresponding to the target created task is presented; wherein the target created task is any one of the at least one created task.

8. The method according to any one of claims 1-6, characterized in that, The creation completion information includes: the task identifier corresponding to the task to be created; therefore, after presenting the creation completion information of the task to be created, the method further includes: Based on the time information corresponding to the task to be created, the following operations are performed each time the task to be created is executed: Based on the task identifier and the next execution time corresponding to the task to be created, the execution identifier corresponding to the current execution of the task to be created is obtained; wherein, the execution identifier is used to: uniquely identify the execution record information of the current execution of the task to be created; Based on the execution identifier, the corresponding task execution distributed lock is acquired so that the task to be created is executed by a single thread during this execution. After the single thread completes the task to be created, the task execution distributed lock is released.

9. A task creation apparatus, characterized in that, include: First display unit: used to present the task interface, which includes: a timer control corresponding to the task to be created; The second display unit is used to switch from the task interface to the time interface in response to a time configuration operation triggered by the timer control. The timer interface includes time information for controlling the repeated execution of the task to be created. The third display unit is used to switch from the timed interface to the task interface in response to an information confirmation operation triggered by the time information. The task interface also includes: content information corresponding to the task to be created. The fourth display unit is used to respond to a task submission operation triggered by the content information and present the creation completion information of the task to be created.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-8.

11. A computer device, characterized in that, include: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method as described in any one of claims 1-8 according to the obtained program instructions.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform the method as described in any one of claims 1-8.

Images