Methods, devices, equipment, media and products for optimizing process nodes in financial services

Abstract

The embodiments of the present application provide a method, device, equipment, medium and product for optimizing process nodes of financial services, which relate to the field of financial technology or artificial intelligence. By obtaining the actual operation time and the actual number of repeated operations at each process node when multiple users operate financial services, the process nodes that need to be optimized in the financial services are determined. For the process nodes that need to be optimized, prompt information is output to indicate the reasons or suggestions for optimization. This method determines the nodes that need to be optimized by operation time and number of operations, effectively solving the problem of unreasonable design of some business process nodes caused by the expansion of business types and diversification of customer needs, significantly reducing the error rate of customers during the operation process, improving the efficiency and quality of business processing, and at the same time reducing the operational burden of customers, thereby achieving continuous optimization of business processes and a substantial improvement in customer experience.

Description

Technical Field

[0001] The present application relates to the field of financial technology or artificial intelligence, and in particular to a method, device, equipment, medium and product for optimizing process nodes of financial services. Background Art

[0002] With the continuous expansion of banking services and the increasing diversification of customer needs, banks need to provide more flexible, efficient business processes that can meet customers' personalized needs. These business processes must be highly adaptable and able to quickly respond to market changes, ensuring that customers receive convenient and accurate services at all times.

[0003] Existing banking processes are standardized and regulated through the clear division of nodes. Each node has clear responsibilities and operational requirements, ensuring the accurate execution of banking operations. Furthermore, through the collaboration between these nodes, users can obtain the services they need in the shortest possible time, improving customer satisfaction and the bank's operational efficiency.

[0004] However, with the continuous expansion of business types and the diversification of customer needs, the node design in some business processes has gradually become unreasonable, resulting in customers making frequent errors during operations. Summary of the Invention

[0005] The present application provides a method, device, equipment, medium and product for optimizing process nodes of financial services, which are used to solve the technical problem of unreasonable design of some business process nodes caused by the increase in the types of banking services and the diversification of customer needs.

[0006] In a first aspect, the present application provides a method for optimizing process nodes of a financial service, comprising:

[0007] Obtain the actual operation time and actual number of repeated operations at each process node of multiple users during their financial business operations within a preset time period;

[0008] For any process node, if the average actual operation time of the multiple users at the process node is greater than the preset ideal operation time of the process node, and / or if the average actual number of repeated operations of the multiple users at the process node is greater than the preset ideal number of repeated operations of the process node, then the process node is determined to be a process node to be optimized;

[0009] For the process node to be optimized, prompt information is output, where the prompt information is used to indicate the reason and / or suggestion for optimization.

[0010] In a second aspect, the present application provides a process node optimization device for financial services, comprising:

[0011] An acquisition module is used to obtain the actual operation time and actual number of repeated operations at each process node of multiple users in the process of operating financial services within a preset time period;

[0012] a determination module configured to, for any process node, determine the process node as a process node to be optimized if an average of actual operation times of the multiple users at the process node is greater than a preset ideal operation time of the process node, and / or if an average of actual repeated operation times of the multiple users at the process node is greater than a preset ideal repeated operation times of the process node;

[0013] The output module is used to output prompt information for the process node to be optimized, and the prompt information is used to indicate the reason and / or suggestion for optimization.

[0014] In a third aspect, an embodiment of the present application provides a process node optimization device for financial services, including: a memory, a processor;

[0015] The memory stores computer-executable instructions;

[0016] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0017] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementation methods of the first aspect.

[0018] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0019] The process node optimization method, device, equipment, medium and product for financial services provided in this application determine the process nodes that need to be optimized in the financial services by obtaining the actual operation time and the actual number of repeated operations at each process node when multiple users operate financial services. For the process nodes that need to be optimized, a prompt message is output to indicate the reasons or suggestions for optimization. This method determines the nodes that need to be optimized by operation time and number of operations, effectively solving the problem of unreasonable design of some business process nodes caused by the expansion of business types and diversification of customer needs, significantly reducing the error rate of customers during the operation process, improving the efficiency and quality of business processing, and at the same time reducing the operational burden of customers, thereby achieving continuous optimization of business processes and a significant improvement in customer experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0021] Figure 1 Schematic diagram of the process node optimization method for financial business provided in this application Figure 1 ;

[0022] Figure 2 Schematic diagram of the process node optimization method for financial business provided in this application Figure 2 ;

[0023] Figure 3 A schematic diagram of the structure of the process node optimization device for financial services provided in this application;

[0024] Figure 4 A schematic diagram of the structure of the process node optimization equipment for financial services provided in this application.

[0025] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0026] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0027] It should be noted that the process node optimization methods, devices, equipment, media and products for financial services provided in this application can be used in the field of financial technology or artificial intelligence, and can also be used in any field other than the field of financial technology or artificial intelligence. This application does not limit the application fields of the process node optimization methods, devices, equipment, media and products for financial services.

[0028] The continuous expansion of banking services and the increasing diversity of customer needs require banks to provide more flexible, efficient, and responsive business processes that precisely meet the individual needs of each customer. These processes must be highly adaptable and able to keep pace with market trends, ensuring that customers enjoy a convenient and precise service experience at all times.

[0029] Currently, banking processes are standardized and regulated through a meticulous division of nodes. Each node is assigned clear responsibilities and operational guidelines, ensuring the accurate and flawless execution of banking operations. Furthermore, these nodes work closely together to form an efficient service chain, enabling customers to quickly access the services they need, thereby improving customer satisfaction and the bank's operational efficiency.

[0030] However, with the continuous expansion of business types and the diversification of customer needs, the node design in some business processes has gradually become unreasonable, resulting in customers making frequent errors during operations.

[0031] In response to the above problems, the process node optimization method for financial services provided in this application determines the process nodes that need to be optimized in financial services by obtaining the actual operation time and the actual number of repeated operations at each process node when multiple users operate financial services. For the process nodes that need to be optimized, a prompt message is output, indicating the reasons or suggestions for optimization. This method determines the nodes that need to be optimized by operation time and number of operations, effectively solving the problem of unreasonable design of some business process nodes caused by the expansion of business types and diversification of customer needs, significantly reducing the error rate of customers during the operation process, improving the efficiency and quality of business processing, and at the same time reducing the operational burden of customers, thereby achieving continuous optimization of business processes and a significant improvement in customer experience.

[0032] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0033] Figure 1 Schematic diagram of the process node optimization method for financial business provided in this application Figure 1 .like Figure 1 As shown, the method includes:

[0034] S101: Acquire actual operation time and actual number of repeated operations at each process node of multiple users during the process of operating financial services within a preset time period.

[0035] The preset time period can be, for example, the past two days, the past week, or the past month, and this application does not impose any special restrictions on this. For example, assuming the preset time period is the past week. If the current time is December 1, 2024, the system will obtain data from November 25, 2024 to December 1, 2024.

[0036] Different types of financial services correspond to different process nodes. For example, if the financial service is a time deposit process, it includes: {Process Node 1: Select deposit type and term, Process Node 2: Prepare funds and identity proof, Process Node 3: Fill out the deposit slip or complete the online process, Process Node 4: Verify identity information, Process Node 5: Confirm funds received, Process Node 6: Issue deposit certificate (such as certificate of deposit), Process Node 7: Maturity reminder and description of renewal / withdrawal options}; If the financial service is an account opening process, it includes: {Process Node 1: Customer consultation and appointment, Process Node 2: Document preparation and review, Process Node 3: Fill out the account opening application form, Process Node 4: Identity verification (such as ID card, facial recognition), Process Node 5: Sign the account opening agreement, Process Node 6: Account setup and activation, Process Node 7: Issuance of bank card / passbook, Process Node 8: Account security reminder and education}.

[0037] By obtaining the actual operation time and the actual number of repeated operations at each process node when multiple users operate financial business within a preset time period, it means that the time spent and the number of operations performed by each user at each process node when completing their respective financial business within the preset time period can be obtained.

[0038] Understandably, different users perform different financial services. For example, when user A is processing a time deposit, each process node in the process takes 10 seconds and the number of repetitions is 1. When user B is opening a bank account, each process node takes 55 seconds and the number of repetitions is 0. When user C is transferring money through mobile banking, each process node takes 1 minute and the number of repetitions is 3.

[0039] The method of obtaining the information in this step may be, for example, obtaining the information from the log records in the bank's self-service machine, or from the log records in other business processing platforms of the bank. This application does not impose any special restrictions on this.

[0040] S102. For any process node, if the average actual operation time of multiple users on the process node is greater than the preset ideal operation time of the process node, and / or if the average actual number of repeated operations of multiple users on the process node is greater than the preset ideal number of repeated operations of the process node, the process node is determined to be a process node to be optimized.

[0041] The ideal operation time refers to the minimum expected time to complete a process node in a financial transaction without any exceptions, delays, or unnecessary waiting. For example, the ideal operation time could be 15 seconds.

[0042] The ideal number of repetitions refers to the minimum number of operations expected to be completed under normal circumstances for a process node in a financial business. The ideal number of repetitions can be, for example, 0. This application does not impose any special restrictions on the ideal operation time and the ideal number of repetitions.

[0043] The purpose of this step is to determine which nodes in the financial business need to be optimized.

[0044] Understandably, multiple users may handle the same financial transaction within a preset time period. However, even for the same financial transaction, different users may experience differences in actual operation time and the number of repetitions. Therefore, to more accurately analyze which process nodes within a financial transaction require optimization, it is necessary to calculate the average actual operation time and number of repetitions for each process node in the same financial transaction for multiple users, and compare this with the preset ideal operation time and ideal number of repetitions.

[0045] For example, consider a mobile banking transfer process, which includes multiple nodes, including login verification, payee selection, transfer amount input, and transfer information confirmation. It is known that the ideal operation times for the "Login Verification" node, the "Payee Selection" node, the "Transfer Amount Input" node, and the "Confirm Transfer Information" node are 20 seconds, 30 seconds, 32 seconds, and 25 seconds, respectively, and the ideal number of repetitions is 0, 0, 0, and 0, respectively.

[0046] Based on the above information, the system will first obtain the actual operation time and actual number of repeated operations of multiple users at each process node during the process of operating financial services within a preset time period; then, for the mobile banking transfer process, the system determines that user A, user B and user C have respectively operated the mobile banking transfer process; then, based on the actual operation time and actual number of repeated operations of user A, user B and user C at each process node, the system determines that the average actual operation time of the "login verification", "select payee", "enter transfer amount" and "confirm transfer information" nodes is 19.67S, 42.33 seconds, 37.33 seconds and 50 seconds, and the average actual number of repeated operations is 1 time, 2 times, 2 times and 2 times; then, the system will compare the average actual operation time of the "login verification" node, "select payee" node, "enter transfer amount" node and "confirm transfer information" node with the ideal operation time, and determine that "select payee", "enter transfer amount" and "confirm transfer information" are the process nodes to be optimized; at the same time, the system will also compare the average actual number of repeated operations of the "login verification", "select payee", "enter transfer amount" and "confirm transfer information" nodes with the ideal number of repeated operations, and determine that the "login verification", "select payee", "enter transfer amount" and "confirm transfer information" nodes are the nodes to be optimized.

[0047] Optionally, the present application provides a method for determining an ideal operation time and an ideal number of repeated operations, including:

[0048] The first step is to determine the actual testing time and actual number of repeated tests of multiple testers at each process node to be tested for any financial business based on the various process nodes to be tested included in the financial business.

[0049] Understandably, during the financial services testing process, it's necessary to first break down the business and identify the various process nodes within it. Each process node is then identified as the one to be tested. Multiple testers are then assigned to test each node, and the actual test time and number of test repetitions per tester are recorded.

[0050] For example, let's assume the financial service is the "Account Opening Process," and the node to be tested is the "Document Preparation and Review" node. Multiple testers are then assigned to test each process node. Each tester performs multiple tests, recording the actual test duration and number of retests for each test. For example, tester A performed four tests on the "Document Preparation and Review" node, with actual test durations of 5 seconds, 5 seconds, 6 seconds, and 5 seconds, respectively, and the actual number of retests for each test was 1. Similarly, testers B, C, D, and E each performed four tests on the node, recording their respective test durations and number of retests.

[0051] The second step is to determine the average actual test time and standard deviation of the actual test time of multiple testers at any process node.

[0052] Among them, the average actual test time is used to represent the average test efficiency of multiple testers on the same process node.

[0053] The standard deviation of actual test time is used to characterize the degree of dispersion between the test times of multiple testers at the same process node.

[0054] In the third step, the average actual test time is determined as the ideal operation time of the process node, or the difference between the average actual test time and the standard deviation of the actual test time is determined as the ideal operation time of the process node.

[0055] The purpose of this step is to provide a clear and measurable optimization time standard for the process node.

[0056] For example, suppose the average actual test duration for the "Document Preparation and Review" node is 10, and the standard deviation is 6. Based on this information, the system can set the optimal time standard for the "Document Preparation and Review" node in two ways: 10 is directly set as the ideal operation duration, and 4 is set as the difference between the average actual test duration and the standard deviation.

[0057] The fourth step is to directly set the ideal number of repeated operations of the process node to 0.

[0058] Among them, 0 indicates that a process node is not executed repeatedly.

[0059] It can be understood that by setting the number of repeated operations of a process node to 0 and using this as a goal or expectation, it means that the system expects that the node will not be repeatedly operated by the user in future process executions.

[0060] S103: Output prompt information for the process node to be optimized, where the prompt information is used to indicate the reason and / or suggestion for the optimization.

[0061] The purpose of this step is to provide clear feedback to relevant personnel (such as developers, operations personnel, or process managers) about the process nodes to be optimized, so that they can understand why these nodes need to be optimized and may obtain specific suggestions on how to optimize them.

[0062] The method for outputting the prompt information in this step may be, for example, to display the prompt information in a visual manner on the management tool of the relevant personnel. The visual method includes, but is not limited to, system logs and pop-up prompts. The application does not impose any special restrictions on this.

[0063] For example, suppose the nodes to be optimized in a mobile banking transfer process are "Login Verification" and "Select Payee." The system would then output the following prompt for "Login Verification": "Reason: Verification steps are cumbersome or system response is slow. Suggestion: We recommend optimizing the verification process, such as introducing biometric technology to reduce password entry times or improving system performance."

[0064] At the same time, for the "Select Payee" node, the corresponding prompt message is output: "Reason: The payee list is too long or the search function is not convenient. Suggestion: Optimize the interface design, provide a clearer payee selection path, or introduce smart matching functions to reduce user manual input and selection time."

[0065] The process node optimization method for financial services provided in the embodiment of the present application analyzes the business process through the actual operation time and the actual number of repeated operations at each process node when multiple users operate financial services within a preset time period. For any process node, if it is determined that the average value of the actual operation time of the user at the node is greater than the preset ideal operation time, or the average value of the actual number of repeated operations is greater than the preset ideal number of repeated operations, it is determined that the process node needs to be optimized. For the process nodes that need to be optimized, a prompt message is output to indicate the reasons or suggestions for optimization. This method effectively solves the problem of unreasonable design of some business process nodes caused by the expansion of business types and the diversification of customer needs, significantly reduces the error rate and confusion of customers during the operation process, and improves the efficiency and quality of business processing.

[0066] Figure 2 Schematic diagram of the process node optimization method for financial business provided in this application Figure 2 ,like Figure 2 As shown, this embodiment Figure 1 Based on the embodiment, a method for optimizing process nodes of financial services is described in detail. The method includes:

[0067] S201: Acquire actual operation time and actual number of repeated operations at each process node of multiple users during the process of operating financial services within a preset time period.

[0068] The explanation of step S201 refers to the explanation of the above embodiment and will not be repeated here.

[0069] S202. For any process node, if the average actual operation time of multiple users on the process node is greater than the preset ideal operation time of the process node, and / or if the average actual number of repeated operations of multiple users on the process node is greater than the preset ideal number of repeated operations of the process node, the process node is determined to be a process node to be optimized.

[0070] The explanation of step S202 refers to the explanation of the above embodiment and will not be repeated here.

[0071] S203. If the average actual operation time of multiple users on the process node is greater than the preset ideal operation time of the process node, a first prompt message is output for the process node to be optimized. The first prompt message is used to indicate that the reason for the optimization is a system abnormality or a cumbersome process.

[0072] The purpose of judging whether the average actual operation time of multiple users at a process node is greater than the preset ideal operation time of the process node is to determine whether the average actual operation time of the process node exceeds the ideal range.

[0073] If the average actual operation time of multiple users on a process node is greater than the preset ideal operation time of the process node, it indicates that the average actual operation time of the process node exceeds the ideal range. At this time, it is necessary to output the first prompt information for the process node to be optimized.

[0074] It is understandable that by outputting the first prompt information, relevant personnel can be reminded in time that the time consumed by a certain process node in actual operation exceeds the preset ideal standard, thereby prompting relevant personnel to quickly locate the cause of the problem. Whether it is a system abnormality or a cumbersome process design, it can receive timely attention and resolution.

[0075] For example, suppose the system presets an ideal operation time of 5 seconds for the "Confirm Transfer Information" node in the mobile banking transfer process. However, an analysis of the data from the past week reveals that the actual operation time for this node has reached an average of 10 seconds. At this point, the system will output the first prompt message: "Attention: The "Confirm Transfer Information" node is pending optimization. The reason for the optimization may be slow system response or overly complicated process design, resulting in excessive user operation time."

[0076] S204. If the average actual number of repeated operations of multiple users on a process node is greater than the preset ideal number of repeated operations of the process node, a second prompt message is output for the process node to be optimized. The second prompt message is used to prompt that the reason for the optimization is unreasonable interface design or cumbersome process.

[0077] The purpose of judging whether the average actual number of repeated operations of multiple users at a process node is greater than the preset ideal number of repeated operations of the process node is to determine whether the user has repeated operation behavior at the process node.

[0078] If the average actual number of repeated operations of multiple users on a process node is greater than the preset ideal number of repeated operations for the process node, it indicates that the user has repeated operations in the process node. At this time, a second prompt message needs to be output for the process node to be optimized.

[0079] It is understandable that by outputting the second prompt information, the problem of too many repetitive operations in the process nodes can be pointed out to relevant personnel in a timely manner, and the relevant personnel can be reminded that the reason for optimization may be that the interface design is not intuitive and easy to use or the process arrangement is too complicated, thereby prompting relevant personnel to pay attention to and improve these aspects, reduce users' repetitive operations, and improve user experience and process efficiency.

[0080] For example, suppose that in the "Select Payee" node of the mobile banking transfer process, the system presets an ideal operation time of 0.5 times. However, through analysis of the data of the past week, it is found that the actual operation time of this node has reached an average of 3 times. At this time, the system will output the following prompt message: "Note: The "Select Payee" node needs to be optimized. The reason for the optimization may be that the payee list is too long or the search function is not convenient, causing users to perform multiple operations. The optimization suggestion is to optimize the search and filtering functions to improve selection efficiency."

[0081] S205. Determine the number of different types of abnormal situations that occur in each process node within the first time period, where the different types of abnormal situations include: the actual operation time is greater than the ideal operation time, and the difference between the actual operation time and the ideal operation time is greater than a first threshold; the actual number of repeated operations is greater than the ideal number of repeated operations, and the difference between the actual number of repeated operations and the ideal number of repeated operations is greater than a second threshold; user operation error; system operation.

[0082] The first time period may be the same as the preset time period, for example, assuming that the preset time period is the past day, then the first time period may also be the past day.

[0083] The first threshold value indicates that the actual operation time of the process node is extremely time-consuming. The first threshold value may be 30 seconds, for example.

[0084] The second threshold value indicates that the actual number of repeated operations of the process node is a high number of repeated operations. The second threshold value may be 5 times, for example.

[0085] User operation errors include but are not limited to: incorrect address information entered by the user at a relevant process node, or incorrect postal code information entered.

[0086] System operations are used to indicate errors that occur in the system itself, such as errors in the system server.

[0087] The purpose of this step is to more comprehensively and accurately count the number of different types of abnormal situations that occur in each process node during the first time period. These abnormal situations cover various types, such as actual operations taking too long, too many repeated operations, user operation errors, and system operation abnormalities.

[0088] For example, assuming the first time period is the past day, and the "Mobile Banking Transfer Process" includes: "Login Verification," "Payee Selection," "Transfer Amount Input," and "Transfer Information Confirmation," the system can count the number of different types of exceptions that occurred in the "Login Verification" node, the "Payee Selection" node, the "Transfer Amount Input" node, and the "Transfer Information Confirmation" node within the past day.

[0089] S206 : Determine the process nodes to be observed among the process nodes based on the number of times different types of abnormal situations occur in each process node.

[0090] The purpose of this step is to determine a more representative process node where an abnormal error occurs from multiple process nodes, and determine the process node as a node to be observed.

[0091] For example, suppose the "Login Verification" node, the "Payee Selection" node, the "Transfer Amount Input" node, and the "Transfer Information Confirmation" node experienced different types of anomalies 10, 13, 18, and 7 times, respectively, over the past day. Based on this information, the system can identify the "Transfer Amount Input" node as the process node to be observed.

[0092] Optionally, this application provides a possible implementation method, which specifically includes:

[0093] The first step is to determine the abnormality rate of each process node based on the number of times different types of abnormal situations occur at each process node.

[0094] Among them, the exception rate refers to the ratio of the number of different types of exceptions that occur in a certain process node within the first time period to the total number of operations of the node.

[0095] The purpose of this step is to determine the proportion of abnormal situations that occur in each process node during the first time period.

[0096] Understandably, in financial services, different process nodes perform distinct tasks and functions. For example, in a mobile banking transfer process, the "Login Verification" node verifies the user's identity, while the "Select Payee" node allows users to select a transfer recipient from their contact list. These nodes have distinct content and execution logic. Consequently, the types and frequency of anomalies encountered during actual operation may vary. Therefore, to accurately assess the proportion of anomalies occurring at these process nodes during actual operation, it is necessary to determine the anomaly rate for each process node based on the number of different types of anomalies that have occurred at each node over a period of time.

[0097] For example, suppose the "Login Verification" node, the "Payee Selection" node, the "Transfer Amount Input" node, and the "Confirm Transfer Information" node experienced different types of abnormalities 10 times, 13 times, 18 times, and 7 times, respectively, in the past day, and the total number of operations in the past day was 30 times, 33 times, 20 times, and 14 times, respectively. Based on this information, the system can determine that the abnormality rates of the "Login Verification" node, the "Payee Selection" node, the "Transfer Amount Input" node, and the "Confirm Transfer Information" node are 33.3%, 39.4%, 90%, and 50%, respectively.

[0098] In the second step, the process nodes with the highest abnormality rate and the process nodes with the most abnormal situations are identified as the process nodes to be observed.

[0099] Among them, by determining the process nodes with the highest abnormality rate and the process nodes with the most abnormal situations as the process nodes to be observed, it means that the system has identified the process nodes in the financial business that need the most attention and improvement.

[0100] In this step, for example, the abnormality rates of each process node can be sorted in descending order to obtain the abnormality rate sorting results of each process node, and the number of abnormal situations occurring in each process node can be sorted in descending order to obtain the number sorting results of each process node; then, according to the abnormality rate sorting results of each process node, the process node with the highest abnormality rate is obtained, and according to the number sorting results of each process node, the process node with the most abnormal situations is obtained; finally, the process node with the highest abnormality rate and the process node with the most abnormal situations are all determined as the process nodes to be observed.

[0101] For example, suppose the "Login Verification" node, the "Payee Selection" node, the "Transfer Amount Input" node, and the "Transfer Information Confirmation" node experienced different types of anomalies 10 times, 13 times, 18 times, and 7 times, respectively, over the past day, and their anomaly rates were 33.3%, 39.4%, 90%, and 50%, respectively. Based on this information, the system can first determine that the process node with the highest anomaly rate is Payee Selection, and that the process node with the most anomalies is Payee Selection. Subsequently, the system will identify Payee Selection as the process node to be observed.

[0102] S207. Based on the number of times various types of abnormal situations occur in the process node to be observed within the first time period, and the number of times various types of abnormal situations occur in the second time period after the first time period, determine the process node to be optimized in the process node to be observed, and output a third prompt information, which is used to prompt that the reason for optimization is unreasonable interface design or cumbersome process.

[0103] The second time period refers to a continuous time period after the first time period. The length of the second time period may be equal to the length of the first time period.

[0104] The purpose of this step is to determine which process nodes need optimization by analyzing the number of times various types of abnormal situations occur in the observed process nodes in two different time periods, and output prompt information to indicate possible reasons for optimization.

[0105] In this step, for example, after determining the number of different types of abnormal situations that occur in the process node to be observed within the first time period, the number of different types of abnormal situations that occur in the process node to be observed within the second time period can be determined first, wherein the second time period is located after the first time period; then, the number of different types of abnormal situations that occur in the process node to be observed within the first time period is compared with the number of different types of abnormal situations that occur in the process node to be observed within the second time period to obtain a changing trend of abnormal situations that occur in the node to be observed under different types of situations; finally, based on the changing trend of abnormal situations that occur in the node to be observed under different types of situations, the process node to be optimized is determined from the nodes to be observed.

[0106] It can be understood that by comparing and analyzing the number of times various types of abnormal situations occur in the process nodes to be observed in two consecutive time periods (i.e., the first time period and the second time period), those process nodes with persistent abnormal problems, i.e., the process nodes to be optimized, can be accurately identified, so that the system can quickly focus on process nodes that may have a negative impact on financial business efficiency and user experience.

[0107] At the same time, by outputting the third prompt information, the problems existing in these process nodes can be clearly pointed out, such as unreasonable interface design or cumbersome processes, thereby providing relevant personnel with clear optimization directions and basis, helping relevant personnel to carry out process improvement work more effectively.

[0108] Optionally, this application provides a possible implementation method, which specifically includes:

[0109] In the first step, based on the number of times various types of abnormal situations occur in the process node to be observed within a first time period and the number of times various types of abnormal situations occur in a second time period after the first time period, the changing trend of various types of abnormal situations in the process node to be observed is determined.

[0110] The types of changing trends include but are not limited to upward trends and downward trends.

[0111] An upward trend refers to an increase in the number of occurrences of a particular type of abnormality at the observed node from the first time period to the second time period. For example, suppose the "Login Verification" node experienced three operational errors during the first time period, but eight during the second time period. Therefore, the "Login Verification" node can be considered to be on an upward trend.

[0112] A downward trend refers to a decrease in the number of abnormalities of a particular type for a node from the first time period to the second time period. For example, suppose the "Document Preparation and Review" node experienced 15 operational error anomalies in the first time period, but only four in the second time period. Therefore, the trend for the "Document Preparation and Review" node is considered downward.

[0113] The purpose of this step is to determine the changing trend of abnormal conditions on these process nodes by comparing the number of times various types of abnormal conditions occur in the process nodes to be observed in two consecutive time periods (the first time period and the second time period).

[0114] In the second step, the process nodes to be observed with an increasing trend of any type of abnormal situation are determined as the process nodes to be optimized among the process nodes to be observed.

[0115] The purpose of this step is to identify those process nodes to be observed that show an upward trend in a certain type of abnormal situation as nodes that need further optimization and improvement, i.e., process nodes to be optimized, based on the abnormal situation change trend obtained from the first step analysis.

[0116] Understandably, after determining the changing trends of various conditions at the process nodes to be observed, it is necessary to further screen out those nodes where abnormal conditions are showing an increasing trend. Frequent or increasing abnormal conditions at these nodes are likely to involve defects, cumbersome operations, or system instability. These problems may not only reduce work efficiency but also increase the risk of errors, adversely affecting the stability and efficiency of the overall process.

[0117] Therefore, by identifying nodes where abnormal situations show an upward trend as process nodes to be optimized, the system can conduct a more comprehensive analysis of these process nodes to be optimized, thereby ensuring the smooth operation and efficient development of financial business.

[0118] The process node optimization method for financial services provided in the embodiment of the present application identifies the nodes to be optimized by obtaining the actual time and number of repetitions of the user's operation of each process node within a preset time period. If the average time consumed by the user operation of a certain node exceeds the ideal value, or the average number of repeated operations is too high, it is regarded as a node to be optimized, and prompt information is output respectively, indicating possible reasons such as system abnormality, cumbersome process or unreasonable interface design. Furthermore, the number of times each node has various abnormalities (such as too long time consumption, too many repeated operations, user operation errors, system operation abnormalities) in different time periods is also counted, and the nodes to be observed are determined accordingly. Based on the changes in the number of abnormalities in consecutive time periods, the node to be optimized is finally determined, and optimization suggestions are output.

[0119] This method successfully solves the problem of unreasonable design of some business process nodes caused by the expansion of business types and the diversification of customer needs by obtaining and analyzing the actual time and number of repetitions of user operations on various financial business process nodes within a preset time period. It can effectively identify those nodes where user operations take too long or are frequently repeated as objects to be optimized, and output prompt information to reveal potential reasons, such as system anomalies, cumbersome processes or unreasonable interface design. Furthermore, the method accurately locates the nodes to be observed by counting the number of anomalies of each node in different time periods, and finally determines the nodes to be optimized and optimization suggestions based on the changes in anomalies within continuous time periods. This method not only significantly improves the speed and quality of business processing, reduces customer operation errors and repeated operations, but also greatly reduces the customer's operating burden, making the business process smoother and more efficient.

[0120] Figure 3 The schematic diagram of the structure of the process node optimization device for financial services provided in this application is as follows: Figure 3 As shown, the process node optimization device 300 for financial services provided in this embodiment includes:

[0121] The acquisition module 301 is used to obtain the actual operation time and the actual number of repeated operations at each process node of multiple users in the process of operating financial services within a preset time period;

[0122] Determining module 302 is configured to, for any process node, determine the process node as a process node to be optimized if an average of the actual operation time consumed by the multiple users at the process node is greater than a preset ideal operation time consumed by the process node, and / or if an average of the actual number of repeated operations performed by the multiple users at the process node is greater than a preset ideal number of repeated operations performed at the process node;

[0123] The output module 303 is used to output prompt information for the process node to be optimized, where the prompt information is used to indicate the reason and / or suggestion for optimization.

[0124] The process node optimization device for financial services provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effects are similar, and are not described in detail in this embodiment.

[0125] Figure 4 This is a schematic diagram of the structure of the process node optimization device for financial services provided in this application. Figure 4 As shown, the electronic device 400 provided in this embodiment includes: at least one processor 401 and a memory 402. Optionally, the device 400 further includes a communication component 403. The processor 401, the memory 402 and the communication component 403 are connected via a bus 404.

[0126] In a specific implementation process, at least one processor 401 executes the computer-executable instructions stored in the memory 402, so that the at least one processor 401 performs the above method.

[0127] The specific implementation process of the processor 401 can be found in the above method embodiment. Its implementation principle and technical effects are similar and will not be repeated here in this embodiment.

[0128] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASICs), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0129] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage.

[0130] A bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, and control buses. For ease of illustration, the buses in the drawings of this application are not limited to just one bus or just one type of bus.

[0131] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0132] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0133] The readable storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0134] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0135] The division of units is merely a logical functional division; actual implementations may employ alternative divisions, such as combining or integrating multiple units or components into another system, or omitting or disabling certain features. Furthermore, any direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units, either through an interface, electrical, mechanical, or other means.

[0136] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0137] 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.

[0138] If a function is implemented as 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, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the method of the present invention. The aforementioned storage medium includes various media that can store program code, such as USB flash drives, mobile hard drives, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.

[0139] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0140] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0141] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0142] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0143] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0144] If an integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0145] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, 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. The computer software product is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, magnetic disk, or optical disk, etc., various media that can store program code.

[0146] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a particular embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined in any way. To keep the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0147] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0148] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for optimizing process nodes of financial services, characterized in that: include: Get the financial business operations of multiple users within a preset time period. The actual operation time and actual number of repeated operations at each process node during the process; For any process node, if the average actual operation time of the multiple users at the process node is greater than the preset ideal operation time of the process node, and / or if the average actual number of repeated operations of the multiple users at the process node is greater than the preset ideal number of repeated operations of the process node, then the process node is determined to be a process node to be optimized; Outputting prompt information for the process node to be optimized, wherein the prompt information is used to indicate the reason for optimization and / or suggestions; Also includes: Determine the number of different types of abnormal situations that occur at each process node within a first time period, wherein the different types of abnormal situations include: the actual operation time is greater than the ideal operation time, and the difference between the actual operation time and the ideal operation time is greater than a first threshold; the actual number of repeated operations is greater than the ideal number of repeated operations, and the difference between the actual number of repeated operations and the ideal number of repeated operations is greater than a second threshold; user operation error; system operation; Determining a process node to be observed among the process nodes based on the number of times different types of abnormal situations occur at the process nodes; Based on the number of times various types of abnormal situations occur in the process node to be observed within a first time period, and the number of times various types of abnormal situations occur in a second time period after the first time period, determining a process node to be optimized among the process nodes to be observed, and outputting third prompt information, wherein the third prompt information is used to prompt that the reason for the optimization is unreasonable interface design or cumbersome process; The determining of a process node to be observed among the process nodes based on the number of times different types of abnormal situations occur at the process nodes includes: Determining an abnormality rate of each process node based on the number of times different types of abnormal situations occur at each process node; The process node with the highest abnormality rate and the process node with the most abnormal situations are both determined as the process nodes to be observed.

2. The method according to claim 1, characterized in that Outputting prompt information for the process node to be optimized includes: If the average actual operation time of the multiple users at the process node is greater than the preset ideal operation time of the process node, a first prompt message is output for the process node to be optimized, and the first prompt message is used to indicate that the reason for the optimization is system abnormality or cumbersome process.

3. The method according to claim 1, characterized in that Outputting prompt information for the process node to be optimized includes: If the average actual number of repeated operations of the multiple users on the process node is greater than the preset ideal number of repeated operations of the process node, a second prompt message is output for the process node to be optimized, and the second prompt message is used to prompt that the reason for the optimization is unreasonable interface design or cumbersome process.

4. The method according to claim 1, wherein The determining of the process nodes to be optimized in the process nodes to be observed based on the number of times various types of abnormal situations occur in the process nodes to be observed within a first time period and the number of times various types of abnormal situations occur in a second time period after the first time period includes: Determining a change trend of various types of abnormal situations of the process node to be observed based on the number of times various types of abnormal situations occur in the process node to be observed within a first time period and the number of times various types of abnormal situations occur in a second time period after the first time period; A process node to be observed in which the change trend of any type of abnormal situation is increasing is determined as a process node to be optimized among the process nodes to be observed.

5. A process node optimization device for financial services, characterized in that: include: An acquisition module is used to obtain the actual operation time and actual number of repeated operations at each process node of multiple users in the process of operating financial services within a preset time period; a determination module configured to, for any process node, determine the process node as a process node to be optimized if an average of actual operation times of the multiple users at the process node is greater than a preset ideal operation time of the process node, and / or if an average of actual repeated operation times of the multiple users at the process node is greater than a preset ideal repeated operation times of the process node; An output module, configured to output prompt information for the process node to be optimized, wherein the prompt information is used to indicate the reason for optimization and / or suggestions; The determining module is further configured to determine the number of different types of abnormal situations occurring at each process node within the first time period, wherein the different types of abnormal situations include: the actual operation time being greater than the ideal operation time, and the difference between the actual operation time and the ideal operation time being greater than a first threshold; the actual number of repeated operations being greater than the ideal number of repeated operations, and the difference between the actual number of repeated operations and the ideal number of repeated operations being greater than a second threshold; user operation error; system operation; The determining module is further configured to determine a process node to be observed among the process nodes based on the number of times different types of abnormal situations occur at the process nodes; The determining module is further configured to determine a process node to be optimized among the process nodes to be observed based on the number of times various types of abnormal situations occur in the process node to be observed within a first time period and the number of times various types of abnormal situations occur in a second time period after the first time period, and output third prompt information, wherein the third prompt information is used to indicate that the reason for the optimization is an unreasonable interface design or a cumbersome process; The determining module is further configured to determine an abnormality rate of each process node based on the number of times different types of abnormal situations occur at each process node; The determining module is specifically configured to determine the process node with the highest abnormality rate and the process node with the most abnormal situations as the process node to be observed.

6. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 4 when executed by a processor.

8. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 4 when executed by a processor.

Images