Information verification method and device, electronic equipment and medium

Abstract

The invention relates to an information verification method and device, electronic equipment and a medium, and the method comprises the steps: receiving a target request for information verification, and enabling the target request to carry target request data; searching a prior association request associated with the target request in a pre-stored existing request record according to a pre-configured request association strategy; the request association strategy is used for describing an association rule among a plurality of requests; under the condition that the previous association request is found, comparing previous request data of the previous association request with the target request data according to a pre-configured verification strategy to obtain an information verification result for the target request; wherein at least one same field exists between the previous request data and the target request data. According to the method, the timeliness of information verification processing can be improved, the verification waiting time can be shortened, and the request of information verification can be initiated in the process of inputting partial field information.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology, and in particular to a method, device, electronic device and medium for information verification. Background Art

[0002] There are a large number of information verification scenarios in the use of various Internet applications. In many scenarios, there are requirements such as risk control, network security or identity authentication. For example, in the use of financial applications, payment applications, online shopping applications, project application applications, etc., there are often scenarios for identity information verification, login information verification, payment information verification, network security verification, application information verification, etc. In the related technologies, most of them are based on a one-click trigger method to perform centralized verification of all information. For example, after the user fills in all the information, he clicks to submit the information verification, and the application background (such as the server used for verification) verifies all the information and then feedbacks the verification results.

[0003] In the process of realizing the concept disclosed in the present invention, the inventors found that there are at least the following technical problems in the related technology: the one-key trigger method requires all information to be verified one by one at one time, and the verification results are given. When the amount of information to be verified is large, the verification logic is bloated and complicated, and the verification takes a long time, resulting in problems such as reduced response speed of the application system and sluggish response of the front-end page. Summary of the invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, embodiments of the present disclosure provide a method, device, electronic device and medium for information verification.

[0005] In the first aspect, an embodiment of the present disclosure provides a method for information verification. The method includes: receiving a target request for information verification, the target request carrying target request data; searching for a prior association request associated with the target request in a pre-stored existing request record according to a pre-configured request association strategy; the request association strategy is used to describe the rules for association between multiple requests; when the prior association request is found, comparing the prior request data of the prior association request with the target request data according to the pre-configured verification strategy to obtain an information verification result for the target request; wherein the prior request data and the target request data have at least one identical field.

[0006] According to an embodiment of the present disclosure, the above-mentioned request association strategy is used to associate requests in the time dimension and the request type dimension; the above-mentioned existing request record contains the following information: request time and type identifier, the above-mentioned type identifier is at least one of the request processing interface identifier or the data verification scenario identifier; the above-mentioned search for the prior associated request associated with the above-mentioned target request in the pre-stored existing request records according to the pre-configured request association strategy includes: for the pre-stored existing request records, double matching of the request time and type identifier is performed according to the above-mentioned request association strategy, and a prior associated request that matches both the time dimension and the request type dimension is obtained.

[0007] According to an embodiment of the present disclosure, the request association strategy includes at least one of the first rule information, the second rule information, the third rule information and the fourth rule information. First rule information: When the request processing interface corresponding to the multiple requests is the same interface and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated. Second rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a call relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated. Third rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a routing relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated. Fourth rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is data intersection between the data verification scenarios corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated.

[0008] In some embodiments, the above-mentioned verification strategy includes: a risk control verification strategy and a content verification strategy. The above-mentioned verification strategy pre-configured, compares the previous request data of the above-mentioned previous associated request with the above-mentioned target request data, and obtains the information verification result for the above-mentioned target request, including: according to the above-mentioned risk control verification strategy, compares the value of the first common field in the above-mentioned previous request data and the above-mentioned target request data, and obtains the risk control verification result; in the case where the above-mentioned risk control verification result is a passed verification, according to the above-mentioned content verification strategy, based on the verified passed result in the above-mentioned previous request data, the value of the second common field in the above-mentioned target request data is verified to obtain a consistency verification result; in the case where the above-mentioned consistency verification result is a passed verification, the incremental to-be-verified field in the above-mentioned target request data is verified to obtain an incremental verification result; according to the above-mentioned incremental verification result, the corresponding information verification result is obtained.

[0009] According to an embodiment of the present disclosure, according to the above-mentioned content verification strategy, based on the verified result in the above-mentioned prior request data, the value of the second common field in the above-mentioned target request data is verified to obtain a consistency verification result, including: taking the value of the second common field that has been verified in the prior request data as a reference value, verifying whether the value of the second common field in the target request data is consistent with the reference value, and obtaining a consistency verification result.

[0010] According to an embodiment of the present disclosure, the above-mentioned target request data includes: request attribute information and entered information; the above-mentioned request attribute information includes the above-mentioned first common field, and the above-mentioned entered information includes the above-mentioned second common field and the above-mentioned incremental field to be verified; wherein the above-mentioned entered information is part or all of the complete submitted information, and the above-mentioned complete submitted information is the submission information corresponding to the completion of filling in all fields in the data verification scenario corresponding to the above-mentioned target request; the above-mentioned first common field is a field specified by the pre-configured policy usage scope.

[0011] According to an embodiment of the present disclosure, the above-mentioned incremental fields to be verified include at least one of the following: a first field to be verified, a second field to be verified; in the entered information of the target request, compared with the different fields in the previous associated request, these different fields serve as the first field to be verified; in the entered information of the target request, one or more identical fields are commonly contained in the previous associated request and the previous associated request fails the value verification for these identical fields, and these identical fields serve as the second field to be verified. Among them, the incremental field to be verified in the above-mentioned target request data is verified to obtain an incremental verification result, including: when the above-mentioned incremental field to be verified is the second field to be verified, comparing whether the value of the second field to be verified in the above-mentioned target request data is the same as the value of the same field in the previous associated request; when they are the same, determining that the above-mentioned information verification result is failed; when they are different, calling related services or verifying the above-mentioned second field to be verified according to preset logic to obtain an incremental verification result for the second field to be verified; when the above-mentioned incremental field to be verified is the first field to be verified, calling related services or verifying the above-mentioned first field to be verified according to preset logic to obtain an incremental verification result for the first field to be verified.

[0012] According to an embodiment of the present disclosure, the above-mentioned information verification result is obtained by comparing the previous request data of the above-mentioned previous associated request with the above-mentioned target request data according to a pre-configured verification strategy, and also includes: when the above-mentioned risk control verification result is verification failure, determining that the information verification result is verification failure; when the above-mentioned consistency verification result is verification failure, determining that the information verification result is verification failure.

[0013] According to an embodiment of the present disclosure, the attribute information of the above-mentioned verification policy includes: a policy type, and the above-mentioned policy type is used to match verification requests under different request types; the content information of the above-mentioned verification policy includes: verification logic; the above-mentioned verification policy, according to a pre-configured verification policy, compares the previous request data of the above-mentioned previous associated request with the above-mentioned target request data to obtain an information verification result for the above-mentioned target request, including: for a pre-configured policy table, matching the request type of the above-mentioned target request with the policy type of the verification policy to obtain a verification policy matching the above-mentioned target request; the above-mentioned policy table contains at least one verification policy and at least one request association policy; based on the verification logic in the matched verification policy, performs information comparison verification between the above-mentioned prior request data and the above-mentioned target request data to obtain the above-mentioned information verification result.

[0014] According to an embodiment of the present disclosure, the above method also includes: in the case where the above-mentioned prior association request cannot be found, parsing the above-mentioned target request data to obtain the parsed fields, and the above-mentioned fields include: attribute fields corresponding to the requested attribute information and information fields corresponding to the entered information; verifying the values ​​of the above-mentioned information fields to obtain the information verification results for the above-mentioned target request.

[0015] According to an embodiment of the present disclosure, the above method also includes: assigning a corresponding target request record identifier to the above target request; based on the above target request record identifier, storing the above target request data and the corresponding information verification result in the above existing request record.

[0016] In a second aspect, an embodiment of the present disclosure provides a device for information verification. The device includes: a request receiving module, an associated request search module, and a comparison and verification module. The request receiving module is used to receive a target request for information verification, and the target request carries target request data. The associated request search module is used to search for a prior associated request associated with the target request in a pre-stored existing request record according to a pre-configured request association strategy; the request association strategy is used to describe the rules for association between multiple requests. The comparison and verification module is used to compare the prior request data of the prior associated request with the target request data according to a pre-configured verification strategy when the prior associated request is found, to obtain an information verification result for the target request; wherein, the prior request data and the target request data have at least one identical field.

[0017] In a third aspect, an embodiment of the present disclosure provides an electronic device. The electronic device includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory is used to store computer programs; and the processor is used to implement the above-mentioned information verification method when executing the program stored in the memory.

[0018] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the information verification method described above is implemented.

[0019] The above technical solution provided by the embodiments of the present disclosure has at least some or all of the following advantages:

[0020] Based on the idea of ​​sequentially associating and comparing multiple requests, the related data of the previous request is stored in the existing request record, and the previous associated request associated with the target request is searched in the existing request record according to the pre-configured request association strategy. The previous request data corresponding to the previous associated request and the target request data have at least one identical field, that is, an overlapping field. Based on the association of the overlapping fields between the previous and next requests, it is possible to transform the one-time centralized verification into multiple comparison verifications of requests with content inclusion relationships or content intersection relationships, thereby reducing the complexity of the subsequent request information verification. In addition, compared with the unified verification, it can improve the timeliness of the information verification processing and reduce the verification waiting time. In specific application scenarios, for the same information verification scenario, the user does not need to enter all the field information before submitting it for verification, and supports initiating information verification requests during the process of entering part of the field information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0023] Figure 1 The system architecture of the information verification method and device applicable to the embodiments of the present disclosure is schematically shown;

[0024] Figure 2 The flowchart of the information verification method according to an embodiment of the present disclosure is schematically shown;

[0025] Figure 3 The following schematically shows a data structure diagram of an existing request record according to an embodiment of the present disclosure;

[0026] Figure 4 The flowchart schematically shows a method for information verification according to another embodiment of the present disclosure;

[0027] Figure 5 The flowchart of the information verification method according to another embodiment of the present disclosure is schematically shown;

[0028] Figure 6 The detailed implementation flow chart of step S231 according to the embodiment of the present disclosure is schematically shown;

[0029] Figure 7 The following schematically shows a schematic diagram of the implementation process of the information verification method according to an embodiment of the present disclosure;

[0030] Figure 8 A structural block diagram schematically shows a device for information verification according to an embodiment of the present disclosure; and

[0031] Fig. 9 The structural block diagram of the electronic device provided by the embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0032] In many scenarios, there are requirements for risk control, network security or identity authentication, such as in the use of financial applications, payment applications, online shopping applications, project application applications, etc., information verification is required to ensure security. However, in the related technologies, most of them are based on a one-click trigger method to perform centralized verification of all information. For example, after the user fills in all the information, he clicks to submit the information verification, and the application background (such as the server used for verification) verifies all the information and then feedbacks the verification result.

[0033] Taking project application applications as an example, many fields are usually preset. These fields are usually distributed in multiple filling pages. Each page contains multiple fields. Users are required to fill in the information of each field in each page in sequence, save the information of each page respectively, and finally click the submit button on the last page to trigger the information verification function. Accordingly, it is necessary to centrally verify all submitted field information in the application background server. When the amount of information to be centrally verified is large, the verification logic is bloated and complicated, and the verification takes a long time, resulting in problems such as reduced response speed of the application system and slow response of the front-end page, and poor user experience. For some commercial software, the slow data processing time caused by the bloated verification logic will further lead to practical problems such as user negative reviews and user loss.

[0034] In view of this, an embodiment of the present disclosure provides a method, device, electronic device and medium for information verification, the method comprising: receiving a target request for information verification, the target request carrying target request data; searching for a prior associated request associated with the target request in a pre-stored existing request record according to a pre-configured request association strategy; the request association strategy is used to describe the rules for association between multiple requests; when the prior associated request is found, comparing the prior request data of the prior associated request with the target request data according to the pre-configured verification strategy to obtain an information verification result for the target request; wherein, the prior request data and the target request data have at least one identical field.

[0035] The idea of ​​associating multiple requests in sequence and performing comparison and verification is proposed. The related data of the previous request is stored in the existing request record. According to the pre-configured request association strategy, the previous associated request associated with the target request is searched in the existing request record. The previous request data corresponding to the previous associated request and the target request data have at least one identical field, that is, an overlapping field. Based on the correlation of the overlapping fields between the previous and next requests, it is possible to transform a one-time centralized verification into a comparison and verification of multiple requests with content inclusion relationships or content intersection relationships, thereby reducing the complexity of information verification in subsequent requests. In addition, compared with unified verification, it can improve the timeliness of information verification processing and reduce verification waiting time. In specific application scenarios, for the same information verification scenario, the user does not need to enter all field information before submitting for verification. It supports initiating information verification requests during the process of entering partial field information.

[0036] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0037] Figure 1 The system architecture of the method and device for information verification applicable to the embodiments of the present disclosure is schematically shown.

[0038] Reference Figure 1As shown, the system architecture 100 of the method and apparatus for information verification applicable to the embodiment of the present disclosure includes: terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is a medium that provides a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0039] The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications or corresponding web applications, small program applications, etc. that require information verification can be installed on the terminal devices 101, 102, 103, such as shopping applications, payment applications, project application applications, financial applications (including banking applications, securities applications, etc.), search applications, social applications, instant messaging applications, search applications, etc. (only for example).

[0040] The terminal devices 101, 102, and 103 may be various electronic devices with display screens, such as electronic devices including but not limited to smart phones, tablet computers, laptop computers, desktop computers, smart watches, smart bracelets, driverless cars, etc.

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

[0042] It should be noted that the information verification method provided in the embodiment of the present disclosure can generally be executed by the server 105 or a terminal device with a certain computing capability. Accordingly, the information verification device provided in the embodiment of the present disclosure can generally be set in the server 105 or in the above-mentioned terminal device with a certain computing capability. The information verification method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the information verification device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

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

[0044] The first exemplary embodiment of the present disclosure provides a method for information verification. The method provided by this embodiment can be Figure 1 The method is executed by the server 105 in the system architecture 100 of the example, and the server 105 is used to provide services for terminal devices installed with various applications that need to perform information verification. Alternatively, the method can also be executed by a terminal device installed with information verification that needs to be performed, for example, the executing terminal device has certain computing power and storage capacity or can call some computing services or storage services.

[0045] Figure 2 The flowchart of the information verification method according to an embodiment of the present disclosure is schematically shown.

[0046] Reference Figure 2 As shown, the information verification method provided by the embodiment of the present disclosure includes the following steps: S210, S220 and S231.

[0047] In step S210, a target request for information verification is received, wherein the target request carries target request data.

[0048] The target request refers to the request received at the current moment. In order to distinguish it from the request at the previous moment, in the embodiment of the present disclosure, the request before the target request is described as the prior request, and the prior request associated with the target request is described as the prior associated request.

[0049] The above target request data may include: request attribute information and entered information; request attribute information refers to metadata information describing the request, including but not limited to: request address (such as IP (Internet Protocol) address), request account (such as mobile phone number, ID number, user name, etc.), request time, etc. Entered information refers to information that has been entered when the request is initiated. The above entered information is part or all of the complete submitted information. The above complete submitted information is the submission information corresponding to all fields in the data verification scenario corresponding to the above target request.

[0050] For example, in the related art, for information reporting applications, the user is required to complete filling in the information of the setting fields on three pages and click the submit function button before centralized verification of all the reported information can be performed.

[0051] In the application scenario of the disclosed method, it is supported to initiate a request for information verification during the process of entering partial field information. For example, at time t1, the user fills in the information on page 1 in the information declaration application of the terminal device and clicks the information verification function button. At this time, the terminal device sends the request at time t1 to the server; correspondingly, the server receives the request Q11 at time t1 for verifying the information on page 1. At this time, the target request data is part of the complete submitted information, and the complete submitted information is the submission information corresponding to the completion of filling in all the information in the set fields of 3 pages. In some implementation scenarios, it is also possible to set only the information verification function button corresponding to the complete submitted information. After the user clicks the Save button for the partially filled in information, the verification of the filled in information is automatically triggered. At this time, the corresponding target request is the request for verification of the entered information.

[0052] In step S220, according to a pre-configured request association strategy, a previous association request associated with the target request is searched in pre-stored existing request records; the request association strategy is used to describe the rules for association between multiple requests.

[0053] Since different data processing scenarios correspond to different data verification strategies, you can configure the corresponding verification strategies for different scenarios in advance.

[0054] Figure 3 A schematic diagram of the data structure of an existing request record according to an embodiment of the present disclosure is schematically shown.

[0055] Reference Figure 3 As shown, the existing request records are illustrated in the form of a data table. The above-mentioned existing request record 300 contains the following information: request record identification 310, request data 320 and information verification result 330. In some embodiments, it may also include remark information 340. The above-mentioned request data 320 includes: request attribute information and entered information. The request attribute information includes, but is not limited to: type identification, request time, request address, etc. The above-mentioned type identification is at least one of the request processing interface identification or the data verification scenario identification. For each received request, a request record identification 310 of the request will be generated, and the request data 320 and the corresponding information verification result 330 will be recorded under the corresponding request record identification; some requests may also record remark information 340 for additional supplementary explanation of the request.

[0056] The above-mentioned existing request records can be stored in the cache or in the database, for example, can be stored in the distributed cache Redis (an open source log-type, key-value pair database written in ANSI C language, supporting network, memory-based or persistent, and providing APIs (application programming interfaces) in multiple languages) cache.

[0057] In some embodiments, the request association strategy described above is used to associate requests in terms of time dimension and request type dimension.

[0058] In the above step S220, according to the pre-configured request association strategy, the previous associated request associated with the above-mentioned target request is searched in the pre-stored existing request records, including: for the pre-stored existing request records, double matching of the request time and type identifier is performed according to the above-mentioned request association strategy to obtain a previous associated request that matches both the time dimension and the request type dimension.

[0059] When this step is executed by the terminal device, the existing request records can be stored locally on the terminal device; or the existing request records can be stored in some external data storage service. The terminal device then calls the data storage service to search for the prior associated request from the existing request records. For example, the terminal device initiates a search request to the data storage service end, and the data storage service end feeds back to the terminal device the result of whether the prior associated request exists and the prior request data under the condition that it exists.

[0060] When this step is executed by the server, the existing request records may be stored in a database accessible to the server (a database of the server itself or third-party data, etc.) or in a local cache.

[0061] According to an embodiment of the present disclosure, the request association policy includes at least one kind of rule information among first rule information, second rule information, third rule information and fourth rule information.

[0062] First rule information: When the request processing interfaces corresponding to multiple requests are the same interface and the time interval between the multiple requests is less than a set threshold, the multiple requests are considered to be associated. For example, referring to the example of request Q11 and Q12 being associated requests described later, the request processing interfaces corresponding to request Q11 and request Q12 are the same interface.

[0063] Second rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a calling relationship between the request processing interfaces corresponding to the above multiple requests, and the time interval between the above multiple requests is less than the set threshold, the above multiple requests are deemed to be associated. The above calling relationship can be a calling relationship between partial data, or a calling relationship between interface functions, for example, part of the verification function of a request processing interface needs to call the relevant data of another request processing interface; or part of the verification function of a request processing interface needs to call the relevant function of another request processing interface. For example, you can refer to the example of request Q13 and request Q14 being associated requests described later; the corresponding is the calling relationship between the processing interface corresponding to request Q14 and part of the data in request Q13.

[0064] Third rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a routing relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are considered to be associated. For example, the example described later that request Q15 and request Q16 are associated requests can be referred to; the corresponding one is that there is a routing relationship between the processing interface corresponding to request Q16 and the processing interface of request Q15.

[0065] Fourth rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is data overlap between the data verification scenarios corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are considered to be associated. For example, you can refer to the example of request Q13 and request Q14 being associated requests described later; there is data overlap between the data verification scenario for securities account opening corresponding to request Q13 and the data verification scenario for registration account binding payment account corresponding to request Q14.

[0066] In some embodiments, the target request and the prior association request belong to: requests that correspond to each other in time sequence in the same information verification scenario. A target request may correspond to one or more prior association requests.

[0067] For example, taking the above-mentioned information declaration application as an example, the user needs to complete filling in the information of the set fields on 3 pages and click the submit function button before centralized verification of all the declared information can be performed.

[0068] In the embodiment of the present disclosure, when the execution subject is a server, the user fills in the first page of information in the information declaration application of the terminal device at time t1 and clicks the information verification function button. At this time, the terminal device sends the t1 time request to the server; accordingly, the server receives the t1 time request Q11 for verifying the first page of information. Afterwards, the user fills in the second page of information at time t2 (t2 is later than t1) and clicks the information verification function button. At this time, the terminal device sends the t2 time request to the server; accordingly, the server receives the t2 time request Q12 for verifying the first two pages of information (including the information of the first and second pages).

[0069] When the execution subject is a terminal device, similar to the process described above, the user completes filling in the first page of information in the information declaration application of the terminal device at time t1 and clicks the information verification function button. At this time, the terminal device is deemed to have received the request Q11 at time t1 for verifying the information on page 1. The user completes filling in the second page of information at time t2 and clicks the information verification function button. At this time, the terminal device is deemed to have received the request Q12 at time t2 for verifying the first two pages of information.

[0070] In the above embodiment, the request Q12 at time t2 can be used as an example of a target request, and the request Q11 at time t1 can be used as an example of a previous associated request of the target request.

[0071] In other embodiments, the target request and the prior associated request belong to: requests that correspond to each other in sequence in an associated information verification scenario. In the following description, the situation where the execution subject is a server or a terminal device is no longer described in detail, and only examples of prior associated requests and target requests in the associated information verification scenario are introduced from the perspective of usage scenarios. The associated information verification scenario may cover: there is a calling relationship between the request processing interfaces corresponding to multiple requests, there is a routing relationship between the request processing interfaces corresponding to multiple requests (for example, a request processing interface reaches a certain execution logic or execution result, an interface jump occurs, and jumps to another request processing interface), and there is data intersection between the data verification scenarios corresponding to multiple requests, etc., which may correspond to the examples of the second rule information to the fourth rule information mentioned above.

[0072] For example, in the scenario of opening a securities account and binding a payment account, at time t3, the user enters the account opening application information in the securities application and submits it, initiating an account opening request Q13 (the execution subject can be a terminal device or a server, which can be understood by referring to the above example). Among them, the entered account opening application information includes: user mobile phone number, user ID card, user password, user email address and other information. Afterwards, at time t4 (t4 is later than t3), the user logs in to the successfully registered securities account and initiates a request Q14 to bind the payment account. The information carried in the request Q14 includes user mobile phone number, user ID card, user password, payment account number and other information.

[0073] In the above embodiment, request Q14 is taken as an example of a target request, and request Q13 is taken as an example of a prior association request.

[0074] For example, in a scenario where a developer authorizes some development projects to be shared and other developers access the shared development projects, at time t5, user A tests a development project X in a development application, sets the development project X as a shared project, and submits a project sharing request Q15 (the execution subject can be a terminal device or a server, which can be understood by referring to the above example). Afterwards, at time t6 (t6 is later than t5), user B logs in to the development account and initiates an access request Q16 for the shared project X based on the shared information.

[0075] In the above embodiment, request Q16 is taken as an example of a target request, and request Q15 is taken as an example of a prior association request.

[0076] In step S231, when the previous association request is found, the previous request data of the previous association request is compared with the target request data according to the pre-configured verification strategy to obtain the information verification result for the target request. This step is performed by the terminal device or the server.

[0077] In the embodiment of the present disclosure, the request data corresponding to the target request is described as the target request data, and the request data corresponding to the prior association request is described as the prior request data. Both the target request data and the prior request data can be in the form of a json (a lightweight data exchange format) string.

[0078] Among them, there is at least one identical field between the prior request data and the target request data. For example, referring to the corresponding example of request Q11 and request Q12, request Q12 is a target request, and the corresponding target request data includes page 1 information and page 2 information, and request Q11 is a prior association request, and the corresponding prior request data includes page 1 information. All fields included in page 1 between the two are the same, that is, there are overlapping fields between the target request data and the prior request data.

[0079] For example, you can also refer to the examples corresponding to the above request Q13 and request Q14, request Q14 is the target request, Q13 is the prior association request, and the overlapping fields between the target request data and the prior request data include: user mobile phone number, user ID card and user password.

[0080] Based on the correlation of overlapping fields between previous and subsequent requests, it is possible to transform a one-time centralized verification into a comparison verification of multiple requests with content inclusion or content intersection relationships, thereby reducing the complexity of subsequent information verification requests. Compared with unified verification, it can improve the timeliness of information verification processing and reduce verification waiting time. In specific application scenarios, for the same information verification scenario, users do not need to enter all field information before submitting for verification. It supports initiating information verification requests during the process of entering partial field information.

[0081] In the embodiment including the above steps S210, S220 and S231, based on the idea of ​​sequentially associating and comparing multiple requests, by storing the relevant data of the previous request in the existing request record, according to the pre-configured request association strategy, the previous associated request associated with the target request is searched in the existing request record, and the previous request data corresponding to the previous associated request and the target request data have at least one identical field, that is, an overlapping field. Based on the correlation of the overlapping fields between the previous and next requests, it is possible to transform the one-time centralized verification into multiple comparison verifications of requests with content inclusion relationships or content intersection relationships, thereby reducing the complexity of the subsequent request information verification, and compared with the unified verification, it is possible to improve the timeliness of the information verification processing and reduce the verification waiting time. In a specific application scenario, for the same information verification scenario, the user does not need to enter all the field information before submitting for verification, and supports initiating a request for information verification during the process of entering part of the field information.

[0082] Figure 4 The flowchart of the information verification method according to another embodiment of the present disclosure is schematically shown. Figure 7 The following schematically shows the implementation process of the information verification method according to the embodiment of the present disclosure. Figure 7 In FIG. 1 , a single-dot dash arrow and a double-dot dash arrow are used to indicate two different execution paths. Sequence numbers ① and ② are used to indicate two possible paths for the same field. For a certain field, the branch corresponding to path ① or ② is executed.

[0083] According to the embodiments of the present disclosure, referring to Figure 4 and Figure 7 As shown, in the processing of the same request, the above method may include steps S210, S220, S232 and S242; in the processing of multiple requests, different branch situations may be included at the same time, that is, the above method includes the above steps S210, S220, S231, S232 and S242.

[0084] In step S232, when the previous association request cannot be found, the entered information in the target request data is parsed to obtain the information field.

[0085] The target request data includes: an attribute field corresponding to the requested attribute information and an information field corresponding to the entered information.

[0086] In step S242, the value of the above information field is verified to obtain the information verification result for the above target request.

[0087] For example, if in the above step S210, request Q11 is used as the target request at the current moment, then after executing step S220 for request Q11, the result obtained is that the corresponding prior associated request cannot be found, then the steps corresponding to steps S232 and S242 are executed. In step S232, it is necessary to parse the information on page 1 corresponding to request Q11 to obtain the values ​​corresponding to the fields in page 1. As an example, after parsing, the following fields and corresponding values ​​are obtained: mobile phone number: XXXXXXXXXXX, IP address: 168.XXX.X.XX; home address: YYYYYY, email address: XXXXX.xxx.com, etc. In step S242, the information of the parsed fields is verified by calling the verification service or based on the preset verification logic to obtain the information verification result for the request Q11. Compared with the method of one-time centralized verification of all information, the method of the embodiment of the present disclosure supports the initiation of information verification requests during the process of entering partial field information, and can also improve the processing time efficiency and reduce the complexity of verification processing when facing the first verification scenario containing partial fields.

[0088] Figure 5 The flowchart of the information verification method according to another embodiment of the present disclosure is schematically shown.

[0089] According to an embodiment of the present disclosure, the information verification method may further include the following steps: S510 and S520 in addition to the above steps S210, S220 and S231, or the above steps S210, S220, S232 and S242; or the above steps S210, S220, S231, S232 and S242. Figure 5 As shown, only steps S510 and S520 are illustrated.

[0090] In step S510, a corresponding target request record identifier is allocated to the target request.

[0091] The request record identifier is used to indicate the unique number for storing each request, and the request record corresponding to each request can be located based on the request record identifier. The existing request records can be in one data table or in different data tables, and different data tables or different storage areas in the data tables are divided based on the request record identifier.

[0092] In step S520, based on the target request record identifier, the target request data and the corresponding information verification result are stored in the existing request record, which is specifically manifested as adding a record corresponding to the target request in the existing request record.

[0093] The above target request data includes request attribute information and input information. The request attribute information includes but is not limited to: target type identification of the target request, target request time, target request address, etc. For ease of comparison, refer to Figure 3 As shown, the request time and type identifier in the request data are listed separately, for example, they can be placed in the key information of the data storage structure.

[0094] In some embodiments, reference Figure 3 and Figure 7 As shown, the above-mentioned existing request record also includes: information verification results and remark information corresponding to the existing request, and the remark information can be used to supplement the relevant description content of the request. In some embodiments, the specific implementation process of the above-mentioned steps S510 and S520 is as follows: after executing step S210, execute step S510, and then execute part of step S520a in step S520: based on the target request record identifier, store the target type identifier, target request time and target request data of the target request in the existing request record; then, after executing step S231 or S232, execute step S520b, based on the target request record identifier, also store the corresponding information verification result in the existing request record.

[0095] The relevant data of each request includes attribute information of the request, such as request time, type identifier, etc., and content information of the request, such as request data and information verification results, etc. By storing the relevant data corresponding to each request in the existing request record, after subsequently receiving the target request associated with the previously associated request, the target request data of the target request can be compared and verified based on the relevant data about the previously associated request in the existing request record.

[0096] In some embodiments, the attribute information of the verification policy includes: a policy type, and the policy type is used to match verification requests under different request types; the content information of the verification policy includes: verification logic.

[0097] In the above step S231, according to the pre-configured verification strategy, the previous request data of the above previous association request and the above target request data are compared to obtain the information verification result for the above target request, including:

[0098] For a pre-configured policy table, matching the request type of the target request with the policy type of the verification policy to obtain a verification policy matching the target request; the policy table includes at least one verification policy and at least one request association policy;

[0099] Based on the verification logic in the matching verification strategy, an information comparison and verification is performed between the above-mentioned prior request data and the above-mentioned target request data to obtain the above-mentioned information verification result.

[0100] For example, in some embodiments, the verification strategy includes: risk control verification strategy and content verification strategy. The verification logic of the verification strategy includes: risk control verification logic and content verification logic. In some embodiments, the risk control verification logic may include verification logic for the first common field. The content verification logic may include verification logic for the second common field and the incremental verification field.

[0101] In this embodiment, the verification strategy is stored in a strategy table, which is pre-configured by a user (e.g., business personnel, operations personnel, developers, or maintenance personnel, etc.), and can configure request association strategies and verification strategies for at least one information verification scenario; when configuring request association strategies and verification strategies for multiple information verification scenarios, the strategy type can be used to distinguish and identify the strategies corresponding to different information verification scenarios, and the mapping relationship between the strategy identifier and the request type is stored at the same time, so as to facilitate matching and searching the corresponding strategy according to the request type. In some embodiments, in the face of different scenarios, the request association strategies can be the same (in most cases, they are the same) or different; in the face of different scenarios, the verification strategies are different in most cases.

[0102] In the case where there are multiple request association policies, the following steps may also be included: for a pre-configured policy table, matching the request type of the target request with the policy type of the request association policy to obtain a request association policy matching the target request.

[0103] Figure 6 The detailed implementation flow chart of step S231 according to the embodiment of the present disclosure is schematically shown.

[0104] According to the embodiments of the present disclosure, referring to Figure 6 Solid wireframe and Figure 7 As shown, in the above step S231, according to the pre-configured verification strategy, the previous request data of the above-mentioned previous associated request and the above-mentioned target request data are compared to obtain the information verification result for the above-mentioned target request, including the following steps: S610, S621, S631 and S640.

[0105] The above-mentioned target request data includes: request attribute information and entered information. As an example, the fields included in the target request data include: type identification, request address (such as IP address, city or region corresponding to IP address, etc.), request account (such as mobile phone number, ID card number, user name, etc.), request time, fields corresponding to entered information, etc. (such as fields K1 to K6), etc.

[0106] In step S610, according to the risk control verification strategy, the value of the first common field in the previous request data and the target request data is compared to obtain a risk control verification result.

[0107] The first common field belongs to the request attribute information, that is, the request attribute information includes the first common field. For example, the first common field is part or all of the fields commonly included in the prior association request and the target request, such as the request address and the request account as an example of the first common field.

[0108] The first common field is a field specified by the pre-configured policy usage scope. For example, the pre-configured policy application scope may specify a field identifier, and may further specify at least one of the field filter number or the field selection time.

[0109] The risk control verification strategy can be a deformation strategy or an IP strategy, etc. For example, in the deformation strategy, if the last digit of the mobile phone number changes within a preset range (for example, changes 1-3 numbers), it is considered a risky access, and the corresponding risk control verification result is verification failure. For example, if the request account corresponding to the previous association request uses the mobile phone number 12345678901, and the request account corresponding to the target request uses the mobile phone number 12345678902, it will be considered a risky access. For example, in the IP strategy, if the IP address of the previous association request is identified as Beijing, and the IP address of the target request is identified as Shanghai, it will be considered a risky access.

[0110] In step S621, when the risk control verification result is passed, according to the content verification strategy, based on the verified result in the previous request data, the value of the second common field in the target request data is verified to obtain a consistency verification result.

[0111] The entered information includes the second common field and the incremental field to be verified. Among them, the fields commonly included in the verified result of the previous associated request and the target request are the second common fields. The entered information is part or all of the complete submitted information. The complete submitted information is the submission information corresponding to the completion of all fields in the data verification scenario corresponding to the target request.

[0112] During the consistency verification process in step S621, the value of the second common field that has been verified in the above-mentioned prior request data is used as a reference value to verify whether the value of the above-mentioned second common field in the above-mentioned target request data is consistent with the above-mentioned reference value to obtain a consistency verification result.

[0113] For example, the entered information of the first associated request includes the value entry information of the fields K1, K2, K3 and K4. The value of field K1 is the verified value: V11, the value of field K2 is the verified value V21, the value of field K3 is V31 which is not verified, and the value of field K4 is V41 which is verified. The target request includes the fields K1, K2, K3, K4, K5 and K6, and the corresponding values ​​are V12, V22, V32, V42, V51 and V61 respectively.

[0114] In this case, the verified results of the prior associated request include: the value results corresponding to fields K1, K2 and K4; the fields K1, K2, K3, K4, K5 and K6 contained in the target request are intersected with fields K1, K2 and K4, and the commonly included fields are K1, K2 and K4. Then the second common field in the target request data is; fields K1, K2 and K4. The values ​​V11, V21 and V41 of the fields K1, K2 and K4 in the prior association request data are used as reference values, and the corresponding verification fields K1, K2 and K4 values ​​V12, V22 and V42 are respectively verified to see if they are consistent with V11, V21 and V41. When the three comparison results are all consistent, the consistency verification result is verification passed; if at least one of the three comparison results (the comparison result of V12 and V11, the comparison result of V22 and V21, and the comparison result of V42 and V41) is inconsistent, the consistency verification result is verification failed.

[0115] In step S631, when the consistency verification result is passed, the incremental verification field in the target request data is verified to obtain an incremental verification result.

[0116] According to an embodiment of the present disclosure, the incremental fields to be verified include at least one of the following: a first field to be verified and a second field to be verified; in the entered information of the target request, compared with the different fields in the prior associated request, these different fields serve as the first field to be verified; in the entered information of the target request, one or more identical fields are commonly contained in the prior associated request and the prior associated request fails the value verification for these identical fields, and these identical fields serve as the second field to be verified.

[0117] In some embodiments of the present disclosure, in the entered information of the target request, a field that is different from that in the previous associated request is the first field to be verified.

[0118] In some other embodiments of the present disclosure, if the entered information of the target request contains one or more identical fields that are common to the prior associated request and the values ​​of these identical fields in the prior associated request have not been verified, then these identical fields are the second fields to be verified.

[0119] The incremental verification field in the target request data is verified to obtain the incremental verification result, including:

[0120] In the case where the incremental field to be verified is the second field to be verified, compare the value of the second field to be verified in the target request data with the value of the same field in the previous association request to see if they are the same; if they are the same, determine that the information verification result is not passed; if they are different, call the relevant service or verify the second field to be verified according to the preset logic to obtain the incremental verification result for the second field to be verified;

[0121] In the case that the incremental field to be verified is the first field to be verified, a related service is called or the first field to be verified is verified according to a preset logic to obtain an incremental verification result for the first field to be verified.

[0122] For example, if the prior association request and the target request have one or more fields Z in common and the values ​​of these fields Z in the prior association request have not been verified, then these fields Z serve as the second fields to be verified.

[0123] As an example, if the value of a field Z in the previous association request has not passed the verification, and there is a value for the field Z in the entered information of the target request, then the field Z of the target request needs to be used as the second field to be verified for subsequent verification. During the verification process, first compare the value of the field Z in the target request and the value of the field Z in the previous association request to see if they are the same. If they are the same, it can be directly determined that the value verification in the field has failed, and the corresponding information verification result is failed; if they are different, the value Z of the field needs to be verified, for example, by calling related services or according to preset logic. If the verification passes, the corresponding incremental verification result of the field is verification passed.

[0124] For example, continuing with the above embodiment, compared with the prior association request, the target request includes different fields, namely fields K5 and K6, as the first fields to be verified; in addition, the target request and the prior association request both include field K3 and the result for field K3 in the prior association request has not been verified, then field K3 in the target request serves as the second field to be verified.

[0125] The values ​​V32, V51 and V61 corresponding to the fields K3, K5 and K6 are verified respectively.

[0126] For the verification of field K3, first compare the value V32 of field K3 in the target request with the value V31 of field K3 in the previous associated request to see if they are the same. If they are the same, it is determined that the value verification of field K3 fails, that is, the incremental verification result of field K3 fails. At this time, regardless of the verification results of fields K5 and K6, it can be determined that the information verification result corresponding to the corresponding target request fails. If they are different, the value of field K3 can be verified by calling related services or according to preset logic to obtain the incremental verification result of K3.

[0127] In some embodiments, during the verification process for multiple fields, each field may be verified one by one, and the next field may be verified after the verification of the previous field is completed.

[0128] In step S640, a corresponding information verification result is obtained according to the above incremental verification result.

[0129] If the incremental verification results of all incremental fields to be verified are passed, the corresponding information verification result is passed; if the incremental verification result of at least one incremental field to be verified is failed, the corresponding information verification result is failed.

[0130] Reference Figure 6 As shown in the dashed box, in some embodiments, the above step S231 also includes at least one step corresponding to the following negative branch: S622, S632. For the same request, only one of the positive branch and the negative branch is executed. In the case of multiple requests, there are multiple branch steps that exist at the same time.

[0131] In step S622, when the above-mentioned risk control verification result is verification failure, it is determined that the information verification result is verification failure.

[0132] In step S632, when the consistency verification result is verification failure, it is determined that the information verification result is verification failure.

[0133] For a target request, in an embodiment including the above steps S610, S621, S631 and S640, or in an embodiment including steps S610 and S622, or in an embodiment including steps S610, S621 and S632, by setting two layers of verification logic, verification is first performed based on the risk control verification strategy, and then content verification is performed based on the content verification strategy; if the risk control verification fails, there is no need to perform subsequent content verification, which saves the time cost corresponding to verifying all information, and the verification process is efficient and accurate; in addition, in the process of content verification, based on the idea of ​​step-by-step verification and making full use of the association of the same fields, first based on the verified results in the above-mentioned prior request data, the value of the second common field in the above-mentioned target request data is verified to obtain a consistency verification result; if the consistency verification result passes, the incremental to-be-verified field is verified again, making full use of the association between the same fields between the prior association request and the target request, improving the verification efficiency, and simplifying the verification logic; if the verification results of a certain same field are inconsistent, it can be directly determined that the information verification result for the target request is not passed.

[0134] Among them, the request attribute information is used as the verification field of the risk control verification strategy, and the request content information is used as the verification field of the content verification strategy. Risk control verification can be performed first based on the request attribute information (for example, when executed by the server, it is generally in the message header of the target request data; when executed by the terminal device, it can be directly identified by the terminal device during the request initiation process). If the risk control verification fails, there is no need to parse the content of the request (for example, when executed by the server, it is generally in the message body of the target request data; when executed by the terminal device, it can be identified by the terminal device during the user input process), which greatly improves the timeliness of the verification.

[0135] A second exemplary embodiment of the present disclosure provides an apparatus for information verification.

[0136] Figure 8 The structure block diagram of the information verification device according to an embodiment of the present disclosure is schematically shown.

[0137] Reference Figure 8 As shown, the information verification device 800 provided by the embodiment of the present disclosure includes: a request receiving module 801, an associated request search module 802, and a comparison and verification module 803.

[0138] The request receiving module 801 is used to receive a target request for information verification, and the target request carries target request data.

[0139] The above-mentioned associated request search module 802 is used to search for the previous associated request associated with the above-mentioned target request in the pre-stored existing request records according to the pre-configured request association strategy; the above-mentioned request association strategy is used to describe the rules for association between multiple requests.

[0140] The comparison and verification module 803 is used to compare the previous request data of the previous association request with the target request data according to a pre-configured verification strategy when the previous association request is found, so as to obtain an information verification result for the target request.

[0141] According to an embodiment of the present disclosure, the above-mentioned device 800 further includes: a parsing module and a verification module.

[0142] The above-mentioned parsing module is used to parse the above-mentioned target request data when the above-mentioned prior association request cannot be found to obtain the parsed fields, and the above-mentioned fields include: attribute fields corresponding to the request attribute information and information fields corresponding to the entered information.

[0143] The verification module is used to verify the value of the information field to obtain the information verification result for the target request.

[0144] According to an embodiment of the present disclosure, the above-mentioned device 800 further includes: a record updating module.

[0145] The record updating module is used to: assign a corresponding target request record identifier to the target request; based on the target request record identifier, store the target request data and the corresponding information verification result into the existing request record.

[0146] According to an embodiment of the present disclosure, the above-mentioned request association strategy is used to associate requests in the time dimension and the request type dimension; the above-mentioned existing request record contains the following information: request time and type identifier, and the above-mentioned type identifier is at least one of a request processing interface identifier or a data verification scenario identifier.

[0147] The above-mentioned process, according to the pre-configured request association strategy, searches for the prior associated request associated with the above-mentioned target request in the pre-stored existing request records, including: for the pre-stored existing request records, performing a double match of the request time and type identifier according to the above-mentioned request association strategy, and obtaining a prior associated request that matches both the time dimension and the request type dimension.

[0148] According to an embodiment of the present disclosure, the request association strategy includes at least one of the first rule information, the second rule information, the third rule information and the fourth rule information. First rule information: When the request processing interface corresponding to the multiple requests is the same interface and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated. Second rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a call relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated. Third rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a routing relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated. Fourth rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is data intersection between the data verification scenarios corresponding to the multiple requests, and the time interval between the multiple requests is less than the set threshold, the multiple requests are deemed to be associated.

[0149] In some embodiments, the above verification strategy includes: a risk control verification strategy and a content verification strategy.

[0150] The comparison and verification module 803 includes: a risk control verification module and a content verification module.

[0151] The risk control verification module is used to: compare the values ​​of the first common field in the previous request data and the target request data according to the risk control verification strategy to obtain a risk control verification result.

[0152] The above-mentioned content verification module is used for: when the above-mentioned risk control verification result is passed, according to the above-mentioned content verification strategy, based on the verified result in the above-mentioned prior request data, verifying the value of the second common field in the above-mentioned target request data to obtain a consistency verification result; when the above-mentioned consistency verification result is passed, verifying the incremental to-be-verified field in the above-mentioned target request data to obtain an incremental verification result; based on the above-mentioned incremental verification result, obtaining the corresponding information verification result.

[0153] According to an embodiment of the present disclosure, the above-mentioned risk control verification module is also used to: when the above-mentioned risk control verification result is verification failure, determine that the information verification result is verification failure.

[0154] The content verification module is further used to: when the consistency verification result is verification failure, determine that the information verification result is verification failure.

[0155] According to an embodiment of the present disclosure, according to the above-mentioned content verification strategy, based on the verified result in the above-mentioned prior request data, the value of the second common field in the above-mentioned target request data is verified to obtain a consistency verification result, including: taking the value of the second common field that has been verified in the prior request data as a reference value, verifying whether the value of the second common field in the target request data is consistent with the reference value, and obtaining a consistency verification result.

[0156] According to an embodiment of the present disclosure, the above-mentioned target request data includes: request attribute information and entered information; the above-mentioned request attribute information includes the above-mentioned first common field, and the above-mentioned entered information includes the above-mentioned second common field and the above-mentioned incremental field to be verified; wherein the above-mentioned entered information is part or all of the complete submitted information, and the above-mentioned complete submitted information is the submission information corresponding to the completion of filling in all fields in the data verification scenario corresponding to the above-mentioned target request; the above-mentioned first common field is a field specified by the pre-configured policy usage scope.

[0157] According to an embodiment of the present disclosure, the above-mentioned incremental fields to be verified include at least one of the following: a first field to be verified, a second field to be verified; in the entered information of the target request, compared with the different fields in the previous associated request, these different fields serve as the first field to be verified; in the entered information of the target request, one or more identical fields are commonly contained in the previous associated request and the previous associated request fails the value verification for these identical fields, and these identical fields serve as the second field to be verified. Among them, the incremental field to be verified in the above-mentioned target request data is verified to obtain an incremental verification result, including: when the above-mentioned incremental field to be verified is the second field to be verified, comparing whether the value of the second field to be verified in the above-mentioned target request data is the same as the value of the same field in the previous associated request; when they are the same, determining that the above-mentioned information verification result is failed; when they are different, calling related services or verifying the above-mentioned second field to be verified according to preset logic to obtain an incremental verification result for the second field to be verified; when the above-mentioned incremental field to be verified is the first field to be verified, calling related services or verifying the above-mentioned first field to be verified according to preset logic to obtain an incremental verification result for the first field to be verified.

[0158] According to an embodiment of the present disclosure, the attribute information of the above verification policy includes: a policy type, and the above policy type is used to match verification requests under different request types; the content information of the above verification policy includes: verification logic.

[0159] The above-mentioned device 800 also includes: a strategy matching module.

[0160] The policy matching module is used to: match the request type of the target request with the policy type of the verification policy according to the pre-configured policy table to obtain the verification policy matching the target request; the policy table includes at least one verification policy and at least one request association policy.

[0161] The comparison and verification module 803 is used to: perform information comparison and verification between the previous request data and the target request data based on the verification logic in the matching verification strategy to obtain the information verification result.

[0162] Any number of the functional modules included in the above-mentioned device 800 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. At least one of the functional modules included in the device 800 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the functional modules included in the device 800 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0163] A third exemplary embodiment of the present disclosure provides an electronic device.

[0164] Fig. 9 The structural block diagram of the electronic device provided by the embodiment of the present disclosure is schematically shown.

[0165] Reference Fig. 9 As shown, the electronic device 900 provided by the embodiment of the present disclosure includes a processor 901, a communication interface 902, a memory 903 and a communication bus 904, wherein the processor 901, the communication interface 902 and the memory 903 communicate with each other through the communication bus 904; the memory 903 is used to store computer programs; the processor 901 is used to implement the information verification method as described above when executing the program stored in the memory.

[0166] The fourth exemplary embodiment of the present disclosure further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the information verification method described above is implemented.

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

[0168] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0169] It should be noted that the collection, collection, update, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution provided by the embodiments of the present disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

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

[0171] The foregoing is merely a specific embodiment of the present disclosure, which enables those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features applied herein.

Claims

1. A method for information verification, characterized in that: include: receiving a target request for information verification, the target request carrying target request data; According to a pre-configured request association strategy, searching for a previous association request associated with the target request in pre-stored existing request records; The request association policy is used to describe the rules for association between multiple requests; When the prior association request is found, the prior request data of the prior association request and the target request data are compared according to a pre-configured verification strategy to obtain an information verification result for the target request; wherein, the prior request data and the target request data have at least one identical field.

2. The method according to claim 1, characterized in that The request association strategy is used to associate requests in the time dimension and the request type dimension; The existing request record includes the following information: request time and type identifier, where the type identifier is at least one of a request processing interface identifier and a data verification scenario identifier; The step of searching, according to a pre-configured request association strategy, a previous association request associated with the target request in pre-stored existing request records includes: For the pre-stored existing request records, a double match of the request time and type identifier is performed according to the request association strategy to obtain a previous associated request that matches both the time dimension and the request type dimension.

3. The method according to claim 2, characterized in that The request association policy includes at least one of the following rule information: First rule information: when the request processing interface corresponding to the multiple requests is the same interface and the time interval between the multiple requests is less than a set threshold, the multiple requests are considered to be associated; Second rule information: when the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a calling relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than a set threshold, the multiple requests are deemed to be associated; Third rule information: when the request processing interfaces corresponding to the multiple requests are different interfaces, and there is a routing relationship between the request processing interfaces corresponding to the multiple requests, and the time interval between the multiple requests is less than a set threshold, the multiple requests are deemed to be associated; Fourth rule information: When the request processing interfaces corresponding to the multiple requests are different interfaces, and there is data overlap between the data verification scenarios corresponding to the multiple requests, and the time interval between the multiple requests is less than a set threshold, the multiple requests are deemed to be associated.

4. The method according to claim 1, characterized in that: The verification strategy includes: risk control verification strategy and content verification strategy; The comparing, according to the pre-configured verification strategy, the previous request data of the previous association request and the target request data to obtain the information verification result for the target request includes: According to the risk control verification strategy, compare the values ​​of the first common field in the prior request data and the target request data to obtain a risk control verification result; When the risk control verification result is a passed verification, according to the content verification strategy, based on the verified passed result in the previous request data, the value of the second common field in the target request data is verified to obtain a consistency verification result; If the consistency verification result is that the verification is passed, verify the incremental to-be-verified field in the target request data to obtain an incremental verification result; According to the incremental verification result, a corresponding information verification result is obtained.

5. The method according to claim 4, characterized in that The target request data includes: request attribute information and entered information; the request attribute information includes the first common field, and the entered information includes the second common field and the incremental verification field; The entered information is part or all of the complete submitted information, and the complete submitted information is the submitted information corresponding to all fields in the data verification scenario corresponding to the target request that have been filled in; The first common field is a field specified by a pre-configured policy usage scope.

6. The method according to claim 5, characterized in that The incremental to-be-verified field includes at least one of the following: a first to-be-verified field and a second to-be-verified field; in the entered information of the target request, compared with the different fields in the previous associated request, these different fields are used as the first to-be-verified fields; In the input information of the target request, if there are one or more identical fields in common with the previous association request and the previous association request fails the value verification for these identical fields, these identical fields are used as the second fields to be verified; The incremental verification field in the target request data is verified to obtain an incremental verification result, including: In the case where the incremental field to be verified is the second field to be verified, comparing whether the value of the second field to be verified in the target request data is the same as the value of the same field in the previous association request; In the same case, determining that the information verification result is failed; In different situations, calling a related service or verifying the second field to be verified according to a preset logic to obtain an incremental verification result for the second field to be verified; In the case that the incremental field to be verified is the first field to be verified, the first field to be verified is verified by calling a related service or according to a preset logic to obtain an incremental verification result for the first field to be verified.

7. The method according to claim 4, characterized in that The step of comparing the previous request data of the previous association request with the target request data according to the pre-configured verification strategy to obtain an information verification result further includes: In the case where the risk control verification result is verification failure, determining that the information verification result is verification failure; When the consistency verification result is verification failure, it is determined that the information verification result is verification failure.

8. The method according to claim 1, characterized in that The attribute information of the verification policy includes: a policy type, which is used to match verification requests under different request types; the content information of the verification policy includes: verification logic; The comparing, according to the pre-configured verification strategy, the previous request data of the previous association request and the target request data to obtain the information verification result for the target request includes: For a pre-configured policy table, matching the request type of the target request with the policy type of the verification policy to obtain a verification policy matching the target request; the policy table includes at least one verification policy and at least one request association policy; Based on the verification logic in the matching verification strategy, an information comparison verification is performed between the prior request data and the target request data to obtain the information verification result.

9. The method according to claim 1, characterized in that: Also includes: If the prior association request cannot be found, the target request data is parsed to obtain the parsed fields, the fields including: an attribute field corresponding to the request attribute information and an information field corresponding to the entered information; The value of the information field is verified to obtain an information verification result for the target request.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: Allocating a corresponding target request record identifier to the target request; Based on the target request record identifier, the target request data and the corresponding information verification result are stored in the existing request record.

11. An information verification device, characterized in that: include: A request receiving module, used for receiving a target request for information verification, wherein the target request carries target request data; An associated request search module, configured to search for a previous associated request associated with the target request in pre-stored existing request records according to a pre-configured request association strategy; The request association policy is used to describe the rules for association between multiple requests; A comparison and verification module is used to compare the previous request data of the previous association request and the target request data according to a pre-configured verification strategy when the previous association request is found, so as to obtain an information verification result for the target request; wherein the previous request data and the target request data have at least one identical field.

12. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method according to any one of claims 1 to 10 when executing a program stored in a memory.

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

Images