Request shunting method and device, equipment, medium and product

Abstract

The invention discloses a request shunting method and device, equipment, a medium and a product, and relates to the technical field of data processing. The method comprises the steps of obtaining first user information corresponding to a first user identifier in a first request under the condition that the first request is received; when the first user information does not meet a preset automatic processing rule and the number of requests of a first target request type sent to the first device in a preset time period is not greater than a request number threshold, sending a first request to the first device; and when the number of the requests of the first target request type sent to the first device in the preset time period is greater than a request number threshold, sending the first request to the second device. According to the request type of the request, the request can be shunted according to the automatic processing rule and the request number threshold value corresponding to the request type, so that the processing pressure of equipment is reduced, and the request processing efficiency is improved.

Description

Technical Field

[0001] The present application belongs to the field of data processing technology, and in particular, relates to a request diversion method, device, equipment, medium and product. Background Art

[0002] With the rapid development of information technology and Internet technology, some organizations, such as financial institutions and banks, have faced the risk of data and resource information leakage. Therefore, in this scenario, it is necessary to strengthen the management and control of data and resource information, and process and verify the requests received by the device. Among them, requests include data requests, permission change requests, and resource application requests.

[0003] In the prior art, when a device receives a request input from a user, the request is processed and verified. In this way, when there are many users, the processing pressure of the device is relatively large, and the processing efficiency of the request is also relatively low. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, device, medium and product for diverting requests. For requests of a first target request type that cannot be automatically processed, if the requests of the first target request type sent to the first device have not exceeded the request quantity threshold, the requests are diverted to the first device; if the requests of the first target request type sent to the first device exceed the request quantity threshold, the requests are diverted to the second device; according to the request type of the request, in accordance with the automatic processing rules and the request quantity threshold corresponding to the request type, the requests can be diverted, thereby reducing the processing pressure of the device and improving the processing efficiency of the request.

[0005] In a first aspect, an embodiment of the present application provides a request diversion method, including:

[0006] When receiving a first request, obtaining first user information corresponding to a first user identifier in the first request, the first request being of a first target request type;

[0007] In the case where the first user information does not satisfy the preset automatic processing rule, detecting whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold;

[0008] When the number of requests of the first target request type sent to the first device within a preset time period is not greater than a request number threshold, send a first request to the first device so that the first device displays the first request and receives a first input of a first user on a processing result of the first request;

[0009] When the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, a first request is sent to the second device so that the second device displays the first request and receives a second input from a second user on the processing result of the first request.

[0010] In a possible embodiment, it also includes:

[0011] When the first user information satisfies a target automatic processing rule in the preset automatic processing rule, a target processing result corresponding to the target automatic processing rule is generated.

[0012] In a possible implementation, the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold; if the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, after sending the first request to the second device, the method further includes:

[0013] When receiving the second request, obtaining second user information corresponding to the second user identifier in the second request, where the second request is of the first target request type;

[0014] When the second user information does not satisfy the preset automatic processing rule, a second request is sent to the second device so that the second device displays the second request and receives a third input of the second user on the processing result of the second request.

[0015] In a possible implementation, when the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, after sending the first request to the second device, the method further includes:

[0016] In the case of receiving a third request, obtaining third user information corresponding to a third user identifier in the third request, where the third request is of a second target request type, and the second target request type is a request type other than the first target request type;

[0017] In the case where the third user information does not satisfy the preset automatic processing rule, detecting whether the number of requests of the second target request type sent to the first device within a preset time period is greater than a request number threshold;

[0018] When the number of requests of the second target request type sent to the first device within the preset time period is not greater than the request number threshold, send a third request to the first device so that the first device displays the third request and receives a fourth input of the first user on the processing result of the third request;

[0019] When the number of requests of the second target request type sent to the first device within a preset time period is greater than the request number threshold, a third request is sent to the second device so that the second device displays the third request and receives a fifth input from the second user on the processing result of the third request.

[0020] In a possible embodiment, it also includes:

[0021] receiving a query request for a processing progress of the first request;

[0022] Displays the progress of the first request.

[0023] In a possible embodiment, the first target request type includes at least a request to change permissions and a request to change a resource replacement quantity.

[0024] In a second aspect, an embodiment of the present application provides a request diversion device, including:

[0025] an acquisition module, configured to acquire, upon receiving a first request, first user information corresponding to a first user identifier in the first request, where the first request is of a first target request type;

[0026] a detection module, configured to detect whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold when the first user information does not satisfy a preset automatic processing rule;

[0027] a sending module, configured to send a first request to the first device when the number of requests of the first target request type sent to the first device within a preset time period is not greater than a request number threshold, so that the first device displays the first request and receives a first input of a first user on a processing result of the first request;

[0028] The sending module is also used to send a first request to a second device when the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, so that the second device displays the first request and receives a second input from a second user on the processing result of the first request.

[0029] In a third aspect, an embodiment of the present application provides an electronic device, the device comprising:

[0030] a processor and a memory storing computer program instructions;

[0031] The processor implements any of the above request diversion methods when executing computer program instructions.

[0032] In a fourth aspect, an embodiment of the present application provides a computer storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method for diverting requests of any one of the above items is implemented.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program product, characterized in that when the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute any one of the above-mentioned request diversion methods.

[0034] The request diversion method, apparatus, device, medium and product of the embodiments of the present application, the method comprising: upon receiving a first request, obtaining first user information corresponding to a first user identifier in the first request, the first request being a first target request type; in a case where the first user information does not satisfy a preset automatic processing rule, detecting whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold; in a case where the number of requests of the first target request type sent to the first device within the preset time period is not greater than the request number threshold, sending a first request to the first device so that the first device displays the first request and receives a first input from the first user on a processing result of the first request; in a case where the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, sending a first request to a second device so that the second device displays the first request and receives a second input from the second user on a processing result of the first request.

[0035] In this way, for requests of the first target request type that cannot be automatically processed, if the number of requests of the first target request type sent to the first device has not exceeded the request quantity threshold, the requests will be diverted to the first device; if the number of requests of the first target request type sent to the first device exceeds the request quantity threshold, the requests will be diverted to the second device; according to the request type of the request, in accordance with the automatic processing rules and the request quantity threshold corresponding to the request type, the requests can be diverted, thereby reducing the processing pressure of the device and improving the processing efficiency of the request. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0037] Figure 1 It is a flowchart of a request diversion method provided by an embodiment of the present application;

[0038] Figure 2 is a flowchart of a request diversion method provided by another embodiment of the present application;

[0039] Figure 3 is a flowchart of a request diversion method provided by another embodiment of the present application;

[0040] Figure 4 is a flowchart of a request diversion method provided by yet another embodiment of the present application;

[0041] Figure 5 is a flowchart of a request diversion method provided by yet another embodiment of the present application;

[0042] Figure 6 is a schematic structural diagram of a requested flow diversion device provided in yet another embodiment of the present application;

[0043] Figure 7 It is a structural diagram of an electronic device provided in yet another embodiment of the present application. DETAILED DESCRIPTION

[0044] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0045] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0046] It should be noted that the acquisition, storage, use and processing of data in the embodiments of the present application are in compliance with the relevant provisions of national laws and regulations.

[0047] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0048] With the rapid development of information technology and Internet technology, some organizations, such as financial institutions and banks, have faced the risk of data and resource information leakage. Therefore, in this scenario, it is necessary to strengthen the management and control of data and resource information, and process and verify the requests received by the device. Among them, requests include data requests, permission change requests, and resource application requests.

[0049] In the prior art, when a device receives a request input from a user, the request is processed and verified. In this way, when there are many users, the processing pressure of the device is relatively large, and the processing efficiency of the request is also relatively low.

[0050] In order to solve the problems of the prior art, the embodiments of the present application provide a method, apparatus, device, medium and product for diverting requests. The method for diverting requests provided in the embodiments of the present application, for requests of the first target request type that cannot be automatically processed, if the requests of the first target request type sent to the first device have not exceeded the request quantity threshold, the requests are diverted to the first device; if the requests of the first target request type sent to the first device exceed the request quantity threshold, the requests are diverted to the second device; according to the request type of the request, according to the automatic processing rules and the request quantity threshold corresponding to the request type, the requests can be diverted, thereby reducing the processing pressure of the device and improving the processing efficiency of the request.

[0051] The following first introduces the request diversion method provided by the embodiment of the present application. Figure 1 As shown, the request diversion method provided in the embodiment of the present application includes the following steps.

[0052] S110. When a first request is received, obtain first user information corresponding to a first user identifier in the first request, where the first request is a first target request type.

[0053] Here, the first request may include requests of different request types, such as data requests, permission change requests, and resource application requests. The first request includes a user identifier. In some embodiments, the first request may be a request received from multiple channels, such as a user's terminal device, a designated device, and the like. As an example, the user may issue the first request through an application or a communication connection of the terminal device. In another example, the user may issue the first request through a device at a designated location (such as an ATM) or a device used by a staff member at the designated location.

[0054] In some embodiments, the first user identification may include but is not limited to at least one of a user name, a user ID, a user account number, and a user number. The first user information may include but is not limited to at least one of the user's transaction information, transaction value, transaction quantity, and abnormal information.

[0055] In some embodiments, the first user information corresponding to the first user identifier is obtained from a database. The database stores a preset user identifier and user information of the preset user identifier in advance.

[0056] S120: When the first user information does not satisfy a preset automatic processing rule, detect whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold.

[0057] Here, the preset automatic processing rule is set in advance. The request quantity threshold can be set in advance. The preset time period can be set in advance, such as within a day.

[0058] Specifically, the request quantity threshold may be a maximum number of requests of the first target request type that the first device can receive per day. The request quantity threshold may be determined according to the capability of the first device to process requests.

[0059] In some embodiments, the request quantity threshold may be determined based on the request type, and the request quantity thresholds corresponding to different request types may be the same or different.

[0060] In some embodiments, the request quantity threshold may also be limited to a certain organization. Specifically, the request quantity threshold may be the maximum number of requests of the first target request type that the first device can receive from the target organization per day. The target organization may be a bank, a financial institution, etc. The request quantity threshold may be the same or different for different organizations.

[0061] In some embodiments, the preset automatic processing rules may include automatic processing rules for multiple processing scenarios, and the preset automatic processing rules may also be limited to a certain organization. The preset automatic processing rules may be the same or different for different organizations. In the case where the first user information does not satisfy the preset automatic processing rules for all processing scenarios, it is detected whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold.

[0062] It is understandable that the preset automatic processing rules can be set by authorized users within the organization, that is, only authenticated users can set the preset automatic processing rules.

[0063] S130. When the number of requests of the first target request type sent to the first device within a preset time period is not greater than a request number threshold, send a first request to the first device so that the first device displays the first request and receives a first input from a first user on a processing result of the first request.

[0064] Here, the first device is set in advance.

[0065] In some embodiments, the first input is the input of the first user on the processing result of the first request, and may be input of different scenarios, such as a scenario of agreeing to the request and a scenario of disagreeing to the request.

[0066] In some embodiments, the scenario can also be a more detailed scenario, such as a supplementary information scenario, a queuing scenario, a confirmation reception scenario, etc.

[0067] It is understandable that the request sent to the first device can be manually accepted by the first user to obtain the processing result.

[0068] S140. When the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, send a first request to the second device so that the second device displays the first request and receives a second input from a second user on a processing result of the first request.

[0069] Here, the second device is set in advance.

[0070] In some embodiments, the second input is the second user's input on the processing result of the first request, and may be input of different scenarios, such as a scenario of agreeing to the request and a scenario of disagreeing to the request.

[0071] In some embodiments, the scenario can also be a more detailed scenario, such as a supplementary information scenario, a queuing scenario, a confirmation reception scenario, etc.

[0072] It is understandable that the request sent to the second device can be manually accepted by the second user to obtain the processing result.

[0073] In this way, for requests of the first target request type that cannot be automatically processed, if the number of requests of the first target request type sent to the first device has not exceeded the request quantity threshold, the requests will be diverted to the first device; if the number of requests of the first target request type sent to the first device exceeds the request quantity threshold, the requests will be diverted to the second device; according to the request type of the request, in accordance with the automatic processing rules and the request quantity threshold corresponding to the request type, the requests can be diverted, thereby reducing the processing pressure of the device and improving the processing efficiency of the request.

[0074] Based on this, in some embodiments, such as Figure 2As shown, corresponding to the above S120, the method may further include:

[0075] S210. When the first user information satisfies a target automatic processing rule in a preset automatic processing rule, a target processing result corresponding to the target automatic processing rule is generated.

[0076] Here, the target automatic processing rule is the automatic processing rule under the target scenario. The target scenario includes the request approval scenario and the request disapproval scenario.

[0077] In some embodiments, the target scenario may be a request disagreement scenario. The automatic processing rules under the target scenario may include multiple rules, and as long as the first user information hits one of them, the automatic processing rules under the target scenario are satisfied. If the abnormal information in the first user information satisfies the automatic processing rules under the request disagreement scenario, the target processing result is the request disagreement information.

[0078] It should be noted that the first user information can only match the automatic processing rule in one scenario at most.

[0079] In this way, for requests that can be processed automatically, the processing results of the requests can be automatically generated according to the preset automatic processing rules, without the need for manual processing, saving labor costs and improving efficiency and accuracy. For requests that cannot be processed automatically, the request quantity threshold of the first device determines whether to send the request to the first device or the second device. The requests can be divided into three streams, thereby reducing the processing pressure when a single device is processing, and further improving the processing efficiency of the requests.

[0080] Based on this, in some embodiments, Figure 3 As shown, the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold; after the above S140, the method may further include:

[0081] S141. When a second request is received, obtain second user information corresponding to a second user identifier in the second request, where the second request is of the first target request type;

[0082] S142: When the second user information does not satisfy the preset automatic processing rule, send a second request to the second device, so that the second device displays the second request and receives a third input of the second user on the processing result of the second request.

[0083] Here, the second request and the first request are of the same request type. The preset user identifier includes the second user identifier.

[0084] In some embodiments, for requests of the same request type, after receiving the first request, if the number of requests of the first target request type sent to the first device within a preset time period is greater than the request number threshold, then if the second request does not meet the preset automatic processing rule, the second request is sent to the second device. That is, if the first request cannot be sent to the first device, then the second request cannot be sent to the first device either, and can be sent directly to the second device.

[0085] In some embodiments, the third input is the second user's input of the processing result of the second request, which may be input of different scenarios, such as a scenario of agreeing to the request and a scenario of disagreeing to the request.

[0086] In some embodiments, the scenario can also be a more detailed scenario, such as a supplementary information scenario, a queuing scenario, a confirmation reception scenario, etc.

[0087] In some embodiments, similar to the first device, the second device may also set a request quantity threshold, and if the number of requests of the first target request type sent to the second device within a preset time period is greater than the request quantity threshold of the second device, the second device refuses to receive requests of the first target request type. Alternatively, the third device may be set to receive the remaining requests of the first target request type within a preset time period.

[0088] In this way, in the processing stage of the first request, it has been determined that the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold. Then, when a second request of the same request type as the first request and the same first target request type is received, it is only necessary to determine whether the second request can be automatically processed, and it is no longer necessary to consider whether to send it to the first device for processing. If it cannot be automatically processed, it is directly sent to the second device for processing, which reduces the time for making judgments, saves computing resources, and can further improve the processing efficiency of requests.

[0089] Based on this, in some embodiments, such as Figure 4 As shown, after the above S140, the method may further include:

[0090] S150: upon receiving a third request, obtaining third user information corresponding to a third user identifier in the third request, where the third request is of a second target request type, and the second target request type is a request type other than the first target request type;

[0091] S160: If the third user information does not satisfy the preset automatic processing rule, detect whether the number of requests of the second target request type sent to the first device within a preset time period is greater than a request number threshold;

[0092] S170: When the number of requests of the second target request type sent to the first device within the preset time period is not greater than the request number threshold, send a third request to the first device, so that the first device displays the third request, and receives a fourth input of the first user on the processing result of the third request;

[0093] S180. When the number of requests of the second target request type sent to the first device within a preset time period is greater than a request number threshold, send a third request to the second device so that the second device displays the third request and receives a fifth input from the second user on the processing result of the third request.

[0094] Here, the third request and the first request are of different request types. The preset user identifier includes the third user identifier.

[0095] In some embodiments, for requests of different request types, after receiving the first request, regardless of whether the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, in the case of receiving the third request, the third user information corresponding to the third user identifier in the third request is obtained, and in the case that the third user information does not meet the preset automatic processing rules, first detect whether the number of requests of the second target request type sent to the first device within the preset time period is greater than the request number threshold, and then decide whether to send the third request to the first device or the second device. If the number of requests of the second target request type sent to the first device within the preset time period is not greater than the request number threshold, send the third request to the first device; if the number of requests of the second target request type sent to the first device within the preset time period is greater than the request number threshold, send the third request to the second device.

[0096] In some embodiments, when the third user information satisfies a preset automatic processing rule, a processing result corresponding to the automatic processing rule is generated.

[0097] It should be noted that the fourth input is the first user's input of the processing result of the third request, which can be input of different scenarios, such as agreeing to the request scenario and disagreeing to the request scenario. The fifth input is the second user's input of the processing result of the third request, which can be input of different scenarios, such as agreeing to the request scenario and disagreeing to the request scenario.

[0098] In this way, for requests of different request types, after receiving the first request, regardless of whether the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, it is necessary to re-determine which device to send to, that is, different requests are distinguished according to the request type, and the requests are diverted, thereby avoiding the problem of excessive processing pressure caused by concentrated processing of requests of the same type, thereby improving the processing efficiency of the requests.

[0099] Based on this, in some embodiments, the method may further include:

[0100] receiving a query request for a processing progress of the first request;

[0101] Displays the progress of the first request.

[0102] In some embodiments, the query request may be a request received from multiple channels, such as a user's terminal device, a designated device, etc. As an example, the user may input the query request through an application or a communication connection of the terminal device. In another example, the user may input the query request through a device at a designated location (such as an ATM) or a device used by a staff member at the designated location.

[0103] In some embodiments, the processing progress corresponds to the scenario, which may include but is not limited to being processed, request approved, and request not approved. It may also be a more detailed processing progress, such as being processed including supplementary information, being queued, and confirmation of receipt.

[0104] In some embodiments, while displaying the processing progress, the time when the request is received, the time when the request is sent, the name of the first device or the second device that sends the request, etc. can also be displayed.

[0105] In this way, users can understand the processing progress of the requests they initiated through different channels, which makes it convenient for users to grasp the progress of business processing in a timely manner and improve user experience.

[0106] Based on this, in some embodiments, the first target request type includes at least a request to change permissions and a request to change resource replacement quantity.

[0107] As an example, Figure 5 As shown, the request diversion method provided in the embodiment of the present application may specifically include:

[0108] S1. receiving a request for changing permissions, wherein the request for changing permissions includes a user ID;

[0109] S2, obtaining user information corresponding to the user identifier, and detecting whether the user information corresponding to the user identifier satisfies a preset automatic processing rule; if not, executing S3; if the user information corresponding to the user identifier satisfies a target automatic processing rule in the preset automatic processing rule, executing S6;

[0110] S3, detecting whether the number of requests of the first target request type sent to the first device within a preset time period is greater than the request number threshold; if not, sending a request to the first device and executing S4; if greater, sending a request to the first device and executing S5;

[0111] S4. The first device displays the request and receives an input from the first user on a processing result of the request, where the input is an input of consent to change the permission or an input of disagreement to change the permission;

[0112] S5. The second device displays the request and receives an input from the second user on a processing result of the request, where the input is an input of consent to change the permission or an input of disagreement to change the permission;

[0113] S6. Generate a target processing result corresponding to the target automatic processing rule, where the target processing result is permission change consent information or permission change disapproval information.

[0114] It can be understood that if the processing result is that the information is agreed to be changed, the permission is changed; if the processing result is that the information is not agreed to be changed, the permission is not changed, and a prompt message can be sent to the device that sent the request to prompt the user that the verification has not passed.

[0115] In this way, in the financial field, the process of lifting controls and adjusting limits on personal bank accounts can be accelerated by diverting requests, thereby improving processing efficiency and enhancing user experience.

[0116] In the embodiments provided in the present application, unified access, unified diversion, unified processing, and unified monitoring of multi-channel tasks accelerate the processing efficiency of requests, improve user experience, and empower and reduce the burden on devices.

[0117] In the embodiments provided in the present application, unified diversion of multi-channel tasks is achieved through the setting of request quantity thresholds, so that tasks can be flexibly diverted to different work teams for processing, meeting changes in personnel configurations between devices. The multi-channel request initiation and processing progress query function enables unified access to multi-channel tasks and task progress tracking, making it convenient for users to handle business, timely knowing the progress of business handling, and improving customer experience. Through the flexible configuration of automatic processing rules, automatic business handling can be achieved, which can greatly reduce manual pressure, reduce burden, and speed up business handling time. Through the first device and the second device, centralized task processing is achieved, which makes full use of manual resources and improves the quality and efficiency of business handling.

[0118] Based on the request diversion method provided in the above embodiment, the present application also provides a specific implementation of the request diversion device. Please refer to the following embodiment.

[0119] See also Figure 6 , the request splitting device 300 provided in the embodiment of the present application includes:

[0120] An acquisition module 310 is configured to acquire, upon receiving a first request, first user information corresponding to a first user identifier in the first request, where the first request is of a first target request type;

[0121] A detection module 320, configured to detect whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold when the first user information does not satisfy a preset automatic processing rule;

[0122] A sending module 330, configured to send a first request to the first device when the number of requests of the first target request type sent to the first device within a preset time period is not greater than a request number threshold, so that the first device displays the first request and receives a first input of a first user on a processing result of the first request;

[0123] The sending module 330 is also used to send a first request to a second device when the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, so that the second device displays the first request and receives a second input from a second user on the processing result of the first request.

[0124] Based on this, in some embodiments, the apparatus 300 may further include:

[0125] The generating module is used to generate a target processing result corresponding to the target automatic processing rule when the first user information satisfies the target automatic processing rule in the preset automatic processing rule.

[0126] Based on this, in some embodiments, the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold; the apparatus 300 may further include:

[0127] The acquisition module 310 is further configured to, if the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, after sending the first request to the second device, and if a second request is received, acquire second user information corresponding to the second user identifier in the second request, the second request being of the first target request type;

[0128] The sending module 330 is also used to send a second request to the second device when the second user information does not meet the preset automatic processing rules, so that the second device displays the second request and receives a third input from the second user on the processing result of the second request.

[0129] Based on this, in some embodiments, the apparatus 300 may further include:

[0130] The acquisition module 310 is further configured to, if the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold, after sending the first request to the second device, in the case where a third request is received, acquire third user information corresponding to a third user identifier in the third request, the third request being of the second target request type, and the second target request type being a request type other than the first target request type;

[0131] The detection module 320 is further configured to detect whether the number of requests of the second target request type sent to the first device within a preset time period is greater than a request number threshold when the third user information does not satisfy the preset automatic processing rule;

[0132] The sending module 330 is further configured to send a third request to the first device when the number of requests of the second target request type sent to the first device within a preset time period is not greater than a request number threshold, so that the first device displays the third request and receives a fourth input of the first user on a processing result of the third request;

[0133] The sending module 330 is also used to send a third request to the second device when the number of requests of the second target request type sent to the first device within a preset time period is greater than a request number threshold, so that the second device displays the third request and receives a fifth input from the second user on the processing result of the third request.

[0134] Based on this, in some embodiments, the apparatus 300 may further include:

[0135] A receiving module, configured to receive a query request for a processing progress of a first request;

[0136] The display module is used to display the processing progress of the first request.

[0137] Based on this, in some embodiments, the first target request type includes at least a request to change permissions and a request to change resource replacement quantity.

[0138] The various modules of the request diversion device provided in the embodiment of the present application can realize the functions of the various steps of the request diversion method provided above and achieve the corresponding technical effects, which will not be repeated here for the sake of concise description.

[0139] Based on the same inventive concept, an embodiment of the present application also provides an electronic device.

[0140] Figure 7 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application is shown.

[0141] The electronic device may include a processor 401 and a memory 402 storing computer program instructions.

[0142] Specifically, the processor 401 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0143] Memory 402 may include a large capacity memory for data or instructions. By way of example and not limitation, memory 402 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, memory 402 may include a removable or non-removable (or fixed) medium. In appropriate cases, memory 402 may be inside or outside of an integrated gateway disaster recovery device. In a specific embodiment, memory 402 is a non-volatile solid-state memory.

[0144] The memory may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of the present disclosure.

[0145] The processor 401 implements any one of the request diversion methods in the above embodiments by reading and executing the computer program instructions stored in the memory 402 .

[0146] In one example, the electronic device may further include a communication interface 403 and a bus 410. Figure 7 As shown, the processor 401, the memory 402, and the communication interface 403 are connected via a bus 410 and communicate with each other.

[0147] The communication interface 403 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0148] The bus 410 includes hardware, software or both, coupling the components of the electronic device to each other. For example, but not limitation, the bus may include an accelerated graphics port (Accelerated Graphics Port, AGP) or other graphics bus, an enhanced industry standard architecture (Extended Industry Standard Architecture, EISA) bus, a front side bus (Front Side Bus, FSB), a hypertransport (Hyper Transport, HT) interconnection, an industry standard architecture (Industry Standard Architecture, ISA) bus, an infinite bandwidth interconnection, a low pin count (Linear Predictive Coding, LPC) bus, a memory bus, a micro channel architecture (MicroChannel Architecture, MCA) bus, a peripheral component interconnect (Peripheral Component Interconnect, PCI) bus, a PCI-Express (Peripheral Component Interconnect-X, PCI-X) bus, a serial advanced technology attachment (Serial Advanced Technology Attachment, SATA) bus, a video electronics standard association local (VESA Local Bus, VLB) bus or other suitable buses or a combination of two or more of these. Where appropriate, the bus 410 may include one or more buses. Although the embodiments of the present application describe and illustrate a specific bus, the present application considers any suitable bus or interconnection. The electronic device can execute the request diversion method in the embodiments of the present invention, thereby realizing the above-mentioned request diversion method.

[0149] In addition, in combination with the request diversion method in the above embodiment, the embodiment of the present application can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the request diversion methods in the above embodiment is implemented.

[0150] The present application also provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes each process of an embodiment of a diversion method to implement any of the above requests.

[0151] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0152] The functional blocks shown in the structural block diagram described above can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), appropriate firmware, plug-in, function card, etc. When implemented in software, the elements of the present application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or communication link by a data signal carried in a carrier. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (Read-Only Memory, ROM), flash memory, erasable read-only memory (Erasable ReadOnly Memory, EROM), floppy disks, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical discs, hard disks, optical fiber media, radio frequency (Radio Frequency, RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0153] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0154] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0155] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A request diversion method, characterized in that: include: Upon receiving a first request, obtaining first user information corresponding to a first user identifier in the first request, the first request being of a first target request type; In a case where the first user information does not satisfy a preset automatic processing rule, detecting whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold; When the number of requests of the first target request type sent to the first device within the preset time period is not greater than the request number threshold, sending the first request to the first device so that the first device displays the first request and receives a first input of a first user on a processing result of the first request; When the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, the first request is sent to the second device so that the second device displays the first request and receives a second input from a second user on the processing result of the first request.

2. The request diversion method according to claim 1, characterized in that: Also includes: In the case where the first user information satisfies a target automatic processing rule in the preset automatic processing rule, a target processing result corresponding to the target automatic processing rule is generated.

3. The request diversion method according to claim 1, characterized in that: The number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold; When the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, after sending the first request to the second device, the method further includes: When receiving a second request, obtaining second user information corresponding to a second user identifier in the second request, the second request being of the first target request type; In the case where the second user information does not satisfy the preset automatic processing rule, the second request is sent to the second device so that the second device displays the second request and receives a third input of the second user on the processing result of the second request.

4. The request diversion method according to claim 1, characterized in that: When the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, after sending the first request to the second device, the method further includes: In the case of receiving a third request, obtaining third user information corresponding to a third user identifier in the third request, wherein the third request is of a second target request type, and the second target request type is a request type other than the first target request type; In a case where the third user information does not satisfy the preset automatic processing rule, detecting whether the number of requests of the second target request type sent to the first device within the preset time period is greater than the request number threshold; When the number of requests of the second target request type sent to the first device within the preset time period is not greater than the request number threshold, sending the third request to the first device, so that the first device displays the third request and receives a fourth input of the first user on a processing result of the third request; When the number of requests of the second target request type sent to the first device within the preset time period is greater than the request number threshold, the third request is sent to the second device so that the second device displays the third request and receives the fifth input of the second user on the processing result of the third request.

5. The request diversion method according to claim 1, characterized in that: Also includes: receiving a query request for the processing progress of the first request; The processing progress of the first request is displayed.

6. The request diversion method according to claim 1, characterized in that: The first target request type includes at least a request to change permissions and a request to change resource replacement quantity.

7. A request processing device, characterized in that: include: an acquisition module, configured to acquire, upon receiving a first request, first user information corresponding to a first user identifier in the first request, wherein the first request is of a first target request type; a detection module, configured to detect whether the number of requests of the first target request type sent to the first device within a preset time period is greater than a request number threshold when the first user information does not satisfy a preset automatic processing rule; a sending module, configured to send the first request to the first device if the number of requests of the first target request type sent to the first device within the preset time period is not greater than the request number threshold, so that the first device displays the first request and receives a first input from a first user on a processing result of the first request; The sending module is also used to send the first request to the second device when the number of requests of the first target request type sent to the first device within the preset time period is greater than the request number threshold, so that the second device can display the first request and receive a second input from a second user on the processing result of the first request.

8. An electronic device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the request diversion method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the request diversion method according to any one of claims 1 to 6 is implemented.

10. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute the requested diversion method as described in any one of claims 1-6.

Images