Permission reminder method, device, equipment and storage medium

Abstract

The embodiments of the present disclosure provide a permission reminder method, which can be applied to the financial field and the resource scheduling technology field. The permission reminder method includes: responding to a transaction request of a target user for a target service, verifying the transaction permission of the target user according to the target request information in the transaction request, and outputting a first verification result; when the first verification result indicates that the target user does not have the transaction permission of the target service, sending the target request information to the message queue platform; when the sorting identification number is less than or equal to the preset threshold, generating permission reminder information according to the target request information in the message queue platform; sending the permission reminder information to the information sending queue; sending each permission reminder information in the information sending queue in turn according to the information sending frequency, wherein the information sending frequency is determined according to the current limiting algorithm. The embodiments of the present disclosure also provide a permission reminder device, equipment, storage medium and program product.

Description

Technical Field

[0001] The present disclosure relates to the financial field and the resource scheduling technology field, and more specifically to a permission reminder method, device, equipment, medium and program product. Background Art

[0002] The open platform needs to manage the service models of cooperative institutions for approved third-party product service models, and send email alerts for transactions for which there is no trading authority.

[0003] In the process of realizing the invention concept of the present disclosure, the inventors discovered the following problems in the related art: in the related art, when the transaction volume is large in a short period of time, the demand for email sending is large, resulting in problems such as email sending failure and information loss, and the system security is low. Summary of the invention

[0004] In view of the above problems, embodiments of the present disclosure provide a permission reminder method, apparatus, device, medium and program product.

[0005] According to a first aspect of an embodiment of the present disclosure, a permission reminder method is provided, including:

[0006] In response to a transaction request of a target user for a target service, verifying the transaction authority of the target user according to target request information in the transaction request, and outputting a first verification result, wherein the target request information includes user identification information of the target user and service identification information of the target service;

[0007] If the first verification result indicates that the target user does not have the transaction authority for the target service, the target request information is sent to the message queue platform, wherein the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform;

[0008] When the sorting identification number is less than or equal to a preset threshold, generating permission reminder information according to the target request information in the message queue platform;

[0009] Sending the permission reminder information to an information sending queue, wherein the information sending queue includes a plurality of permission reminder information, and the content of each permission reminder information is different;

[0010] Each of the above-mentioned permission reminder information in the above-mentioned information sending queue is sent in sequence according to the information sending frequency, wherein the above-mentioned information sending frequency is determined according to the current limiting algorithm.

[0011] According to an embodiment of the present disclosure, the method further includes:

[0012] In the case where the permission reminder information is sent successfully, generating a permission reminder information sending record corresponding to the target request information;

[0013] The above permission reminder information sending record is stored in a database so as to perform data query based on the above database.

[0014] According to an embodiment of the present disclosure, the method further includes:

[0015] Verify the sending record of the permission reminder information based on the target request information, and output a second verification result;

[0016] When the second verification result indicates that there is no sending record of the permission reminder information corresponding to the target request information in the sending record, the transaction permission of the target user is verified according to the target request information in the transaction request, and the first verification result is output.

[0017] According to an embodiment of the present disclosure, when the sorting identification number is less than a preset threshold, generating permission reminder information according to the target request information in the message queue platform includes:

[0018] When the sorting identification number is less than a preset threshold, obtaining the user identification information and the service identification information in the message queue;

[0019] Determine the recipient information of the permission reminder information according to the service identification information;

[0020] The permission reminder information is generated according to the user identification information, the service identification information and the recipient information.

[0021] According to an embodiment of the present disclosure, the above-mentioned sorting identification number is generated by the above-mentioned message queue platform according to the following method:

[0022] Obtaining the number of request messages obtained within a preset time period through the message queue platform;

[0023] Based on the number of request information within the preset time period, the sort identification number corresponding to the target request information is determined.

[0024] According to an embodiment of the present disclosure, the above permission reminder method is applied to an open platform.

[0025] A second aspect of an embodiment of the present disclosure provides a permission reminder device, including:

[0026] a response module, configured to respond to a transaction request of a target user for a target service, verify the transaction authority of the target user according to target request information in the transaction request, and output a first verification result, wherein the target request information includes user identification information of the target user and service identification information of the target service;

[0027] A first sending module is used to send the target request information to the message queue platform when the first verification result indicates that the target user does not have the transaction authority of the target service, wherein the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform;

[0028] The first generating module is used to generate permission reminder information according to the target request information in the message queue platform when the sorting identification number is less than or equal to a preset threshold:

[0029] A second sending module is used to send the permission reminder information to an information sending queue, wherein the information sending queue includes a plurality of permission reminder information, and the content of each permission reminder information is different;

[0030] The third sending module is used to send each of the above-mentioned permission reminder information in the above-mentioned information sending queue in sequence according to the information sending frequency, wherein the above-mentioned information sending frequency is determined according to the current limiting algorithm.

[0031] A third aspect of an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned permission reminder method.

[0032] A fourth aspect of the embodiments of the present disclosure further provides a computer-readable storage medium on which executable instructions are stored, and when the instructions are executed by a processor, the processor executes the above-mentioned permission reminder method.

[0033] A fifth aspect of the embodiments of the present disclosure further provides a computer program product, including a computer program, which implements the above-mentioned permission reminder method when executed by a processor.

[0034] According to an embodiment of the present disclosure, when the verification result indicates that the target user does not have the transaction authority for the target service, the target request information is sent to the message queue platform, and a sorting identification number corresponding to the target request information is generated by the message queue platform. When the sorting identification number is less than or equal to the preset threshold, permission reminder information is generated according to the target request information in the message queue platform, and the permission reminder information is sent to the information sending queue, so that each permission reminder information in the information sending queue is sent in sequence according to the information sending frequency. By detecting the sorting identification number of the target request information, the problem of exceeding the maximum number of email sending times within a certain period of time can be avoided. By setting the information sending frequency, the problem of too high a frequency of sending permission reminder information, which causes the loss of permission reminder information, can be avoided, thereby increasing the probability of successful sending of permission reminder information and improving system security. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0036] Figure 1 The application scenario diagram of the permission reminder method according to an embodiment of the present disclosure is schematically shown.

[0037] Figure 2 The following schematically shows a flowchart of a permission reminder method according to an embodiment of the present disclosure.

[0038] Figure 3 The flowchart of the method for generating permission reminder information according to an embodiment of the present disclosure is schematically shown.

[0039] Figure 4 A flowchart of a permission reminder method according to another embodiment of the present disclosure is schematically output.

[0040] Figure 5 The structural block diagram of the permission reminder device according to an embodiment of the present disclosure is schematically shown.

[0041] Figure 6 A block diagram of an electronic device suitable for implementing a permission reminder method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0042] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0043] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0044] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0045] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0046] In the Internet era, the act of packaging website services into a series of computer-readable data interfaces and opening them up for use by third-party developers is called Open API. The platform that provides open API (application programming interface) is itself called an open platform. Through the open platform, websites can not only provide simple access to web pages, but also conduct complex data interactions, converting their web sites into development platforms equivalent to operating systems. Third-party developers can develop a variety of applications based on these existing, public web sites.

[0047] The open platform will control transactions initiated by each third party, and will send email alerts for transactions without transaction permissions. When the transaction volume is large in a short period of time, the demand for email sending is large, resulting in email sending failures and information loss, and the system security is low.

[0048] An embodiment of the present disclosure provides a permission reminder method, comprising: responding to a transaction request of a target user for a target service, verifying the transaction permission of the target user according to target request information in the transaction request, and outputting a first verification result, wherein the target request information includes user identification information of the target user and service identification information of the target service; when the first verification result indicates that the target user does not have the transaction permission of the target service, sending the target request information to a message queue platform, wherein the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform; when the sorting identification number is less than or equal to a preset threshold, generating permission reminder information according to the target request information in the message queue platform; sending the permission reminder information to an information sending queue, wherein the information sending queue includes multiple permission reminder messages, and the content of each permission reminder message is different; sending each permission reminder message in the information sending queue in sequence according to the information sending frequency, wherein the information sending frequency is determined according to a current limiting algorithm.

[0049] Figure 1 The application scenario diagram of the permission reminder method according to an embodiment of the present disclosure is schematically shown.

[0050] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a network, a terminal device and a server. The network 104 is used to provide a medium for a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0051] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0052] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0053] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0054] It should be noted that the permission reminder method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the permission reminder device provided in the embodiment of the present disclosure can generally be set in the server 105. The permission reminder method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the permission reminder device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0055] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0056] The following will be based on Figure 1 The scene described by Figure 2 to Figure 4 The permission reminder method of the disclosed embodiment is described in detail.

[0057] Figure 2 The following schematically shows a flowchart of a permission reminder method according to an embodiment of the present disclosure.

[0058] like Figure 2 As shown, the permission reminder method of this embodiment includes operations S201 to S205, and the transaction processing method can be executed by a terminal device or a server.

[0059] In operation S201, in response to a transaction request of a target user for a target service, the transaction authority of the target user is verified according to target request information in the transaction request, and a first verification result is output, wherein the target request information includes user identification information of the target user and service identification information of the target service.

[0060] According to an embodiment of the present disclosure, the permission reminder method can be applied to an open platform, for example, and the open platform can include an open bank, etc. Target users can include, for example, enterprise users or individual users who have cooperation rights with the open platform, etc. Target services can include, for example, service functions that the open platform provides to third-party users, etc. For example, the target services can include service functions such as information query and bill installment.

[0061] According to an embodiment of the present disclosure, the user identification information may include, for example, a user identification number or a user name corresponding to each target user, etc. The service identification information may include, for example, a service identification number or a service name corresponding to each target service, etc.

[0062] According to an embodiment of the present disclosure, the transaction authority of the target user can be verified according to the target request information in the transaction request, for example, by verifying the user identification information of the target user and the service identification information of the target service, and verifying whether there is an authorization relationship between the user identification information of the target user and the service identification information of the target service. For example, an authorization list can be stored in the storage system of the open platform, and the authorization list includes the authorization relationship between the user identification information of multiple users and the service identification information of multiple services. The authorization relationship between the target user and the target service can be determined through the authorization list.

[0063] In operation S202, when the first verification result indicates that the target user does not have transaction authority for the target service, the target request information is sent to the message queue platform, wherein the target request information corresponds to a sorting identification number generated by the message queue platform.

[0064] According to an embodiment of the present disclosure, when the first verification result indicates that the target user does not have transaction authority for the target service, it indicates that a permission reminder is required for the transaction.

[0065] According to an embodiment of the present disclosure, the message queue platform may include, for example, Apache Kafka (a high-throughput distributed publish-subscribe message system), etc. The message queue platform may include, for example, labeling each target request information to generate a sorting identification number corresponding to each target request information to determine the quantity information of the target request information in the message queue.

[0066] In operation S203, when the sort identification number is less than or equal to the preset threshold, permission reminder information is generated according to the target request information in the message queue platform.

[0067] According to an embodiment of the present disclosure, the preset threshold may include, for example, an upper limit on the number of emails sent within a preset time period of the mailbox. The preset time period may be set according to specific needs, for example, 24 hours, 48 ​​hours, etc.

[0068] According to an embodiment of the present disclosure, the permission reminder information may include, for example, emails, text messages, phone calls, etc. The embodiment of the present disclosure does not specifically limit the type of the permission reminder information.

[0069] In this embodiment, taking the permission reminder information as an email as an example, the mailbox system has restrictions on the frequency of information transmission and the number of emails sent. By the sort identification number of the request information in the message queue, it can be determined whether the current target request information exceeds the upper limit of the mailbox sending number.

[0070] In operation S204, the permission reminder information is sent to an information sending queue, wherein the information sending queue includes a plurality of permission reminder information, and the content of each permission reminder information is different.

[0071] According to an embodiment of the present disclosure, the information sending queue may include, for example, a plurality of permission reminder information.

[0072] In operation S205, each permission reminder message in the information sending queue is sent in sequence according to the information sending frequency, wherein the information sending frequency is determined according to a current limiting algorithm.

[0073] According to an embodiment of the present disclosure, the information sending queue can, for example, send each permission reminder message in sequence according to the leaky bucket algorithm. Further, taking the permission reminder message as an email as an example, the capacity of the leaky bucket is the maximum number of emails sent within a preset time period of the mailbox, and the leaky bucket drip rate is the number of emails sent per minute by the mailbox. When there is permission reminder information in the leaky bucket, the email can be sent according to the leaky bucket drip rate.

[0074] According to the embodiments of the present disclosure, when the verification result indicates that the target user does not have the transaction authority for the target service, the target request information is sent to the message queue platform, and a sorting identification number corresponding to the target request information is generated by the message queue platform. When the sorting identification number is less than or equal to the preset threshold, permission reminder information is generated according to the target request information in the message queue platform, and the permission reminder information is sent to the information sending queue, so that each permission reminder information in the information sending queue is sent in sequence according to the information sending frequency. Taking the permission reminder information as an email as an example, by detecting the sorting identification number of the target request information, the problem of exceeding the maximum number of email sending times within a certain period of time can be avoided. By setting the information sending frequency, the problem of excessive email sending frequency causing email loss can be avoided, thereby increasing the probability of successful email sending and improving system security.

[0075] According to an embodiment of the present disclosure, the permission reminder method further includes:

[0076] When the permission reminder information is sent successfully, a permission reminder information sending record corresponding to the target request information is generated and the permission reminder information sending record is stored in a database so as to perform data query based on the database.

[0077] According to an embodiment of the present disclosure, the permission reminder information sending record may include, for example, the permission reminder information identifier, which may include an email identifier, a text message identifier, a phone identifier, etc. The email identifier may include, for example, the subject name of the email, the sending time, etc. Each email identifier corresponds to a target request information.

[0078] According to an embodiment of the present disclosure, the email identifier may also be stored in Redis (Remote Dictionary Server, remote dictionary service), for example.

[0079] According to an embodiment of the present disclosure, the permission reminder method further includes:

[0080] The sending record of the permission reminder information is verified based on the target request information, and a second verification result is output. If the second verification result indicates that there is no sending record of the permission reminder information corresponding to the target request information in the sending record, the transaction authority of the target user is verified according to the target request information in the transaction request, and a first verification result is output.

[0081] According to an embodiment of the present disclosure, it is determined whether there is an email identifier corresponding to the target request information based on the user identifier information of the target user and the service identifier information of the target service in the target request information. If there is an email identifier corresponding to the target request information, it indicates that the permission reminder information has been sent for the target request information, otherwise it indicates that the permission reminder information has not been sent for the target request information.

[0082] According to the embodiments of the present disclosure, the sending record of the permission reminder information is verified based on the target request information to determine whether the permission reminder information has been sent for the target request information, thereby avoiding repeated sending of reminder emails and wasting of system resources.

[0083] Figure 3 The flowchart of the method for generating permission reminder information according to an embodiment of the present disclosure is schematically shown.

[0084] like Figure 3 As shown, the method for generating permission reminder information includes operations S301 to S303.

[0085] In operation S301, when the sort identification number is less than a preset threshold, user identification information and service identification information are obtained in the message queue.

[0086] In operation S302, the recipient information of the permission reminder information is determined according to the service identification information.

[0087] In operation S303, permission reminder information is generated according to the user identification information, the service identification information and the recipient information.

[0088] According to an embodiment of the present disclosure, when the sort identification number is less than a preset threshold, it indicates that the number of permission reminder messages sent within the preset time period does not exceed the upper limit of the number of emails sent by the mailbox, and the permission reminder messages corresponding to the target request information can continue to be sent.

[0089] According to an embodiment of the present disclosure, each target service corresponds to a receiver, and the receivers of different target services may be the same or different. The receiver information may include, for example, the receiver's email address.

[0090] According to the embodiments of the present disclosure, taking the permission reminder information as an email as an example, the body content of the permission reminder email can be generated according to the user identification information and the service identification information, and the recipient information of the permission reminder email can be generated according to the recipient information. Furthermore, the body content of the permission reminder email can also include any other content, such as remarks information, etc. The embodiments of the present disclosure do not limit the specific body content of the permission reminder email.

[0091] According to an embodiment of the present disclosure, the sort identification number is generated by the message queue platform according to the following method:

[0092] The number of request information obtained within a preset time period is obtained through the message queue platform. Based on the number of request information within the preset time period, a sorting identification number corresponding to the target request information is determined.

[0093] According to an embodiment of the present disclosure, the preset time period can be determined, for example, according to the reset time of the upper limit of email sending of the mailbox, for example, including 24 hours, 48 ​​hours, etc. Further, the preset time period can also be determined, for example, according to the upper limit of SMS sending or the upper limit of phone calls.

[0094] Figure 4 A flowchart of a permission reminder method according to another embodiment of the present disclosure is schematically output.

[0095] like Figure 4 As shown, a third-party customer initiates a transaction request to the open platform, and the open platform determines whether the third-party customer has transaction authority. If the third-party customer has transaction authority, the third-party customer is allowed to conduct the transaction, and the authority reminder process ends. If the third-party customer does not have transaction authority, it is determined whether a reminder message has been sent for the transaction on the same day.

[0096] If a reminder message has been sent for the transaction on the same day, the permission reminder process ends. If no reminder message has been sent for the transaction on the same day, the transaction request is sent to the Kafka message queue.

[0097] Determine whether the number of transaction requests on the day is greater than the maximum number of times the mailbox can send each day. If the number of transaction requests on the day is greater than the maximum number of times the mailbox can send each day, end the permission reminder process. If the number of transaction requests on the day is less than or equal to the maximum number of times the mailbox can send each day, read the transaction request information from the Kafka message queue and generate permission reminder information based on the transaction request information.

[0098] The permission reminder information is sent to the leaky bucket so that the permission reminder information can be sent based on the preset sending frequency. Furthermore, the capacity of the leaky bucket is the maximum number of emails sent within the preset time period of the mailbox, and the leaky bucket drip rate is the number of emails sent per minute by the mailbox. When there is permission reminder information in the leaky bucket, emails can be sent according to the leaky bucket drip rate.

[0099] Based on the above permission reminder method, the present disclosure also provides a permission reminder device 500. Figure 5 The device is described in detail.

[0100] Figure 5 The structure block diagram of the permission reminder device 500 according to the embodiment of the present disclosure is schematically shown.

[0101] like Figure 5 As shown, the permission reminder device 500 of this embodiment includes a response module 501 , a first sending module 502 , a first generating module 503 , a second sending module 504 and a third sending module 505 .

[0102] The response module 501 is used to respond to the target user's transaction request for the target service, verify the target user's transaction authority according to the target request information in the transaction request, and output a first verification result, wherein the target request information includes the user identification information of the target user and the service identification information of the target service. In one embodiment, the response module 501 can be used to perform the operation S201 described above, which will not be repeated here.

[0103] The first sending module 502 is used to send the target request information to the message queue platform when the first verification result indicates that the target user does not have the transaction authority of the target service, wherein the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform. In one embodiment, the first sending module 502 can be used to perform the operation S202 described above, which will not be repeated here.

[0104] The first generating module 503 is used to generate permission reminder information according to the target request information in the message queue platform when the sorting identification number is less than or equal to the preset threshold. In one embodiment, the first generating module 503 can be used to perform the operation S203 described above, which will not be repeated here.

[0105] The second sending module 504 is used to send the permission reminder information to the information sending queue, wherein the information sending queue includes multiple permission reminder information, and the content of each permission reminder information is different. In one embodiment, the second sending module 504 can be used to perform the operation S204 described above, which will not be repeated here.

[0106] The third sending module 505 is used to send each permission reminder message in the information sending queue in sequence according to the information sending frequency, wherein the information sending frequency is determined according to the current limiting algorithm. In one embodiment, the third sending module 505 can be used to perform the operation S205 described above, which will not be repeated here.

[0107] According to an embodiment of the present disclosure, when the verification result indicates that the target user does not have the transaction authority for the target service, the target request information is sent to the message queue platform, and a sorting identification number corresponding to the target request information is generated by the message queue platform. When the sorting identification number is less than or equal to the preset threshold, permission reminder information is generated according to the target request information in the message queue platform, and the permission reminder information is sent to the information sending queue, so that each permission reminder information in the information sending queue is sent in sequence according to the information sending frequency. By detecting the sorting identification number of the target request information, the problem of exceeding the maximum number of email sending times within a certain period of time can be avoided. By setting the information sending frequency, the problem of email loss caused by excessive email sending frequency can be avoided, thereby increasing the probability of successful email sending and improving system security.

[0108] According to an embodiment of the present disclosure, the permission reminder device 500 further includes a second generating module and a fourth sending module.

[0109] The second generating module is used to generate a permission reminder information sending record corresponding to the target request information when the permission reminder information is sent successfully.

[0110] The fourth sending module is used to store the permission reminder information sending record in the database so as to perform data query based on the database.

[0111] According to an embodiment of the present disclosure, the permission reminder device 500 further includes a first verification module and a second verification module.

[0112] The first verification module is used to verify the sending record of the permission reminder information based on the target request information and output a second verification result.

[0113] The second verification module is used to verify the transaction authority of the target user according to the target request information in the transaction request and output a first verification result when the second verification result indicates that there is no sending record of the authority reminder information corresponding to the target request information in the sending record.

[0114] According to an embodiment of the present disclosure, the first generating module 503 includes a first acquiring unit, a second determining unit and a generating unit.

[0115] The first acquisition unit is used to acquire user identification information and service identification information in the message queue when the sort identification number is less than a preset threshold.

[0116] The second determining unit is used to determine the recipient information of the permission reminder information according to the service identification information.

[0117] The generating unit is used to generate permission reminder information according to the user identification information, the service identification information and the recipient information.

[0118] According to an embodiment of the present disclosure, the first sending module 502 includes a second acquiring unit and a second determining unit.

[0119] The second acquisition unit is used to acquire the quantity of request information acquired within a preset time period through the message queue platform.

[0120] The second determining unit is used to determine a sorting identification number corresponding to the target request information based on the number of request information within a preset time period.

[0121] According to an embodiment of the present disclosure, any multiple modules of the response module 501, the first sending module 502, the first generating module 503, the second sending module 504 and the third sending module 505 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the response module 501, the first sending module 502, the first generating module 503, the second sending module 504 and the third sending module 505 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation modes of software, hardware and firmware or in a proper combination of any of them. Alternatively, at least one of the response module 501, the first sending module 502, the first generating module 503, the second sending module 504 and the third sending module 505 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.

[0122] Figure 6 A block diagram of an electronic device suitable for implementing a permission reminder method according to an embodiment of the present disclosure is schematically shown.

[0123] like Figure 6As shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include an onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0124] In RAM 603, various programs and data required for the operation of electronic device 600 are stored. Processor 601, ROM 602 and RAM 603 are connected to each other via bus 604. Processor 601 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 602 and / or RAM 603. It should be noted that the program can also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0125] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the I / O interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage portion 608 as needed.

[0126] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0127] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk-ROM (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than ROM 602 and RAM 603.

[0128] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the item recommendation method provided by the embodiment of the present disclosure.

[0129] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 601. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0130] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0131] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, apparatus, module, unit, etc. described above can be implemented by a computer program module.

[0132] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0133] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0134] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0135] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A permission reminder method, comprising: In response to a transaction request of a target user for a target service, verifying the transaction authority of the target user according to target request information in the transaction request, and outputting a first verification result, wherein the target request information includes user identification information of the target user and service identification information of the target service; If the first verification result indicates that the target user does not have the transaction authority for the target service, the target request information is sent to the message queue platform, wherein the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform; In the case where the sorting identification number is less than or equal to a preset threshold, generating permission reminder information according to the target request information in the message queue platform includes: in the case where the sorting identification number is less than the preset threshold, obtaining the user identification information and the service identification information in the message queue platform; determining the recipient information of the permission reminder information according to the service identification information; generating the permission reminder information according to the user identification information, the service identification information and the recipient information, wherein the preset threshold represents the upper limit of the number of permission reminder messages sent within a preset time period, and the sorting identification number is used to determine whether the current target request information exceeds the upper limit of the number of sends, and each target service corresponds to a recipient; Sending the permission reminder information to an information sending queue, wherein the information sending queue includes a plurality of permission reminder information, and the content of each permission reminder information is different; Sending each permission reminder message in the information sending queue in sequence according to the information sending frequency, wherein the information sending frequency is determined according to a current limiting algorithm; Wherein, the method further comprises: In the case where the permission reminder information is sent successfully, generating a permission reminder information sending record corresponding to the target request information, wherein the permission reminder information sending record includes an identifier of the permission reminder information, and the identifier corresponds to the target request information; Verifying the sending record of the permission reminder information based on the target request information and outputting a second verification result; wherein, verifying the sending record of the permission reminder information based on the target request information includes: determining whether there is an identifier corresponding to the target request information according to the user identifier information of the target user and the service identifier information of the target service in the target request information; When the second verification result indicates that there is no sending record of permission reminder information corresponding to the target request information in the sending record, the transaction permission of the target user is verified according to the target request information in the transaction request, and the first verification result is output.

2. The method according to claim 1, further comprising: The permission reminder information sending record is stored in a database so as to perform data query based on the database.

3. The method according to claim 1, wherein: The sort identification number is generated by the message queue platform according to the following method: Obtaining the number of request messages obtained within a preset time period through the message queue platform; The sorting identification number corresponding to the target request information is determined based on the number of request information within the preset time period.

4. The method according to claim 1, wherein: The permission reminder method is applied to an open platform.

5. A permission reminder device, comprising: a response module, configured to respond to a transaction request of a target user for a target service, verify the transaction authority of the target user according to target request information in the transaction request, and output a first verification result, wherein the target request information includes user identification information of the target user and service identification information of the target service; A first sending module, configured to send the target request information to a message queue platform when the first verification result indicates that the target user does not have transaction authority for the target service, wherein the target request information corresponds to a sorting identification number generated by the message queue platform; A first generating module, configured to generate permission reminder information according to the target request information in the message queue platform when the sorting identification number is less than or equal to a preset threshold, wherein the preset threshold represents an upper limit on the number of permission reminder information sent within a preset time period, and the sorting identification number is used to determine whether the current target request information exceeds the upper limit on the number of sending; Wherein, the first generation module includes: A first acquisition unit, configured to acquire the user identification information and the service identification information in the message queue platform when the sort identification number is less than a preset threshold; A second determining unit, configured to determine the recipient information of the permission reminder information according to the service identification information, wherein each target service corresponds to a recipient; A generating unit, configured to generate the permission reminder information according to the user identification information, the service identification information and the recipient information; A second sending module, configured to send the permission reminder information to an information sending queue, wherein the information sending queue includes a plurality of permission reminder information, each of which has different content; A third sending module, configured to sequentially send each permission reminder message in the information sending queue according to an information sending frequency, wherein the information sending frequency is determined according to a current limiting algorithm; Wherein, the device further comprises: A second generating module is used to generate a permission reminder information sending record corresponding to the target request information when the permission reminder information is sent successfully, wherein the permission reminder information sending record includes an identifier of the permission reminder information, and the identifier corresponds to the target request information; A first verification module is configured to verify the sending record of the permission reminder information based on the target request information and output a second verification result; wherein the verifying the sending record of the permission reminder information based on the target request information includes: determining whether there is an identifier corresponding to the target request information according to the user identifier information of the target user and the service identifier information of the target service in the target request information; A second verification module is used to verify the transaction authority of the target user according to the target request information in the transaction request, and output the first verification result when the second verification result indicates that there is no sending record of the authority reminder information corresponding to the target request information in the sending record.

6. An electronic device comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 4.

7. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 4.

8. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images