Business request processing method, apparatus, device, storage medium, and program product

Abstract

The application relates to the technical field of data processing, and particularly discloses a business request processing method and device, equipment, a storage medium and a program product. The method comprises the following steps: in the case that a business request is received, determining a business request identifier according to request information carried in the business request; determining whether the business request conforms to a business processing authority according to the business request identifier; and if it is determined that the business request conforms to the business processing authority, performing business processing on the business request according to preset processing logic. The method can effectively avoid repeated sending of short messages.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a business request processing method and device, equipment, a storage medium and a program product. BACKGROUND

[0002] It is a common user middle platform support function to send a short message verification code to a user for verification code login or authentication. In order to avoid excessive short message harassment of the user and waste of short message cost due to too many short message sending times, the frequency and quantity of short message sending to the user are controlled to avoid repeated sending.

[0003] In the prior art, the time interval control of the short message sending button on the front end page is performed, for example, after it is determined that the user clicks the short message sending button on the front end page, the short message sending button on the front end page is grayed out.

[0004] However, if the interface for obtaining the short message verification code is attacked, the time interval control strategy of the button on the front end page is meaningless, that is, the prior art cannot effectively avoid repeated sending of the short message when processing the short message sending request. SUMMARY

[0005] Therefore, it is necessary to provide a business request processing method, device, equipment, storage medium and program product capable of effectively avoiding repeated sending of short messages in view of the above technical problems.

[0006] In a first aspect, the present application provides a business request processing method, comprising: in the case of receiving a business request, determining a business request identifier according to request information carried in the business request; determining whether the business request meets a business processing authority according to the business request identifier; and if it is determined that the business request meets the business processing authority, performing business processing on the business request according to a preset processing logic.

[0007] In one of the embodiments, determining whether the business request meets the business processing authority according to the business request identifier comprises: generating a request data record according to the business request identifier; writing the request data record into a preset shared business request authority table, taking the business request identifier as a primary key, and obtaining a writing result of the request data record; and if the writing result of the request data record is writing success, it is determined that the business request meets the business processing authority.

[0008] In one of the embodiments, determining whether the business request meets the business processing authority according to the business request identifier further comprises: if the writing result of the data record is writing failure, it is determined that the business request does not meet the business processing authority.

[0009] In one of the embodiments, the request information includes a user identifier and a service request scenario identifier, and the service request identifier is determined according to the request information carried in the service request, including: determining the service request identifier according to the user identifier, the service request scenario identifier and a service request time.

[0010] In one of the embodiments, the method further includes: if it is determined that the service request does not conform to the service processing authority, saving the service request, and re-determining whether the service request conforms to the service processing authority after a preset time period, until the number of retries reaches a preset number threshold or it is determined that the service request conforms to the service processing authority.

[0011] In one of the embodiments, the service request is processed according to the preset processing logic, including: if the request information carried in the service request meets a preset processing condition, performing short message verification processing and / or short message sending processing on the service request, and performing storage processing on the service data.

[0012] In one of the embodiments, the method further includes: if the request information carried in the service request does not meet the preset processing condition, or the service processing on the service request fails, deleting the request data record corresponding to the service request identifier in the shared service request authority table.

[0013] In a second aspect, the application further provides a service request processing apparatus, including:

[0014] A first determination module, configured to determine a service request identifier according to request information carried in a service request when the service request is received;

[0015] A second determination module, configured to determine whether the service request conforms to a service processing authority according to the service request identifier;

[0016] A first processing module, configured to process the service request according to a preset processing logic if it is determined that the service request conforms to the service processing authority.

[0017] In one of the embodiments, the second determination module is specifically configured to generate a request data record according to the service request identifier, write the request data record into a preset shared service request authority table, take the service request identifier as a primary key, and obtain a write result of the request data record; if the write result of the request data record is write success, it is determined that the service request conforms to the service processing authority.

[0018] In one of the embodiments, the second determination module is further configured to determine that the service request does not conform to the service processing authority if the write result of the data record is write failure.

[0019] In one of the embodiments, the request information comprises a user identifier and a service request scenario identifier, and the first determining module is specifically configured to determine the service request identifier according to the user identifier, the service request scenario identifier and a service request time.

[0020] In one of the embodiments, the apparatus further comprises a second processing module configured to, if the second determining module determines that the service request does not conform to the service processing authority, save the service request, and then determine whether the service request conforms to the service processing authority after a preset time period, until a retry number reaches a preset number threshold or the service request conforms to the service processing authority.

[0021] In one of the embodiments, the first processing module is specifically configured to, if the request information carried in the service request meets a preset processing condition, perform a short message verification processing and / or a short message sending processing on the service request, and perform a storage processing on the service data.

[0022] In one of the embodiments, the first processing module is further configured to, if the request information carried in the service request does not meet the preset processing condition, or the service processing on the service request fails, delete a request data record corresponding to the service request identifier in the shared service request authority table.

[0023] In a third aspect, the present application further provides a service request processing device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the method of any one of the first aspect when executing the computer program.

[0024] In a fourth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method of any one of the first aspect.

[0025] In a fifth aspect, the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the method of any one of the first aspect.

[0026] The business request processing method, device, equipment, storage medium and program product determine the business request identifier according to the request information carried in the business request when the business request is received, determine whether the business request meets the business processing authority according to the business request identifier, and perform business processing on the business request according to the preset processing logic if it is determined that the business request meets the business processing authority. In this way, when the server receives multiple repeated business requests, it can be quickly judged based on the business request identifier whether the current business request meets the business processing authority, and then only the business request meeting the business processing authority is processed. When the above method is applied to the scenario of processing the short message sending request, the interface for obtaining the short message verification code is attacked, or in the case of high concurrency, the repeated sending of short messages can be effectively avoided. BRIEF DESCRIPTION OF DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other related drawings can also be obtained without creative labor based on these drawings.

[0028] Figure 1 Flowchart of a business request processing method in an embodiment;

[0029] Figure 2 Flowchart of a step of determining whether a business request meets a business processing authority in an embodiment;

[0030] Figure 3 Flowchart of a business request processing method in another embodiment;

[0031] Figure 4 Structural block diagram of a business request processing device in an embodiment;

[0032] Figure 5 Structural block diagram of a business request storage device in another embodiment;

[0033] Figure 6 Internal structure diagram of a business request processing equipment in an embodiment. DETAILED DESCRIPTION

[0034] In order to make the purposes, technical solutions and advantages of the present application clearer, further detailed description will be given below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application. It should be noted that in the embodiments of the present application, some software, groups, models and other industry existing solutions may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solutions of the present application, but does not mean that the applicant has or will necessarily use the solution.

[0035] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations. The acquisition, storage, use, processing and the like of data in the technical solutions of the present application comply with the relevant regulations of national laws and regulations.

[0036] The business request processing method, device, equipment, storage medium and program product provided by the embodiments of the present application can be applied to short message sending request processing; of course, it can also be applied to other business systems that need to process business requests in scenarios, which are not limited in the embodiments of the present application.

[0037] It is one of the common user middle platform supporting functions to send a short message verification code to the user for verification code login or authentication. In order to avoid excessive short message harassment of the user and waste of short message cost caused by too many short message sending times, the frequency and quantity of sending short messages to the user will be controlled to avoid repeated sending.

[0038] In the prior art, the available time interval of the short message sending button on the front end page is controlled, for example, after it is determined that the user clicks the short message sending button on the front end page, the short message sending button on the front end page is grayed out.

[0039] However, if the interface for obtaining the short message verification code is attacked, the button time interval control strategy of the front end page is meaningless, that is, the prior art cannot effectively avoid repeated sending of short messages when processing the short message sending request.

[0040] Therefore, the present application provides a business request processing method capable of effectively avoiding repeated sending of short messages. In an exemplary embodiment, as shown in Figure 1 A business request processing method is provided, and the present embodiment takes the method applied to a server as an example. The method includes the following steps:

[0041] S101, in the case of receiving a service request, determining a service request identifier according to request information carried in the service request.

[0042] Optionally, the service request can be sent by a terminal, and the server obtains the request information carried in the service request after receiving the service request, and then determines the service request identifier of the current service request according to the request information.

[0043] Optionally, the service request identifier can be used to represent the service request, and the request information can include a user identifier and a service request scenario identifier, wherein the user identifier can be a unique identifier of the user, used to distinguish and identify different users, and the user identifier can be a communication account of the user, an identity ID of the user, or a device ID of the user, etc., and the communication account of the user can be a mobile phone number or an email address, etc., and the type of the user identifier and the type of the user communication account are not limited in the embodiment of the application.

[0044] Optionally, the service scenario identifier can be an independent scenario ID pre-allocated by the user front-end scenario according to the user touch, and different service scenarios correspond to different service scenario identifiers.

[0045] Optionally, when the user identifier is the identity ID of the user or the device ID of the user, since the user may change the device or use multiple accounts, it is necessary to correctly associate the device ID and the user ID and the communication account of the user.

[0046] In one possible implementation, the service request identifier can be determined according to the user identifier, the service request scenario identifier and the service request time.

[0047] Optionally, the service request identifier can be a serial string obtained by splicing the user identifier, the service scenario and the service request time, and the splicing rules of each service request identifier are the same.

[0048] Optionally, splicing the service request time in the service request identifier can control the frequency of processing the service request, and the service request time can be accurate to the year, month, day, hour, minute, or the year, month, day, hour, and the application embodiment does not limit this, for example, when the type of the service request time is the year, month, day, hour, and minute, it can be controlled to process the service request only once in a minute, and when the type of the service request time is the year, month, day, and hour, it can be controlled to process the service request only once in an hour.

[0049] In another possible implementation, the service request identifier can also be determined according to the user identifier and the service request scenario identifier.

[0050] In another possible implementation manner, the flow serial can be determined according to a user identifier, a service scenario and a service request time, the flow serial is encrypted according to a preset encryption algorithm, and the encrypted flow serial is taken as the service request identifier.

[0051] In S102, it is determined whether the service request conforms to a service processing authority according to the service request identifier.

[0052] Optionally, the service request conforms to the service processing authority when the service request is not processed by the server in a time period. The time period can be preset according to a service rule, and a time type of the service request time corresponds to the time period. For example, when the time type of the service request time is year, month, day and minute, the time period can be one minute; when the time type of the service request time is year, month and day, the time period can be one hour; and the time period can also be half an hour, which is not limited in the embodiments of the present application.

[0053] In a possible implementation manner, when it is determined whether the service request conforms to the service processing authority according to the service request identifier, a Bloom filter can be set, and then the Bloom filter is queried to determine whether the service request identifier exists after the service request identifier is determined. If the service request identifier exists, the service request does not conform to the service processing authority; if the service request identifier does not exist, the service request conforms to the service processing authority, and the service request identifier is added to the Bloom filter.

[0054] Optionally, the Bloom filter is a high-efficiency data structure, which is mainly used to determine whether an element exists. The Bloom filter is composed of a bit array and multiple hash functions, and uses a long binary vector or bitmap. All bits are initially set to 0. When an element is added, the positions corresponding to the element are calculated by multiple hash functions, and the positions are set to 1. When the element is queried, the element is calculated by multiple hash functions to obtain multiple positions in the bit array. If one of the positions is 0, the element does not exist.

[0055] Optionally, since the Bloom filter only needs to check a few bits in the bit array to obtain a result, the read-write speed of the Bloom filter is extremely fast, and therefore, the Bloom filter can be used to determine whether the service request conforms to the service processing authority in a high-concurrency case.

[0056] In another possible implementation manner, the service request identifier can be taken as a primary key to be written into a database table, and a writing result is obtained. Whether the service request conforms to the service processing authority is determined according to the writing result.

[0057] In S103, if it is determined that the service request conforms to the service processing authority, the service request is processed according to a preset processing logic.

[0058] Optionally, after determining that the business request meets the business processing permissions, the business request can be processed according to the request information carried in the business request and the preset processing logic.

[0059] Optionally, the preset processing logic may include the logic for verifying the request information, the business processing logic after the verification passes, the business processing logic after the verification fails, and the processing logic for business processing exceptions.

[0060] Optionally, business processing may include, but is not limited to, at least one of the following: SMS verification processing, SMS sending processing, and business data storage processing.

[0061] The aforementioned business request processing method, upon receiving a business request, determines a business request identifier based on the request information carried in the request; determines whether the business request meets the business processing permissions based on the business request identifier; and if the business request meets the business processing permissions, processes the business request according to preset processing logic. In this way, when the server receives multiple duplicate business requests, it can quickly determine whether the current business request meets the business processing permissions based on the business request identifier, and then only process business requests that meet the business processing permissions. When this method is applied to the scenario of SMS sending request processing, it can effectively prevent duplicate SMS sending in the event of an attack on the interface for obtaining SMS verification codes, or in high-concurrency situations.

[0062] In one exemplary embodiment, such as Figure 2 As shown, optionally, determining whether a business request meets the business processing permissions based on the business request identifier includes the following steps 201 to 203. Wherein:

[0063] S201, Generate request data record based on business request identifier.

[0064] Optionally, a request data record can be generated based on the business request identifier. The request data record may include the business request identifier and the time when the request data record was generated.

[0065] Optionally, the time format for generating the requested data record can be year-month-day, year-month-day-hour, or other time formats.

[0066] S202, write the request data record into the preset shared business request permission table, with the business request identifier as the primary key, and obtain the writing result of the request data record.

[0067] Optionally, the requested data record can be written into a preset shared business request permission table by performing an insert operation in Structured Query Language (SQL).

[0068] Optionally, the shared service request permission table can include a service request identifier and a request data record registration time. A possible table structure includes the fields shown in Table 1:

[0069] Table 1 is a table structure of the shared service request permission table

[0070]

[0071] Optionally, the shared service request permission table can be only one table, that is, the service request identifier corresponding to the request data of all service requests is written into the shared service request permission table. Alternatively, the shared service request permission table has multiple tables, and the service request identifier corresponding to the request data of different service requests is written into different shared service request permission tables through a database and table splitting strategy. In this way, the query and writing performance of the database system can be improved, and the scalability and fault tolerance are enhanced.

[0072] Optionally, the database splitting can be that multiple independent databases exist, each database is referred to as a “database split”, and the request data records are written into a shared service request permission table in a corresponding database according to a preset rule. The table splitting can be that multiple independent small tables exist, each small table is referred to as a “shard” or “table split”, and the request data records are written into a shared service request permission table according to a preset rule.

[0073] Optionally, the shared service request permission table can also be a time partition table with a registration time field as a partition field. When the number of request data records in the shared service request permission table is too large, the data can be cleaned according to time, or a timing task or an external data cleaning instruction can be set to clean the data in the table according to time.

[0074] For example, a user identifier includes a user mobile phone number, 10 shared service request permission tables can be established, and a preset rule can be that a value of a certain digit in the mobile phone number is used to determine into which shared service request permission table the request data corresponding to the service request identifier is written. For example, if the penultimate digit of the mobile phone number is 3, the corresponding request data is written into the third shared service request permission table. The preset rule can also be that the mobile phone number is mathematically processed to determine into which shared service request permission table the request data corresponding to the service request identifier is written. The specific setting of the preset rule is not limited in the embodiments of the application.

[0075] Optionally, the writing result of the request data record can be determined through an exception handling mechanism. For example, the writing result can be determined by capturing a SQLException exception. The writing result can also be determined by analyzing the operation log of the database.

[0076] S203, if the write result of the request data record is a write success, it is determined that the service request meets the service processing permission.

[0077] Optionally, if the write result of the request data record is a write failure, it is determined that the service request does not meet the service processing permission.

[0078] Optionally, if the SQLException exception is captured after the insertion operation is performed, it is determined that the write result of the request data record is a write failure, and if the SQLException exception is not captured, it is determined that the write result of the request data record is a write success.

[0079] Optionally, the service request identifier is used as the primary key, and the primary key conflict mechanism of the database can ensure that in a high-concurrency case, no matter how many identical request data records enter, only one request data record will be successfully written into the preset shared service request permission table, and the rest of the request data records will fail to be written. Therefore, only one request can successfully obtain the service processing permission in a time period.

[0080] Optionally, in a distributed system, if the service request is repeatedly initiated by the client multiple times, the initiated service request may be distributed to different servers for processing at the server side. Each server will determine the service request identifier according to the service request and write it into the preset shared service request permission table. Since the service request is the same, the service request identifier is also the same. Therefore, after any server successfully writes the request data record into the preset shared service request permission table, other servers will not be able to write data into the shared service request permission table. In this way, it is possible to prevent multiple servers from repeatedly obtaining the service processing permission.

[0081] The above-mentioned request data record is generated according to the service request identifier, the request data record is written into the preset shared service request permission table, the service request identifier is used as the primary key, and the write result of the request data record is obtained. If the write result of the request data record is a write success, it is determined that the service request meets the service processing permission. In this way, based on the primary key conflict mechanism of the database, it is ensured that no matter how many identical request data records enter, only one request data record will be successfully written into the preset shared service request permission table, and the rest of the request data records will fail to be written. Therefore, only one request can successfully obtain the service processing permission in a time period, and only the service request meeting the service processing permission is processed. This can effectively avoid the repeated sending of short messages.

[0082] In an exemplary embodiment, the service request processing method further comprises:

[0083] If it is determined that the service request does not conform to the service processing permission, the service request is saved, and it is re-determined whether the service request conforms to the service processing permission after a preset time period, until the retry number reaches a preset number threshold, or it is determined that the service request conforms to the service processing permission.

[0084] Optionally, the service request that does not conform to the service processing permission can be forwarded to a message queue for storage, and can also be saved in a retry table in a database table or other storage medium.

[0085] Optionally, when saving the service request that does not conform to the service processing permission, all repeated service requests can be stored, or only one can be stored.

[0086] Optionally, the preset time period can be longer than the processing time of the preset processing logic for processing the service request, or can be the same as the processing time.

[0087] Optionally, after the preset time period, it can be checked whether the retry number reaches the preset number threshold, if the retry number does not reach the preset number threshold, the service request identifier can be re-determined to execute the above steps 201 to 202 again, if the write result is write success, the service request is processed according to the preset processing logic, and the current service request is deleted from the message queue or the retry table, if the write result is write failure, the retry number is increased by 1 and the preset time period is waited again for retry.

[0088] Optionally, the corresponding request data record can also be found in the service request permission table according to the service request identifier after the preset time period, if the corresponding request data record exists, the current service request can be deleted from the message queue or the retry table, if the corresponding request data record does not exist, the above steps 201 to 202 can be executed again.

[0089] Optionally, the service processing data can also be queried according to the service request identifier after the preset time period, similarly, if the corresponding service processing data exists, the current service request can be deleted from the message queue or the retry table, if the corresponding service processing data does not exist, the above steps 201 to 202 can be executed again.

[0090] The above, if it is determined that the service request does not conform to the service processing permission, the service request is saved, and it is re-determined whether the service request conforms to the service processing permission after a preset time period, until the retry number reaches a preset number threshold, or it is determined that the service request conforms to the service processing permission, in this way, the reliability of service request processing can be improved, and the fault tolerance of service request processing can be improved on the premise of effectively avoiding repeated sending of short messages.

[0091] In an exemplary embodiment, the service request is processed according to preset processing logic, including:

[0092] If the request information carried in the service request meets the preset processing condition, the service request is subjected to SMS verification processing and / or SMS sending processing, and the service data is subjected to storage processing.

[0093] Optionally, after the service request meets the service processing authority, the request information carried in the service request is verified, which can include identity verification of the user, compliance and validity verification of the communication account, etc. The related service parameters can also be queried in the service system through the request information, and the service parameters are verified to ensure the legality, validity and security of the service request processing.

[0094] Optionally, after the verification of the request information carried in the service request is passed, it is determined that the preset processing condition is met, a random verification code can be generated, or other business logic processing is performed, and after the processing is completed, a preset SMS sending interface is called, and the processing result of the current service request is determined according to the calling result of the SMS sending interface.

[0095] Optionally, the service data generated in the processing process can be stored, or the service data can be uniformly stored after the SMS sending interface calling is completed, and the embodiments of the present application do not limit this.

[0096] Optionally, the service data can include service request identifier, random verification code, SMS sending time, calling result of the SMS sending interface, etc.

[0097] If the request information carried in the service request meets the preset processing condition, the service request is subjected to SMS verification processing and / or SMS sending processing, and the service data is subjected to storage processing, the service request meeting the service processing authority can be processed according to preset processing logic.

[0098] In an exemplary embodiment, the service request processing method further includes: if the request information carried in the service request does not meet the preset processing condition, or the service processing of the service request fails, the request data record corresponding to the service request identifier in the shared service request authority table is deleted.

[0099] Optionally, when the request information carried in the service request does not meet the preset processing condition, the service request is no longer processed, and the request data record corresponding to the service request identifier in the shared service request authority table is deleted, so that after the current service request fails, other requests can continue to obtain the authority for service processing.

[0100] Optionally, the service processing failure of the service request can be caused by network fluctuation, operator exception or service determination exception, etc. After the service processing failure, transaction rollback can be performed by the transaction control, the service data is not stored, and the request data record corresponding to the service request identifier in the shared service request permission table is deleted, so that other requests can continue to obtain permission to process the service after the current service request fails.

[0101] Optionally, the transaction control can be used to ensure the integrity and consistency of the data in the database. In any case, when the transaction is committed, the database should maintain a consistent state, and if any operation in the transaction fails, all operations must be rolled back to the initial state to avoid data corruption or loss.

[0102] As an optional implementation, as shown in Figure 3 The service request processing method provided in the embodiments of the present application can include the following specific steps:

[0103] S301, in the case of receiving a service request, determining a service request identifier according to a user identifier, a service request scenario identifier and a service request time.

[0104] S302, generating a request data record according to the service request identifier.

[0105] S303, writing the request data record into a preset shared service request permission table, taking the service request identifier as the primary key, and obtaining the writing result of the request data record.

[0106] S304, if the writing result of the data record is writing failure, determining that the service request does not meet the service processing permission, and saving the service request.

[0107] S305, re-determining whether the service request meets the service processing permission after a preset time period, until the retry number reaches a preset number threshold or the service request meets the service processing permission.

[0108] S306, if the writing result of the request data record is writing success, determining that the service request meets the service processing permission.

[0109] S307, determining whether the request information carried in the service request meets a preset processing condition.

[0110] S308, if the request information carried in the service request meets the preset processing condition, performing SMS verification processing and / or SMS sending processing on the service request, and performing storage processing on the service data.

[0111] S309, if the request information carried in the service request does not satisfy the preset processing condition or the service processing of the service request fails, deleting the request data record corresponding to the service request identifier in the shared service request permission table.

[0112] It should be understood that, although each step in the flowchart involved in each embodiment as described above is shown in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately executed with at least part of other steps or steps or stages in other steps.

[0113] Based on the same inventive concept, the embodiments of the present application also provide a service request processing apparatus for implementing the above-mentioned service request processing method. The problem-solving implementation scheme provided by the apparatus is similar to the implementation scheme described in the above method, so the specific limitations in one or more service request processing apparatus embodiments provided below can refer to the limitations of the service request processing method described above, and will not be repeated here.

[0114] In one exemplary embodiment, as shown in Figure 4 A service request processing apparatus 400 is provided, comprising a first determination module 401, a second determination module 402 and a first processing module 403, wherein:

[0115] The first determination module 401 is configured to determine a service request identifier according to request information carried in a service request when the service request is received.

[0116] The second determination module 402 is configured to determine whether the service request meets the service processing permission according to the service request identifier.

[0117] The first processing module 403 is configured to perform service processing on the service request according to a preset processing logic if it is determined that the service request meets the service processing permission.

[0118] In one exemplary embodiment, the second determination module 402 is specifically configured to generate a request data record according to the service request identifier, write the request data record into a preset shared service request permission table, take the service request identifier as the primary key, and obtain the write result of the request data record; if the write result of the request data record is write success, it is determined that the service request meets the service processing permission.

[0119] In an example embodiment, the second determining module 402 is further configured to determine that the service request does not conform to the service processing authority if the write result of the data record is a write failure.

[0120] In an example embodiment, the request information includes a user identifier and a service request scenario identifier, and the first determining module 401 is specifically configured to determine the service request identifier according to the user identifier, the service request scenario identifier, and a service request time.

[0121] In an example embodiment, as shown in Figure 5 The service request processing apparatus 400 further includes a second processing module 404 configured to save the service request if the second determining module determines that the service request does not conform to the service processing authority, and to re-determine whether the service request conforms to the service processing authority after a preset time period, until the number of retries reaches a preset number threshold or the service request is determined to conform to the service processing authority.

[0122] In an example embodiment, the first processing module 403 is specifically configured to perform an SMS verification processing and / or an SMS sending processing on the service request, and to perform a storage processing on the service data if the request information carried in the service request meets a preset processing condition.

[0123] In an example embodiment, the first processing module 403 is further configured to delete the request data record corresponding to the service request identifier in the shared service request authority table if the request information carried in the service request does not meet the preset processing condition or the service processing on the service request fails.

[0124] The above-described various modules in the service request processing apparatus can be all or partially implemented by software, hardware, and a combination thereof. The above-described various modules can be embedded in or independent of a processor in the service request processing device in a hardware form, or can be stored in a memory in the service request processing device in a software form, so as to be called and executed by the processor to perform the operations corresponding to the above-described various modules.

[0125] In an example embodiment, a service request processing device is provided, which can include but is not limited to a server, and an internal structure diagram of the service request processing device can be as shown in Figure 6The business request processing device shown in the figure includes a processor, a memory, an input / output interface (I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the business request processing device is used to provide computing and control capabilities. The memory of the business request processing device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The database of the business request processing device is used to store data. The input / output interface of the business request processing device is used to exchange information between the processor and external devices. The communication interface of the business request processing device is used to communicate with external terminals through network connection. The computer program is executed by the processor to implement a business request processing method.

[0126] Those skilled in the art can understand that Figure 6 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the business request processing device to which the scheme of the present application is applied. The specific business request processing device can include more or fewer components than those shown in the figure, or combine certain components, or have a different component arrangement.

[0127] In one exemplary embodiment, a business request processing device is provided, including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the following steps: upon receiving a business request, determining a business request identifier according to request information carried in the business request; determining whether the business request conforms to a business processing authority according to the business request identifier; if it is determined that the business request conforms to the business processing authority, performing business processing on the business request according to a preset processing logic.

[0128] In one embodiment, the processor executing the computer program further implements the following steps: generating a request data record according to the business request identifier; writing the request data record into a preset shared business request authority table, with the business request identifier as the primary key, and obtaining a write result of the request data record; if the write result of the request data record is write success, it is determined that the business request conforms to the business processing authority.

[0129] In one embodiment, the processor executing the computer program further implements the following steps: if the write result of the data record is write failure, it is determined that the business request does not conform to the business processing authority.

[0130] In an embodiment, the request information comprises a user identifier and a service request scenario identifier, and the processor, when executing the computer program, further implements the following steps: determining a service request identifier according to the user identifier, the service request scenario identifier, and a service request time.

[0131] In an embodiment, the processor, when executing the computer program, further implements the following steps: if it is determined that the service request does not conform to the service processing authority, saving the service request, and re-determining whether the service request conforms to the service processing authority after a preset time period, until a retry count reaches a preset count threshold or it is determined that the service request conforms to the service processing authority.

[0132] In an embodiment, the processor, when executing the computer program, further implements the following steps: if the request information carried in the service request meets a preset processing condition, performing an SMS verification processing and / or an SMS sending processing on the service request, and performing a storage processing on the service data.

[0133] In an embodiment, the processor, when executing the computer program, further implements the following steps: if the request information carried in the service request does not meet the preset processing condition, or the service processing on the service request fails, deleting a request data record corresponding to the service request identifier in the shared service request authority table.

[0134] The service request processing device provided in the embodiment can implement the technical solutions in the service request processing method embodiments, and has similar implementation principles and technical effects, which will not be described herein again.

[0135] In an embodiment, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program. The computer program, when executed by a processor, implements the following steps: in a case where a service request is received, determining a service request identifier according to request information carried in the service request; determining whether the service request conforms to a service processing authority according to the service request identifier; and if it is determined that the service request conforms to the service processing authority, performing a service processing on the service request according to a preset processing logic.

[0136] In an embodiment, the computer program, when executed by the processor, further implements the following steps: generating a request data record according to the service request identifier; writing the request data record into a preset shared service request authority table, taking the service request identifier as a primary key, and obtaining a write result of the request data record; and if the write result of the request data record is write success, determining that the service request conforms to the service processing authority.

[0137] In an embodiment, the computer program, when executed by the processor, further implements the following steps: if the write result of the data record is write failure, determining that the service request does not conform to the service processing authority.

[0138] In an embodiment, the request information comprises a user identifier and a service request scenario identifier, and the computer program, when executed by the processor, further implements the following steps: determining a service request identifier according to the user identifier, the service request scenario identifier, and a service request time.

[0139] In an embodiment, the computer program, when executed by the processor, further implements the following steps: if it is determined that the service request does not conform to the service processing authority, saving the service request, and re-determining whether the service request conforms to the service processing authority after a preset time period, until a retry count reaches a preset count threshold or it is determined that the service request conforms to the service processing authority.

[0140] In an embodiment, the computer program, when executed by the processor, further implements the following steps: if the request information carried in the service request meets a preset processing condition, performing an SMS verification processing and / or an SMS sending processing on the service request, and performing a storage processing on service data.

[0141] In an embodiment, the computer program, when executed by the processor, further implements the following steps: if the request information carried in the service request does not meet the preset processing condition, or the service processing on the service request fails, deleting a request data record corresponding to the service request identifier in the shared service request authority table.

[0142] The computer program in the computer readable storage medium provided in the embodiment can be used to execute the technical solutions in the service request processing method embodiments described above when executed by the processor, and has similar implementation principles and technical effects, which will not be described here again.

[0143] In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the following steps: in a case where a service request is received, determining a service request identifier according to request information carried in the service request; determining whether the service request conforms to a service processing authority according to the service request identifier; and if it is determined that the service request conforms to the service processing authority, performing a service processing on the service request according to a preset processing logic.

[0144] In an embodiment, the computer program, when executed by the processor, further implements the following steps: generating a request data record according to the service request identifier; writing the request data record into a preset shared service request authority table, taking the service request identifier as a primary key, and obtaining a write result of the request data record; and if the write result of the request data record is write success, determining that the service request conforms to the service processing authority.

[0145] In an embodiment, the computer program, when executed by the processor, further implements the following steps: if the write result of the data record is write failure, determining that the service request does not conform to the service processing authority.

[0146] In an embodiment, the request information comprises a user identifier and a service request scenario identifier, and the computer program, when executed by the processor, further implements the following step: determining a service request identifier according to the user identifier, the service request scenario identifier, and a service request time.

[0147] In an embodiment, the computer program, when executed by the processor, further implements the following step: if it is determined that the service request does not conform to the service processing authority, saving the service request, and re-determining whether the service request conforms to the service processing authority after a preset time period, until a retry count reaches a preset count threshold or it is determined that the service request conforms to the service processing authority.

[0148] In an embodiment, the computer program, when executed by the processor, further implements the following step: if the request information carried in the service request satisfies a preset processing condition, performing an SMS verification processing and / or an SMS sending processing on the service request, and performing a storage processing on the service data.

[0149] In an embodiment, the computer program, when executed by the processor, further implements the following step: if the request information carried in the service request does not satisfy the preset processing condition or the service processing on the service request fails, deleting a request data record corresponding to the service request identifier in the shared service request authority table.

[0150] The computer program in the computer program product provided in the embodiment can be used to execute the technical solutions in the service request processing method embodiments described above when executed by the processor, and has similar implementation principles and technical effects, which will not be described herein again.

[0151] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0152] The technical features of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, however, as long as the combinations of the technical features do not exist contradictory, they should be considered as the scope of the present application.

[0153] The above-described embodiments are merely illustrative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as a limitation on the scope of the patent. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of protection of the present application should be subject to the appended claims.

Claims

1. A business request processing method, characterized in that, The method includes: Upon receiving a business request, a business request identifier is determined based on the request information carried in the business request. The request information includes a user identifier and a business request scenario identifier. The business request identifier is obtained by concatenating the user identifier, the business request scenario identifier, and the business request time. The type of the business request time includes any of the following: year-month-day, year-month-day-hour, or year-month-day-hour-minute. Generate a request data record based on the business request identifier; The request data record is written into a preset shared business request permission table, the business request identifier is used as the primary key of the shared business request permission table, and the writing result of the request data record is obtained. If the write result of the requested data record is successful, then the business request is determined to meet the business processing permissions. If the write result of the requested data record is a write failure, then it is determined that the business request does not meet the business processing permission. If it is determined that the business request meets the business processing permission, then the business request is processed according to the preset processing logic.

2. The method according to claim 1, characterized in that, The method further includes: If it is determined that the service request does not meet the service processing permissions, the service request is saved, and after a preset time period, the service request is re-determined to meet the service processing permissions, until the number of retries reaches a preset threshold, or until the service request is determined to meet the service processing permissions.

3. The method according to claim 1, characterized in that, The step of processing the business request according to the preset processing logic includes: If the request information carried in the service request meets the preset processing conditions, then the service request is processed by SMS verification and / or SMS sending, and the service data is stored.

4. The method according to claim 3, characterized in that, The method further includes: If the request information carried in the business request does not meet the preset processing conditions, or if the business processing of the business request fails, then the request data record corresponding to the business request identifier in the shared business request permission table is deleted.

5. A business request processing device, characterized in that, The device includes: The first determining module is used to determine a business request identifier based on the request information carried in the business request when a business request is received; the request information includes a user identifier and a business request scenario identifier, and the business request identifier is obtained by concatenating the user identifier, the business request scenario identifier and the business request time, and the type of the business request time includes any of the following: year-month-day, year-month-day-hour, year-month-day-hour-minute; The second determining module is used to generate a request data record based on the business request identifier; write the request data record into a preset shared business request permission table, wherein the business request identifier serves as the primary key of the shared business request permission table, and obtain the writing result of the request data record; if the writing result of the request data record is successful, then the business request is determined to meet the business processing permission; if the writing result of the request data record is unsuccessful, then the business request is determined to not meet the business processing permission. The first processing module is used to process the business request according to a preset processing logic if it is determined that the business request meets the business processing permission.

6. The apparatus according to claim 5, characterized in that, The device further includes: The second processing module is configured to, if the second determining module determines that the service request does not comply with the service processing permission, save the service request and re-determine whether the service request complies with the service processing permission after a preset time period, until the number of retries reaches a preset threshold, or until the service request is determined to comply with the service processing permission.

7. The apparatus according to any one of claims 5, characterized in that, The first processing module is specifically used to perform SMS verification processing and / or SMS sending processing on the business request if the request information carried in the business request meets the preset processing conditions, and to perform storage processing on the business data.

8. The apparatus according to claim 7, characterized in that, The first processing module is further configured to delete the request data record corresponding to the business request identifier in the shared business request permission table if the request information carried in the business request does not meet the preset processing conditions, or if the business processing of the business request fails.

9. A service request processing device, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

Images