Method and device for determining verification mode, electronic equipment and storage medium

By obtaining scene information and combining multi-objective evolution algorithms to determine the verification request type and method, the problem of mismatch in the verification methods in the existing technology is solved, and the security and user experience are improved.

CN119128839APending Publication Date: 2024-12-13BEIJING QIYI CENTURY SCI & TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202411102053.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-12-13

AI Technical Summary

Technical Problem

The random configuration of existing verification methods causes the scenario requirements to mismatch with the verification methods, affecting security and user experience.

Method used

By obtaining the scenario information to be updated, the verification request type and verification method are determined, and a multi-objective evolution algorithm is used to combine security indicator parameters and user experience indicator parameters to calculate the optimal solution combination information to determine the target verification method.

Benefits of technology

Effectively matching scenario information and verification methods improves security and user experience, and solves the problem of mismatch in verification methods under random configuration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119128839A_ABST
    Figure CN119128839A_ABST
Patent Text Reader

Abstract

The invention relates to a method and device for determining a verification mode, electronic equipment and a storage medium, and the method for determining the verification mode comprises the steps: obtaining to-be-updated scene information based on a verification updating instruction, determining a verification request type and a verification mode according to the scene information, and carrying out the target evolution through employing the verification request type and the verification mode, the verification combination information is obtained, and then the target verification mode corresponding to the verification request type is determined based on the verification combination information, so that the target verification mode matched with the verification request type is determined for the verification request type. The problem that the scene requirement is not matched with the verification mode when the verification mode is randomly configured in the prior art is solved, and the verification mode matched with the scene information can be effectively determined.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method, device, electronic device and storage medium for determining a verification method. Background Art

[0002] With the development of the Internet, the functions provided by various applications and the user information they require are also increasing. In order to protect the security of user information and the stable operation of applications, verification methods are usually set to identify whether the operation is done by a real person, so as to prevent scripts, black users or automated programs from adversely affecting user information or the operation of applications.

[0003] There are many existing verification methods, such as sliding verification, image and text verification, nine-square grid verification, and voice verification. The common purpose of these verification methods is to increase the network security protection layer and reduce identity theft, automated attacks and other types of network fraud; however, different verification methods have different security and user experience. For example, sliding verification is relatively simple and has a better user experience, but the security is low and it is easy to be cracked, while voice verification has higher security and is not easy to be cracked, but its verification process is complicated, resulting in a poor user experience. The existing verification method configuration is usually randomly configured, and different scenarios have different security requirements, which will lead to the problem of mismatch between scenario requirements and verification methods. Summary of the invention

[0004] In order to solve the problem of mismatch between scenario requirements and verification methods in the existing related technologies using random configuration verification methods, the present application provides a method, device, electronic device and storage medium for determining a verification method.

[0005] In a first aspect, the present application provides a method for determining a verification mode, comprising:

[0006] Based on the verification update instruction, obtain the scene information to be updated;

[0007] Determine the verification request type and verification method based on the scenario information;

[0008] The verification request type and the verification method are used to perform target evolution to obtain verification combination information;

[0009] Based on the verification combination information, a target verification mode corresponding to the verification request type is determined.

[0010] Optionally, at least two verification methods are included, and the verification request type and the verification method are used to perform target evolution to obtain verification combination information, including:

[0011] Based on the scenario information, determine the security index parameters and user experience index parameters corresponding to each of the verification methods;

[0012] The verification request type and the verification method are used, combined with the security index parameter and the user experience index parameter to perform target evolution, and obtain the verification combination information.

[0013] Optionally, at least two of the verification request types are included, and the verification request type and the verification method are used to perform target evolution in combination with the security index parameter and the user experience index parameter to obtain the verification combination information, including:

[0014] Configure one of the verification methods for each verification request type to obtain at least two pieces of combination information to be confirmed;

[0015] Determine, based on the scenario information, a security index weight corresponding to the security index parameter, and determine a user experience index weight corresponding to the user experience index parameter;

[0016] Using the security index parameter and the user experience index parameter, combined with the security index weight and the user experience index weight, an optimal solution set calculation is performed on each of the combination information to be confirmed to obtain the optimal solution combination information;

[0017] The verification combination information is generated by using the optimal solution combination information.

[0018] Optionally, the adopting of the security index parameter and the user experience index parameter, in combination with the security index weight and the user experience index weight, performing an optimal solution set calculation on each of the combination information to be confirmed to obtain the optimal solution combination information includes:

[0019] Determine the verification method allocation information corresponding to each of the combination information to be confirmed;

[0020] The security index parameter and the user experience index parameter are used, combined with the security index weight and the user experience index weight, to calculate the allocation score corresponding to the verification method allocation information;

[0021] The to-be-confirmed combination information corresponding to the target allocation score is determined as the optimal solution combination information, and the target allocation score represents the allocation score with the largest score.

[0022] Optionally, the adopting the verification request type and the verification mode, combining the security index parameter and the user experience index parameter to perform target evolution to obtain the verification combination information includes:

[0023] Obtain a preset multi-objective evolution model;

[0024] Inputting the verification request type, the verification method, the security index parameter and the user experience index parameter into the multi-objective evolution model;

[0025] The verification combination information is generated according to the model output result of the multi-objective evolution model.

[0026] Optionally, determining the verification request type and verification method according to the scenario information includes:

[0027] Determining a target scene area according to the scene information;

[0028] Based on the target scene area, extracting a verification request identifier;

[0029] The verification request type is determined according to the verification request identifier, and a verification method corresponding to the target scene area is obtained.

[0030] Optionally, extracting a verification request identifier based on the target scene area includes:

[0031] From the target scene area, obtain the requested data set within a preset time;

[0032] The verification request identifier is extracted from the request data set.

[0033] In a second aspect, the present application provides a device for determining a verification method, including:

[0034] An acquisition module, used for acquiring scene information to be updated based on the verification update instruction;

[0035] A first determination module, used to determine the verification request type and verification method according to the scenario information;

[0036] A target evolution module, used to perform target evolution using the verification request type and the verification method to obtain verification combination information;

[0037] The second determination module is used to determine a target verification method corresponding to the verification request type based on the verification combination information.

[0038] In a third aspect, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0039] Memory, used to store computer programs;

[0040] A processor is used to implement the method for determining the verification method described in any one of the first aspects when executing a program stored in a memory.

[0041] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for determining a verification method as described in any one of the first aspects is implemented.

[0042] The embodiment of the present application obtains the scene information to be updated based on the verification update instruction, and determines the verification request type and the verification method based on the scene information, so as to perform target evolution by using the verification request type and the verification method to obtain the verification combination information, and then determines the target verification method corresponding to the verification request type based on the verification combination information, thereby achieving the purpose of determining the target verification method that matches the verification request type, solving the problem of mismatch between the scene requirements and the verification method that exists in the existing related technology using the random configuration verification method, and being able to effectively determine the verification method that matches the scene information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0044] 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 the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0045] Figure 1 A flowchart of a method for determining a verification method provided in an embodiment of the present application;

[0046] Figure 2 A schematic diagram of the structure of a device for determining a verification method provided in an embodiment of the present application;

[0047] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0049] In order to protect the security of user information and the stable operation of applications, different verification methods are used in existing related technologies for risk control verification. The main function of risk control verification is to identify and verify the identity of users to prevent unauthorized access and fraud. Some common verification methods are: 1) Slide verification. Slide verification requires users to complete a sliding action on the screen through a mouse, touch screen or other input device; this verification method can distinguish between human users and automated programs, because computer programs find it difficult to imitate complex human gestures. Advantages: user-friendly, simple and fast operation, and little impact on user experience. Disadvantages: It is easier to be broken through by black industries. 2) Image verification: requires users to identify letters and numbers from distorted text or pictures and enter these characters; it is based on the idea that humans can recognize text that is difficult to read due to image noise, deformation, and occlusion, but most automated systems cannot do this; Advantages: prevent automated tools from performing spam attacks, spamming advertisements and other malicious behaviors, Disadvantages: more complicated operation. 3) Voice verification: Voice verification requires users to listen to a voice clip and input what they hear; this is usually used as an auxiliary verification method for users with limited vision, and can also be used as a substitute for traditional graphic verification codes; advantage: provides inclusiveness, allowing users with visual impairments to pass the verification, disadvantage: the operation takes a long time. 4) Nine-square grid verification: Nine-square grid verification is an interactive verification method, which usually requires users to verify by clicking the correct area in the nine-square grid according to prompts, such as finding specific items or icons in the picture; advantage: improves the ability to protect against automated program attacks, disadvantage: requires users to have a certain level of understanding.

[0050] The common purpose of the above verification methods is to increase the network security protection layer and reduce identity theft, automated attacks and other types of network fraud. At that time, using inappropriate verification methods in different scenarios will not only greatly reduce the user experience, but also fail to provide effective security protection. For example, in scenarios with high security requirements, using simple verification methods such as sliding verification will be easily attacked by automated programs and will not provide effective security protection. In scenarios with low security requirements, if complex verification methods such as voice verification are used, the user experience will be greatly reduced. The existing verification method configuration is usually randomly configured, which will cause the problem of mismatch between scenario requirements and verification methods.

[0051] In order to solve the problem of low efficiency of vehicle information query in the prior art, the present application provides a method, device, electronic device and storage medium for determining a verification method, which obtains scene information to be updated based on a verification update instruction, and determines the verification request type and verification method based on the scene information, so as to perform target evolution using the verification request type and verification method to obtain verification combination information, and then determines the target verification method corresponding to the verification request type based on the verification combination information, thereby achieving the purpose of determining a target verification method that matches the verification request type, solving the problem of mismatch between scene requirements and verification methods in the existing related technology using a random configuration verification method, and being able to effectively determine a verification method that matches the scene information.

[0052] Figure 1 A flow chart of a method for determining a verification method provided in an embodiment of the present application. The method can be applied to one or more electronic devices such as a client and a server. In addition, the execution subject of the method can be hardware or software. When the above-mentioned execution subject is hardware, the execution subject can be one or more of the above-mentioned electronic devices. For example, a single electronic device can execute the method, or a plurality of electronic devices can cooperate with each other to execute the method. When the above-mentioned execution subject is software, the method can be implemented as a plurality of software or software modules, or as a single software or software module. No specific limitation is made herein.

[0053] like Figure 1 As shown, the present application discloses an embodiment, providing a method for determining a verification mode, which may specifically include the following steps:

[0054] Step S110: based on the verification update instruction, obtaining the scene information to be updated;

[0055] Specifically, the verification update instruction may represent an instruction for inputting a verification method configuration update according to requirements, wherein the input method may be an instruction input by a developer according to requirements, or an instruction issued by a server, and of course may be other methods, which are not specifically limited in this embodiment; thereby, based on the verification update instruction, the scene information to be updated may be obtained, and the scene information to be updated represents information corresponding to the scene for which the verification method needs to be updated, and the scene information may represent specific scenarios such as application scenarios, specific interface scenarios of the application, mobile terminal scenarios, web terminal scenarios, etc., which are not specifically limited in this embodiment.

[0056] Step S120: Determine the verification request type and verification method based on the scenario information;

[0057] Specifically, after determining the scenario information, the verification request type and verification method can be determined based on the scenario information, wherein the verification request type indicates the request type that needs to be verified in the scenario represented by the scenario information, such as the web page scenario may include a login verification request type and a payment verification request type, etc.; and the verification method indicates the verification method that can be configured in the scenario represented by the scenario information, for example, the verification methods that can be configured in the web page scenario may include sliding verification and image verification, while the verification methods that can be configured in the mobile terminal scenario may include sliding verification, image verification, and voice verification, etc. It can be seen that in this embodiment, in the case of scenario information representing different scenarios, the same or different verification request types and verification methods can be determined, and both the verification request type and verification method can be one or more, and this embodiment does not make specific limitations on this.

[0058] Step S130: Use the verification request type and verification method to evolve the target and obtain verification combination information.

[0059] Specifically, after determining the verification request type and verification method, the verification request type and verification method can be used to perform target evolution to obtain verification combination information, wherein target evolution represents multi-objective evolution, and more specifically, a multi-objective evolutionary algorithm (Multi-Objective Evolutionary Algorithm, MOEA) can be used, and target evolution is used to determine the optimal solution, that is, to determine the verification method that best corresponds to the verification request type, so that the verification combination information can represent the optimal solution information including the verification method corresponding to the verification request type; and the present embodiment can include multiple verification request types and multiple verification methods, that is, the verification combination information can also represent the optimal solution information of the verification methods corresponding to each verification request type.

[0060] Step S140: Determine the target verification method corresponding to the verification request type based on the verification combination information.

[0061] Specifically, after obtaining the verification combination information, the target verification method corresponding to each verification request type can be extracted from the verification combination information, where the target verification method indicates the verification method of the optimal solution corresponding to the verification request type.

[0062] It can be seen that in this embodiment, the scene information to be updated is obtained through the verification update instruction, and the verification request type and verification method are determined based on the scene information, so as to determine the corresponding verification request type and verification method according to different scenarios, and use the verification request type and verification method to perform target evolution to obtain verification combination information, that is, the verification method corresponding to the optimal solution of each verification request type is calculated through target evolution, and then the target verification method corresponding to the verification request type is determined based on the verification combination information, thereby achieving the purpose of determining the matching target verification method for the verification request type, solving the problem of mismatch between scene requirements and verification methods in the existing related technology using random configuration verification methods, and being able to effectively determine the verification method that matches the scene information.

[0063] In an optional embodiment of the present application, step S130 uses the verification request type and verification method to evolve the target and obtain verification combination information, which may specifically include the following steps: based on the scenario information, determine the security indicator parameters and user experience indicator parameters corresponding to each verification method; use the verification request type and verification method, combine the security indicator parameters and user experience indicator parameters to evolve the target and obtain verification combination information.

[0064] In this embodiment, in the process of determining the verification request type and the verification method based on the scenario information, at least two verification methods can be determined, and then the security indicator parameters and user experience indicator parameters corresponding to each verification method can be determined based on the scenario information, wherein the security indicator parameter represents the parameter for indicating the security indicator configured in advance for the verification method according to the scenario, and the security indicator parameter represents the parameter for indicating the user experience indicator configured in advance for the verification method according to the scenario, that is, the same verification method may also have different security indicator parameters and user experience indicator parameters under different scenario information; thereby, the verification request type and the verification method can be used, combined with the security indicator parameters and the user experience indicator parameters to perform target evolution and obtain verification combination information, wherein the specific target evolution method can adopt the MOEA algorithm, or can adopt the neural network model for optimal solution processing, of course, it can also be other methods, and this embodiment does not make specific limitations on this.

[0065] In this embodiment, for the security indicator parameters and user experience indicator parameters, the same verification method may have different security indicator parameters and user experience indicator parameters under different scenario information. For example, for the image and text recognition verification method, when the scenario information is a mobile client scenario, the security indicator parameter is 8, and the user experience indicator parameter is 6; and for the image and text recognition verification method, when the scenario information is a web page scenario, the security indicator parameter is 9, and the user experience indicator parameter is 7.

[0066] It can be seen that in this embodiment, the verification request type, verification method, security indicator parameters and user experience indicator parameters are combined in the process of target evolution, so that in the process of target evolution, the verification method assigned to each verification request type can be scored according to the security indicator parameters and user experience indicator parameters corresponding to the verification method, thereby improving the rationality and accuracy of the generation of verification combination information.

[0067] In an optional embodiment of the present application, verification request type and verification method are used, combined with security indicator parameters and user experience indicator parameters to perform target evolution, and obtain verification combination information, which may specifically include the following steps: configuring a verification method for each verification request type to obtain at least two combination information to be confirmed; determining the security indicator weight corresponding to the security indicator parameter based on the scenario information, and determining the user experience indicator weight corresponding to the user experience indicator parameter; using security indicator parameters and user experience indicator parameters, combined with security indicator weights and user experience indicator weights, to calculate the optimal solution set for each combination information to be confirmed, and obtain optimal solution combination information; using the optimal solution combination information to generate verification combination information.

[0068] In this embodiment, in the process of determining the verification request type and the verification method based on the scenario information, at least two verification request types can be determined. Then, in the process of using the verification request type and the verification method, combining the security indicator parameters and the user experience indicator parameters to perform target evolution and obtaining the verification combination information, a verification method can be configured for each verification request type to obtain at least two combination information to be confirmed, wherein the verification methods configured for each verification request type can be the same or different, and the combination information to be confirmed represents the combination information including each verification request type and its configured verification method; then, based on the scenario information, the security indicator weight corresponding to the security indicator parameter and the user experience indicator weight corresponding to the user experience indicator parameter can be determined, the security indicator weight represents the weight corresponding to the security indicator parameter in the scenario represented by the scenario information, and the user experience indicator weight represents the weight corresponding to the user experience indicator parameter in the scenario represented by the scenario information, that is, under different scenario information The security indicator parameters and the user experience indicator parameters can be configured with the same or different weights respectively, but the sum of the security indicator weight and the user experience indicator weight should be 1; thus, the security indicator parameters and the user experience indicator parameters can be used, combined with the security indicator weight and the user experience indicator weight, to calculate the optimal solution set for each combination of information to be confirmed, and obtain the optimal solution combination information. The optimal solution set calculation uses the security indicator weight and the user experience indicator weight to calculate the distribution score corresponding to each combination of information to be confirmed. The distribution score represents the security indicator parameter and the user experience indicator parameter corresponding to each verification request type in the combination of information to be confirmed, and the score is obtained after calculation in combination with the security indicator weight and the user experience indicator weight. The optimal solution combination information thus obtained can represent the combination of the verification request type and the verification method with the highest score under the scenario represented by the scenario information; and then the configuration combination of the verification request type and the verification method represented by the optimal solution combination information can be determined as the verification combination information.

[0069] In one example, when verification request type A, verification request type B, and verification request type C are included, and the verification methods include verification method X and verification method Y, a verification method is configured for each verification request type. Verification method X or verification method Y can be configured for verification request type A, verification method X or verification method Y can be configured for verification request type B, and verification method X or verification method Y can be configured for verification request type C. In this way, 8 configuration methods can be obtained, that is, 8 combinations of information to be confirmed can be obtained. In addition, for the security index weights and user experience index weights, the security index parameters and user experience index parameters of the same verification method may have different security index weights and user experience index weights under different scenario information. For example, for the image and text recognition verification method, when the scenario information is a mobile client scenario, the security index weight corresponding to the security index parameter is 0.7, and the user experience index weight corresponding to the user experience index parameter is 0.3; and for the image and text recognition verification method, when the scenario information is a web page scenario, the security index weight corresponding to the security index parameter is 0.6, and the user experience index weight corresponding to the user experience index parameter is 0.4; it can be seen that the sum of the security index weight and the user experience index weight is 1, but the specific weight values ​​may be different under different scenario information.

[0070] In an optional embodiment of the present application, security indicator parameters and user experience indicator parameters are used, combined with security indicator weights and user experience indicator weights, to calculate the optimal solution set for each combination of information to be confirmed, and obtain the optimal solution combination information, which may specifically include the following steps: determining the verification method allocation information corresponding to each combination of information to be confirmed; using security indicator parameters and user experience indicator parameters, combined with security indicator weights and user experience indicator weights, to calculate the allocation score corresponding to the verification method allocation information; determining the combination of information to be confirmed corresponding to the target allocation score as the optimal solution combination information, and the target allocation score represents the allocation score with the largest score.

[0071] In this embodiment, in the process of calculating the optimal solution set for each combination information to be confirmed, the verification method allocation information corresponding to each combination information to be confirmed can be determined, and the verification method allocation information indicates the specific allocation of the verification method configured for each verification request type in the combination information to be confirmed; thereby, the security index parameter and the user experience index parameter can be used, combined with the security index weight and the user experience index weight, to calculate the allocation score corresponding to the verification method allocation information, and the allocation score indicates the score corresponding to the allocation method represented by the verification method allocation information. The specific calculation process can determine the verification method corresponding to each verification request type according to the verification method allocation information, and calculate the security index value corresponding to each verification method according to the security index weight and the security index parameter, and calculate the user experience index value corresponding to each verification method according to the user experience index weight and the user experience index parameter, and determine the sum of the security index value and the user experience index value as the allocation score corresponding to the verification method allocation information; and then the size of the allocation score corresponding to each verification method allocation information can be compared, and the maximum allocation score can be determined as the target allocation score, and the combination information to be confirmed corresponding to the target allocation score can be determined as the optimal solution combination information.

[0072] It can be seen that in this embodiment, the target allocation score is determined by comparing the allocation scores, so as to obtain the optimal solution combination information, and the allocation score is calculated based on the security indicator parameters and the user experience indicator parameters, combined with the security indicator weight and the user experience indicator weight, and the security indicator parameters, the user experience indicator parameters, the security indicator weight and the user experience indicator weight all have a corresponding relationship with the scene information, thereby determining the optimal solution combination information that best matches the scene information; thereby achieving the purpose of determining the target verification method that matches the verification request type, solving the problem of mismatch between scene requirements and verification methods in the existing related technologies using random configuration verification methods, and being able to effectively determine the verification method that matches the scene information.

[0073] In one example, when the scene information is a web page scene and has two combination information to be confirmed, including combination information A to be confirmed and combination information B to be confirmed, the verification method allocation information A corresponding to the combination information A to be confirmed indicates that the verification request type A is configured with a graphic verification method, and the verification request type B is configured with a voice verification method; the verification method allocation information B corresponding to the combination information B to be confirmed indicates that the verification request type A is configured with a sliding verification method, and the verification request type B is configured with a nine-square grid verification method; at this time, it is determined that the security index parameter of the graphic verification method corresponding to the web page scene is 6, the user experience index parameter is 5, the security index weight is 0.7, and the user experience index weight is 0.3; the security index parameter of the voice verification method is 9, the user experience index parameter is 3, the security index weight is 0.9, and the user experience index weight is 0.1; the security index parameter of the sliding verification method is 5, the user experience index parameter is 9, the security index weight is 0.4, and the user experience index weight is 0.6; the security index parameter of the nine-square grid verification method is 8, the user experience index parameter is 4, the security index weight is 0.8, and the user experience index weight is 0.2;

[0074] At this time, the allocation score corresponding to the verification method allocation information A is calculated as: 6*0.7+5*0.3+9*0.9+3*0.1=14.1; the allocation score corresponding to the verification method allocation information B is calculated as: 5*0.4+9*0.6+8*0.8+4*0.2=14.6; the allocation score 14.6 corresponding to the verification method allocation information B can be taken as the maximum allocation score, and the allocation score 14.6 corresponding to the verification method allocation information B can be determined as the target allocation score, and then the to-be-confirmed combination information B corresponding to the verification method allocation information B can be determined as the optimal solution combination information; of course, the above is only for illustrative purposes, and the specific implementation can be adaptively adjusted according to different scenarios and requirements, and this embodiment does not make specific limitations on this.

[0075] In an optional embodiment of the present application, the verification request type and verification method are used, combined with security indicator parameters and user experience indicator parameters to perform target evolution to obtain verification combination information, which may specifically include the following steps: obtaining a preset multi-objective evolution model; inputting the verification request type, verification method, security indicator parameters and user experience indicator parameters into the multi-objective evolution model; and generating verification combination information based on the model output results of the multi-objective evolution model.

[0076] In this embodiment, the verification request type and verification method are used, combined with security indicator parameters and user experience indicator parameters to perform target evolution, and the verification combination information obtained. The specific target evolution method can be based on a preset multi-objective evolution model. At this time, the preset multi-objective evolution model can be obtained, and the verification request type, verification method, security indicator parameters and user experience indicator parameters are used as inputs of the multi-objective evolution model and input into the multi-objective evolution model, so that the multi-objective evolution model uses the verification request type, verification method, security indicator parameters and user experience indicator parameters to perform multi-objective evolution, and outputs the model output result. The model output result represents the optimal solution combination information calculated based on the verification request type, verification method, security indicator parameters and user experience indicator parameters. At this time, the optimal solution combination information contained in the model output result can be used to generate verification combination information.

[0077] In one example, when the multi-objective evolutionary model is the MOEA algorithm, quantitative indicators for security and user experience of each verification method can be defined, such as setting (V = {v_1, v_2, v_3, v_4}) v_1 represents sliding verification, v_2 image and text verification, v_3 voice verification and v_4 nine-square grid verification. Each verification method can be represented by (v_i), and the defined security index is (S(v_i)) and the user experience index is (UX(v_i)); the goal is to find the most suitable verification method for each verification request type, and the optimization goal is: maximizing security and maximizing user experience.

[0078] Assuming that there is a set of verification request types (R = {r_1, r_2, ..., r_n}) under the scenario information, where each verification request type is represented by (r_j), then it is necessary to determine the target verification method corresponding to the verification request type.

[0079] 1) Define two optimization objectives: the security index parameter is (f_1) and the user experience index parameter is (f_2):

[0080] (f_1(r_j,v_i)=S(v_i))

[0081] (f_2(r_j,v_i)=UX(v_i))

[0082] 2) Establish optimization model:

[0083] (\max\limits_{v_i\in V}f_1(r_j,v_i))

[0084] (\max\limits_{v_i\in V}f_2(r_j,v_i))

[0085] The multi-objective optimization problem can be expressed as:

[0086] (\max\limits_{v_i\in V}\left(\theta_1\cdot f_1(r_j,v_i),\theta_2\cdotf_2(r_j,v_i)\right)\forall j\in{1,...,n})

[0087] Among them, (\theta_1) is the weight of the security index and (\theta_2) is the weight of the user experience index. (\theta_1) and (\theta_2) determine the relative importance of security and user experience in fitness evaluation. In multi-objective optimization, the choice of weights usually depends on the preference for different objectives in actual applications, that is, adaptive configuration can be performed according to different scenario information.

[0088] 3) Then, in the process of using the MOEA algorithm, a heuristic search process can also be set (such as NSGA-II or SPEA2 algorithms), in which the fitness function needs to combine the above two objectives. The selection, crossover, mutation and selection agent operations need to be designed according to these objectives in order to generate a Pareto front in each generation.

[0089] At the end of the calculation, the MOEA algorithm will give a series of non-inferior solutions (non-dominated solutions), each of which corresponds to a different (v_i) choice, so that each verification request type selects the solution that can give the best trade-off, that is, the target verification method corresponding to each verification request type.

[0090] In an optional embodiment of the present application, in step S120, the verification request type and verification method are determined based on the scene information, which may specifically include the following steps: determining the target scene area based on the scene information; extracting the verification request identifier based on the target scene area; determining the verification request type based on the verification request identifier, and obtaining the verification method corresponding to the target scene area.

[0091] In this embodiment, after determining the scene information, the target scene area can be determined based on the scene information. The target scene area represents the scene area represented by the scene information. For example, when the scene information is a web page scene, all range areas in the web page are determined as the target scene area. It should be noted that in this embodiment, the target scene area is the range area of ​​the application. For example, the target scene area corresponding to the web page scene is all areas that need to be verified in the web page. Therefore, one or more verification request identifiers can be extracted based on the target scene area. The verification request identifier indicates that there is an identifier that needs to be verified in the target scene area, such as a login verification request identifier corresponding to a login verification request and a payment verification request identifier corresponding to a payment verification request. Then, the verification request type can be determined based on the verification request identifier, that is, the type marked by each verification request identifier is determined as the verification request type, and the verification method corresponding to the target scene area is obtained. In the process of obtaining the verification method, the verification method corresponding to the target scene area can be determined based on the preset scene area and verification method correspondence table, that is, different target scene areas can correspond to different verification methods.

[0092] In an optional embodiment of the present application, based on the target scene area, the verification request identifier is extracted, which may specifically include the following steps: obtaining a request data set within a preset time from the target scene area; and extracting the verification request identifier from the request data set.

[0093] In the present embodiment, in the process of extracting the verification request identifier, a request data set within a preset time can be obtained from the target scene area, and the request data set represents a data set of verification requests initiated by users within the preset time in the target scene area, so that one or more verification request identifiers can be extracted from the request data set, and then the verification request type can be determined using the verification request identifier.

[0094] like Figure 2 As shown, the present application also discloses an embodiment, providing a device for determining a verification method, including:

[0095] An acquisition module 210, configured to acquire scene information to be updated based on the verification update instruction;

[0096] A first determination module 220, configured to determine a verification request type and a verification method according to the scenario information;

[0097] A target evolution module 230, configured to perform target evolution using the verification request type and the verification method to obtain verification combination information;

[0098] The second determination module 240 is configured to determine a target verification method corresponding to the verification request type based on the verification combination information.

[0099] In an optional embodiment of the present application, at least two verification methods are included, and the target evolution module 230 may include:

[0100] A first determining unit, configured to determine, based on the scenario information, a security index parameter and a user experience index parameter corresponding to each of the verification methods;

[0101] The target evolution unit is used to adopt the verification request type and the verification method, and combine the security index parameter and the user experience index parameter to perform target evolution to obtain the verification combination information.

[0102] In an optional embodiment of the present application, at least two verification request types are included, and the target evolution unit may include:

[0103] A configuration subunit, configured to configure one of the verification modes for each verification request type, and obtain at least two pieces of combination information to be confirmed;

[0104] A first determining subunit, configured to determine, based on the scenario information, a security index weight corresponding to the security index parameter, and determine a user experience index weight corresponding to the user experience index parameter;

[0105] A first calculation subunit is used to use the security index parameter and the user experience index parameter, in combination with the security index weight and the user experience index weight, to perform an optimal solution set calculation on each of the combination information to be confirmed, so as to obtain the optimal solution combination information;

[0106] The first generating subunit is used to generate the verification combination information by adopting the optimal solution combination information.

[0107] In an optional embodiment of the present application, the first computing subunit may include:

[0108] A second determining subunit is used to determine the verification mode allocation information corresponding to each of the combination information to be confirmed;

[0109] A second calculation subunit is used to calculate the allocation score corresponding to the verification mode allocation information by using the security index parameter and the user experience index parameter, in combination with the security index weight and the user experience index weight;

[0110] The third determining subunit is used to determine the to-be-confirmed combination information corresponding to the target allocation score as the optimal solution combination information, wherein the target allocation score represents the allocation score with the largest score.

[0111] In an optional embodiment of the present application, the target evolution unit may include:

[0112] A first acquisition subunit is used to acquire a preset multi-objective evolution model;

[0113] An input subunit, used to input the verification request type, the verification method, the security index parameter and the user experience index parameter into the multi-objective evolution model;

[0114] The second generating subunit is used to generate the verification combination information according to the model output result of the multi-objective evolution model.

[0115] In an optional embodiment of the present application, the first determining module 220 may include:

[0116] A second determining unit, configured to determine a target scene area according to the scene information;

[0117] An extraction unit, configured to extract a verification request identifier based on the target scene area;

[0118] The third determination unit is used to determine the verification request type according to the verification request identifier, and obtain the verification method corresponding to the target scene area.

[0119] In an optional embodiment of the present application, the extraction unit may include:

[0120] The second acquisition subunit is used to acquire a set of requested data within a preset time from the target scene area;

[0121] The extraction subunit is used to extract the verification request identifier from the request data set.

[0122] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0123] like Figure 3 As shown, an embodiment of the present application provides an electronic device, including a processor 310, a communication interface 320, a memory 330 and a communication bus 340, wherein the processor 310, the communication interface 320, and the memory 330 communicate with each other through the communication bus 340;

[0124] Memory 330, for storing computer programs;

[0125] In one embodiment of the present application, the processor 310, when executing the program stored in the memory 330, implements the method for determining the verification method provided by any of the aforementioned method embodiments, obtains the scene information to be updated through the verification update instruction, and determines the verification request type and the verification method based on the scene information, thereby determining the corresponding verification request type and the verification method according to different scenes, and performing target evolution by using the verification request type and the verification method to obtain verification combination information, that is, calculating the verification method corresponding to the optimal solution of each verification request type through target evolution, and then determining the target verification method corresponding to the verification request type based on the verification combination information, thereby achieving the purpose of determining the target verification method that matches the verification request type, solving the problem of mismatch between scene requirements and verification methods in the existing related technology using the random configuration verification method, and being able to effectively determine the verification method that matches the scene information.

[0126] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method for determining a verification method as provided in any of the aforementioned method embodiments is implemented. By verifying an update instruction, the scene information to be updated is obtained, and based on the scene information, the verification request type and the verification method are determined, thereby playing a role in determining the corresponding verification request type and the verification method according to different scenes, so as to perform target evolution using the verification request type and the verification method to obtain verification combination information, that is, to calculate the verification method corresponding to the optimal solution of each verification request type through target evolution, and then determine the target verification method corresponding to the verification request type based on the verification combination information, thereby achieving the purpose of determining a matching target verification method for the verification request type, solving the problem of mismatch between scene requirements and verification methods in the existing related technology using a random configuration verification method, and being able to effectively determine a verification method that matches the scene information.

[0127] 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.

[0128] The above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0129] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. 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 invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for determining a verification method, characterized in that: include: Based on the verification update instruction, obtain the scene information to be updated; Determine the verification request type and verification method based on the scenario information; The verification request type and the verification method are used to perform target evolution to obtain verification combination information; Based on the verification combination information, a target verification mode corresponding to the verification request type is determined.

2. The method for determining the verification mode according to claim 1, characterized in that: At least two verification methods are included, and the verification request type and the verification method are used to perform target evolution to obtain verification combination information, including: Based on the scenario information, determine the security index parameters and user experience index parameters corresponding to each of the verification methods; The verification request type and the verification method are used, combined with the security index parameter and the user experience index parameter to perform target evolution, and obtain the verification combination information.

3. The method for determining the verification mode according to claim 2, characterized in that: At least two of the verification request types are included, and the verification request type and the verification method are used to perform target evolution in combination with the security index parameter and the user experience index parameter to obtain the verification combination information, including: Configure one of the verification methods for each verification request type to obtain at least two pieces of combination information to be confirmed; Determine, based on the scenario information, a security index weight corresponding to the security index parameter, and determine a user experience index weight corresponding to the user experience index parameter; Using the security index parameter and the user experience index parameter, combined with the security index weight and the user experience index weight, an optimal solution set calculation is performed on each of the combination information to be confirmed to obtain the optimal solution combination information; The verification combination information is generated by using the optimal solution combination information.

4. The method for determining the verification mode according to claim 3, characterized in that: The adopting of the security index parameter and the user experience index parameter, in combination with the security index weight and the user experience index weight, performing optimal solution set calculation on each of the combination information to be confirmed, and obtaining the optimal solution combination information, includes: Determine the verification method allocation information corresponding to each of the combination information to be confirmed; The security index parameter and the user experience index parameter are used, combined with the security index weight and the user experience index weight, to calculate the allocation score corresponding to the verification method allocation information; The to-be-confirmed combination information corresponding to the target allocation score is determined as the optimal solution combination information, and the target allocation score represents the allocation score with the largest score.

5. The method for determining the verification mode according to claim 2, characterized in that: The adopting the verification request type and the verification mode, combining the security index parameter and the user experience index parameter to perform target evolution, and obtaining the verification combination information includes: Obtain a preset multi-objective evolution model; Inputting the verification request type, the verification method, the security index parameter and the user experience index parameter into the multi-objective evolution model; The verification combination information is generated according to the model output result of the multi-objective evolution model.

6. The method for determining a verification method according to claim 1, characterized in that: The determining, based on the scenario information, the verification request type and the verification method, includes: Determining a target scene area according to the scene information; Based on the target scene area, extracting a verification request identifier; The verification request type is determined according to the verification request identifier, and a verification method corresponding to the target scene area is obtained.

7. The method for determining the verification mode according to claim 6, characterized in that: The step of extracting a verification request identifier based on the target scene area includes: From the target scene area, obtain the requested data set within a preset time; The verification request identifier is extracted from the request data set.

8. A device for determining a verification method, characterized in that: include: An acquisition module, used for acquiring scene information to be updated based on the verification update instruction; A first determination module, used to determine the verification request type and verification method according to the scenario information; A target evolution module, used to perform target evolution using the verification request type and the verification method to obtain verification combination information; The second determination module is used to determine a target verification method corresponding to the verification request type based on the verification combination information.

9. 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, used to implement the method for determining the verification method described in any one of claims 1-7 when executing a program stored in a memory.

10. 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 for determining the verification mode according to any one of claims 1 to 7 is implemented.

Citation Information

Cited By

  • Authority verification method, electronic equipment, storage medium and program product

    CN120354435A

  • Authorization verification method, electronic device, storage medium, and program product

    CN120354435B