CN114049208A - Permission reminding method, device, equipment and storage medium - Google Patents

Permission reminding method, device, equipment and storage medium Download PDF

Info

Publication number
CN114049208A
CN114049208A CN202111335913.5A CN202111335913A CN114049208A CN 114049208 A CN114049208 A CN 114049208A CN 202111335913 A CN202111335913 A CN 202111335913A CN 114049208 A CN114049208 A CN 114049208A
Authority
CN
China
Prior art keywords
information
target
sending
authority
permission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111335913.5A
Other languages
Chinese (zh)
Inventor
邓宗武
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
Original Assignee
China Construction Bank Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp filed Critical China Construction Bank Corp
Priority to CN202111335913.5A priority Critical patent/CN114049208A/en
Publication of CN114049208A publication Critical patent/CN114049208A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/546Message passing systems or structures, e.g. queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • Software Systems (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the disclosure provides an authority reminding method, which can be applied to the financial field and the technical field of resource scheduling. The permission reminding method comprises the following steps: responding 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; under the condition that the first verification result represents that the target user does not have the transaction authority of the target service, target request information is sent to a message queue platform; under the condition that the sequencing identification number is smaller than or equal to a preset threshold value, generating permission reminding information according to target request information in the message queue platform; sending the permission reminding information to an information sending queue; and sequentially transmitting each authority prompting message in the message transmission queue according to the message transmission frequency, wherein the message transmission frequency is determined according to a current limiting algorithm. The embodiment of the disclosure also provides an authority reminding device, equipment, a storage medium and a program product.

Description

Permission reminding method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of finance and resource scheduling technologies, and more particularly, to a method, an apparatus, a device, a medium, and a program product for right reminding.
Background
The open platform needs to perform cooperative service mode management and control on the approved third-party product service mode, and needs to perform mail warning on the transaction without transaction authority.
In carrying out the inventive concept of the present disclosure, the inventors found that the following problems exist in the related art: in the related art, under the condition that the transaction amount in a short time is large, the mail sending requirement is large, the problems of mail sending failure and information loss are caused, and the system safety is low.
Disclosure of Invention
In view of the foregoing, embodiments of the present disclosure provide a method, an apparatus, a device, a medium, and a program product for rights reminding.
According to a first aspect of the embodiments of the present disclosure, there is provided a permission reminding method, including:
responding 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 comprises user identification information of the target user and service identification information of the target service;
under the condition that the first verification result represents that the target user does not have the transaction authority of the target service, the target request information is sent to a message queue platform, wherein the target request information corresponds to a sequencing identification number, and the sequencing identification number is generated by the message queue platform;
under the condition that the sequencing identification number is smaller than or equal to a preset threshold value, generating permission reminding information according to the target request information in the message queue platform;
sending the authority prompting information to an information sending queue, wherein the information sending queue comprises a plurality of authority prompting information, and the content of each authority prompting information is different;
and sequentially transmitting each authority prompting message in the message transmission queue according to a message transmission frequency, wherein the message transmission frequency is determined according to a current limiting algorithm.
According to an embodiment of the disclosure, the method further comprises:
generating an authority prompting information sending record corresponding to the target request information under the condition that the authority prompting information is sent successfully;
and storing the permission reminding information sending record in a database so as to carry out data query based on the database.
According to an embodiment of the disclosure, the method further comprises:
verifying the sending record of the authority prompting information based on the target request information, and outputting a second verification result;
and if the second check result represents that the sending record does not have the sending record of the authority reminding information corresponding to the target request information, checking the transaction authority of the target user according to the target request information in the transaction request, and outputting the first check result.
According to an embodiment of the present disclosure, the generating of the permission alert information according to the target request information in the message queue platform when the sorting identifier is smaller than a preset threshold includes:
under the condition that the sequencing identification number is smaller than a preset threshold value, acquiring the user identification information and the service identification information from the message queue;
determining receiver information of the authority prompting information according to the service identification information;
and generating the authority reminding information according to the user identification information, the service identification information and the receiver information.
According to an embodiment of the present disclosure, the above-mentioned sequencing identification number is generated by the above-mentioned message queue platform according to the following method:
acquiring the quantity of acquired request information in a preset time period through the message queue platform;
and determining the sorting identification number corresponding to the target request information based on the quantity of the request information in the preset time period.
According to the embodiment of the disclosure, the permission reminding method is applied to an open platform.
A second aspect of the embodiments of the present disclosure provides an authority reminding device, including:
a response module, configured to respond to a transaction request of a target user for a target service, verify a transaction right of the target user according to target request information in the transaction request, and output a first verification result, where 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 check result indicates that the target user does not have the transaction permission of the target service, where the target request information corresponds to a sorting identifier, and the sorting identifier is generated by the message queue platform;
a first generating module, configured to generate, when the sorting identifier is smaller than or equal to a preset threshold, an authority reminding message according to the target request message in the message queue platform:
the second sending module is used for sending the authority prompting information to an information sending queue, wherein the information sending queue comprises a plurality of authority prompting information, and the content of each authority prompting information is different;
and the third sending module is used for sequentially sending each permission reminding message in the message sending queue according to a message sending frequency, wherein the message sending frequency is determined according to a current limiting algorithm.
A third aspect of the embodiments of the present disclosure provides an electronic device, including: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the above-described privilege alert method.
The fourth aspect of the embodiments of the present disclosure also provides a computer-readable storage medium, on which executable instructions are stored, and when executed by a processor, the instructions cause the processor to execute the above-mentioned permission reminding method.
A fifth aspect of the embodiments of the present disclosure further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the above permission reminding method.
According to the embodiment of the disclosure, under the condition that the verification result represents that the target user has no transaction authority of the target service, the target request information is sent to the message queue platform, the message queue platform generates a sequencing identification number corresponding to the target request information, under the condition that the sequencing identification number is smaller than or equal to a preset threshold value, authority reminding information is generated according to the target request information in the message queue platform, and the authority reminding information is sent to the information sending queue, so that each authority reminding information in the information sending queue is sent in sequence according to the information sending frequency. The problem that the number of times of sending the mails is exceeded within a certain time can be avoided by detecting the sequencing identification number of the target request information, the problem that the authority reminding information is lost due to overhigh frequency of sending the authority reminding information can be avoided by setting the information sending frequency, the probability of successful sending of the authority reminding information is improved, and the system safety is improved.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:
fig. 1 schematically shows an application scenario diagram of a permission reminding method according to an embodiment of the present disclosure.
Fig. 2 schematically shows a flowchart of a permission reminding method according to an embodiment of the disclosure.
Fig. 3 schematically shows a flowchart of a method for generating permission reminder information according to an embodiment of the present disclosure.
Fig. 4 schematically outputs a flowchart of a permission reminding method according to another embodiment of the disclosure.
Fig. 5 schematically shows a block diagram of a permission reminding device according to an embodiment of the disclosure.
Fig. 6 schematically shows a block diagram of an electronic device adapted to implement a method of rights alerting, according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In the internet era, services of websites are packaged into a series of computer-recognizable data interfaces which are opened for third-party developers to use, the behavior is called Open API, and a platform providing Open API (application programming interface) is called Open platform. Through the open platform, the website can not only provide simple access to the Web page, but also perform complex data interaction, and convert the Web websites into a development platform equivalent to an operating system. Third party developers can develop a rich variety of applications based on these already existing, open Web sites.
The open platform can manage and control the transaction initiated by each third party, and the mail alarm is needed for the transaction without transaction authority. Under the condition of large transaction amount in a short time, the mail sending requirement is high, the problems of mail sending failure and information loss are caused, and the system safety is low.
The embodiment of the disclosure provides a permission reminding method, which includes: responding 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 comprises user identification information of the target user and service identification information of the target service; under the condition that the first verification result represents that the target user does not have the transaction authority of the target service, target request information is sent to a message queue platform, wherein the target request information corresponds to a sequencing identification number, and the sequencing identification number is generated by the message queue platform; under the condition that the sequencing identification number is smaller than or equal to a preset threshold value, generating permission reminding information according to target request information in the message queue platform; sending the authority prompting information to an information sending queue, wherein the information sending queue comprises a plurality of authority prompting information, and the content of each authority prompting information is different; and sequentially transmitting each authority prompting message in the message transmission queue according to the message transmission frequency, wherein the message transmission frequency is determined according to a current limiting algorithm.
Fig. 1 schematically shows an application scenario diagram of a permission reminding method according to an embodiment of the present disclosure.
As shown in fig. 1, the application scenario 100 according to this embodiment may include a network, a terminal device, and a server. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the permission reminding method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the permission reminding device provided by the embodiment of the present disclosure may be generally disposed in the server 105. The permission reminding method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the permission reminding device provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
The permission reminding method of the disclosed embodiment will be described in detail through fig. 2 to fig. 4 based on the scenario described in fig. 1.
Fig. 2 schematically shows a flowchart of a permission reminding method according to an embodiment of the disclosure.
As shown in fig. 2, the authority reminding method of the embodiment includes operations S201 to S205, and the transaction processing method may be executed by a terminal device or a server.
In operation S201, in response to a transaction request of a target user for a target service, verifying a transaction right of the target user according to target request information in the transaction request, and outputting a first verification result, where the target request information includes user identification information of the target user and service identification information of the target service.
According to the embodiment of the disclosure, the permission reminding method can be applied to an open platform, for example, the open platform can include an open bank and the like. The target users may include, for example, enterprise users or individual users that have collaborative rights with the open platform, and the like. The target service may include, for example, a service function that the opening platform opens to a third-party user, and the like.
According to an embodiment of the present disclosure, the user identification information may include, for example, a user identification number or a user name, etc. corresponding to each target user. The service identification information may include, for example, a service identification number or a service name, etc., corresponding to each target service.
According to the embodiment of the present disclosure, verifying the transaction right of the target user according to the target request information in the transaction request may be, for example, verifying user identification information of the target user and service identification information of the target service, and verifying whether an authorization relationship exists between the user identification information of the target user and the service identification information of the target service. For example, an authorization list may be stored in the storage system of the open platform, where the authorization list includes authorization relationships between user identification information of multiple users and service identification information of multiple services, and the authorization relationship between a target user and a target service may be determined through the authorization list.
In operation S202, under the condition that the first verification result indicates that the target user does not have the transaction authority of the target service, the target request information is sent to the message queue platform, where the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform.
According to the embodiment of the disclosure, when the first verification result represents that the target user does not have the transaction authority of the target service, it indicates that the authority reminding needs to be performed on the transaction.
According to embodiments of the present disclosure, the message queue platform may include, for example, Apache Kafka (a high-throughput distributed publish-subscribe messaging system), and the like. The message queue platform may include, for example, a label for each target request message. To generate an ordering identification number corresponding to each target request message to determine the quantity information of the target request messages in the message queue.
In operation S203, under the condition that the sorting identification number is less than or equal to the preset threshold, permission reminding information is generated according to the target request information in the message queue platform.
According to the embodiment of the present disclosure, the preset threshold may include, for example, an upper limit of the number of sent mails in a preset time period of the mailbox. The preset time period may be set according to specific needs, and may include 24 hours, 48 hours, and the like, for example.
According to the embodiment of the disclosure, the permission reminding information may include, for example, a mail, a short message, a telephone, and the like, and the type of the permission reminding information is not specifically limited in the embodiment of the disclosure.
In this embodiment, for example, the permission reminding information is used as the mail, and the mailbox system has limitations on information sending frequency and mail sending number. Through the sequencing identification number of the request information in the message queue, whether the current target request information exceeds the upper limit of the mailbox sending quantity can be judged.
In operation S204, the permission reminder information is sent to an information sending queue, where the information sending queue includes a plurality of permission reminder information, and each permission reminder information has different content.
According to an embodiment of the present disclosure, the information transmission queue may include, for example, a plurality of authority reminder information.
In operation S205, each permission reminder in the information transmission queue is sequentially transmitted according to an information transmission frequency, where the information transmission frequency is determined according to a current limiting algorithm.
According to the embodiment of the disclosure, the information sending queue can send each authority reminding information in sequence according to a leaky bucket algorithm, for example. Furthermore, taking the authority reminding information as the mail as an example, the capacity of the leaky bucket is the highest sending times of the mail in a preset time period of the mailbox, the dripping rate of the leaky bucket is the number of the mailboxes sent by the mailbox every minute, and when the authority reminding information exists in the leaky bucket, the mail can be sent according to the dripping rate of the leaky bucket.
According to the embodiment of the disclosure, under the condition that the verification result represents that the target user has no transaction authority of the target service, the target request information is sent to the message queue platform, the message queue platform generates a sequencing identification number corresponding to the target request information, under the condition that the sequencing identification number is smaller than or equal to a preset threshold value, authority reminding information is generated according to the target request information in the message queue platform, and the authority reminding information is sent to the information sending queue, so that each authority reminding information in the information sending queue is sent in sequence according to the information sending frequency. By taking the authority prompting information as the mail, the problem that the maximum sending times of the mail is exceeded within a certain time can be avoided by detecting the sequencing identification number of the target request information, and the problem that the mail is lost due to overhigh sending frequency of the mail can be avoided by setting the information sending frequency, so that the probability of successful sending of the mail is improved, and the system safety is improved.
According to the embodiment of the disclosure, the permission reminding method further comprises:
and under the condition that the permission reminding information is successfully sent, generating a permission reminding information sending record corresponding to the target request information. And storing the permission reminding information sending record in a database so as to perform data query based on the database.
According to the embodiment of the disclosure, the permission reminding information sending record may include, for example, an identifier of the permission reminding information, where the identifier may include a mail identifier, a short message indication, a telephone identifier, and the like, and the mail identifier may include, for example, a subject name, a sending time, and the like of the mail. Each mail identification corresponds to one target request message.
According to an embodiment of the present disclosure, the mail identification may also be stored in, for example, a Remote Dictionary service (Redis Server).
According to the embodiment of the disclosure, the permission reminding method further comprises:
and checking the sending record of the permission reminding information based on the target request information, and outputting a second checking result. And under the condition that the second verification result represents that the sending record does not have the permission reminding information corresponding to the target request information, verifying the transaction permission of the target user according to the target request information in the transaction request, and outputting a first verification result.
According to the embodiment of the disclosure, whether the mail identification corresponding to the target request information exists is determined according to the user identification information of the target user and the service identification information of the target service in the target request information. And under the condition that the mail identification corresponding to the target request information exists, representing that the authority prompting information has already been sent aiming at the target request information, otherwise, representing that the authority prompting information has not been sent aiming at the target request information.
According to the embodiment of the disclosure, the sending record of the permission reminding information is checked based on the target request information, and whether the permission reminding information is sent aiming at the target request information can be determined. The repeated sending of the reminding mails and the waste of system resources can be avoided.
Fig. 3 schematically shows a flowchart of a method for generating permission reminder information according to an embodiment of the present disclosure.
As shown in fig. 3, the method for generating the authority prompting information includes operations S301 to S303.
In operation S301, in the case that the sequence identification number is smaller than the preset threshold, user identification information and service identification information are acquired in the message queue.
In operation S302, receiver information of the authority reminder information is determined according to the service identification information.
In operation S303, authority reminding information is generated according to the user identification information, the service identification information, and the recipient information.
According to the embodiment of the disclosure, when the sequencing identification number is smaller than the preset threshold, the sending number of the permission reminding information in the preset time period is represented not to exceed the upper limit of the sending number of the mails of the mailbox, and the permission reminding information corresponding to the target request information can be continuously sent.
According to the embodiment of the disclosure, each target service corresponds to a receiver, and the receivers of different target services may be the same or different. The recipient information may include, for example, an email address of the recipient, etc.
According to the embodiment of the disclosure, the permission reminding information is taken as an example of the mail, for example, the text content of the permission reminding mail can be generated according to the user identification information and the service identification information, and the receiving information of the permission reminding mail can be generated according to the receiver information. Further, the text content of the permission reminding mail may also include other arbitrary contents, such as remark information, and the specific text content of the permission reminding mail is not limited in the embodiment of the disclosure.
According to an embodiment of the present disclosure, the sequencing identification number is generated by the message queue platform according to the following method:
and acquiring the quantity of the acquired request information in a preset time period through the message queue platform. And determining the sequencing identification number corresponding to the target request information based on the quantity of the request information in the preset time period.
According to the embodiment of the present disclosure, the preset time period may be determined according to a reset time of a mail sending upper limit of the mailbox, for example, and may include 24 hours, 48 hours, and the like. Further, the preset time period may also be determined according to an upper limit of sending a short message or an upper limit of dialing a telephone call, for example.
Fig. 4 schematically outputs a flowchart of a permission reminding method according to another embodiment of the disclosure.
As shown in fig. 4, a transaction request is sent to the open platform by a third party client, and the open platform determines whether the third party client has a transaction right. And under the condition that the third-party client has the transaction authority, the third-party client is permitted to perform the transaction, and the authority reminding process is ended. And under the condition that the third party does not have the transaction authority, judging whether reminding information is sent for the transaction on the same day.
And ending the authority reminding flow under the condition that reminding information is sent for the transaction on the same day. In the event that no reminder has been sent for the transaction on the current day, a transaction request is sent to the kafka message queue.
And judging whether the quantity of the transaction requests in the day is greater than the maximum sending time limit of the mailbox every day, and finishing the permission reminding process under the condition that the quantity of the transaction requests in the day is greater than the maximum sending time limit. And under the condition that the number of the transaction requests in the day is less than or equal to the maximum sending times limit every day, reading the transaction request information from the kafka message queue, and generating authority reminding information according to the transaction request information.
And sending the permission reminding information to the leaky bucket so as to send the permission reminding information based on the preset sending frequency. Furthermore, the capacity of the leaky bucket is the highest sending times of the mails in a preset time period of the mailbox, the dripping speed of the leaky bucket is the number of the mailboxes sent by the mailbox per minute, and when authority reminding information exists in the leaky bucket, the mails can be sent according to the dripping speed of the leaky bucket.
Based on the permission reminding method, the disclosure also provides a permission reminding device 500. The apparatus will be described in detail below with reference to fig. 5.
Fig. 5 schematically shows a block diagram of a rights reminder 500 according to an embodiment of the disclosure.
As shown in fig. 5, the authority reminding apparatus 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.
The response module 501 is configured to, in response to a transaction request of a target user for a target service, verify a transaction right of the target user according to target request information in the transaction request, and output a first verification result, where the target request information includes user identification information of the target user and service identification information of the target service. In an embodiment, the response module 501 may be configured to perform the operation S201 described above, which is not described herein again.
The first sending module 502 is configured to send the target request information to the message queue platform when the first check result indicates that the target user does not have the transaction permission of the target service, where the target request information corresponds to a sorting identification number, and the sorting identification number is generated by the message queue platform. In an embodiment, the first sending module 502 may be configured to perform the operation S202 described above, which is not described herein again.
The first generating module 503 is configured to generate permission reminding information according to the target request information in the message queue platform when the sorting identification number is smaller than or equal to the preset threshold. In an embodiment, the first generating module 503 may be configured to perform the operation S203 described above, which is not described herein again.
The second sending module 504 is configured to send the permission reminding information to an information sending queue, where the information sending queue includes multiple permission reminding information, and the content of each permission reminding information is different. In an embodiment, the second sending module 504 may be configured to perform the operation S204 described above, which is not described herein again.
And a third sending module 505, configured to send each permission reminding message in the message sending queue in sequence according to a message sending frequency, where the message sending frequency is determined according to a current limiting algorithm. In an embodiment, the third sending module 505 may be configured to perform the operation S205 described above, which is not described herein again.
According to the embodiment of the disclosure, under the condition that the verification result represents that the target user has no transaction authority of the target service, the target request information is sent to the message queue platform, the message queue platform generates a sequencing identification number corresponding to the target request information, under the condition that the sequencing identification number is smaller than or equal to a preset threshold value, authority reminding information is generated according to the target request information in the message queue platform, and the authority reminding information is sent to the information sending queue, so that each authority reminding information in the information sending queue is sent in sequence according to the information sending frequency. The problem that the number of times of sending the mails is exceeded within a certain time can be avoided by detecting the sequencing identification number of the target request information, and the problem that the mails are lost due to overhigh frequency of sending the mails can be avoided by setting the information sending frequency, so that the probability of successful sending of the mails is improved, and the system safety is improved.
According to the embodiment of the present disclosure, the permission reminding apparatus 500 further includes a second generating module and a fourth sending module.
And the second generation module is used for generating the permission reminding information sending record corresponding to the target request information under the condition that the permission reminding information is sent successfully.
And the fourth sending module is used for storing the permission reminding information sending record in the database so as to carry out data query based on the database.
According to the embodiment of the present disclosure, the permission reminding apparatus 500 further includes a first check module and a second check module.
And the first checking module is used for checking the sending record of the permission reminding information based on the target request information and outputting a second checking result.
And the second checking module is used for checking the transaction authority of the target user according to the target request information in the transaction request and outputting a first checking result under the condition that the second checking result represents that the sending record of the authority prompting information corresponding to the target request information does not exist in the sending record.
According to an embodiment of the present disclosure, the first generating module 503 includes a first obtaining unit, a second determining unit, and a generating unit.
And the first acquisition unit is used for acquiring the user identification information and the service identification information in the message queue under the condition that the sequencing identification number is smaller than a preset threshold value.
And the second determining unit is used for determining receiver information of the permission reminding information according to the service identification information.
And the generating unit is used for generating the authority reminding information according to the user identification information, the service identification information and the receiver information.
According to an embodiment of the present disclosure, the first sending module 502 includes a second obtaining unit and a second determining unit.
And the second obtaining unit is used for obtaining the quantity of the obtained request information in the preset time period through the message queue platform.
And the second determining unit is used for determining the sorting identification number corresponding to the target request information based on the quantity of the request information in the preset time period.
According to the embodiment of the present disclosure, any plurality 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 combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the 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 may 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 may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or by a suitable combination of any several 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 when executed, may perform a corresponding function.
Fig. 6 schematically shows a block diagram of an electronic device adapted to implement a method of rights alerting, according to an embodiment of the present disclosure.
As shown in fig. 6, an 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 section 608 into a Random Access Memory (RAM) 603. Processor 601 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 601 may also include onboard memory for caching purposes. Processor 601 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.
In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 602 and/or RAM 603. It is to be noted that the programs may also be stored in one or more memories other than the ROM 602 and RAM 603. The processor 601 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
Electronic device 600 may also include input/output (I/O) interface 605, input/output (I/O) interface 605 also connected to bus 604, according to an embodiment of the disclosure. The electronic device 600 may also include one or more of the following components connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 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, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments 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 the ROM 602 and RAM 603.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the item recommendation method provided by the embodiment of the disclosure.
The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 601. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, downloaded and installed through the communication section 609, and/or installed from the removable medium 611. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program, when executed by the processor 601, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (10)

1. A permission reminding method comprises the following steps:
responding 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 comprises user identification information of the target user and service identification information of the target service;
under the condition that the first verification result represents that the target user does not have the transaction authority of the target service, the target request information is sent to a message queue platform, wherein the target request information corresponds to a sequencing identification number, and the sequencing identification number is generated by the message queue platform;
generating permission reminding information according to the target request information in the message queue platform under the condition that the sequencing identification number is smaller than or equal to a preset threshold value;
sending the authority prompting information to an information sending queue, wherein the information sending queue comprises a plurality of authority prompting information, and the content of each authority prompting information is different;
and sequentially transmitting each authority prompting message in the message transmission queue according to a message transmission frequency, wherein the message transmission frequency is determined according to a current limiting algorithm.
2. The method of claim 1, further comprising:
generating an authority prompting information sending record corresponding to the target request information under the condition that the authority prompting information is sent successfully;
and storing the permission reminding information sending record in a database so as to carry out data query based on the database.
3. The method of claim 2, further comprising:
verifying the sending record of the permission reminding information based on the target request information, and outputting a second verification result;
and under the condition that the second verification result represents that the sending record does not have the authority prompting information corresponding to the target request information, verifying the transaction authority of the target user according to the target request information in the transaction request, and outputting the first verification result.
4. The method of claim 1, wherein the generating permission reminder information according to the target request information in the message queue platform when the sequencing identification number is smaller than a preset threshold value comprises:
under the condition that the sequencing identification number is smaller than a preset threshold value, acquiring the user identification information and the service identification information from the message queue;
determining receiver information of the permission reminding information according to the service identification information;
and generating the permission reminding information according to the user identification information, the service identification information and the receiver information.
5. The method of claim 1, wherein the ordering identification number is generated by the message queue platform according to the following method:
acquiring the quantity of acquired request information in a preset time period through the message queue platform;
and determining the sequencing identification number corresponding to the target request information based on the quantity of the request information in the preset time period.
6. The method of claim 1, wherein the permission reminding method is applied to an open platform.
7. An authority reminding device, comprising:
the response module is used for responding 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 comprises 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 check result indicates that the target user does not have the transaction permission of the target service, where the target request information corresponds to a ranking identification number, and the ranking identification number is generated by the message queue platform;
the first generation module is used for generating permission reminding information according to the target request information in the message queue platform under the condition that the sequencing identification number is smaller than or equal to a preset threshold value;
the second sending module is used for sending the permission reminding information to an information sending queue, wherein the information sending queue comprises a plurality of permission reminding information, and the contents of the permission reminding information are different;
and the third sending module is used for sequentially sending each permission reminding message in the message sending queue according to a message sending frequency, wherein the message sending frequency is determined according to a current limiting algorithm.
8. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-6.
9. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 6.
10. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 6.
CN202111335913.5A 2021-11-11 2021-11-11 Permission reminding method, device, equipment and storage medium Pending CN114049208A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111335913.5A CN114049208A (en) 2021-11-11 2021-11-11 Permission reminding method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111335913.5A CN114049208A (en) 2021-11-11 2021-11-11 Permission reminding method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114049208A true CN114049208A (en) 2022-02-15

Family

ID=80208622

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111335913.5A Pending CN114049208A (en) 2021-11-11 2021-11-11 Permission reminding method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114049208A (en)

Similar Documents

Publication Publication Date Title
CN110955640B (en) Cross-system data file processing method, device, server and storage medium
CN113900834A (en) Data processing method, device, equipment and storage medium based on Internet of things technology
CN115357761A (en) Link tracking method and device, electronic equipment and storage medium
CN113572763B (en) Data processing method and device, electronic equipment and storage medium
CN113411400B (en) Information calling method and device, electronic equipment and readable storage medium
CN113132400A (en) Business processing method, device, computer system and storage medium
CN113076224A (en) Data backup method, data backup system, electronic device and readable storage medium
CN115801764A (en) File transmission method, device, equipment and storage medium
US20190042653A1 (en) Automatic identification of user information
CN114049208A (en) Permission reminding method, device, equipment and storage medium
CN114461230A (en) Gray scale publishing method, device, equipment and medium
CN114218283A (en) Abnormality detection method, apparatus, device, and medium
CN114490130A (en) Message subscription method and device, electronic equipment and storage medium
CN114168607A (en) Global serial number generation method, device, equipment, medium and product
CN113449886A (en) Data processing method, processing device, equipment and storage medium
CN112083945A (en) NPM installation package update prompting method and device, electronic equipment and storage medium
CN111580882A (en) Application program starting method, device, computer system and medium
CN114721882B (en) Data backup method and device, electronic equipment and storage medium
CN114969059B (en) Method and device for generating order information, electronic equipment and storage medium
CN113760899A (en) Data table change control method and device, electronic equipment and readable storage medium
CN114861054A (en) Information acquisition method and device, electronic equipment and storage medium
CN114461367A (en) Batch execution method, apparatus, electronic device, medium, and computer program product
CN116775307A (en) Service processing method, device, equipment and storage medium
CN113436000A (en) Remittance processing method, remittance processing apparatus, electronic device, and readable storage medium
CN117176576A (en) Network resource changing method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination