Timing task configuration method and device

By maintaining the correspondence between task names and identifiers on the terminal device, responding to the update information of the configuration center, and automatically processing the configuration of timing tasks, the problem of low efficiency in timing task configuration in the existing technology is solved, and efficient timing task management is achieved .

CN118939389APending Publication Date: 2024-11-12ZHEJIANG ZEEKR INTELLIGENT TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310537324.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-10
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The configuration efficiency of timing tasks in the prior art is low, and technicians are required to develop interfaces and adjust scheduling strategies, resulting in cumbersome deployment and reconfiguration processes.

Method used

By maintaining the correspondence between custom task names and timing task identifiers on the terminal device, responding to the update information of the configuration center, obtaining the configuration information of the target timing task, determining whether the timing task identifier indicates update, and deleting or adding the corresponding timing task , realize automated configuration.

Benefits of technology

It improves the configuration efficiency of timing tasks, reduces the operational needs of technicians in the configuration center, realizes the automatic configuration of timing tasks, and avoids repeated development and scheduling strategy adjustments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939389A_ABST
    Figure CN118939389A_ABST
Patent Text Reader

Abstract

The invention provides a timed task configuration method and device. The method is applied to terminal equipment. The terminal equipment maintains a corresponding relationship between a custom task name and a timed task identifier of a timed task deployed on the terminal equipment; the timed task identifier is used for indicating the timed task; the method comprises the steps of obtaining configuration information corresponding to a target timed task contained in task configuration in response to update information of task configuration which is maintained for a configuration center and corresponds to the timed task; the configuration information comprises a target custom task name corresponding to the target timed task; based on the corresponding relationship, determining a timed task identifier corresponding to the target custom task name, and determining whether a timed task deployed on the terminal equipment indicated by the timed task identifier is updated relative to the target timed task; and if yes, deleting the timed task, and adding a target timed task corresponding to the configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device and machine-readable storage medium for configuring a scheduled task. Background Art

[0002] Scheduled tasks refer to a type of tasks that are scheduled and executed according to custom time rules. In current technology, when deploying a new scheduled task, it is necessary to develop a corresponding scheduled task interface and deploy the scheduled task based on the interface; and when it is necessary to reconfigure the deployed scheduled task, the technicians need to readjust the scheduling strategy of the scheduled task or cancel the scheduled task, resulting in low efficiency in the configuration of scheduled tasks. Summary of the invention

[0003] The present application provides a scheduled task configuration method, which is applied to a terminal device; the terminal device maintains a correspondence between a custom task name of a scheduled task deployed on the terminal device and a scheduled task identifier; wherein the scheduled task identifier is used to indicate the scheduled task; the method comprises:

[0004] In response to update information of a task configuration corresponding to the scheduled task maintained by a configuration center, obtaining configuration information corresponding to a target scheduled task contained in the task configuration; the configuration information includes a target custom task name corresponding to the target scheduled task;

[0005] Based on the corresponding relationship, determine the scheduled task identifier corresponding to the target custom task name, and determine whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task; if so, delete the scheduled task and add the target scheduled task corresponding to the configuration information.

[0006] Optionally, the scheduled task identifier includes a handle object used to indicate the scheduled task.

[0007] Optionally, before determining the scheduled task identifier corresponding to the target custom task name based on the corresponding relationship, the method further includes:

[0008] Determine whether the corresponding relationship contains the target custom task name;

[0009] If yes, further determining a scheduled task identifier corresponding to the target custom task name based on the corresponding relationship;

[0010] If not, add a target scheduled task corresponding to the configuration information.

[0011] Optionally, the terminal device supports the Spring framework; the configuration information further includes a calling method name corresponding to the target scheduled task;

[0012] Before adding the target scheduled task corresponding to the configuration information, the method further includes:

[0013] Based on the calling method name, determining whether the Spring framework supports the calling method corresponding to the calling method name;

[0014] If yes, further add a target scheduled task corresponding to the configuration information.

[0015] Optionally, the configuration information further includes a target custom time rule; the target custom time rule is used to define the execution time strategy of the scheduled task;

[0016] The determining whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task includes:

[0017] Matching the custom time rule in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rule corresponding to the target scheduled task;

[0018] Determine whether the scheduled task is updated based on the matching result.

[0019] Optionally, the method further includes:

[0020] Obtaining a target scheduled task identifier corresponding to the target scheduled task;

[0021] In the correspondence, a correspondence between the target scheduled task identifier and the target custom task name is added.

[0022] The present application also provides an electronic device, comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are interconnected via the bus;

[0023] The memory stores machine-readable instructions, and the processor executes the scheduled task configuration method by calling the machine-readable instructions.

[0024] The present application also provides a machine-readable storage medium, which stores machine-readable instructions. When the machine-readable instructions are called and executed by a processor, the scheduled task configuration method is implemented.

[0025] The technical solution provided by this application may at least include the following beneficial effects:

[0026] Through the above embodiments, the terminal device can obtain the configuration information corresponding to the target scheduled task contained in the task configuration by responding to the update information of the task configuration corresponding to the scheduled task maintained by the configuration center; since the terminal device maintains the corresponding relationship between the custom task name and the scheduled task identifier of the scheduled task deployed on the terminal device, the terminal device can determine the scheduled task identifier corresponding to the target custom task name based on the corresponding relationship, and the positioning task identifier is used to indicate the scheduled task deployed on the terminal device, and the terminal device can determine whether the scheduled task indicated by the scheduled task identifier is updated relative to the target scheduled task, and when it is determined that the scheduled task is updated, delete the scheduled task and add the target scheduled task corresponding to the configuration information. Therefore, when it is necessary to add a new scheduled task or reconfigure the scheduled task already deployed in the terminal device, it is only necessary for the technician to add or modify the corresponding configuration information in the configuration center, and the terminal device can complete the subsequent configuration process according to the update of the configuration information, without the need for the technician to simultaneously develop an interface corresponding to the scheduled task or for the technician to readjust the task scheduling strategy for the scheduled task, thereby realizing the automatic configuration of the scheduled task and improving the efficiency of the scheduled task configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 The figure is a flowchart of a method for configuring a scheduled task, shown in an exemplary embodiment.

[0028] Figure 2 The figure is a flowchart of another method for configuring a scheduled task according to an exemplary embodiment.

[0029] Figure 3 The figure is a hardware structure diagram of an electronic device where a timed task configuration device is located, showing an exemplary embodiment.

[0030] Figure 4 It is a block diagram of a timed task configuration device shown in an exemplary embodiment. DETAILED DESCRIPTION

[0031] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0032] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0033] Scheduled tasks refer to a type of tasks that are scheduled and executed through user-defined time rules. In current technology, common scheduled tasks need to be deployed independently. Since adding a new scheduled task requires technicians to develop a scheduled task interface corresponding to the scheduled task and deploy the scheduled task in the terminal device based on the scheduled task interface, the deployment process of scheduled tasks is relatively cumbersome. When it is necessary to reconfigure the scheduled task that has been deployed in the terminal device, the technicians need to readjust the task scheduling strategy for the scheduled task or cancel the scheduled task, resulting in low efficiency in the configuration of scheduled tasks.

[0034] In view of this, the present application aims to propose a method for configuring a scheduled task. The method completes automatic configuration of the scheduled task by responding to update information of the task configuration of the scheduled task by the configuration center and determining whether the scheduled task deployed on the terminal device is updated relative to the target scheduled task included in the task configuration.

[0035] When implemented, the method is applied to a terminal device; the terminal device maintains a correspondence between a custom task name and a timed task identifier of a timed task deployed on the terminal device; wherein the timed task identifier is used to indicate the timed task; the terminal device can obtain configuration information corresponding to a target timed task contained in the task configuration in response to update information of a task configuration corresponding to the timed task maintained by a configuration center; the configuration information includes a target custom task name corresponding to the target timed task;

[0036] Furthermore, the terminal device can determine the scheduled task identifier corresponding to the target custom task name based on the corresponding relationship, and determine whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task; if so, delete the scheduled task and add the target scheduled task corresponding to the configuration information.

[0037] Through the above embodiments, the terminal device can obtain the configuration information corresponding to the target scheduled task contained in the task configuration by responding to the update information of the task configuration corresponding to the scheduled task maintained by the configuration center; since the terminal device maintains the corresponding relationship between the custom task name and the scheduled task identifier of the scheduled task deployed on the terminal device, the terminal device can determine the scheduled task identifier corresponding to the target custom task name based on the corresponding relationship, and the positioning task identifier is used to indicate the scheduled task deployed on the terminal device, and the terminal device can determine whether the scheduled task indicated by the scheduled task identifier is updated relative to the target scheduled task, and when it is determined that the scheduled task is updated, delete the scheduled task and add the target scheduled task corresponding to the configuration information. Therefore, when it is necessary to add a new scheduled task or reconfigure the scheduled task already deployed in the terminal device, it is only necessary for the technician to add or modify the corresponding configuration information in the configuration center, and the terminal device can complete the subsequent configuration process according to the update of the configuration information, without the need for the technician to simultaneously develop an interface corresponding to the scheduled task or for the technician to readjust the task scheduling strategy for the scheduled task, thereby realizing the automatic configuration of the scheduled task and improving the efficiency of the scheduled task configuration.

[0038] The present application is described below through specific embodiments and in combination with specific application scenarios.

[0039] See also Figure 1 , Figure 1 FIG. 1 is a flowchart of a method for configuring a scheduled task according to an exemplary embodiment. Figure 1 As shown, the method can be applied to a terminal device; the terminal device can maintain a corresponding relationship between a custom task name of a scheduled task deployed on the terminal device and a scheduled task identifier; wherein the scheduled task identifier can be used to indicate the scheduled task;

[0040] At least one scheduled task can be deployed on the terminal device, and a custom task name corresponding to any scheduled task in the at least one scheduled task and a scheduled task identifier corresponding to any scheduled task can be maintained, and the scheduled task identifier can be used to indicate any scheduled task.

[0041] Based on the terminal device maintaining the corresponding relationship, the method may include the following steps:

[0042] Step 102, in response to update information of the task configuration corresponding to the scheduled task maintained by the configuration center, obtain configuration information corresponding to the target scheduled task contained in the task configuration; the configuration information includes a target custom task name corresponding to the target scheduled task.

[0043] The terminal device may be equipped with a configuration center, wherein the configuration center may refer to a basic service component for uniformly managing configurations of various applications. In practical applications, the configuration center may maintain task configurations related to scheduled tasks, and the task configurations may include at least one task configuration of a scheduled task. The task configurations maintained by the configuration center may be updated through the configuration center, and the configuration center may generate update information for updating the task configurations.

[0044] For example, when a user updates the task configuration of the scheduled task through the configuration center, the configuration center can generate update information corresponding to the task configuration. The terminal device can respond to the update information and obtain configuration information corresponding to any target scheduled task in at least one scheduled task included in the task configuration.

[0045] It should be noted that the updating of the task configuration corresponding to the scheduled task may be to add a custom scheduled task to the task configuration, or to update the task configuration corresponding to the scheduled task in the task configuration that has been deployed on the terminal device.

[0046] This specification does not limit how the terminal device responds to the update information. For example, monitoring of the task configuration for the scheduled task can be added in the configuration center. When the configuration center generates update information corresponding to the task configuration, the terminal device can respond to monitoring the update information and obtain the configuration information corresponding to any target scheduled task in at least one scheduled task included in the task configuration.

[0047] In one illustrated implementation, the scheduled task identifier includes a handle object for indicating the scheduled task.

[0048] For example, the terminal device may maintain a correspondence between a custom task name of a scheduled task deployed on the terminal device and a handle object used to indicate the scheduled task.

[0049] Step 104, based on the corresponding relationship, determine the scheduled task identifier corresponding to the target custom task name, and determine whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task; if so, delete the scheduled task and add the target scheduled task corresponding to the configuration information.

[0050] The scheduled task identifier may be used to indicate the scheduled task deployed on the terminal device. The scheduled task deployed on the terminal device and corresponding to the scheduled task identifier may be determined through the scheduled task identifier.

[0051] For example, the terminal device can determine the scheduled task identifier corresponding to the target custom task name based on the maintained correspondence, and can determine the scheduled task deployed in the terminal device through the scheduled task identifier. It can determine whether the scheduled task deployed on the terminal device has been updated by comparing the scheduled task with the target scheduled task. If the scheduled task deployed on the terminal device has been updated, the scheduled task deployed on the terminal device can be deleted and the target scheduled task can be added to the terminal device.

[0052] In one embodiment shown, before determining the scheduled task identifier corresponding to the target custom task name based on the correspondence, the method may also include: determining whether the target custom task name is included in the correspondence; if the target custom task name is included in the correspondence, then further determining the scheduled task identifier corresponding to the target custom task name based on the correspondence; if not, adding a target scheduled task corresponding to the configuration information.

[0053] Since the update of the task configuration for the scheduled task may be to add a target scheduled task in the task configuration, in this case, the target scheduled task has not yet been deployed on the terminal device, and the correspondence maintained in the terminal device does not include a scheduled task identifier corresponding to the target scheduled task. Therefore, before determining the scheduled task identifier corresponding to the target custom task name based on the correspondence, it is also possible to first determine whether the target scheduled task is deployed on the terminal device by determining whether the target custom task name is included in the correspondence. If the target scheduled task is deployed on the terminal device, the scheduled task identifier corresponding to the target custom task name may be further determined based on the correspondence. If the target scheduled task is not deployed on the terminal device, the target scheduled task may be deployed in the terminal device.

[0054] For example, the correspondence relationship can be represented by a correspondence relationship table; wherein the correspondence relationship table may include one or more table items for describing the correspondence relationship between the custom task name and the scheduled task identifier; please refer to Table 1, which is a correspondence relationship table shown in an exemplary embodiment.

[0055] Customize task name Scheduled task identifier Task Name_1 Identifier_1 Task Name_2 Identifier_2 Task Name_3 Identifier_3

[0056] Table 1

[0057] As shown in Table 1, the custom task name may include task name_1, task name_2, and task name_3, and the scheduled task identifier may include identifier_1, identifier_2, and identifier_3.

[0058] Specifically, the target custom task name may be task name_2, and the terminal device may determine that the correspondence table contains the task name_2, and may further determine, based on the correspondence table, that the scheduled task identifier corresponding to the task name_2 is identifier_2; the target custom task name may also be task name_4, and the terminal device may determine that the correspondence table does not contain the task name_4, and may add a target scheduled task corresponding to the configuration information corresponding to the task name_4.

[0059] In this way, it is possible to first determine whether the target scheduled task has been deployed on the terminal device, and then perform the subsequent corresponding configuration process, thereby avoiding repeated configuration of scheduled tasks and improving the efficiency of scheduled task configuration.

[0060] In one embodiment shown, the terminal device may support the Spring framework; the configuration information may also include a calling method name corresponding to the target scheduled task; before adding the target scheduled task corresponding to the configuration information, the method may also include: based on the calling method name, determining whether the Spring framework supports the calling method corresponding to the calling method name; if the Spring framework supports the calling method corresponding to the calling method name, the target scheduled task corresponding to the configuration information may be further added.

[0061] The Spring framework is an open source framework created to solve the complexity of enterprise application development. The Spring framework supports multiple calling methods, wherein the calling method may include the calling method in the Bean class supported by the Spring framework. Before the terminal device adds the target scheduled task, it can first determine whether the Spring framework supports the calling method that needs to be called when the target scheduled task is executed. If it is determined that the Spring framework supports the calling method, the target scheduled task corresponding to the configuration information can be further added.

[0062] For example, the configuration information may also include the Bean name of the Bean class where the calling method is located; the terminal device may query whether the Spring framework contains a calling method corresponding to the calling method name based on the calling method name corresponding to the target scheduled task and the Bean name contained in the configuration information; if the Spring framework contains a calling method corresponding to the calling method name, the target scheduled task corresponding to the configuration information may be further added.

[0063] In this way, when the Spring framework supports the calling method required for the execution of the target scheduled task, the subsequent scheduled task configuration process can be performed to avoid invalid configuration of the scheduled task and improve the efficiency of the scheduled task configuration.

[0064] In one embodiment shown, the configuration information may also include target custom time rules; the target custom time rules may be used to define the execution time strategy of the scheduled task; the determination of whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task may include: matching the custom time rules in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rules corresponding to the target scheduled task; and determining whether the scheduled task is updated based on the matching result.

[0065] By matching the custom time rules in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rules corresponding to the target scheduled task, it can be determined whether the scheduled task has been updated based on the matching result. If the custom time rules in the scheduled task successfully match the target custom time rules corresponding to the target scheduled task, it means that the scheduled task has not been updated; if the custom time rules in the scheduled task do not successfully match the target custom time rules corresponding to the target scheduled task, it means that the scheduled task has been updated.

[0066] For example, the terminal device can match the custom time rules in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rules corresponding to the target scheduled task. If the custom time rules match the target custom time rules successfully, it can be determined that the scheduled task has not been updated. If the custom time rules do not match the target custom time rules successfully, it can be determined that the scheduled task has been updated.

[0067] In this way, it can be determined whether the scheduled task deployed on the terminal device is updated, thereby improving the efficiency of scheduled task deployment.

[0068] Regarding the adding of the target scheduled task corresponding to the configuration information, specifically, the terminal device can encapsulate the custom scheduled task object corresponding to the target scheduled task based on the Bean name corresponding to the Bean class where the calling method is located contained in the configuration information, the calling method name, the target custom task name and the target custom time rule; and can generate the target scheduled task based on the custom scheduled task object.

[0069] The present specification does not limit the specific form of the target custom time rule. For example, the target custom time rule may be a time expression or other forms for defining the execution time strategy of the scheduled task.

[0070] In one embodiment shown, the target custom time rule may include a time expression for defining an execution time strategy of the scheduled task.

[0071] For example, the target custom time rule may include a cron expression for defining the execution time strategy of the scheduled task, wherein the cron expression is a character string for defining the execution time strategy of the scheduled task.

[0072] In one embodiment shown, a target scheduled task identifier corresponding to the target scheduled task may be obtained; and a correspondence between the target scheduled task identifier and the target custom task name may be added to the correspondence.

[0073] For example, after the target scheduled task is added, a target scheduled task identifier corresponding to the target scheduled task can be generated, the terminal device can obtain the target scheduled task identifier, and the terminal device can add a correspondence between the target scheduled task identifier and the target custom task name in the correspondence; since the target scheduled task identifier is used to indicate the target scheduled task that has been deployed on the terminal device, the terminal device can determine whether the terminal device has deployed the target scheduled task based on the correspondence, and can determine the target scheduled task identifier corresponding to the target custom task name through the correspondence.

[0074] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of this specification, the following takes updating the target scheduled task deployed on the terminal device as an example, combined with the following Figure 2 The flowchart of the scheduled task configuration method shown is used to illustrate the embodiments in this specification.

[0075] See also Figure 2 , Figure 2 It is a flowchart of another method for configuring scheduled tasks shown in an exemplary embodiment. The terminal device supports the Spring framework, and at least one scheduled task can be deployed on the terminal device, and a custom task name corresponding to any scheduled task in the at least one scheduled task and a scheduled task identifier corresponding to any scheduled task can be maintained. Among them, the at least one scheduled task includes the target scheduled task, and the terminal device maintains a correspondence between the target custom task name of the target scheduled task and the target scheduled task identifier of the target scheduled task, and the target scheduled task identifier can be used to indicate the target scheduled task.

[0076] The terminal device may be equipped with a configuration center, through which the user may update the task configuration of the target scheduled task. The terminal device may respond to the update information of the task configuration corresponding to the scheduled task maintained by the configuration center, and obtain the configuration information corresponding to the target scheduled task contained in the task configuration; the configuration information may include a target custom task name corresponding to the target scheduled task, a calling method name corresponding to the target scheduled task, and a target custom time rule.

[0077] The target custom task name may be task name_2, the terminal device may determine that the corresponding relationship includes the task name_2, and may further determine, based on the corresponding relationship, that the scheduled task identifier corresponding to the task name_2 is identifier_2.

[0078] The terminal device can match the custom time rules in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rules corresponding to the target scheduled task. If the custom time rules match the target custom time rules successfully, it can be determined that the scheduled task has not been updated. If the custom time rules do not match the target custom time rules successfully, it can be determined that the scheduled task has been updated.

[0079] If the scheduled task is updated, the scheduled task deployed on the terminal device can be deleted, and based on the calling method name, it is determined whether the Spring framework supports the calling method corresponding to the calling method name; if the Spring framework supports the calling method corresponding to the calling method name, the target scheduled task corresponding to the configuration information can be added to the terminal device.

[0080] Corresponding to the embodiment of the scheduled task configuration method, this specification also provides an embodiment of a scheduled task configuration device.

[0081] See also Figure 3 , Figure 3 It is a hardware structure diagram of an electronic device where a timing task configuration device is located, which is shown as an exemplary embodiment. At the hardware level, the device includes a processor 302, an internal bus 304, a network interface 306, a memory 308, and a non-volatile memory 310, and of course may also include hardware required for other services. One or more embodiments of this specification can be implemented based on software, such as the processor 302 reading the corresponding computer program from the non-volatile memory 310 into the memory 308 and then running it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0082] See also Figure 4 , Figure 4 is a block diagram of a timed task configuration device shown in an exemplary embodiment. The timed task configuration device can be applied to Figure 3 In the electronic device shown, the technical solution of this specification is implemented. The device can be applied to a terminal device; the terminal device can maintain a corresponding relationship between a custom task name and a scheduled task identifier of a scheduled task deployed on the terminal device; wherein the scheduled task identifier can be used to indicate the scheduled task; the device may include:

[0083] The acquisition unit 402 is used to acquire configuration information corresponding to the target scheduled task contained in the task configuration in response to the update information of the task configuration corresponding to the scheduled task maintained by the configuration center; the configuration information includes the target custom task name corresponding to the target scheduled task;

[0084] Determination unit 404 is used to determine the scheduled task identifier corresponding to the target custom task name based on the corresponding relationship, and determine whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task; if so, delete the scheduled task and add the target scheduled task corresponding to the configuration information.

[0085] In this embodiment, the scheduled task identifier includes a handle object used to indicate the scheduled task.

[0086] In this embodiment, the determining unit 404 may also be used to:

[0087] Determine whether the corresponding relationship contains the target custom task name;

[0088] If yes, further determining a scheduled task identifier corresponding to the target custom task name based on the corresponding relationship;

[0089] If not, add a target scheduled task corresponding to the configuration information.

[0090] In this embodiment, the terminal device may support the Spring framework; the configuration information may also include a calling method name corresponding to the target scheduled task;

[0091] The determining unit 404 may also be used to:

[0092] Based on the calling method name, determining whether the Spring framework supports the calling method corresponding to the calling method name;

[0093] If yes, further add a target scheduled task corresponding to the configuration information.

[0094] In this embodiment, the configuration information further includes a target custom time rule; the target custom time rule is used to define the execution time strategy of the scheduled task;

[0095] The determining unit 404 may be specifically configured to:

[0096] Matching the custom time rule in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rule corresponding to the target scheduled task;

[0097] Determine whether the scheduled task is updated based on the matching result.

[0098] In this embodiment, the device may further include an acquisition unit, configured to:

[0099] Obtaining a target scheduled task identifier corresponding to the target scheduled task;

[0100] In the correspondence, a correspondence between the target scheduled task identifier and the target custom task name is added.

[0101] The implementation process of the functions and effects of each unit in the device is specifically described in the implementation process of the corresponding steps in the method, which will not be repeated here.

[0102] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can refer to the partial description of the method embodiments. The device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. Ordinary technicians in this field can understand and implement it without paying creative work.

[0103] The systems, devices, modules or units described in the embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0104] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0105] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0106] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0107] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0108] The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0109] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "one", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0110] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0111] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

[0112] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

Claims

1. A method for configuring a scheduled task, applied to a terminal device; the terminal device maintains a correspondence between a custom task name of a scheduled task deployed on the terminal device and a scheduled task identifier; wherein, The scheduled task identifier is used to indicate the scheduled task; the method comprises: In response to update information of a task configuration corresponding to the scheduled task maintained by a configuration center, obtaining configuration information corresponding to a target scheduled task contained in the task configuration; the configuration information includes a target custom task name corresponding to the target scheduled task; Based on the corresponding relationship, determine the scheduled task identifier corresponding to the target custom task name, and determine whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task; if so, delete the scheduled task and add the target scheduled task corresponding to the configuration information. 2 . According to the method of claim 1 , the scheduled task identifier comprises a handle object for indicating the scheduled task.

3. According to the method of claim 1, before determining the scheduled task identifier corresponding to the target custom task name based on the corresponding relationship, the method further comprises: Determine whether the corresponding relationship contains the target custom task name; If yes, further determining a scheduled task identifier corresponding to the target custom task name based on the corresponding relationship; If not, add a target scheduled task corresponding to the configuration information.

4. According to the method of claim 1 or 3, the terminal device supports the Spring framework; the configuration information further includes the name of the calling method corresponding to the target scheduled task; Before adding the target scheduled task corresponding to the configuration information, the method further includes: Based on the calling method name, determining whether the Spring framework supports the calling method corresponding to the calling method name; If yes, further add a target scheduled task corresponding to the configuration information.

5. According to the method of claim 1, the configuration information further comprises a target custom time rule; the target custom time rule is used to define the execution time strategy of the scheduled task; The determining whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task includes: Matching the custom time rule in the scheduled task deployed on the terminal device indicated by the scheduled task identifier with the target custom time rule corresponding to the target scheduled task; Determine whether the scheduled task is updated based on the matching result.

6. The method according to claim 4, further comprising: Obtaining a target scheduled task identifier corresponding to the target scheduled task; In the correspondence, a correspondence between the target scheduled task identifier and the target custom task name is added.

7. A scheduled task configuration device, applied to a terminal device; the terminal device maintains a correspondence between a custom task name of a scheduled task deployed on the terminal device and a scheduled task identifier; wherein, The scheduled task identifier is used to indicate the scheduled task; the device comprises: An acquisition unit, configured to acquire configuration information corresponding to a target scheduled task contained in the task configuration in response to update information of a task configuration corresponding to the scheduled task maintained by a configuration center; the configuration information includes a target custom task name corresponding to the target scheduled task; A determination unit is used to determine, based on the corresponding relationship, a scheduled task identifier corresponding to the target custom task name, and determine whether the scheduled task deployed on the terminal device indicated by the scheduled task identifier is updated relative to the target scheduled task; if so, delete the scheduled task and add the target scheduled task corresponding to the configuration information.

8. An electronic device, comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are interconnected via the bus; The memory stores machine-readable instructions, and the processor executes the scheduled task configuration method according to any one of claims 1 to 6 by calling the machine-readable instructions.

9. A machine-readable storage medium, wherein the machine-readable storage medium stores machine-readable instructions, and when the machine-readable instructions are called and executed by a processor, the scheduled task configuration method according to any one of claims 1 to 6 is implemented.