WO2018024176A1

WO2018024176A1 - Device and method preventing repeated logins of same user

Info

Publication number: WO2018024176A1
Application number: PCT/CN2017/095307
Authority: WO
Inventors: 郭磊
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-08-04
Filing date: 2017-07-31
Publication date: 2018-02-08
Also published as: CN107689941A

Abstract

The invention discloses a device and method preventing repeated logins of the same user. The method comprises: receiving a login request containing a user identification and user terminal characteristic information of a user terminal being used by a user; acquiring record information comprising a user identification field and a corresponding user terminal characteristic information field recording the user identification of the user and the user terminal characteristic information of the user terminal being used by the user, respectively; determining, according to the login request and the record information, whether a repeated login has performed by the user; and if so, generating a response to prevent the same user from repeatedly logging in. The embodiment ensures security and uniqueness of user information. In comparison to an unfavorable impact of adopting the prior art on website service performance, employing the invention results in no impact on website performance, causing no performance bottleneck to the website when the website is accessed by a large number of users, facilitating enhancement of user experience and expansion of website capacity, and providing advantages of simple implementation and small development costs.

Description

Device and method for preventing repeated login by same user

Technical field

The present invention relates to the field of communications technologies, and in particular, to an apparatus and method for preventing repeated login by the same user.

Background technique

In recent years, mobile communications and the Internet have become the two fastest growing businesses in the world with the greatest market potential and the most attractive prospects. The rapid growth that has never been seen in this history reflects the dramatic rise in human demand for mobility and information as times and technologies advance. More and more people want to access the Internet and get much-needed information. Websites based on PC (Personal Computer) and mobile terminals have sprung up, and most websites require users to log in and log in to use the related services provided by the website.

In order to improve the user experience and data security, it is necessary to keep the same user in a non-repeating login state at the same time, that is, to keep the same user logged in only one terminal at the same time.

For the website, it can be deployed in a single server. However, due to the large number of Internet users, the number of visitors to the website is generally large. In order to improve the performance and bring a better experience to users, most websites generally adopt server cluster deployment.

For a single-server deployment site, you can use the service software session feature to keep the same user logged in on only one terminal at the same time. For the website deployed by the cluster server, the server software session automatic synchronous replication function or the database is used to maintain the same. The state in which the same user only logs in on one terminal. However, the above methods in the prior art all affect the performance of the website business, especially when there are large users on the website, it will become a performance bottleneck of the website.

Summary of the invention

The main technical problem to be solved by the embodiments of the present invention is to provide an apparatus and method for preventing repeated login by the same user, which solves the problem of utilizing the service software session feature or the server software session automatic synchronous replication function in the prior art, or by using a database. Keeping the same user logged in on only one terminal at the same time, which affects the performance of the website business, becomes a problem of website performance bottleneck in the case of a large number of users.

To solve the above technical problem, an embodiment of the present invention provides an apparatus for preventing repeated login by the same user, including:

The receiving module is configured to receive a login request of the user, where the information carried in the login request includes the user identity and the client feature information of the client currently used by the user;

The determining module is configured to determine, according to the information carried in the login request and the obtained record information, whether the user is a duplicate login, the record information includes a user identity identifier field, and a client feature information field corresponding to the user identity identifier field, the user The identity identifier field is used to record the user identity of the authorized user, and the client feature information field is used to record the client feature information of the client that is currently used by the user in the login success state;

The response module is configured to respond to the login request according to a preset manner if the judgment result of the determination module is repeated login, so as to prevent the same user from repeatedly logging in.

To solve the above technical problem, the embodiment of the present invention further provides a method for preventing the same user from repeatedly logging in, including:

Receiving a login request of the user, where the information carried in the login request includes the user identity and the client feature information of the client currently used by the user;

Determining whether the user is a duplicate login according to the information carried in the login request and the obtained record information, the record information includes a user identity identifier field, and a client feature information field corresponding to the user identity identifier field, where the user identity identifier field is used. Recording the user identity of the authorized user, and the client feature information field is used to record the client feature information of the client that is currently used by the user in the login success state;

If the result of the judgment is repeated login, the login request is responded to in a preset manner to prevent the same The user logs in repeatedly.

In an embodiment of the present invention, a computer storage medium is further provided, and the computer storage medium may store an execution instruction for performing the implementation of preventing the same user from repeatedly logging in the foregoing embodiment.

The embodiment of the invention discloses a device and a method for preventing the same user from repeatedly logging in. The user may receive the login request of the user and obtain the record information. The login request carries the user identity and the client feature information of the client currently used by the user. The user identity field and the client feature information field are respectively stored in the record information, and are used to record the user identity of the authorized user and the client feature information of the client used by the corresponding user in the login success state, respectively, when receiving the user's After the login request, according to the information carried in the login request and the record information, it is possible to accurately and quickly determine whether the user is a duplicate login, and when the judgment result is a duplicate login, respond accordingly to prevent the same user from repeatedly logging in. The user data is guaranteed to be unique. Compared with the prior art, the service software session feature is used, or the server software session automatic synchronous replication function is used, or the database is used to maintain the login status of the same user. This embodiment has no effect on the performance of the website. In the big Without the user's use of the website, the site will not cause a performance bottleneck, help to improve the user's sense of the use of the site and increasing the capacity of the site.

DRAWINGS

FIG. 1 is a flowchart of a method for preventing repeated login by the same user according to Embodiment 1 of the present invention;

2 is a schematic block diagram of an apparatus for preventing repeated login by the same user according to Embodiment 2 of the present invention;

FIG. 3 is a schematic diagram of another apparatus for preventing repeated login by the same user according to Embodiment 2 of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings.

Embodiment 1:

Referring to FIG. 1, the embodiment provides a method for preventing the same user from repeatedly logging in. The user identity identifier carried in the user login request and the client feature information and the record information of the client used by the user can be used to control the repeated login of the user. The user identifier of the authorized user and the client feature information corresponding to the identity identifier are recorded in the record information, and the client feature information is client feature information that is successfully logged in. Therefore, according to the client feature information in the login request of the user and the client feature information in the record information, whether the user's current login is a duplicate login result can be obtained, and then the response can be obtained according to the judgment result. Prevent the same user from repeatedly logging in. The user's repeated login behavior is effectively avoided, the security level of the user account is improved, and the leakage of security information caused by repeated login is avoided, which is particularly suitable for the situation where the security requirement of the user's private information on the website is relatively high.

Referring to FIG. 1, a method for preventing repeated login by the same user in this embodiment is shown, including:

S101. Receive a login request of the user, where the information carried in the login request includes the user identity identifier and client feature information of the client currently used by the user.

S102. Determine, according to the information carried in the login request and the obtained record information, whether the user is a duplicate login, the record information includes a user identity identifier field, and a client feature information field corresponding to the user identity identifier field, and the user identity identifier field. The user identity information used to record the authorized user, and the client feature information field is used to record the client feature information of the client that is currently used by the user in the login success state;

S103. If the result of the determination is repeated login, respond to the login request in a preset manner to prevent the same user from repeatedly logging in.

In this embodiment, the objects that the user logs in using the login request include, but are not limited to, various portal websites such as Taobao, glutinous rice, Meituan, and various websites such as QQ, WeChat, and the like. Clients include, but are not limited to, electronic devices such as mobile terminals, tablets, and desktop computers. The client can exchange data with the server of the website through a wireless network or a wired network when logging in. In this embodiment, the website that is logged in may be a website deployed by a single server, or may be a cluster of servers. Way to deploy the site. This embodiment is not limited thereto.

The user identity is information used to distinguish different users, and can be understood as login account information, such as a user ID. The client feature information is information that can be used to distinguish different clients. The client feature information may be different according to the type of the client, including but not limited to IP, the identifier of the mobile terminal, the IMEI number, and the session identifier.

In this embodiment, the storage location of the record information in S102 may be in the server of the login website, or may be in another storage section. The preferred way is to store the record information in an external cache space, where the external is relative to the server of the website, the external cache space can be a third-party distributed cache space, and the distributed cache can guarantee the server. User data uniqueness, security, and access performance efficiency in a cluster environment. In addition, the external cache space may be other types of storage space, which is not limited in this embodiment.

Preferably, the step of acquiring the record information in S102 comprises: acquiring the record information from the external cache space.

The record information includes a user identity field and a client feature information field, which are used to record the user identity of the authorized user, and the client feature information of the client that is authorized to use the user in the login success state. It can be understood that the user identity and the client feature information are correspondingly stored in the record information. Preferably, the user identity identifier and the client feature information in the record corresponding information may be used to store the user identity field and the client. The end feature information field is used as the header of the table. When recording, the user identity of the authorized user is filled in the cell under the user identity field, and the client feature information of the client used by the same authorized user is currently in the login success state. Fill in the corresponding cell under the client feature information field.

In addition, the user identity field and the client feature information field in this embodiment may exist in the form of a key-value pair. When it is required to record related information of the user and the client that successfully log in, the user identity may be used as the key name. The client feature information is used as a key value to form a user identity-client feature information key-value pair, wherein the user identity in a key-value pair is The user identity of the authorized user. The client feature information is the client feature information of the client that is authorized to log in successfully.

In this embodiment, the user identity in the record information is the user identity of the authorized user. To ensure that the user who is successfully logged in is the authorized user who has successfully registered, before S102, the login request in S101 is generally required to be carried. The user identity in the information is verified. After the server verifies the user identity, the user accesses the logged-in website. The specific process of the verification is generally to match the user identity in the login request with the user identity that is successfully registered. If the matching is successful, the verification succeeds, the matching fails, and the verification fails. In this embodiment, the user identity that is successfully registered may exist in a specific registry.

In this embodiment, the manner in which the user identity is recorded into the record information includes but is not limited to the following two types:

The first way: after the user is successfully registered, the user identity registered by the user is recorded in the record information.

The second way: after each successful login of the user, the user identity of the successful login is recorded in the record information. It can be foreseen that in the second way, if a user logs out, the corresponding user identity and client identification information in the record information will be cleared.

In this embodiment, if the user identity in the record information adopts the first record mode, the user identity of all registered users is recorded in the record information, and the user identity carried in the login request is verified. The user identity in the login request can be directly matched with the record information, without additionally setting a registry record to register the user identity of the user, thereby saving system computing resources and storage resources. If the second recording mode is adopted, it is necessary to additionally add a registry record to register the user identity of the user, which wastes storage space. Therefore, in the present embodiment, the first recording mode is obviously more advantageous.

In addition, in this embodiment, since the client feature information recorded in the record information is the client feature information of the client currently used by the user in the login state, it can be foreseen that the user is successfully in the login state after the user logs out of the current login. The client uses the corresponding record in the record information - the client feature information will be cleared, if the record information uses the form to record the user mark The information and the client feature information are emptied, and the customer feature information corresponding to the user identification information of the user under the client feature information field is emptied. The user identification information can be deleted or saved at the same time. If the user logs in with the user identity, the client feature information of the corresponding successfully registered client can be directly recorded in the record information.

When the user first uses the client to log in to the registration website after registration, it can be foreseen that the client feature information corresponding to the user identity of the user in the record information is empty, and the client feature information is recorded only after the user successfully logs in. Go to the corresponding space. After the user logs out, the client feature information is cleared until the next time the user logs in successfully, and then the client feature information of the client corresponding to the user is filled in.

In the process of using the website, it is inevitable that the user can use other clients to repeatedly log in to the same website. Considering the user's experience and data security, the same user needs to be in the login state at the same time.

Therefore, it is determined in S102 whether the user's current login is a duplicate login. Since the record information in this embodiment records the client feature information of the client currently used in the login state, the client feature information in the record information can be real-time. The client that successfully logs in to the user is reflected. Therefore, the present embodiment can determine whether the login is a duplicate login based on the record information.

When the user identity verification in the login request is verified, it can be determined whether the login is a duplicate login. In S102, according to the information carried in the login request and the obtained record information, determining whether the user is a duplicate login in this manner includes any one of the following two methods:

The first type: according to the user identity carried in the login request, whether the client feature information field corresponding to the identity of the same user in the record information is empty; if not, the result of the determination is that the user is a duplicate login.

Of course, if the client feature information field corresponding to the identity of the same user is empty, the current login is a non-duplicate login. Allowing this login will not cause duplicate logins.

The second type: according to the user identity carried in the login request, whether the client feature information in the client feature information field corresponding to the same user identity in the record information is queried The client feature information carried in the request is matched; if it does not match, the result of the judgment is that the user is a duplicate login this time.

In the second determination mode, if the client feature information in the client feature information field corresponding to the same user identity in the record information is empty, the matching result is still a non-duplicate login.

In this embodiment, the foregoing two methods may be used in combination. For example, it is determined whether the client feature information field corresponding to the same user identity in the record information is empty or empty, and the result of the determination is that the user is non-repeating this time. If the login is not empty, it is determined whether the client feature information in the client feature information field corresponding to the same user identity in the record information matches the client feature information carried in the login request. If the match does not match, the result is a user. This time, if the login is repeated and the match is made, the result of the judgment is that the user is a non-duplicate login.

When the result of the determination in S102 is a non-repeated login, it is foreseen that the client feature information field corresponding to the user identity carried in the login request is empty, indicating that the current user is not using any client in the login success state, and the permission is allowed. The secondary login does not cause repeated logins. Therefore, in S103, preventing the same user from repeatedly logging in includes: when the result of the determination is non-repeating login, the user is allowed to log in successfully, and the client feature information carried in the login request is filled into the record. The client feature information field corresponding to the same user identity in the message.

When the result of the determination in S102 is repeated login, in order to improve the security of the user experience and data, and to avoid leakage of user privacy, it is necessary to prevent the same user from logging in from multiple clients at the same time. At this time, in S103, responding to the login request according to the preset manner includes any one of the following three methods:

First: Deny the user's login request.

The second type: prompts the user whether to force the login. If the user is forced to log in, the user is forced to log out of the client that is successfully logged in, and the user is allowed to log in successfully. The user corresponding to the user ID of the user in the record information is recorded. The client feature information in the end feature information field is replaced with the client feature information of the client currently used by the user.

In the second mode, the user can use the voice, dialog box, and the like to prompt the user to log in through the terminal used by the user to log in. The user can provide the user with the interface on the interactive interface of the terminal. If the user chooses to force login, the terminal generates a forced login request, requests the forced exit of the client that the user is successfully logged in, and allows the user to log in this time. When the server receives the mandatory login request and implements After the login is successful, the client that successfully logs in changes, and the client feature information in the client feature information field corresponding to the user identity of the user in the record information needs to be replaced with the client feature information of the client currently used by the user.

The third type: determine whether the current login success status of the user is mandatory login, and if so, reject the user's current login request.

The third way is to prevent the problem that the server side is allowed to log in when the client has been forced to log out of the login service after the forced login is implemented. As a result, the user is forced to log out. When the terminal accesses the service, it can determine whether the current login success status of the user is mandatory login. If yes, the client that successfully logs in is logged in by means of mandatory login. Other clients may be forced to exit. You need to deny logins from other clients to avoid double logins.

In the process of using the client, when the user no longer needs to log in to the website to access the service, if the client is still in the login success state, other users may obtain the user information of the authorized user on the website through the client, thereby Lead to leakage of user information, resulting in privacy leaks or more serious economic losses. Therefore, in this embodiment, in order to further protect the security of the user data, the idle time of the client operation that the user has not successfully passed the login may be recorded. When the idle time exceeds the time threshold, the client successfully successfully logged out may be deleted and deleted. User client characteristics in the cache. Listening for idle time can be achieved by calling the session session listener with automatic exit or active exit.

With the method for preventing the same user from repeatedly logging in, the obtained record information correspondingly stores the user identity identifier field and the client feature information field, which are respectively used to record the user identity of the authorized user and the corresponding user is currently in the login success state. After receiving the login request of the user, the client's client feature information can accurately and quickly determine the user according to the user identity carried in the login request and the client feature information and the record information of the client currently used by the client. Whether this time is a repeated login, and the result of the judgment is repeated login. When responding, the same user is prevented from repeatedly logging in, ensuring that the user data is unique and secure. Compared with the prior art, the service software session feature is utilized, or the server software session is automatically synchronized, or the database is used to maintain the same user. In the manner of the login status, the performance of the website has no effect on the performance of the website. In the case that a large number of users use the website, the performance bottleneck is not caused to the website, which is beneficial to improving the user's website usage and expanding the capacity of the website. The implementation is simple, the development cost is small, and the specific implementation can be appropriately adjusted in combination with the characteristics of the server software, and has higher flexibility.

Embodiment 2:

Referring to FIG. 2, the embodiment shows an apparatus for preventing duplicate login by the same user, including:

The receiving module 21 is configured to receive a login request of the user, where the information carried in the login request includes the user identity identifier and client feature information of the client currently used by the user;

The determining module 22 is configured to determine, according to the information carried in the login request and the obtained record information, whether the user is a duplicate login, the record information includes a user identity identifier field, and a client feature information field corresponding to the user identity identifier field, The user identity field is used to record the user identity of the authorized user, and the client feature information field is used to record the client feature information of the client that is currently used by the user in the login success state.

The response module 23 is configured to respond to the login request in a preset manner to prevent the same user from repeatedly logging in if the determination result of the determination module is repeated login.

The device for preventing the same user from repeatedly logging in in this embodiment may be distributed on the server side to perform an operation of preventing repeated login.

The client of this embodiment includes, but is not limited to, an electronic device such as a mobile terminal, a tablet computer, or a desktop computer. The client can exchange data with the server of the website through a wireless network or a wired network when logging in.

The user identity is information used to distinguish different users, and can be understood as login account information, such as a user ID. The client feature information is information that can be used to distinguish different clients. The client feature information can be different according to the type of the client. Including but not limited to IP, the identifier of the mobile terminal, the IMEI number, and the session identifier.

In this embodiment, the storage location of the acquired record information may be in the server of the login website, or may be in another storage section. The preferred way is to store the record information in an external cache space, where the external is relative to the server of the website, the external cache space can be a third-party distributed cache space, and the distributed cache can guarantee the server. User data uniqueness, security, and access performance efficiency in a cluster environment. In addition, the external cache space may be other types of storage space, which is not limited in this embodiment.

Further, referring to FIG. 3, the apparatus for preventing duplicate login by the same user in this embodiment further includes: an obtaining module 24 configured to acquire record information from an external cache space. Further, when the record information is stored in other specific spaces, the acquisition module 24 can also be set to acquire record information from other specific spaces.

In this embodiment, the user identity in the record information is the user identity of the authorized user. In order to ensure that the user who is successfully logged in is an authorized user who has successfully registered, the judgment module 22 generally needs to carry the login request. The user identity in the information is verified, and the user's identity is authenticated before the user accesses the logged-in website.

Therefore, the apparatus for preventing the same user from repeatedly logging in may further include: a verification module configured to match the user identity in the login request with the user identity in the acquired registry, and if the matching is successful, the verification succeeds, and the matching is performed. Failure, verification failed. The user identifier of the user who is successfully registered is stored in the registry, and the registry may be formed by the service side collecting the registered user identity after the user successfully registers. The registry can be stored in the same cache space as the record information, or it can be stored in a different space.

In this embodiment, the filling manner of the user identity in the record information includes: after the user is successfully registered, filling the user identity registered by the user into the record information, or successfully logging in after each successful login of the user. The user ID is populated into the record information. It can be foreseen that in the latter way, if a user logs out, the corresponding user identity and client identification information in the record information will be cleared.

In this embodiment, if the user identity in the record information adopts the former padding method, Recorded in the record information is the user identity of all registered users. When the verification module 24 verifies the user identity carried in the login request, the user identity in the login request can be directly matched with the record information. There is no need to additionally set the registry record to register the user's user identity, saving system computing resources and storage resources. If the latter two recording methods are adopted, it is necessary to additionally add a registry record to register the user identity of the user, which wastes storage space. Therefore, the former recording method is obviously more advantageous.

In this embodiment, since the client feature information recorded in the acquired record information is the client feature information of the client currently used by the user in the login state, it can be foreseen that the client used before the user launches after the user logs out of the current login. The corresponding record-client feature information in the record information is cleared. If the record information uses the form to record the user identification information and the client feature information, the user identification information corresponding to the user under the client feature information field is cleared. Customer profile information. The user identification information may be deleted or deleted at the same time. If the user logs in with the user identity, the user identity information of the corresponding successfully registered client may be directly filled into the record according to the user identity. Information.

Therefore, the judging module 22 needs to determine whether the user's current login is a duplicate login. Since the record information in this embodiment records the client feature information of the client currently used in the login state, the client feature information in the log information can be real-time. The client that successfully logs in to the user is reflected. Therefore, the present embodiment can determine whether the login is a duplicate login based on the record information.

Further, the determining module 22 is configured to query, according to the user identity carried in the login request, whether the client feature information field corresponding to the same user identity in the record information is empty; if not, the result of the determination is that the user is the duplicate login. ;

Or, according to the user identity carried in the login request, whether the client feature information in the client feature information field corresponding to the same user identity in the record information is logged in The client feature information carried in the request matches; if it does not match, the judgment result is that the user is a duplicate login this time.

Of course, the judging module 22 can also use the above two judgment methods in combination.

The response module is further configured to allow the user to log in successfully, and the client feature information carried in the login request is filled into the client corresponding to the same user identity in the record information. End feature information field.

When the judgment result of the judgment module 22 is repeated login, the response module 23 is configured to respond by one of the following three methods:

Reject the user's login request;

If the user is forced to log in, if the user is forced to log in, the user is forced to log out of the client that is successfully logged in, and the user is allowed to log in successfully. The client feature information field corresponding to the user ID of the user in the record information is recorded. The client feature information in the client is replaced with the client feature information of the client currently used by the user;

Determines whether the current login success status of the user is mandatory login. If yes, the user's current login request is rejected.

In this embodiment, when the user no longer needs to log in to the website to access the service for a long time, if the client is still in the login success state, the user may obtain the user information of the authorized user on the website through the client, thereby Lead to leakage of user information, resulting in privacy leaks or more serious economic losses. Therefore, in this embodiment, in order to further protect the security of the user data, the device for preventing the same user from repeatedly logging in may further include a protection module. Set to obtain the idle time for the user who has not successfully passed the login. When the idle time exceeds the time threshold, the client successfully logs out and deletes the user feature in the cache. Among them, the monitoring of the idle time can be realized by using the automatic session or the active exit to invoke the session session listener.

With the device for preventing the same user from repeatedly logging in, the receiving module can receive the login request of the user, and the determining module carries the user identity identifier and the client feature information of the client currently used by the user according to the login request, and the record information recorded in the record information. User identity and pair The client's client feature information used by the user in the login success state is used to determine whether the login is a duplicate login, and the response module uses the corresponding response when the determination result is a duplicate login, thereby avoiding repeated logins by the same user. The device of the embodiment is simple in implementation, and can repeatedly and accurately determine the repeated login behavior and respond to ensure that the user data is unique and secure, and the embodiment has an adverse effect on the service performance of the website caused by the prior art. The device does not affect the performance of the business, does not cause a performance bottleneck of the website, and can bring a better experience to the user.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in a storage medium (ROM/RAM, diskette, optical disk) by a computing device, and in some cases The steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Therefore, the invention is not limited to any particular combination of hardware and software.

The above is a further detailed description of the present invention in connection with the specific embodiments, and the specific embodiments of the present invention are not limited to the description. It will be apparent to those skilled in the art that the present invention may be made without departing from the spirit and scope of the invention.

Industrial applicability

The embodiment of the invention discloses a device and a method for preventing the same user from repeatedly logging in. The user may receive the login request of the user and obtain the record information. The login request carries the user identity and the client feature information of the client currently used by the user. The user identity field and the client feature information field are stored in the record information, and are used to record the identity of the authorized user. The identifier and the client feature information of the client that is currently in the login success state of the user, after receiving the login request of the user, according to the information carried in the login request and the record information, can accurately and quickly determine whether the user is currently Repeat the login, and when the judgment result is repeated login, respond accordingly to prevent the same user from repeatedly logging in to ensure that the user data is unique and secure. Compared with the prior art, the service software session feature is used, or the server software session is automatically synchronized. The copy function, or the way to maintain the login status of the same user by means of the database, has no effect on the performance of the website. When a large number of users use the website, the performance bottleneck is not caused to the website, which is beneficial to improving the user's website usage. And expand the capacity of the website.

Claims

A device for preventing duplicate logins by the same user, including:

The receiving module is configured to receive a login request of the user, where the information carried in the login request includes the user identity identifier and client feature information of the client currently used by the user;

The determining module is configured to determine, according to the information carried in the login request and the obtained record information, whether the user is a duplicate login, the record information includes a user identity identifier field, and a client corresponding to the user identity identifier field. An end feature information field, where the user identity identifier field is used to record a user identity of the authorized user, and the client feature information field is used to record client feature information of the client that is currently used by the user in the login success state;

The response module is configured to respond to the login request according to a preset manner if the determination result of the determining module is a repeated login, to prevent the same user from repeatedly logging in.
The apparatus for preventing repeated login by the same user according to claim 1, wherein

The response module is further configured to: if the determination result of the determining module is a non-repetitive login, permit the user to successfully log in this time, and fill the record information carried in the login request into the record information. The client feature information field corresponding to the same user identity.
The apparatus for preventing repeated login by the same user according to claim 1, wherein the determining module is configured to:

Determining, according to the user identity identifier carried in the login request, whether the client feature information field corresponding to the identity of the same user in the record information is empty; if not, determining that the user is a duplicate login this time ;

Or, according to the user identity identifier carried in the login request, querying whether the client feature information in the client feature information field corresponding to the same user identity in the record information is the same as that carried in the login request. The client feature information is matched; if there is no match, the judgment result is that the user is a duplicate login this time.
The apparatus for preventing repeated login by the same user according to claim 1, further comprising: an obtaining module configured to acquire the record information from an external cache space.
The apparatus for preventing repeated login by the same user according to any one of claims 1 to 4, wherein the response module is configured to pass one of the following three methods if the determination result of the determination module is repeated login Respond:

Rejecting the current login request of the user;

Prompting whether the user is forced to log in. If the user is forced to log in, the user is forced to log out of the client that is successfully logged in, and the user is allowed to log in successfully. The client feature information in the client feature information field corresponding to the user identity of the user is replaced with the client feature information of the client currently used by the user;

Determining whether the current login success status of the user is a mandatory login, and if yes, rejecting the current login request of the user.
A method for preventing duplicate logins by the same user, including:

Receiving a login request of the user, where the information carried in the login request includes a user identity identifier and client feature information of a client currently used by the user;

Determining, according to the information carried in the login request and the obtained record information, whether the user is a duplicate login, the record information includes a user identity identifier field, and a client feature information field corresponding to the user identity identifier field, The user identity field is used to record the user identity of the authorized user, and the client feature information field is used to record the client feature information of the client that is currently used by the user in the login success state;

If the result of the determination is a repeated login, the login request is responded to in a preset manner to prevent the same user from repeatedly logging in.
The method for preventing repeated login by the same user according to claim 6, further comprising:

If the result of the determination is a non-repeated login, the user is allowed to log in successfully, and the client feature information carried in the login request is filled in the client feature information field corresponding to the same user identity in the record information.
A method of preventing repeated login by the same user as claimed in claim 6, wherein Determining whether the user is a duplicate login this time according to the information carried in the login request and the obtained record information includes:

Determining, according to the user identity identifier carried in the login request, whether the client feature information field corresponding to the identity of the same user in the record information is empty; if not, determining that the user is a duplicate login this time ;

Or, according to the user identity identifier carried in the login request, querying whether the client feature information in the client feature information field corresponding to the same user identity in the record information is the same as that carried in the login request. The client feature information is matched; if there is no match, the judgment result is that the user is a duplicate login this time.
The method for preventing repeated login by the same user according to claim 6, further comprising the step of acquiring the record information as follows:

The record information is obtained from an external cache space.
The method for preventing repeated login by the same user according to any one of claims 6 to 9, wherein if the determination result is repeated login, responding to the login request according to a preset manner includes one of the following three manners:

Rejecting the current login request of the user;

Prompting whether the user is forced to log in. If the user is forced to log in, the user is forced to log out of the client that is successfully logged in, and the user is allowed to log in successfully. The client feature information in the client feature information field corresponding to the user identity of the user is replaced with the client feature information of the client currently used by the user;

Determining whether the current login success status of the user is a mandatory login, and if yes, rejecting the current login request of the user.