Login verification method and device

Abstract

The present application discloses a login verification method and device, which includes: receiving a login request from a first user; determining a user group to which the first user belongs; obtaining a login weight value of the first user and a login weight value of a second user in the user group, wherein the second user is an online user in the user group; and allowing the first user to log in when the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value. Since when performing login verification on a user, the user can be jointly verified with other users in the user group to which the user belongs, and the user is allowed to log in only when the sum of the login weight value of the user and the login weight value of the online users in the user group is greater than the preset weight value, the security is relatively high.

Description

Technical Field

[0001] The present application relates to the field of network security technology, and in particular to a login verification method and device. Background Art

[0002] Login verification refers to the process of authenticating the user when the user enters an application or system. Only when the verification is passed can the user enter the application or system. Otherwise, the user will be denied access to ensure the security of user information and the system. In related technologies, when a user logs in to an application or system, he or she usually logs in using an account and password. When authenticating the user, it can be verified whether the password entered by the user is consistent with the password reserved by the application or system. If they are consistent, the identity verification is passed and the user is allowed to log in. If they are inconsistent, the identity verification fails and the user is denied access. However, in actual applications, the security of this login verification method is relatively low. For example, if a user's account and password are stolen by an illegal user, the illegal user can disguise the user's identity to enter the application or system, which will not only cause the leakage of user information, but also bring certain security risks to the application or system. Summary of the invention

[0003] The embodiments of the present application provide a login verification method and device for solving the problem that the current login verification method has low security when a user logs into an application or system.

[0004] To solve the above technical problems, the embodiments of the present application are implemented as follows:

[0005] In a first aspect, a login verification method is proposed, comprising:

[0006] receiving a login request from a first user;

[0007] determining a user group to which the first user belongs;

[0008] Obtaining a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group;

[0009] In the case where the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value, the first user is allowed to log in.

[0010] In a second aspect, a login verification device is provided, comprising:

[0011] A receiving module, receiving a login request from a first user;

[0012] A determination module, determining a user group to which the first user belongs;

[0013] an acquisition module, which acquires a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group;

[0014] The login verification module allows the first user to log in if the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value.

[0015] In a third aspect, the present application provides an electronic device, including:

[0016] processor;

[0017] a memory for storing instructions executable by the processor;

[0018] The processor is configured to execute the instructions to implement the method as described in the first aspect.

[0019] In a fourth aspect, the present application provides a computer-readable storage medium. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method described in the first aspect.

[0020] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0021] In the embodiment of the present application, the user group to which the user belongs, the login weight value of each user in the user group, and the preset weight value when the user is allowed to log in to the application or system can be pre-set. When receiving the login request of the first user, the user group to which the first user belongs can be determined according to the login request, and it is judged whether the sum of the login weight value of the first user and the login weight value of the second user in the user group who is online is greater than the preset weight value. If so, the first user is allowed to log in. In this way, when the user is logged in, the user can be logged in in conjunction with other users in the user group to which the user belongs, and the user is allowed to log in only when the sum of the login weight value of the user and the login weight value of the online users in the user group is greater than the preset weight value. Therefore, the security is relatively high. When the user's account and password are stolen, as long as the sum of the login weight value of the user and the login weight value of the online users in the user group to which the user belongs is not greater than the preset weight value, the illegal user cannot log in to the application or system, thereby avoiding the security problems existing in the related art when the login verification is based on the user's account and password, and effectively ensuring the security of the application or system. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present application 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, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0023] Figure 1 It is a flowchart of a login verification method according to an embodiment of the present application;

[0024] Figure 2 is a flowchart of a method for setting a user group according to an embodiment of the present application;

[0025] Figure 3 It is a flowchart of a login verification method according to an embodiment of the present application;

[0026] Figure 4 is a schematic diagram of the structure of an electronic device according to an embodiment of the present application;

[0027] Figure 5 It is a structural diagram of a login verification device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] Login verification refers to checking whether the user has the authority to enter the application or system when the user enters the application or system. Login verification is a common technical means, through which it can effectively ensure that only authorized users can enter the application or system. In related technologies, common login methods include account / email / mobile number + password / verification code login, email + dynamic email verification code login, mobile phone + dynamic SMS / voice verification code login, third-party authorization login, etc.

[0029] However, the above login methods all have the risk of the user's login information (i.e. account + password) being stolen. Once the user's login information is stolen by an illegal user, it will lead to the leakage of user information and even bring certain security risks to the application or system. For example, if the user's login information for a certain application is obtained by an illegal user, the illegal user can enter the application by disguising the identity of the user, thereby destroying the integrity and security of the user's data. Alternatively, if the login information of a user with higher system management authority is obtained by an illegal user, the illegal user may destroy the integrity and security of the system or platform by disguising the user's identity, causing great losses to the system or platform.

[0030] In order to solve the above technical problems, the embodiment of the present application provides a login verification method and device. When the user is logged in, it is no longer just to verify the user himself, but to authenticate the user in combination with other users in the user group to which the user belongs, so as to improve security. Specifically, the user group to which the user belongs, the login weight value of each user in the user group, and the preset weight value when the user is allowed to log in to the application or system can be pre-set. When receiving the login request of the first user, the user group to which the first user belongs can be determined according to the login request, and it is determined whether the sum of the login weight value of the first user and the login weight value of the second user in the user group who is online is greater than the preset weight value. If so, the first user is allowed to log in, and if not, the first user is denied to log in. In this way, when the user's account and password are stolen, as long as the sum of the login weight value of the user and the login weight value of the online users in the user group to which the user belongs is not greater than the preset weight value, the illegal user cannot log in to the application or system, thereby avoiding the security problems existing in the related art when the login verification is performed based on the user's account and password, and effectively ensuring the security of the application or system.

[0031] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0032] The terms "first", "second", etc. in this specification and claims are used to distinguish similar objects, and are not used to describe a particular order or precedence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of this specification can be implemented in an order other than those illustrated or described herein. In addition, "and / or" in this specification and claims means at least one of the connected objects, and the character " / " generally means that the objects associated with each other are in an "or" relationship.

[0033] It should be noted that the application scenario of the embodiment of the present application may be a scenario in which a user logs in to an application or system, and the executor of the technical solution provided by the embodiment of the present application may be the server corresponding to the application or system that the user requests to log in.

[0034] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0035] Figure 1 It is a flowchart of a login verification method according to an embodiment of the present application. Figure 1The login verification methods shown are described below.

[0036] S102: Receive a login request from a first user.

[0037] When the first user logs in to the application or system, the first user may send a login request to the server corresponding to the application or system, and the server may receive the login request of the first user. The login request may include the login information of the first user, and the login information may include the account and password of the first user. The account may be an email address or a mobile phone number, etc., and the password may be a password set by the user when registering in the application or system, or a dynamic verification code, etc.

[0038] Optionally, after receiving the login request of the first user, the following steps may be included:

[0039] Verifying the login information of the first user;

[0040] If the verification is successful, determine the user group to which the first user belongs;

[0041] If the verification fails, a third prompt message is generated, and the third prompt message is used to prompt that the verification of the first user's login information has failed.

[0042] The login information of the first user may be the account number and password entered by the user when logging into the application or system, and the account number and password are carried in the login request. When verifying the login information, it is possible to verify whether the password entered by the first user is consistent with the correct password (such as the password set when the user registers, the dynamic verification code sent by the server to the user). If they are consistent, the verification is passed, and if they are inconsistent, the verification fails. In the case of passing the verification, the subsequent S104 can be executed. In the case of failing the verification, the user login can be denied, and a third prompt message can also be generated to prompt the first user that the login information verification has failed. In the case of failing the verification of the first user's login information, if the first user still wants to continue to log in to the application and system, the account number or password needs to be modified.

[0043] In this way, after receiving the login request of the first user, the login information of the first user can be verified and the user login can be denied if the verification fails, so the security can be improved. In addition, since the subsequent verification steps based on the login weight value are only executed when the verification passes, the double verification of the first user can be achieved based on the verification of the login information and the verification of the login weight value, thereby further improving the security.

[0044] S104: Determine the user group to which the first user belongs.

[0045] When determining the user group to which the first user belongs, optionally, in some embodiments, it can be determined according to the account included in the login request of the first user. Specifically, a correspondence between the account of the first user and the user group to which the first user belongs can be pre-established, so that after receiving the login request of the first user, the user group to which the first user belongs can be determined according to the account carried in the login request and the pre-established correspondence.

[0046] It should be noted that the number of user groups to which the first user belongs may be one or more. When the number of user groups is multiple, when determining the user group to which the first user belongs, one of the user groups to which the first user belongs may be determined, or multiple user groups to which the first user belongs may be determined. No specific limitation is made here.

[0047] The user group to which the first user belongs may be pre-created by the first user, or may also be pre-created by other users in the user group. Taking the first user creating a user group as an example, optionally, in some implementations, the user group may be pre-created in the following manner:

[0048] receiving a request from a first user to create a user group;

[0049] receiving a member invitation request from the first user to the fourth user, where the member invitation request is used to invite the fourth user to join the user group;

[0050] sending a member invitation request to a fourth user;

[0051] When the confirmation information of the fourth user is received, the fourth user is set as a member of the user group.

[0052] Specifically, the application or system may provide a function for creating a user group. When the first user wants to create a user group, the function may be used to send a user group creation request to the server corresponding to the application or system, and the server may receive the creation request sent by the first user. The first user may create a user group after the first user successfully registers in the application or system, or may create the user group during the use of the application or system, which is not specifically limited here.

[0053] After the first user sends a request to create a user group to the server, he can invite other users to join the user group and send a member invitation request to the server. The member invitation request can carry the identification information of the invited user. For the sake of distinction, the invited user can be represented as a fourth user. The identification information of the fourth user can be the account of the fourth user. The number of fourth users can be one or more, that is, the first user can invite one user to join the user group at a time, or invite multiple users to join the user group at a time.

[0054] After receiving the member invitation request for the fourth user, the server may send the member invitation request to the fourth user through a system message or the like. For the fourth user, if the first user's invitation is agreed, a confirmation message may be sent to the server; if the first user's invitation is not agreed, a rejection message may be sent to the server. If the server receives the confirmation message from the fourth user, the fourth user may be set as a member of the user group; if the fourth user's rejection message is received, the first user may be prompted that the invitation failed. In the case of successfully inviting the fourth user to join the user group, the first user may continue to invite other users to join the user group, or, if the invited user has met the requirements, the invitation may be terminated. In the case of failure to invite the fourth user, the first user may continue to invite other users to join the user group. Thus, by inviting other users to join the user group, a user group may be finally created. Among them, the user group includes the first user and at least one other user.

[0055] It should be noted that the fourth user to be invited needs to be a user who has successfully registered in the application or system, otherwise the fourth user cannot be invited to join the user group. Optionally, after receiving the member invitation request for the fourth user, the server can determine whether the fourth user is included in the registered users. If included, a member invitation request is sent to the fourth user. If not, the first user can be prompted that the fourth user does not exist. After receiving the prompt, if the first user still wants to invite the fourth user to join the user group, the fourth user can be notified to register in the application or system by phone, text message, etc. After the fourth user successfully registers, the first user can send a member invitation request to the server again for the fourth user. In addition, in order to improve security, the fourth user can preferably be a user who has not joined other user groups. Optionally, after receiving the membership invitation request for the fourth user, the server can determine whether the fourth user has not joined other user groups. If so, the membership invitation request can be sent to the fourth user. If not, the first user can be prompted whether to continue to invite the fourth user to join the user group. If the first user confirms to continue the invitation, a confirmation message can be sent to the server, and the server will send the membership invitation request to the fourth user. If the first user confirms not to invite, a rejection invitation message can be sent to the server, and the server will refuse to send the membership invitation request to the fourth user.

[0056] After the server creates a user group based on the above method, it can establish a correspondence between the user group and the accounts of the users in the user group. In this way, when a login request from the first user is received, the user group to which the first user belongs can be determined based on the account of the first user and the pre-established correspondence between the user account and the user group.

[0057] S106: Obtain a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group.

[0058] After determining the user group to which the first user belongs, it is possible to determine which users in the user group are online. Here, for the sake of distinction, the online users in the user group can be represented as second users, and the number of second users can be one or more. After determining the second user, the login weight value of the first user and the login weight value of the second user can be obtained. Among them, the larger the login weight value, the higher the importance of the user in the login verification.

[0059] It should be noted that, in a possible implementation, the number of second users may be 0, that is, there are no online users in the user group. In this case, only the login weight value of the first user can be obtained, and there is no need to obtain the login weight value of the second user. In order to facilitate understanding of the technical solution provided in the embodiment of the present application, only the example of the second user not being 0 is used for explanation.

[0060] The login weight value of each user in the user group can be set by the users in the user group, or can also be set by the server according to the activity level, credit rating and other information of each user in the user group, which is not specifically limited here. In order to meet the needs of users, it is preferred that the login weight value can be set by the users in the user group. Among them, in the case where the login weight value is set by the users in the user group, the login weight value can be set by the user who creates the user group. For example, if the user group is created by the first user, the login weight value can be set by the first user.

[0061] Taking the first user setting the login weight value as an example, optionally, in some implementations, the following steps may be included:

[0062] Receive weight setting information of the first user, where the weight setting information includes a login weight value of each user in the user group;

[0063] Send weight setting information to other users in the user group;

[0064] When confirmation information from other users in the user group is received, weight setting is performed according to the weight setting information.

[0065] Specifically, after the first user creates a user group, the first user can set corresponding login weight values ​​for the first user and other users in the user group. When setting the login weight value, the first user can set it according to actual needs, and no specific limitation is made here. Among them, the larger the login weight value of the user, the higher the importance of the user in the login verification, and the greater the decisive role played by the server in whether to allow the user to log in when the server performs login verification based on the login weight value.

[0066] After setting the login weight value, the first user can send weight setting information to the server, and the weight setting information can include the login weight value of each user in the user group. After receiving the weight setting information, the server can send the weight setting information to other users in the user group through system messages and other means. If other users agree with the login weight value set by the first user, the server can send confirmation information. After receiving the confirmation information, the server can set the login weight value of each user in the user group according to the weight setting information, so that the login weight value set by the first user takes effect. If other users do not agree with the login weight value set by the first user, the server can send a rejection message. After receiving the rejection message, the server can prompt the first user that the login weight value set by the first user is not recognized by other users and needs to be reset. At this time, the first user can reset the login weight value and send a new weight setting information to the server, and then the server sends the new weight setting information to other users for confirmation, and so on. Cycle until other users confirm the login weight value set by the first user, at which time the server can set the login weight value of each user in the user group according to the new weight setting information, so that the reset login weight value set by the first user takes effect. Optionally, in some embodiments, in order to improve the efficiency of setting the login weight value and avoid the problem of a long login weight value setting time caused by the first user repeatedly setting the login weight value, the first user may negotiate with other users in the user group in advance through telephone, text message, etc. before setting the login weight value, and send the negotiated weight setting information to the server after reaching an agreement.

[0067] When the first user sets the login weight value, the login weight set by the first user will take effect only when other users in the user group confirm it. Therefore, the set login weight value can meet the needs of each user in the user group.

[0068] After setting the login weight value of each user in the user group using the method described above, when a login request from a first user is received and the user group to which the first user belongs and a second user who is online in the user group are determined, the login weight value of the first user and the login weight value of the second user can be obtained from the pre-set login weight values.

[0069] S108: When the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value, the first user is allowed to log in.

[0070] After obtaining the login weight value of the first user and the login weight value of the second user, the sum of the login weight value of the first user and the login weight value of the second user can be determined, and then it is determined whether the sum of the login weight values ​​is greater than the preset weight value. The preset weight value can be set by the server according to the actual situation, or it can also be set by the users in the user group, which is not specifically limited here. In order to meet the needs of users, it is preferred that the preset weight value can be set by the users in the user group. In the case where the preset weight value is set by the users in the user group, it can be set specifically by the user who created the user group. Taking the user group created by the first user as an example, after the first user creates the user group, the preset weight value can be set accordingly. Specifically, the first user can set the preset weight value together when setting the login weight value of each user in the user group. For example, in the above S106, when the first user sends the weight setting information to the server, the weight setting information can also include the preset weight value, and the preset weight value needs to be confirmed by other users in the user group. When other users confirm, the service can make the preset weight value set by the first user effective, otherwise the first user needs to re-set the preset weight value. The specific setting process of the preset weight value can refer to the setting process of the login weight value by the first user in the above S106, which will not be described in detail here.

[0071] When determining the sum of the login weight value of the first user and the login weight value of the second user, if the number of user groups to which the first user determined in S104 belongs is 1, then the sum of the login weight value of the first user and the login weight value of the second user in the one user group may be determined. If the number of user groups to which the first user determined in S104 belongs is multiple, then the sum of the login weight value of the first user and the login weight values ​​of the second users in the multiple user groups may be determined, or the sum of the login weight value of the first user and the login weight value of the second user in one user group among the multiple user groups (for example, the user group with the smallest login weight value of the second user) may be determined, or the sum between the login weight value of the first user and the average login weight value of the second users in the multiple user groups may be determined, and no specific limitation is made here.

[0072] After determining the sum of the login weight value of the first user and the login weight value of the second user, when judging whether the sum of the login weight values ​​is greater than the preset weight value, if the judgment result is yes, it can be said that the security of the first user's login this time is relatively high, and the server can allow the first user to log in to the application or system. If the judgment result is no, it can be said that there may be security risks in the first user's login this time. At this time, in order to ensure the security of user information and the system, the server can reject the first user's login request, that is, not allow the first user to log in to the application or system.

[0073] Optionally, in some implementations, after rejecting the login request of the first user, the server may include the following steps:

[0074] Generate a first prompt message, the first prompt message is used to prompt the first user that the sum of the login weight values ​​of the user group does not meet the login condition;

[0075] Determining whether a login request from a third user in the user group is received within a preset time period;

[0076] If yes, determine whether the sum of the login weight values ​​of the first user, the second user, and the third user is greater than the preset weight value;

[0077] When the sum of the login weight values ​​of the first user, the second user and the third user is greater than the preset weight value, the first user is allowed to log in.

[0078] Specifically, after rejecting the login request of the first user, the server may generate a first prompt message, which may be used to prompt the first user that the sum of the login weight values ​​of the user group does not meet the login condition, that is, prompt the first user the reason for the failed login. For the first user, if he wants to continue to log in to the application or system, he may notify other users in the user group to assist the first user in logging in through a phone call, text message, etc. Optionally, the first user may also send a login assistance request to the server to request the server to send notification information to other users in the user group through a system message, etc., asking whether to assist the first user in logging in.

[0079] For other users in the user group, if they confirm to assist the first user to log in, they can log in to the application or system and send a login request to the server. If they confirm not to assist the first user to log in, they can not log in to the application or system. Optionally, before confirming whether to assist the first user to log in, other users in the user group can first confirm whether the first user is the user himself. If the first user is the user himself, they can assist the first user to log in. If the first user is not the user himself, they can not assist the first user to log in, so as to ensure the security of user information and system.

[0080] For the server, after generating the first prompt information, it can determine whether a login request sent by other users in the user group is received within a preset time period. Here, for the sake of distinction, the user who assists the first user in logging in can be represented as a third user in the user group, and the number of third users can be one or more. If the server receives a login request from a third user within a preset time period, it can further determine whether the sum of the login weight values ​​of the first user, the second user, and the third user is greater than the preset weight value. If so, the first user is allowed to log in. Among them, after receiving the login request from the third user, the login information of the third user can also be verified. If the verification is passed and the sum of the login weight values ​​of the first user, the second user, and the third user is greater than the preset weight value, the first user is allowed to log in, thereby improving security.

[0081] Optionally, in some embodiments, after generating the first prompt message, the server may confirm that the assisted login has failed in any of the following situations (1) to (3), and generate a second prompt message to prompt the first user that the assisted login has failed.

[0082] (1) No login request from a third user is received within a preset time period.

[0083] (2) The login information verification of the third user fails.

[0084] (3) The sum of the login weight values ​​of the first user, the second user, and the third user is less than or equal to the preset weight value.

[0085] Optionally, when confirming that the assisted login has failed, if the preset time has not been exceeded, the server may allow the first user to continue to invite other users to assist in the login; if the preset time has been exceeded, the server may prompt the first user to log in again.

[0086] After the first user successfully logs in to the application or system, optionally, in some implementations, the following steps may also be included:

[0087] In the case where it is monitored that the fourth user in the user group is offline, determining whether the sum of the login weight values ​​of the online users in the user group is greater than a preset weight value;

[0088] If not, the online users in the user group are offlined.

[0089] Specifically, after the first user successfully logs into the application system, the server can monitor the status of users in the user group to which the first user belongs. If it is monitored that a user in the user group switches from an online state to an offline state, that is, it is monitored that a user in the user group is offline, it can be determined whether the sum of the login weight values ​​of the online users in the current user group is greater than the preset weight value. If not, the online users in the user group can be offline, that is, the online users in the user group can be forced to log off. If so, the online status of the online users can be maintained. In this way, the online and offline status of users in the user group can be flexibly controlled through the login weight value.

[0090] In order to facilitate understanding of the technical solution provided in the embodiments of the present application, in a more specific implementation method, please refer to the following Figure 2 and Figure 3 The embodiment shown.

[0091] Figure 2 It is a flowchart of a method for setting a user group according to an embodiment of the present application. Figure 2 The illustrated embodiment may include the following steps.

[0092] S202: Receive a registration request from a user.

[0093] The user's registration request may include registration information, and the registration information may include the account number and password set by the user.

[0094] S204: Verify the user's registration information.

[0095] S206: If the verification is successful, the user is prompted that the registration is successful.

[0096] If the user registration is successful, the user may be prompted whether to create a user group. If the user confirms to create a user group, a user group creation request may be sent to the server, and the server may execute S208. If the user confirms not to create a user group, the server may perform login verification on the user in a conventional login verification manner during subsequent logins.

[0097] S208: Receive a user's request to create a user group.

[0098] S210: Receive a member invitation request from a user.

[0099] S212: Determine whether the invited user has joined other user groups.

[0100] If the invited user has joined other user groups, the user can be prompted that the invitation failed, and the user can continue to invite other users to join the user group, and the server can return to execute S210. If the invited user has not joined other user groups, S214 can be executed.

[0101] S214: Send the member invitation request to the invited user.

[0102] S216: Determine whether confirmation information from the invited user is received.

[0103] If confirmation information from the invited user is received, it means that the invited user confirms to join the user group, and S218 can be executed at this time. If confirmation information from the invited user is not received, it means that the invited user does not agree to join the user group, and the user can be prompted that the invitation failed. The user can continue to invite other users to join the user group, and the server can return to execute S210.

[0104] S218: Setting the invited user as a member of the user group.

[0105] After setting the invited user as a member of the user group, the user can continue to invite other users to join the group and send a member invitation request to the server, and the server can return to execute S210. If the users in the user group have met the requirements, the user can end the invitation. After that, the user can set the login weight value and preset weight value of each user in the user group, and send the weight setting information to the server, and the server can execute S220.

[0106] S220: Receive weight setting information sent by the user.

[0107] S222: Send the weight setting information to other users in the user group.

[0108] S224: Determine whether confirmation information from other users is received.

[0109] If confirmation information is received from other users, it means that other users agree with the weight value set by the user. At this time, the server can execute S226. If confirmation information is not received from other users, it means that other users do not agree with the weight value set by the user. The user needs to re-set the weight value and send the re-set weight information to the server. The server can execute S220.

[0110] S226: Setting weights according to the weight setting information.

[0111] Based on the above S202 to S226, the user can create a user group, and after creating the user group, the login weight and the preset weight value of each user in the user group can be set. The specific implementation of the above S202 to S206 can be found in Figure 1 The specific implementation of the corresponding steps in the illustrated embodiment will not be described in detail here.

[0112] Figure 3It is a flowchart of a login verification method according to an embodiment of the present application. Figure 3 The illustrated embodiment may include the following steps.

[0113] S302: Receive a login request from a first user.

[0114] S304: Determine the user group to which the first user belongs.

[0115] S306: Obtain a login weight value of the first user and a login weight value of a second user in the user group who is online.

[0116] S308: Determine whether the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value.

[0117] If it is greater, S320 may be executed; if it is not greater, S310 may be executed.

[0118] S310: Prompt the first user that the sum of the login weight values ​​of the user group does not meet the login condition.

[0119] S312: Determine whether a login request from a third user in the user group is received within a preset time period.

[0120] If so, S314 may be executed, otherwise, S18 may be executed.

[0121] S314: Determine whether the login information of the third user is verified.

[0122] If the verification is successful, S316 may be executed, otherwise S318 may be executed.

[0123] S316: Determine whether the sum of the login weight values ​​of the first user, the second user, and the third user is greater than a preset weight value.

[0124] If yes, S320 may be executed, if no, S318 may be executed.

[0125] S318: Prompt the first user that the login failed.

[0126] S320: Allow the first user to log in.

[0127] The specific implementation of the above S302 to S320 can be found in Figure 1 The specific implementation of the corresponding steps in the illustrated embodiment will not be described in detail here.

[0128] Optionally, after the first user logs in to the application or system, the server can also determine whether the sum of the login weight values ​​of the online users in the user group is greater than the preset weight value when monitoring that the user in the user group is offline. If so, the online status of the current online user can be maintained. If not, the online user in the user group is offline. For details, please refer to Figure 1 The corresponding contents in the illustrated embodiment will not be described in detail here.

[0129] The technical solution provided by the embodiment of the present application can pre-set the user group to which the user belongs, the login weight value of each user in the user group, and the preset weight value when the user is allowed to log in to the application or system. When receiving the login request of the first user, the user group to which the first user belongs can be determined according to the login request, and it is judged whether the sum of the login weight value of the first user and the login weight value of the second user in the user group who is online is greater than the preset weight value. If so, the first user is allowed to log in. In this way, when the user is logged in, the user can be logged in in conjunction with other users in the user group to which the user belongs, and the user is allowed to log in only when the sum of the login weight value of the user and the login weight value of the online users in the user group is greater than the preset weight value. Therefore, the security is relatively high. When the user's account and password are stolen, as long as the sum of the login weight value of the user and the login weight value of the online users in the user group to which the user belongs is not greater than the preset weight value, the illegal user cannot log in to the application or system, thereby avoiding the security problems existing in the related art when the login verification is based on the user's account and password, and effectively ensuring the security of the application or system.

[0130] Based on the technical solution provided in the embodiment of the present application, the security of the system or application can be improved. Among them, the more users in the user group, the more the login weight value of each user is reasonably allocated, and the reasonable preset weight value is set, the more conducive to the security of the system or application. When a user's account is stolen, as long as the login weight value at the time of login and the login weight value of the online users in the user group are not greater than the pre-weight value, the system or application cannot be entered. In some application scenarios, the login verification method provided in the embodiment of the present application can control children or others from accessing the system or application. In addition, the verification idea based on weight can also be applied to payment scenarios. For example, payment transactions can only be performed when the user's personal weight value or the sum of multiple weight values ​​is greater than the preset weight value.

[0131] For applications or systems with high security requirements, the technical solutions provided by the embodiments of the present application can be adopted to improve the security of the application or system. For example, in the smart city basic security platform system, the system is provided with a leadership login group (i.e., a leadership user group), and multiple leaders need to log in together and the sum of the login weight values ​​is greater than the preset weight value before they can enter the system and view the smart city large screen information and sensitive data. If the account of a leader in the leadership login group is stolen, others cannot log in to the system alone through this account, thereby ensuring the security of the system. In addition, the technical solutions provided by the embodiments of the present application can also be applied to smart education products to control the behavior of users entering the system. For example, parents control children's access to a system. If the parents do not log in to the system, the children cannot enter the system alone. The parents exit the system, and the children are immediately exited from the system.

[0132] The above describes specific embodiments of the present application. 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.

[0133] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 4 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0134] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0135] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0136] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a login verification device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0137] receiving a login request from a first user;

[0138] determining a user group to which the first user belongs;

[0139] Obtaining a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group;

[0140] In the case where the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value, the first user is allowed to log in.

[0141] The above application Figure 4The method performed by the login verification device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in a decoding processor. The software module can be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0142] The electronic device may also perform Figures 1 to 3 The method and the login verification device are implemented in Figures 1 to 3 The functions in the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0143] Of course, in addition to software implementation methods, the electronic device of the present application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0144] The embodiment of the present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to execute Figures 1 to 3 The method of the embodiment shown is specifically used to perform the following operations:

[0145] receiving a login request from a first user;

[0146] determining a user group to which the first user belongs;

[0147] Obtaining a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group;

[0148] In the case where the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value, the first user is allowed to log in.

[0149] Figure 5 This is a schematic diagram of the structure of a login verification device 50 according to an embodiment of the present application. Figure 5 In a software implementation, the login verification device 50 may include: a receiving module 51, a determining module 52, an acquiring module 53 and a login verification module 54, wherein:

[0150] A receiving module 51 receives a login request from a first user;

[0151] A determination module 52, determining the user group to which the first user belongs;

[0152] An acquisition module 53 is configured to acquire a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group;

[0153] The login verification module 54 allows the first user to log in if the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value.

[0154] Optionally, in some implementations, the login verification module 54 further includes:

[0155] In the case where the sum of the login weight values ​​of the first user and the second user is less than or equal to the preset weight value, generating a first prompt message, wherein the first prompt message is used to prompt the first user that the sum of the login weight values ​​of the user group does not meet the login condition;

[0156] Determining whether a login request from a third user in the user group is received within a preset time period;

[0157] If yes, determining whether the sum of the login weight values ​​of the first user, the second user and the third user is greater than the preset weight value;

[0158] In a case where the sum of the login weight values ​​of the first user, the second user, and the third user is greater than the preset weight value, the first user is allowed to log in.

[0159] Optionally, in some implementations, the login verification module 54 further includes:

[0160] In the case where any of the following conditions is met, a second prompt message is generated, where the second prompt message is used to prompt the first user that the assisted login fails:

[0161] No login request from the third user is received within the preset time period;

[0162] The login information verification of the third user fails;

[0163] The sum of the login weight values ​​of the first user, the second user, and the third user is less than or equal to the preset weight value.

[0164] Optionally, in some implementations, the login verification module 54, after allowing the first user to log in, further includes:

[0165] In the case where it is monitored that a user in the user group is offline, determining whether the sum of the login weight values ​​of online users in the user group is greater than the preset weight value;

[0166] If not, an offline operation is performed on the online users in the user group.

[0167] Optionally, in some implementations, the login verification module 54, after the receiving module 51 receives the login request of the first user, further includes:

[0168] Verifying the login information of the first user;

[0169] If the verification is successful, determining the user group to which the first user belongs;

[0170] In the case where the verification fails, a third prompt message is generated, where the third prompt message is used to prompt that the verification of the first user login information has failed.

[0171] Optionally, in some implementations, the login verification device 50 further includes a user group creation module, and the user group creation module pre-creates the user group in the following manner:

[0172] receiving a request from the first user to create the user group;

[0173] receiving a member invitation request from the first user to a fourth user, where the member invitation request is used to invite the fourth user to join the user group;

[0174] sending the member invitation request to the fourth user;

[0175] In case of receiving the confirmation information of the fourth user, the fourth user is set as a member of the user group.

[0176] Optionally, in some implementations, after creating the user group, the user group creation module further includes:

[0177] receiving weight setting information of the first user, wherein the weight setting information includes a login weight value of each user in the user group and the preset weight value;

[0178] Sending the weight setting information to other users in the user group;

[0179] When confirmation information from other users in the user group is received, weight setting is performed according to the weight setting information.

[0180] The login verification device 50 provided in the embodiment of the present application can also execute Figures 1 to 3 The method and the login verification device are implemented in Figures 1 to 3 The functions of the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0181] In short, the above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0182] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0183] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0184] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity 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, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0185] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

Claims

1. A login verification method, characterized in that: include: receiving a login request from a first user; determining a user group to which the first user belongs; Obtaining a login weight value of the first user and a login weight value of a second user in the user group, where the second user is an online user in the user group, and the login weight value is set by the users in the user group or by the server according to user information, where the user information includes the user's activity level and credit rating, and the larger the login weight value of the user, the higher the importance of the user in login verification; In the case where the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value, the first user is allowed to log in.

2. The method according to claim 1, characterized in that The method further comprises: In the case where the sum of the login weight values ​​of the first user and the second user is less than or equal to the preset weight value, generating a first prompt message, wherein the first prompt message is used to prompt the first user that the sum of the login weight values ​​of the user group does not meet the login condition; Determining whether a login request from a third user in the user group is received within a preset time period; If yes, determining whether the sum of the login weight values ​​of the first user, the second user and the third user is greater than the preset weight value; In a case where the sum of the login weight values ​​of the first user, the second user, and the third user is greater than the preset weight value, the first user is allowed to log in.

3. The method according to claim 2, characterized in that The method further comprises: In the case where any of the following conditions is met, a second prompt message is generated, where the second prompt message is used to prompt the first user that the assisted login fails: No login request from the third user is received within the preset time period; The login information verification of the third user fails; The sum of the login weight values ​​of the first user, the second user, and the third user is less than or equal to the preset weight value.

4. The method according to claim 1, characterized in that After allowing the first user to log in, the method further includes: In the case where it is monitored that a user in the user group is offline, determining whether the sum of the login weight values ​​of online users in the user group is greater than the preset weight value; If not, an offline operation is performed on the online users in the user group.

5. The method according to claim 1, characterized in that After receiving a login request from the first user, the method further includes: Verifying the login information of the first user; If the verification is successful, determining the user group to which the first user belongs; In the case where the verification fails, a third prompt message is generated, where the third prompt message is used to prompt that the verification of the first user login information has failed.

6. The method according to claim 1, characterized in that The user group is pre-created in the following way: receiving a request from the first user to create the user group; receiving a member invitation request from the first user to a fourth user, where the member invitation request is used to invite the fourth user to join the user group; sending the member invitation request to the fourth user; In case of receiving the confirmation information of the fourth user, the fourth user is set as a member of the user group.

7. The method according to claim 6, characterized in that After creating the user group, the method further includes: receiving weight setting information of the first user, wherein the weight setting information includes a login weight value of each user in the user group and the preset weight value; Sending the weight setting information to other users in the user group; When confirmation information from other users in the user group is received, weight setting is performed according to the weight setting information.

8. A login verification device, characterized in that: include: A receiving module, receiving a login request from a first user; A determination module, determining a user group to which the first user belongs; an acquisition module, acquiring a login weight value of the first user and a login weight value of a second user in the user group, wherein the second user is an online user in the user group, and the login weight value is set by the users in the user group or by the server according to user information, wherein the user information includes the user's activity level and credit rating, and the larger the login weight value of the user, the higher the importance of the user in login verification; The login verification module allows the first user to log in if the sum of the login weight values ​​of the first user and the second user is greater than a preset weight value.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method as claimed in any one of claims 1 to 7.

Images