A multi-scenario task scheduling method, device and equipment and storage medium

Abstract

The application relates to a multi-scene task scheduling method and device, equipment and a storage medium, which are applied to a multi-scene task scheduling platform. The method comprises the following steps: acquiring basic information of a plurality of business systems, wherein the basic information comprises name information, registration mode information and machine address information of the business systems; connecting the plurality of business systems based on the name information and the machine address information of the plurality of business systems; setting corresponding task scheduling instructions for tasks to be executed of the plurality of business systems, saving the corresponding task scheduling instructions into corresponding databases according to different calling frequencies; and when the tasks to be executed are executed, calling the corresponding task scheduling instructions in the corresponding databases to control the business systems to execute the tasks to be executed. The application has the technical effect that data reading, writing and querying are fast when a plurality of task scheduling instructions are called and executed.

Description

Technical Field

[0001] This application relates to the field of backend technology optimization, specifically to a multi-scenario task scheduling method, device, equipment, and storage medium. Background Technology

[0002] With the development of computers, many companies are gradually moving towards internetization. As companies upgrade and expand their businesses, their business systems need to process a large number of transactions every day.

[0003] In current technology, when a company's business systems process business, they pre-set relevant task scheduling instructions on the task scheduling platform. When the time to process the business arrives, the task scheduling platform sends the task scheduling instructions, and the business system processes the business after receiving the instructions.

[0004] Regarding the aforementioned technologies, the inventors believe that with over ten million task scheduling instructions being stored and invoked daily, it cannot be guaranteed that data can be read, written, and queried quickly when invoking and executing a few task scheduling instructions. Summary of the Invention

[0005] This application provides a multi-scenario task scheduling method, apparatus, device, and storage medium. These are used to improve the speed of data reading, writing, and querying when calling and executing multiple task scheduling instructions.

[0006] Firstly, this application provides a multi-scenario task scheduling method, employing the following technical solution: A multi-scenario task scheduling method applied to a multi-scenario task scheduling platform, the method includes acquiring basic information of multiple business systems, wherein the basic information includes the name information, registration method information, and machine address information of the business systems; connecting the multiple business systems based on the name information and machine address information of the multiple business systems; setting corresponding task scheduling instructions for the tasks to be executed by the multiple business systems; each task scheduling instruction has a different calling frequency, and according to the different calling frequencies, the corresponding task scheduling instructions are saved to corresponding databases; when executing the task to be executed, the corresponding task scheduling instructions in the corresponding database are called to control the business system to execute the task to be executed.

[0007] By adopting the above technical solutions, the multi-scenario task scheduling platform can quickly and accurately connect with multiple business systems simultaneously and process multiple business processes at the same time. Different task scheduling instructions are set for each business end to handle different business processes, and these instructions are saved for easy management. This also ensures that each task scheduling instruction has data traceability and is under monitoring. For business users, there is no need to set specific timetables or assign dedicated personnel to remind relevant staff to handle business processes. The task scheduling instructions will issue commands to the corresponding business systems to handle the corresponding business processes, reducing the consumption of manpower and resources, ensuring timely processing of business processes, and improving the speed of data reading, writing, and querying when calling and executing multiple task scheduling instructions.

[0008] Optionally, obtaining the basic information of multiple business systems includes: obtaining the registration methods of the multiple business systems; the registration methods include automatic registration and manual registration; if the business system selects the automatic registration method, then the corresponding task scheduling instruction is set for all terminal devices containing the business system; if the business system selects the manual registration method, then the corresponding task scheduling instruction is set for some of the terminal devices containing the business system.

[0009] By adopting the above technical solution, the business platform can set the number of terminal devices required to execute task scheduling instructions according to its own business, so as to avoid the situation where terminal devices that do not need to execute task scheduling instructions are scheduled, resulting in the occupation of a large amount of storage space and causing the multi-scenario task scheduling platform to crash; it can also set multiple terminal devices to execute task scheduling instructions simultaneously, thereby speeding up the efficiency of business processing and making reasonable and effective use of resources.

[0010] Optionally, the step of saving the corresponding task scheduling instructions to the corresponding databases according to different calling frequencies includes: the task scheduling instructions have high calling frequencies and low calling frequencies; when the number of calls reaches a preset threshold, it belongs to the high calling frequency; when the number of calls does not reach the preset threshold, it belongs to the low calling frequency; the task scheduling instructions with high calling frequencies are stored in a preset HBase database; and the task scheduling instructions with low calling frequencies are stored in a preset MySQL database.

[0011] By adopting the above technical solution, an HBase database is introduced to store high-frequency task scheduling instruction data, and a MySQL database is introduced to store low-frequency task scheduling instruction data. This saves costs while also providing faster retrieval and query speeds. It also minimizes the risk of the task scheduling platform crashing in multiple scenarios caused by the simultaneous invocation of tens of millions of task scheduling instructions. This improves the speed of data reading, writing, and querying when invoking and executing a number of task scheduling instructions.

[0012] Optionally, after saving the corresponding task scheduling instructions to the corresponding database according to different calling frequencies, the method further includes: obtaining the advanced configuration information filled in by the business system, wherein the advanced configuration includes: task level configuration, scheduling type configuration and alarm enable / disable configuration; the task level configuration includes normal level and important level; the scheduling type configuration includes cron type, no type and fixed speed type.

[0013] By adopting the above technical solution, the business side can further limit the task scheduling instructions by setting the task level, scheduling type and whether to enable alarms according to its own business type. The multi-scenario task scheduling platform sets the trigger time and number of triggers of the task scheduling instructions according to the above settings, so as to avoid the loss of the business side caused by the arbitrary triggering of task scheduling instructions or the excessive number of triggers.

[0014] Optionally, the step of calling the corresponding task scheduling instruction in the corresponding database to control the business system to execute the task to be executed includes: detecting whether the task to be executed has failed; if the business system fails to execute the task to be executed, determining whether the business system chooses to enable alarms based on the advanced configuration information filled in by the business system; if the business system chooses to enable alarms, issuing a multi-channel subscribing alarm; if the business system successfully executes the task to be executed, not sending the multi-channel subscribing alarm.

[0015] By adopting the above technical solution, when the multi-scenario task scheduling platform detects that the business terminal has failed to execute a task, it will send an alarm to the business terminal. There are multiple alarm methods, all of which are selected by the business terminal. The business terminal can also choose whether to send an alarm or how many alarms to send based on the importance of the task. This ensures that the business terminal can know about the task failure as soon as possible and make adjustments accordingly, so as to avoid losses caused by the business terminal not being able to know about and handle the task failure in a timely manner.

[0016] Optionally, detecting that the business system fails to execute the task to be executed includes: continuously calling the corresponding task scheduling instruction to control the business system to execute the task to be executed; if the task to be executed is executed successfully, recording the number of times the task scheduling instruction is called and the timeout time of the task execution; if the task to be executed continues to fail, recording the number of execution failures.

[0017] By adopting the above technical solution, when the business side fails to execute a task, the multi-scenario task scheduling platform continuously calls the task scheduling instruction. Even if the business side fails to execute the task due to network instability or other special reasons, it is still possible to successfully execute the task by continuously calling the task scheduling instruction, thus minimizing the losses caused by the business side's failure to execute tasks in a timely manner. If the task is successfully executed, the number of calls and the time spent executing the task will be recorded. If the task still fails to execute after continuously calling the task scheduling instruction, the number of executions will also be recorded to facilitate subsequent investigation of the cause of the task failure. Based on the cause of the failure, improvements can be made to avoid the recurrence of such problems, reducing the manpower and resources spent on subsequent troubleshooting and enabling timely handling of business matters.

[0018] Optionally, after detecting that the business system has failed to execute the task to be executed, the method further includes: setting the trigger time and number of triggers for the multi-channel subscribing alarm based on the task level and the scheduling type; if the task level is identified as the normal level, then prohibiting the sending of the multi-channel subscribing alarm; if the task level is identified as the important level, then sending the multi-channel subscribing alarm.

[0019] By adopting the above technical solution, since tasks vary in type and importance, if a task is not important, alarms can be restricted to avoid high-frequency alarm sending from interfering with the business side; if a task is important, alarms can be set to be sent at multiple times and frequencies, and the latest number of failures and reasons will be sent to the user through alarms. There are also multiple ways to send alarms, which are suitable for various occasions and various groups of people, making it highly practical.

[0020] Secondly, this application provides a multi-scenario task scheduling device, employing the following technical solution: A multi-scenario task scheduling device, comprising: an acquisition module, a connection module, a setting module, an execution module, and an alarm module; wherein, the acquisition module is used to acquire basic information of the business system and advanced configuration filled in by the business system, the advanced configuration including: task level, scheduling type, and whether to enable alarm; the connection module is used to connect to the business system; the setting module is used to set corresponding task scheduling instructions for each task to be executed by the business system; the execution module is used to call the corresponding task scheduling instructions to control the business system to execute the task to be executed when any task to be executed by the business system needs to be executed; the alarm module is used to issue an alarm when the business system fails to execute the task to be executed.

[0021] By adopting the above technical solutions, the multi-scenario task scheduling platform can connect with multiple business systems simultaneously. Business users can quickly connect through simple configuration and simultaneously call tens of millions of task scheduling instructions to control the corresponding business systems to execute tasks. Data flow becomes clearer, and data storage and retrieval are easier. For tasks that fail to execute, the multi-scenario task scheduling platform will continue to call task scheduling instructions to ensure that the business user can successfully execute the task and avoid losses caused by unsuccessful task execution. It will also issue alarms through various methods, and the alarm time and number will be set according to the user-defined task importance, reducing the consumption of manpower and resources and ensuring that business processes can be handled on time.

[0022] Thirdly, this application provides an electronic device that adopts the following technical solution: it includes a processor, a memory, a user interface, and a network interface. The memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory so that the electronic device executes a computer program such as any of the interview matching degree judgment methods described above.

[0023] Fourthly, this application provides a computer-readable storage medium that stores a computer program capable of being loaded by a processor and executing any of the above-mentioned interview matching degree judgment methods.

[0024] In summary, this application includes at least one of the following beneficial technical effects:

[0025] 1. It can handle multiple business simultaneously, ensuring that each task scheduling instruction is under monitoring, reducing the consumption of manpower and resources, ensuring timely processing of business, and improving the speed of data reading, writing and querying when calling and executing several task scheduling instructions.

[0026] 2. It can simultaneously invoke tens of millions of task scheduling instructions to control the corresponding business systems to execute tasks. For tasks that fail to execute, the multi-scenario task scheduling platform will continue to invoke task scheduling instructions to ensure that the business side can successfully execute the task as much as possible, avoid losses caused by unsuccessful task execution, and will also issue alerts through various alarm methods. Attached Figure Description

[0027] Figure 1 This is a flowchart illustrating a multi-scenario task scheduling method according to an embodiment of this application;

[0028] Figure 2 This is a schematic diagram of a multi-scenario task scheduling device according to an embodiment of this application;

[0029] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application.

[0030] Explanation of reference numerals in the attached diagram: 1. Acquisition module; 2. Connection module; 3. Setting module; 4. Execution module; 5. Alarm module; 1000. Electronic device; 1001. Processor; 1002. Communication bus; 1003. User interface; 1004. Network interface; 1005. Memory. Detailed Implementation

[0031] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0032] In the description of the embodiments of this application, words such as "illustrative," "for example," or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "illustrative," "for example," or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Rather, the use of words such as "illustrative," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0033] The present application will be further described in detail below with reference to the accompanying drawings.

[0034] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be described in further detail below with reference to the accompanying drawings. Before introducing the embodiments of the present invention, some terms involved in the embodiments of the present invention will be defined and explained first.

[0035] Task scheduling: Task scheduling is a crucial component of operating systems. For real-time operating systems, task scheduling directly impacts their real-time performance. Common methods include: interruptible scheduling (critically preventing priority inversion) and non-interruptible scheduling (first-come, first-served, uninterrupted). Application software is a type of software situated between application systems and system software. It utilizes the basic service functions provided by system software to connect various parts of a network application system or different applications, achieving resource and function sharing.

[0036] Multi-scenario task scheduling platform: This platform primarily handles delayed tasks, triggered tasks, and multi-channel subscribed alerts. These tasks have variable scheduling frequencies, which are often not supported by ordinary task scheduling middleware. Low-frequency tasks typically require manual intervention or direct requests to third-party interfaces, necessitating significant additional configuration. Business users can achieve rapid and efficient development and iteration through simple configuration, making data flow clearer and more traceable.

[0037] Multi-channel subscribed alerts: Business users can choose from various alert methods such as voice alerts, application group alerts, personal DingTalk alerts, and global alert groups, depending on the importance of the task. The system will limit the alert frequency based on the task importance set by the user to avoid high-frequency alerts from interfering with the user. It will also send important information such as the latest number of failures and the reasons for failures to the user.

[0038] HBase is a highly reliable, high-performance, column-oriented, scalable distributed database primarily used to store unstructured and semi-structured loosely formatted data. A single HBase table can have billions of rows and millions of columns, and data can be inserted in both horizontal and vertical dimensions, offering significant flexibility. While the performance of querying and writing data in a relational database table drops exponentially when the number of records reaches hundreds of millions—a disaster for traditional databases—HBase can handle billions or even more records in a single table without performance issues, even when limiting a specific column. Unlike many row-oriented relational databases, HBase is column-oriented in its storage and access control; each column is stored independently and supports independent column-based retrieval.

[0039] MySQL database: MySQL is a relational database management system. Relational databases store data in different tables, rather than putting all data in one large repository, which increases speed and improves flexibility. The SQL language used by MySQL is the most commonly used standardized language for accessing data. MySQL software employs a dual-licensing policy. Due to its small size, high speed, and low total cost of ownership, especially this characteristic, MySQL is generally chosen as the database for the development of small to medium-sized and large websites.

[0040] Figure 1 This is a flowchart illustrating a multi-scenario task scheduling method according to an embodiment of this application. It should be understood that, although... Figure 1 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows; unless explicitly stated otherwise, there is no strict order requirement for the execution of these steps, and they can be executed in other orders; and Figure 1 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0041] This application discloses a multi-scenario task scheduling method, such as Figure 1As shown, the method includes steps S1-S4.

[0042] Step S1: Obtain basic information from multiple business systems.

[0043] Specifically, when some terminal devices, such as computers or mobile phones, need to connect with a multi-scenario task scheduling platform, they need to fill in some basic information, including name information, registration method information, and machine address information.

[0044] Step S2: The multi-scenario task scheduling platform connects to the business system.

[0045] In one example, based on the name and machine address information filled in by the business end, the multi-scenario task scheduling platform obtains the basic information and connects to the business end's device, which can be a computer or a mobile phone.

[0046] The registration method information includes automatic registration and manual registration; if the business system selects automatic registration, then the corresponding task scheduling instructions are set for all terminal devices containing the business system; if the business system selects manual registration, then the corresponding task scheduling instructions are set for some terminal devices containing the business system.

[0047] In one example, if the business side chooses automatic registration, then when the multi-scenario task platform connects to the business side's computer or mobile phone, any computer or mobile phone containing the business program will connect to the platform; if the business side chooses manual registration, then the business side can select some computers or mobile phones to connect according to its needs.

[0048] Step S3: Set corresponding task scheduling instructions for tasks to be executed by multiple business systems and save them. According to different calling frequencies, save the corresponding task scheduling instructions to the corresponding database.

[0049] In one example, different task scheduling instructions are set to control the corresponding system to execute relevant tasks, depending on the different tasks to be performed by each business system. For example, if the instruction is to pay salaries at 9:00 AM on the 10th of each month, then after the preset time, the multi-scenario task scheduling platform will call this task scheduling instruction to control the finance system to execute the salary payment instruction. If the business terminal is a mobile phone, when we shop online and select multiple items to pay for, the phone will automatically pop up a payment prompt due to the pre-set task scheduling instructions, and when our goods arrive at the delivery station, it will also automatically send us a pickup message.

[0050] The process of setting and saving corresponding task scheduling instructions for each task to be executed by each business system includes: based on the different calling frequencies of each task scheduling instruction, there are high calling frequencies and low calling frequencies of task scheduling instructions; storing high calling frequency task scheduling instructions in an HBase database; and storing low calling frequency task scheduling instructions in a MySQL database.

[0051] In one example, because the multi-scenario task scheduling platform needs to call tens of millions of task scheduling instructions every day, and the call time and frequency of each task scheduling instruction are not the same, the task scheduling instructions with high call frequency are stored in the HBase database, and the task scheduling instructions with low call frequency are stored in the MySQL database. For task scheduling instructions such as sending salaries to the finance system, which are executed once a month on average, these low-frequency instructions are stored in the MySQL database, while the payment instructions, which require high-frequency calls, are stored in the HBase database.

[0052] For example, when an HBase database experiences issues such as excessive data storage or high call frequency, causing data to become unreadable or unwriteable, a portion of the data in the HBase database will be transferred to the MySQL database until the HBase database returns to normal. Similarly, the MySQL database will also be transferred. The two databases work together to better enable the reading, writing, and querying of over ten million data entries per day.

[0053] After setting and saving the corresponding task scheduling instructions for tasks to be executed by multiple business systems, the process also includes: obtaining the advanced configuration filled in by the business systems. The advanced configuration includes: task level configuration, scheduling type configuration, and whether to enable alarms. The task level configuration includes normal level and important level. The scheduling type includes cron type, no type, and fixed speed type.

[0054] In one example, when the scheduling type is set to cron, a preset number of times can be triggered at a specific time, for example, seven times at 11 PM tomorrow. When the scheduling type is set to none, there is no scheduling type, and the task scheduling command will not be invoked to trigger the required processing. When the scheduling type is set to fixed speed, it can be triggered at a specific time each day, for example, once at 11 PM every day. The task level is divided into normal and important levels. For example, if the task is a normal task, such as reminding the business system to clock in, setting the scheduling type to fixed speed will trigger clock-in at 8 AM and 6 PM. If the task fails, you can choose not to enable alarms or select only one alarm. Another example is when the business needs to process a large amount of business. The task level is set to important, and then the scheduling type is set to select the time and number of times the scheduling command is invoked. For example, if the task scheduling command needs to be invoked seven times every night at 11 PM, the scheduling type is cron; if it needs to be invoked once every hour, the fixed speed type is selected. When the task fails, you can choose multiple alarms or multiple alarm methods, such as voice alarms, application group alarms, and email alarms.

[0055] Step S4: When executing a task to be executed, the corresponding task scheduling instruction in the database is invoked to control the business system to execute the task to be executed.

[0056] In one example, each business system has a corresponding task scheduling instruction set to control the execution of tasks by that system. Each business system has a corresponding scheduling time and execution count set. When the set time is reached, the task scheduling instruction is invoked to control the business system to execute the task.

[0057] The corresponding task scheduling instructions control the business system to execute the tasks to be executed, including: detecting whether the tasks to be executed have been executed successfully; if the business system fails to execute the tasks to be executed, based on the advanced configuration filled in by the business system, if the business system chooses to enable alarms, then issue multi-channel subscribing alarms; if the business system successfully executes the tasks to be executed, then do not send multi-channel subscribing alarms; multi-channel subscribing alarms include voice alarms, application group alarms, and email alarms.

[0058] In one example, the multi-scenario task scheduling platform monitors the task execution status in real time each time the system executes a task. For instance, when the company's financial system sends employee salaries, if the business system fails to execute the instruction to send employee salaries due to network latency or regional power outages, the multi-scenario task platform will issue an alert. The alert will be sent according to the user's settings, either by sending an email or a group message to notify the company's management or employees of the task failure.

[0059] The task level configuration includes normal level and important level. If the business system fails to execute the task to be executed, the following actions are taken: continuously call the corresponding task scheduling instruction to control the business system to execute the task to be executed. If the task to be executed is executed successfully, the number of times the task scheduling instruction is called and the timeout time of the task execution are recorded. If the task to be executed continues to fail, the number of execution failures is recorded.

[0060] In one example, if a task fails to execute due to network instability or other special reasons on the business side, the multi-scenario task scheduling platform will continue to send task scheduling instructions, as many times as possible, until the business side recovers and executes the task to be executed. Then, the reason for the failure and the number of calls will be recorded. If the task still fails to execute after multiple calls, the number of calls will be recorded, as well as the reason for the failure.

[0061] After detecting that the business system has failed to execute the task to be executed, the following steps are also taken: Based on the task level and scheduling type, set the trigger time and number of triggers for multi-channel subscribing alarms. If the task level is identified as normal, multi-channel subscribing alarms are prohibited from being sent; if the task level is identified as important, multi-channel subscribing alarms are sent.

[0062] In one example, when the company's finance system is issuing salaries to employees, the task is classified as "important" due to the large amount of money involved. However, if the finance system crashes or other unforeseen circumstances prevent timely salary payments, the reason for the task's failure is communicated to employees via group messages. Multiple email alerts can then be sent to relevant finance personnel to remind them to investigate the cause of the delay. If the task is classified as "normal" and the task is not important, then no alert can be issued upon task failure.

[0063] Based on the above method, this application also discloses a schematic diagram of a multi-scenario task scheduling method.

[0064] like Figure 2 As shown, the device includes: an acquisition module 1, a connection module 2, a setting module 3, an execution module 4, and an alarm module 5.

[0065] The acquisition module 1 is used to acquire basic information and advanced configurations filled in by the business system. The advanced configurations include: task level, scheduling type, and whether alarms are enabled; the connection module 2 is used to connect to the business system; the setting module 3 is used to set corresponding task scheduling instructions for each task to be executed by each business system.

[0066] The execution module 4 is used to call the corresponding task scheduling instruction to control the business system to execute the task when any task to be executed in any business system needs to be executed; the alarm module 5 is used to issue an alarm when the business system fails to execute the task to be executed.

[0067] It should be noted that the above embodiments of the apparatus are only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0068] Please see Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 3 As shown, the electronic device 1000 may include: at least one processor 1001, at least one network interface 1004, a user interface 1003, a memory 1005, and at least one communication bus 1002.

[0069] The communication bus 1002 is used to realize the connection and communication between these components.

[0070] The user interface 1003 may include a display screen and a camera. Optionally, the user interface 1003 may also include a standard wired interface and a wireless interface.

[0071] The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

[0072] The processor 1001 may include one or more processing cores. The processor 1001 connects to various parts of the server using various interfaces and lines, and performs various server functions and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 1005, and by calling data stored in the memory 1005. Optionally, the processor 1001 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 1001 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content to be displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 1001 and may be implemented as a separate chip.

[0073] The memory 1005 may include random access memory (RAM) or read-only memory. Optionally, the memory 1005 may include a non-transitory computer-readable storage medium. The memory 1005 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 1005 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 1005 may also be at least one storage device located remotely from the aforementioned processor 1001. Figure 3 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an application program for a multi-scenario task scheduling method.

[0074] exist Figure 3In the electronic device 1000 shown, the user interface 1003 is mainly used to provide an input interface for the user and obtain the user input data; while the processor 1001 can be used to call an application program stored in the memory 1005 that is a multi-scenario task scheduling method. When executed by one or more processors, the electronic device executes one or more of the methods described in the above embodiments.

[0075] An electronic device readable storage medium stores instructions that, when executed by one or more processors, cause the electronic device to perform one or more of the methods described in the above embodiments.

[0076] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0077] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0078] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some service interfaces; indirect couplings or communication connections between devices or units may be electrical or other forms.

[0079] The units described as separate components may or may not be physically separate. 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 units can be selected to achieve the purpose of this embodiment according to actual needs.

[0080] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0081] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0082] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Other embodiments of this disclosure will be readily apparent to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims

1. A multi-scenario task scheduling method, characterized in that, An application to a multi-scenario task scheduling platform includes the following method: acquiring basic information of multiple business systems, wherein the basic information includes the name information, registration method information, and machine address information of the business systems; connecting the multiple business systems based on the name information and machine address information; setting corresponding task scheduling instructions for tasks to be executed by the multiple business systems; each task scheduling instruction has a different calling frequency, and according to the different calling frequencies, saving the corresponding task scheduling instructions to a corresponding database; when executing the task to be executed, calling the corresponding task scheduling instructions in the corresponding database to control the business system to execute the task to be executed.

2. The multi-scenario task scheduling method according to claim 1, characterized in that, The step of obtaining basic information about multiple business systems includes: obtaining the registration methods of the multiple business systems; the registration methods include automatic registration and manual registration; if a business system selects the automatic registration method, then the corresponding task scheduling instruction is set for all terminal devices containing the business system; if a business system selects the manual registration method, then the corresponding task scheduling instruction is set for some of the terminal devices containing the business system.

3. The multi-scenario task scheduling method according to claim 1, characterized in that, The step of saving the corresponding task scheduling instructions to the corresponding database according to different calling frequencies includes: the task scheduling instructions have high calling frequencies and low calling frequencies; when the number of calls reaches a preset threshold, it belongs to the high calling frequency; when the number of calls does not reach the preset threshold, it belongs to the low calling frequency; the task scheduling instructions with high calling frequencies are stored in a preset HBase database; and the task scheduling instructions with low calling frequencies are stored in a preset MySQL database.

4. The multi-scenario task scheduling method according to claim 1, characterized in that, After saving the corresponding task scheduling instructions to the corresponding database according to different call frequencies, the method further includes: obtaining the advanced configuration information filled in by the business system. The advanced configuration includes: task level configuration, scheduling type configuration, and alarm enable / disable configuration. The task level configuration includes normal level and important level. The scheduling type configuration includes cron type, no type, and fixed speed type.

5. The multi-scenario task scheduling method according to claim 4, characterized in that, The step of calling the corresponding task scheduling instruction in the corresponding database to control the business system to execute the task to be executed includes: detecting whether the task to be executed has failed; if the business system fails to execute the task to be executed, determining whether the business system chooses to enable alarms based on the advanced configuration information filled in by the business system; if the business system chooses to enable alarms, issuing a multi-channel subscribing alarm; if the business system successfully executes the task to be executed, not sending the multi-channel subscribing alarm; the multi-channel subscribing alarm includes voice alarms, application group alarms, and email alarms.

6. The multi-scenario task scheduling method according to claim 5, characterized in that, The detection of the failure of the business system to execute the task to be executed includes: continuously calling the corresponding task scheduling instruction to control the business system to execute the task to be executed; if the task to be executed is executed successfully, the number of times the task scheduling instruction is called and the timeout time of the task execution are recorded; if the task to be executed continues to fail, the number of execution failures is recorded.

7. The multi-scenario task scheduling method according to claim 5, characterized in that, After detecting that the business system has failed to execute the task to be executed, the method further includes: setting the trigger time and number of triggers for the multi-channel subscribing alarm based on the task level and the scheduling type; if the task level is identified as the normal level, then the sending of the multi-channel subscribing alarm is prohibited; if the task level is identified as the important level, then the multi-channel subscribing alarm is sent.

8. A multi-scenario task scheduling device, characterized in that, The device includes: an acquisition module (1), a connection module (2), a setting module (3), and an execution module (4); wherein, The acquisition module (1) is used to acquire basic information of multiple business systems, wherein the basic information includes the name information, registration method information and machine address information of the business systems; The connection module (2) is used to connect the multiple business systems based on the name information and machine address information of the multiple business systems; The setting module (3) is used to set corresponding task scheduling instructions for the tasks to be executed by the multiple business systems; each task scheduling instruction has a different calling frequency, and according to the different calling frequencies, the corresponding task scheduling instructions are saved to the corresponding database respectively; The execution module (4) is used to call the corresponding task scheduling instruction in the corresponding database to control the business system to execute the task when the task to be executed is executed.

9. An electronic device, characterized in that, The device includes a processor, a memory, a user interface, and a network interface. The memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory to cause the electronic device to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer program is stored that can be loaded by a processor and executed as described in any one of claims 1-7.

Images