WO2015024506A1 - 安全认证方法、服务器以及安全认证系统 - Google Patents

安全认证方法、服务器以及安全认证系统 Download PDF

Info

Publication number
WO2015024506A1
WO2015024506A1 PCT/CN2014/084760 CN2014084760W WO2015024506A1 WO 2015024506 A1 WO2015024506 A1 WO 2015024506A1 CN 2014084760 W CN2014084760 W CN 2014084760W WO 2015024506 A1 WO2015024506 A1 WO 2015024506A1
Authority
WO
WIPO (PCT)
Prior art keywords
login
user
account
area
server
Prior art date
Application number
PCT/CN2014/084760
Other languages
English (en)
French (fr)
Inventor
张�杰
许灿冲
Original Assignee
腾讯科技(深圳)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技(深圳)有限公司 filed Critical 腾讯科技(深圳)有限公司
Publication of WO2015024506A1 publication Critical patent/WO2015024506A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication

Definitions

  • the account protection method in the prior art is generally: when detecting that a user's account continuously sends malicious information such as pornography and fraudulent advertisements, the account is frozen, so that the account cannot be permanently used for a period of time or even permanently. log in.
  • Embodiments of the present invention provide a security authentication method, a server, and a security authentication system.
  • the login request further includes login address information
  • the obtaining the location information of the user according to the login request includes:
  • IP Internet Protocol
  • LBS Location Based Service
  • the location information of the user corresponding to the network address of the user is queried according to the correspondence between the network address and the location information.
  • the acquiring the location information of the user according to the login request comprises: acquiring a network address of the user from a message forwarding network element that forwards the login request, where the network address includes an IP address and an LBS address; as well as
  • the location information of the user corresponding to the network address of the user is queried according to the correspondence between the network address and the location information.
  • the method further includes:
  • the common login area of the user is determined according to the historical login behavior.
  • the determining whether the location information meets the preset login condition comprises: determining whether the location information belongs to the common login area, and if yes, determining that the preset login condition is met, if not And determining that the preset login condition is not satisfied.
  • the determining, according to the historical login behavior, the common login area of the account includes: determining, according to a historical login behavior, each login area of the account;
  • the login area where the number of logins reaches the preset value is set as the target login area, and the target login area is used as the common login area of the account.
  • the determining, by the historical login behavior, the common login area of the account includes: determining, according to a historical login behavior, each login area of the account;
  • the login area in which the number of logins in the most recent preset time reaches the preset value is set as the target login area, and the target login area is used as the common login area of the account.
  • the determining, according to the historical login behavior, the common login area of the user includes: determining, according to a historical login behavior, each login area of the account;
  • the security authentication method includes:
  • the login statistics server determines the common login area of the account according to the historical login behavior, and sends the common login area information to the login verification server.
  • the login policy server receives a login request from the user to the account, where the login request includes identification information of the account;
  • the login policy server determines that the account is in a frozen state according to the identifier information, the login policy server acquires location information of the user according to the login request;
  • the login policy server sends the location information of the user to the login verification server; the login verification server determines whether the location information belongs to a common login area of the account, and sends the location information to the login policy server. Judging the result;
  • the login policy server allows the user to log in to the account.
  • the login request further includes login address information
  • the acquiring, by the login policy server, the location information of the user according to the login request includes: the login policy server parsing a network address of the user from the login address information, where the network address includes an Internet Protocol (IP) Address and location-based monthly service (LBS) address;
  • IP Internet Protocol
  • LBS location-based monthly service
  • the login policy server queries the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the acquiring, by the login policy server, location information of the user according to the login request includes:
  • the login policy server acquires a network address of the user from a message forwarding network element that forwards the login request, where the network address includes an IP address and an LBS address;
  • the login policy server queries the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the login statistics server determines, according to the historical login behavior, a common login area of the account, including: The login statistics server determines each login area of the account according to the historical login behavior; the login statistics server sets a login area whose login number reaches a preset value as a target login area, and uses the target login area as the Common login area for the account;
  • the login statistics server determines each login area of the account according to the historical login behavior; and the login statistics server sets a login area whose preset number of logins in the most recent preset duration reaches a preset value as the target login area, and the The target login area serves as a common login area for the account;
  • the login statistics server determines each login area of the account according to the historical login behavior; the login statistics server determines a first reference value of each login area according to the first weight and the number of logins in each login area, according to the second right And a second reference value of each login area is determined by the value and the login time of each login area, and the sum of the first reference value and the second reference value is used as a comprehensive reference value of the login area;
  • the login statistics server uses a login area whose integrated reference value reaches a preset value as a common login area of the account.
  • a receiving unit configured to receive a login request of the user, where the login request includes identifier information of the account that requests the login; the login request acquires location information of the user;
  • the authentication unit is configured to determine whether the location information satisfies a preset login condition, and if yes, allow the user to log in to the account.
  • the login request further includes login address information
  • the obtaining unit includes:
  • a first obtaining module configured to parse a network address of the user from the login address information, where the network address includes an Internet Protocol (IP) address and a location-based monthly service (LBS) address; and
  • IP Internet Protocol
  • LBS location-based monthly service
  • a first query module configured to query according to a correspondence between a network address and location information The location information of the user corresponding to the user's network address.
  • the acquiring unit includes:
  • a second acquiring module configured to acquire, by using a message forwarding network element that forwards the login request, a network address of the user, where the network address includes an IP address and an LBS address;
  • the second query module is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the server further includes:
  • a determining unit configured to determine a common login area of the account according to a historical login behavior.
  • the authentication unit is configured to determine whether the location information belongs to the common login area, and if yes, determine that the preset login condition is met, and if not, determine that the preset is not met. Login conditions.
  • the determining unit includes:
  • a first determining module configured to determine, according to a historical login behavior, each login area of the account; and a third query module, configured to set a login area whose login number reaches a preset value as a target login area, and set the target The login area serves as a common login area for the account.
  • the determining unit includes:
  • a second determining module configured to determine, according to the historical login behavior, each login area of the account; and a fourth query module, configured to set a login area whose preset number of logins in the most recent preset duration reaches a preset value as the target login area, and The target login area serves as a common login area for the account.
  • the determining unit includes:
  • a third determining module configured to determine each of the login areas of the account according to the historical login behavior; and a calculating module, configured to determine, according to the first weight and the number of logins in each login area, a first reference value of each login area, according to the second right And a second reference value of each login area is determined by the value and the login time of each login area, and the sum of the first reference value and the second reference value is used as a comprehensive reference value of the login area;
  • a fourth determining module configured to use a login area where the integrated reference value reaches a preset value as a common login area of the account.
  • the login statistics server is configured to determine a common login area of the account according to the historical login behavior, and send the common login area information to the login verification server;
  • the login policy server is configured to receive a login request of the account by the user, where the login request includes the identifier information of the account, and if it is determined that the account is in a frozen state according to the identifier information, The login request acquires the location information of the user, and sends the location information of the user to the login verification server;
  • the login face server is configured to determine whether the location information belongs to a common login area of the account, and send a determination result to the login policy server.
  • the login policy server is further configured to allow the user to log in to the account.
  • the embodiments of the present invention have the following advantages:
  • the server may receive the login request of the user, where the login request includes the identifier information of the account that requests the login.
  • the server may obtain the location information of the user according to the login request. And determining whether the location information satisfies the preset login condition, and if so, allowing the user to log in to the account. Therefore, when an account is in a frozen state, the server does not reject all users' logins to the account, but according to the location information when the user logs in, when the location information of the user logs in meets the preset login conditions. The user is allowed to log in to the account.
  • FIG. 1 is a schematic diagram of an embodiment of a security authentication method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of another embodiment of a security authentication method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of another embodiment of a security authentication method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of another embodiment of a security authentication method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another embodiment of a security authentication method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of an embodiment of a server according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of another embodiment of a server according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another embodiment of a server according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of another embodiment of a server according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of another embodiment of a server according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of an embodiment of a security authentication system according to an embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • the embodiment of the invention provides a security authentication method, a server and a security authentication system, which can avoid the impact of the freezing process on the account used by a normal user.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • an embodiment of the security authentication method in the embodiment of the present invention includes steps 101 to 104.
  • step 101 the server queries whether the account is in a frozen state by the received user login request. If the account is in a frozen state, the server acquires the location information of the user according to the login request.
  • the server may send a login request to the server, and the server may receive the login request sent by the user, where the login request may include the identifier information of the account that requests the login.
  • the login request may further include a user name, a password, and the like, which is not limited herein.
  • the server may query the current status of the account that the user requests to log in according to the identification information of the account in the login request. If the result of the query indicates that the account is currently in a frozen state, the account currently belongs to the account. An abnormal account needs to monitor the login status of the account, and the server can obtain the location information of the user according to the login request.
  • the location information may be a specific geographic location where the user is logged in, or It is the location of the network, which is not limited here.
  • step 102 the server determines whether the location information satisfies the preset login condition. If yes, step 103 is performed. If not, step 104 is performed.
  • step 103 the user is allowed to log in to the account.
  • the location information satisfies the preset login condition, the current user logs in to the account at a specific location, and the behavior conforms to the historical login habit of the user. Therefore, the user can be identified as a normal user, and the user is allowed to log in. Account.
  • step 104 the user is denied access to the account.
  • the location information does not meet the preset login condition, the current user login behavior does not conform to the user's historical login habits. Therefore, the user may be deemed to be an illegal user, and the user is not allowed to log in to the account.
  • the server may receive the login request of the user, where the login request includes the identifier information of the account that requests the login.
  • the server may obtain the location information of the user according to the login request. And determining whether the location information satisfies the preset login condition, and if so, allowing the user to log in to the account. Therefore, when an account is in a frozen state, the server does not reject all users' logins to the account, but according to the location information when the user logs in, when the location information of the user logs in meets the preset login conditions.
  • the user is allowed to log in to the account. Since the account owner (ie, the normal user) generally logs in a relatively fixed area, the user's login request can be distinguished according to the location information when the user logs in. The impact on the use of accounts by normal users.
  • the server after the server acquires the location information of the user according to the login request, it can be determined whether the location information satisfies the preset login condition. For example, the server may determine the common login area of the user according to the historical login behavior, and then determine whether the obtained location information belongs to the common login area. If yes, determine that the location information meets the preset login condition. If not, Then, it is determined that the location information does not meet the preset login condition. In an actual application, the server may determine the common login area of the user according to the historical login behavior in multiple manners, which are described in detail below.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the server may determine the common login area of the user according to the total number of logins by the user.
  • another embodiment of the security authentication method in the embodiment of the present invention includes step 201 to step. Step 207.
  • step 201 the server determines the login area of the account based on the historical login behavior.
  • the logged-in user can report the login behavior information to the server from time to time.
  • the login behavior information includes the account of the logged-in user, the login time, and the logged-in IP address.
  • the login behavior reported by the login user can be as shown in Table 1:
  • the server may collect the login behavior information reported after the account is logged in, so that multiple login areas of the account can be determined from these historical login behaviors.
  • the server can determine, according to the IP address, the geographical location where the login user logs in, that is, the login area.
  • the historical login behavior collected by the server can be as shown in Table 2.
  • the server can determine the account "Tencentl l l” through Table 2, and the total number of logins is 19, and the login areas are "Shenzhen", “Guangzhou”, “Beijing”, and "Shanghai”.
  • step 202 the server sets the login area whose number of logins reaches the preset value as the target login area, and uses the target login area as the common login area of the account.
  • the preset value may be an absolute value (for example, 10 times or 20 times, etc.), or may be a relative value (for example, 30% or more of the total number of logins in all login areas of the account, or 40) %, etc., in the present embodiment, an absolute value is taken as an example for explanation.
  • the login area is the most common. For example, the login area with the most login times is selected in all the login areas of the account.
  • step 203 the server receives a user login request for the account.
  • the server may send a login request to the server, and the server may receive the login request sent by the user, where the login request may include the identification information of the account requesting the login.
  • the login request may further include a user name, a password, and the like.
  • the body is not limited here.
  • the login request sent by the user may be as shown in Table 3:
  • step 204 if the server determines that the account is in a frozen state, the server acquires the location information of the user according to the login request.
  • the server after receiving the login request sent by the user, the server does not directly reject the login request of the user, but sends the login request according to the user.
  • the login request gets the user's location information.
  • the server may obtain the location information of the user in multiple manners, for example: 1.
  • the server may obtain the location information of the user from the login request.
  • the server can parse the network address of the user (that is, the "login IP address" as shown in Table 3) from the login address information, and use the login IP address. As the location information of the user.
  • the location information may be an address based service (LBS) address or other type of content that can be used to represent location information, in addition to being an IP address. This is not limited here.
  • LBS address based service
  • the server may obtain the location information of the user from the message forwarding network element that forwards the login request. If the login request sent by the user does not carry the login address information, the user may use the message forwarding network element (for example, a proxy server). In order to obtain the accurate location information of the user, the server may obtain the network address of the user from the message forwarding network element that forwards the login request, and the network address may be an IP address, or an LBS address, or other types can be used. The content of the location information is not limited here.
  • the server After obtaining the network address of the user, the server can query the location information of the user according to the correspondence between the network address and the location information.
  • the server can query The location information to the user is "Guangzhou”.
  • step 205 the server determines whether the location information belongs to the common login area. If yes, step 206 is performed. If not, step 207 is performed.
  • step 206 the user is allowed to log in to the account.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area. This behavior is consistent with the historical login habit of the login user of the account. Therefore, the user can be identified as a normal user, and the user is allowed to log in. Account.
  • the common login area of the account is "Shenzhen” and "Guangzhou”
  • the login IP address in the login request sent by the user is 59.41.178.123
  • the corresponding location information is "Guangzhou”
  • the server allows the user to log in to the account Tencentl 11.
  • step 207 the user is denied access to the account.
  • the location information does not belong to the common login area
  • the current user does not log in to the account in the common login area. This behavior does not match the historical login habit of the login user of the account. Therefore, the user can be identified as an illegal user. The user is denied access to the account.
  • the common login area of the account is "Shenzhen" and "Guangzhou”. If the login IP address in the login request sent by the user is 58.35.248.33, and the corresponding location information is "Shanghai,", the If the location information does not belong to the common login area of the account, the user is an illegal user, and the server can reject the user login account Tencentl ll.
  • the server may determine a common login area of the account according to the historical login behavior.
  • the server may obtain the location information of the user according to the login request, if the location information If the user is a normal user, the user is allowed to log in to the account. Therefore, the user's login request can be distinguished according to the location information when the user logs in. This can effectively prevent the impact of the freeze on the normal user account. .
  • the above embodiment describes a scheme in which the server determines the user's common login area according to the total number of logins by the user. Another scheme is described below.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the server may determine the user's common login according to the user's login in the near future.
  • another embodiment of the security authentication method in the embodiment of the present invention includes steps 301 to 308.
  • step 301 the server determines the login area of the account based on the historical login behavior.
  • the login can report the login behavior information to the server from time to time.
  • the login behavior information includes the account of the logged-in user, the login time, and the registered IP address.
  • the login behavior information reported by the login user can be as shown in Table 1, and is not described here.
  • the server can collect the login behavior information reported after the account is logged in, so it is possible to determine a plurality of login areas of the account from these historical login behaviors.
  • the server can determine, according to the IP address, the geographical location where the login user logs in, that is, the login area.
  • the historical login behavior collected by the server may be as shown in Table 2, and is not described here.
  • the server can determine the account "Tencentl i r" through Table 2, and the total login time is 19 times.
  • the login areas are "Shenzhen”, “Guangzhou”, “Beijing”, and "Shanghai”.
  • step 302 the server sets the login area whose preset number of logins in the most recent preset duration reaches the preset value as the target login area, and uses the target login area as the common login area of the account.
  • the last preset duration can be determined according to the actual situation. For example, it can be one week, half a month, one month, one quarter, half year, etc. In the embodiment, half a month is taken as an example for description.
  • the preset value in this embodiment may be an absolute value (for example, 10 times or 20 times, etc.), or may be a relative value (for example, 30 of the total number of logins in each login area in the most recent preset duration) % or more, or 40%, etc.)
  • an absolute value is taken as an example for explanation.
  • the preset value is 8 times, "Guangzhou” can be set as the target registration area.
  • the target login area is "Guangzhou”
  • the user's common login area can be determined as "Guangzhou”. It is to be understood that, in addition to the manner in which the preset value is set, the common login area may be determined in other manners, for example, the login area with the most login times is selected in all the login areas, and is not limited herein.
  • step 303 the server receives a user login request for the account.
  • the server may send a login request to the server, and the server may receive the login request sent by the user, where the login request may include an identifier of the account that requests the login.
  • the login request may also be Further, the user name, the password, and the like are included, and the details are not limited herein.
  • the login request sent by the user may be as shown in Table 3, and details are not described herein again.
  • the server determines that the account is in a frozen state, the server obtains the location information of the user according to the login request.
  • the server does not directly reject the user after receiving the login request sent by the user.
  • the login request but the location information of the user is obtained according to the login request sent by the user.
  • the server may obtain the location information of the user in a plurality of manners, and the specific manner is the same as that described in step 204 in the embodiment shown in FIG. 2, and details are not described herein again.
  • step 305 the server determines whether the location information belongs to the common login area. If yes, step 306 is performed. If not, step 307 is performed.
  • step 306 the user is allowed to log in to the account.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area. This behavior is consistent with the user's historical login habits. Therefore, the user can be identified as a normal user, and the user is allowed to log in to the account.
  • the common login area of the account is "Guangzhou”
  • the login IP address in the login request sent by the user is 59.41.178.123
  • the corresponding location information is "Guangzhou”
  • the location information may be determined to belong to the user.
  • the common login area indicates that the user is a normal user, and the server allows the user to log in to the account Tencentl ll.
  • step 307 the user is denied login to the account.
  • the location information does not belong to the common login area
  • the current user does not log in to the account in the common login area. This behavior does not match the historical login habit of the login user of the account. Therefore, the user can be identified as an illegal user. The user is denied access to the account.
  • the common login area of the account is "Guangzhou”. If the login IP address in the login request sent by the user is 58.35.248.33 and the corresponding location information is "Shanghai", it may be determined that the location information does not belong to the location information.
  • the common login area of the account indicates that the user is an illegal user, and the server can reject the user login account Tencentl 11.
  • the server may determine a common login area of the account according to the historical login behavior.
  • the server may obtain the location information of the user according to the login request, if the location information If the user is a normal user, the user is allowed to log in to the account. Therefore, the user's login request can be distinguished according to the location information when the user logs in. This can effectively prevent the impact of the freeze on the normal user account. .
  • Embodiment 4 describes a scheme in which the server determines the common login area of the user according to the number of times the user has recently preset the login. Another solution is described below.
  • Embodiment 4 is described below.
  • the server can determine the common login area of the user according to the login time and the number of logins.
  • another embodiment of the security authentication method in the embodiment of the present invention includes steps 401 to 407.
  • step 401 the server determines the login area of the account based on the historical login behavior.
  • the logged-in user can report the login behavior information to the server from time to time.
  • the login behavior information includes the account of the logged-in user, the login time, and the logged-in IP address.
  • the login behavior information reported by the user may be as shown in Table 1, and details are not described herein again.
  • the server can collect the login behavior information reported after the account is logged in, so it is possible to determine a plurality of login areas of the account from these historical login behaviors.
  • the server can determine, according to the IP address, the geographical location where the login user logs in, that is, the login area.
  • the historical login behavior collected by the server can be as shown in Table 5.
  • the server can confirm that the login account "Tencentl ll" has been registered 17 times in total through the table 5.
  • the login areas are "Shenzhen (8 times),, “Guangzhou (7 times),,” “Beijing (1 time),,,” Shanghai (1 time) ".
  • the server determines a first reference value of each login area according to the first weight and the number of logins in each login area, and determines a second of each login area according to the second weight and the login time of each login area.
  • the reference value is used, and the sum of the first reference value and the second reference value is used as a comprehensive reference value of the login area.
  • the server can comprehensively consider the number of logins and the login time of each login area, and calculate a comprehensive reference value according to different weights.
  • the first reference value can be calculated as follows: For a certain login area, each login can be counted as a 10-point reference value, and the first weight is 0.9, then the first reference value is: 0.9* (total number of logins* 10 ).
  • the second reference value may be calculated as follows: For a certain login area, the second weight is 0.3, and the registration time of each login in the login area minus the reference time is added and multiplied by the second weight. The value is the second weight of the login area. For ease of understanding, the following is a specific example. Assuming that the reference time is July 1, 2013, the comprehensive reference values for each region are shown in Table 6.
  • step 402 the server sets the login area whose integrated reference value reaches the preset value as the target login area, and uses the target login area as the common login area of the account.
  • the login area with the highest comprehensive reference value can be used as the common login area of the account, and the common login area of the account is "Guangzhou,”.
  • the server receives a login request from the user.
  • the server may send a login request to the server, and the server may receive the login request sent by the user, where the login request may include the identifier information of the account that requests the login.
  • the login request may further include a user name, a password, and the like, which are not limited herein.
  • the login request sent by the user may be as shown in Table 3, and details are not described herein again.
  • step 404 if the server determines that the account is in a frozen state, the server is requested according to the login. Find the location information of the user.
  • the server after receiving the login request sent by the user, the server does not directly reject the login request of the user, but according to the user.
  • the sent login request gets the location information of the user.
  • the server may obtain the location information of the user in a plurality of manners, and the specific manner is the same as that described in step 204 in the embodiment shown in FIG. 2, and details are not described herein again.
  • step 405 the server determines whether the location information belongs to the common login area. If yes, step 406 is performed. If not, step 407 is performed.
  • step 406 the user is allowed to log in to the account.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area. This behavior is consistent with the historical login habit of the login user of the account. Therefore, the user can be identified as a normal user, and the user is allowed to log in. Account.
  • the common login area of the account is "Guangzhou”
  • the login IP address in the login request sent by the user is 59.41.178.123
  • the corresponding location information is "Guangzhou”
  • the location information may be determined to belong to the user.
  • the common login area indicates that the user is a normal user, and the server allows the user to log in to the account Tencentl ll.
  • step 407 the user is denied access to the account.
  • the location information does not belong to the common login area
  • the current user does not log in to the account in the common login area. This behavior does not match the historical login habit of the login user of the account. Therefore, the user can be identified as an illegal user. The user is denied access to the account.
  • the common login area of the account is "Guangzhou”. If the login IP address in the login request sent by the user is 58.35.248.33 and the corresponding location information is "Shanghai", it may be determined that the location information does not belong to the location information.
  • the common login area of the account indicates that the user is an illegal user, and the server can reject the user login account Tencentl 11.
  • the server may determine a common login area of the account according to the historical login behavior.
  • the server may obtain the location information of the user according to the login request, if the location information If the user is a normal user, the user is allowed to log in to the account. Therefore, the user can log in to the user according to the location information when logging in. influences.
  • the "server” described in the foregoing embodiment may be a specific server or a server cluster composed of several servers.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • another embodiment of the security authentication method in the embodiment of the present invention includes steps 501 to 507.
  • the login statistics server determines the login area of the account based on the historical login behavior.
  • the logged-in user can report the login behavior information to the login statistic server from time to time.
  • the login behavior information includes information such as the account of the logged-in user, the time of login, and the logged-in IP address.
  • step 502 the login statistics server sends the common login area information to the login verification server.
  • the login statistics server can collect the login behavior information reported by the login user of the account after each login, so each login area of the account can be determined from these historical login behaviors.
  • the login statistics server can determine the login area of the account by the following method.
  • the login statistics server determines each login area of the account based on the historical login behavior, and the login statistics server sets the login area whose login count reaches the preset value as the target login area, and uses the target login area as the common login area of the account.
  • the login statistics server determines each login area of the account according to the historical login behavior, and the login statistics server sets the login area whose preset number of logins in the most recent preset time reaches the preset value as the target login area, and uses the target login area as the user's common area. Login area.
  • the login statistics server determines each login area of the account according to the historical login behavior, and the login statistics server determines the first of each login area according to the first weight and the number of logins in each login area. a reference value, determining a second reference value of each login area according to the second weight and the login time of each login area, and using the sum of the first reference value and the second reference value as a comprehensive reference value of the login area, and logging statistics
  • the server uses the login area whose integrated reference value reaches the preset value as the common login area of the account.
  • step 503 the login policy server receives the login request of the user.
  • the login policy can be sent to the login policy server, and the login policy server can receive the login request sent by the user, and the login request can include the identifier information of the account that requests the login.
  • the login request may further include a user name, a password, and the like, which are not limited herein.
  • step 504 if the login policy server determines that the account is in a frozen state, the login policy server obtains the location information of the user according to the login request.
  • the login policy server does not directly reject the login request of the user after receiving the login request sent by the user, but The login request sent by the user obtains the location information of the user.
  • the login policy server can obtain the location information of the user in multiple manners, which may be as follows.
  • the server can obtain the location information of the user from the login request.
  • the login policy server may parse the network address of the user from the login address information, where the network address is an IP address or an LBS address; and the login policy server according to the network address and location information Corresponding relationship between the user and the location information of the user corresponding to the network address of the user.
  • the server can obtain the location information of the user from the message forwarding network element that forwards the login request.
  • the login policy server obtains the network address of the user from the message forwarding network element that forwards the login request, and the network address is an IP address or an LBS address;
  • the login policy server queries the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information. It should be noted that the manner of obtaining the location information of the user is consistent with the content described in step 204 in the embodiment shown in FIG. 2, and details are not described herein again.
  • step 505 the login policy server sends the user's location information to the login verification server.
  • step 506 the login verification server determines whether the location information belongs to a common login area of the account, and transmits the determination result to the login policy server.
  • the login verification server After the login verification server obtains the location information of the user according to the login request, it can determine whether the location information belongs to the common login area of the account, and sends the determination result to the login policy server.
  • step 507 if the result of the determination is yes, the login policy server allows the user to log in to the account.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area of the account. This behavior is consistent with the historical login habit of the login user of the account. Therefore, the user can be identified as a normal user.
  • the policy server allows the user to log in to the account.
  • the login statistics server may determine a common login area of the account according to the historical login behavior.
  • the login policy server receives the login request of the user, if the account is in a frozen state, the location information of the user may be obtained according to the login request. If the location information belongs to the common login area, the user can be identified as a normal user, and the user is allowed to log in to the account. Therefore, the user may be prevented from freezing to the normal user according to the location information when the user logs in. The impact of using an account.
  • the security authentication method in the embodiment of the present invention has been described above.
  • the embodiment of the present invention further provides a server.
  • the server in the embodiment of the present invention may include a receiving unit 601, an obtaining unit 602, and an authentication unit 603.
  • the receiving unit 601 is configured to receive a login request of the user, where the login request includes identifier information of the account that requests the login.
  • the obtaining unit 602 is configured to query, by the user login request received by the receiving unit 601, whether the account to be logged in is in a frozen state, and if the account is in a frozen state, acquire the location information of the user according to the login request.
  • the authentication unit 603 is configured to determine whether the location information meets a preset login condition, and if yes, allow the user to log in to the account.
  • the receiving unit 601 may receive the login request of the user, where the login request includes the identifier information of the account that requests the login.
  • the obtaining unit 602 determines that the account is in the frozen state according to the identifier information
  • the user may obtain the user according to the login request.
  • the location information is determined by the authentication unit 603 whether the location information satisfies the preset login condition. If yes, the user is allowed to log in to the account, so when an account is in a frozen state, the server does not reject all users for the account. Logging in, but distinguishing according to the location information when the user logs in.
  • the user When the location information when the user logs in meets the preset login condition, the user is allowed to log in to the account, since the account owner (ie, the normal user) generally The fixed area is used for login. Therefore, the user's login request can be distinguished according to the location information when the user logs in. This can effectively avoid the impact of the freeze processing on the normal user account.
  • the authentication unit 603 may determine whether the location information satisfies the preset login condition. For example, the server may determine the common login area of the account according to the historical login behavior, and then determine whether the obtained location information belongs to the common login area of the account, and if yes, determine that the preset login condition is met, if not, It is determined that the preset login condition is not met. In an actual application, the server can determine the common login area of the user according to the historical login behavior in various manners, which are described in detail below.
  • the server may determine a common login area of the account according to the number of times the account is logged in.
  • the server may include a receiving unit 701, an obtaining unit 702, and an authentication unit 703.
  • the receiving unit 701 is configured to receive a login request of the user, where the login request includes identifier information of the account that requests to log in.
  • the obtaining unit 702 is configured to query, by the user login request received by the receiving unit 701, whether the account to be logged in is in a frozen state, and if the account is in a frozen state, obtain the location information of the user according to the login request.
  • the authentication unit 703 is configured to determine whether the location information satisfies a preset login condition, and if yes, allow the user to log in to the account.
  • the server in this embodiment may further include:
  • the determining unit 704 is configured to determine a common login area of the account according to the historical login behavior.
  • the authentication unit 703 may be configured to determine whether the location information belongs to the common login area, and if yes, determine that the preset login condition is met, and if not, determine The login condition for this preset is not met.
  • the determining unit 704 in this embodiment may further include:
  • a first determining module 7041 configured to determine, according to a historical login behavior, each login area of the account
  • the third query module 7042 is configured to set a login area where the number of logins reaches a preset value as a target login area, and use the target login area as a common login area of the account.
  • the obtaining unit 702 in this embodiment may include:
  • the first obtaining module 7021 is configured to parse the network address of the user from the login address information, where the network address is an IP address, or an LBS address;
  • the first query module 7022 is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the obtaining unit 702 in this embodiment may include:
  • the second obtaining module 7023 is configured to obtain, by using a message forwarding network element that forwards the login request, a network address of the user, where the network address is an IP address, or an LBS address;
  • the second query module 7024 is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the logged-in user can report the login behavior information to the server from time to time.
  • the login behavior information includes the account of the logged-in user, the login time, and the logged-in IP address.
  • the server may collect the login behavior information reported after the account is logged in. Therefore, the first determining module 7041 in the determining unit 704 can determine each login area of the account from the historical login behaviors. It should be noted that, because the login behavior information reported by the login user includes the login IP address, the server can determine, according to the IP address, the geographical location actually located when the login user logs in, that is, the login area.
  • the third query module 7042 in the determining unit 704 may set the login area whose login number reaches the preset value as the target login.
  • the zone and the target login zone is used as the common login zone for the account.
  • the common login area may be determined in other manners, for example, the login area with the most login times is selected in each login area, and is not limited herein.
  • the login request can be sent to the server, and the receiving unit 701 can receive the login request sent by the user, and the login request can include the identification information of the account that requests the login.
  • the login request may further include a user name, a password, and the like, which are not limited herein.
  • the obtaining unit 702 can obtain location information of the user in multiple manners.
  • the obtaining unit 702 can obtain the location information of the user from the login request.
  • the first obtaining module 7021 in the obtaining unit 702 parses the network address of the user from the login address information, where the network address is an IP address, or an LBS address, or It is a content that other types can be used to represent location information, and is not limited herein.
  • the first query module 7022 of the obtaining unit 702 queries the location information of the user corresponding to the network address of the user according to the corresponding relationship between the network address and the location information.
  • the obtaining unit 702 obtains the location information of the user from the message forwarding network element that forwards the login request.
  • the user may use the message forwarding network element (for example, the proxy server) to log in.
  • the second acquisition module in the obtaining unit 702 The 7023 may obtain the network address of the user from the message forwarding network element that forwards the login request, where the network address is an IP address, or an LBS address, or The type of his can be used to represent the content of the location information, which is not limited herein.
  • the second query module 7024 of the obtaining unit 702 queries the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the authentication unit 703 can determine whether the location information belongs to the common login area.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area. This behavior is consistent with the historical login habit of the login user of the account. Therefore, the user can be identified as a normal user, and the user is allowed to log in. Account.
  • the location information does not belong to the common login area
  • the current user does not log in to the account in the common login area. This behavior does not match the historical login habit of the login user of the account. Therefore, the user can be identified as an illegal user. The user is denied access to the account.
  • the determining unit 704 may determine a common login area of the account according to the historical login behavior.
  • the receiving unit 701 receives the login request of the user, if the account is in a frozen state, the obtaining unit 702 may acquire the user according to the login request.
  • the location information if the location information belongs to the common login area, the authentication unit 703 can determine that the user is a normal user, and then allow the user to log in to the account. Therefore, it is effective to distinguish the login request of the user according to the location information when the user logs in. The effect of avoiding the freeze processing on the account used by normal users.
  • the server may determine a common login area of the account according to the number of times the account user is logged in.
  • another embodiment of the server in the embodiment of the present invention includes a receiving unit 801, an obtaining unit 802, and an authentication unit 803. .
  • the receiving unit 801 is configured to receive a login request of the user, where the login request includes identifier information of the account that requests to log in;
  • the obtaining unit 802 is configured to query, by the user login request received by the receiving unit 801, whether the account to be logged in is in a frozen state, and if the account is in a frozen state, obtain the location information of the user according to the login request.
  • the authentication unit 803 is configured to determine whether the location information meets a preset login condition, and if yes, The user is allowed to log in to the account.
  • the determining unit 804 is configured to determine a common login area of the account according to the historical login behavior.
  • the authentication unit 803 may be configured to determine whether the location information belongs to the common login area, and if yes, determine that the preset login condition is met, if not, Determine that the login condition for this preset is not met.
  • the determining unit 804 in this embodiment may further include:
  • a second determining module 8041 configured to determine, according to a historical login behavior, each login area of the account
  • the fourth query module 8042 sets a login area where the number of logins in the most recent preset time reaches the preset value as the target login area, and uses the target login area as a common login area of the account.
  • the obtaining unit 802 in this embodiment may include:
  • the first obtaining module 8021 is configured to parse the network address of the user from the login address information, where the network address is an IP address, or an LBS address;
  • the first query module 8022 is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the obtaining unit 802 in this embodiment may include:
  • the second obtaining module 8023 is configured to obtain, by using a message forwarding network element that forwards the login request, a network address of the user, where the network address is an IP address, or an LBS address;
  • the second query module 8024 is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the logged-in user can report the login behavior information to the server from time to time.
  • the login behavior information includes the account of the logged-in user, the login time, and the logged-in IP address.
  • the server may collect the login behavior report reported after the account is logged in. Therefore, the second determining module 8041 in the determining unit 804 can determine each of the login areas of the account from these historical login behaviors.
  • the server can determine, according to the IP address, the geographical location where the login user logs in, that is, the login area.
  • the fourth query module 8042 in the determining unit 804 may reach the login area of the preset number of times in the most recent preset time period. Set as the target login area and use the target login area as the common login area for the account.
  • the most recent preset duration in this embodiment may be determined according to the actual situation, and may be, for example, one week, one half month, one month, one quarter, half year, etc., which is not limited herein.
  • the preset value in this embodiment may be an absolute value (for example, 10 times or 20 times, etc.), or may be a relative value (for example, 30 of the total number of logins in each login area in the most recent preset duration) % or more, or 40%, etc.), which is not limited here.
  • the common login area may be determined in other manners, for example, the login area having the most login times is selected in each login area, and the specificity is not limited herein.
  • the login request can be sent to the server, and the receiving unit 801 can receive the login request sent by the user, and the login request can include the identification information of the account that requests the login.
  • the login request may further include a user name, a password, and the like, which are not limited herein.
  • the obtaining unit 802 can obtain location information of the user in multiple manners.
  • the obtaining unit 802 directly obtains the location information of the user from the login request.
  • the first obtaining module 8021 in the obtaining unit 802 parses the network address of the user from the login address information, where the network address is an IP address, or an LBS address, or It is a content that other types can be used to represent location information, and is not limited herein.
  • the first query module 8022 in the obtaining unit 802 is based on the pair between the network address and the location information. In response, the location information of the user corresponding to the network address of the user is queried.
  • the obtaining unit 802 obtains the location information of the user from the message forwarding network element that forwards the login request.
  • the user may use a message forwarding network element (for example, a proxy server) to log in.
  • a message forwarding network element for example, a proxy server
  • the 8023 can obtain the network address of the user from the message forwarding network element that forwards the login request, and the network address is an IP address, or an LBS address, or other types of content that can be used to indicate location information, which is not limited herein. .
  • the second query module 8024 of the obtaining unit 802 queries the location information of the user corresponding to the network address of the user according to the corresponding relationship between the network address and the location information.
  • the authentication unit 803 can determine whether the location information belongs to the common login area.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area. This behavior is consistent with the historical login habit of the login user of the account. Therefore, the user can be identified as a normal user, and the user is allowed to log in. Account.
  • the location information does not belong to the common login area
  • the current user does not log in to the account in the common login area. This behavior does not match the historical login habit of the login user of the account. Therefore, the user can be identified as an illegal user. The user is denied access to the account.
  • the determining unit 804 may determine a common login area of the account according to the historical login behavior.
  • the receiving unit 801 receives the login request of the user, if the account is in a frozen state, the obtaining unit 802 may acquire the user according to the login request.
  • the location information if the location information belongs to the common login area, the authentication unit 803 can determine that the user is a normal user, and then allow the user to log in to the account. Therefore, it is effective to distinguish the login request of the user according to the location information when the user logs in. The effect of avoiding the freeze processing on the account used by normal users.
  • the server may determine the common login area of the account according to the total number of times the account is logged in and the login time.
  • another embodiment of the server in the embodiment of the present invention includes The receiving unit 901, the obtaining unit 902, and the authentication unit 903 are included.
  • the receiving unit 901 is configured to receive a login request of the user, where the login request includes identifier information of the account that requests to log in.
  • the obtaining unit 902 is configured to query, by the user login request received by the receiving unit 901, whether the account to be logged in is in a frozen state, and if the account is in a frozen state, obtain the location information of the user according to the login request.
  • the authentication unit 903 is configured to determine whether the location information satisfies a preset login condition, and if yes, allow the user to log in to the account.
  • the determining unit 904 is configured to determine a common login area of the account according to the historical login behavior.
  • the authentication unit 903 may be configured to determine whether the location information belongs to the common login area, and if yes, determine that the preset login condition is met, if not, Determine that the login condition for this preset is not met.
  • the determining unit 904 in this embodiment may further include:
  • a third determining module 9041 the user determines each login area of the account according to the historical login behavior;
  • the calculating module 9042 is configured to determine a first reference value of each login area according to the first weight and the number of logins in each login area, according to the first Determining a second reference value of each login area by using a second weight and a login time in each login area, and using a sum of the first reference value and the second reference value as a comprehensive reference value of the login area;
  • the fourth determining module 9043 is configured to use a login area where the integrated reference value reaches a preset value as a common login area of the account.
  • the obtaining unit 902 in this embodiment may include:
  • the first obtaining module 9021 is configured to parse the network address of the user from the login address information, where the network address is an IP address, or an LBS address;
  • the first query module 9022 is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the obtaining unit 902 in this embodiment may include:
  • the second obtaining module 9023 is configured to acquire the user from a message forwarding network element that forwards the login request.
  • Network address the network address is an IP address, or an LBS address;
  • the second query module 9024 is configured to query the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the logged-in user can report the login behavior information to the server from time to time.
  • the login behavior information includes the account of the logged-in user, the login time, and the logged-in IP address.
  • the server may collect the login behavior information reported after the account is logged in, so the third determining module 9041 in the determining unit 904 can determine each login area of the account from these historical login behaviors.
  • the server can determine, according to the IP address, the geographical location where the login user logs in, that is, the login area i or .
  • the calculating module 9042 in the determining unit 904 may determine a first reference value of each login area according to the first weight and the number of logins in each login area, and determine each login area according to the second weight and the login time in each login area. And a second reference value, and the sum of the first reference value and the second reference value is used as a comprehensive reference value of the login area.
  • the determining unit 904 can comprehensively consider the number of logins and the login time of each login area, and calculate a comprehensive reference value according to different weights.
  • the first reference value can be calculated as follows: For a certain login area, each login can be counted as a 10-point reference value, and the first weight is 0.9, then the first reference value is: 0.9* (total number of logins* 10 ).
  • the second reference value may be calculated as follows: For a certain login area, the second weight is 0.3, and the registration time of each login in the login area minus the reference time is added and multiplied by the second weight. The value is the second weight of the login area.
  • the comprehensive reference value of each area can be as shown in Table 6 above, and details are not described here.
  • the fourth determination module 9043 in the determination unit 904 may use the login area whose integrated reference value reaches the preset value as the common login area of the account.
  • the login request may be sent to the server, and the receiving unit 901 may receive the login request sent by the user, where the login request may include the identification information of the account requesting the login.
  • the login request may further include a user name, a password, and the like, which are not limited herein.
  • the obtaining unit 902 can obtain location information of the user in multiple manners.
  • the obtaining unit 902 obtains the location information of the user from the login request.
  • the first obtaining module 9021 in the obtaining unit 902 parses the network address of the user from the login address information, where the network address is an IP address, or an LBS address, or It is a content that other types can be used to represent location information, and is not limited herein.
  • the first query module 9022 of the obtaining unit 902 queries the location information of the user corresponding to the network address of the user according to the corresponding relationship between the network address and the location information.
  • the obtaining unit 902 obtains the location information of the user from the message forwarding network element that forwards the login request. If the login request sent by the user does not carry the login address information, the user may use the message forwarding network element (for example, a proxy server). In order to obtain the accurate location information of the user, the second obtaining module 9023 in the obtaining unit 902 can obtain the network address of the user from the message forwarding network element that forwards the login request, and the network address is an IP address, or is an LBS. The address, or other type, can be used to represent the location information, which is not limited herein.
  • the second query module 9024 in the obtaining unit 902 queries the location information of the user corresponding to the network address of the user according to the corresponding relationship between the network address and the location information.
  • the authentication unit 903 can determine whether the location information belongs to the common login area.
  • the location information belongs to the common login area
  • the current user logs in to the account in the common login area. This behavior is consistent with the historical login habit of the login user of the account, so it can be determined that the user is used. If the user is a normal user, the user is allowed to log in to the account.
  • the location information does not belong to the common login area
  • the current user does not log in to the account in the common login area. This behavior does not match the historical login habit of the login user of the account. Therefore, the user can be identified as an illegal user. The user is denied access to the account.
  • the determining unit 904 may determine a common login area of the account according to the historical login behavior.
  • the receiving unit 901 receives the login request of the user, if the account is in a frozen state, the obtaining unit 902 may acquire the user according to the login request.
  • the location information if the location information belongs to the common login area, the authentication unit 903 can determine that the user is a normal user, and then allow the user to log in to the account. Therefore, it is effective to distinguish the login request of the user according to the location information when the user logs in. The effect of avoiding the freeze processing on the account used by normal users.
  • the server in the embodiment of the present invention has been described above from the perspective of various functional structures of the server.
  • the embodiment of the present invention further provides a server, wherein the functional modules implemented by the server in the embodiment of the present invention are integrated, as shown in FIG. 10, which shows a schematic structural diagram of a server involved in the embodiment of the present invention.
  • the server may include one or more processing core processor 1001, one or more computer readable storage media memories 1002, a radio frequency (RF) circuit 1003, a wireless communication module such as a Bluetooth module and/or wireless protection.
  • RF radio frequency
  • WIFI Wireless Fidelity
  • module 1004 (such as WIFI module 1004 in FIG. 10), power supply 1005, sensor 1006, input unit 1007, and display unit 1008.
  • the processor 1001 is the control center of the server, connecting various portions of the entire server using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 1002, and recalling data stored in the memory 1002, Execute the various functions of the server and process the data to monitor the server as a whole.
  • the processor 1001 may include one or more processing cores.
  • the processor 1001 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application, and the like, and the modem processor mainly processes wireless communication. It can be understood that the above modem processor may not be integrated into the processor 1001.
  • the memory 1002 can be used to store software programs and modules, and the processor 1001 executes various functional applications and data processing by running software programs and modules stored in the memory 1002.
  • the memory 1002 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the server, etc.
  • the memory 1002 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 1002 can also include a memory controller to provide access to memory 1002 by processor 1001.
  • the RF circuit 1003 can be used for receiving and transmitting signals during the transmission and reception of information. Specifically, after receiving the downlink information of the base station, it is processed by one or more processors 1001; in addition, the uplink data is transmitted to the base station.
  • the RF circuit 1003 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, and a low noise amplifier (Low Noise). Amplifier, LNA), duplexer, etc.
  • the RF circuit 1003 can also communicate with the network and other devices through wireless communication.
  • the wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), and code division multiple access ( Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), etc.
  • GSM Global System of Mobile communication
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • E-mail Short Messaging Service
  • WIFI is a short-range wireless transmission technology.
  • the server can send and receive electronic mail and access streaming media through the WIFI module 1004, which can provide wireless broadband Internet access.
  • FIG. 10 shows the WIFI module 1004, it is to be understood that it does not belong to the essential configuration of the server, and may be omitted as needed within the scope of not changing the essence of the invention.
  • the server also includes a power source 1005 (such as a battery) that supplies power to the various components.
  • the power source can
  • the utility model is connected to the processor 1001 through a power management system, thereby realizing functions such as managing charging, discharging, and power consumption management through the power management system.
  • the power supply 1005 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
  • the server may also include at least one type of sensor 1006, such as a light sensor, a motion sensor, and other sensors.
  • the server can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors, and other sensors, and will not be described here.
  • the server can also include an input unit 1007 that can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • input unit 1007 can include a touch-sensitive surface as well as other input devices. Touch-sensitive surfaces, also known as touch screens or trackpads, collect touch operations on or near the user (such as the user using a finger, stylus, etc., any suitable object or accessory on a touch-sensitive surface or touch-sensitive Operation near the surface), and drive the corresponding connecting device according to a preset program.
  • the touch sensitive surface can include both a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information
  • the processor 1001 is provided and can receive commands from the processor 1001 and execute them.
  • touch-sensitive surfaces can be implemented in a variety of types, including resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 1007 can also include other input devices. Specifically, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, a joystick, and the like.
  • the server can also include a display unit 1008 that can be used to display information entered by the user or information provided to the user and various graphical user interfaces of the server, which can be composed of graphics, text, icons, video, and It is composed of any combination.
  • the display unit 1008 may include a display panel.
  • the display panel may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the touch-sensitive surface may cover the display panel, and when the touch-sensitive surface detects a touch operation thereon or nearby, it is transmitted to the processor 1001 to determine the type of the touch event, and then the processor 1001 displays according to the type of the touch event. A corresponding visual output is provided on the panel.
  • touch The sensitive surface and display panel are implemented as two separate components to implement input and input functions, but in some embodiments, the touch-sensitive surface can be integrated with the display panel to implement input and output functions.
  • the server may further include a camera, a Bluetooth module, and the like, and details are not described herein again.
  • the processor 1001 in the server loads the executable file corresponding to the process of one or more applications into the memory 1002 according to the following instructions, and is processed by the processor.
  • the 1001 is configured to run an application stored in the memory 1002, thereby implementing various functions, as follows: receiving a login request of a user, where the login request includes identification information of an account requesting login; if it is determined that the account is in a frozen state, according to the Login request to obtain location information of the user;
  • the security authentication system in the embodiment of the present invention includes: a login statistics server 1101, a login policy server 1102, and a login verification server 1103.
  • the login statistics server 1101 is configured to determine a common login area of the account according to the historical login behavior, and send the common login area information to the login verification server 1103.
  • the login policy server 1102 is configured to receive a login request of the user, where the login request includes the identifier information of the account that requests the login, and if the account is determined to be in a frozen state according to the identifier information, obtain the location information of the user according to the login request, The location information of the user is transmitted to the login verification server 1103.
  • the login verification server 1103 is configured to determine whether the location information belongs to a common login area of the user, and send the determination result to the login policy server 1102.
  • the login policy server 1102 is further configured to allow the user to log in to the account.
  • the logged-in user may report the login behavior information to the login statistics server 1101 from time to time.
  • the login behavior information includes the account of the logged-in user. Recorded time, registered IP address and other information.
  • the login statistics server 1101 can collect the login behavior information reported after the account is logged in, so each login area of the account can be determined from these historical login behaviors.
  • the specific determination method can be as follows.
  • the login statistics server 1101 determines each login area of the account based on the history registration behavior, and the login statistics server 1101 sets the login area whose login number reaches the preset value as the target login area, and uses the target login area as the common login area of the account. .
  • the login statistics server 1101 determines each login area of the account based on the historical login behavior, and the login statistics server 1101 sets the login area in which the number of logins within the most recent preset duration reaches the preset value as the target login area, and uses the target login area as the user. Common login area.
  • the login statistics server 1101 determines each login area of the account according to the historical login behavior, and the login statistics server 1101 determines a first reference value of each login area according to the first weight and the number of logins in each login area, according to the second weight and The second reference value of each login area is determined at the login time of each login area, and the sum of the first reference value and the second reference value is used as a comprehensive reference value of the login area, and the login statistics server 1101 reaches the preset reference value.
  • the numeric login area serves as a common login area for the account.
  • the login policy can be sent to the login policy server 1102.
  • the login policy server 1102 can receive the login request sent by the user, and the login request can include the identifier information of the account that requests the login.
  • the login request may further include a user name, a password, and the like, which are not limited herein.
  • the login policy server 1102 does not directly reject the login request of the user after receiving the login request sent by the user, but The location information of the user is obtained according to the login request sent by the user.
  • the login policy server 1102 can obtain the location information of the user in multiple manners.
  • the login policy server 1102 obtains the location information of the user from the login request.
  • the login policy server 1102 parses the user's network address from the login address information, and the network address is an IP address or an LBS address;
  • the login policy server 1102 queries the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the login policy server 1102 obtains the location information of the user from the message forwarding network element that forwards the login request.
  • the login policy server 1102 obtains the network address of the user from the message forwarding network element that forwards the login request, and the network address is an IP address or an LBS address;
  • the login policy server 1102 queries the location information of the user corresponding to the network address of the user according to the correspondence between the network address and the location information.
  • the login policy server 1102 transmits the location information of the user to the login verification server 1103.
  • the login verification server 1103 determines whether the location information belongs to the common login area of the user, and transmits the determination result to the login policy server 1102.
  • the login verification server 1103 After the login verification server 1103 obtains the location information of the user according to the login request, it can determine whether the location information belongs to the common login area of the account, and sends the determination result to the login policy server 1102.
  • Policy server 1102 allows the user to log into the account.
  • the login statistics server 1101 can determine the common login area of the account according to the historical login behavior.
  • the login policy server 1102 receives the login request of the user, if the account is in a frozen state, the user can obtain the location of the user according to the login request. Information, if the location information belongs to a common login area, the user can be identified as a normal user, and the user is allowed to log in to the account, so Differentiating the login request of the user according to the location information when the user logs in can effectively avoid the impact of the freeze processing on the account used by the normal user.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separate, and the components displayed as the units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a computer device which may be a personal computer, a server, a storage medium including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (Random Access Memory) , RAM), disk or disc, etc.
  • a computer device which may be a personal computer, a server, a storage medium including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (Random Access Memory) , RAM), disk or disc, etc.
  • ROM read-only memory
  • RAM random access memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明实施例公开了一种安全认证方法、服务器以及安全认证系统,能够避免冻结处理对正常用户使用账号的影响。安全认证方法包括:接收用户的登录请求,所述登录请求中包含请求登录的账户的标识信息;若根据所述标识信息确定所述账户处于冻结状态,则根据所述登录请求获取所述用户的位置信息;判断所述位置信息是否满足预置的登录条件,若满足,则允许所述用户登录所述账户。本发明实施例还提供一种服务器以及安全认证系统。本发明实施例能够有效避免冻结处理对正常用户使用账号的影响。

Description

安全认证方法、 服务器以及安全认证系统
本申请要求于 2013 年 8 月 21 日提交中国专利局、 申请号为 201310367429.X,发明名称为"一种安全认证方法、 服务器以及安全认证系统" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及通信领域, 尤其涉及一种安全认证方法、服务器以及安全认证 系统。 背景技术 随着互联网技术的不断发展, 互联网的开放程度越来越高, 相应的, 木马 病毒等也开始横行, 互联网环境中用户的账号安全很难得到保证。
现有技术中的账号保护方法一般为:当检测到某个用户的账号不断发送色 情、 诈骗广告等恶意信息时, 则对会该账号进行冻结处理, 使得该账号在一段 时间内、 甚至永久无法登录。
但是,如果该账号是被他人盗取使用的, 那么直接对该账号进行冻结处理 则会影响正常用户对该账号的使用。 发明内容 本发明实施例提供了一种安全认证方法、 服务器以及安全认证系统。
本发明实施例提供的安全认证方法, 包括:
接收用户的账户登录请求,所述登录请求中包含请求登录的账户的标识信 息;
若根据所述标识信息确定所述账户处于冻结状态,则根据所述登录请求获 取所述用户的位置信息; 以及
判断所述位置信息是否满足预置的登录条件, 若满足, 则允许所述用户登 录所述账户。
可选地, 当所述登录请求中还包括登录地址信息时;
所述根据所述登录请求获取所述用户的位置信息包括:
从所述登录地址信息中解析出所述用户的网络地址,所述网络地址包括互 联网协议(IP )地址和基于位置的服务(LBS )地址; 以及
根据网络地址与位置信息之间的对应关系,查询所述用户的网络地址对应 的所述用户的位置信息。
可选地, 所述根据所述登录请求获取所述用户的位置信息包括: 从转发所述登录请求的消息转发网元获取所述用户的网络地址,所述网络 地址包括 IP地址和 LBS地址; 以及
根据网络地址与位置信息之间的对应关系,查询所述用户的网络地址对应 的所述用户的位置信息。
可选地, 所述方法还包括:
根据历史登录行为确定所述用户的常用登录区域。
可选地, 所述判断所述位置信息是否满足预置的登录条件包括: 判断所述位置信息是否属于所述常用登录区域, 若属于, 则确定满足所述 预置的登录条件, 若不属于, 则确定不满足所述预置的登录条件。
可选地, 所述根据历史登录行为确定所述账户的常用登录区域包括: 根据历史登录行为确定所述账户的各登录区域; 以及
将登录次数达到预置数值的登录区域设定为目标登录区域,并将所述目标 登录区域作为所述账户的常用登录区域。
可选地, 所述根据历史登录行为确定所述账户的常用登录区域包括: 根据历史登录行为确定所述账户的各登录区域;
将最近预置时长内登录次数达到预置数值的登录区域设定为目标登录区 域, 并将所述目标登录区域作为所述账户的常用登录区域。
可选地, 所述根据历史登录行为确定所述用户的常用登录区域包括: 根据历史登录行为确定所述账户的各登录区域;
根据第一权值以及在各登录区域的登录次数确定各登录区域的第一参考 值, 根据第二权值以及在各登录区域的登录时间确定各登录区域的第二参考 值, 并将第一参考值与第二参考值之和作为该登录区域的综合参考值; 以及 将综合参考值达到预置数值的登录区域作为所述账户的常用登录区域。 本发明实施例提供的安全认证方法, 包括:
登录统计服务器根据历史登录行为确定账户的常用登录区域,并将常用登 录区域信息发送至登录校验服务器;
所述登录策略服务器接收用户对所述账户的登录请求,所述登录请求中包 含所述账户的标识信息;
若所述登录策略服务器根据所述标识信息确定所述账户处于冻结状态,则 所述登录策略服务器根据所述登录请求获取所述用户的位置信息;
所述登录策略服务器将所述用户的位置信息发送至所述登录校验服务器; 所述登录校验服务器判断所述位置信息是否属于所述账户的常用登录区 域, 并向所述登录策略服务器发送判断结果; 以及
若所述位置信息属于所述账户的常用登录区域,则所述登录策略服务器允 许所述用户登录所述账户。
可选地, 当所述登录请求中还包括登录地址信息时;
所述登录策略服务器根据所述登录请求获取所述用户的位置信息包括: 所述登录策略服务器从所述登录地址信息中解析出所述用户的网络地址 , 所述网络地址包括互联网协议 ( IP )地址和基于位置的月良务(LBS )地址; 以 及
所述登录策略服务器根据网络地址与位置信息之间的对应关系,查询所述 用户的网络地址对应的所述用户的位置信息。
可选地,所述登录策略服务器根据所述登录请求获取所述用户的位置信息 包括:
所述登录策略服务器从转发所述登录请求的消息转发网元获取所述用户 的网络地址, 所述网络地址包括 IP地址和 LBS地址; 以及
所述登录策略服务器根据网络地址与位置信息之间的对应关系,查询所述 用户的网络地址对应的所述用户的位置信息。
可选地,所述登录统计服务器根据历史登录行为确定账户的常用登录区域 包括: 所述登录统计服务器根据历史登录行为确定所述账户的各登录区域; 所述登录统计服务器将登录次数达到预置数值的登录区域设定为目标登 录区域, 并将所述目标登录区域作为所述账户的常用登录区域;
或,
所述登录统计服务器根据历史登录行为确定所述账户的各登录区域;以及 所述登录统计服务器将最近预置时长内登录次数达到预置数值的登录区 域设定为目标登录区域, 并将所述目标登录区域作为所述账户的常用登录区 域;
或,
所述登录统计服务器根据历史登录行为确定所述账户的各登录区域; 所述登录统计服务器根据第一权值以及在各登录区域的登录次数确定各 登录区域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登 录区域的第二参考值,并将第一参考值与第二参考值之和作为该登录区域的综 合参考值; 以及
所述登录统计服务器将综合参考值达到预置数值的登录区域作为所述账 户的常用登录区域。
本发明实施例提供的服务器, 包括:
接收单元, 用于接收用户的登录请求, 所述登录请求中包含请求登录的账 户的标识信息; 所述登录请求获取所述用户的位置信息;
认证单元, 用于判断所述位置信息是否满足预置的登录条件, 若满足, 则 允许所述用户登录所述账户。
可选地, 当所述登录请求中还包括登录地址信息时;
所述获取单元包括:
第一获取模块, 用于从所述登录地址信息中解析出所述用户的网络地址, 所述网络地址包括互联网协议 ( IP )地址和基于位置的月良务(LBS )地址; 以 及
第一查询模块, 用于根据网络地址与位置信息之间的对应关系, 查询所述 用户的网络地址对应的所述用户的位置信息。
可选地, 所述获取单元包括:
第二获取模块,用于从转发所述登录请求的消息转发网元获取所述用户的 网络地址, 所述网络地址包括 IP地址和 LBS地址; 以及
第二查询模块, 用于根据网络地址与位置信息之间的对应关系, 查询所述 用户的网络地址对应的所述用户的位置信息。
可选地, 所述服务器还包括:
确定单元, 用于根据历史登录行为确定所述账户的常用登录区域。
可选地, 所述认证单元用于判断所述位置信息是否属于所述常用登录区 域, 若属于, 则确定满足所述预置的登录条件, 若不属于, 则确定不满足所述 预置的登录条件。
可选地, 所述确定单元包括:
第一确定模块, 用于根据历史登录行为确定所述账户的各登录区域; 以及 第三查询模块,用于将登录次数达到预置数值的登录区域设定为目标登录 区域, 并将所述目标登录区域作为所述账户的常用登录区域。
可选地, 所述确定单元包括:
第二确定模块, 用于根据历史登录行为确定所述账户的各登录区域; 以及 第四查询模块,将最近预置时长内登录次数达到预置数值的登录区域设定 为目标登录区域, 并将所述目标登录区域作为所述账户的常用登录区域。
可选地, 所述确定单元包括:
第三确定模块, 根据历史登录行为确定所述账户的各登录区域; 计算模块,用于根据第一权值以及在各登录区域的登录次数确定各登录区 域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登录区域 的第二参考值,并将第一参考值与第二参考值之和作为该登录区域的综合参考 值; 以及
第四确定模块,用于将综合参考值达到预置数值的登录区域作为所述账户 的常用登录区域。
本发明实施例提供的安全认证系统, 包括:
登录统计服务器、 登录策略服务器以及登录校臉服务器; 所述登录统计服务器用于根据历史登录行为确定账户的常用登录区域,并 将所述常用登录区域信息发送至所述登录校验服务器;
所述登录策略服务器用于接收用户对所述账号的登录请求,所述登录请求 中包含所述账户的标识信息, 若根据所述标识信息确定所述账户处于冻结状 态, 则才艮据所述登录请求获取所述用户的位置信息,将所述用户的位置信息发 送至所述登录校验服务器;
所述登录校臉服务器用于判断所述位置信息是否属于所述账号的常用登 录区域, 并向所述登录策略服务器发送判断结果;
若所述位置信息属于所述账号的常用登录区域,则所述登录策略服务器还 用于允许所述用户登录所述账户。
从以上技术方案可以看出, 本发明实施例具有以下优点:
本发明实施例中,服务器可以接收用户的登录请求, 该登录请求中包含请 求登录的账户的标识信息,当服务器根据该标识信息确定该账户处于冻结状态 时, 可以根据登录请求获取用户的位置信息, 并判断位置信息是否满足预置的 登录条件, 若满足, 则允许用户登录账户。 所以当某个账户处于冻结状态时, 服务器并不会拒绝所有用户对该账户的登录,而是根据用户登录时的位置信息 来区分处理, 当用户登录时的位置信息满足预置的登录条件时, 则允许该用户 登录该账户, 由于账户所有人(即正常用户)一般都会在比较固定的区域进行 登录,所以根据用户登录时的位置信息对用户的登录请求进行区分处理可以有 效的避免冻结处理对正常用户使用账号的影响。 附图说明 图 1为本发明实施例中安全认证方法一个实施例示意图;
图 2为本发明实施例中安全认证方法另一实施例示意图;
图 3为本发明实施例中安全认证方法另一实施例示意图;
图 4为本发明实施例中安全认证方法另一实施例示意图;
图 5为本发明实施例中安全认证方法另一实施例示意图;
图 6为本发明实施例中服务器一个实施例示意图;
图 7为本发明实施例中服务器另一实施例示意图; 图 8为本发明实施例中服务器另一实施例示意图;
图 9为本发明实施例中服务器另一实施例示意图;
图 10为本发明实施例中服务器另一实施例示意图; 以及
图 11为本发明实施例中安全认证系统一个实施例示意图。 具体实施方式 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。基于本发明中的实施例,本领域技术人员在没有做出创造性劳 动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明实施例提供了一种安全认证方法、服务器以及安全认证系统, 能够 避免冻结处理对正常用户使用账号的影响。
实施例一:
请参阅图 1 , 本发明实施例中安全认证方法一个实施例包括步骤 101至步 骤 104。
在步骤 101中,服务器通过所接收到的用户登录请求查询账号是否处于冻 结状态,如果该账号处于冻结状态, 则服务器根据该登录请求获取用户的位置 信息。
本实施例中, 当用户希望登录某一账户时, 可以向服务器发送登录请求, 则服务器可以接收到用户发送的登录请求,该登录请求中可以包含请求登录的 账户的标识信息。
可以理解的是, 除了包含请求登录的账户的标识信息(例如账户编号、 账 户名称等)之外, 该登录请求中还可以进一步包含用户名、 密码等信息, 具体 此处不做限定。
当服务器接收到用户发送的登录请求之后,可以根据该登录请求中的账户 的标识信息查询用户请求登录的账户的当前状态,若查询的结果显示该账户目 前处于冻结状态, 则说明该账户目前属于异常账户, 需要对该账户的登录情况 进行监控, 则服务器可以根据登录请求获取用户的位置信息。
本实施例中, 该位置信息可以为用户在登录时所处的具体地理位置,或者 是网络位置, 具体此处不做限定。
在步骤 102中, 服务器判断位置信息是否满足预置的登录条件, 若满足, 则执行步骤 103 , 若不满足, 则执行步骤 104。
在步骤 103中, 允许用户登录账户。
若该位置信息满足预置的登录条件,则说明当前的用户在某个特定的位置 登录该账户, 这一行为符合用户的历史登录习惯, 所以可以认定该用户为正常 用户, 则允许该用户登录账户。
在步骤 104中, 拒绝用户登录账户。
若该位置信息不满足预置的登录条件,则说明当前的用户的登录行为不符 合用户的历史登录习惯, 所以可以认定该用户为非法用户, 则不允许该用户登 录账户。
本实施例中,服务器可以接收用户的登录请求, 该登录请求中包含请求登 录的账户的标识信息, 当服务器根据该标识信息确定该账户处于冻结状态时, 可以根据登录请求获取用户的位置信息,并判断位置信息是否满足预置的登录 条件, 若满足, 则允许用户登录账户。 所以当某个账户处于冻结状态时, 服务 器并不会拒绝所有用户对该账户的登录,而是根据用户登录时的位置信息来区 分处理, 当用户登录时的位置信息满足预置的登录条件时, 则允许该用户登录 该账户, 由于账户所有人(即正常用户)一般都会在比较固定的区域进行登录, 所以根据用户登录时的位置信息对用户的登录请求进行区分处理可以有效的 避免冻结处理对正常用户使用账号的影响。
在上述实施例中,服务器根据登录请求获取用户的位置信息之后, 可以判 断该位置信息是否满足预置的登录条件。例如,服务器可以预先根据历史登录 行为确定用户的常用登录区域,然后再判断获取到的位置信息是否属于该常用 登录区域, 若属于, 则确定该位置信息满足预置的登录条件, 若不属于, 则确 定该位置信息不满足预置的登录条件,在实际的应用中,服务器可以通过多种 方式根据历史登录行为确定用户的常用登录区域, 下面分别详细进行描述。
实施例二:
本实施例中,服务器可以根据用户总共登录的次数确定用户的常用登录区 域, 请参阅图 2, 本发明实施例中安全认证方法另一实施例包括步骤 201至步 骤 207。
在步骤 201中, 服务器根据历史登录行为确定账户的登录区域。
账户每次被登录之后, 登录用户可以不定时的向服务器上报登录行为信 息, 该登录行为信息中包含有登录用户的账户、 登录的时间、 登录的 IP地址 等信息。
例如, 登录用户上报的登录行为信息可以如表 1所示:
表 1
Figure imgf000011_0001
本实施例中, 服务器可以收集到该账户被登录之后所上报的登录行为信 息, 所以能够从这些历史登录行为中确定该账户的多个登录区域。
需要说明的是, 由于登录行为信息中包含有 IP地址, 所以服务器可以根 据该 IP地址确定登录用户登录时实际所处的地理位置, 即登录区域。
例如, 服务器收集到的历史登录行为可以如表 2所示。
服务器通过表 2可以确定账户 "Tencentl l l',总共被登录 19次,登录区域分 别为"深圳"、 "广州"、 "北京"、 "上海"。
在步骤 202中,服务器将登录次数达到预置数值的登录区域设定为目标登 录区域, 并将目标登录区域作为该账户的常用登录区域。
需要说明的是,该预置数值可以为绝对数值(例如达到 10次或 20次等), 也可以为相对数值(例如在该账户的所有登录区域的总登录次数中占 30%以 上, 或 40%等), 本实施例中以绝对数值为例进行说明。
从表 2中可以看出, 在该账户的总共 19次登录中, 在深圳登录的次数有 8次, 在广州登录的次数有 9次, 在北京和上海登录的次数各有 1次。
若预置数值为 8次, 则可以将"深圳"和"广州"设定为目标登录区域; 若预 置数值为 9次,则可以将"广州"设定为目标登录区域。本实施例中,假设将 "深 圳"和"广州"设定为目标登录区域, 则可以确定用户的常用登录区域为"深圳" 和"广州"。
可以理解的是, 除了设置预置数值的方式之外,还可以采用其他方式确定 常用登录区域,例如在该账户的所有登录区域中选择登录次数最多的登录区域 等, 具体此处不做限定。
表 2
Figure imgf000012_0001
在步骤 203中, 服务器接收用户对该账户的登录请求。
当用户希望登录该账户时, 可以向服务器发送登录请求, 则服务器可以接 收到用户发送的登录请求, 该登录请求中可以包含请求登录的账户的标识信 息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 用户发送的登录请求可以如表 3所示:
表 3
Figure imgf000013_0001
在步骤 204中, 若服务器确定该账户处于冻结状态, 则服务器根据登录请 求获取该用户的位置信息。
本实施例中, 若账户 Tencentlll被冻结, 例如, 该账户由于发送恶意信息 而被冻结, 则服务器在接收到用户发送的登录请求之后, 不会直接拒绝用户的 登录请求, 而是会根据用户发送的登录请求获取用户的位置信息。
本实施例中, 服务器可以通过多种方式获取用户的位置信息, 例如: 一、 服务器可以从登录请求中获取该用户的位置信息。
若用户发送的登录请求中携带有登录地址信息,则服务器可以从该登录地 址信息中解析出用户的网络地址(即如表 3中所示的"登录 IP地址"), 并使用 该登录 IP地址作为用户的位置信息。
可以理解的是, 在实际应用中, 该位置信息除了可以是 IP地址之外, 还 可以是基于地址的服务(Location Based Service, LBS )地址, 或者是其他类 型能够用以表示位置信息的内容, 具体此处不做限定。
二、 服务器可以从转发该登录请求的消息转发网元获取该用户的位置信 若用户发送的登录请求中未携带有登录地址信息,则有可能用户使用了消 息转发网元(例如代理服务器)进行登录, 为了获取该用户准确的位置信息, 服务器可以从转发该登录请求的消息转发网元获取该用户的网络地址,该网络 地址可以为 IP地址, 或者是 LBS地址, 或者是其他类型能够用以表示位置信 息的内容, 具体此处不做限定。
服务器在获取到用户的网络地址之后,可以根据网络地址与位置信息之间 的对应关系, 查询到用户的位置信息。
如表 3所示, 若用户登录的 IP地址为 59.41.178.123 , 则服务器可以查询 到用户的位置信息为 "广州"。
在步骤 205中, 服务器判断位置信息是否属于常用登录区域, 若属于, 则 执行步骤 206, 若不属于, 则执行步骤 207。
在步骤 206中, 允许用户登录账户。
若该位置信息属于常用登录区域,则说明当前的用户在常用登录区域登录 该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以认定该用 户为正常用户, 则允许该用户登录账户。
本实施例中, 假设该账户的常用登录区域为"深圳"和"广州", 用户发送的 登录请求中的登录 IP地址为 59.41.178.123 , 其对应的位置信息为 "广州", 则 可以确定该位置信息属于用户的常用登录区域, 则说明该用户为正常用户, 则 服务器允许该用户登录账户 Tencentl 11。
在步骤 207中, 拒绝用户登录账户。
若该位置信息不属于常用登录区域,则说明当前的用户没有在常用登录区 域登录该账户,这一行为不符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为非法用户, 则可以拒绝该用户登录账户。
本实施例中, 账户的常用登录区域为"深圳"和"广州", 若用户发送的登录 请求中的登录 IP地址为 58.35.248.33 , 其对应的位置信息为 "上海,,, 则可以确 定该位置信息不属于该账户的常用登录区域, 则说明该用户为非法用户, 则服 务器可以拒绝该用户登录账户 Tencentl l l。
本实施例中,服务器可以根据历史登录行为确定账户的常用登录区域, 当 服务器接收到用户的登录请求时, 如果该账户处于冻结状态, 可以根据该登录 请求获取用户的位置信息, 若该位置信息属于常用登录区域, 则可以认定该用 户为正常用户, 则允许该用户登录账户, 所以根据用户登录时的位置信息对用 户的登录请求进行区分处理可以有效的避免冻结处理对正常用户使用账号的 影响。
上述实施例中描述了服务器根据用户总共登录的次数确定用户的常用登 录区域的方案, 下面介绍另外一种方案。
实施例三:
本实施例中,服务器可以根据近期内用户登录的情况确定用户的常用登录 区域, 请参阅图 3 , 本发明实施例中安全认证方法另一实施例包括步骤 301至 步骤 308。
在步骤 301中, 服务器根据历史登录行为确定账户的登录区域。
账户每次被登录之后,登录可以不定时的向服务器上报登录行为信息, 该 登录行为信息中包含有登录用户的账户、登录的时间、 登录的 IP地址等信息。
本实施例中,登录用户上报的登录行为信息可以如表 1所示, 此处不再赘 述。
本实施例中, 服务器可以收集到该账户被登录之后所上报的登录行为信 息, 所以能够从这些历史登录行为中确定该账户的多个登录区域。
需要说明的是, 由于登录行为信息中包含有 IP地址, 所以服务器可以根 据该 IP地址确定登录用户登录时实际所处的地理位置, 即登录区域。
本实施例中,服务器收集到的历史登录行为可以如表 2所示, 此处不再赘 述。
例如,服务器通过表 2可以确定账户 "Tencentl i r,总共被登录 19次, 登录 区域分别为"深圳"、 "广州"、 "北京"、 "上海"。
在步骤 302中,服务器将最近预置时长内登录次数达到预置数值的登录区 域设置为目标登录区域, 并将该目标登录区域作为该账户的常用登录区域。
其中, 最近预置时长可以才艮据实际情况确定, 例如可以为一周、 半个月、 一个月、 一季度、 半年等, 本实施例中以半个月为例进行说明。
需要说明的是, 本实施例中的预置数值可以为绝对数值(例如达到 10次 或 20次等),也可以为相对数值 (例如在最近预置时长各登录区域的总登录次 数中占 30%以上, 或 40%等), 本实施例中以绝对数值为例进行说明。
从表 2中可以看出, 截止 7月 31 日, 最近的半个月内账户 "Tencentl l l" 共被登录 12次, 具体如表 4所示。
从表 4 中可以看出, 在最近半个月内, 账户 "Tencentl l l" 共被登录 12 次, 在深圳登录的次数有 1次, 在广州登录的次数有 9次, 在北京和上海登录 的次数各有 1次。
若预置数值为 8次, 则可以将"广州"设定为目标登录区域, 本实施例中, 假设目标登录区域为 "广州 " , 则可以确定用户的常用登录区域为 "广州 "。 可以理解的是, 除了设置预置数值的方式之外,还可以采用其他方式确定 常用登录区域,例如在所有登录区域中选择登录次数最多的登录区域等,具体 此处不做限定。
表 4
Figure imgf000016_0001
在步骤 303中, 服务器接收用户对该账户的登录请求。
当用户希望登录该账户时,可以向服务器发送登录请求, 则服务器可以接 收到用户发送的登录请求, 该登录请求中可以包含请求登录的账户的标识信 可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 用户发送的登录请求可以如表 3所示, 此处不再赘述。 在步骤 304中, 若服务器确定该账户处于冻结状态, 则服务器根据登录请 求获取该用户的位置信息。
本实施例中, 若账户 Tencentl l l被冻结, 例如, 该账户由于发送恶意信息 而被冻结, 则服务器在接收到用户发送的登录请求之后, 不会直接拒绝用户的 登录请求, 而是会根据用户发送的登录请求获取用户的位置信息。
本实施例中,服务器可以通过多种方式获取用户的位置信息,具体方式与 图 2所示实施例中的步骤 204所描述的内容一致, 此处不再赘述。
在步骤 305中, 服务器判断位置信息是否属于常用登录区域, 若属于, 则 执行步骤 306, 若不属于, 则执行步骤 307。
在步骤 306中, 允许用户登录账户。
若该位置信息属于常用登录区域,则说明当前的用户在常用登录区域登录 该账户,这一行为符合用户的历史登录习惯,所以可以认定该用户为正常用户, 则允许该用户登录账户。
本实施例中, 假设该账户的常用登录区域为"广州", 用户发送的登录请求 中的登录 IP地址为 59.41.178.123 , 其对应的位置信息为 "广州", 则可以确定 该位置信息属于用户的常用登录区域, 则说明该用户为正常用户, 则服务器允 许该用户登录账户 Tencentl l l。
在步骤 307中拒绝用户登录账户。
若该位置信息不属于常用登录区域,则说明当前的用户没有在常用登录区 域登录该账户,这一行为不符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为非法用户, 则可以拒绝该用户登录账户。
本实施例中, 账户的常用登录区域为"广州", 若用户发送的登录请求中的 登录 IP地址为 58.35.248.33 , 其对应的位置信息为 "上海", 则可以确定该位置 信息不属于该账户的常用登录区域, 则说明该用户为非法用户, 则服务器可以 拒绝该用户登录账户 Tencentl 11。
本实施例中,服务器可以根据历史登录行为确定账户的常用登录区域, 当 服务器接收到用户的登录请求时, 如果该账户处于冻结状态, 可以根据该登录 请求获取用户的位置信息, 若该位置信息属于常用登录区域, 则可以认定该用 户为正常用户, 则允许该用户登录账户, 所以根据用户登录时的位置信息对用 户的登录请求进行区分处理可以有效的避免冻结处理对正常用户使用账号的 影响。
上述实施例中描述了服务器根据用户最近预置登录的次数确定用户的常 用登录区域的方案, 下面介绍另外一种方案。 实施例四:
本实施例中,服务器可以根据登录时间和登录次数综合确定用户的常用登 录区域, 请参阅图 4, 本发明实施例中安全认证方法另一实施例包括步骤 401 至步骤 407。
在步骤 401中, 服务器根据历史登录行为确定账户的登录区域。
账户每次被登录之后, 登录用户可以不定时的向服务器上报登录行为信 息, 该登录行为信息中包含有登录用户的账户、 登录的时间、 登录的 IP地址 等信息。
本实施例中, 用户上报的登录行为信息可以如表 1所示, 此处不再赘述。 本实施例中, 服务器可以收集到该账户被登录之后所上报的登录行为信 息, 所以能够从这些历史登录行为中确定该账户的多个登录区域。
需要说明的是, 由于登录行为信息中包含有 IP地址, 所以服务器可以根 据该 IP地址确定登录用户登录时实际所处的地理位置, 即登录区域。
例如, 服务器收集到的历史登录行为可以如表 5所示。
服务器通过表 5可以确定登录账户" Tencentl l l"总共被登录 17次,登录区 域分别为"深圳 ( 8次),,、 "广州 ( 7次),,、 "北京( 1次),,、 "上海( 1次) "。
在本实施例中,服务器根据第一权值以及在各登录区域的登录次数确定各 登录区域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登 录区域的第二参考值 ,并将第一参考值与第二参考值之和作为该登录区域的综 合参考值。
本实施例中, 服务器可以综合考虑各登录区域的登录次数以及登录时间, 并按照不同的权值计算得出综合参考值。
第一参考值的计算方式可以为: 对于某登录区域而言,每一次登录可以计 为 10点参考值, 第一权值为 0.9, 则第一参考值为: 0.9* (总登录次数 * 10 )。
第二参考值的计算方式可以为: 对于某登录区域而言, 第二权值为 0.3 , 该登录区域内的每一次登录的登录时间减去参考时间后的数值相加再乘以第 二权值即为该登录区域的第二权值, 为便于理解, 下面以一个具体实例进行说 明。 假设参考时间为 2013年 7月 1 日, 则各区域的综合参考值如表 6所示。
由表 6可以看出, 经过计算, "深圳,,的综合参考值为 78.6, "北京,,的综合 参考值为 11.8, "上海 "的综合参考值为 12, "广州 "的综合参考值为 81.8。 需要说明的是, 上面只是举出了一个具体的计算例子,在实际应用中还可 以有更多种的计算方式, 只要使得"综合参考值与登录次数成正比, 且越在近 期登录, 综合参考值越高"即可, 具体 式此处不做限定。
Figure imgf000019_0001
Figure imgf000019_0002
在步骤 402中,服务器将综合参考值达到预置数值的登录区域设定为目标 登录区域, 并将目标登录区域作为该账户的常用登录区域。
本实施例中,可以将综合参考值最高的登录区域作为该账户的常用登录区 域, 则该账户的常用登录区域为 "广州,,。
在步骤 403中, 服务器接收用户的登录请求。 当用户希望登录该账户时,可以向服务器发送登录请求, 则服务器可以接 收到用户发送的登录请求, 该登录请求中可以包含请求登录的账户的标识信 息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 用户发送的登录请求可以如表 3所示, 此处不再赘述。
表 6
Figure imgf000020_0001
在步骤 404中, 若服务器确定该账户处于冻结状态, 则服务器根据登录请 求获取该用户的位置信息。
本实施例中, 若账户 Tencentl l l被冻结, 例如, 该账户由于发送恶意信息 而被冻结, 则服务器在接收到用户发送的登录请求之后, 不会直接拒绝用户的 登录请求, 而是会根据用户发送的登录请求获取用户的位置信息。
本实施例中,服务器可以通过多种方式获取用户的位置信息,具体方式与 图 2所示实施例中的步骤 204所描述的内容一致, 此处不再赘述。
在步骤 405中, 服务器判断位置信息是否属于常用登录区域, 若属于, 则 执行步骤 406, 若不属于, 则执行步骤 407。
在步骤 406中, 允许用户登录账户。
若该位置信息属于常用登录区域,则说明当前的用户在常用登录区域登录 该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以认定该用 户为正常用户, 则允许该用户登录账户。
本实施例中, 假设该账户的常用登录区域为"广州", 用户发送的登录请求 中的登录 IP地址为 59.41.178.123 , 其对应的位置信息为 "广州", 则可以确定 该位置信息属于用户的常用登录区域, 则说明该用户为正常用户, 则服务器允 许该用户登录账户 Tencentl l l。
在步骤 407中, 拒绝用户登录账户。
若该位置信息不属于常用登录区域,则说明当前的用户没有在常用登录区 域登录该账户,这一行为不符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为非法用户, 则可以拒绝该用户登录账户。
本实施例中, 账户的常用登录区域为"广州", 若用户发送的登录请求中的 登录 IP地址为 58.35.248.33 , 其对应的位置信息为 "上海", 则可以确定该位置 信息不属于该账户的常用登录区域, 则说明该用户为非法用户, 则服务器可以 拒绝该用户登录账户 Tencentl 11。
本实施例中,服务器可以根据历史登录行为确定账户的常用登录区域, 当 服务器接收到用户的登录请求时, 如果该账户处于冻结状态, 可以根据该登录 请求获取用户的位置信息, 若该位置信息属于常用登录区域, 则可以认定该用 户为正常用户, 则允许该用户登录账户, 所以根据用户登录时的位置信息对用 户的登录请求进行区分处理可以有效的避免冻结处理对正常用户使用账号的 影响。
在实际的应用中, 上述实施例中描述的 "服务器,,可以为一个具体的服务 器, 也可以为若干个服务器组成的服务器集群。
为便于理解,下面以一个具体实施例对若干个服务器组成的服务器集群的 方案进行描述。
实施例五:
请参阅图 5, 本发明实施例中安全认证方法另一实施例包括步骤 501至步 骤 507。
在步骤 501中, 登录统计服务器根据历史登录行为确定账户的登录区域。 本实施例中, 账户每次被登录之后,登录用户可以不定时的向登录统计服 务器上报登录行为信息, 该登录行为信息中包含有登录用户的账户、登录的时 间、 登录的 IP地址等信息。
在步骤 502中,登录统计服务器将常用登录区域信息发送至登录校验服务 器。
本实施例中,登录统计服务器可以收集到该账户的登录用户在各次登录之 后上报的登录行为信息,所以能够从这些历史登录行为中确定该账户的各登录 区域。
例如, 登录统计服务器可以通过以下方法确定账户的登录区域。
一、 根据总登录次数确定
例如,登录统计服务器根据历史登录行为确定账户的各登录区域,登录统 计服务器将登录次数达到预置数值的登录区域设定为目标登录区域,并将目标 登录区域作为该账户的常用登录区域。
二、 根据近期登录次数确定
例如,登录统计服务器根据历史登录行为确定账户的各登录区域,登录统 计服务器将最近预置时长内登录次数达到预置数值的登录区域设定为目标登 录区域, 并将目标登录区域作为用户的常用登录区域。
三、 根据登录次数和时间综合确定
例如,登录统计服务器根据历史登录行为确定账户的各登录区域,登录统 计服务器根据第一权值以及在各登录区域的登录次数确定各登录区域的第一 参考值,根据第二权值以及在各登录区域的登录时间确定各登录区域的第二参 考值, 并将第一参考值与第二参考值之和作为该登录区域的综合参考值,登录 统计服务器将综合参考值达到预置数值的登录区域作为账户的常用登录区域。
需要说明的是,上述三种确定方式的具体过程在图 2至图 4所示的实施例 中已经详细描述过, 此处不再赞述。
在步骤 503中, 登录策略服务器接收用户的登录请求。
当用户希望登录该账户时,可以向登录策略服务器发送登录请求, 则登录 策略服务器可以接收到用户发送的登录请求,该登录请求中可以包含请求登录 的账户的标识信息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
在步骤 504中, 若登录策略服务器确定账户处于冻结状态, 则登录策略服 务器根据登录请求获取该用户的位置信息。
本实施例中, 若账户被冻结, 例如, 该账户可能由于发送恶意信息而被冻 结, 则登录策略服务器在接收到用户发送的登录请求之后, 不会直接拒绝用户 的登录请求, 而是会根据用户发送的登录请求获取用户的位置信息。
本实施例中,登录策略服务器可以通过多种方式获取用户的位置信息, 具 体可以有如下一些方式。
一、 服务器可以从登录请求中获取该用户的位置信息。
例如, 当登录请求中还包括登录地址信息时,登录策略服务器可以从登录 地址信息中解析出用户的网络地址,该网络地址为 IP地址,或者为 LBS地址; 登录策略服务器根据网络地址与位置信息之间的对应关系,查询该用户的 网络地址对应的该用户的位置信息。
二、 服务器可以从转发该登录请求的消息转发网元获取该用户的位置信 息。
例如,登录策略服务器从转发登录请求的消息转发网元获取该用户的网络 地址, 该网络地址为 IP地址, 或者为 LBS地址;
登录策略服务器根据网络地址与位置信息之间的对应关系,查询该用户的 网络地址对应的该用户的位置信息。 需要说明的是,具体获取用户的位置信息的方式与图 2所示实施例中的步 骤 204所描述的内容一致, 此处不再赘述。
在步骤 505 中, 登录策略服务器将用户的位置信息发送至登录校验服务 器。
在步骤 506中,登录校验服务器判断位置信息是否属于该账户的常用登录 区域, 并向登录策略服务器发送判断结果。
登录校验服务器根据登录请求获取用户的位置信息之后,可以判断该位置 信息是否属于该账户的常用登录区域, 并将判断结果发送给登录策略服务器。
在步骤 507中, 若判断结果为是, 则登录策略服务器允许该用户登录该账 户。
若该位置信息属于常用登录区域,则说明当前的用户在该账户的常用登录 区域登录该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为正常用户, 则登录策略服务器允许该用户登录账户。
本实施例中,登录统计服务器可以根据历史登录行为确定账户的常用登录 区域,当登录策略服务器接收到用户的登录请求时,如果该账户处于冻结状态, 可以根据该登录请求获取用户的位置信息, 若该位置信息属于常用登录区域, 则可以认定该用户为正常用户, 则允许该用户登录账户, 所以根据用户登录时 的位置信息对用户的登录请求进行区分处理可以有效的避免冻结处理对正常 用户使用账号的影响。
上面对本发明实施例中的安全认证方法进行了描述,本发明实施例还提供 了一种服务器。
实施例六:
请参阅图 6,本发明实施例中服务器可以包括接收单元 601、获取单元 602 和认证单元 603。
接收单元 601 , 用于接收用户的登录请求, 该登录请求中包含请求登录的 账户的标识信息。
获取单元 602, 用于通过接收单元 601接收到的用户登录请求查询所要登 录的账户是否处于冻结状态,如果该账户处于冻结状态, 则根据该登录请求获 取该用户的位置信息。 认证单元 603, 用于判断该位置信息是否满足预置的登录条件, 若满足, 则允许该用户登录该账户。
本实施例中,接收单元 601可以接收用户的登录请求,该登录请求中包含 请求登录的账户的标识信息,当获取单元 602根据该标识信息确定该账户处于 冻结状态时, 可以根据登录请求获取用户的位置信息, 并由认证单元 603判断 位置信息是否满足预置的登录条件, 若满足, 则允许用户登录账户, 所以当某 个账户处于冻结状态时,服务器并不会拒绝所有用户对该账户的登录, 而是根 据用户登录时的位置信息来区分处理,当用户登录时的位置信息满足预置的登 录条件时, 则允许该用户登录该账户, 由于账户所有人(即正常用户)一般都 会在比较固定的区域进行登录,所以根据用户登录时的位置信息对用户的登录 请求进行区分处理可以有效的避免冻结处理对正常用户使用账号的影响。
在上述实施例中, 获取单元 602根据登录请求获取用户的位置信息之后, 认证单元 603可以判断该位置信息是否满足预置的登录条件。例如,服务器预 先可以根据历史登录行为确定账户的常用登录区域,然后再判断获取到的位置 信息是否属于该账户的常用登录区域, 若属于, 则确定满足预置的登录条件, 若不属于, 则确定不满足预置的登录条件, 在实际的应用中, 服务器可以通过 多种方式根据历史登录行为确定用户的常用登录区域, 下面分别详细进行描 述。
实施例七:
本实施例中,服务器可以根据该账户总共被登录的次数确定账户的常用登 录区域, 请参阅图 7, 本发明实施例中服务器可以包括接收单元 701、 获取单 元 702和认证单元 703。
接收单元 701 , 用于接收用户的登录请求, 该登录请求中包含请求登录的 账户的标识信息。
获取单元 702, 用于通过接收单元 701接收到的用户登录请求查询所要登 录的账户是否处于冻结状态,如果该账户处于冻结状态, 则根据该登录请求获 取该用户的位置信息。
认证单元 703 , 用于判断该位置信息是否满足预置的登录条件, 若满足, 则允许该用户登录该账户。 本实施例中的服务器还可以进一步包括:
确定单元 704, 用于根据历史登录行为确定该账户的常用登录区域。
当确定单元 704用于确定账户的常用登录区域时,认证单元 703可以用于 判断该位置信息是否属于该常用登录区域, 若属于, 则确定满足该预置的登录 条件, 若不属于, 则确定不满足该预置的登录条件。
本实施例中的确定单元 704可以进一步包括:
第一确定模块 7041, 用于根据历史登录行为确定该账户的各登录区域; 以及
第三查询模块 7042, 用于将登录次数达到预置数值的登录区域设定为目 标登录区域, 并将该目标登录区域作为该账户的常用登录区域。
当登录请求中还包含登录地址信息时,本实施例中的获取单元 702可以包 括:
第一获取模块 7021, 用于从该登录地址信息中解析出该用户的网络地址, 该网络地址为 IP地址, 或者为 LBS地址; 以及
第一查询模块 7022, 用于根据网络地址与位置信息之间的对应关系, 查 询该用户的网络地址对应的该用户的位置信息。
或者, 本实施例中的获取单元 702可以包括:
第二获取模块 7023 , 用于从转发该登录请求的消息转发网元获取该用户 的网络地址, 该网络地址为 IP地址, 或者为 LBS地址; 以及
第二查询模块 7024, 用于根据网络地址与位置信息之间的对应关系, 查 询该用户的网络地址对应的该用户的位置信息。
为便于理解,下面以一个具体应用场景对本实施例服务器中的各单元之间 的交互进行描述。
账户每次被登录之后, 登录用户可以不定时的向服务器上报登录行为信 息, 该登录行为信息中包含有登录用户的账户、 登录的时间、 登录的 IP地址 等信息。
本实施例中, 服务器可以收集到该账户被登录之后所上报的登录行为信 息, 所以确定单元 704中的第一确定模块 7041能够从这些历史登录行为中确 定该账户的各登录区域。 需要说明的是, 由于登录用户上报的登录行为信息中包含有登录 IP地址, 所以服务器可以根据该 IP地址确定登录用户登录时实际所处的地理位置, 即 登录区域。
当确定单元 704中的第一确定模块 7041根据历史登录行为确定该账户的 各登录区域之后, 确定单元 704中的第三查询模块 7042可以将登录次数达到 预置数值的登录区域设定为目标登录区域,并将目标登录区域作为该账户的常 用登录区域。
可以理解的是, 除了设置预置数值的方式之外,还可以采用其他方式确定 常用登录区域,例如在各登录区域中选择登录次数最多的登录区域等,具体此 处不做限定。
当用户希望登录该账户时, 可以向服务器发送登录请求, 则接收单元 701 可以接收到用户发送的登录请求,该登录请求中可以包含请求登录的账户的标 识信息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 获取单元 702可以通过多种方式获取用户的位置信息。
一、 获取单元 702可以从登录请求中获取该用户的位置信息。
若用户发送的登录请求中携带有登录地址信息,则获取单元 702中的第一 获取模块 7021从该登录地址信息中解析出用户的网络地址, 该网络地址为 IP 地址, 或者为 LBS地址, 或者是其他类型能够用以表示位置信息的内容, 具 体此处不做限定。
获取单元 702中的第一查询模块 7022根据网络地址与位置信息之间的对 应关系, 查询该用户的网络地址对应的该用户的位置信息。
二、获取单元 702从转发该登录请求的消息转发网元获取该用户的位置信 息。
若用户发送的登录请求中未携带有登录地址信息, 则有可能用户使用了消 息转发网元(例如代理服务器)进行登录, 为了获取该用户准确的位置信息, 获取单元 702中的第二获取模块 7023可以从转发该登录请求的消息转发网元 获取该用户的网络地址, 该网络地址为 IP地址, 或者为 LBS地址, 或者是其 他类型能够用以表示位置信息的内容, 具体此处不做限定。
获取单元 702中的第二查询模块 7024根据网络地址与位置信息之间的对 应关系, 查询该用户的网络地址对应的该用户的位置信息。
获取单元 702根据登录请求获取用户的位置信息之后,认证单元 703可以 判断该位置信息是否属于常用登录区域。
若该位置信息属于常用登录区域,则说明当前的用户在常用登录区域登录 该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以认定该用 户为正常用户, 则允许该用户登录账户。
若该位置信息不属于常用登录区域,则说明当前的用户没有在常用登录区 域登录该账户,这一行为不符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为非法用户, 则可以拒绝该用户登录账户。
需要说明的是, 本实施例中服务器中各单元之间的详细交互过程如图 2 所示实施例中描述的内容, 具体此处不再赘述。
本实施例中,确定单元 704可以根据历史登录行为确定该账户的常用登录 区域, 当接收单元 701接收到用户的登录请求时, 如果该账户处于冻结状态, 获取单元 702可以根据该登录请求获取用户的位置信息,若该位置信息属于常 用登录区域, 则认证单元 703可以认定该用户为正常用户, 则允许该用户登录 账户,所以根据用户登录时的位置信息对用户的登录请求进行区分处理可以有 效的避免冻结处理对正常用户使用账号的影响。
实施例八:
本实施例中,服务器可以根据账户用户总共被登录的次数确定该账户的常 用登录区域, 请参阅图 8 , 本发明实施例中服务器另一实施例包括接收单元 801、 获取单元 802和认证单元 803。
接收单元 801 , 用于接收用户的登录请求, 该登录请求中包含请求登录的 账户的标识信息;
获取单元 802, 用于通过接收单元 801接收到的用户登录请求查询所要登 录的账户是否处于冻结状态,如果该账户处于冻结状态, 则根据该登录请求获 取该用户的位置信息。
认证单元 803, 用于判断该位置信息是否满足预置的登录条件, 若满足, 则允许该用户登录该账户。
本实施例中的服务器还可以进一步包括:
确定单元 804, 用于根据历史登录行为确定该账户的常用登录区域。
当确定单元 804用于确定账户的常用登录区域时,该认证单元 803可以用 于判断该位置信息是否属于该常用登录区域, 若属于, 则确定满足该预置的登 录条件, 若不属于, 则确定不满足该预置的登录条件。
本实施例中的确定单元 804可以进一步包括:
第二确定模块 8041 , 用于根据历史登录行为确定该账户的各登录区域; 以及
第四查询模块 8042, 用户将最近预置时长内登录次数达到预置数值的登 录区域设定为目标登录区域, 并将该目标登录区域作为该账户的常用登录区 域。
当登录请求中还包括登录地址信息时,本实施例中的获取单元 802可以包 括:
第一获取模块 8021 , 用于从该登录地址信息中解析出该用户的网络地址 , 该网络地址为 IP地址, 或者 LBS地址; 以及
第一查询模块 8022, 用于根据网络地址与位置信息之间的对应关系, 查 询该用户的网络地址对应的该用户的位置信息。
或者, 本实施例中的获取单元 802可以包括:
第二获取模块 8023 , 用于从转发该登录请求的消息转发网元获取该用户 的网络地址, 该网络地址为 IP地址, 或者为 LBS地址; 以及
第二查询模块 8024, 用于根据网络地址与位置信息之间的对应关系, 查 询该用户的网络地址对应的该用户的位置信息。
为便于理解,下面以一个具体应用场景对本实施例服务器中的各单元之间 的交互进行描述。
账户每次被登录之后, 登录用户可以不定时的向服务器上报登录行为信 息, 该登录行为信息中包含有登录用户的账户、 登录的时间、 登录的 IP地址 等信息。
本实施例中, 服务器可以收集到该账户被登录之后所上报的登录行为信 息, 所以确定单元 804中的第二确定模块 8041能够从这些历史登录行为中确 定该账户的各登录区域。
需要说明的是, 由于用户上报的登录行为信息中包含有登录 IP地址, 所 以服务器可以根据该 IP地址确定登录用户登录时实际所处的地理位置, 即登 录区域。
当确定单元 804中的第二确定模块 8041根据历史登录行为确定该账户的 各登录区域之后, 确定单元 804中的第四查询模块 8042可以将最近预置时长 内登录次数达到预置数值的登录区域设定为目标登录区域,并将该目标登录区 域作为该账户的常用登录区域。
本实施例中的最近预置时长可以^^据实际情况确定, 例如可以为一周、半 个月、 一个月、 一季度、 半年等, 具体此处不做限定。
需要说明的是, 本实施例中的预置数值可以为绝对数值(例如达到 10次 或 20次等),也可以为相对数值 (例如在最近预置时长各登录区域的总登录次 数中占 30%以上, 或 40%等), 具体此处不做限定。
可以理解的是, 除了设置预置数值的方式之外,还可以采用其他方式确定 常用登录区域,例如在各登录区域中选择登录次数最多的登录区域等, 具体此 处不做限定。
当用户希望登录该账户时, 可以向服务器发送登录请求, 则接收单元 801 可以接收到用户发送的登录请求,该登录请求中可以包含请求登录的账户的标 识信息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 获取单元 802可以通过多种方式获取用户的位置信息。
一、 获取单元 802直接从登录请求中获取该用户的位置信息。
若用户发送的登录请求中携带有登录地址信息,则获取单元 802中的第一 获取模块 8021从该登录地址信息中解析出用户的网络地址, 该网络地址为 IP 地址, 或者为 LBS地址, 或者是其他类型能够用以表示位置信息的内容, 具 体此处不做限定。
获取单元 802中的第一查询模块 8022根据网络地址与位置信息之间的对 应关系, 查询该用户的网络地址对应的该用户的位置信息。
二、获取单元 802从转发该登录请求的消息转发网元获取该用户的位置信 息。
若用户发送的登录请求中未携带有登录地址信息,则有可能用户使用了消 息转发网元(例如代理服务器)进行登录, 为了获取该用户准确的位置信息, 获取单元 802中的第二获取模块 8023可以从转发该登录请求的消息转发网元 获取该用户的网络地址, 该网络地址为 IP地址, 或者为 LBS地址, 或者是其 他类型能够用以表示位置信息的内容, 具体此处不做限定。
获取单元 802中的第二查询模块 8024根据网络地址与位置信息之间的对 应关系, 查询该用户的网络地址对应的该用户的位置信息。
获取单元 802根据登录请求获取用户的位置信息之后,认证单元 803可以 判断该位置信息是否属于常用登录区域。
若该位置信息属于常用登录区域,则说明当前的用户在常用登录区域登录 该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以认定该用 户为正常用户, 则允许该用户登录账户。
若该位置信息不属于常用登录区域,则说明当前的用户没有在常用登录区 域登录该账户,这一行为不符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为非法用户, 则可以拒绝该用户登录账户。
需要说明的是, 本实施例中服务器中各单元之间的详细交互过程如图 3 所示实施例中描述的内容, 具体此处不再赘述。
本实施例中,确定单元 804可以根据历史登录行为确定该账户的常用登录 区域, 当接收单元 801接收到用户的登录请求时, 如果该账户处于冻结状态, 获取单元 802可以根据该登录请求获取用户的位置信息,若该位置信息属于常 用登录区域, 则认证单元 803可以认定该用户为正常用户, 则允许该用户登录 账户,所以根据用户登录时的位置信息对用户的登录请求进行区分处理可以有 效的避免冻结处理对正常用户使用账号的影响。
实施例九:
本实施例中,服务器可以根据账户总共被登录的次数以及登录时间综合确 定该账户的常用登录区域, 请参阅图 9, 本发明实施例中服务器另一实施例包 括接收单元 901、 获取单元 902和认证单元 903。
接收单元 901 , 用于接收用户的登录请求, 该登录请求中包含请求登录的 账户的标识信息。
获取单元 902, 用于通过接收单元 901接收到的用户登录请求查询所要登 录的账户是否处于冻结状态,如果该账户处于冻结状态, 则根据该登录请求获 取该用户的位置信息。
认证单元 903, 用于判断该位置信息是否满足预置的登录条件, 若满足, 则允许该用户登录该账户。
本实施例中的服务器还可以进一步包括:
确定单元 904, 用于根据历史登录行为确定该账户的常用登录区域。
当确定单元 904用于确定账户的常用登录区域时,该认证单元 903可以用 于判断该位置信息是否属于该常用登录区域, 若属于, 则确定满足该预置的登 录条件, 若不属于, 则确定不满足该预置的登录条件。
本实施例中的确定单元 904可以进一步包括:
第三确定模块 9041 , 用户根据历史登录行为确定该账户的各登录区域; 计算模块 9042, 用于根据第一权值以及在各登录区域的登录次数确定各 登录区域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登 录区域的第二参考值 ,并将第一参考值与第二参考值之和作为该登录区域的综 合参考值; 以及
第四确定模块 9043 , 用于将综合参考值达到预置数值的登录区域作为该 账户的常用登录区域。
当登录请求中还包括登录地址信息时,本实施例中的获取单元 902可以包 括:
第一获取模块 9021 , 用于从该登录地址信息中解析出该用户的网络地址, 该网络地址为 IP地址, 或者为 LBS地址; 以及
第一查询模块 9022, 用于根据网络地址与位置信息之间的对应关系, 查 询该用户的网络地址对应的该用户的位置信息。
或者, 本实施例中的获取单元 902可以包括:
第二获取模块 9023, 用于从转发该登录请求的消息转发网元获取该用户 的网络地址, 该网络地址为 IP地址, 或者为 LBS地址; 以及
第二查询模块 9024, 用于根据网络地址与位置信息之间的对应关系, 查 询该用户的网络地址对应的该用户的位置信息。
为便于理解,下面以一个具体应用场景对本实施例服务器中的各单元之间 的交互进行描述。
账户每次被登录之后, 登录用户可以不定时的向服务器上报登录行为信 息, 该登录行为信息中包含有登录用户的账户、 登录的时间、 登录的 IP地址 等信息。
本实施例中, 服务器可以收集到该账户被登录之后所上报的登录行为信 息, 所以确定单元 904中的第三确定模块 9041能够从这些历史登录行为中确 定该账户的各登录区域。
需要说明的是, 由于用户上报的登录行为信息中包含有登录 IP地址, 所 以服务器可以根据该 IP地址确定登录用户登录时实际所处的地理位置, 即登 录区 i或。
确定单元 904中的计算模块 9042可以根据第一权值以及在各登录区域的 登录次数确定各登录区域的第一参考值,根据第二权值以及在各登录区域的登 录时间确定各登录区域的第二参考值,并将第一参考值与第二参考值之和作为 该登录区域的综合参考值。
本实施例中,确定单元 904可以综合考虑各登录区域的登录次数以及登录 时间, 并按照不同的权值计算得出综合参考值。
第一参考值的计算方式可以为: 对于某登录区域而言,每一次登录可以计 为 10点参考值, 第一权值为 0.9, 则第一参考值为: 0.9* (总登录次数 * 10 )。
第二参考值的计算方式可以为: 对于某登录区域而言, 第二权值为 0.3 , 该登录区域内的每一次登录的登录时间减去参考时间后的数值相加再乘以第 二权值即为该登录区域的第二权值, 各区域的综合参考值可以如上述表 6 所 示, 具体此处不再赘述。
需要说明的是, 上面只是举出了一个具体的计算例子,在实际应用中还可 以有更多种的计算方式, 只要使得"综合参考值与登录次数成正比, 且越在近 期登录, 综合参考值越高"即可, 具体实现方式此处不做限定。 确定单元 904中的计算模块 9042计算得到各登录区域的综合参考值之后 , 确定单元 904中的第四确定模块 9043可以将综合参考值达到预置数值的登录 区域作为该账户的常用登录区域。
当用户希望登录该账户时, 可以向服务器发送登录请求, 则接收单元 901 可以接收到用户发送的登录请求,该登录请求中可以包含请求登录的账户的标 识信息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 获取单元 902可以通过多种方式获取用户的位置信息。
一、 获取单元 902从登录请求中获取该用户的位置信息。
若用户发送的登录请求中携带有登录地址信息,则获取单元 902中的第一 获取模块 9021从该登录地址信息中解析出用户的网络地址, 该网络地址为 IP 地址, 或者为 LBS地址, 或者是其他类型能够用以表示位置信息的内容, 具 体此处不做限定。
获取单元 902中的第一查询模块 9022根据网络地址与位置信息之间的对 应关系, 查询该用户的网络地址对应的该用户的位置信息。
二、获取单元 902从转发该登录请求的消息转发网元获取该用户的位置信 若用户发送的登录请求中未携带有登录地址信息,则有可能用户使用了消 息转发网元(例如代理服务器)进行登录, 为了获取该用户准确的位置信息, 获取单元 902中的第二获取模块 9023可以从转发该登录请求的消息转发网元 获取该用户的网络地址, 该网络地址为 IP地址, 或者为 LBS地址, 或者是其 他类型能够用以表示位置信息的内容, 具体此处不做限定。
获取单元 902中的第二查询模块 9024根据网络地址与位置信息之间的对 应关系, 查询该用户的网络地址对应的该用户的位置信息。
获取单元 902根据登录请求获取用户的位置信息之后 ,认证单元 903可以 判断该位置信息是否属于常用登录区域。
若该位置信息属于常用登录区域,则说明当前的用户在常用登录区域登录 该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以认定该用 户为正常用户, 则允许该用户登录账户。
若该位置信息不属于常用登录区域,则说明当前的用户没有在常用登录区 域登录该账户,这一行为不符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为非法用户, 则可以拒绝该用户登录账户。
需要说明的是, 本实施例中服务器中各单元之间的详细交互过程如图 4 所示实施例中描述的内容, 具体此处不再赘述。
本实施例中,确定单元 904可以根据历史登录行为确定该账户的常用登录 区域, 当接收单元 901接收到用户的登录请求时, 如果该账户处于冻结状态, 获取单元 902可以根据该登录请求获取用户的位置信息,若该位置信息属于常 用登录区域, 则认证单元 903可以认定该用户为正常用户, 则允许该用户登录 账户,所以根据用户登录时的位置信息对用户的登录请求进行区分处理可以有 效的避免冻结处理对正常用户使用账号的影响。
上面从服务器的各功能结构的角度对本发明实施例中的服务器进行了描 实施例十:
本发明实施例还提供一种服务器,其中可以集成有本发明实施例中服务器 所实现的功能模块, 如图 10所示, 其示出了本发明实施例所涉及的服务器的 结构示意图。
该服务器可以包括一个或者一个以上处理核心的处理器 1001、 一个或一 个以上计算机可读存储介质的存储器 1002、 射频 (Radio Frequency, RF ) 电 路 1003、 无线通信模块, 如蓝牙模块和 /或无线保真(Wireless Fidelity, WIFI ) 模块 1004等 (图 10中以 WIFI模块 1004为例)、 电源 1005、 传感器 1006、 输入单元 1007、 以及显示单元 1008等部件。 本领域技术人员可以理解, 图 10 中示出的服务器结构并不构成对服务器的限定,可以包括比图示更多或更少的 部件, 或者组合某些部件, 或者不同的部件布置。
处理器 1001是该服务器的控制中心, 利用各种接口和线路连接整个服务 器的各个部分, 通过运行或执行存储在存储器 1002内的软件程序和 /或模块, 以及调用存储在存储器 1002内的数据, 执行服务器的各种功能和处理数据, 从而对服务器进行整体监控。 可选的, 处理器 1001可包括一个或多个处理核 心; 优选的, 处理器 1001可集成应用处理器和调制解调处理器, 其中, 应用 处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理 无线通信。 可以理解的是, 上述调制解调处理器也可以不集成到处理器 1001 中。
存储器 1002可用于存储软件程序以及模块,处理器 1001通过运行存储在 存储器 1002的软件程序以及模块, 从而执行各种功能应用以及数据处理。 存 储器 1002可主要包括存储程序区和存储数据区, 其中, 存储程序区可存储操 作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等) 等;存储数据区可存储根据服务器的使用所创建的数据等。此外,存储器 1002 可以包括高速随机存取存储器,还可以包括非易失性存储器, 例如至少一个磁 盘存储器件、 闪存器件、 或其他易失性固态存储器件。 相应地, 存储器 1002 还可以包括存储器控制器, 以提供处理器 1001对存储器 1002的访问。
RF电路 1003可用于收发信息过程中, 信号的接收和发送, 特别地, 将基 站的下行信息接收后, 交由一个或者一个以上处理器 1001处理; 另外, 将涉 及上行的数据发送给基站。 通常, RF电路 1003包括但不限于天线、 至少一个 放大器、调谐器、一个或多个振荡器、用户身份模块( Subscriber Identity Module, SIM )卡、 收发信机、 耦合器、 低噪声放大器(Low Noise Amplifier, LNA )、 双工器等。 此外, RF电路 1003还可以通过无线通信与网络和其他设备通信。 该无线通信可以使用任一通信标准或协议, 包括但不限于全球移动通讯系统 ( Global System of Mobile communication, GSM )、通用分组无线月良务( General Packet Radio Service, GPRS )、 码分多址 ( Code Division Multiple Access, CDMA )、宽带码分多址 ( Wideband Code Division Multiple Access, WCDMA )、 长期演进 ( Long Term Evolution , LTE )、 电子邮件、 短消息服务 (Short Messaging Service, SMS )等。
WIFI属于短距离无线传输技术, 服务器通过 WIFI模块 1004收发电子邮 件和访问流式媒体等, 它可以提供无线的宽带互联网访问。 虽然图 10示出了 WIFI模块 1004, 但是可以理解的是, 其并不属于服务器的必须构成, 完全可 以根据需要在不改变发明的本质的范围内而省略。
服务器还包括给各个部件供电的电源 1005 (比如电池), 优选的, 电源可 以通过电源管理系统与处理器 1001逻辑相连, 从而通过电源管理系统实现管 理充电、 放电、 以及功耗管理等功能。 电源 1005还可以包括一个或一个以上 的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、 电源状态指示器等任意组件。
该服务器还可包括至少一种传感器 1006, 比如光传感器、 运动传感器以 及其他传感器。 该服务器还可配置的陀螺仪、 气压计、 湿度计、 温度计、 红外 线传感器等其他传感器, 在此不再赘述。
该服务器还可包括输入单元 1007, 该输入单元 1007可用于接收输入的数 字或字符信息,以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、 光学或者轨迹球信号输入。 具体地, 在一个具体的实施例中, 输入单元 1007 可包括触敏表面以及其他输入设备。触敏表面,也称为触摸显示屏或者触控板, 可收集用户在其上或附近的触摸操作 (比如用户使用手指、触笔等任何适合的 物体或附件在触敏表面上或在触敏表面附近的操作 ), 并根据预先设定的程式 驱动相应的连接装置。可选的,触敏表面可包括触摸检测装置和触摸控制器两 个部分。 其中, 触摸检测装置检测用户的触摸方位, 并检测触摸操作带来的信 号, 将信号传送给触摸控制器; 触摸控制器从触摸检测装置上接收触摸信息, 并将它转换成触点坐标, 再送给处理器 1001 , 并能接收处理器 1001发来的命 令并加以执行。 此外, 可以釆用电阻式、 电容式、 红外线以及表面声波等多种 类型实现触敏表面。 除了触敏表面,输入单元 1007还可以包括其他输入设备。 具体地, 其他输入设备可以包括但不限于物理键盘、 功能键(比如音量控制按 键、 开关按键等)、 轨迹球、 鼠标、 操作杆等中的一种或多种。
该服务器还可包括显示单元 1008, 该显示单元 1008可用于显示由用户输 入的信息或提供给用户的信息以及服务器的各种图形用户接口,这些图形用户 接口可以由图形、 文本、 图标、 视频和其任意组合来构成。 显示单元 1008可 包括显示面板,可选的,可以釆用液晶显示器 ( Liquid Crystal Display, LCD ), 有机发光二极管 ( Organic Light-Emitting Diode, OLED )等形式来配置显示面 板。 进一步的, 触敏表面可覆盖显示面板, 当触敏表面检测到在其上或附近的 触摸操作后, 传送给处理器 1001 以确定触摸事件的类型, 随后处理器 1001 根据触摸事件的类型在显示面板上提供相应的视觉输出。 虽然在图 10中, 触 敏表面与显示面板是作为两个独立的部件来实现输入和输入功能,但是在某些 实施例中, 可以将触敏表面与显示面板集成而实现输入和输出功能。
尽管未示出, 服务器还可以包括摄像头、 蓝牙模块等, 在此不再赘述。 具 体在本实施例中, 服务器中的处理器 1001会按照如下的指令, 将一个或一个 以上的应用程序的进程对应的可执行文件加载到存储器 1002中, 并由处理器
1001来运行存储在存储器 1002中的应用程序, 从而实现各种功能, 如下: 接收用户的登录请求, 该登录请求中包含请求登录的账户的标识信息; 若确定该账户处于冻结状态, 则根据该登录请求获取该用户的位置信息; 以及
判断该位置信息是否满足预置的登录条件, 若满足, 则允许该用户登录该 账户。
实施例十一:
本发明实施例还提供一种安全认证系统, 请参阅图 11 , 本发明实施例中 的安全认证系统包括: 登录统计服务器 1101、 登录策略服务器 1102以及登录 校验服务器 1103。
该登录统计服务器 1101 用于根据历史登录行为确定账户的常用登录区 域, 并将常用登录区域信息发送至登录校验服务器 1103。
该登录策略服务器 1102用于接收用户的登录请求, 该登录请求中包含请 求登录的账户的标识信息, 若根据该标识信息确定该账户处于冻结状态, 则根 据该登录请求获取该用户的位置信息,将该用户的位置信息发送至该登录校验 服务器 1103。
该登录校验服务器 1103用于判断该位置信息是否属于该用户的常用登录 区域, 并向该登录策略服务器 1102发送判断结果。
若该判断结果为是, 则该登录策略服务器 1102还用于允许该用户登录该 账户。
为便于理解,下面以一个具体应用场景对本实施例安全认证系统中的各设 备之间的交互进行描述:
本实施例中, 账户每次被登录之后,登录用户可以不定时的向登录统计服 务器 1101上报登录行为信息, 该登录行为信息中包含有登录用户的账户、 登 录的时间、 登录的 IP地址等信息。
本实施例中, 登录统计服务器 1101可以收集到该账户被登录之后所上报 的登录行为信息, 所以能够从这些历史登录行为中确定该账户的各登录区域。
具体的确定方式可以采用如下几种方式。
一、 根据总登录次数确定
例如, 登录统计服务器 1101根据历史登录行为确定账户的各登录区域, 登录统计服务器 1101将登录次数达到预置数值的登录区域设定为目标登录区 域, 并将目标登录区域作为该账户的常用登录区域。
二、 根据近期登录次数确定
例如, 登录统计服务器 1101根据历史登录行为确定账户的各登录区域, 登录统计服务器 1101将最近预置时长内登录次数达到预置数值的登录区域设 定为目标登录区域, 并将目标登录区域作为用户的常用登录区域。
三、 根据登录次数和时间综合确定
例如, 登录统计服务器 1101根据历史登录行为确定账户的各登录区域, 登录统计服务器 1101根据第一权值以及在各登录区域的登录次数确定各登录 区域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登录区 域的第二参考值,并将第一参考值与第二参考值之和作为该登录区域的综合参 考值, 登录统计服务器 1101将综合参考值达到预置数值的登录区域作为账户 的常用登录区域。
需要说明的是,上述三种确定方式的具体过程在图 2至图 4所示的实施例 中已经详细描述过, 此处不再赞述。
当用户希望登录该账户时, 可以向登录策略服务器 1102发送登录请求, 则登录策略服务器 1102可以接收到用户发送的登录请求, 该登录请求中可以 包含请求登录的账户的标识信息。
可以理解的是, 该登录请求中还可以进一步包含用户名、 密码等信息, 具 体此处不做限定。
本实施例中, 若账户被冻结, 例如, 该账户可能由于发送恶意信息而被冻 结, 则登录策略服务器 1102在接收到用户发送的登录请求之后, 不会直接拒 绝用户的登录请求, 而是会根据用户发送的登录请求获取用户的位置信息。 本实施例中, 登录策略服务器 1102可以通过多种方式获取用户的位置信 息, 具体可以有如下一些方式。
一、 登录策略服务器 1102从登录请求中获取该用户的位置信息。
例如, 当登录请求中还包括登录地址信息时, 登录策略服务器 1102从该 登录地址信息中解析出用户的网络地址, 该网络地址为 IP地址, 或者为 LBS 地址;
登录策略服务器 1102根据网络地址与位置信息之间的对应关系, 查询该 用户的网络地址对应的该用户的位置信息。
二、 登录策略服务器 1102从转发该登录请求的消息转发网元获取该用户 的位置信息。
例如, 登录策略服务器 1102从转发登录请求的消息转发网元获取该用户 的网络地址, 该网络地址为 IP地址, 或者为 LBS地址;
登录策略服务器 1102根据网络地址与位置信息之间的对应关系, 查询该 用户的网络地址对应的该用户的位置信息。
需要说明的是,具体获取用户的位置信息的方式与图 2所示实施例中的步 骤 205所描述的内容一致, 此处不再赘述。
登录策略服务器 1102将用户的位置信息发送至登录校验服务器 1103。 登录校验服务器 1103判断位置信息是否属于该用户的常用登录区域,并向 登录策略服务器 1102发送判断结果。
登录校验服务器 1103根据登录请求获取用户的位置信息之后,可以判断该 位置信息是否属于该账户的常用登录区域,并将判断结果发送给登录策略服务 器 1102。
若该位置信息属于常用登录区域, 则说明当前的用户在该账户的常用登录 区域登录该账户,这一行为符合该账户的登录用户的历史登录习惯, 所以可以 认定该用户为正常用户, 则登录策略服务器 1102允许该用户登录账户。
本实施例中, 登录统计服务器 1101可以根据历史登录行为确定账户的常 用登录区域, 当登录策略服务器 1102接收到用户的登录请求时, 如果该账户 处于冻结状态,可以根据该登录请求获取用户的位置信息, 若该位置信息属于 常用登录区域, 则可以认定该用户为正常用户, 则允许该用户登录账户, 所以 根据用户登录时的位置信息对用户的登录请求进行区分处理可以有效的避免 冻结处理对正常用户使用账号的影响。
所属领域的技术人员可以清楚地了解到, 为描述的方便和简洁, 上述描述 的系统,装置和单元的具体工作过程,可以参考上述方法实施例中的对应过程, 在此不再赞述。
在本申请所提供的几个实施例中, 应该理解到, 所揭露的系统, 装置和方 法, 可以通过其它的方式实现。 例如, 以上所描述的装置实施例仅仅是示意性 的, 例如, 所述单元的划分, 仅仅为一种逻辑功能划分, 实际实现时可以有另 外的划分方式, 例如多个单元或组件可以结合或者可以集成到另一个系统,或 一些特征可以忽略, 或不执行。 另一点, 所显示或讨论的相互之间的耦合或直 接耦合或通信连接可以是通过一些接口, 装置或单元的间接耦合或通信连接, 可以是电性, 机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为 单元显示的部件可以是或者也可以不是物理单元, 即可以位于一个地方,或者 也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部 单元来实现本实施例方案的目的。
另外, 在本发明各个实施例中的各功能单元可以集成在一个处理单元中, 也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元 中。上述集成的单元既可以釆用硬件的形式实现,也可以采用软件功能单元的 形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售 或使用时, 可以存储在一个计算机可读取存储介质中。 基于这样的理解, 本发 明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全 部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储 介质中, 包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器, 的存储介质包括: U盘、移动硬盘、 只读存储器(Read-Only Memory, ROM ), 随机存取存储器(Random Access Memory, RAM ), 磁碟或者光盘等各种可以 存储程序代码的介质。 以上所述, 以上实施例仅用以说明本发明的技术方案, 而非对其限制; 尽 管参照上述实施例对本发明进行了详细的说明,本领域的普通技术人员应当理 解: 其依然可以对上述各实施例所记载的技术方案进行修改,或者对其中部分 技术特征进行等同替换; 而这些修改或者替换, 并不使相应技术方案的本质脱 离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种安全认证方法, 其特征在于, 包括:
接收用户的账户登录请求,所述登录请求中包含请求登录的账户的标识信 息;
若根据所述标识信息确定所述账户处于冻结状态,则根据所述登录请求获 取所述用户的位置信息; 以及
判断所述位置信息是否满足预置的登录条件, 若满足, 则允许所述用户登 录所述账户。
2、 根据权利要求 1所述的方法, 其特征在于, 当所述登录请求中还包括 登录地址信息时;
所述根据所述登录请求获取所述用户的位置信息包括:
从所述登录地址信息中解析出所述用户的网络地址,所述网络地址包括互 联网协议(IP )地址, 和基于位置的服务(LBS )地址; 以及
根据网络地址与位置信息之间的对应关系,查询所述用户的网络地址对应 的所述用户的位置信息。
3、 根据权利要求 1所述的方法, 其特征在于, 所述根据所述登录请求获 取所述用户的位置信息包括:
从转发所述登录请求的消息转发网元获取所述用户的网络地址,所述网络 地址包括 IP地址, 和 LBS地址; 以及
根据网络地址与位置信息之间的对应关系,查询所述用户的网络地址对应 的所述用户的位置信息。
4、 根据权利要求 1至 3中任一项所述的方法, 其特征在于, 所述方法还 包括:
根据历史登录行为确定所述账户的常用登录区域。
5、 根据权利要求 4所述的方法, 其特征在于, 所述判断所述位置信息是 否满足预置的登录条件包括:
判断所述位置信息是否属于所述常用登录区域, 若属于, 则确定满足所述 预置的登录条件, 若不属于, 则确定不满足所述预置的登录条件。
6、 根据权利要求 4所述的方法, 其特征在于, 所述根据历史登录行为确 定所述账户的常用登录区域包括:
根据历史登录行为确定所述账户的各登录区域; 以及
将登录次数达到预置数值的登录区域设定为目标登录区域,并将所述目标 登录区域作为所述账户的常用登录区域。
7、 根据权利要求 4所述的方法, 其特征在于, 所述根据历史登录行为确 定所述用户的常用登录区域包括:
根据历史登录行为确定所述账户的各登录区域; 以及
将最近预置时长内登录次数达到预置数值的登录区域设定为目标登录区 域, 并将所述目标登录区域作为所述账户的常用登录区域。
8、 根据权利要求 4所述的方法, 其特征在于, 所述根据历史登录行为确 定所述账户的常用登录区域包括:
根据历史登录行为确定所述账户的各登录区域;
根据第一权值以及在各登录区域的登录次数确定各登录区域的第一参考 值, 根据第二权值以及在各登录区域的登录时间确定各登录区域的第二参考 值, 并将第一参考值与第二参考值之和作为该登录区域的综合参考值; 以及 将综合参考值达到预置数值的登录区域作为所述账户的常用登录区域。
9、 一种安全认证方法, 其特征在于, 包括:
登录统计服务器根据历史登录行为确定账户的常用登录区域,并将常用登 录区域信息发送至登录校验服务器;
所述登录策略服务器接收用户对所述账户的登录请求,所述登录请求中包 含所述账户的标识信息;
若所述登录策略服务器根据所述标识信息确定所述账户处于冻结状态,则 所述登录策略服务器根据所述登录请求获取所述用户的位置信息;
所述登录策略服务器将所述用户的位置信息发送至所述登录校验服务器; 所述登录校验服务器判断所述位置信息是否属于所述账户的常用登录区 域, 并向所述登录策略服务器发送判断结果; 以及
若所述位置信息属于所述账户的常用登录区域,则所述登录策略服务器允 许所述用户登录所述账户。
10、根据权利要求 9所述的方法, 其特征在于, 当所述登录请求中还包括 登录地址信息时;
所述登录策略服务器根据所述登录请求获取所述用户的位置信息包括: 所述登录策略服务器从所述登录地址信息中解析出所述用户的网络地址, 所述网络地址包括互联网协议 ( IP )地址和为基于位置的服务(LBS )地址; 以及
所述登录策略服务器根据网络地址与位置信息之间的对应关系,查询所述 用户的网络地址对应的所述用户的位置信息。
11、 根据权利要求 9所述的方法, 其特征在于, 所述登录策略服务器根据 所述登录请求获取所述用户的位置信息包括:
所述登录策略服务器从转发所述登录请求的消息转发网元获取所述用户 的网络地址, 所述网络地址包括 IP地址和 LBS地址; 以及
所述登录策略服务器根据网络地址与位置信息之间的对应关系,查询所述 用户的网络地址对应的所述用户的位置信息。
12、 根据权利要求 9至 11中任一项所述的方法, 其特征在于, 所述登录 统计服务器根据历史登录行为确定所述账户的常用登录区域包括:
所述登录统计服务器根据历史登录行为确定所述账户的各登录区域; 所述登录统计服务器将登录次数达到预置数值的登录区域设定为目标登 录区域, 并将所述目标登录区域作为所述账户的常用登录区域;
或,
所述登录统计服务器根据历史登录行为确定所述账户的各登录区域; 所述登录统计服务器将最近预置时长内登录次数达到预置数值的登录区 域设定为目标登录区域, 并将所述目标登录区域作为所述账户的常用登录区 域;
或,
所述登录统计服务器根据历史登录行为确定所述账户的各登录区域; 所述登录统计服务器根据第一权值以及在各登录区域的登录次数确定各 登录区域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登 录区域的第二参考值 ,并将第一参考值与第二参考值之和作为该登录区域的综 合参考值; 所述登录统计服务器将综合参考值达到预置数值的登录区域作为所述账 户的常用登录区域。
13、 一种服务器, 其特征在于, 包括:
接收单元, 用于接收用户的登录请求, 所述登录请求中包含请求登录的账 户的标识信息;
获取单元, 用于当根据所述标识信息确定所述账户处于冻结状态时,根据 所述登录请求获取所述用户的位置信息;
认证单元, 用于判断所述位置信息是否满足预置的登录条件, 若满足, 则 允许所述用户登录所述账户。
14、 根据权利要求 13所述的服务器, 其特征在于, 当所述登录请求中还 包括登录地址信息时;
所述获取单元包括:
第一获取模块, 用于从所述登录地址信息中解析出所述用户的网络地址, 所述网络地址包括互联网协议 ( IP )地址和基于位置的月良务(LBS )地址; 以 及
第一查询模块, 用于根据网络地址与位置信息之间的对应关系, 查询所述 用户的网络地址对应的所述用户的位置信息。
15、 根据权利要求 13所述的服务器, 其特征在于, 所述获取单元包括: 第二获取模块,用于从转发所述登录请求的消息转发网元获取所述用户的 网络地址, 所述网络地址包括 IP地址和 LBS地址; 以及
第二查询模块, 用于根据网络地址与位置信息之间的对应关系, 查询所述 用户的网络地址对应的所述用户的位置信息。
16、根据权利要求 12至 15中任一项所述的服务器, 其特征在于, 所述服 务器还包括:
确定单元, 用于根据历史登录行为确定所述账户的常用登录区域。
17、 根据权利要求 16所述的服务器, 其特征在于,
所述认证单元用于判断所述位置信息是否属于所述常用登录区域, 若属 于, 则确定满足所述预置的登录条件, 若不属于, 则确定不满足所述预置的登 录条件。
18、 根据权利要求 16所述的服务器, 其特征在于, 所述确定单元包括: 第一确定模块, 用于根据历史登录行为确定所述账户的各登录区域; 以及 第三查询模块,用于将登录次数达到预置数值的登录区域设定为目标登录 区域, 并将所述目标登录区域作为所述账户的常用登录区域。
19、 根据权利要求 16所述的服务器, 其特征在于, 所述确定单元包括: 第二确定模块, 用于根据历史登录行为确定所述账户的各登录区域; 以及 第四查询模块,将最近预置时长内登录次数达到预置数值的登录区域设定 为目标登录区域, 并将所述目标登录区域作为所述账户的常用登录区域。
20、 根据权利要求 16所述的服务器, 其特征在于, 所述确定单元包括: 第三确定模块, 根据历史登录行为确定所述账户的各登录区域; 计算模块,用于根据第一权值以及在各登录区域的登录次数确定各登录区 域的第一参考值,根据第二权值以及在各登录区域的登录时间确定各登录区域 的第二参考值,并将第一参考值与第二参考值之和作为该登录区域的综合参考 值; 以及
第四确定模块,用于将综合参考值达到预置数值的登录区域作为所述账户 的常用登录区域。
21、 一种安全认证系统, 其特征在于, 包括:
登录统计服务器、 登录策略服务器以及登录校验服务器;
所述登录统计服务器用于根据历史登录行为确定账户的常用登录区域,并 将所述常用登录区域信息发送至所述登录校验服务器;
所述登录策略服务器用于接收用户对所述账号的登录请求,所述登录请求 中包含所述账户的标识信息, 若根据所述标识信息确定所述账户处于冻结状 态, 则才艮据所述登录请求获取所述用户的位置信息,将所述用户的位置信息发 送至所述登录校验服务器;
所述登录校验服务器用于判断所述位置信息是否属于所述账户的常用登 录区域, 并向所述登录策略服务器发送判断结果;
若所述位置信息属于所述账户的常用登录区域,则所述登录策略服务器还 用于允许所述用户登录所述账户。
PCT/CN2014/084760 2013-08-21 2014-08-20 安全认证方法、服务器以及安全认证系统 WO2015024506A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310367429.X 2013-08-21
CN201310367429.XA CN104426844B (zh) 2013-08-21 2013-08-21 一种安全认证方法、服务器以及安全认证系统

Publications (1)

Publication Number Publication Date
WO2015024506A1 true WO2015024506A1 (zh) 2015-02-26

Family

ID=52483083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/084760 WO2015024506A1 (zh) 2013-08-21 2014-08-20 安全认证方法、服务器以及安全认证系统

Country Status (2)

Country Link
CN (1) CN104426844B (zh)
WO (1) WO2015024506A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111010402A (zh) * 2019-12-24 2020-04-14 深信服科技股份有限公司 账号登陆方法、装置、设备及计算机可读存储介质
US20210042756A1 (en) * 2018-05-30 2021-02-11 Simplecredit Micro-Lending Co., Ltd. Blockchain-based Security Management Method, Related Device and Storage Medium

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106330840B (zh) 2015-07-01 2020-06-30 阿里巴巴集团控股有限公司 挂失账号的登录方法和装置
CN105491028B (zh) * 2015-11-25 2019-01-25 四川诚品电子商务有限公司 电商平台账户的身份认证方法
CN107317790B (zh) * 2016-04-27 2020-12-01 阿里巴巴集团控股有限公司 网络行为的监控方法及装置
CN108021803A (zh) * 2016-10-31 2018-05-11 黄策 按时空划分保护账户登陆信息的管理方法
CN108206865A (zh) * 2016-12-19 2018-06-26 北京国双科技有限公司 获取用户所处地理位置的方法及装置
CN107196970A (zh) * 2017-07-15 2017-09-22 深圳市华琥技术有限公司 一种安全认证方法、服务器
CN110198305A (zh) * 2019-05-05 2019-09-03 平安科技(深圳)有限公司 坐席ip的异常检测方法、系统、计算机设备及存储介质
CN110798453B (zh) * 2019-10-16 2022-07-12 上海易点时空网络有限公司 用于一键登录的数据处理方法及装置
CN112633895A (zh) * 2021-01-05 2021-04-09 交通银行股份有限公司 银行线上网点业务数字货币交易的风险控制方法及系统
CN113472746A (zh) * 2021-05-31 2021-10-01 珠海大横琴科技发展有限公司 一种数据处理方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007141085A (ja) * 2005-11-21 2007-06-07 Fuji Xerox Co Ltd コンピュータシステム、認証制御方法、プログラム及びサーバ・クライアントシステム
CN101626295A (zh) * 2008-07-08 2010-01-13 中国移动通信集团公司 一种网络登录的安全保障方法及其装置和系统
CN103095658A (zh) * 2011-11-03 2013-05-08 北京神州泰岳软件股份有限公司 一种账户登录的方法和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080163342A1 (en) * 2006-12-04 2008-07-03 Christopherson David L System and method for managing information relating to end-of-life issues
US10165007B2 (en) * 2011-09-15 2018-12-25 Microsoft Technology Licensing, Llc Securing data usage in computing devices
CN103001826B (zh) * 2012-11-29 2015-09-30 北京奇虎科技有限公司 用于监测用户登录的设备和方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007141085A (ja) * 2005-11-21 2007-06-07 Fuji Xerox Co Ltd コンピュータシステム、認証制御方法、プログラム及びサーバ・クライアントシステム
CN101626295A (zh) * 2008-07-08 2010-01-13 中国移动通信集团公司 一种网络登录的安全保障方法及其装置和系统
CN103095658A (zh) * 2011-11-03 2013-05-08 北京神州泰岳软件股份有限公司 一种账户登录的方法和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210042756A1 (en) * 2018-05-30 2021-02-11 Simplecredit Micro-Lending Co., Ltd. Blockchain-based Security Management Method, Related Device and Storage Medium
CN111010402A (zh) * 2019-12-24 2020-04-14 深信服科技股份有限公司 账号登陆方法、装置、设备及计算机可读存储介质

Also Published As

Publication number Publication date
CN104426844A (zh) 2015-03-18
CN104426844B (zh) 2019-02-05

Similar Documents

Publication Publication Date Title
WO2015024506A1 (zh) 安全认证方法、服务器以及安全认证系统
US9712562B2 (en) Method, device and system for detecting potential phishing websites
WO2015090248A1 (zh) 服务器的过载保护方法及装置
CN106686070B (zh) 一种数据库数据迁移方法、装置、终端及系统
WO2014180123A1 (zh) 恶意网址的访问防御方法和相关装置
US11765170B2 (en) Data processing method, system, and apparatus, storage medium, and device
WO2016180138A1 (zh) 推广信息投放有效性确定方法、监测服务器及终端
WO2015027714A1 (zh) 视频播放方法、装置、终端设备和服务器
CN111064713B (zh) 一种分布式系统中的节点控制方法和相关装置
CN103731810A (zh) 接入点共享方法及装置
KR20160009599A (ko) 디바이스들 사이의 네크워크 액세스의 효율적인 자동 공유
WO2014169661A1 (en) Method and system for processing report information
CN107888550B (zh) 性能指标数据采集方法和装置、策略发送方法和装置
CN107466041B (zh) 识别伪基站方法、装置及移动终端
CN109714298B (zh) 验证方法、装置及存储介质
CN106657165B (zh) 一种网络攻击的防御方法、服务器及终端
WO2017054585A1 (zh) 网络接入方法、装置及系统
US20150089600A1 (en) Methods, devices and systems for router access control
WO2018210214A1 (zh) 设备定位方法及装置
CN113037741A (zh) 一种鉴权方法和相关装置
CN107682860B (zh) 重定向管控方法、装置、网络设备和移动终端
WO2015101302A1 (zh) 数据共享方法、系统、用户端及后台服务器
WO2017091951A1 (zh) 一种系统消息的通知方法及用户设备
WO2015014173A1 (zh) 离线自动锁定业务的方法、装置及系统
CN105577627B (zh) 通信方法、装置、网络设备、终端设备和通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14837925

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 07/07/2016)

122 Ep: pct application non-entry in european phase

Ref document number: 14837925

Country of ref document: EP

Kind code of ref document: A1