A method and related apparatus for managing timing tasks
By automating the updating of scheduled task configuration files and program parameters, the problem of manually editing configuration files in existing technologies is solved, thereby improving the flexibility and efficiency of scheduled task management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING CO WHEELS TECH CO LTD
- Filing Date
- 2024-12-30
- Publication Date
- 2026-06-30
AI Technical Summary
In existing technologies, configuring scheduled tasks requires manual editing of configuration files, resulting in inflexible configuration and low efficiency.
In response to changes in the configuration file, the configuration reading program is invoked to update the configuration file, obtain and update the parameters of the scheduled task program, and automatically load it into the task scheduler for execution.
It automates the entire process from modifying the scheduled task program to scheduling and execution, improving configuration flexibility and efficiency while reducing manual operations.
Smart Images
Figure CN122309046A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of software system technology, and in particular to a method and related apparatus for managing timed tasks. Background Technology
[0002] Scheduled tasks are time-controlled tasks set up in the system. By executing scheduled tasks, data cleaning, querying, and other operations can be performed periodically, providing reliable support for system monitoring and operation. They are an indispensable part of the software system.
[0003] Currently, scheduled task configurations are generally defined using static text files. Modifying scheduled tasks requires manually editing the configuration file and reloading the scheduled task by executing the corresponding commands, resulting in inflexible and inefficient configuration. Summary of the Invention
[0004] In view of the above problems, this application provides a method and related apparatus for managing scheduled tasks, so as to improve management efficiency and save manual operation. The specific solution is as follows:
[0005] The first aspect of this application provides a method for managing scheduled tasks, including:
[0006] In response to a modification signal to the original configuration file, the configuration reading program is invoked to update the configuration content associated with the modification signal to the original configuration file, thereby obtaining the updated configuration file;
[0007] Call the scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database;
[0008] The scheduled task updater is invoked, and the parameters of the scheduled task program are updated according to the updated configuration file to obtain the updated scheduled task program.
[0009] The updated scheduled task program is loaded into the task scheduler for scheduled execution.
[0010] In one possible implementation, before invoking the configuration reading program to update the configuration content associated with the modification signal to the original configuration file in response to a modification signal of the original configuration file, and obtaining the updated configuration file, the method further includes:
[0011] The configuration content monitoring program is invoked to identify modification operation signals of the original configuration file, and when a modification operation signal of the original configuration file is identified, the modification signal is generated.
[0012] In one possible implementation, the configuration reader updates the configuration content associated with the modified signal into the original configuration file, resulting in an updated configuration file, including:
[0013] After deleting the original configuration content associated with the configuration content from the original configuration file, the configuration content is added back to the original configuration file to obtain the updated configuration file.
[0014] In one possible implementation, before invoking the scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database, the following steps are also included:
[0015] The task instantiation sequence is invoked to register the characteristic information of the scheduled task program into the system;
[0016] Determine whether the scheduled task program after instantiation has implemented the corresponding interface functions;
[0017] If so, the feature information is stored in the system's global variables.
[0018] In one possible implementation, before calling the task instantiation sequence to register the characteristic information of the scheduled task program into the system, the method further includes:
[0019] The register is invoked to identify the structural parameters of the user-input timed task program and obtain the feature information.
[0020] In one possible implementation, determining whether the timed task program after instantiation implements the corresponding interface functionality includes:
[0021] Determine whether the task instance obtained after compiling the scheduled task program belongs to the class of the corresponding interface function;
[0022] If so, then it is determined that the scheduled task program has implemented the corresponding interface function;
[0023] If not, then it is determined that the scheduled task program has implemented the corresponding interface function.
[0024] A second aspect of this application provides a timed task management device, comprising:
[0025] The configuration file update module is used to respond to a modification signal to the original configuration file, call the configuration reading program to update the configuration content associated with the modification signal to the original configuration file, and obtain the updated configuration file;
[0026] The scheduled task acquisition module is used to call the scheduled task acquisition program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database.
[0027] The scheduled task update module is used to call the scheduled task update program, update the parameters of the scheduled task program according to the updated configuration file, and obtain the updated scheduled task program; and,
[0028] The scheduled task execution module is used to load the updated scheduled task program into the task scheduler for scheduled execution.
[0029] A third aspect of this application provides a computer program product including computer-readable instructions that, when executed on an electronic device, cause the electronic device to implement the timed task management method of the first aspect or any implementation thereof.
[0030] A fourth aspect of this application provides an electronic device, including at least one processor and a memory connected to the processor, wherein:
[0031] The memory is used to store computer programs;
[0032] The processor is used to execute the computer program so that the electronic device can implement the timed task management method of the first aspect or any implementation thereof.
[0033] The fifth aspect of this application provides a computer storage medium carrying one or more computer programs, which, when executed by an electronic device, enable the electronic device to implement the timed task management method of the first aspect or any implementation thereof.
[0034] By employing the above technical solution, the scheduled task management method provided in this application can promptly respond to changes in the configuration file after the content of the scheduled task changes. It calls a configuration reading program to update the configuration content associated with the change signal into the original configuration file, obtaining the updated configuration file. Then, it calls a scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database. Next, it calls a scheduled task update program to update the parameters of the scheduled task program according to the updated configuration file, obtaining the updated scheduled task program. Finally, it loads the updated scheduled task program into the task scheduler for scheduling and execution. This achieves full automation from modification to scheduling execution of the scheduled task program, eliminating the need for manual execution of various commands for scheduled task management and improving the flexibility and efficiency of scheduled task configuration. Attached Figure Description
[0035] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.
[0036] Figure 1 An architecture diagram of a scheduled task management system provided in this application;
[0037] Figure 2 A structural diagram of a terminal provided in this application;
[0038] Figure 3 A structural diagram of a server provided in this application;
[0039] Figure 4 A flowchart of a scheduled task management method provided in this application;
[0040] Figure 5 The flowchart for task registration and scheduling execution provided in this application;
[0041] Figure 6 A structural diagram of a timed task management device provided in this application;
[0042] Figure 7 This is a structural diagram of an electronic device provided in this application. Detailed Implementation
[0043] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.
[0044] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.
[0045] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.
[0046] See Figure 1 , Figure 1 A schematic diagram of the architecture of a scheduled task management system is shown. The system may include a terminal 100 and a server 200. The server 200 may include one or more servers (…). Figure 1 (The example includes a server). The server 200 can provide the scheduled task management method provided in the embodiments of this application to one or more terminals.
[0047] The terminal 100 may have an application installed on it that can modify the contents of the configuration file for the scheduled task. The application and the webpage can provide an interface. The terminal 100 can receive the relevant modification parameters entered by the user on the modification interface and send the parameters to the server 200. The server 200 can obtain the processing result based on the received parameters and return the processing result to the terminal 100.
[0048] It should be understood that in some optional implementations, the terminal 100 can also complete the action of obtaining the processing result based on the received parameters on its own, without the need for the server to cooperate. This application embodiment is not limited to this.
[0049] The following description Figure 1 The product form of the mid-terminal 100;
[0050] The terminal 100 in this application embodiment can be a mobile phone, tablet computer, wearable device, vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc., and this application embodiment does not impose any restrictions on it.
[0051] Figure 2 A schematic diagram of an optional hardware structure for terminal 100 is shown.
[0052] refer to Figure 2 As shown, the terminal 100 may include a radio frequency unit 110, a memory 120, an input unit 130, a display unit 140, a camera 150 (optional), an audio circuit 160 (optional), a speaker 161 (optional), a microphone 162 (optional), a headphone jack 163 (optional), a processor 170, an external interface 180, a power supply 190, and other components. Those skilled in the art will understand that... Figure 2These are merely examples of terminals or multi-functional devices and do not constitute a limitation on terminals or multi-functional devices. They may include more or fewer components than shown in the illustration, or combine certain components, or use different components.
[0053] The input unit 130 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the portable multi-functional device. Specifically, the input unit 130 may include a touchscreen 131 (optional) and / or other input devices 132. The touchscreen 131 can collect touch operations performed by the user on or near it (such as operations performed by the user using fingers, knuckles, styluses, or any suitable object on or near the touchscreen), and drive the corresponding connection devices according to a pre-set program. The touchscreen can detect the user's touch actions, convert the touch actions into touch signals and send them to the processor 170, and can receive and execute commands sent by the processor 170; the touch signal includes at least touch point coordinate information. The touchscreen 131 can provide an input interface and an output interface between the terminal 100 and the user. In addition, various types of touchscreens, such as resistive, capacitive, infrared, and surface acoustic wave, can be used to implement the touchscreen. Besides the touchscreen 131, the input unit 130 may also include other input devices. Specifically, other input devices 132 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.
[0054] Among them, the input device 132 can receive input data, etc.
[0055] The display unit 140 can be used to display information input by the user or information provided to the user, various menus of the terminal 100, interactive interfaces, file display, and / or playback of any multimedia file. In this embodiment, the display unit 140 can be used to display an interface for parameter modification, processing results, etc.
[0056] The memory 120 can be used to store instructions and data. The memory 120 may primarily include an instruction storage area and a data storage area. The data storage area can store various types of data, such as multimedia files and text. The instruction storage area can store software units such as operating systems, applications, and instructions required for at least one function, or subsets or extended sets thereof. It may also include non-volatile random access memory. It provides the processor 170 with hardware, software, and data resources for managing the computing device, supporting control software and applications. It is also used for storing multimedia files, as well as storing running programs and applications.
[0057] The processor 170 is the control center of the terminal 100. It connects various parts of the terminal 100 via various interfaces and lines. By running or executing instructions stored in the memory 120 and calling data stored in the memory 120, it performs various functions and processes data of the terminal 100, thereby controlling the terminal device as a whole. Optionally, the processor 170 may include one or more processing units; preferably, the processor 170 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 170. In some embodiments, the processor and memory can be implemented on a single chip; in some embodiments, they can also be implemented separately on independent chips. The processor 170 can also be used to generate corresponding operation control signals, send them to the corresponding components of the computing processing device, read and process data in the software, especially read and process data and programs in the memory 120, so that the various functional modules therein perform corresponding functions, thereby controlling the corresponding components to act according to the instructions.
[0058] The memory 120 can be used to store software code related to the timed task management method, and the processor 170 can execute the steps of the timed task management method, and can also schedule other units (such as the above-mentioned input unit 130 and display unit 140) to achieve the corresponding functions.
[0059] The radio frequency unit 110 (optional) can be used for receiving and transmitting signals during information transmission or calls. For example, it can receive downlink information from the base station and process it for the processor 170; additionally, it can transmit uplink data to the base station. Typically, the RF circuit includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc. Furthermore, the radio frequency unit 110 can also communicate wirelessly with network devices and other devices. This wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.
[0060] In this embodiment of the application, the radio frequency unit 110 can send the modified configuration data to the server 200 and receive the processing result of the new scheduled task execution sent by the server 200.
[0061] It should be understood that the radio frequency unit 110 is optional and can be replaced with other communication interfaces, such as a network port.
[0062] The terminal 100 also includes a power supply 190 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 170 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.
[0063] Terminal 100 also includes an external interface 180, which can be a standard Micro USB interface or a multi-pin connector, which can be used to connect terminal 100 to other devices for communication or to connect a charger to charge terminal 100.
[0064] Although not shown, terminal 100 may also include a flash, a wireless fidelity (WiFi) module, a Bluetooth module, sensors with various functions, etc., which will not be described in detail here. Some or all of the methods described below can be applied to, for example... Figure 2 In the terminal 100 shown.
[0065] The following description Figure 1 The product form of the mid-range server 200;
[0066] Figure 3 A structural diagram of a server 200 is provided, as follows: Figure 3 As shown, server 200 includes bus 201, processor 202, communication interface 203, and memory 204. Processor 202, memory 204, and communication interface 203 communicate with each other via bus 201.
[0067] Bus 201 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 3 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0068] The processor 202 can be any one or more of the following processors: central processing unit (CPU), graphics processing unit (GPU), microprocessor (MP), or digital signal processor (DSP).
[0069] Memory 204 may include volatile memory, such as random access memory (RAM). Memory 204 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).
[0070] The memory 204 can be used to store software code related to the timed task management method, and the processor 202 can execute the steps of the chip's timed task management method, and can also schedule other units to achieve the corresponding functions.
[0071] It should be understood that the aforementioned terminal 100 and server 200 can be centralized or distributed devices. The processors (e.g., processor 170 and processor 202) in the aforementioned terminal 100 and server 200 can be hardware circuits (such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), general-purpose processors, digital signal processors (DSPs), microprocessors or microcontrollers, etc.) or combinations of these hardware circuits. For example, the processor can be a hardware system with instruction execution capabilities, such as a CPU or DSP, or a hardware system without instruction execution capabilities, such as an ASIC or FPGA, or a combination of the aforementioned hardware systems without instruction execution capabilities and hardware systems with instruction execution capabilities.
[0072] Currently, the configuration of scheduled tasks in in-vehicle systems is defined through static text files. Any changes require manual editing of the file and reloading of the scheduled tasks via commands. This method is time-consuming, laborious, and lacks flexibility when dynamic configuration or addition of scheduled tasks is needed.
[0073] To address the aforementioned problems, embodiments of this application provide a scheduled task management method. The scheduled task management method of this application embodiment will be described in detail below with reference to the accompanying drawings.
[0074] Reference Figure 4 , Figure 4 A flowchart illustrating a scheduled task management method provided in this application embodiment is shown below. Figure 4 As shown in the embodiment of this application, a timed task management method may include steps 401 to 404, which are described in detail below.
[0075] 401. In response to a modification signal to the original configuration file, the configuration reading program is invoked to update the configuration content associated with the modification signal to the original configuration file, thus obtaining the updated configuration file.
[0076] Specifically, an application for dynamically configuring scheduled tasks can be set up on the user's debugging terminal (such as a laptop, computer, etc.). This application provides a configuration interface for scheduled tasks, which displays the configuration files of the current scheduled tasks in the system. Users can view and modify the contents of the configuration files (such as the name of the scheduled task, execution parameters, etc.) according to their selections. After the modification is completed and a confirmation operation is performed, a change signal indicating that the configuration file modification is complete will be generated.
[0077] Upon receiving this modification signal, the configuration reading program will be triggered to update the corresponding configuration file in the system, thereby updating the original configuration file corresponding to the scheduled task in the system. The configuration reading program can be constructed based on the structural characteristics of the scheduled task within the system's built-in scheduled task tool to adjust the relevant parts of the configuration file.
[0078] It is understood that those skilled in the art can define and adjust the specific implementation of the configuration reading program as needed, and no restrictions are imposed here.
[0079] 402. Call the scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database.
[0080] Specifically, the scheduled task registration database stores the identifiers, names, and storage addresses of scheduled task programs that have been pre-registered in the system. For example, by calling the scheduled task retrieval program, a scheduled task program matching the identifier in the configuration file can be extracted from the scheduled task registration database. In practical applications, scheduled task programs are stored in memory as key-value pairs, where the key can be the identifier of the scheduled task program stored in a variable, and the corresponding value is the scheduled task program itself.
[0081] 403. Call the scheduled task updater to update the parameters of the scheduled task program according to the updated configuration file, and obtain the updated scheduled task program.
[0082] Specifically, given that scheduled task programs are stored in the system using various parameters—such as the task name, structure, and constructor—the scheduled task update program can be invoked to iterate through the corresponding parts of the program based on the mapping between these parameters and the contents of the configuration file. This allows for the modification of the corresponding parts of the scheduled task program, thereby updating it.
[0083] 404. Load the updated scheduled task program into the task scheduler for scheduling and execution.
[0084] Based on the updated scheduled task program, it is instantiated and added to the task scheduler. This allows the task scheduler to periodically execute the scheduled task according to its execution cycle. Instantiation here refers to the process of creating an object of a class in object-oriented programming, using the formula object name = class name(parameter1, parameter2...parametern). This creates an object with the attributes and methods of the scheduled task program, facilitating its scheduling by the task scheduler.
[0085] It can be seen that, compared with existing technologies, this scheduled task management method can complete the update and configuration of scheduled tasks without restarting the system or application, thereby improving the stability and maintainability of the system. Furthermore, it effectively reduces manual intervention, improving the efficiency of scheduled task management and reducing management complexity.
[0086] In one possible implementation, to further improve the efficiency of scheduled task management, before step 401 above, in response to a modification signal in the original configuration file, calls the configuration reading program to update the configuration content associated with the modification signal to the original configuration file, and obtains the updated configuration file, the process of obtaining the modification signal includes:
[0087] The configuration content monitoring program is invoked to identify modification signals of the original configuration file, and a modification signal is generated when a modification signal of the original configuration file is identified.
[0088] Specifically, the user interface for the scheduled task configuration file can be provided with a button to confirm the modification operation, and the original configuration file modification options can be provided. After the user confirms the revision by clicking the button, the configuration content monitoring program will be triggered to compare the content of each modification option with the corresponding content of the configuration file, thereby determining whether the configuration file has been modified, and thus triggering the generation of a change signal.
[0089] To improve the accuracy of configuration file updates and the reliability of subsequent scheduled task program updates, step 401 above calls the configuration reading program to update the configuration content associated with the modified signals into the original configuration file, obtaining the updated configuration file, which may specifically include:
[0090] The updated configuration file is obtained by deleting the original configuration content associated with the configuration content from the original configuration file and then adding the new configuration content back to the original configuration file. This method of deleting first and then adding is used to update the configuration file, thus avoiding the influence of residual content in the configuration file on the updated content.
[0091] In one possible implementation, to improve the maintainability of dynamic management of scheduled tasks in the system, the registration process of scheduled task programs in the scheduled task registration database used above includes the following steps:
[0092] Step 11: Call the task instantiation program to register the characteristic information of the scheduled task program into the system.
[0093] Specifically, the call register stored through a pre-defined storage path can identify the structural parameters of the user-input scheduled task program to obtain characteristic information. This characteristic information may include user-defined parameters such as the name, structure, and constructor of the scheduled task. Based on this characteristic information, the instantiated scheduled task program's class name and parameters are stored in the system so that, during scheduled task execution, the corresponding scheduled task program can be started based on this information.
[0094] Step 12: Determine whether the scheduled task program after instantiation has implemented the corresponding functional interface.
[0095] Specifically, the system checks whether the task instance obtained after compiling the scheduled task program belongs to the class of the corresponding functional interface. This verifies whether a scheduled task, after instantiation, belongs to a class that implements the corresponding functional interface and whether it has been successfully registered in the system.
[0096] Step 13: If yes, store the feature information in the system's global variables.
[0097] Specifically, the name and storage address of the scheduled task can be stored in a global variable for the scheduled task scheduler to use for scheduling.
[0098] As a specific application of the above-mentioned scheduled task management method, refer to Figure 5 The registration and update processes for scheduled tasks are shown below:
[0099] like Figure 5 As shown in the left side of the middle section, after the registration process begins, the caching program is called to store the user-provided parameters such as the name, structure, and constructor of the custom scheduled task.
[0100] The registration program is called to register the parameter information of the custom scheduled task to the system, and the instantiation operation of the scheduled task is used to determine whether the scheduled task has been registered successfully.
[0101] After determining that the instantiated scheduled task program implements the corresponding functional interface, the relevant parameters of the scheduled task program are stored in global variables.
[0102] When performing the update process for a scheduled task:
[0103] After initializing the system's scheduled task management, a watchdog can be used to determine whether the original configuration file has been modified, and then the configuration reading program can be called to update the original configuration file.
[0104] The scheduled task acquisition program is called to obtain the corresponding scheduled task program parameters from the global variables. Then, the scheduled task update program is called to update the parameters of the scheduled task program according to the updated configuration file. Finally, the program is loaded into the task scheduler and scheduled for execution by the task scheduler.
[0105] The above describes a scheduled task management method provided by the embodiments of this application. The following will describe the apparatus for executing the above scheduled task management method.
[0106] Please see Figure 6 , Figure 6 This is a schematic diagram of a timed task management device provided in an embodiment of this application. Figure 6 As shown, the timed task management device includes:
[0107] The configuration file update module 601 is used to respond to a modification signal to the original configuration file, call the configuration reading program to update the configuration content associated with the modification signal to the original configuration file, and obtain the updated configuration file.
[0108] The scheduled task acquisition module 602 is used to call the scheduled task acquisition program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database.
[0109] The scheduled task update module 603 is used to call the scheduled task update program, update the parameters of the scheduled task program according to the updated configuration file, and obtain the updated scheduled task program. And,
[0110] The scheduled task execution module 604 is used to load the updated scheduled task program into the task scheduler for scheduled execution.
[0111] In one possible implementation, it also includes: a modification signal generation module, used to, in response to a modification signal in the original configuration file, call the configuration reading program to update the configuration content associated with the modification signal to the original configuration file, before obtaining the updated configuration file:
[0112] The configuration content monitoring program is invoked to identify modification operation signals of the original configuration file, and when a modification operation signal of the original configuration file is identified, the modification signal is generated.
[0113] In one possible implementation, the process by which the configuration file update module 601 calls the configuration reading program to update the configuration content associated with the modified signal into the original configuration file, thereby obtaining the updated configuration file, includes:
[0114] After deleting the original configuration content associated with the configuration content from the original configuration file, the configuration content is added back to the original configuration file to obtain the updated configuration file.
[0115] In one possible implementation, it further includes: a scheduled task registration module, used before calling the scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database:
[0116] The task instantiation sequence is invoked to register the characteristic information of the scheduled task program into the system;
[0117] Determine whether the scheduled task program after instantiation has implemented the corresponding interface functions;
[0118] If so, the feature information is stored in the system's global variables.
[0119] In one possible implementation, the feature information acquisition module is used to register the feature information of the scheduled task program into the system before calling the task instantiation sequence:
[0120] The register is invoked to identify the structural parameters of the user-input timed task program and obtain the feature information.
[0121] In one possible implementation, the process by which the scheduled task acquisition module 602 determines whether the scheduled task program after instantiation has implemented the corresponding interface function includes:
[0122] Determine whether the task instance obtained after compiling the scheduled task program belongs to the class of the corresponding interface function;
[0123] If so, then it is determined that the scheduled task program has implemented the corresponding interface function;
[0124] If not, then it is determined that the scheduled task program has implemented the corresponding interface function.
[0125] This application also provides an electronic device in its embodiments. (See reference...) Figure 7 The diagram illustrates a structural schematic suitable for implementing the electronic device in the embodiments of this application. The electronic device in the embodiments of this application may include, but is not limited to, fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 7 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.
[0126] like Figure 7As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. When the electronic device is powered on, the RAM 703 also stores various programs and data required for the operation of the electronic device. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.
[0127] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, memory cards, hard drives, etc.; and communication devices 709. Communication device 709 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.
[0128] This application also provides a computer program product including computer-readable instructions, which, when executed on an electronic device, cause the electronic device to implement any of the timed task management methods provided in this application.
[0129] This application also provides a computer-readable storage medium that carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the timed task management methods provided in this application.
[0130] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.
[0131] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0132] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.
[0133] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
Claims
1. A method for managing scheduled tasks, characterized in that, include: In response to a modification signal in the original configuration file, the configuration reading program is invoked to update the configuration content associated with the modification signal into the original configuration file, thereby obtaining the updated configuration file; Call the scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database; The scheduled task updater is invoked, and the parameters of the scheduled task program are updated according to the updated configuration file to obtain the updated scheduled task program. The updated scheduled task program is loaded into the task scheduler for scheduled execution.
2. The scheduled task management method according to claim 1, characterized in that, Before invoking the configuration reading program to update the configuration content associated with the modification signal into the original configuration file in response to a modification signal in the original configuration file, and obtaining the updated configuration file, the process further includes: The configuration content monitoring program is invoked to identify modification operation signals of the original configuration file, and when a modification operation signal of the original configuration file is identified, the modification signal is generated.
3. The timed task management method according to claim 1, characterized in that, The configuration reading program updates the configuration content associated with the modified signal into the original configuration file, resulting in an updated configuration file, including: After deleting the original configuration content associated with the configuration content from the original configuration file, the configuration content is added back to the original configuration file to obtain the updated configuration file.
4. The timed task management method according to any one of claims 1 to 3, characterized in that, Before invoking the scheduled task retrieval program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database, the process also includes: The task instantiation sequence is invoked to register the characteristic information of the scheduled task program into the system; Determine whether the scheduled task program after instantiation has implemented the corresponding interface functions; If so, the feature information is stored in the system's global variables.
5. The timed task management method according to claim 4, characterized in that, Before calling the task instantiation sequence to register the feature information of the scheduled task program into the system, the process also includes: The register is invoked to identify the structural parameters of the user-input timed task program and obtain the feature information.
6. The scheduled task management method according to claim 4, characterized in that, The step of determining whether the scheduled task program after instantiation has implemented the corresponding interface functions includes: Determine whether the task instance obtained after compiling the scheduled task program belongs to the class of the corresponding interface function; If so, then it is determined that the scheduled task program has implemented the corresponding interface function; If not, then it is determined that the scheduled task program has implemented the corresponding interface function.
7. A timed task management device, characterized in that, include: The configuration file update module is used to respond to a modification signal to the original configuration file, call the configuration reading program to update the configuration content associated with the modification signal to the original configuration file, and obtain the updated configuration file; The scheduled task acquisition module is used to call the scheduled task acquisition program to extract the scheduled task program associated with the original configuration file from the scheduled task registration database. The scheduled task update module is used to call the scheduled task update program, update the parameters of the scheduled task program according to the updated configuration file, and obtain the updated scheduled task program; and, The scheduled task execution module is used to load the updated scheduled task program into the task scheduler for scheduled execution.
8. A computer program product, characterized in that, It includes computer-readable instructions that, when executed on an electronic device, cause the electronic device to implement the timed task management method as described in any one of claims 1 to 6.
9. An electronic device, characterized in that, It includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program to enable the electronic device to implement the timed task management method as described in any one of claims 1 to 6.
10. A computer storage medium, characterized in that, The storage medium carries one or more computer programs, which, when executed by an electronic device, enable the electronic device to implement the timed task management method as described in any one of claims 1 to 6.