Account login method and device

Abstract

The present invention discloses an account login method and apparatus. The method comprises: generating a valid credential for the account login device after the account successfully logs in to the device, wherein the valid credential has a preset expiration date; determining the time interval between the current login and the previous login in the event of a subsequent login; and logging into the account and updating the valid credential if the time interval is less than the expiration date. The present invention solves the technical problem in related art software where, after a user's login identifier expires, the user needs to log in again, resulting in multiple logins and a poor user experience.

Description

Technical Field

[0001] The present invention relates to the field of user management, and in particular to an account login method and device. Background Art

[0002] In related technologies, each software app generates a unique identifier representing the user's identity after logging in. To ensure the security of the user account, this identifier expires within a certain period of time, requiring the user to log in again. This means that any login within the validity period does not require a new login. Once the validity period expires, the user will be required to log in again, regardless of how frequently they logged in before, resulting in a poor user experience due to frequent logins.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiment of the present invention provides an account login method and device to at least solve the technical problem in the related art that after the user login identifier expires, the user needs to re-login, resulting in multiple logins and poor user experience.

[0005] According to one aspect of an embodiment of the present invention, a method for logging into an account is provided, comprising: after an account successfully logs into a device, generating a valid credential for the account to log into the device, wherein the valid credential has a preset validity period; in case of a subsequent login of the account, determining the time interval between the current login and the last login; and in case the time interval is less than the validity period, logging into the account and updating the valid credential.

[0006] Optionally, after the account successfully logs in on the device, before generating valid credentials for the account to log in to the device, it also includes: receiving a login request for the account to log in on the device; performing password verification on the account according to the login request; and logging in to the account if the account passes the password verification.

[0007] Optionally, after the account successfully logs in on the device, generating a valid credential for the account to log in to the device includes: when the account successfully logs in to the device for the first time, generating the valid credential on the device based on the login account and login time; and receiving the valid credential sent by the device.

[0008] Optionally, the method further includes: sending a prompt message when the time interval exceeds the validity period, wherein the prompt message is used to prompt the account to perform password verification; and logging into the account when the password verification passes.

[0009] Optionally, after the account successfully logs in to the device, before generating a valid credential for the account to log in to the device, it also includes: receiving an adjustment request from the account to adjust the validity period of the valid credential, wherein the adjustment request includes the adjusted validity period of the valid credential; and responding to the adjustment request, modifying the validity period of the valid credential.

[0010] Optionally, when the time interval is less than the validity period, logging into the account and updating the valid certificate includes: logging into the account when the time interval is less than the validity period; updating the valid certificate according to the account and login time of this login, and updating the validity period of the valid certificate.

[0011] According to another aspect of an embodiment of the present invention, an account login device is also provided, including: a generation module, used to generate a valid credential for the account to log in to the device after the account successfully logs in to the device, wherein the valid credential has a preset validity period; a determination module, used to determine the time interval between the current login and the last login in the event of a subsequent login of the account; a first login module, used to log in to the account and update the valid credential when the time interval is less than the validity period.

[0012] Optionally, it also includes: a receiving module for receiving a login request for the account to log in on the device; a verification module for performing password verification on the account according to the login request; and a second login module for logging in to the account if the account passes the password verification.

[0013] According to another aspect of an embodiment of the present invention, a processor is further provided, wherein the processor is configured to run a program, wherein the program executes any one of the above-mentioned account login methods when running.

[0014] According to another aspect of an embodiment of the present invention, a computer storage medium is further provided, wherein the computer storage medium includes a stored program, wherein when the program is running, the device where the computer storage medium is located is controlled to execute any one of the above-mentioned account login methods.

[0015] In an embodiment of the present invention, after an account successfully logs in to a device, a valid credential for the account to log in to the device is generated, wherein the valid credential has a preset validity period; in the case of a subsequent login of the account, the time interval between the current login and the last login is determined; when the time interval is less than the validity period, the account is logged in and the valid credential is updated. This achieves the purpose of logging in again within the validity period of the valid credential, updating the valid credential, and extending the validity period of the valid credential, thereby achieving the technical effect of avoiding the problem, and further solving the technical problem in the related art that the software needs to re-login after the user login identification expires, resulting in multiple logins for the user and a poor user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0017] Figure 1 is a flow chart of an account login method according to an embodiment of the present invention;

[0018] Figure 2 2 is a schematic diagram of an account login device according to an embodiment of the present invention. DETAILED DESCRIPTION

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

[0020] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0021] According to an embodiment of the present invention, a method embodiment of an account login method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0022] Figure 1 is a flow chart of an account login method according to an embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0023] Step S102: After the account successfully logs in to the device, a valid credential for the account to log in to the device is generated, wherein the valid credential has a preset validity period;

[0024] Step S104, in the case of a subsequent login to the account, determining the time interval between the current login and the previous login;

[0025] Step S106: If the time interval is less than the validity period, log in to the account and update the valid credentials.

[0026] Through the above steps, after the account successfully logs in to the device, a valid credential for the account to log in to the device is generated, wherein the valid credential has a preset validity period; in the case of a subsequent login of the account, the time interval between the current login and the last login is determined; when the time interval is less than the validity period, the account is logged in and the valid credential is updated. This achieves the purpose of logging in again within the validity period of the valid credential, updating the valid credential, and extending the validity period of the valid credential, thereby achieving the technical effect of avoiding, and further solving the technical problem in the related art that the software needs to re-login after the user login identification expires, resulting in multiple logins for the user and a poor user experience.

[0027] The above account can be logged in on the device through the software APP on the device, using the account and password when logging in, and logging in when the account and password are correct and match.

[0028] After the account successfully logs in on the above-mentioned device, a valid credential for the account to log in on the device, such as a token, is generated on the device, where the valid credential includes the login time when the account successfully logs in on the device and the validity period of the valid credential.

[0029] The expiration date is the preset expiration date of the valid credential. Before generating the valid credential, the expiration date can be set according to the user's needs, which can improve the user's flexibility and allow the valid credential to be set according to the user's needs. The above expiration date can also be the default value of the valid credential, which is usually invisible to the user. The system operator can adjust the validity period of the valid credential by modifying the code. The invisibility to the user can prevent malicious settings by users, making it easier to conduct real analysis of the user's login behavior, and also avoid the problem of reduced account security caused by the user setting an excessively long time.

[0030] After the valid credential is generated, it is sent to the server. The execution subject of the above steps may be the server, and the valid credential is stored on the device for subsequent processing.

[0031] When the account subsequently logs in to the device, the current login time and the time of the last successful login are obtained to determine the time interval between the two logins. If the time interval is less than the validity period of the valid credential, it means that the account has logged in frequently on the device. During the validity period of the valid credential, the account can log in directly without password verification, thereby avoiding multiple logins affecting the user experience.

[0032] After the current login is successful, the valid certificate is automatically updated so that the validity period of the valid certificate is recalculated and calculated from the current successful login. Within the validity period after the current login, if you successfully log in again, the validity period can be updated again. In this way, the validity period of the valid certificate is dynamically updated according to the login behavior of the account, so that when the account login frequency is high, password verification login can be avoided, thereby improving the user experience.

[0033] Compared with the unique identifier generated by the existing technology, the validity period of this identifier cannot be changed. Once generated, within the objective validity period, no matter how many times you log in, you will need to perform password verification when the validity period expires.

[0034] For example, if an account successfully logs in on January 2nd, a valid credential is generated. The validity period of the valid credential is one month. Before February 2nd, for example, if the account logs in again on January 25th, the validity period of the valid credential will be updated when logging in on January 25th. The validity period of the valid credential will be before February 25th. The validity period of the valid credential will be automatically updated with each login. Compared with the existing technology, if you log in on January 2nd and generate an ID with a validity period of one month, you can log in any number of times before February 2nd, but this will not affect the change of the validity period. Once February 2nd is exceeded, password verification is required. If the account is frequently logged in, it will lead to a poor user experience for the account.

[0035] Optionally, after the account successfully logs in on the device, before generating valid credentials for the account to log in to the device, it also includes: receiving a login request for the account to log in on the device; performing password verification on the account according to the login request; and logging in to the account if the account passes the password verification.

[0036] When logging in to the device, the account can be verified by password verification. If the password and account number are correct and match accurately, the account is allowed to log in to the device. In other implementations of this embodiment, the account can also be verified by fingerprint verification, face verification, unlock gesture verification, etc. If the verification is passed, the account is allowed to log in to the device.

[0037] Only when the account logs in successfully can a valid credential be generated to manage the user's subsequent logins.

[0038] Optionally, after the account successfully logs in on the device, generating valid credentials for the account to log in to the device includes: when the account successfully logs in to the device for the first time, generating valid credentials on the device based on the login account and login time; and receiving the valid credentials sent by the device.

[0039] When an account successfully logs in to a device for the first time, a valid credential is generated on the device based on the login account and login time. Specifically, the MD5 algorithm or hash algorithm is used to calculate the final data or bytes of the login account information, device information, and login time, which serves as the valid credential. This valid credential is set with a corresponding expiration date. The system or server can monitor the expiration date using a timing algorithm and update the valid credential if the account logs in again within the expiration date.

[0040] Optionally, it also includes: sending a prompt message when the time interval exceeds the validity period, wherein the prompt message is used to prompt the account to perform password verification; if the password verification is passed, logging into the account.

[0041] If the time interval between the user's current login time and the last login time exceeds the above-mentioned validity period, it means that the account login frequency is low and login is not frequent. A prompt message is sent to prompt the account to verify the password. If the password verification is successful, the account is logged in.

[0042] Optionally, after the account successfully logs in on the device and before generating valid credentials for the account to log in to the device, it also includes: receiving an adjustment request from the account to adjust the validity period of the valid credentials, wherein the adjustment request includes the adjusted validity period of the valid credentials; responding to the adjustment request and modifying the validity period of the valid credentials.

[0043] The validity period can be adjusted based on user needs. Specifically, an adjustment request is received from an account to adjust the validity period of a valid credential, wherein the adjustment request includes the adjusted validity period of the valid credential; and the validity period of the valid credential is modified in response to the adjustment request. This allows the validity period to be adjusted based on user needs, improving the adaptability of the validity period to different users and thereby enhancing the user experience.

[0044] Optionally, when the time interval is less than the validity period, logging into the account and updating the valid credentials includes: when the time interval is less than the validity period, logging into the account; updating the valid credentials according to the account and login time of this login, and updating the validity period of the valid credentials.

[0045] The above-mentioned updating of valid credentials includes updating the valid credentials according to the account information, device information and login time of this login, as well as updating the validity period of the valid credentials. Thus, the valid credentials are dynamically updated according to the user's login behavior.

[0046] It should be noted that the embodiment of the present application also provides an optional implementation method, which is described in detail below.

[0047] This embodiment aims to improve the app user experience and reduce unnecessary user operations. It provides a method for enabling users to log in to frequently used websites or software apps only once on the same device, eliminating the need for multiple logins, even if the user uses them daily or monthly. Specifically, it provides a method for enabling users to log in to frequently used websites and software apps without multiple logins.

[0048] Specifically, when a user logs in to the APP for the first time, the login time and the unique valid credential token generated after login are recorded and stored locally, and the unique identifier of the device is sent to the server using a network request. Each time the user opens the APP, the last login time is obtained and compared with the current time. If the comparison result is greater than the validity period of the unique valid credential, the token has expired, indicating that the user does not use the software frequently and logging in again will not affect the user experience. A prompt needs to be popped up to ask the user to log in again. If the comparison result is less than the validity period of the unique valid credential, indicating that the user uses the software frequently and logs in multiple times, affecting the user experience, then a network request can be sent through a token that has not yet expired to silently refresh the token and update the token validity period. The user does not need to log in again.

[0049] Figure 2 is a schematic diagram of an account login device according to an embodiment of the present invention. Figure 2As shown, according to another aspect of an embodiment of the present invention, an account login device is also provided, including: a generation module 22, a determination module 24 and a first login module 26. The device is described in detail below.

[0050] The generation module 22 is used to generate a valid credential for the account to log in to the device after the account successfully logs in to the device, wherein the valid credential has a preset validity period; the determination module 24 is connected to the above-mentioned generation module 22 and is used to determine the time interval between the current login and the last login in the case of subsequent account login; the first login module 26 is connected to the above-mentioned determination module 24 and is used to log in to the account and update the valid credential when the time interval is less than the validity period.

[0051] Through the above-mentioned device, after the account successfully logs in to the device, a valid credential for the account to log in to the device is generated, wherein the valid credential has a preset validity period; in the case of a subsequent login of the account, the time interval between the current login and the last login is determined; when the time interval is less than the validity period, the account is logged in and the valid credential is updated. This achieves the purpose of logging in again within the validity period of the valid credential and updating the valid credential, thereby achieving the technical effect of avoiding the validity period of the valid credential, and further solving the technical problem in the related art that the software needs to re-login after the user login identification expires, resulting in multiple logins for the user and a poor user experience.

[0052] Optionally, it also includes: a receiving module for receiving a login request for an account to log in to the device; a verification module for performing password verification on the account according to the login request; and a second login module for logging in to the account if the account passes the password verification.

[0053] According to another aspect of an embodiment of the present invention, a processor is further provided, and the processor is used to run a program, wherein when the program is run, any one of the above-mentioned account login methods is executed.

[0054] According to another aspect of an embodiment of the present invention, a computer storage medium is further provided, which includes a stored program, wherein when the program is running, the device where the computer storage medium is located is controlled to execute any one of the above account login methods.

[0055] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0056] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0057] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0058] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0059] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0060] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store program codes.

[0061] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for logging into an account, characterized in that: include: After the account successfully logs in to the device, a valid credential for the account to log in to the device is generated, wherein the valid credential has a preset validity period; In the event of a subsequent login to the account, determining the time interval between the current login and the previous login; If the time interval is less than the validity period, log in to the account and update the valid credential; The validity period is set according to user requirements or system default settings; The valid credentials are obtained by performing an encryption algorithm on the login account information, device information and login time; The method further includes the system monitoring the validity period according to a timing algorithm, and updating the valid credentials when the account logs in again within the validity period; After the account successfully logs in to the device, and before generating a valid credential for the account to log in to the device, the process further includes: receiving an adjustment request from the account for adjusting the validity period of the valid certificate, wherein the adjustment request includes the adjusted validity period of the valid certificate; In response to the adjustment request, modify the validity period of the valid certificate; After the account successfully logs in to the device, generating a valid credential for the account to log in to the device includes: When the account successfully logs in to the device for the first time, generating the valid credential on the device according to the login account and login time; Receive a valid credential sent by the device.

2. The method according to claim 1, characterized in that After the account successfully logs in to the device, before generating a valid credential for the account to log in to the device, the method further includes: receiving a login request for the account to log in on the device; Performing password verification on the account according to the login request; When the account passes the password verification, the account is logged in.

3. The method according to claim 1, characterized in that Also includes: When the time interval exceeds the validity period, sending a prompt message, wherein the prompt message is used to prompt the account to perform password verification; When the password verification is passed, log in to the account.

4. The method according to any one of claims 1 to 3, characterized in that When the time interval is less than the validity period, logging into the account and updating the valid credential includes: When the time interval is less than the validity period, logging into the account; The valid certificate is updated according to the account and login time of this login, and the validity period of the valid certificate is updated.

5. An account login device, characterized in that: include: A generating module, configured to generate a valid credential for the account to log into the device after the account successfully logs in to the device, wherein the valid credential has a preset validity period; a determination module for determining, in the event of a subsequent login by the account, a time interval between the current login and the previous login; a first login module, configured to log into the account and update the valid credential if the time interval is less than the validity period; The validity period is set according to user requirements or system default settings; The valid credentials are obtained by performing an encryption algorithm on the login account information, device information and login time; The device is also used for the system to monitor the validity period according to a timing algorithm, and to update the valid credentials when the account logs in again within the validity period; wherein, after an account successfully logs in to a device and before generating a valid credential for the account to log in to the device, the apparatus is further configured to receive an adjustment request from the account to adjust the validity period of the valid credential, wherein the adjustment request includes the adjusted validity period of the valid credential; and in response to the adjustment request, modify the validity period of the valid credential; The generating module further includes: a generating submodule for generating the valid credential on the device according to the login account and login time when the account successfully logs in to the device for the first time; and a receiving submodule for receiving the valid credential sent by the device.

6. The device according to claim 5, characterized in that Also includes: A receiving module, configured to receive a login request from the account on the device; A verification module, configured to perform password verification on the account according to the login request; The second login module is used to log in to the account if the account passes the password verification.

7. A processor, characterized in that: The processor is used to run a program, wherein the program executes the account login method according to any one of claims 1 to 4 when running.

8. A computer storage medium, characterized in that The computer storage medium includes a stored program, wherein when the program is running, the device where the computer storage medium is located is controlled to execute the account login method according to any one of claims 1 to 4.

Images