Dial testing task scheduling method and device in financial scene and electronic equipment

Abstract

The invention discloses a dial testing task scheduling method and device in a financial scene and electronic equipment, and relates to the field of financial science and technology, the method comprises the steps that financial dial testing task information is read, the financial dial testing task information at least comprises a dial testing strategy and a dial testing point environment, and the dial testing strategy at least comprises a task type and a task execution frequency; according to the task type and the task execution frequency, distributing each financial dial testing task to a plurality of preset asynchronous scheduling queues through a financial dial testing task scheduling center, extracting a to-be-executed financial dial testing task from the asynchronous scheduling queues, and issuing the financial dial testing task to a financial dial testing task executor in each dial testing point environment, and the financial dial testing task executor executes the financial dial testing task to obtain a task execution result. According to the invention, the technical problem that there is no proactive dial test scheme for the network quality in a financial scene in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of financial technology or other related fields, and in particular to a dialing task scheduling method and device, and electronic equipment in a financial scenario. Background Art

[0002] With the continuous development of the Internet era and the digital financial industry, stable quality and service are the lifeline of financial enterprises, while user choice is the symbol of business success, and business quality is the core factor affecting user behavior choices. Dial-up testing is a proactive monitoring and testing method that mainly uses cross-regional monitoring networks and uses real end-user usage scenarios as a perspective to monitor the functional availability, performance management, and network performance of target applications, thereby discovering potential faults before end users do.

[0003] Network quality monitoring in financial scenarios is usually implemented using a network quality monitoring system. In the existing technology, there is a lack of network quality monitoring in financial scenarios, that is, there is a lack of active dialing testing initiated by the dialing testing platform on the target network, that is, there is a lack of active monitoring of network quality in financial scenarios, which affects the network quality indicators of financial institutions.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a method and device for scheduling dialing test tasks in a financial scenario, and an electronic device, so as to at least solve the technical problem of the lack of a solution for actively dialing test on network quality in a financial scenario in the related art.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a dialing test task scheduling method in a financial scenario is provided, comprising: reading financial dialing test task information, wherein the financial dialing test task information is information corresponding to each financial dialing test task configured by a dialing test console, the financial dialing test task information at least includes: a dialing test strategy and a dialing test point environment, the dialing test strategy at least includes: a task type and a task execution frequency, the financial dialing test task refers to a task corresponding to a financial service proposed by a consumer to a financial institution; according to the task type and the task execution frequency, each of the financial dialing test tasks is allocated to a plurality of preset asynchronous scheduling queues by a financial dialing test task scheduling center, wherein each of the asynchronous scheduling queues corresponds to a specified task execution rule; extracting the financial dialing test tasks to be executed from the asynchronous scheduling queues, and sending the financial dialing test tasks to financial dialing test task executors in each dialing test point environment, and the financial dialing test task executors execute the financial dialing test tasks to obtain task execution results.

[0007] Optionally, the step of allocating each of the financial dialing tasks to a plurality of preset asynchronous scheduling queues through a financial dialing task scheduling center according to the task type and the task execution frequency includes: locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task, wherein each of the asynchronous scheduling queues corresponds to a task type; determining the next execution time point of the financial dialing task according to the task execution frequency, and sending the financial dialing task and the corresponding dialing task information to the located asynchronous scheduling queue when the next execution time point is triggered; and asynchronously pushing the financial dialing task to a plurality of distributed dialing point environments through the asynchronous scheduling queue using an event-driven mechanism.

[0008] Optionally, before locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task, it also includes: creating multiple distributed task queues; configuring the executable task execution frequency and task type for each distributed task queue to obtain multiple asynchronous scheduling queues.

[0009] Optionally, the step of sending the financial dial test task to the financial dial test task executor in each dial test point environment includes: extracting the task type, task execution parameters and expected verification standards of the financial dial test task to be executed from the asynchronous scheduling queue, wherein the task execution parameters at least include: task execution frequency; determining the dial test point environment to be assigned to the financial dial test task according to the task type, the task execution parameters and the expected verification standards of the financial dial test task; and asynchronously pushing the financial dial test task to the corresponding dial test point environment through a distributed message queue, wherein the financial dial test task executor in each dial test point environment receives the task information in the asynchronous scheduling queue, and stores the financial dial test task in a local task queue according to the task information.

[0010] Optionally, the step of executing the financial dialing test task by the financial dialing test task executor and obtaining the task execution result includes: the dialing test task executor reads the task information of the financial dialing test task to be executed from the local task queue; the dialing test task executor selects a preset task processing thread Handler to execute the task according to the task type in the financial dialing test task information, and the task processing thread Handler executes a predetermined dialing test action according to the task type, and the dialing test action includes at least one of the following network request, port detection, and file transfer test; during the task execution process, the dialing test task executor records the task execution result, wherein the task execution result includes at least one of the following: start time, end time, execution exception, and result of interaction with financial services; the dialing test task executor analyzes the task execution result according to the task type and expected verification criteria to determine the availability of financial services; and feeds back the task execution result to the financial dialing test task scheduling center through a distributed message queue.

[0011] Optionally, before reading the financial dialing test task information, it also includes: receiving the dialing test type, task type, task execution frequency, task status, expected verification standard, and alarm rule of each financial dialing test task configured online by the user end through the dialing test console, and generating the dialing test strategy; receiving the communication protocol, network area, operator and firewall of each financial dialing test task through the dialing test console, and generating the dialing test point environment; determining the financial dialing test task information based on the dialing test strategy and the dialing test point environment of each financial dialing test task; and recording and persisting the financial dialing test task information in a database.

[0012] Optionally, the dial test types include: custom dial test and instant dial test, and the custom dial test refers to triggering task execution according to a configured frequency period; the task type includes at least one of the following: network quality, page performance, port performance, file transfer, audio and video experience; the task status is one of the following: dial test task enabled, dial test task stopped, dial test task deleted; the expected verification standard refers to setting different expected verification results for financial dial test task execution for different task types; the alarm rule refers to issuing an alarm notification according to the result of the expected task verification.

[0013] According to another aspect of an embodiment of the present invention, a dialing test task scheduling device in a financial scenario is further provided, comprising: a task information reading unit, configured to read financial dialing test task information, wherein the financial dialing test task information is information corresponding to each financial dialing test task configured through a dialing test console, the financial dialing test task information at least includes: a dialing test strategy and a dialing test point environment, the dialing test strategy at least includes: a task type and a task execution frequency, the financial dialing test task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution; a task allocation unit, configured to allocate each of the financial dialing test tasks to a plurality of preset asynchronous scheduling queues through a financial dialing test task scheduling center according to the task type and the task execution frequency, wherein each of the asynchronous scheduling queues corresponds to a specified task execution rule; a task execution unit, configured to extract the financial dialing test task to be executed from the asynchronous scheduling queue, and send the financial dialing test task to a financial dialing test task executor in each dialing test point environment, so that the financial dialing test task executor executes the financial dialing test task to obtain a task execution result.

[0014] Optionally, the task allocation unit includes: a task type positioning module, used to locate the asynchronous scheduling queue corresponding to the task type of the financial dialing task, wherein each of the asynchronous scheduling queues is pre-configured with a corresponding task type; a task frequency and time determination module, used to determine the next execution time point of the financial dialing task according to the task execution frequency; a task issuing module, used to issue the financial dialing task and the corresponding dialing task information to the located asynchronous scheduling queue when the next execution time point is triggered; an asynchronous push module, used to asynchronously push the financial dialing task to multiple distributed dialing point environments through the asynchronous scheduling queue using an event-driven mechanism, such as Kafka.

[0015] Optionally, the dialing task scheduling device in the financial scenario also includes: a task queue creation unit, used to create multiple distributed task queues before locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task; a task queue configuration unit, used to configure the executable task execution frequency and task type for each of the distributed task queues to obtain multiple asynchronous scheduling queues.

[0016] Optionally, the task execution unit includes: a task extraction module, used to extract the task type, task execution parameters and expected verification standards of the financial dialing task to be executed from the asynchronous scheduling queue; a dialing point environment determination module, used to determine the dialing point environment to which the financial dialing task is to be assigned according to the task type, the task execution parameters and the expected verification standards of the financial dialing task; a message queue pushing module, used to asynchronously push the financial dialing task to the corresponding dialing point environment through a distributed message queue, wherein the financial dialing task executor in each dialing point environment receives the task information in the asynchronous scheduling queue, and stores the financial dialing task in the local task queue according to the task information.

[0017] Optionally, the task execution unit further includes: a task reading module, used by the financial dialing task executor to read the task information of the financial dialing task to be executed from the local task queue; a task processing thread selection module, used by the financial dialing task executor to select a preset task processing thread Handler to execute the task according to the task type in the financial dialing task information, and the task processing thread Handler executes a predetermined dialing action according to the task type; an execution result recording module, used by the financial dialing task executor to record the task execution result during the task execution process, and the task execution result includes but is not limited to the start time, end time, execution exception and the result of interaction with the financial service; an execution result analysis module, used by the financial dialing task executor to analyze the task execution result according to the task type and the expected verification standard to determine the availability of the financial service; a result feedback module, used to feed back the task execution result to the financial dialing task scheduling center through a distributed message queue.

[0018] Optionally, the dialing test task scheduling device in the financial scenario also includes: a dialing test strategy generation unit, which is used to receive the dialing test type, task type, task execution frequency, task status, expected verification standard, and alarm rule of each financial dialing test task configured online by the user end through the dialing test console, and generate the dialing test strategy; a dialing test point environment generation unit, which is used to receive the communication protocol, network area, operator and firewall of each financial dialing test task through the dialing test console, and generate the dialing test point environment; a task information determination unit, which is used to determine the financial dialing test task information based on the dialing test strategy and the dialing test point environment of each financial dialing test task; and a task information storage unit, which is used to record and persist the financial dialing test task information in a database.

[0019] Optionally, the dialing test types in the dialing test strategy generation unit include: custom dialing test, instant dialing test, wherein custom dialing test refers to triggering task execution according to a configured frequency period; the task types include but are not limited to: network quality, page performance, port performance, file transfer, audio and video experience; the task status includes: dialing test task enabled, dialing test task stopped, dialing test task deleted; the expected verification standard refers to setting different expected verification results for financial dialing task execution for different task types; the alarm rule refers to issuing an alarm notification according to the expected verification result.

[0020] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any of the above-mentioned dialing task scheduling methods in a financial scenario.

[0021] According to another aspect of an embodiment of the present invention, an electronic device is also provided, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the above-mentioned dialing task scheduling methods in a financial scenario.

[0022] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of the dialing task scheduling method in a financial scenario described above are implemented.

[0023] In the present disclosure, the financial dialing task information is first read, and each financial dialing task is assigned to a plurality of preset asynchronous scheduling queues through a financial dialing task scheduling center according to the task type and the task execution frequency. Each asynchronous scheduling queue corresponds to a specified task execution rule, and the financial dialing task to be executed is extracted from the asynchronous scheduling queue, and the financial dialing task is sent to the financial dialing task executor in each dialing point environment. The financial dialing task executor executes the financial dialing task to obtain a task execution result, wherein the financial dialing task information is information corresponding to each financial dialing task configured through the dialing console, and the financial dialing task information at least includes: a dialing strategy and a dialing point environment. The dialing strategy at least includes: a task type and a task execution frequency. The financial dialing task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution.

[0024] In the present disclosure, active dialing testing for financial services and the configuration, scheduling, distribution and operation of large-scale dialing testing tasks are supported. Asynchronous scheduling and push of financial dialing testing tasks can be achieved through distributed message queues, and financial dialing testing tasks are distributed to financial dialing testing task executors in each dialing testing point environment. The financial dialing testing task executors execute the financial dialing testing tasks to obtain task execution results, thereby improving the accuracy and efficiency of network monitoring in financial scenarios, meeting the active dialing testing capabilities of enterprise-level financial services, and solving the technical problem of the lack of solutions for active dialing testing of network quality in financial scenarios in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0026] Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing a dialing task scheduling method in a financial scenario is shown;

[0027] Figure 2 is a flowchart of an optional dialing task scheduling method in a financial scenario according to an embodiment of the present invention;

[0028] Figure 3 is a flowchart of an optional active dialing task management method adapted to financial scenarios according to an embodiment of the present invention;

[0029] Figure 4 is a schematic diagram of an optional dialing task scheduling device according to an embodiment of the present invention;

[0030] Figure 5 is a schematic diagram of an optional dialing task execution device according to an embodiment of the present invention;

[0031] Figure 6 is a schematic diagram of an optional dialing task scheduling device in a financial scenario according to an embodiment of the present invention;

[0032] Figure 7 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] To facilitate those skilled in the art to understand the present invention, some terms or nouns involved in the embodiments of the present invention are explained below:

[0036] Dial testing is a network monitoring method that simulates real user behavior to test the target website or application at specific time intervals.

[0037] The dial test console can be run on the server / cloud computing center and accessed through a browser. Users can configure the details of the dial test task, monitor the task execution status, and view the real-time and historical data of the dial test results.

[0038] The financial dial test task dispatch center is responsible for receiving, analyzing, dispatching and issuing dial test tasks. The dispatch center can be a physical server or a service in a virtualized environment. It is usually deployed in the data center or cloud service environment of a financial institution / enterprise to ensure data security and high availability of the system.

[0039] Dial-up test point environment: Dial-up test points are distributed in different geographical locations and use different network environments and devices to simulate real user behavior. The dial-up test point environment may include various types of devices, such as personal computers, smartphones, servers, etc., and various network conditions, such as 4G / 5G mobile networks, corporate intranets, etc. The dial-up test point environment can be a physical device, a virtual machine, or a container, which can be flexibly configured according to the needs of the dial-up test.

[0040] The financial dial test task executor is a software or hardware module deployed in each dial test point environment, responsible for executing the dial test task, recording the execution results, and feeding the data back to the task scheduling center or monitoring and analysis system. The executor can be a lightweight client software installed on various devices, or a dedicated hardware device used to execute a specific type of dial test task.

[0041] The database system is used to store dialing task information, execution results, and analysis data. It can be a relational database or a database specifically used for big data and real-time analysis, supporting high-concurrency data writing and reading, as well as long-term data storage and historical analysis.

[0042] The monitoring and analysis system is used to display and analyze the dial test results, helping users and operation and maintenance teams to intuitively understand the performance and availability of financial services. The monitoring and analysis system can be deployed within the enterprise or as part of the cloud service, providing flexible data visualization and alarm mechanisms.

[0043] It should be noted that the dialing task scheduling method and device in the financial scenario in the present disclosure can be used in the financial technology field to adapt to the active dialing scheme in the financial scenario to monitor the network quality of the financial institution. It can also be used in any field other than the financial technology field to adapt to the active dialing scheme in the financial scenario to monitor the network quality of the financial institution. The application field of the dialing task scheduling method and device in the financial scenario is not limited in the present disclosure.

[0044] It should be noted that the information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) collected by this disclosure are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with the relevant laws, regulations and standards of the relevant regions, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation portals are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0045] It should be noted that in the present disclosure, when collecting and analyzing customer information, corresponding operation entrances are provided for users to choose to agree or reject the automated decision results; if the user chooses to reject, the expert decision-making process is entered.

[0046] The following embodiments of the present invention can be applied to systems / applications / devices for scheduling dialing tasks in various financial scenarios. The present invention includes a console for configuring and managing dialing tasks, a persistence module for storing task information, asynchronous task scheduling and push through distributed message queues, task execution handlers supporting multiple communication protocols (task handlers execute tasks of different communication protocols), and a visualization tool for storing and analyzing client dialing data and real-time monitoring and analysis results (providing customized analysis views and supporting fast packet loss rate algorithms in network quality monitoring), thereby improving the accuracy and efficiency of network monitoring in financial scenarios.

[0047] The present invention takes real customer usage scenarios as the perspective, supports actual dialing testing of financial services, supports the configuration, scheduling, distribution and operation of large-scale dialing testing tasks through distributed task scheduling and decoupling task scheduling and execution, and can meet the active dialing testing capabilities of enterprise-level financial services.

[0048] The present invention is described in detail below in conjunction with various embodiments.

[0049] Embodiment 1

[0050] According to an embodiment of the present invention, an embodiment of a dialing task scheduling method in a financial scenario is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0051] The dialing task scheduling method embodiment in a financial scenario provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or mobile device) for implementing a dialing task scheduling method in a financial scenario is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more ( Figure 1, 102a, 102b, ..., 102n are used to illustrate) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU (Microcontroller Unit) or a programmable logic device FPGA (Field Programmable Gate Array)), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. Those skilled in the art can understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0052] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0053] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the dialing task scheduling method in the financial scenario in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the dialing task scheduling method in the financial scenario mentioned above is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0054] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0055] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0056] Under the above operating environment, this application provides Figure 2 The dialing task scheduling method in the financial scenario is shown. Figure 2 The present invention is a flowchart of an optional method for scheduling dialing tasks in a financial scenario according to an embodiment of the present invention.

[0057] It should be noted that the application scenario of this embodiment is in financial services (such as online banking, mobile payment, securities trading, etc.), and the stability and response time of the system are crucial to the user experience. This embodiment can simulate real user behavior through active dialing, monitor the availability and performance of these services, and promptly discover potential network delays, server failures, code errors and other problems to ensure the continuity and reliability of financial services. In addition, by setting expected verification standards and alarm rules, the technical solution provided by this embodiment can immediately trigger an alarm when an abnormality occurs in the service, help the operation and maintenance team quickly locate the problem, and reduce the direct impact on users. For example, when it is detected that the response time of the transaction system exceeds the preset threshold, the corresponding fault response mechanism can be immediately started to avoid long-term service interruption.

[0058] Based on the analysis of the dial test results, service bottlenecks or uneven resource allocation can be identified, providing data support for subsequent system optimization and expansion. For example, if it is found that the access delay of users in a certain area is high, the user experience can be improved by adjusting the network configuration or adding service nodes in the area.

[0059] It should be noted that, before reading the financial dialing task information, the present embodiment requires the user to configure the dialing task online through a unified dialing console, including: receiving the dialing type, task type, task execution frequency, task status, expected verification standard, and alarm rule of each financial dialing task configured online by the user end through the dialing console, and generating a dialing strategy; receiving the communication protocol, network area, operator, and firewall of each financial dialing task through the dialing console, and generating a dialing point environment; determining the financial dialing task information based on the dialing strategy and dialing point environment of each financial dialing task; and recording and persisting the financial dialing task information in a database.

[0060] The dialing test console mentioned in this embodiment is the front-end interface for users to interact with the financial dialing test system, allowing users to configure and manage financial dialing test tasks online. The design of the console should be user-friendly to ensure that users can intuitively set various aspects of the dialing test, including but not limited to task type, frequency, expected results and alarm conditions. The dialing test console automatically generates a dialing test strategy by receiving information such as the dialing test type (custom dialing test, instant dialing test), task type, execution frequency, task status, expected verification standards and alarm rules input by the user. The dialing test strategy is the guideline for the system to execute the dialing test task, including the execution conditions, expected results and exception handling mechanism of the task.

[0061] Among them, the dialing test types mentioned in this embodiment may include: custom dialing test and instant dialing test. Custom dialing test refers to triggering task execution according to the configured frequency period, and instant dialing test refers to executing the task immediately after the dialing test point receives the dialing test task; the task type includes at least one of the following: network quality, page performance, port performance, file transfer, audio and video experience; the task status is one of the following: dialing test task enabled, dialing test task stopped, dialing test task deleted; the expected verification standard refers to setting different expected verification results for financial dialing task execution for different task types; the alarm rule refers to issuing an alarm notification according to the result of the expected task verification.

[0062] The custom dial test mentioned in this embodiment means that the user can set the execution frequency and cycle of the task, such as every 5 minutes, every 10 minutes, every day, etc. The system automatically puts the task into the corresponding asynchronous scheduling queue according to these set conditions so that it can be executed at a specified time point. The instant dial test means that the user can trigger the instant dial test. This type of task does not need to wait for the preset cycle. Once the configuration is completed, the dial test starts immediately. For each task type mentioned in this embodiment: including network quality, page performance, port performance, file transfer, audio and video experience, etc., each type of task has its specific expected verification standards and alarm rules. For example, the network quality task may focus on indicators such as network delay and packet loss rate, while the page performance task may focus on page loading time and response speed. For the task status mentioned in this embodiment: including task enablement, task stop and task deletion, the user is provided with the ability to manage the task life cycle. Tasks in the enabled state will be scheduled for execution, tasks in the stopped state will be suspended until they are re-enabled by the user, and tasks in the deleted state will be removed from the system and will no longer be executed. The expected verification standard mentioned in this embodiment is the standard for the success or failure of the task defined by the user, depending on the task type. For example, the expected verification criteria for a network quality task may include network latency being less than a certain threshold, packet loss rate being less than a certain ratio, etc. For the alarm rules mentioned in this embodiment, if the task execution result does not meet the expected verification criteria, the system will trigger an alarm according to the user-defined alarm rules. This may include sending emails, SMS notifications, or displaying alarm information on the console, etc.

[0063] The dial test console receives information such as communication protocol, network area, operator, and firewall to generate the dial test point environment. The dial test point environment defines the network conditions and environment in which the system performs dial tests, ensuring the accuracy and reliability of the dial test results. Different dial test points may be located in different geographical locations, use different network service providers, and have different network configurations to comprehensively evaluate the performance of financial services under various conditions. Based on the above dial test strategies and dial test point environments, the system determines the specific information of each financial dial test task, including the execution parameters of the task, the expected verification conditions, etc. This information is the basis for the dial test task executor to execute tasks, monitor results, and trigger alarms. Finally, the system records and persists the generated financial dial test task information to the database. The database provides persistent storage of data to ensure that task information is not lost even when the system is restarted or encounters a failure. In addition, the database also supports the query and analysis of historical tasks, helping users and system administrators better understand the performance trends and failure modes of financial services.

[0064] like Figure 2 As shown, the dialing task scheduling method in the financial scenario may include the following steps:

[0065] Step S201, reading financial dialing task information. The financial dialing task information is information corresponding to each financial dialing task configured through the dialing console, and the financial dialing task information at least includes: dialing strategy, dialing point environment, and the dialing strategy at least includes: task type and task execution frequency. The financial dialing task refers to a task corresponding to a simulated financial service requested by a consumer to a financial institution.

[0066] Here, the dial test console is the interface for users to interact with the system. Users can configure the above information here. The system determines the details of the dial test task to be executed by reading the configuration information, providing a data basis for subsequent scheduling and execution.

[0067] This embodiment needs to pre-read the task information of each financial dialing task configured by the user before implementing the active dialing task issuance and task execution in the financial scenario. The reading of the financial dialing task information is the starting point of the entire dialing process. The dialing strategy in the financial dialing task information is a strategy for detailed planning of each dialing task, including at least the type of task and the execution frequency. The task type defines the specific goals of the dialing, such as network quality, page performance, port performance, file transfer, or audio and video experience. The execution frequency is the periodicity or immediacy of the task execution specified by the policy. The dialing point environment refers to the actual environmental conditions for performing the dialing operation, including but not limited to communication protocols, network areas, operators, and firewall settings, which means that the dialing task will be executed in a specific network environment to simulate the user's access experience under different conditions.

[0068] It should be noted that the financial dialing test task mentioned in this embodiment may refer to simulating a consumer's request for financial services to a financial institution, such as initiating an online payment, executing a stock transaction, etc., in order to verify the stability and performance of the financial services.

[0069] Step S202: Allocate each financial dialing task to a plurality of preset asynchronous scheduling queues through the financial dialing task scheduling center according to the task type and the task execution frequency, wherein each asynchronous scheduling queue corresponds to a specified task execution rule.

[0070] After reading the financial dialing task information, the system needs to distribute it to multiple preset asynchronous scheduling queues according to the task type and execution frequency. Here, the system needs to find the pre-configured asynchronous scheduling queue corresponding to the task type according to the task type in the read financial dialing task information, and then determine the next execution time point of the task according to the task execution frequency (immediate or periodic).

[0071] Optionally, step S202 includes: locating an asynchronous scheduling queue corresponding to the task type of the financial dialing task, wherein each asynchronous scheduling queue corresponds to a task type; determining the next execution time point of the financial dialing task according to the task execution frequency, and when the next execution time point is triggered, sending the financial dialing task and the corresponding dialing task information to the located asynchronous scheduling queue; and asynchronously pushing the financial dialing task to multiple distributed dialing point environments using an event-driven mechanism through the asynchronous scheduling queue.

[0072] In the management of financial dialing tasks, the efficiency and accuracy of task scheduling are crucial to ensure that dialing tasks can be executed according to the expected time and rules. In the financial dialing task scheduling center, the system will locate specific asynchronous scheduling queues according to the task type (such as network quality, page performance, port performance, file transfer, audio and video experience, etc.). Each queue is responsible for the scheduling and execution of a type of task. This mechanism can ensure the efficient processing of similar tasks and the reasonable allocation of resources. According to the execution frequency of the financial dialing task (immediate or periodic), the system will calculate the next execution time point of the task. For instant dialing tasks, they will be executed immediately once created; for dialing tasks with custom periods, the system will calculate the future execution time points according to the set period (such as every 5 minutes, every 10 minutes, every day, etc.). When the preset time point is reached, the financial dialing task scheduling center will send the task information to the corresponding asynchronous scheduling queue for execution.

[0073] In this embodiment, the asynchronous scheduling queue pushes task information to the dialing point environments distributed in different geographical locations in real time in an event-driven manner. This means that each dialing point environment does not need to actively query the scheduling center or queue, but waits for the event trigger in the queue to receive and execute a specific financial dialing task. This mechanism greatly reduces network latency and improves the efficiency and response speed of task execution.

[0074] Optionally, before locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task, the method further includes: creating multiple distributed task queues; configuring the executable task execution frequency and task type for each distributed task queue to obtain multiple asynchronous scheduling queues.

[0075] Before scheduling financial dial-up tasks, the system needs to have a complete, pre-configured queue system to support dial-up tasks of different types and frequencies. In the financial dial-up task scheduling center, the system administrator or automated script first needs to create multiple distributed task queues. Each queue corresponds to a specific combination of task type and execution frequency, such as "real-time network quality queue", "5-minute cycle page performance queue", etc. These queues are usually built on distributed message queue technology (such as Kafka) to provide high throughput and low latency communication capabilities.

[0076] Each distributed task queue will be configured in detail according to its corresponding task type and execution frequency. For example, an immediate dial test task will be assigned to a queue that can respond immediately, while a periodic dial test task will be assigned to a corresponding periodic queue according to its execution cycle. This configuration method ensures the flexibility and pertinence of task scheduling, and meets the different requirements for different types of tasks in financial dial test scenarios.

[0077] Through the above configuration process, the system forms a series of asynchronous scheduling queues, which can asynchronously allocate tasks to different queues according to task type and execution frequency, preparing for subsequent scheduling and task execution.

[0078] Step S203, extracting the to-be-executed financial dialing test task from the asynchronous scheduling queue, and sending the financial dialing test task to the financial dialing test task executor in each dialing test point environment, and the financial dialing test task executor executes the financial dialing test task to obtain the task execution result.

[0079] After the financial dialing task is assigned to the asynchronous scheduling queue, the next step is to extract the task and send it to the financial dialing task executor in each dialing point environment. The executor will specifically execute the dialing task and feedback the execution result to the system. Among them, the dialing task executor extracts the task information to be executed from the asynchronous scheduling queue to which it belongs. The executor will store the task information locally according to the task type and execution rules, and prepare for execution. After that, the executor selects the appropriate task handler (such as http, tcp / udp, ping, etc.) according to the task information to execute the financial dialing task, such as initiating network requests, performing port detection, testing file transfer, etc., to simulate real users' access to financial services.

[0080] It should be noted that during the task execution, the financial dialing task executor will record detailed information about the task execution, including the start time, end time, any abnormalities encountered during the execution, and the specific results of the interaction with the financial service. The executor will analyze the execution results based on the task type and expected verification standards to determine whether the status of the financial service meets expectations. Finally, the task execution results will be fed back to the financial dialing task scheduling center through a distributed message queue or directly stored in the result monitoring and analysis module. These results can be further analyzed to form a performance report for the financial service, providing a basis for system optimization and fault warning.

[0081] Here, the step of sending the financial dial test task to the financial dial test task executor in each dial test point environment includes: extracting the task type, task execution parameters and expected verification standard of the financial dial test task to be executed from the asynchronous scheduling queue, wherein the task execution parameters at least include: task execution frequency; determining the dial test point environment to which the financial dial test task is to be assigned according to the task type, task execution parameters and expected verification standard of the financial dial test task; and asynchronously pushing the financial dial test task to the corresponding dial test point environment through a distributed message queue, wherein the financial dial test task executor in each dial test point environment receives the task information in the asynchronous scheduling queue, and stores the financial dial test task in the local task queue according to the task information.

[0082] Based on the extracted financial dialing task information (task type, execution parameters, expected verification standards), the system dynamically determines the dialing point environment to which the task should be assigned. This process takes into account the characteristics of the dialing task, as well as factors such as the network conditions, geographical location, and operators of the dialing point environment, to ensure that the task can be executed in an environment that accurately reflects the target financial service usage scenario. For example, a network quality dialing task may be assigned to multiple dialing points with different network conditions in order to comprehensively evaluate the performance of financial services under network fluctuations.

[0083] The system asynchronously pushes the extracted and parsed financial dialing tasks to each selected dialing point environment through distributed message queue technology (such as Kafka, RabbitMQ, etc.). This asynchronous mechanism avoids direct synchronization waiting between the task scheduling center and the dialing point environment, and improves the execution efficiency and response speed of the system. After the financial dialing task executor in each dialing point environment receives the task information in the queue, it will store it in the local task queue. The local task queue ensures that even if the network connection with the scheduling center is temporarily interrupted, the dialing task executor can independently complete the task execution and result collection according to the task information in the queue, ensuring the continuity and reliability of the dialing task.

[0084] In the local task queue, the financial dial test task executor executes the corresponding dial test action according to the stored task information. This includes but is not limited to HTTP requests, TCP / UDP port detection, file transfer tests, audio and video experience checks, etc. The specific actions depend on the task type. During the execution process, the executor will record detailed execution logs, including the start time, end time, any abnormal situations encountered during the execution process, and the specific results of the interaction with the financial service. These execution results will serve as the basis for subsequent monitoring analysis and fault warning.

[0085] After completing the financial dialing task, the task executor will feed back the execution results to the financial dialing task dispatch center through the distributed message queue, or directly send it to the monitoring and analysis system for subsequent data analysis and decision support. This feedback mechanism forms a closed loop with the task extraction and allocation process, ensuring that the system can monitor the execution status and results of the financial dialing task in real time and accurately, providing strong data support for the performance optimization of financial services and rapid response to faults.

[0086] Optionally, the step of executing the financial dialing test task by the financial dialing test task executor and obtaining the task execution result includes: the dialing test task executor reads the task information of the financial dialing test task to be executed from the local task queue; the dialing test task executor selects a preset task processing thread Handler to execute the task according to the task type in the financial dialing test task information, and the task processing thread Handler executes a predetermined dialing test action according to the task type, and the dialing test action includes at least one of the following network request, port detection, and file transfer test; during the task execution process, the dialing test task executor records the task execution result, wherein the task execution result includes at least one of the following: start time, end time, execution exception, and result of interaction with financial services; the dialing test task executor analyzes the task execution result according to the task type and expected verification standard to determine the availability of the financial service; and the task execution result is fed back to the financial dialing test task scheduling center through a distributed message queue.

[0087] The financial dial test task executor in each dial test point environment will read the information of the financial dial test task to be executed from the local queue regularly or according to the event trigger mechanism of the local queue. This information includes the specific type of task (such as network request, port detection, file transfer test, etc.), related execution parameters (such as execution frequency, expected verification standard) and detailed information of the target financial service (such as service address, protocol type, etc.). Then, based on the read financial dial test task information, the executor will intelligently select the preset task processing thread Handler to execute the task. These Handlers are software modules specially designed to execute specific types of dial test actions, and each Handler corresponds to a task type. For example, when the type of task to be executed is "network request", the executor will select the http task Handler; when the task type is "port performance", the executor will select the port performance Handler. The Handler module will execute the predetermined dial test action according to the task type, such as initiating HTTP request, executing TCP / UDP port detection, and performing file transfer test. During the execution of the dial test task, the financial dial test task executor will record the execution results of the task in detail. These results include the task start time, end time, any exceptions encountered during execution, and specific results of the interaction with the financial service. For example, for a network request task, the execution results may include the response time of the request, the response status code, and the amount of data returned; for a port detection task, the results may include the port open status, response time, and round-trip time of the data packet.

[0088] The executor conducts in-depth analysis of the task execution results based on the task type and expected verification criteria to determine whether the financial service meets the predetermined availability and performance requirements. For example, for a page performance task, if the page loading time exceeds the threshold set by the expected verification criteria, the executor will determine that the service has low availability in the current environment. Through this analysis, the system can promptly detect problems and anomalies in financial services, providing a basis for subsequent troubleshooting and performance optimization.

[0089] Through the above steps, the financial dialing test task information can be read first, and each financial dialing test task can be allocated to a plurality of preset asynchronous scheduling queues through the financial dialing test task scheduling center according to the task type and the task execution frequency. Each asynchronous scheduling queue corresponds to a specified task execution rule, and the financial dialing test task to be executed is extracted from the asynchronous scheduling queue, and the financial dialing test task is sent to the financial dialing test task executor in each dialing test point environment. The financial dialing test task executor executes the financial dialing test task to obtain the task execution result, wherein the financial dialing test task information is the information corresponding to each financial dialing test task configured through the dialing test console, and the financial dialing test task information at least includes: a dialing test strategy and a dialing test point environment. The dialing test strategy at least includes: a task type and a task execution frequency. The financial dialing test task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution. In this embodiment, active dialing testing for financial services and configuration, scheduling, distribution and operation of large-scale dialing testing tasks are supported. Asynchronous scheduling and push of financial dialing testing tasks can be achieved through distributed message queues, and financial dialing testing tasks are distributed to financial dialing testing task executors in each dialing testing point environment. The financial dialing testing task executors execute the financial dialing testing tasks to obtain task execution results, thereby improving the accuracy and efficiency of network monitoring in financial scenarios, meeting the active dialing testing capabilities of enterprise-level financial services, and solving the technical problem of the lack of solutions for active dialing testing of network quality in financial scenarios in related technologies.

[0090] After the task is executed and analyzed, the financial dialing task executor feeds back the task execution results to the financial dialing task dispatch center through a distributed message queue (such as Kafka). After receiving these results, the dispatch center can conduct further summary analysis to form a global financial service performance report, or trigger the corresponding alarm mechanism to notify the operation and maintenance team to handle potential failures. In addition, the dispatch center can also store the execution results in an OLAP database, such as ClickHouse, to facilitate historical data query and long-term trend analysis.

[0091] It should be noted that after receiving the task execution results, the financial dialing task dispatching center in this embodiment connects the result data to the monitoring and analysis system (such as Grafana) for real-time monitoring and analysis. The monitoring scope includes the dialing service status, availability, performance, etc. The monitoring indicators are developed from three dimensions: availability, time consumption, and error conditions, helping users and operation and maintenance teams to fully understand the real-time status and historical trends of financial services and provide data support for decision-making.

[0092] In the embodiment of the present invention, by simulating real user behavior, the active dialing test technology of the present application can detect potential faults and performance problems before the customer actually uses it. This early warning mechanism enables the operation and maintenance team to intervene quickly, reduce the impact of faults on business and users, and improve the overall reliability of financial services.

[0093] At the same time, the embodiment of the present invention can support large-scale, multi-type dial-up tasks to run simultaneously by using distributed message queues for task scheduling. The decoupling design of task scheduling and execution ensures the independence and efficiency of task execution, and can ensure that each task can be responded to and executed in a timely manner even in high-concurrency scenarios, meeting the monitoring needs of enterprise-level financial services.

[0094] Another optional specific implementation is described in detail below.

[0095] Figure 3 is a flowchart of an optional active dialing task management method adapted to financial scenarios according to an embodiment of the present invention. Figure 3 As shown, the active dialing task management method includes:

[0096] Step 1: Start the start node and register the dial test task information.

[0097] The embodiment of the present invention provides an enterprise-level dial test management capability, supporting the management of multiple dial test tasks. At the beginning of dial test management, the user configures the dial test task online through a unified dial test console. The core of the dial test task information is the dial test strategy, dial test environment, and dial test service.

[0098] The dial test strategy is the specific execution rules of the dial test task, which mainly includes the following rules:

[0099] (1) Dial test type: including custom dial test and immediate dial test. Immediate dial test means that the dial test point will execute the task immediately after receiving the dial test task. Custom dial test requires configuration of execution frequency, and the task execution is triggered according to the frequency period.

[0100] (2) Task type: including network quality, page performance, port performance, file transfer, audio and video experience, etc.

[0101] (3) Execution frequency: the time period of execution.

[0102] (4) Task status: The status of the dial test task, including enable, stop, delete, etc.

[0103] (5) Expected verification: For different task types, set different dial test task execution expected verification results, such as port performance task type, expected verification port detection return value, etc.

[0104] (6) Alarm rules: Alarm notifications are issued according to expected verification conditions.

[0105] The online configuration function of the dial test console enables financial enterprises to flexibly adjust the dial test strategy according to business needs, including task type, execution frequency and alarm rules. At the same time, the design of the distributed task queue and dial test point environment provides good scalability for the system, which can easily increase dial test points and optimize scheduling strategies as the business expands and the network environment changes.

[0106] Step 2: Store the task persistently in the database.

[0107] Here, the dial test console persists the dial test task information records in the database system.

[0108] Step 3: Load the dial test task into each distributed message queue.

[0109] Step 4: Distribute the dialing test task to each dialing test point.

[0110] The dial test dispatch center reads the dial test tasks from the system, schedules the tasks according to the task strategy rules, and sends them to each dial test point in the dial test point environment ( Figure 3 It shows dialing point 1, dialing point 2...dialing point N).

[0111] Figure 4 is a schematic diagram of an optional dial test task scheduling device according to an embodiment of the present invention, which can support distributed scheduling of large-scale dial test tasks and send them to corresponding dial test point environments, such as Figure 4 As shown, the dispatch center is connected to the database and multiple dial-up test clients. The dispatch center includes multiple dispatch modules, each of which corresponds to multiple asynchronous dispatch queues.

[0112] When executing dial test task scheduling, it includes:

[0113] In the first step, the scheduling module loads the task information.

[0114] The second step is task distribution: according to the task policy rules, put the task into the corresponding asynchronous scheduling queue. For example, based on the distributed message queue KafKa, multiple topics can be created, each topic corresponds to a different task queue. According to the policy rules, multiple queues based on execution frequency + task type can be established, such as real-time_port detection queue, 5-minute fixed frequency_page performance detection queue, etc. The task execution module of each dial-up test client obtains the scheduling information from the queue and is responsible for task execution.

[0115] The third step is scheduling push: the scheduling request is pushed to the client executor through the "asynchronous scheduling queue", and an immediate response is received from the client executor to confirm whether the scheduling is successful.

[0116] Due to the use of asynchronous execution and distributed scheduling, this implementation can more reasonably allocate and utilize system resources. Through precise configuration of task types and execution frequencies, the system can avoid excessive consumption of resources while ensuring the dialing effect, achieving the dual goals of cost control and resource optimization.

[0117] Figure 5 is a schematic diagram of an optional dial test task execution device according to an embodiment of the present invention, which can support the simultaneous operation of large-scale dial test tasks, such as Figure 5 As shown, including:

[0118] 1. In the dial test task running client, preset the task running mode in it, and provide task handlers of various modes mainly based on http tasks (for example Figure 5 The schematic diagram shows the http-dial test task handler, tcp / udp-dial test task handler, and ping-dial test task handler). It also provides multi-frequency scheduled task templates to load the corresponding frequency dial test tasks respectively.

[0119] 2. The client, as a task executor, receives the scheduling request from the scheduling queue, obtains the corresponding task information and stores it in the execution queue, and then responds to the scheduling center immediately. The client extracts the dialing task from the execution queue, puts it into the task handler of the corresponding template, implements the task, and provides financial services for financial institutions.

[0120] Through the implementation of the present invention, a dialing test result monitoring and analysis capability is provided. By collecting client dialing test requests and result data, the detailed data can be connected and stored in an OLAP database (such as ClickHouse) through a distributed message queue (such as Kafka). Based on the detailed data, the analysis view is customized through tools such as Grafana for real-time monitoring. The monitoring scope includes dialing test service status, availability, performance analysis, etc., to help users understand the dialing test results. The monitoring indicators include three dimensions: availability, time consumption, and error conditions.

[0121] By continuously and actively monitoring financial services, this application can ensure the stability and response speed of the services, thereby directly improving the user experience. In financial services, such as online transactions and mobile payments, user experience is a key indicator for measuring service quality. The technical effect of this implementation can ensure the efficiency and stability of these services in various network environments, and enhance users' trust and satisfaction with financial services.

[0122] At the same time, the technical solution provided by this embodiment enhances the security of the system while protecting the privacy of users through encrypted transmission and secure storage of data during the execution of financial dialing tasks, as well as simulation of user behavior instead of using real data.

[0123] The following is a detailed description in conjunction with another embodiment.

[0124] Embodiment 2

[0125] The dialing task scheduling device in a financial scenario provided in this embodiment includes multiple implementation units, each of which corresponds to each implementation step in the above-mentioned embodiment 1.

[0126] Figure 6 FIG. 1 is a schematic diagram of an optional dialing task scheduling device in a financial scenario according to an embodiment of the present invention. Figure 6 As shown, the dialing task scheduling device in the financial scenario may include: a task information reading unit 61, a task allocating unit 62, and a task executing unit 63.

[0127] Among them, the task information reading unit 61 is used to read the financial dialing task information, wherein the financial dialing task information is the information corresponding to each financial dialing task configured by the dialing console, and the financial dialing task information at least includes: dialing strategy, dialing point environment, and the dialing strategy at least includes: task type and task execution frequency. The financial dialing task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution.

[0128] The task allocation unit 62 is used to allocate each financial dialing task to a plurality of preset asynchronous scheduling queues through the financial dialing task scheduling center according to the task type and the task execution frequency, wherein each asynchronous scheduling queue corresponds to a specified task execution rule.

[0129] The task execution unit 63 is used to extract the to-be-executed financial dialing test task from the asynchronous scheduling queue, and send the financial dialing test task to the financial dialing test task executor in each dialing test point environment, so that the financial dialing test task executor executes the financial dialing test task to obtain the task execution result.

[0130] The dialing test task scheduling device in the above financial scenario can first read the financial dialing test task information through the task information reading unit 61, and through the task allocation unit 62, according to the task type and the task execution frequency, through the financial dialing test task scheduling center, each financial dialing test task is allocated to a plurality of preset asynchronous scheduling queues, each asynchronous scheduling queue corresponds to a specified task execution rule, and the task execution unit 63 extracts the financial dialing test task to be executed from the asynchronous scheduling queue, and sends the financial dialing test task to the financial dialing test task executor in each dialing test point environment, and the financial dialing test task executor executes the financial dialing test task to obtain the task execution result, wherein the financial dialing test task information is the information corresponding to each financial dialing test task configured by the dialing test console, and the financial dialing test task information at least includes: dialing test strategy, dialing test point environment, and the dialing test strategy at least includes: task type and task execution frequency, and the financial dialing test task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution. In this embodiment, active dialing testing for financial services and configuration, scheduling, distribution and operation of large-scale dialing testing tasks are supported. Asynchronous scheduling and push of financial dialing testing tasks can be achieved through distributed message queues, and financial dialing testing tasks are distributed to financial dialing testing task executors in each dialing testing point environment. The financial dialing testing task executors execute the financial dialing testing tasks to obtain task execution results, thereby improving the accuracy and efficiency of network monitoring in financial scenarios, meeting the active dialing testing capabilities of enterprise-level financial services, and solving the technical problem of the lack of solutions for active dialing testing of network quality in financial scenarios in related technologies.

[0131] Optionally, the task allocation unit includes: a task type positioning module, which is used to locate the asynchronous scheduling queue corresponding to the task type of the financial dialing task, wherein each asynchronous scheduling queue is pre-configured with the corresponding task type; a task frequency and time determination module, which is used to determine the next execution time point of the financial dialing task according to the task execution frequency; a task sending module, which is used to send the financial dialing task and the corresponding dialing task information to the located asynchronous scheduling queue when the next execution time point is triggered; an asynchronous push module, which is used to asynchronously push the financial dialing task to multiple distributed dialing point environments through the asynchronous scheduling queue using an event-driven mechanism, such as Kafka.

[0132] Optionally, the dialing task scheduling device in the financial scenario also includes: a task queue creation unit, which is used to create multiple distributed task queues before locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task; a task queue configuration unit, which is used to configure the executable task execution frequency and task type for each distributed task queue to obtain multiple asynchronous scheduling queues.

[0133] Optionally, the task execution unit includes: a task extraction module, used to extract the task type, task execution parameters and expected verification standards of the financial dialing task to be executed from the asynchronous scheduling queue; a dialing point environment determination module, used to determine the dialing point environment to which the financial dialing task is to be assigned according to the task type, task execution parameters and expected verification standards of the financial dialing task; a message queue pushing module, used to asynchronously push the financial dialing task to the corresponding dialing point environment through a distributed message queue, wherein the financial dialing task executor in each dialing point environment receives the task information in the asynchronous scheduling queue, and stores the financial dialing task in the local task queue according to the task information.

[0134] Optionally, the task execution unit also includes: a task reading module, which is used by the financial dialing task executor to read the task information of the financial dialing task to be executed from the local task queue; a task processing thread selection module, which is used by the financial dialing task executor to select a preset task processing thread Handler to execute the task according to the task type in the financial dialing task information, and the task processing thread Handler executes a predetermined dialing action according to the task type; an execution result recording module, which is used by the financial dialing task executor to record the task execution result during the task execution process, and the task execution result includes but is not limited to the start time, end time, execution exception and the result of interaction with the financial service; an execution result analysis module, which is used by the financial dialing task executor to analyze the task execution result according to the task type and the expected verification standard to determine the availability of the financial service; a result feedback module, which is used to feed back the task execution result to the financial dialing task scheduling center through a distributed message queue.

[0135] Optionally, the dialing test task scheduling device in the financial scenario also includes: a dialing test strategy generation unit, which is used to receive the dialing test type, task type, task execution frequency, task status, expected verification standard, and alarm rule of each financial dialing test task configured online by the user end through the dialing test console, and generate a dialing test strategy; a dialing test point environment generation unit, which is used to receive the communication protocol, network area, operator and firewall of each financial dialing test task through the dialing test console, and generate a dialing test point environment; a task information determination unit, which is used to determine the financial dialing test task information based on the dialing test strategy and dialing test point environment of each financial dialing test task; and a task information storage unit, which is used to record and persist the financial dialing test task information in a database.

[0136] Optionally, the dial test types in the dial test strategy generation unit include: custom dial test and instant dial test, wherein custom dial test refers to triggering task execution according to the configured frequency period; task types include but are not limited to: network quality, page performance, port performance, file transfer, audio and video experience; task status includes: dial test task enable, dial test task stop, dial test task deletion; expected verification standard refers to setting different expected verification results for financial dial test task execution for different task types; alarm rules refer to alarm notification according to expected verification results.

[0137] The dialing task scheduling device in the above financial scenario may also include a processor and a memory. The above task information reading unit 61, task allocation unit 62, task execution unit 63, etc. are all stored in the memory as program units, and the processor executes the above program units stored in the memory to implement corresponding functions.

[0138] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the active dialing task of financial services in financial scenarios can be adapted by adjusting kernel parameters.

[0139] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (fl ash RAM), and the memory includes at least one storage chip.

[0140] Embodiment 3

[0141] An embodiment of the present application may provide an electronic device, Figure 7 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 7 As shown, the electronic device may include: one or more ( Figure 7 (only one is shown) processor 702, memory 704, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0142] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0143] The processor can call the information and application program stored in the memory through the transmission device to perform the following steps: read the financial dialing test task information, wherein the financial dialing test task information is the information corresponding to each financial dialing test task configured through the dialing test console, the financial dialing test task information at least includes: a dialing test strategy and a dialing test point environment, the dialing test strategy at least includes: a task type and a task execution frequency, and the financial dialing test task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution; according to the task type and the task execution frequency, each financial dialing test task is allocated to a plurality of preset asynchronous scheduling queues through a financial dialing test task scheduling center, wherein each asynchronous scheduling queue corresponds to a specified task execution rule; extract the financial dialing test task to be executed from the asynchronous scheduling queue, and send the financial dialing test task to the financial dialing test task executor in each dialing test point environment, and the financial dialing test task executor executes the financial dialing test task to obtain a task execution result.

[0144] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: locate the asynchronous scheduling queue corresponding to the task type of the financial dialing task, wherein each asynchronous scheduling queue corresponds to a task type; determine the next execution time point of the financial dialing task according to the task execution frequency, and when the next execution time point is triggered, send the financial dialing task and the corresponding dialing task information to the located asynchronous scheduling queue; and asynchronously push the financial dialing task to multiple distributed dialing point environments using an event-driven mechanism through the asynchronous scheduling queue.

[0145] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: before locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task, create multiple distributed task queues; configure the executable task execution frequency and task type for each distributed task queue to obtain multiple asynchronous scheduling queues.

[0146] The processor can call the information and application program stored in the memory through the transmission device to perform the following steps: extract the task type, task execution parameters and expected verification standard of the financial dial test task to be executed from the asynchronous scheduling queue, wherein the task execution parameters at least include: task execution frequency; determine the dial test point environment to which the financial dial test task is to be assigned according to the task type, task execution parameters and expected verification standard of the financial dial test task; asynchronously push the financial dial test task to the corresponding dial test point environment through the distributed message queue, wherein the financial dial test task executor in each dial test point environment receives the task information in the asynchronous scheduling queue, and stores the financial dial test task in the local task queue according to the task information.

[0147] The processor can call the information and application program stored in the memory through the transmission device to perform the following steps: the dialing test task executor reads the task information of the to-be-executed financial dialing test task from the local task queue; the dialing test task executor selects a preset task processing thread Handler to execute the task according to the task type in the financial dialing test task information, and the task processing thread Handler executes a predetermined dialing test action according to the task type, and the dialing test action includes at least one of the following network request, port detection, and file transfer test; during the task execution process, the dialing test task executor records the task execution result, wherein the task execution result includes at least one of the following: start time, end time, execution exception, and result of interaction with the financial service; the dialing test task executor analyzes the task execution result according to the task type and the expected verification standard to determine the availability of the financial service; and the task execution result is fed back to the financial dialing test task scheduling center through the distributed message queue.

[0148] The processor can call the information and application program stored in the memory through the transmission device to perform the following steps: before reading the financial dialing test task information, receive the dialing test type, task type, task execution frequency, task status, expected verification standard, and alarm rule of each financial dialing test task configured online by the user end through the dialing test console to generate a dialing test strategy; receive the communication protocol, network area, operator and firewall of each financial dialing test task through the dialing test console to generate a dialing test point environment; determine the financial dialing test task information based on the dialing test strategy and dialing test point environment of each financial dialing test task; and record and persist the financial dialing test task information in a database.

[0149] It can be understood by those skilled in the art that Figure 7 The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone, a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, etc. Figure 7 The structure of the electronic device is not limited. Figure 7 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 7 Different configurations are shown.

[0150] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0151] Embodiment 4

[0152] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the dialing task scheduling method in the financial scenario provided in the first embodiment.

[0153] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the dialing task scheduling method in a financial scenario of any one of the above-mentioned embodiments one.

[0154] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0155] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the dialing task scheduling method in the financial scenario described in each embodiment of the present application.

[0156] The present application also provides a computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the dialing task scheduling method in the financial scenario described in each embodiment of the present application are implemented.

[0157] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0158] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0159] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0160] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0161] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0162] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, 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, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0163] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A dialing task scheduling method in a financial scenario, characterized in that: include: Reading financial dialing test task information, wherein the financial dialing test task information is information corresponding to each financial dialing test task configured through the dialing test console, the financial dialing test task information at least includes: a dialing test strategy and a dialing test point environment, the dialing test strategy at least includes: a task type and a task execution frequency, and the financial dialing test task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution; According to the task type and the task execution frequency, each of the financial dialing tasks is assigned to a plurality of preset asynchronous scheduling queues through a financial dialing task scheduling center, wherein each of the asynchronous scheduling queues corresponds to a specified task execution rule; The financial dial test task to be executed is extracted from the asynchronous scheduling queue, and the financial dial test task is sent to the financial dial test task executor in each dial test point environment, and the financial dial test task executor executes the financial dial test task to obtain a task execution result.

2. The dialing task scheduling method according to claim 1, characterized in that: The step of allocating each of the financial dialing tasks to a plurality of preset asynchronous scheduling queues through a financial dialing task scheduling center according to the task type and the task execution frequency includes: Locating an asynchronous scheduling queue corresponding to a task type of the financial dialing task, wherein each of the asynchronous scheduling queues corresponds to a task type; Determine the next execution time point of the financial dialing task according to the task execution frequency, and send the financial dialing task and the corresponding dialing task information to the located asynchronous scheduling queue when the next execution time point is triggered; The financial dialing task is asynchronously pushed to multiple distributed dialing point environments through the asynchronous scheduling queue and using an event-driven mechanism.

3. The dialing task scheduling method according to claim 2, characterized in that: Before locating the asynchronous scheduling queue corresponding to the task type of the financial dialing task, the method further includes: Create multiple distributed task queues; The frequency and type of tasks that can be executed are configured for each of the distributed task queues to obtain a plurality of the asynchronous scheduling queues.

4. The dialing task scheduling method according to claim 1, characterized in that: The step of sending the financial dialing test task to the financial dialing test task executor in each dialing test point environment includes: Extracting the task type, task execution parameters and expected verification standard of the financial dialing task to be executed from the asynchronous scheduling queue, wherein the task execution parameters at least include: task execution frequency; Determining the dialing point environment to which the financial dialing task is to be assigned according to the task type, the task execution parameters and the expected verification standard of the financial dialing task; The financial dialing task is asynchronously pushed to the corresponding dialing point environment through a distributed message queue, wherein the financial dialing task executor in each dialing point environment receives the task information in the asynchronous scheduling queue, and stores the financial dialing task in a local task queue according to the task information.

5. The dialing task scheduling method according to claim 1, characterized in that: The step of executing the financial dialing task by the financial dialing task executor to obtain a task execution result includes: The dialing task executor reads the task information of the financial dialing task to be executed from the local task queue; The dial test task executor selects a preset task processing thread Handler to perform the task according to the task type in the financial dial test task information, and the task processing thread Handler performs a predetermined dial test action according to the task type, and the dial test action includes at least one of the following network request, port detection, and file transfer test; During the task execution process, the task execution result is recorded by the dialing task executor, wherein the task execution result includes at least one of the following: start time, end time, execution exception, and result of interaction with financial services; The dialing task executor analyzes the task execution result according to the task type and the expected verification standard to determine the availability of the financial service; The task execution result is fed back to the financial dialing task scheduling center through a distributed message queue.

6. The dialing task scheduling method according to claim 1, characterized in that: Before reading the financial dialing task information, it also includes: Receive the dial test type, task type, task execution frequency, task status, expected verification standard, and alarm rule of each financial dial test task configured online by the user terminal through the dial test console, and generate the dial test strategy; Receiving the communication protocol, network area, operator and firewall of each financial dial test task through the dial test console, and generating the dial test point environment; Determining the financial dial testing task information based on the dial testing strategy and the dial testing point environment of each of the financial dial testing tasks; The financial call task information is recorded and persisted in a database.

7. The dialing task scheduling method according to claim 6, characterized in that: The dial test types include: custom dial test and instant dial test. The custom dial test refers to triggering task execution according to the configured frequency period; the task type includes at least one of the following: network quality, page performance, port performance, file transfer, audio and video experience; the task status is one of the following: dial test task enabled, dial test task stopped, dial test task deleted; the expected verification standard refers to setting different expected verification results for financial dial test task execution for different task types; the alarm rule refers to issuing an alarm notification according to the result of the expected task verification.

8. A dialing task scheduling device in a financial scenario, characterized in that: include: A task information reading unit is used to read financial dialing task information, wherein the financial dialing task information is information corresponding to each financial dialing task configured by the dialing console, and the financial dialing task information at least includes: a dialing strategy and a dialing point environment, and the dialing strategy at least includes: a task type and a task execution frequency, and the financial dialing task refers to a task corresponding to a simulated financial service proposed by a consumer to a financial institution; A task allocation unit, configured to allocate each of the financial dialing tasks to a plurality of preset asynchronous scheduling queues through a financial dialing task scheduling center according to the task type and the task execution frequency, wherein each of the asynchronous scheduling queues corresponds to a specified task execution rule; The task execution unit is used to extract the financial dialing test task to be executed from the asynchronous scheduling queue, and send the financial dialing test task to the financial dialing test task executor in each dialing test point environment, so that the financial dialing test task executor executes the financial dialing test task to obtain the task execution result.

9. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the dialing task scheduling method in a financial scenario as described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the dialing task scheduling method in a financial scenario described in any one of claims 1 to 7 are implemented.

Images